[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

    SpaceManiac

    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.

    Features:
    • 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.

    Configuration:
    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:
    Code:
    users:
        ConspiracyWizard:
            permissions:
                permissions.example: true
            groups:
            - admin
    groups:
        default:
            permissions:
                permissions.build: false
        admin:
            permissions:
                permissions.*: true
            inheritance:
            - user
        user:
            permissions:
                permissions.build: true
            worlds:
                creative:
                    coolplugin.item: true
            inheritance:
            - default
    messages:
        build: '&cYou do not have permission to build here.'
    

    Permissions:
    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:
    Code:
    server.basics:
        children:
            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:
    Code:
    server.basics:
        description: Basic permissions for My Cool Server.
        default: true
        children:
            commandbook.motd: true
            commandbook.say: true
            commandbook.say.me: true
            commandbook.time: true
    server.admin:
        description: Admin permissions for My Cool Server.
        default: op
        children:
            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:
    Code:
    da-name-format: '+prefix+name&e'
    date-format: HH:mm:ss
    message-format: '+prefix+name&f: +message'
    mchat:
        prefix:
            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.

    Downloads:
    Current Version:

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

    [​IMG]

    Changelog:

    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

    Deathlysteve-

    i know that! ive typed "*" in mcmyadmin and it writes in the config "superpermsbridge.*"
    the point is that the plugin doesnt even work ive reinstalled like 50 times and shizz... nothing like wtf!!?!
     
  3. Offline

    Ziden

    Very very much, thanx ! :) But where do i get that hashmap from ? Ill try it out ! Thanx,,..
     
  4. Offline

    SpaceManiac

    Make sure it's "superpermbridge" and not "superpermsbridge" that you're prefixing bridged nodes with, this may be the problem...

    Have you given ops the 'permissions.build' node? Do you have SuperpermsBridge installed? Is your default group named 'default'?

    The bridge doesn't do so and likely won't. This is something WorldGuard will have to update to work with (essentially it needs to check if player has worldguard.region.doaction.xyz instead of checking if they're in group xyz).

    For nodes ending in ".*" on plugins that haven't updated yet, add "superpermbridge." to the beginning.

    I've been busy with life and other things so I may not be able to respond to every issue. Permissions 2.7 and 3.x converters will be done as soon as I find time to work on them.
     
    [qwerty] likes this.
  5. Offline

    Trevor_

    Code:
    [LIST=1][*]22:18:07 [SEVERE] Could not pass event PLAYER_QUIT to PermissionsBukkit
    [*]java.lang.IllegalArgumentException: Attachment cannot be null
    [*]        at org.bukkit.permissions.PermissibleBase.removeAttachment(PermissibleBase.java:134)
    [*]        at org.bukkitcontrib.player.ContribCraftPlayer.removeAttachment(ContribCraftPlayer.java:140)
    [*]        at com.platymuus.bukkit.permissions.PermissionsPlugin.unregisterPlayer(PermissionsPlugin.java:137)
    [*]        at com.platymuus.bukkit.permissions.PlayerListener.onPlayerQuit(PlayerListener.java:24)
    [*]        at org.bukkit.plugin.java.JavaPluginLoader$2.execute(JavaPluginLoader.java:251)
    [*]        at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:58)
    [*]        at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:332)
    [*]        at net.minecraft.server.ServerCoKilled
    [/LIST]
    Here you go sir.
     
  6. Just declare it and save it somewhere in your plugin. That's just the way I'm doing it.
     
  7. Offline

    Switch0r

    So all my permissions 3.1.6 plugins will work with this bukkitpermissions?
    I dont want to use a bridge, just one permission is enough.
    I hope its the last time we need to change :p
     
  8. Offline

    staxx6

    @SpaceManiac please look the post #425 #441
    I hate the restart bug :/
    And it look like that problem have more people
     
  9. Offline

    maller

    I have the restart bug to :| I had to move to permissions 3 until it gets fixed, but that doesn't support some of my plugins as they only have permissions for bukkitpermissions.
    So hoping for fix soon :D
     
  10. Offline

    PhonicUK

    @SpaceManiac, It is indeed superpermbridge.* that McMyAdmin is adding, all is well.
     
  11. Offline

    hyperch

    Hmmm, nobody seems to be able to use any commands. My config.yml looks like this:

    Code:
    users:
        USERNAME:
            groups:
            - admin
    groups:
        default:
            permissions:
                //wand: true
                permissions.build: true
                worldedit.*: true
        admin:
            permissions:
                permissions.*: true
            inheritance:
            - mod
        mod:
            permissions:
                //wand: true
                permissions.build: true
                worldedit.*: true
            inheritance:
            - default
    messages:
        build: '&cYou do not have permission to build here.'
    
     
  12. Offline

    Zach667711

    This plugin works for me but I need to know how to have world specific permissions nodes like having factions.* in the Factions world and no where else. Your help is greatly appriciated :)
     
  13. Offline

    BigBrain74

    I keep getting this error:
    18:45:39 [SEVERE] java.lang.ClassCastException: org.bukkitcontrib.ContribPlayerInstance cannot be cast to org.bukkitcontrib.ContribPlayerInstance
    18:45:39 [SEVERE] at org.bukkitcontrib.ContribPlayerManager.flush(ContribPlayerManager.java:38)
    18:45:39 [SEVERE] at net.minecraft.server.ServerConfigurationManager.b(ServerConfigurationManager.java:304)
    18:45:39 [SEVERE] at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:452)
    18:45:39 [SEVERE] at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:361)
    18:45:39 [SEVERE] at net.minecraft.server.ThreadServerApplication.run(SourceFile:422)
    18:45:39 [SEVERE] Unexpected exception
    java.lang.ClassCastException: org.bukkitcontrib.ContribPlayerInstance cannot be cast to org.bukkitcontrib.ContribPlayerInstance
    at org.bukkitcontrib.ContribPlayerManager.flush(ContribPlayerManager.java:38)
    at net.minecraft.server.ServerConfigurationManager.b(ServerConfigurationManager.java:304)
    at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:452)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:361)
    at net.minecraft.server.ThreadServerApplication.run(SourceFile:422)
     
  14. Offline

    lukawise9828

    How do i download this plugin??

    Hey how do i download this plugin

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 17, 2016
  15. Offline

    SpaceManiac

    Make sure you don't have BukkitContrib installed twice.

    For the //wand command, the node is 'worldedit.wand' if I recall correctly. WorldEdit has not yet updated to support Superperms so use 'superpermbridge.worldedit.*'

    Alright, just double-checking.

    There is a download link in the first post.

    Everyone having the PLAYER_QUIT issue - I will get up a temporary fix when I get the chance, but the root cause of the problem may reside in CraftBukkit, so it will need more investigation (it seems to be that PermissionsBukkit is receiving both a kick and a quit event, which it should not be).
     
  16. Offline

    hyperch

    Testing it now. How to know which plugins have been ported?
     
  17. Offline

    Paradox256

    Are any other messages like the build one configurable? It'd be cool if I could make it say other messages when people try to use /god when they can't, etc.
     
  18. Offline

    Lanuk

    Can someone tell me how to make one of my ranks default? I want to make it so that when players log in they will automatically be set to Member.

    I tried putting "server.default: true" in the permissions but it didnt work

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 17, 2016
  19. Offline

    xtyro

    any progress in refreshing permissions after switching a world?
     
  20. Offline

    selonianth

    CButD tells me it has no source for Permsbukkit or superperms, any ideas why?
     
  21. Offline

    Xaiier

    I was messing with the config and somehow I have lost the ability to do /permissions. I have all perms and am OP.
    Help?

    Fixed it, it seems I had two perm bridges installed.
     
  22. Offline

    midget_3111

    I would like to know this aswell :) I've had to close off all the worlds on my server a part from creative :(. I'm sure it will be worth the wait though!
     
  23. Offline

    HunterAP

    He actually fixed this a while ago. I helped him test it on IRC. I'm a bit surprised that those changes haven't made it into a release yet.
     
  24. Offline

    Kararty

    Any errors here? :S
    Code:
    users:
        Kararty:
            permissions:
                permissions.example: true
            groups:
            - admin
    groups:
        &2default:
            permissions:
                permissions.build: false
        &3admin:
            permissions:
    commandbook.give
    bb.admin.watch
    bb.admin.watch
    bb.admin.info
    bb.admin.watch
    bb.admin.info
    bb.admin.info
    bb.admin.info
    bb.admin.rollback
    bb.admin.rollback
    BOSEconomy.common.wallet
    BOSEconomy.common.income
    BOSEconomy.common.mastry
    BOSEconomy.common.pay
    BOSEconomy.common.stats
    BOSEconomy.common.top5
    BOSEconomy.common.bracket.rename
    BOSEconomy.common.bracket.info
    BOSEconomy.common.bracket.listmembers
    BOSEconomy.common.bracket.addmember
    BOSEconomy.common.bracket.removemember
    BOSEconomy.common.bracket.setmultiplier
    BOSEconomy.common.bank.rename
    BOSEconomy.common.bank.list
    BOSEconomy.common.bank.info
    BOSEconomy.common.bank.mastry
    BOSEconomy.common.bank.withdraw
    BOSEconomy.common.bank.deposit
    BOSEconomy.common.bank.addowner
    BOSEconomy.common.bank.addmember
    BOSEconomy.common.bank.removemember
    BOSEconomy.common.bank.income
    BOSEconomy.common.bank.listmembers
    BOSEconomy.common.help
    BOSEconomy.admin.money.info
    BOSEconomy.admin.viewmastry
    BOSEconomy.admin.money.set
    BOSEconomy.admin.money.add
    BOSEconomy.admin.money.sub
    BOSEconomy.admin.money.clear
    BOSEconomy.admin.money.scale
    BOSEconomy.admin.reload
    BOSEconomy.admin.save
    BOSEconomy.admin.bracket.create
    BOSEconomy.admin.bracket.remove
    BOSEconomy.admin.bracket.rename
    BOSEconomy.admin.bracket.list
    BOSEconomy.admin.bracket.info
    BOSEconomy.admin.bracket.set
    BOSEconomy.admin.bracket.setmaster
    BOSEconomy.admin.bracket.removemaster
    BOSEconomy.admin.bracket.listmembers
    BOSEconomy.admin.bracket.addmember
    BOSEconomy.admin.bracket.removemember
    BOSEconomy.admin.bracket.setmultiplier
    BOSEconomy.admin.bank.create
    BOSEconomy.admin.bank.remove
    BOSEconomy.admin.bank.rename
    BOSEconomy.admin.bank.list
    BOSEconomy.admin.bank.info
    BOSEconomy.admin.bank.mastry
    BOSEconomy.admin.bank.listmembers
    BOSEconomy.admin.bank.income
    BOSEconomy.admin.bank.withdraw
    BOSEconomy.admin.bank.deposit
    BOSEconomy.admin.bank.addowner
    BOSEconomy.admin.bank.addmember
    BOSEconomy.admin.bank.removemember
    BOSEconomy.admin.payday.reset
    commandbook.kick
    commandbook.bans.ban
    commandbook.bans.unban
    commandbook.bans.isbanned
    commandbook.clear
    commandbook.clear.other
    commandbook.warp.set
    commandbook.warp.teleport
    commandbook.teleport.other
    commandbook.return
    commandbook.call
    commandbook.teleport
    commandbook.spawn
    commandbook.weather
    commandbook.weather.thunder
    commandbook.spawnmob
    commandbook.spawnmob.many
    commandbook.time
    commandbook.time.lock
    heroicdeath.messages
    herospawn.tp
    herospawn.set
    jail.command.jailcreate
    jail.command.jailcreatecells
    jail.command.jaildelete
    jail.command.jaildeletecells
    jail.command.jail
    jail.command.unjail
    jail.command.jailtransfer
    jail.command.jailtransferall
    jail.command.jailcheck
    jail.command.jailtelein
    jail.command.jailteleout
    jail.command.jaillist
    jail.command.jaillistcells
    jail.command.unjailforce
    jail.command.jailclear
    jail.command.jailclearforce
    jail.command.jailmute
    jail.command.jailstop
    jail.usercmd.jailstatus
    jail.usercmd.jailpay
    mywarp.warp.basic.createpublic
    mywarp.warp.basic.welcome
    mywarp.warp.basic.warp
    mywarp.warp.basic.delete
    mywarp.warp.sign.warp
    mywarp.warp.sign.create
    mywarp.admin
    over9000homes.alwaysAllowed
    worldedit.brush.sphere
    worldedit.brush.cylinder
    worldedit.brush.clipboard
    worldedit.brush.smooth
    worldedit.brush.ex
    worldedit.chunkinfo
    worldedit.listchunks
    worldedit.delchunks
    worldedit.clipboard.copy
    worldedit.clipboard.cut
    worldedit.clipboard.paste
    worldedit.clipboard.rotate
    worldedit.clipboard.flip
    worldedit.clipboard.load
    worldedit.clipboard.save
    worldedit.clipboard.clear
    worldedit.generation.cylinder
    worldedit.generation.sphere
    worldedit.generation.forest
    worldedit.generation.pumpkins
    worldedit.history.undo
    worldedit.history.redo
    worldedit.history.clear
    worldedit.navigation.unstuck
    worldedit.navigation.ascend
    worldedit.navigation.descend
    worldedit.navigation.ceiling
    worldedit.navigation.thru
    worldedit.navigation.jumpto
    worldedit.navigation.up
    worldedit.region.set
    worldedit.region.replace
    worldedit.region.overlay
    worldedit.region.faces
    worldedit.region.smooth
    worldedit.region.move
    worldedit.region.stack
    worldedit.regen
    worldedit.scripting.execute
    worldedit.selection.pos
    worldedit.selection.hpos
    worldedit.selection.chunk
    worldedit.wand
    worldedit.wand.toggle
    worldedit.selection.expand
    worldedit.selection.contract
    worldedit.selection.shift
    worldedit.selection.outset
    worldedit.selection.inset
    worldedit.selection.size
    worldedit.analysis.count
    worldedit.analysis.distr
    worldedit.snapshots.list
    worldedit.snapshots.restore
    worldedit.snapshots.restore
    worldedit.superpickaxe
    worldedit.superpickaxe.area
    worldedit.superpickaxe.recursive
    worldedit.tool.info
    worldedit.tool.tree
    worldedit.tool.replacer
    worldedit.tool.data-cycler
    worldedit.superpickaxe
    worldedit.brush.options.mask
    worldedit.brush.options.material
    worldedit.brush.options.size
    worldedit.fill
    worldedit.fill.recursive
    worldedit.drain
    worldedit.fixlava
    worldedit.fixwater
    worldedit.removeabove
    worldedit.removebelow
    worldedit.removenear
    worldedit.replacenear
    worldedit.snow
    worldedit.thaw
    worldedit.extinguish
    worldedit.butcher
    worldedit.remove
    worldedit.reload
    over9000homes.canUse
    styxspace.teleport.enter
    styxspace.teleport.exit
    worldguard.god
    worldguard.god.other
    worldguard.ungod
    worldguard.ungod.other
    worldguard.heal
    worldguard.heal.other
    worldguard.slay
    worldguard.slay.other
    worldguard.locate
    worldguard.stack
    worldguard.fire-toggle.*
    worldguard.fire-toggle.*
    worldguard.halt-activity.*
    worldguard.halt-activity.*
    worldguard.region.define.*
    worldguard.region.redefine.own.*
    worldguard.region.redefine.member.*
    worldguard.region.redefine.*
    worldguard.region.claim.*
    worldguard.region.select.own.
    worldguard.region.select.member.*
    worldguard.region.select.member.
    worldguard.region.select.*
    worldguard.region.select.
    worldguard.region.info.own.*
    worldguard.region.info.member.*
    worldguard.region.info.*
    worldguard.region.flag.own.*
    worldguard.region.flag.own.
    worldguard.region.flag.member.*
    worldguard.region.flag.member.
    worldguard.region.flag.*
    worldguard.region.flag.
    worldguard.region.flag.flags.<flag>.*
    worldguard.region.flag.flags.*
    worldguard.region.setparent.own.*
    worldguard.region.setparent.own.<region>
    worldguard.region.setparent.member.*
    worldguard.region.setparent.member.<region>
    worldguard.region.setparent.*
    worldguard.region.setparent.<region>
    worldguard.region.remove.own.*
    worldguard.region.remove.own.<region>
    worldguard.region.remove.member.*
    worldguard.region.remove.member.<region>
    worldguard.region.remove.*
    worldguard.region.remove.<region>
                permissions.*: true
            inheritance:
            - Trusted
        &4trusted:
            permissions:
    BOSEconomy.common.wallet
    BOSEconomy.common.income
    BOSEconomy.common.mastry
    BOSEconomy.common.pay
    BOSEconomy.common.stats
    BOSEconomy.common.top5
    BOSEconomy.common.bracket.rename
    BOSEconomy.common.bracket.info
    BOSEconomy.common.bracket.listmembers
    BOSEconomy.common.bracket.addmember
    BOSEconomy.common.bracket.removemember
    BOSEconomy.common.bracket.setmultiplier
    BOSEconomy.common.bank.rename
    BOSEconomy.common.bank.list
    BOSEconomy.common.bank.info
    BOSEconomy.common.bank.mastry
    BOSEconomy.common.bank.withdraw
    BOSEconomy.common.bank.deposit
    BOSEconomy.common.bank.addowner
    BOSEconomy.common.bank.addmember
    BOSEconomy.common.bank.removemember
    BOSEconomy.common.bank.income
    BOSEconomy.common.bank.listmembers
    BOSEconomy.common.help
    commandbook.who
    commandbook.motd
    commandbook.intro
    commandbook.midi
    commandbook.rules
    commandbook.kit.list
    commandbook.kit.kits.starter
    commandbook.time.check
    commandbook.spawn
    commandbook.say.me
    commandbook.msg
    commandbook.clear
    commandbook.spawn
    heroicdeath.messages
    herospawn.tp
    mywarp.warp.basic.warp
    mywarp.warp.basic.list
    mywarp.warp.sign.warp
    over9000homes.canUse
    styxspace.teleport.enter
    styxspace.teleport.exit
                permissions.build: true
            worlds:
                creative:
                    coolplugin.item: true
            inheritance:
            - default
    messages:
        build: '&cYou do not have permission to build here.'
    
     
  25. Offline

    midget_3111

    Ohh! is there anyway we can get nightly builds from a repo or something?
     
  26. Offline

    HuntMASTER15

    I can't do the /permissions command no matter what I do. Here is my config. Also no other files show up other than config. It's like the plugin isn't even started but it shows up in console.
    users:
    HuntMASTER15:
    permissions:
    groups:
    - KingVampire
    groups:
    Human:
    permissions:
    permissions.build: true
    essentials.heal: true
    essentials.afk: true
    essentials.helpop: true
    essentials.motd: true
    essentials.msg: true
    essentials.help: true
    Royalty:
    permissions:
    essentials.ban: true
    essentials.banip: true
    essentials.kick: true
    essentials.heal.cooldown.bypass: true
    essentials.deljail: true
    essentials.jails: true
    essentials.setjail: true
    essentials.togglejail: true
    essentials.mute: true
    permissions.build: true
    essentials.heal: true
    essentials.afk: true
    essentials.helpop: true
    essentials.motd: true
    essentials.msg: true
    essentials.help: true
    permissions.*: true
    inheritance:
    - Human
    Vampire:
    permissions:
    permissions.build: true
    inheritance:
    - Human
    KingVampire:
    permissions:
    vampire.command.list: true
    vampire.command.infect: true
    vampire.command.turn: true
    vampire.command.cure: true
    vampire.command.feed: true
    vampire.command.time.*: true
    vampire.command.load: true
    vampire.command.save: true
    permissions.build: true
    inheritance:
    -Royalty
    Pirate:
    permissions:
    armageddon.display: true
    armageddon.configure: true
    armageddon.toggle: true
    armageddon.grenades.snare: true
    armageddon.grenades.stun: true
    armageddon.grenades.explosive: true
    armageddon.grenades.molotov: true
    armageddon.grenades.spider_web: true
    permissions.build: true
    AlphaPirate:
    permissions:
    armageddon.display: true
    armageddon.configure: true
    armageddon.toggle: true
    armageddon.grenades.*: true
    armageddon.guns.*: true
    inheritance:
    -Royalty
    Werewolf:
    permissions:
    mobdisguise.wolf: true
    essentials.afk: true
    essentials.helpop: true
    essentials.motd: true
    essentials.msg: true
    essentials.help: true
    inheritance:
    -Vampire
    AlphaWerewolf:
    permissions:
    mobdisguise.*: true
    inheritance:
    -Royalty
    messages:
    build: '&cYou do not have permission to build here.'
    This needs easier to read instructions for people like me otherwise people will just go to the other permissions plugins since they have so many help videos.
    Edit: For some reason it all went back to normal spacing but I do have the correct spacing in the config.
     
  27. Offline

    Kiwii

    New players are automatically put into a group named 'default' no matter if it actually exists. There is no way to change the default group's name but it is actually not used anywhere anyway.
    Just rename your group 'Member' to 'default' and everything should be fine.

    Btw, this should answer all those questions:
    comment taken from the default config file (open)
    # 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.
    (Warning: Do not read it, if you intend to troll!)
     
  28. Offline

    Lanuk

    Ahh thanks, will do!
     
  29. Offline

    blahblahjam

    nevermind, i fixed it. i was op. xD
     
  30. Offline

    Incendia

    Since this doesn't emulate groups through the bridge, does anyone know something that does?
     

Share This Page