[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

    Kurai Ookami

    I used to have problems with punctuation you could use Online YAML Parser to scratch that possibility off the list just copy and paste your current setup and it debugs instantly with every change you make.
     
  3. Offline

    HAWKEYE10

    Will This Plugin Be Updating
     
  4. Offline

    Sabersamus


    i have talked to the author, and yes. it will be updating
     
  5. Offline

    HAWKEYE10

  6. Offline

    ornz

    Can someone help me
    I have some mods like lockette, worldedit, ownblocks
    The problem is that Op-s in my server have access to all the script rights and when i am not OP, i cant do stuff with specified nodes to my nickname. I'm in the correct group called "owner". How can i remove OP-s rights and make my own work.
    http://pastebin.com/3bgPFeuC - my config
    http://pastebin.com/74mqbJce - my permissions file
     
  7. Offline

    Ewe Loon

    First thing you need to know, is that OP is not a part of permissions bukkit and OP overrides all permissions granting everything, I havnt found a way around it

    To remove ops rights Deop all you current uses (delete or blank the ops.txt file in the servers folder, with server off)
    However you might want to leave yourself as an OP

    If you want to allow some opp rights there are some plugins that will grant them with permissions to control who has access to each command ( I cant name any , as im writing my own )

    also after reading you configs you should use inheritance, it makes it easy to see the differences between ranks

    Question, Is it possible to assign groups to players on a per world basis ?
    example Ewe_loon is in group "user" on world called "skylandservival" and in group "Admin" on a world called "FreeBuild"

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

    Credomane

    SpaceManiac
    Better update PermissionsBukkit. Just about everything in your official build is going to get removed. :)

    I don't think any permissions plugin does that. It is completely unneeded unless you built your permissions in a strange fashion. Use the per world permissions to accomplish this.
     
  9. Offline

    ItsHarry

    How would I use this as an API? For a plugin I need to get all players and their groups :(
     
  10. Offline

    L355

    Hi I was having some troubles with my permissions and mchat the ranks wouldnt show up and the permissions wouldn't work at all any help would be GREAT!
     
  11. Offline

    FlawlessSin

    When a player starts out they aren't in a default group, anyway to do that?
     
  12. Offline

    iMatthew_10_13

    All I want to know is how do you set up prefixes, on This plugin, Permissions Bukkit, But using Herochat. I already have SuperPerms, so Herochat should be working. I have the knowledge for config. file, but it is
     
  13. Offline

    SpaceManiac

    Gasp!
    I have uploaded a reasonably complete update for R5 to BukkitDev - check it out here or in the first post. Thanks for your patience!
     
  14. Offline

    HappyGrenades

    So let me get this straight, any plugin that supports SuperPerms will work with this plugin?
     
  15. Offline

    mamutos99

    Hi, I would set the rank Member as a rank that is given to players automatically after entering the server. How to do it on the PermissionsBukkit?
     
  16. Offline

    beleg

    yes

    you have to name the group "default"
     
  17. Offline

    aligator

    is there any possibility to youse permissionnodes with numbers as value?
    something like this:
    xwarp.warp.limit.private: 3
     
  18. Offline

    Acars

    Ok so basicly im having trouble with this plugin... last night i had everything working besides herochat. i added one permission and nothing else worked. it stopped working. i deleted the permissions jar and foldier and redid the nodes and now nothing is working. heres how i have it set up.
    Code:
    users:
        Ih0p:
            permissions:
            groups:
            - default       
    groups:
        default:
            permissions:
                permissions.build.*: false
                heroes.classes.Tank: true
                heroes.classes.Medic: true
                heroes.classes.Caster: true
                heroes.classes.Ranger: true    
     
  19. Offline

    joryvd

    I can't get players added to groups. When i try it, it says "an internal error occured while attempting this command". Might be dumb question but can anybody please help me with it? I'm kinda new to this stuff...
     
  20. Offline

    DraXxus1549

    Can someone tell me why my permission file is working? I have myself in the admin group but for some reason I cannot use the permissions that are associated with it.

    Here is my permissions config file.

    Code:
    users:
        draxxus1549:
            groups:
            - admin
    groups:
        default:
            permissions:
                permissions.build: false
        admin:
            permissions:
                permissions.*: true
                essentials.* : 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.'
    Also the build permissions aren't working, do I need a plugin for it to work?
     
  21. Offline

    joryvd

    Is there a global '*' available? or is something like this coming? Or is there another way to disable bukkit permissions?

    Most likely the built-in bukkit permissions are blocking you. Try opping yourself and deopping and see if it makes any difference

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

    DraXxus1549

    I oped my self and I was able to use commands then I deoped my self and I no longer had access.
     
  23. Offline

    funky man


    You have spaces after default (i marked where with *'s)
     
  24. Offline

    lolhoofd

    hi, i'm kinda new to permission.
    and i can't seem to get it working properly

    i'm in the right group, but when i log in i don't have any perms
    but when i use "perm reload" in the console. then i get my perms

    here are my
    permissions.yml: http://pastebin.com/HzkwYbX1

    and
    config.yml: http://pastebin.com/ZE44ztvd
     
  25. Offline

    godsyn

    Ticket already submitted concerning this. Up-vote the issue.
     
  26. Offline

    DraXxus1549

    Anyone have any idea why my permissions are not working? I also tried another permissions plugin (permissionsEx) and I am only able to use commands when I am oped even though I have permission via the permission config.
     
  27. Offline

    achterham

    Hey, i've got a problem,
    Every new player, that joins the server is just default.
    I want that he is another rank,
    How to do that?

    I have this now:

    Code:
    groups:
        Baby:
            default: true
            permissions:
                essentials.warp: true
                essentials.help: true
                essentials.helpop: true
                essentials.list: true
                essentials.motd: true
                essentials.rules: true
                essentials.spawn: true
                permissions.build: false
        Child:
            permissions:
                bookworm.copy.others: true
                bookworm.copy.own: true
                bookworm.create: true
                bookworm.destroy.own: true
                bookworm.place.own: true
                bookworm.remove.own: true
                bookworm.write.own: true
                ChestShop.shop.buy: true
                ChestShop.shop.create: true
                ChestShop.shop.sell: true
                essentials.afk: true
                essentials.back: true
                essentials.back.ondeath: true
                essentials.balance: true
                essentials.balance.others: true
                essentials.balancetop: true
                essentials.chat.color: true
                essentials.chat.question: true
                essentials.chat.shout: true
                essentials.compass: true
                essentials.depth: true
                essentials.help: true
                essentials.helpop: true
                essentials.home: true
                essentials.ignore: true
                essentials.list: true
                essentials.mail: true
                essentials.mail.send: true
                essentials.me: true
                essentials.motd: true
                essentials.msg: true
                essentials.pay: true
                essentials.ping: true
                essentials.portal: true
                essentials.powertool: true
                essentials.protect: true
                essentials.rules: true
                essentials.sethome: true
                essentials.sign.use.heal: true
                essentials.sign.use.weather: true
                essentials.signs.break.disposal: true
                essentials.signs.break.mail: true
                essentials.signs.break.protection: true
                essentials.signs.break.trade: true
                essentials.signs.create.disposal: true
                essentials.signs.create.mail: true
                essentials.signs.create.protection: true
                essentials.signs.create.trade: true
                essentials.suicide: true
                essentials.tpa: true
                essentials.tpaccept: true
                essentials.tpahere: true
                essentials.tpdeny: true
                essentials.warp: true
                essentials.warp.list: true
                essentials.worth: true
                permissions.build: true
                essentials.spawn: true
            inheritance:
            - Baby
        Mayor:
            permissions:
                essentials.*: true
                permissions.*: true
            inheritance:
            - Baby
            - Child
    messages:
        build: '&cYou do not have permission to build here.'
    users:
        drownzz:
            groups:
            - Baby
        ibear:
            groups:
            - Child
    
     
  28. Offline

    statistx

    Hi.
    Updated from 1.2 to 1.5 and now i have two problems:

    in the log at the server start it says something along the line of "Can't write config.yml cause there is allready one" which alone wouldn't be a problem, BUT my permissions are all messed up.

    The user with the special group "mod" doesn't have ANY permissions.
    I tried to rename the group, i tried to put him into users.
    I didn't touch any of the other files (like the permissions.yml) since that was never needed before and after i switched back to 1.2 it worked perfectly.
    Now the usual question: should i just stay on 1.2 or (what i would prefer, since of stability and compatibility) what can i do to get it working in 1.5

    Code:
    users:
        assassin69:
            permissions:
                permissions.example: true
            groups:
            - admin
        duveru:
            permissions:
                permissions.example: true
            groups:
            - admin
        Ilius:
            permissions:
                permissions.example: true
            groups:
            - mod
        m0etzger:
            permissions:
                permissions.example: true
            groups:
            - user
        g_pompidou:
            permissions:
                permissions.example: true
            groups:
            - user
        SeeKuhe:
            permissions:
                permissions.example: true
            groups:
            - user
        soporaeternus:
            permissions:
                permissions.example: true
            groups:
            - user
        Karv_Mosh:
            permissions:
                permissions.example: true
            groups:
            - user
        _Lusankaya_:
            permissions:
                permissions.example: true
            groups:
            - user
        Lancastersilk:
            permissions:
                permissions.example: true
            groups:
            - user
        farade:
            permissions:
                permissions.example: true
            groups:
            - user
        _Schnitzel_:
            permissions:
                permissions.example: true
            groups:
            - user
        shorty777:
            permissions:
                permissions.example: true
            groups:
            - user
        MadeByHand:
            permissions:
                permissions.example: true
            groups:
            - user
        vanny2911:
            permissions:
                permissions.example: true
            groups:
            - user
        foxtrott01:
            permissions:
                permissions.example: true
            groups:
            - user
    groups:
        default:
            permissions:
                permissions.build: false
        admin:
            permissions:
                permissions.*: true
                admincmd.*: true
                XcraftGate.*: true
            inheritance:
            - user
            - mod
        mod:
            permissions:
                admincmd.item.add: true
                admincmd.time.set: true
            inheritance:
            - user
        user:
            permissions:
                permissions.build: true
                admincmd.tp.*: true
                admincmd.player.list: true
                admincmd.player.msg: true
                movecraft.*: true
                admincmd.weather.clear: true
                admincmd.spawn.tp: true
                pvptoggle.*: true
                XcraftGate.use.*: true
                XcraftGate.gate.*: true
                XcraftGate.gate: true
            worlds:
                creative:
                    coolplugin.item: true
            inheritance:
            - default
    messages:
        build: '&cYou do not have permission to build here.'
    
    Any help is highly appreciated.
    Thanks in advance
     
  29. Offline

    Acars

    for some reason it still dosnt work im positive i have deleted the extra spaces.
     
  30. Offline

    Lynxdragon

    Haha you could just give it to me?

    Holy crap dude its been TWO pages and you cant look back and read how its supposed to work.

    God damit LOOK BACK! LINK HERE ----> http://forums.bukkit.org/threads/ad...ups-plugin-1-0-1-r1.26785/page-82#post-955927

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

    statistx

    Thanks, but chill out, i spent a lot of time checking the official site, it just didn't occur to me to go back 2 pages in a thread that has 84. What are the odds..
    But regardless, my thanks are honest ;)

    edit: after looking at it i decided it's over my head right now, i will stay at 1.2 as long as it works
    edit2: or maybe not. have to wait for a user to find out, after some formatting errors, i don't get any error messages at least and all commands i can think of myself of trying, work

    On another note: I still get the Warning "Could not save config.yml....blah blah", is that normal? does it have any impact?

    my new files (that i still need to test when other usergroups are available to me) look like this. IF someone finds the time to read and can validate if they should work, thanks, if not nevermind.

    config
    Code:
    users:
        meakaadmin:
            groups:
            - admin
        guywhowantedextrapermissions:
            groups:
            - mod
        randomuser:
            groups:
            - user
     
    groups:
        default:
            permissions:
                default: true
        admin:
            permissions:
                admin: true
            inheritance:
            - user
            - mod
        mod:
            permissions:
                mod: true
            inheritance:
            - user
        user:
            permissions:
                user: true
            inheritance:
     
    messages:
        build: '&cYou do not have permission to build here.'
     
    debug: true
    permissions:
    Code:
    default:
        children:
            permissions.build: false
     
    user:
        children:
            permissions.build: true
            admincmd.tp.*: true
            admincmd.player.list: true
            admincmd.player.msg: true
            admincmd.weather.clear: true
            admincmd.spawn.tp: true
            pvptoggle.use: true
            pvptoggle.command.toggle: true
            pvptoggle.command.status: true
            pvptoggle.pvp.autoenable: true
            XcraftGate.use.*: true
            XcraftGate.gate.*: true
            XcraftGate.gate: true
    mod:
        children:
            admincmd.item.add: true
            admincmd.time.set: true
     
    admin:
        children:
            permissions.*: true
            admincmd.*: true
            XcraftGate.*: true
            pvptoggle: true
            pvptoggle.gcommand: true
    
     

Share This Page