[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

    ForsakenRealmz

    Hi, my "Member" group for permissions isn't allowing anyone to do anything. It's like all of the permissions I have set for them stopped working. This is what the group looks like.

    groups:
    Member:
    default: true
    info:
    prefix: Member
    suffix: ''
    build: true
    inheritance:
    permissions:
    creativecolours.sign: true
    essentials.afk: true
    essentials.back: true
    essentials.back.ondeath: true
    essentials.compass: true
    essentials.depth: true
    essentials.help: true
    essentials.home: true
    essentials.list: true
    essentials.me: true
    essentials.motd: true
    essentials.msg: true
    essentials.rules: true
    essentials.sethome: true
    essentials.spawn: true
    essentials.warp: true
    essentials.warp.list: true
    iConomy.help: true
    iConomy.holdings: true
    iConomy.payment: true
    iConomy.user: true
    jail.pay: true
    lwc.create: true
    lwc.create.?: true
    lwc.flag.*: true
    lwc.info: true
    lwc.modify: true
    lwc.protect: true
    lwc.remove: true
    lwc.unlock: true
    towny.chat.nation: true
    towny.chat.town: true
    towny.nation.*: true
    towny.nation.delete: true
    towny.nation.grant-titles: true
    towny.nation.new: true
    towny.nation.rename: true
    towny.town.*: true
    towny.town.claim: true
    towny.town.delete: true
    towny.town.new: true
    towny.town.plot: true
    towny.town.rename: true
    towny.town.resident: true
    towny.town.spawn.*: true
    towny.town.spawn.ally: true
    towny.town.spawn.nation: true
    towny.town.spawn.town: true
    towny.town.toggle.*: true
    towny.town.toggle.explosions: true
    towny.town.toggle.fire: true
    towny.town.toggle.mobs: true
    towny.town.toggle.public: true
    towny.town.toggle.pvp: true
    towny.wild.*: true
    towny.wild.build: true
    towny.wild.destroy: true
    towny.wild.item_use: true
    towny.wild.switch: true
     
  3. Offline

    NinjaZidane

    To all the comments above about updating Permissions Bukkit...

    You guys do realize that it needs NO updates...right? You are missing the point of PermBukkit: it isn't supposed to be a "lets pack 1000 features into it" plugin...it is supposed to be simplistic, light, and self maintained.

    With that ideology in mind, PermBukkit accomplished this perfectly. So long as the SuperPerm API never changes, PermBukkit will ALWAYS work. Any issues here mostly stem from invalid permission setups.

    If you are looking for fancy multi-world setups, mysql whatever support, more in-game control, etc etc then go with either bPermissions or PermissionsEX and stop complaining on this thread.
     
    JohnEBH likes this.
  4. Offline

    xShiFTyy

    Can u please make this wiht prefixes and suffixes ive tryed like 10+ plugins to get them and there all annoying to use or just dont support permissions bukkit
     
  5. Offline

    Snaipe

    Adding prefixes/suffixes is not the business of a supererm manager, you should find a prefix/suffix adder with permissions nodes.
     
  6. Offline

    Sneaky Potatoes

    Someone please look at my config. Should work... right?

    HTML:
    users:
        Raynbows:
            permissions:
                permissions.*: true
                falsebook.blocks.*: true
                falsebook.blocks.gate: true
            groups:
            - Admin
    groups:
        Default:
            permissions:
                permissions.build: false
        Trusted:
            permissions:
                permissions.build: true
        Moderator:
            permissions:
                permissions.build: true
        Admin:
            permissions:
                permissions.*: true
                craftbook.mech.gate: true
                craftbook.mech.ammeter.use: true
                craftbook.mech.bridge: true
                craftbook.mech.bookshelf.use: true
                craftbook.mech.cauldron: true
                craftbook.mech.elevator: true
                craftbook.mech.elevator.use: true
                craftbook.mech.gate: true
                craftbook.mech.light-switch: true
     
  7. Offline

    Luwiego

    I have a problem. Whenever new players join the server they are marked as [default] because thats the default group. How do i change the default group to something like Builder ?
     
  8. Offline

    Mavericko

    hello,i cant understand how to use superperms.
    I have permissionsBukkit,but some plugins are not supported.
    So I installed superpermsbridge. what should I do next?
     
  9. Offline

    Greylocke

    just add superpermbridge. (note that there is no S in the middle of the permissions node) to the beginning of the plugin's permissions nodes.

    As an example, this permissions node is invalid because PermissionsBukkit does not evaluate the .*:
    lockette.create.*: true

    But it could be used with SuperPermsBridge like this:
    superpermbridge.lockette.create.*: true
     
  10. Offline

    Mavericko

    Something not working for me.I want to use SPITEMS_v1.3.3 for my server.But its only supporting permissionsEX.
    I added this line in my permissionsBukkit config.yml for default users:
    superpermbridge.spitems.member: true
    But default users still cant open the shop. I know im doing something wrog,but dont know what :D
     
  11. Offline

    Greylocke

    According to this post SuperPermsBukkit shouldn't be necessary. And according to this post it should work with SuperPermsBridge, even if it isn't necessary.

    Are you doing a /permissions reload after each change to the permissions file? I'd advise posting this on the SpItems forums for more help. This really doesn't look like a PermissionsBukkit issue.
     
    Mavericko likes this.
  12. Offline

    Mavericko

    Thank you! Its working :)
     
    Greylocke likes this.
  13. Offline

    Julianoz1224

    I have someone on my server that keeps using the /stop command, is there a node for the default server commands? if so, it would be great help if someone could tell me :)
     
  14. Offline

    DarkZeR0

  15. Offline

    Pr4w

    I'm guessing the problem's from you, not the plugin. Citizens works fine on PermissionsBukkit here :-°
     
  16. Offline

    DarkZeR0

    Yeah i need help really bad.
    All i want is to my players to use healer blacksmith trader
     
  17. Offline

    NinjaZidane

    bukkit.command.stop is the node

    bukkit.command.stop: false

    At least, I think so. Try that and let me know.
     
  18. Offline

    KarlJostein

    Hey, im trying to change the group's names, and after i've changed them, saved the settings and reloaded once, it doesnt work anymore? And I cant add more groups either. Please help me with this problem, I dont know what to do.
     
  19. Offline

    Nielscorn

    could someone PLEASE help me :(!!

    i have this in: plugins/permissionsbukkit/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.
    
    users:
        Nielscorn:
            permissions:
                permissions.example: true
            groups:
            - God
        Mini_Man117:
            permissions:
                permissions.example: true
            groups:
            - Admin
        Shorty26:
            permissions:
                permissions.example: true
            groups:
            - Member
        bradonator:
            permissions:
                permissions.example: true
            groups:
            - Member
        godgodgodgo:
            permissions:
                permissions.example: true
            groups:
            - Member
        coolnija:
            permissions:
                permissions.example: true
            groups:
            - Member
        retep12345:
            permissions:
                permissions.example: true
            groups:
            - Member
        robater:
            permissions:
                permissions.example: true
            groups:
            - Member
        militiasarm:
            permissions:
                permissions.example: true
            groups:
            - Member
        zedfeather:
            permissions:
                permissions.example: true
            groups:
            - Member
        seany2987:
            permissions:
                permissions.example: true
            groups:
            - Member
        fatfartmonkey:
            permissions:
                permissions.example: true
            groups:
            - Member
        trippski:
            permissions:
                permissions.example: true
            groups:
            - Member
        thearturian:
            permissions:
                permissions.example: true
            groups:
            - Member
        innovasion:
            permissions:
                permissions.example: true
            groups:
            - Member
        epiclimited:
            permissions:
                permissions.example: true
            groups:
            - Member
        stuartWOAH:
            permissions:
                permissions.example: true
            groups:
            - Member
        paigebrumby:
            permissions:
                permissions.example: true
            groups:
            - Member
        dragku:
            permissions:
                permissions.example: true
            groups:
            - Member
        redracer22:
            permissions:
                permissions.example: true
            groups:
            - Member
        jaredvvj:
            permissions:
                permissions.example: true
            groups:
            - Member
        densed:
            permissions:
                permissions.example: true
            groups:
            - Member
        skully256:
            permissions:
                permissions.example: true
            groups:
            - Member
        mogadonskoda:
            permissions:
                permissions.example: true
            groups:
            - Member
        m1f:
            permissions:
                permissions.example: true
            groups:
            - Member
        datastalker:
            permissions:
                permissions.example: true
            groups:
            - Member
        ben_christian24:
            permissions:
                permissions.example: true
            groups:
            - Member
        wolfgang3d3:
            permissions:
                permissions.example: true
            groups:
            - Member
        sirironsoul:
            permissions:
                permissions.example: true
            groups:
            - Member
        chibenlol:
            permissions:
                permissions.example: true
            groups:
            - Member
        nocake007:
            permissions:
                permissions.example: true
            groups:
            - Member
        XDragonhunterX:
            permissions:
                permissions.example: true
            groups:
            - Member
        hahaa:
            permissions:
                permissions.example: true
            groups:
            - Member
        pivu0:
            permissions:
                permissions.example: true
            groups:
            - Admin
        bri64:
            permissions:
                permissions.example: true
            groups:
            - Member
        midoforces:
            permissions:
                permissions.example: true
            groups:
            - Member
        dementedbunnie:
            permissions:
                permissions.example: true
            groups:
            - Member
        Miasan:
            permissions:
                permissions.example: true
            groups:
            - Admin
        masonator117:
            permissions:
                permissions.example: true
            groups:
            - Admin
        chanman55:
            permissions:
                permissions.example: true
            groups:
            - Member
        adrisj7:
            permissions:
                permissions.example: true
            groups:
            - Member
        liambannister:
            permissions:
                permissions.example: true
            groups:
            - Member
        bazman123:
            permissions:
                permissions.example: true
            groups:
            - Member
        iryank:
            permissions:
                permissions.example: true
            groups:
            - Member
        coltonandjared:
            permissions:
                permissions.example: true
            groups:
            - Member
        groverfield:
            permissions:
                permissions.example: true
            groups:
            - Member
        foxracer30:
            permissions:
                permissions.example: true
            groups:
            - Member
        fap_monster:
            permissions:
                permissions.example: true
            groups:
            - Member
        adminisbest:
            permissions:
                permissions.example: true
            groups:
            - Member
        Takaramono:
            permissions:
                permissions.example: true
            groups:
            - Admin
        annihilaterq:
            permissions:
                permissions.example: true
            groups:
            - Member
        blitz1977:
            permissions:
                permissions.example: true
            groups:
            - Member
        BombingPro:
            permissions:
                permissions.example: true
            groups:
            - Admin
        gamerathome:
            permissions:
                permissions.example: true
            groups:
            - Member
        verybestnoob:
            permissions:
                permissions.example: true
            groups:
            - Member
        wwwslatercom:
            permissions:
                permissions.example: true
            groups:
            - Member
        SirleeuwenKlauw:
            permissions:
                permissions.example: true
            groups:
            - Admin
        caelamus:
            permissions:
                permissions.example: true
            groups:
            - Member
    groups:
        Guest:
            permissions:
                permissions.build: true
                permissions.help: true
                permissions.group.help: true
                permissions.group.list: true
                permissions.player.help: true
                lockette.user.create.*: true
                worldedit.navigation.unstuck: true
                worldedit.extinguish: true
                commandbook.who: true
                commandbook.motd: true
                commandbook.rules: true
                commandbook.time.check: true
                commandbook.say.me: true
                commandbook.msg: true
                commandbook.away: true
                bukkit.command.kill: true
                bukkit.command.me: true
                bukkit.command.help: true
                bukkit.command.list: true
        Member:
            permissions:
                permissions.build: true
                worldguard.locate: true
                worldedit.chunkinfo: true
                worldedit.listchunks: true
                commandbook.home.teleport: true
                commandbook.home.set: true
                commandbook.whereami: true
                commandbook.whereami.compass: true
                commandbook.bans.isbanned: true
            worlds:
                creative:
                    coolplugin.item: true
            inheritance:
            - Guest
    
        Admin:
            permissions:
                permissions.*: true
                lockette.admin.create.*: true
                lockette.admin.bypass: true
                lockette.admin.snoop: true
                lockette.admin.reload: true
                worldguard.fire-toggle.*: true
                worldguard.halt-activity.*: true
                worldguard.reload: true
                worldguard.report: true
                worldguard.region.bypass.*: true
                worldedit.reload: true
                commandbook.broadcast: true
                commandbook.mute: true
                commandbook.clear.*: true
                commandbook.slap.other: true
                commandbook.slap: true
                commandbook.reload: true
                commandbook.kick: true
                commandbook.bans.ban: true
                commandbook.bans.load: true
                commandbook.bans.save: true
                bukkit.command.kick: true
                bukkit.command.ban.player: true
                bukkit.command.unban.player: true
                bukkit.command.ban.ip: true
                bukkit.command.unban.ip: true
                bukkit.command.teleport: true
                bukkit.command.save.perform: true
                bukkit.command.say: true
                bukkit.command.whitelist.enable: true
                bukkit.command.whitelist.disable: true
                bukkit.command.whitelist.add: true
                bukkit.command.whitelist.remove: true
                bukkit.command.whitelist.reload: true
                bukkit.command.gamemode: true
                bukkit.command.ban: true
                bukkit.command.unban: true
            inheritance:
            - Member
    
        God:
            permissions:
                permissions.build: true
                lockette.admin.break: true
                worldguard.*: true
                worldedit.*: true
                commandbook.*: true
                bukkit.command.*: true
            worlds:
                creative:
                    coolplugin.item: true
            inheritance:
            - Admin
    messages:
        build: '&cYou do not have permission to build here.'
    
    The people can all build(i changed that before i wrote all the nodes) but nobody is in Member group or even Admin group, nobody can even use guest commands :/
     
  20. Offline

    rodier

    for everyone who are new to permissionbukkit and try to get mchat working - they must changed many thing since PB, plus seems mchat isnt maintained very well.. so my best tip is, use EssentialsChat. in Essentials config you can easily set suffixes/prefixes and chat colors for all your PB groups. it is really easy :) its in config under Chat section.
     
  21. Offline

    groveham

    How hard is it to switch form permissions x3 (now inactive) to this permissions plugin?
     
  22. Offline

    wowees8

    can you add new ranks? because i want to add a special rank.
     
  23. Offline

    lolydodo123

    Is it possible to switch from PEX to this permissions?
    Pex: Permissions EX
    Thanks.
    :p
     
  24. Offline

    ForsakenRealmz

    Hi, I have Towny, mChat, and this permissions build. I was wondering why or how I can make it so when people get on my server it automatically says "Member" or "Default" as a prefix. I have it set up so that when I personally add them to the group it says that. But I need to automatic! I hope someone can help

    Thanks,
     
  25. Offline

    OZ4RK

    The group that new players are automatically put in MUST be called 'default'. The prefix you give that group doesn't matter, (mchat, ichat). Reply if you need clarification.

    Unfortunetely, you just kinda have to do it. :/ Might be some converters out there, but there's nothing better that a clean, fresh database.

    Try renaming the default group which you currently have as 'Guest' to 'default'.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Jul 14, 2016
  26. Offline

    infinikiller64

    i need help where do i put the permissions with the user and groups??? there is no main config
    and when i use:
    permissions player setperm Infinikiller64 permissions.* true
    it says i dont exist and i dont know the proper syntax for the world because you didnt make scense
     
  27. Offline

    BigCoots

    How do I make my users able to warp? Ever since I installed this plugin it won't let them.

    Can anyone help me out?
     
  28. Offline

    ForsakenRealmz

    For the default class I have it set to true. I didn't have mChat before some people joined. So do you think I'll have to personally add people to the group if they are old players on my server and new players will automatically be added to the default group?

    Also if anyone has some good permission nodes for Moderators (Not Admins) so that then I can finally take away my Mod's OP status so then they can't do everything that would be great!
     
  29. Offline

    saul100

    Very easy. Try the Permissions Converter.
    What warp plugin?

    You need to look up the plugins warp permission nodes and add it under a specific group's permissions.

    E.G

    Commandbook warps
    Code:
    commandbook.warp.teleport
    xWarp warps

    Code:
    warp.to.*
     
  30. Offline

    OZ4RK

    OK, so IfI underdtand you correctly, your default group is functioning properly, if you're transfering databases, yes you will have to manually add your old players to the config. I suggest a copy and paste setup, just replacing names.
    Permissions nodes depend on what plugins you have, so I can't help there

    There should be a main config file if you properly setup the plugin.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Jul 14, 2016
  31. Offline

    ForsakenRealmz

    That's all the help I need thanks!
     

Share This Page