[ADMN/DEV] PermissionsBukkit v2.0 - Official Default Groups Plugin [1.5.2-R1.0]

Discussion in 'Archived: Plugin Releases' started by SpaceManiac, Jul 17, 2011.

  1. Offline


    PermissionsBukkit - the Official Default Groups Plugin
    Current Version: v2.0
    Find PermissionsBukkit on BukkitDev!

    If you are getting a specific error or cannot determine what is wrong with your permissions file, filing a ticket on BukkitDev will make me much more likely to respond to you; general questions are best to ask in this thread or on the forums on BukkitDev.

    It's been a long time coming, but with the accomplishment of build 1000 Bukkit has finally accomplished a built-in Permissions system (codenamed Superperms). For more info on how they work, and how to integrate them with your plugin, see the official Permissions FAQ. Keep in mind that you should rarely, if ever, have to hook this plugin directly; instead keep things in the realm of checking player.hasPermission("yourplugin.node"). The FAQ thread has more info on how to use Superperms with things like chat prefixes/suffixes.

    • Storage of users and groups in plugins/PermissionsBukkit/config.yml.
    • Both users and groups can be assigned individual permissions and parent groups to inherit permissions from.
    • Support for global and per-world permissions.
    • Reload configuration from file with out reloading the plugin.
    • Ability to check if a player has a specific permission node.
    • Ability to dump all permissions a player has and the plugins that set them.
    • Ability to print plugin, description, and default for a given permission node.
    • Ability to modify the permissions of groups and users and the groups of a user in-game.
    • Built-in antibuild via the "permissions.build" node (defaults to allowing anyone to build).
    • A minimalistic bridge from Permissions 3.0 to Superperms is available as a separate plugin, which does not depend on PermissionsBukkit.
    Command Usage:

    Show Spoiler
    PermissionsBukkit uses the command /permissions, with aliases /perms and /perm.

    /permissions reload - reload the configuration from disk.
    /permissions check <node> [player] - check if a player or the sender has a permission (any plugin).
    /permissions info <node> - prints information on a specific permission.
    /permissions dump [player] [page] - prints info about a player's (or the sender's) permissions.
    /permissions setrank <player> <group> - set a player to be in a group with per-group permissions.
    /permissions group - list group-related commands.
    /permissions group list - list all groups.
    /permissions group players <group> - list players in a group.
    /permissions group setperm <group> <[world:]node> [true|false] - set a permission on a group.
    /permissions group unsetperm <group> <[world:]node> - unset a permission on a group.
    /permissions player - list player-related commands.
    /permissions player groups <player> - list groups a player is in.
    /permissions player setgroup <player> <group,...> - set a player to be in only the given groups.
    /permissions player addgroup <player> <group> - add a player to a group.
    /permissions player removegroup <player> <group> - remove a player from a group.
    /permissions player setperm <player> <[world:]node> [true|false] - set a permission on a player.
    /permissions player unsetperm <player> <[world:]node> - unset a permission on a player.

    All commands have in-game help and are usable from the server console.

    Show Spoiler
    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 permissions for all PermissionsBukkit commands. 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.

    An example configuration file might look like this:
                permissions.example: true
            - admin
                permissions.build: false
                permissions.*: true
            - user
                permissions.build: true
                    coolplugin.item: true
            - default
        build: '&cYou do not have permission to build here.'

    Show Spoiler
    PermissionsBukkit checks for the following permission nodes:
    • permissions.build - Allows a player to build. Defaults to true.
    • permissions.help - Allows viewing of usage for /permissions.
    • permissions.reload - Allows use of /permissions reload.
    • permissions.check - Allows use of /permissions reload.
    • permissions.info - Allows use of /permissions reload.
    • permissions.dump - Allows use of /permissions reload.
    • permissions.group.help - Allows viewing of usage for /permissions group.
    • permissions.group.list - Allows use of /permissions group list.
    • permissions.group.players - Allows use of /permissions group players.
    • permissions.group.setperm - Allows use of /permissions group setperm.
    • permissions.group.unsetperm - Allows use of /permissions group unsetperm.
    • permissions.player.help - Allows viewing of usage for /permissions player
    • permissions.player.groups - Allows use of /permissions player groups.
    • permissions.player.setgroup - Allows use of /permissions player setgroup.
    • permissions.player.addgroup - Allows use of /permissions player addgroup.
    • permissions.player.removegroup - Allows use of /permissions player removegroup.
    • permissions.player.setperm - Allows use of /permissions player addgroup.
    • permissions.player.unsetperm - Allows use of /permissions player removegroup.
    Also, the following parent nodes are provided for convenience:

    • permissions.* - Maps to permissions.help, .reload, .check, .info, .dump, and to permissions.group.* and permissions.player.*. Defaults to op.
    • permissions.group.* - Maps to permissions.group.help, .list, .players, .setperm, and .unsetperm.
    • permissions.player.* - Maps to permissions.player.help, .groups, .setgroup, .addgroup, .removegroup, .setperm, and .unsetperm.

    Frequently Asked Questions:
    1. Where are my * nodes? (open)
    Bukkit's Superperms has no built-in concept of a global '*' node that automatically gives all permissions, which is intentional - a player can instead be given all permissions by being given 'op' status (that is, listed in ops.txt). Additionally, individual plugins define a parent node (which could be 'pluginname.*' or 'pluginname.all' or anything else) which maps to whatever subpermissions in that plugin the author desires.

    An example is PermissionsBukkit, which provides three such permissions: 'permissions.group.*' for all /permissions group commands, 'permissions.player.*' for all /permissions player commands, and'permissions.*' for all /permissions commands (including permissions.group.* and permissions.player.*).

    If you are using SuperpermsBridge, you can do something similar to '*' nodes for plugins which use Permissions 2.7/3.1 - see the next FAQ for more information.
    2. How do I use SuperpermsBridge? (open)
    SuperpermsBridge is kind of like FakePermissions for GroupManager or PermissionsBridge for PermissionsEx. Once it's installed, it pretends to be the Permissions plugin and converts any plugins that use Permissions 2.7 or Permissions 3.1 to use Superperms instead.

    You can have PermissionsBukkit without SuperpermsBridge or SuperpermsBridge without PermissionsBukkit if you like, but both of these are limited in functionality. If you install SuperpermsBridge without PermissionsBukkit you will not be able to make use of PermissionsBukkit's groups feature or admin commands, and if you install PermissionsBukkit without SuperpermsBridge, plugins that have not updated to use Superperms directly will not function.

    For plugins that use Permissions 2.7/3.1, you can use the special node 'superpermbridge.*' to give the equivalent of what used to be the '*' node for plugins that do not use Superperms directly. If you don't want to give the * node, you can also use the node 'superpermbridge.pluginname' to do the equivalent of what used to be the 'pluginname.*' node. Once again, these only apply to plugins that SuperpermsBridge handles and not to plugins using Superperms directly.
    3. How do I use the root permissions.yml? (open)
    The file 'permissions.yml' in the root of your server can be used to set up custom parent permissions. Parent permissions are a single node that, when given to a player or group, automatically give all their children node. Here's a simple example:
            commandbook.motd: true
            commandbook.say: true
            commandbook.say.me: true
            commandbook.time: true
    Now, if you give a player the node 'server.basics', they automatically get all the nodes listed here. Children may also say 'false' instead of 'true', in which case giving the parent will remove the child instead of giving it.

    You can also specify a description if you like, which can be used by plugins to provide information on your node (such as PermissionsBukkit's /perm info command). If you want, you can also provide a default, which can be one of "true", "false", "op", or "notop". CraftBukkit will automatically assign everyone, no one (default), ops, or non-ops the children permissions based on the specified default. Without any plugin like PermissionsBukkit, you can use this defaults system as a limited way to assign people permissions. Here's a more complex example:
        description: Basic permissions for My Cool Server.
        default: true
            commandbook.motd: true
            commandbook.say: true
            commandbook.say.me: true
            commandbook.time: true
        description: Admin permissions for My Cool Server.
        default: op
            commandbook.broadcast: true
            commandbook.teleport: true
            commandbook.kick: true
            commandbook.ban: true
    You can also define permissions without children, but this is of limited usefulness in permissions.yml (though is important in plugin.yml; see question #6)
    4. How do I switch from (other Permissions plugin)? (open)
    Depends on the Permissions plugin! If you were using PEX's YAML backend, I have a converter done and available on the PermissionsBukkit Tools page. Also available on the tools page is an automatic converter for Essentials GroupManager users.yml and groups.yml files. Automatic converters for Permissions 2.7 and 3.x are on their way, but in the meantime you can still convert your configurations manually.
    5. Where are prefixes and suffixes (or option nodes)? (open)
    Bukkit Superperms has no built-in prefix/suffix settings or non-boolean permission nodes, so individual chat plugins will have to start supporting Superperms in order to make use of non-Permissions-plugin based prefixes and suffixes. Herochat, iChat, and Simple Suffix are all aware of the Superperms update, but in the meantime you can use mChat, which already supports Superperms.

    Once you install mChat and configure the mchat.prefix, mchat.suffix, and mchat.group names in its configuration file (see the example), use PermissionsBukkit to give players or groups the permissions "mchat.prefix.admin", replacing "admin" with whatever node you configured. For example, with an mchat configuration that looks similar to this:
    da-name-format: '+prefix+name&e'
    date-format: HH:mm:ss
    message-format: '+prefix+name&f: +message'
            admin: '&4DtK [SO] &7 '
            sadmin: '&9DtK [SA] &7 '
            jadmin: '&aDtK [JA] &7  '
            member: '&cDtK [M] &7 '
    You can assign players or groups the mchat.prefix.admin node to get the "SO" prefix, mchat.prefix.sadmin to get the "SA" prefix, and so on.
    6. (Coders) How do I set up my plugin.yml? (open)
    Take a look at this post in Dinnerbone's FAQ for an example. This is a lot like the setup of permissions.yml (see above), but you can also define non-parent permissions (just include description and default and leave out children).
    7. Is PermissionsBukkit outdated? (open)
    No! PermissionsBukkit 2.0 was last updated for 1.3.1-R2.0, is verified to work on 1.4.7-R1.0, and is unlikely to break on future releases.

    Current Version:

    PermissionsBukkit v2.0 (jar) (details)
    Old Versions:
    PermissionsBukkit v1.6 (jar) (details)



    Friday 7 September 2012 (2.0)
    • Fixed a case-sensitivity issue with setting per-world permissions that could cause some permissions to fail to apply.
    • Added /perm setrank <player> <group> subcommand (alias rank) with per-group permissions (permissions.setrank and permissions.setrank.<group>)
    • Added plugin metrics via http://mcstats.org/plugin/PermissionsBukkitMCStats (disableable in plugins/PluginMetrics/config.yml)
    Wednesday 29 February 2012 (1.6)
    • Fixed some massive issues that were caused due to having uploaded a buggy, in-development version instead of 1.5.
    • Note: If your configuration was messed up as a result of this issue, the new build should gradually correct it as needed.
    Saturday 25 February 2012 (1.5b)
    • Revamped to be compatible with R5.
    • Fixed issues with permissions not carrying properly on world change.
    • Many internal improvements for performance and stability.
    • SuperpermsBridge: in honor of R5 removing deprecated code, SuperpermsBridge is officially gone!
    Monday 18 July 2011 (1.1/1.2)
    • Fix BukkitContrib incompatibility issues.
    • Improved the output of the /perm check command.
    • Fixed issues when 'users:' is not specified in the config file.
    • Fixed the /permissions reload command.
    • SuperpermsBridge: improve wildcard handling; in addition to 'superpermbridge.*' and 'superpermbridge.pluginname', now supported are 'superpermbridge.plugin.*', 'superpermbridge.plugin.subnode.*', and so on.
    Monday 18 July 2011 (1.0/1.1)
    • SuperpermsBridge: adding the special 'superpermbridge.*' and 'superpermbridge.pluginname' nodes (see #2 in the FAQ for details).
    Sunday 17 July 2011 (1.0/1.0)

    • Initial release of PermissionsBukkit v1.0 and SuperpermsBridge v1.0.
    madmac, Gesundheit, tripleX and 23 others like this.
  2. Offline

    funky man

    No problems we should try and help each other more. You say you are trying to "figure out" permissionbukkit, but what is it you need help with/trouble your having?
  3. Offline


    When I have permissions.build: false players can't open doors. Is there a way to allow players to open doors, yet not be able to build anything?
  4. Offline


            - admin
                permissions.build: false
                lwc.deny: true
                commandbook.*: false
                permissions.*: true
                lwc.mod: true
                commandbook.*: true
                worldedit.*: true
                permissions.build: true
                lwc.protect: true
                lwc.deny: false
                commandbook.give.*: false
                commandbook.more: false
                commandbook.setspawn: false
                commandbook.time: false
                commandbook.spawnmob: false
                commandbook.weather: false
                commandbook.teleport: true
                commandbook.teleport.other: false
                commandbook.locations.coords: false
                commandbook.return: true
                commandbook.call: true
                commandbook.home.teleport: true
                commandbook.home.other: false
                commandbook.home.teleport.other: false
                commandbook.home.set: true
                commandbook.home.set.other: false
                commandbook.warp.teleport: true
                commandbook.warp.teleport.other: false
                commandbook.warp.set: false
                commandbook.warp.remove: false
                commandbook.warp.list: true
                commandbook.say: true
                commandbook.away: true
                commandbook.mute: false
                commandbook.clear: true
                commandbook.clear.other: false
                commandbook.slap: true
                commandbook.slap.other: false
                commandbook.rocket: true
                commandbook.rocket.other: false
                commandbook.barrage: true
                commandbook.barrage.other: false
                commandbook.shock: true
                commandbook.shock.other: false
                commandbook.thor: false
                commandbook.gamemode: false
                commandbook.kick: false
                commandbook.bans: false
                commandbook.god: false
                worldedit.*: false
                permissions.*: true
                permissions.group: false
                permissions.player: false
                bukkit.command.*: false
        build: '&cYou do not have the permission to do this.'
    this is my config.yml, but it keeps returing
    2012-03-22 19:55:10 [SEVERE] [PermissionsBukkit] Unable to load configuration!
    2012-03-22 19:55:10 [WARNING] [PermissionsBukkit] Failed to write changed config.yml: plugins/PermissionsBukkit/config.yml (Permission denied)
    2012-03-22 19:57:02 [SEVERE] [PermissionsBukkit] Unable to load configuration!
    after I use the /permissions reload command.

    could anyone please help me?

    oke, I used the online YAML parser

    but now i get this warning
    2012-03-22 20:28:27 [WARNING] [PermissionsBukkit] Failed to write changed config.yml: plugins/PermissionsBukkit/config.yml (Permission denied)
    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: Jul 14, 2016
  5. Offline


    I am getting an error message from the console saying that the groups can not be recognized. However, when I tried to give permissions individually, this did not work either. In effect, none of the permissions are working.
  6. Offline


    Just change it in the bukkit.yml and restart your server (a value of 0 or 1 should do).
    If you are using multiverse, the radius can be set per world. Refer to Multiverse documentation if that is the case.
  7. Offline


    disregard my last post, both the error are now gone.
    but i got a new in return.

    whenever i try to move someone into a group i get this in the server:
    2012-03-25 12:50:17 [SEVERE] null
    org.bukkit.command.CommandException: Unhandled exception executing command 'permissions' in plugin PermissionsBukkit v1.6
        at org.bukkit.command.PluginCommand.execute(PluginCommand.java:42)
        at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:166)
        at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:469)
        at net.minecraft.server.NetServerHandler.handleCommand(NetServerHandler.java:906)
        at net.minecraft.server.NetServerHandler.chat(NetServerHandler.java:866)
        at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:849)
        at net.minecraft.server.Packet3Chat.handle(Packet3Chat.java:33)
        at net.minecraft.server.NetworkManager.b(NetworkManager.java:229)
        at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:116)
        at net.minecraft.server.NetworkListenThread.a(NetworkListenThread.java:78)
        at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:554)
        at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:452)
        at net.minecraft.server.ThreadServerApplication.run(SourceFile:490)
    Caused by: java.lang.NullPointerException
        at com.platymuus.bukkit.permissions.PermissionsCommand.createPlayerNode(PermissionsCommand.java:400)
        at com.platymuus.bukkit.permissions.PermissionsCommand.playerCommand(PermissionsCommand.java:301)
        at com.platymuus.bukkit.permissions.PermissionsCommand.onCommand(PermissionsCommand.java:152)
        at org.bukkit.command.PluginCommand.execute(PluginCommand.java:40)
        ... 12 more
    bbqsamich likes this.
  8. Offline

    JD DeGaetano

    Is superpermsbridge working with 1.2.4? I need to use the .* nodes.
  9. Offline


    You should make a command to give EVERYONE a permission.
  10. Offline


    Uhh, are you talking about OP? Which gives everyone permission for everything...?
  11. Offline


    Can you please add the ability to reload/recalculate PermissionAttachments for other plugins. (via public methods)
    • public void registerPlayer(Player player);
    • public void unregisterPlayer(Player player);
    Because i want to create an autopromotion plugin. I managed to change the permissions(config), but i cannot apply them until server reload.
  12. Offline


    err??? that's already builtin u know?? use the "Default:" group, it applies to EVERYONE
  13. Offline


    Is there a way to still let users use doors, levers, buttons, pressureplates, etc... when i give them permissions.build: false ?
    I Just created a special showcase world where all of the best creations that have been made on my server will be displayed. Of course i don't wan't anyone to start editing things on a world thats only there for showing off creations. So i just give everyone permissions.build: false on this world.
    The problem now however is that they can't even leave the house where they first spawn in because they can't open doors....
  14. Offline


    Every time i try to give permissions with: permissions player setgroup [Name] [Group]
    I get this Error:

    [WARNING] Unexpected exception while parsing console command
    org.bukkit.command.CommandException: Unhandled exception executing command 'permissions' in plugin PermissionsBukkit v1.6
        at org.bukkit.command.PluginCommand.execute(PluginCommand.java:42)
        at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:166)
        at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:473)
        at org.bukkit.craftbukkit.CraftServer.dispatchServerCommand(CraftServer.java:469)
        at net.minecraft.server.MinecraftServer.b(MinecraftServer.java:599)
        at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:568)
        at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:452)
        at net.minecraft.server.ThreadServerApplication.run(SourceFile:490)
    Caused by: java.lang.NullPointerException
        at com.platymuus.bukkit.permissions.PermissionsCommand.createPlayerNode(PermissionsCommand.java:400)
        at com.platymuus.bukkit.permissions.PermissionsCommand.playerCommand(PermissionsCommand.java:286)
        at com.platymuus.bukkit.permissions.PermissionsCommand.onCommand(PermissionsCommand.java:152)
        at org.bukkit.command.PluginCommand.execute(PluginCommand.java:40)
        ... 7 more
    My Permissions Config:

          permissions.build: false
          permissions.build: true
          Sidekick.changename: true
          Sidekick.weather: true
          Sidekick.time: true
          Sidekick.heal: true
          Sidekick.clearinventory: true
          Sidekick.toollast: true
          Sidekick.teleport: true
          Sidekick.god: true
          Sidekick.survival: true
          Sidekick.creative: true
          Sidekick.tome: true
          Sidekick.eat: true
          Sidekick.listworlds: true
          permissions.*: true
        inheritance: User
          Sidekick.use: true
          Sidekick.anti: true
          Sidekick.realmode: true
          Sidekick.changename: true
          Sidekick.weapon: true
          Sidekick.weather: true
          Sidekick.pvp: true
          Sidekick.broadcast1: true
          Sidekick.broadcast2: true
          Sidekick.explodeme: true
          Sidekick.info: true
          Sidekick.time: true
          Sidekick.effect: true
          Sidekick.kick: true
          Sidekick.heal: true
          Sidekick.superjump: true
          Sidekick.clearinventory: true
          Sidekick.location: true
          Sidekick.broadcastlocation: true
          Sidekick.item: true
          Sidekick.realmode?: true
          Sidekick.afkmessage: true
          Sidekick.mysterybox: true
          Sidekick.teleport: true
          Sidekick.nomobs: true
          Sidekick.toollast: true
          Sidekick.worldgen: true
          Sidekick.tools: true
          Sidekick.quit: true
          Sidekick.join: true
          Sidekick.beware: true
          Sidekick.loginkit: true
          Sidekick.god: true
          Sidekick.antibuild: true
          Sidekick.signname: true
          Sidekick.portal: true
          Sidekick.rules: true
          Sidekick.sneaks: true
          Sidekick.nofire: true
          Sidekick.fly: true
          Sidekick.sk.money: true
          Sidekick.sk.pay: true
          Sidekick.sk.give: true
          Sidekick.suffix: true
          Sidekick.prefix: true
          Sidekick.survival: true
          Sidekick.creative: true
          Sidekick.tome: true
          Sidekick.restart: true
          Sidekick.xp: true
          Sidekick.kill: true
          Sidekick.eat: true
          Sidekick.water: true
          Sidekick.shotgun: true
          Sidekick.edit: true
          Sidekick.edit?: true
          Sidekick.world: true
          Sidekick.broadcast: true
          Sidekick.chat: true
          Sidekick.both: true
          Sidekick.spawner: true
          Sidekick.shutdown: true
          Sidekick.ban: true
          Sidekick.ip: true
          Sidekick.show: true
          Sidekick.g: true
          Sidekick.strike: true
          Sidekick.message: true
          Sidekick.set: true
          Sidekick.advertise: true
          Sidekick.all: true
          Sidekick.send: true
          Sidekick.setspawn: true
          Sidekick.spawn: true
          Sidekick.listworlds: true
          Sidekick.mode: true
          Sidekick.read: true
          Sidekick.player: true
          Sidekick.log: true
          Sidekick.move: true
          Sidekick.warn: true
          Sidekick.sell: true
          Sidekick.blockadd: true
          Sidekick.whois: true
          Sidekick.worldpvp: true
          Sidekick.lastseen: true
          Sidekick.file: true
          Sidekick.override: true
          Sidekick.wear: true
          Sidekick.potion: true
          permissions.*: true
          permissions.build: true
          permissions.help: true
          permissions.reload: true
          permissions.check: true
          permissions.info: true
          permissions.dump: true
          permissions.group.*: true
          permissions.group.help: true
          permissions.group.list: true
          permissions.group.players: true
          permissions.group.setperm: true
          permissions.group.unsetperm: true
          permissions.player.*: true
          permissions.player.help: true
          permissions.player.groups: true
          permissions.player.setgroup: true
          permissions.player.addgroup: true
          permissions.player.removegroup: true
          permissions.player.setperm: true
          permissions.player.unsetperm: true
        inheritance: Admin
      build: '&cYou do not have permission to build here.'
    debug: false
    Any Ideas?
  15. Offline


    Hey will this work on 1.2.4 Rb 1?
  16. Offline


    Permissions is working on my server just fine as we speak, on the latest build.
  17. I'm sorry, but this plugin is complete garbage. It is extremely glitchy, and poorly optimized
  18. Offline


    No, You just have no clue how to use it.
  19. Offline


    Before i saw this i couldn't undestand permissions. But this plugin is more simple. Thank you! I wanted my friends not having permissions to everything, and now they don't have :)
  20. Offline


    change user into users: ( not the group )
  21. Offline


    wait 1.2.3 permissions will work for 1.2.4 servers?
  22. Offline


    i wish
  23. Offline


    Can someone please help me with my permissions I am rather new to admin

    prefix: '&f[&7Default&f]'
    default: true
    build: true
    - modifyworld.
    - permissions.build: true
    - essentials.balance: true
    - essentials.tpa: true
    - essentials.home: true
    - essentials.spawn: true
    - essentials.sethome: true
    - essentials.tpdeny: true
    - essentials.tpallow: true
    - essentials.suicide: true
    - essentials.mail: true
    - essentials.sendmail: true
    - essentials.info: true
    - essentials.help: true
    - essentials.afk: true
    - essentials.rules: true
    - essentials.time: true
    - essentials.list: true
    - physicalshop.use: true
    - physicalshop.build: true
    - residence.create: true
    - multiverse.access.*: true
    prefix: '&f[&cAdmin&f]'
    default: false
    build: true
    - '*'
    - Admin
    build: '&cYou do not have permission to build here.'

    debug: false

  24. Offline


    Slippy309 aidanhd500
    Yes this plugin works perfectly fine on 1.2.4 servers.
    Unlike mods these plugins don't break every single update.

    That config file does not look anything like the config file should look for this plugin.
    I'm guessing that config file is made by a different permissions plugin.
  25. Offline


    I'm really confused. I've setup my config file and when I upload it to my server I see the file there and it's the same size as the one on my computer. However, when I reload the permissions mod the file blanks out completely and becomes 0bytes in size. Anyone else had this error or know what's going on?
  26. Offline


    Well if that is the case, can you please share your mystic secrets with us mere mortals? I have not been able to get this plugin to work for months now. I was using it previously with no issues but now it just will not load my config no matter what I do.
  27. Offline


    PermissionsPEX is your futere friend then =)
  28. Offline


    this Plugin works on 1.2.4 R1.0?
  29. Offline


    A few people claim it does but as they wont say HOW they got it work, we are not inclined to believe them.
  30. Offline


    First of all you need version 1.6 of permissionsbukkit. You can find it on the bukkitdev page. For some reason he didn't put a link in this page.
    If it still won't work show me any errors you might be getting in the console together with the content of your config.yml.
    Maybe try to regenerate the config and configure it again. You can regenerate it by removing the config.yml (or just renaming so you won't lose it)
  31. Offline


    no error , but don't load my configs! :eek:
                permissions.example: true
            - admin
                permissions.build: true
                ChestShop.shop.create: true
                ChestShop.shop.buy: true
                ChestShop.shop.sell : true
                iConomy.help: true
                iConomy.holdings: true
                iConomy.holdings.others: true
                iConomy.payment: true
                SecretSwitch.create: true
                lockette.user.create.*: true
                permissions.*: true
                ChestShop.shop.*: true
                iConomy.help: true
                iConomy.holdings: true
                iConomy.holdings.others: true
                iConomy.payment: true
                iConomy.accounts.create: true
                iConomy.accounts.remove: true
                iConomy.accounts.give: true
                iConomy.accounts.take: true
                iConomy.accounts.set: true
                iConomy.accounts.status: true
                iConomy.accounts.status.set: true
                iConomy.accounts.purge: true
                iConomy.accounts.empty: true
                SecretSwitch.create: true
                lockette.admin.create.*: true
                lockette.admin.break: true
                lockette.admin.bypass: true
                lockette.admin.snoop: true
                lockette.admin.reload: true         
            - user
                permissions.build: true
                    coolplugin.item: true
            - default
        build: '&cYou do not have permission to build here.'
    debug: false
    is not config complicated , is just to separating the admin from the users
    sorry my English! :p

Share This Page