For some reason my PermissionsBukkit isn't working. There is no error in the console but it acts like neither me nor my friend are in any group. Here's my config: Code: # PermissionsBukkit configuration file # # A permission node is a string like 'permissions.build', usually starting # with the name of the plugin. Refer to a plugin's documentation for what # permissions it cares about. Each node should be followed by true to grant # that permission or false to revoke it, as in 'permissions.build: true'. # Some plugins provide permission nodes that map to a group of permissions - # for example, PermissionsBukkit has 'permissions.*', which automatically # grants all admin permissions. You can also specify false for permissions # of this type. # # Users inherit permissions from the groups they are a part of. If a user is # not specified here, or does not have a 'groups' node, they will be in the # group 'default'. Permissions for individual users may also be specified by # using a 'permissions' node with a list of permission nodes, which will # override their group permissions. World permissions may be assigned to # users with a 'worlds:' entry. # # Groups can be assigned to players and all their permissions will also be # assigned to those players. Groups can also inherit permissions from other # groups. Like user permissions, groups may override the permissions of their # parent group(s). Unlike users, groups do NOT automatically inherit from # default. World permissions may be assigned to groups with a 'worlds:' entry. # # The cannot-build message is configurable. If it is left blank, no message # will be displayed to the player if PermissionsBukkit prevents them from # building, digging, or interacting with a block. Use '&' characters to # signify color codes. groups: default: prefix: '&7(Member)&7 ' default: true permissions: - modifyworld.* - essentials.help - essentials.ignore - essentials.list - essentials.msg - essentials.r - essentials.rules - essentials.suicide - essentials.ping - essentials.spawn - essentials.back - essentials.tpa - essentials.tpaccept - essentials.tpdeny VIP: prefix: '&6(VIP)&7 ' permissions: - -modifyworld.mobtarget.monster.creeper - modifyworld.* inheritance: - Default Moderator: prefix: '&2(Mod)&7 ' permissions: - essentials.socialspy - essentials.seen - essentials.whois - essentials.ban - essentials.banip - essentials.kick - essentials.mute - essentials.invsee - essentials.tempban inheritance: - Default Admins: prefix: '&4(Admin)&7 ' permissions: - '*' Owner: prefix: '&5(Owner)&7 ' permissions: - '*' users: kd280z: group: - Default CameleonDude: group: - Owner messages: build: '&cYou do not have permission to build here.' debug: false
Your using permissionsEX format. In permissionsBukkit nodes have to have "<node>: true" or "<node>: false" eg - essentials.help: true
Ohhh ok. For the * node would it be "- *: true" or "- '*': true"? I just tried it both ways and he's not getting any of the permissions his group should have. I have even tried type "/permissions setrank cameleondude owner" and nothing happens. Also it might be worth mentioning that "/permissions group list" will not work either. I found a guide at The Ultimate Guide to Permissions | Bukkit Forums and after my best attempts at following that this is what I ended up with: PHP: # PermissionsBukkit configuration file## A permission node is a string like 'permissions.build', usually starting# with the name of the plugin. Refer to a plugin's documentation for what# permissions it cares about. Each node should be followed by true to grant# that permission or false to revoke it, as in 'permissions.build: true'.# Some plugins provide permission nodes that map to a group of permissions -# for example, PermissionsBukkit has 'permissions.*', which automatically# grants all admin permissions. You can also specify false for permissions# of this type.## Users inherit permissions from the groups they are a part of. If a user is# not specified here, or does not have a 'groups' node, they will be in the# group 'default'. Permissions for individual users may also be specified by# using a 'permissions' node with a list of permission nodes, which will# override their group permissions. World permissions may be assigned to# users with a 'worlds:' entry.## Groups can be assigned to players and all their permissions will also be# assigned to those players. Groups can also inherit permissions from other# groups. Like user permissions, groups may override the permissions of their# parent group(s). Unlike users, groups do NOT automatically inherit from# default. World permissions may be assigned to groups with a 'worlds:' entry.## The cannot-build message is configurable. If it is left blank, no message# will be displayed to the player if PermissionsBukkit prevents them from# building, digging, or interacting with a block. Use '&' characters to# signify color codes. groups: Member: prefix: '&7(Member)&7 ' permissions: modifyworld.*: true essentials.help: true essentials.ignore: true essentials.list: true essentials.msg: true essentials.r: true essentials.rules: true essentials.suicide: true essentials.ping: true essentials.spawn: true essentials.back: true essentials.tpa: true essentials.tpaccept: true essentials.tpdeny: true inheritance: - default VIP: prefix: '&6(VIP)&7 ' permissions: modifyworld.*: true inheritance: - Member Moderator: prefix: '&2(Mod)&7 ' permissions: essentials.socialspy: true essentials.seen: true essentials.whois: true essentials.ban: true essentials.banip: true essentials.kick: true essentials.mute: true essentials.invsee: true essentials.tempban: true inheritance: - Member Admins: prefix: '&4(Admin)&7 ' permissions: *: true Owner: prefix: '&5(Owner)&7 ' permissions: *: trueusers: kd280z: groups: Member CameleonDude: groups: Ownermessages: build: '&cYou do not have permission to build here.' debug: false I also tried removing the prefix lines and making the star nodes look like '*' but neither of those worked. EDIT by Moderator: merged posts, please use the edit button instead of double posting.
That helped a lot, now the /permissions group list works and the server actually recognizes the file. I ran into another issue: My friend is set as an owner and I am (I believe) set as a member. When we first reloaded after removing modifyworld he could not use /tp but I was opped and I typed "/permissions setrank cameleondude Owner" and now it seems like he can use all commands other than /permissions commands. I could not use commands until he opped himself and set me as a member which I believe means member is not set as the default rank. Also I cannot interact with any parts of the world and he can only break things while using the correct tool. This is what the config looks like right now: PHP: # PermissionsBukkit configuration file## A permission node is a string like 'permissions.build', usually starting# with the name of the plugin. Refer to a plugin's documentation for what# permissions it cares about. Each node should be followed by true to grant# that permission or false to revoke it, as in 'permissions.build: true'.# Some plugins provide permission nodes that map to a group of permissions -# for example, PermissionsBukkit has 'permissions.*', which automatically# grants all admin permissions. You can also specify false for permissions# of this type.## Users inherit permissions from the groups they are a part of. If a user is# not specified here, or does not have a 'groups' node, they will be in the# group 'default'. Permissions for individual users may also be specified by# using a 'permissions' node with a list of permission nodes, which will# override their group permissions. World permissions may be assigned to# users with a 'worlds:' entry.## Groups can be assigned to players and all their permissions will also be# assigned to those players. Groups can also inherit permissions from other# groups. Like user permissions, groups may override the permissions of their# parent group(s). Unlike users, groups do NOT automatically inherit from# default. World permissions may be assigned to groups with a 'worlds:' entry.groups: Member: permissions: essentials.help: true essentials.ignore: true essentials.list: true essentials.msg: true essentials.r: true essentials.rules: true essentials.suicide: true essentials.ping: true essentials.spawn: true essentials.back: true essentials.tpa: true essentials.tpaccept: true essentials.tpdeny: true inheritance: - default VIP: inheritance: - Member Moderator: permissions: essentials.socialspy: true essentials.seen: true essentials.whois: true essentials.ban: true essentials.banip: true essentials.kick: true essentials.mute: true essentials.invsee: true essentials.tempban: true inheritance: - Member Admins: permissions: '*': true Owner: permissions: '*': trueusers: kd280z: groups: - member CameleonDude: groups: - ownermessages: build: '&cYou do not have permission to build here.'debug: falseAutoUpdate: true
Code: inheritance: - default means that group inherited all the permissions nodes from the group stated, because you dont have a group called default that line needs to be removed. If i remember correctly the group near the top of the config is the default one though i maybe wrong. Just a suggestion, you config from before was of permissionsEX, did you switch over to permBukkit? i would recommend you use permEX cause u have the configuration for it already
