[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

    Celtic Minstrel

    The default group in PermissionsBukkit is the one called default.
     
  3. Offline

    Toobian

    Since 2 hours. I try to configure PermissionsBukkit. But permission "permissions.*" don't work. I juste change name's user in generate file.
    Please help.
     
  4. Offline

    Snowy007

    Ah i see what you mean. And i think i can get that working.
    I can assign world specific permissions for each group right?
    since i have 2 builder groups in creative, which are going to become just one group in skylands i could do something like this right?:
    Code:
        Builders:
            permissions:
                permissions.build: true
            worlds:
                creative:
                    permission.1: true
                    permission.2: true
                    permission.3: true
                skylands:
                    the.skylands.permissions: true
            inheritance:
            - Guest
        Elite Builders:
            permissions:
            worlds:
                creative:
                    permission.4: true
                    permission.5: true
            inheritance:
            - Builders
    with this in the creative world elite builders will have builder permissions + 2 extra permissions.
    and the same permissons in skylands.
    and then i just need to make sure to give both groups the same prefix when they are in skylands?
    any good plugin i can use for prefixes? I use ichat at the moment but it hasn't updated for permissionsbukkit yet...

    tell me if i am completely wrong. :p
     
  5. Offline

    bob3695

    I dont know if I am missing something but is there a programming API? I am looking to set a persons group from my plugin.
     
  6. Offline

    vildaberper

    Oh, sorry.
    Anyways, have any idea why the player loose his permissions?
     
  7. Offline

    mrgreaper

    @SpaceManiac any chance of some support?!? im sorry but i have been asking for help for a couple of days now and no reply

    cb 1000
    permissions worked 100% perfect

    cb1060
    suddenly the console and admins cant access any permission command
    /permissions anything comes up with you do not have permission yatta yatta

    admins have ofcourse permissions.*: true

    this is getting annoying please help
     
  8. Offline

    Celtic Minstrel

    My recommendation would be bInfo, but there are a few others floating around like mChat and SimplePrefix.

    No, that's certainly the sort of thing I was thinking of.

    There isn't an API. Chances are that if your plugin needs to put players in groups, it should be a permissions manager itself. Out of curiosity, what is your plugin?
     
  9. Will you update this for CB1060?
     
  10. Offline

    bob3695

    Well I was going for something a lot more simple then that. I would give permissions for certain people to promote up to certain groups. I don't want to write a whole permissions manager just to implement this simple feature. This feature is needed on my server as I need people that can set someone to one group, but not another. I looked at the permissionsbukkit source and I think it can be easily done if some of the functions in the plugin were given an API (like the ability to set a group). It already has the ability for me to check their group but cant change anything from it. I guess I could make a "modified" version of PermissionsBukkit as I have no interest in re-inventing the wheel and PermissionsBukkit works out very well for me.

    I am running on 1060 with no issues right now!
     
  11. Offline

    o0AzzA0o

    i think on version 1060 you get plugin fails to pass quit event to permissionsbukkit but other then that it works
     
  12. Offline

    Celtic Minstrel

    Correct me if I'm wrong, but are you referring to /promote and /demote commands? If so, that's something that you would probably want to modify PermissionsBukkit for; if you do so, SpaceManiac may even accept your changes into the main source. :)

    EDIT: Wait no, you're talking about what amounts to "grant" permissions, aren't you; the permission to grant something to another user, in this case group membership. Still, the rest of what I said still applies.
     
  13. Offline

    bob3695

    it would be like a promote/demote command...the twist is this (I already have a basic plugin written up to do this)

    I have the following groups:

    default (no tag)
    V
    TG
    SM
    SS
    BTN
    DIV
    THIEF

    Now, what I want to be able to do is say this:

    SS can promote members that are in default to the V group...but thats it.
    BTN can promote members of default to V, TG, SM, SS, or THIEF
    DIV can promote members from anywhere to anywhere.

    This can be accomplished via promote/demote so long as permissions designed correctly so I can say something like the following:

    SS:
    Permissions:
    permissions.canpromotefrom.default: true
    permissions.canpromoteto.V: true

    and so on. So ONLY if the member is in default can the people in SS place them in V.

    Yes, it is a little bit complicated but they are my requirements and as this is a bit more complicated then most people will want/need I just took permissionbukkit and opened up 2 functions that I need access to from a separate plugin and wrote the plugin specifically for my server.
     
  14. Offline

    Musame

    This is after the H-mod Group system The best permissions addon i ever used.. no complications with other addons. :D
    ok i have sit 30 mins to configurate becouse im an newbie with permissions bud with notepad ++ and onlyne YAML parser i create awesome groups. Thats so cool dude i can give out commands from addons to groups in an easy way. like: Dont use regions bud god is allowed to use :D this is hmod style i love it :D its so awesome work i have to thank all the guys how work on it! Nice!
    ps: sry my bad english im german ^^
    Peace and have fun with this addon :D
     
  15. Offline

    chelben9

    does this work for 1060

    idk if its just me but i wont work it shows up from the start that supermbridge works but the permissionsbukkit doesnt work

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

    Aesran

    Hi,

    i have a little problem with your plugins, it's work perfecly but group are don't recognized by worldguard region.

    I don't really understand why, because if i just set the name of player, it's work, but group don't work. So with Permissions 3.x no problem ..

    And here or in worldguard plugin i don't see anyone have problem ...

    Can you help me ?

    Version of permissions : 1.1
    Version of worldguard: 5.2
    Craftbukkit : 1000

    PermissionsBukkit - config

    Code:
    users:
        phosphor11:
            groups:
            - Lucenna
        tyrron:
            groups:
            - test
        frostw:
            groups:
            - lucenna
    groups:
        default:
            permissions:
                essentials.help: true
                essentials.helpop: true
                essentials.me: true
                essentials.mail.*: true
                essentials.nick: true
                essentials.pay: true
                essentials.balance: true
                essentials.list: true
                essentials.motd: true
                essentials.rules: true
                essentials.signs.trade.use: true
                essentials.signs.buy.use: true
                essentials.sgns.sell.use: true
                chaircraft.sit: true
                movecraft.boat.*: true
                movecraft.boat.sail: true
                movecraft.ship.*: true
                movecraft.ship.sail: true
                lc.level.*: true
                lwc.protect: true
                falsebook.blocks.*: true
                falsebook.blocks.lift: false
                permissions.build: true
        olteral:
            permissions:
                essential.help: true
                permissions.build: true
            inheritance:
            - default
        svard:
            permissions:
                essential.help: true
                permissions.build: true
            inheritance:
            - default
        lucenna:
            permissions:
                essential.help: true
                permissions.build: true
            inheritance:
            - default
        avip:
            permissions:
                essentials.signs.trade.*: true
                essentials.home: true
                essentials.sethome: true
                essentials.spawn: true
                essentials.back: true
                essentials.back.ondeath: true
                permissions.build: true
            inheritance:
            - default
        Moderator:
            permissions:
                essentials.kill: false
                essentials.egod: false
                permissions.build: true
            inheritance:
            - builder
        Admin:
            permissions:
                permissions.build: true
            inheritance:
            - semiadmin
        semiadmin:
            permissions:
        test:
            permissions:
            inheritance:
    messages:
        build: '&cYou do not have permission to build here.'
    
     
  17. Offline

    mrvertigo27

    ok, i have a newbie question
    when someone joins my server
    before I edit the text file
    they get the default rank (with all permissions and rights there of) right?
    If this is the case is there a way with in game commands to add them to the text file without editing the text file by hand? or automatically enter them in the config file automatically?
     
  18. Offline

    Celtic Minstrel

    @Aesran – I think WorldGuard 5.2 doesn't support superperms. Update WorldGuard to the latest dev version, then give each group the permission 'group.groupname' where groupname is the actual name of the group.
     
  19. Can anyone help me? Please log into my server if you can I will tell you the IP.. I Put in Permissions and I added myself to the admin group but for some reason I cannot build please help!
     
  20. Offline

    Mrchasez

    This is my config
    Why can't my Members use any permissions?
    They can just build, Thats it.
    how do i fix it so the permissions i have listed will work
    Edit: No ranks can do anything but build




    Code:
    #
    users:
      hergergerk:
        groups:
          - Member
    (Not going to list 3000 members, But they are set up like the one above)
    groups:
      VIP:
        permissions:
          'nocheat.*': true
          nocheat.fly: true
          permissions.build: true
        inheritance:
          - default
          - member
      Owner:
        permissions:
          permissions.build: true
          permissions.*
          permissions.group.*
          permissions.player.*
    
        inheritance:
          - admin
          - moderator
          - paladin
          - builder
          - member
          - default
      Member:
        permissions:
          essentials.: true
          essentials.balance: true
          essentials.deny: true
          essentials.help: true
          essentials.home: true
          essentials.msg: true
          essentials.pay: true
          essentials.sethome: true
          essentials.tpaccept: true
          iConomyChestShop.shop.buy: true
          iConomyChestShop.shop.create: true
          iConomyChestShop.shop.sell: true
          lwc.protect: true
          mcmmo.ability.axes: true
          mcmmo.ability.excavation: true
          mcmmo.ability.herbalism: true
          mcmmo.ability.mining: true
          mcmmo.ability.swords: true
          mcmmo.ability.unarmed: true
          mcmmo.ability.woodcutting: true
          mcmmo.skills.acrobatics: true
          mcmmo.skills.archery: true
          mcmmo.skills.axes: true
          mcmmo.skills.excavation: true
          mcmmo.skills.herbalism: true
          mcmmo.skills.mining: true
          mcmmo.skills.repair: true
          mcmmo.skills.swords: true
          mcmmo.skills.taming: true
          mcmmo.skills.unarmed: true
          mcmmo.skills.woodcutting: true
          towny.publicspawntp: true
          towny.town.claim: true
          towny.town.new: true
          towny.town.resident: true
          'towny.wild.*': true
          'towny.town.*': true
          towny.spawntp: true
          towny.nation.new: true
          permissions.build: true
        inheritance:
          - default
      Paladin:
        permissions:
          essentials.fixwater: true
          permissions.build: true
        inheritance:
          - default
          - member
          - vip
          - builder
          - knight
          - hero
      Supreme:
        permissions:
          worldedit.superpickaxe: true
          worldedit.superpick: true
          permissions.build: true
        inheritance:
          - default
          - member
          - vip
          - builder
          - knight
          - hero
      Admin:
        permissions:
          essentials.help: true
          essentials.helpop.receive: true
          essentials.unban: true
          'nocheat.*': true
          towny.admin: true
          worldedit.butcher: true
          worldedit.superpick: true
          worldedit.superpickaxe: true
          permissions.build: true
        inheritance:
          - moderator
          - default
          - member
          - vip
          - builder
          - knight
      Citizen:
        permissions:
          essentials.: true
          essentials.balance: true
          essentials.deny: true
          essentials.help: true
          essentials.home: true
          essentials.msg: true
          essentials.pay: true
          essentials.sethome: true
          essentials.tpaccept: true
          iConomyChestShop.shop.buy: true
          iConomyChestShop.shop.create: true
          iConomyChestShop.shop.sell: true
          lwc.protect: true
          mcmmo.ability.axes: true
          mcmmo.ability.excavation: true
          mcmmo.ability.herbalism: true
          mcmmo.ability.mining: true
          mcmmo.ability.swords: true
          mcmmo.ability.unarmed: true
          mcmmo.ability.woodcutting: true
          mcmmo.skills.acrobatics: true
          mcmmo.skills.archery: true
          mcmmo.skills.axes: true
          mcmmo.skills.excavation: true
          mcmmo.skills.herbalism: true
          mcmmo.skills.mining: true
          mcmmo.skills.repair: true
          mcmmo.skills.swords: true
          mcmmo.skills.taming: true
          mcmmo.skills.unarmed: true
          mcmmo.skills.woodcutting: true
          towny.town.claim: true
          towny.town.new: true
          towny.town.resident: true
          permissions.build: true
        inheritance:
          - default
      default:
        permissions:
          essentials.help: true
          essentials.helpop: true
          essentials.list: true
          essentials.motd: true
          essentials.rules: true
          essentials.spawn: true
          iConomyChestShop.shop.buy: true
          iConomyChestShop.shop.create: true
          iConomyChestShop.shop.sell: true
          towny.town.invite: true
          towny.wild.build: true
          towny.wild.destory: true
          towny.wild.itemuse: true
          towny.wild.switch: true
          permissions.build: true
      Hero:
        permissions:
          essentials.clearinventory: true
          essentials.essentials.tp: true
          essentials.jump: true
          essentials.lavaplace: true
          essentials.me: true
          essentials.superpick: true
          essentials.tree: true
          essentials.waterplace: true
          worldedit.superpickaxe: true
          permissions.build: true
        inheritance:
          - default
          - member
          - vip
          - builder
          - knight
      Baron:
        permissions:
          essentials.compass: true
          essentials.item: true
          essentials.tpa: true
          permissions.build: true
        inheritance:
          - default
          - member
          - vip
      Knight:
        permissions:
          essentials.jump: true
          essentials.me: true
          essentials.waterplace: true
          permissions.build: true
        inheritance:
          - default
          - member
          - vip
          - builder
      Builder:
        permissions:
          essentials.compass: true
          essentials.item: true
          essentials.tpa: true
          permissions.build: true
        inheritance:
          - default
          - member
          - vip
      Moderator:
        permissions:
          bb.admin.info: true
          essentials.ban: true
          essentials.kick: true
          essentials.mute: true
          essentials.togglejail: true
          essentials.tp: true
          essentials.unban: true
          groupmanager.mandemote: true
          groupmanager.manpromote: true
          mcmmo.chat.adminchat: true
          permissions.build: true
          permissions.player.setgroup
        inheritance:
          - default
          - member
          - vip
          - builder
          - baron
     
  21. Anyone Have a skype and is good with permissions?!?!??! Please I neeeeeed help... Add me skype PlaystationCraig. Someone that is good with permissions is needed explanitory. I am new to this and can follow instructions easily.
     
  22. Offline

    d00ba

    This uses the same commands as permissions 2.7.4, so when using the superpermsbridge plugin you're no longer able to reload the old permissions file /permissions -reload all

    So if you make changes to the old permissions file you have to restart the server to reload them..

    Anyway around this?
     
  23. Offline

    gameswereus

    What if I want to have a donor and a mod? Is there anyway to do this without making a whole separate group for him?
     
  24. Offline

    laguser

    There is a big problem with this plugin! with setgroup

    example:
    If I am a moderator/admin who have the perms to setgroup, they can just promote anybody to the same group as them or higher.

    I think they can even promote themselves to admin (Not Tested)
     
  25. Offline

    Snowy007

    Thanks.
    Now i was busy configuring the permissions and i came up with one last question. (hopefully)
    I want the 2 builder groups to have different permissions in skylands and creative.
    But i was thinking.. both those worlds also have nether worlds and the groups need to keep their permissions when they go to a nether world.
    Will i have to create the config like this?
    With all the world permissions entered twice for the normal and nether world?
    Or will each nether world automatically apply the permissions of the normal world they belong to?

    Code:
        Builders:
            permissions:
                permissions.build: true
            worlds:
                creative:
                    permission.1: true
                    permission.2: true
                    permission.3: true
                creative_nether:
                    permission.1: true
                    permission.2: true
                    permission.3: true
                skylands:
                    the.skylands.permissions: true
                skylands_nether:
                    the.skylands.permissions: true
            inheritance:
            - Guest
    Also... related to above question.
    if i would create another creative world in the future, that would need exactly the same permissions set as the current creative world. Will i have to put all those permissions on both worlds. Or is there a more easy way of telling world to use the same permissions as another world?
    That way i won't have to keep the permissions updated on multiple worlds when i install a new plugin. And it keeps the config.yml from growing very very large.
     
  26. Someone help me on my sever with this permissions :D Skype name is PlaystationCraig.. Really in need of help
     
  27. Offline

    Torados

    The new builtin permissions are much more complicated thet the old permissions.

    Setting up the config i`m admin on my server, and after login i`m not admin.
    The /time command doesn`t work. And, i don`t understand, the /list command, too.
    I only got "i`m sorry, Dave, but i cannot let you do that."

    Why is it so freakin complicated instead of the old permissions ?

    here`s my config:
    Code:
    users:
        torados:
            permissions:
            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: '&cDu hast keine Rechte um hier zu bauen.'
    It`s like the default config, only my name was changed to be admin.
    I really need a step2step tutorial for configuring that, because i`m not really good in speaking english and i don`t understand all the fine details.

    Maybe someone can explain me that in german.
    "Vielleicht kann mir das wer in Deutsch erklären."

    thanks
     
  28. Offline

    Celtic Minstrel

    Short answer is yes, you need to duplicate the permissions for each world. There are ways to do it in a way that will let you change it just once if you need to change something, though. One is to define (for example) the.skylands.permissions as a node in permissions.yml with all the child permissions you want and just grant that. The other way is to use YAML aliases, though I'm not sure if that might have the potential to create problems if you decided to edit permissions using the in-game commands. Anyway, if you want to use YAML aliases, your example would be reduced to something like this:
    Code:
        Builders:
            permissions:
                permissions.build: true
            worlds:
                creative: &creative
                    permission.1: true
                    permission.2: true
                    permission.3: true
                creative_nether: *creative
                skylands: &skylands
                    the.skylands.permissions: true
                skylands_nether: *skylands
            inheritance:
            - Guest
    Using nodes defined in permissions.yml would give a reduction more like this:
    Code:
        Builders:
            permissions:
                permissions.build: true
            worlds:
                creative:
                    creative.permissions: true
                creative_nether:
                    creative.permissions: true
                skylands:
                    skylands.permissions: true
                skylands_nether:
                    skylands.permissions: true
            inheritance:
            - Guest
    (In this case creative.permissions and skylands.permissions are placeholders for a single permission node; you could even use those as the names, though I'd recommend inserting a prefix that's less likely to conflict with a plugin. I myself use server.* for custom permissions.)

    Either of the above ways would do what you want; you'd still need to go in and add the new world with its permissions, but if you use shorthand like I described it's a matter of one or two lines per group.

    Oh, and to define permission nodes in permissions.yml:
    Code:
    server.creative.permissions:
        default: true|false|op|not op # optional line, choose just one of the four options
        description: Creative permissions for the server! # optional line
        children
            permission.1: true
            permission.2: true
            permission.3: true
     
    vSanjo likes this.
  29. Offline

    bogboom

    Can anyone tell me why this wont work:

    Code:
    groups:
      default:
        permissions:
          server.guest: true
          permissions.build: false
        worlds:
          guest:
             permissions.build: true
    Basically I want Guests to be able to build in the guest world but no where else. However if I join in another world and tp to "Guest" I cannot build. If I join Directly to the "Guest" world, I can build, and then I can go to other worlds and build as well. It seems as if it does not check this permission when tp'ing between worlds.
     
  30. Offline

    Celtic Minstrel

    @bogboom – Download the latest dev build which fixes this; it's posted somewhere in this thread, probably in a post by krinsdeath.
     
  31. Offline

    AcelinH98

    HELPP When In My Server And Type /Give AcelinH98 5 64, It say i dont have access, And ive added every permissions Node on the group im in which is Host, WHY ISNT IT WORKING ! And I also have Essentials and ive put all the Nodes for that on my group and i type /i 5 64, And still NO ACCESS!!
     

Share This Page