[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

    bogboom

  3. Offline

    kel

  4. Offline

    Celtic Minstrel

    @kel – The fix is to quote the username:
    Code:
    users:
      '8547623':
        groups: [ ... ]
        permissions: [ ... ]
     
  5. Offline

    Ranzear

    SuperPermsBridge was breaking a lot of my plugins because as described it gives legacy 3.0 style permissions, but the plugin reports itself as Permissions 2.7.7! I edited the plugin.yml in SuperPermsBridge.jar to version 3.1.6 and a ton of stuff now works again since moving over to PermissionsBukkit.

    Nasty oversight, easy fix...
     
    KoryuObihiro likes this.
  6. Offline

    vSanjo

    I just did this thinking 'this whole PermissionsBukkit thing is out of hand, it probably won't wo-' .. and it did.

    Amazing.
     
  7. Offline

    Black_Jack

    No sql support? Such as Permissions 3.x?
     
  8. Offline

    phaed

    Permissions go haywire (commands stop working) when you /reload a server with Spout and PermissionsBukkit installed. cb#1060, latest spout, latest PB.
     
  9. Offline

    Celtic Minstrel

    If you really must have SQL, go get PermissionsEx.
     
  10. Offline

    phaed

    82: List<Player> onlinePlayers = group.getOnlinePlayers();

    Code:
    22:11:53 [SEVERE] java.lang.NullPointerException
    
    22:11:53 [SEVERE]      at com.platymuus.bukkit.permissions.Group.getPlayers(Group.java:31)
    
    22:11:53 [SEVERE]      at com.platymuus.bukkit.permissions.Group.getOnlinePlayers(Group.java:43)
    
    22:11:53 [SEVERE]      at net.sacredlabyrinth.Phaed.Core.managers.CommandManager.who(CommandManager.java:82)
     
  11. Offline

    WaffleD

    Guys I need help. I get "You don't have permission to do that" whenever I try to use any of the NPC commands, and I can only access two of my iConomy commands.


    Code:
    users:
        WaffleD:
            permissions:
                permissions.example: true
            groups:
            - admin
    
    groups:
        default:
            permissions:
                permissions.build: false
        admin:
            permissions:
                permissions.*: true
                essentials.*: true
                iConomy.*: true
                citizens.*: true
            inheritance:
            - user
        user:
            permissions:
                permissions.build: true
                iConomy.access: true
                citizens.trader.use.trade: true
                magicspells.grant.fireball: true
                magicspells.cast.fireball: false
                magicspells.grant.list: true
                magicspells.cast.list: true
                magicspells.grant.help: true
                magicspells.cast.help: true
    
    worlds:
                creative:
                    coolplugin.item: true
            inheritance:
            - default
    messages:
        build: 'i&cYou do not have permission to build here.'
    
    Any solutions for this?
     
  12. Offline

    Ranzear

    Understatement. Using /perms reload at the very least doesn't fix it, or at worst induces the same issue.

    When I do a full stop/restart a lot of the issues I'm chasing just disappear (except mChat, which apparently was written 'to detect for Permissions 2.7.7 and use the 3.0 API in that case' which makes it go schizo anyway).
     
  13. 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!!
     
  14. Offline

    Nipper

    @SpaceManiac Question: I looked all over the post. I do no seem to find a place saying multi world support. I run more then one world one creative one survival. I still want to be able to give some commands on one world but not the other. I juts need a little bit of clarifying on this.
     
  15. Offline

    Robert Pendell

    I'm looking at this and it looks good. I'm going to hold off a bit though as I need to go and revamp my Admin group (need to remove * and replace with an appropriate set) and need to replace a few plugins with ones that properly support PermissionsBukkit (about half were not updated since bukkit 953). Now then does this have multi-world support at all?
     
  16. Offline

    mrgreaper

    still have the following error

    Code:
    >permissions
    17:00:05 [INFO] You do not have permissions to do that.
    
    this is in the console

    the console does not have permission to use ANY permission commands
    and niether do our admins with permissions.*

    reported this 3 days ago and 2 days ago and again now...wonder if theres any point?
    we are on the latest version of permission bukkit (1.1) and superpermbridge (1.2) and rb of bukkit 1060
     
  17. Offline

    Celtic Minstrel

    There might be an option in the Essentials config to enable Bukkit permissions. If not, you may need to update Essentials.
    There is multi-world support. There are some examples of how to do it in the last few pages; even some on this page.
     
  18. Offline

    SkeetGaDoo

    Hello all,

    I don't mean to overlook what many of you might have already said. I feel like my answer is on the tip of my tongue, but I JUST can't seem to get it all together.

    All I want to do right now is set up PermissionsBukkit 1.1 with Essentials for my members. So far, I have these plugins installed:

    Essentials v2.4.2
    Essentials Spawn v2.4.2
    Lockette (Chest Security) 1.3.8
    PermissionsBukkit 1.1
    SupermsBridge 1.2


    I understand the gist of setting up PermissionsBukkit's config file to set up users and groups, and I have done so like this (apologies for not showing the config with correct indentation):

    groups:
    default:
    permissions:
    permissions.build: true
    member:
    permissions:
    lockette.user.create.*: true
    essentials.afk: true
    essentials.help: true
    essentials.list: true
    essentials.mail: true
    essentials.mail.send: true
    essentials.me: true
    essentials.motd: true
    essentials.msg: true
    essentials.rules: true
    essentials.whois: true
    essentials.balance: true
    essentials.balance.others: true
    essentials.balancetop: true
    essentials.pay: true
    essentials.sell: true
    essentials.worth: true
    essentials.spawn: true
    essentials.home: true
    essentials.sethome: true
    inheritance:
    - default
    moderator:
    permissions:
    essentials.kick: true
    essentials.mute: true
    essentials.ban: true
    essentials.banip: true
    essentials.unban: true
    essentials.unbanip: true
    essentials.tp: true
    essentials.tphere: true

    inheritance:
    - member
    admin:
    permissions:
    essentials.*: true
    permissions.*: true
    lockette.*: true
    inheritance:
    - moderator
    messages:
    build: '&cYou do not have permission to build here.'


    From what I have read in the previous posts, There ARE some plugins that don't recognize PermissionsBukkit (ie: Essentials) therein lies my problem. There have been a number of people who have said SupermsBridge tricks it into thinking its Permissions so it does recognize the plugin PermissionsBukkit (hooray!), yet I don't fully understand SupermsBridge, and it is somewhat difficult to find information on it.

    When working with individual commands in essentials for groups would I just:

    supermbridge.essentials.help: true

    or does supermsbridge only help with 'all-access' commands like:

    supermbridge.essentials.*: true

    My goal:

    I'd like to set up PermissionsBukkit's Configuration file for the groups, so that when users join, they are automatically assigned to default (happens regardless). I'd like to be able to move them into groups I have already made with preset permissions and essentials commands without them having access to all of the commands (Which is what is happening to me right now).

    Any help? Maybe an edited look at my config above might help me to understand.

    Thanks again to anyone for taking the time to look at this,

    Skeet
     

    Attached Files:

  19. Offline

    iCheckPlugins

    Atm, I'm using Permissions 3, but I need to find an easy way to switch without going through every single node and copying and pasting. Is there a really easy way to switch to switch?
     
  20. Offline

    d00ba

    Apparently not. Plus if you're using plugins like WorldEdit and WorldGuard you can forget it as they don't support this.

    "Citizens supports Permissions 2.7.x and 3.x"

    I believe they're adding PermissionsBukkit support in Citizens 1.1

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

    WaffleD

    Citizens will no longer support Permissions 2.7.x and 3.x in the 1.1 update, and it also worked for PermissionsBukkit for me, but it just stopped working all of the sudden.
     
  22. Offline

    SilencShadoW

    Hey i realy like ur plugin but i got a big problem, my "default" member (new member without any group!) cant use the CommandSigns plugin .. my member can ... they got the "ur not accepted yet" message ... and my normal default group can use it too ... why my "new" member without any group (normaly should be default?!) cant right click the sign??
     
  23. Offline

    SBD09

    ok I got a problem when people join the server for the first time they don't get put into the default group how do i fix this? My default group permissions are below.

    Code:
        Guest:
            permissions:
                permissions.build: false
                mchat.prefix.Guest: true
                essentials.spawn: true
                essentials.rules: true
                essentials.list: true
                essentials.afk: true
     
  24. Offline

    efstajas

    I NEED an ability to change the name of the default group...

    Edit.: Are you fucking kidding me... I just configured everything, switched from Permissions 3 to this... restarted server... whole config overwritten to default. I just spent 3 hours to do that and now it's just deleted.
    I am pretty mad now.
    I'll stay with Permissions 3 'til it's not possible anymore.

    Edit. 2: This plugin isn't good. All the trouble with porting over... Permissions 3 was by far more flexible. I am REALLY missing the derp.derp.* and '-derp.derp' nodes.
    I decided to stay awake this night just to switch to PermissionsBukkit when there's nobody on, it took 3 hours and now this plugin deleted my whole work. I am really frustrated.

    Please explain this to me, @SpaceMania

    Edit.3: Is there a chance for Permissions 3 to be ported to the Bukkit Permissions API?

    I think the default group must be named default... This plugin seems really unfinished.

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

    BattleGroundxx

    Hey @SpaceManiac can you explain to me this: do we still need a permissions plugin?
    And can you help me write the code for the permissions.yml?
    Basically I am the server owner so naturally I'm the admin and have access to all commands my minecraft name is: BattleGroundxx
    And my friend is part of another group (moderator) and has access to all default commands (build, destroy etc.) His minecraft name is: mittydoug
    And i know that certain plugins have permissions and since this is a private server the admin and moderator groups have access to all commands that are required by plugins
    and i am going to install this plugin

    So all I ask is you write the code for the permissions.yml and the plugin above because im not so computer savy and 1 more thing the moderator group does not have access to these commands (basically the ones required by PermissionsBukkit) anyways these are the command the moderator group has no access to:

    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 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.

    If you can do all this i would VERY VERY VERY VERY much appreciate it!

    The plugins I am currently running are:
    AutoRepair
    Backup
    BananaChunk
    ChopTree
    ClayGen
    CraftBukkitUpToDate
    DwarfForge
    EffectiveArrows
    FastObby
    HeroicDeath
    HomeSweetHome
    IntelliDoors
    MobArena
    ObsidianFlow
    Pail
    SimpleTime-v4.3
    SpongeRestore
    Spout
    Stargate
    StyxBed
    TextWrap


    Again all groups/users have access to the commands required by plugins!
    Thank you very much if you can write the code for permissions.yml and the PermissionsBukkit That would be so helpful I know this is a Large request but again I am not computer savy with java. If you can complete this for me I that would be greatly appreciated.

    Thank You!
     
  26. Offline

    Richard Scheide

    Can someone tell me why the only thing we can do is build? I should be admin and the test user can't use any of the permissions.

    Code:
    users:
        Kull_TheConq:
            permissions:
                waypoint.*: true
                waypoints.*: true
            groups:
            - admin
        LordFritz:
            permissions:
            groups:
            - user
    groups:
        default:
            permissions:
                permissions.build: false
        admin:
            permissions:
                permissions.*: true
                '*': true
            inheritance:
            - user
        user:
            permissions:
                permissions.build: true
            worlds:
                world:
                    waypoint.*: true
                    waypoints.*: true
                    citizens.*: true
                    citizens.toggle.*: true
                    simplechestlock.command.reload: true
                    simplechestlock.command.save: true
                    simplechestlock.lock: true
                    simplechestlock.lock.*: true
                    simplechestlock.lock.Lockable_Name_Here: true
                    mantraweather.weather: true
                    residence.create: true
            inheritance:
            - default
    messages:
        build: '&cYou do not have permission to build here.'
     
  27. Offline

    efstajas

    This plugin doesn't support * nodes. Also, do you have the permissions bridge?
     
  28. Offline

    Richard Scheide

    I had Permissions 3.2.* but it started acting up after 1060 upgrade. Do you mean SuperPerm, if so. No. I simply remove the old permissions.

    Also, is there a code for admin like '*' for admin to have everything?
     
  29. Offline

    efstajas

    No, there's nothing like *... I really don't support this plugin. I'll look into PermissionsEx since Permissions 3 seems to be dead.
     
  30. Offline

    Celtic Minstrel

    I think you only do it for ones with a * … though I thought Essentials had updated to support PermissionsBukkit, so maybe you should also try upgrading Essentials and searching for config options that might be relevant.

    WorldEdit and WorldGuard do in unofficial versions.

    You shouldn't really editing configuration files while the server is running though.

    PermissionsBukkit has this.
    Code:
    my.permission.node: false
    As for wildcards, it supports them for those plugins that define them for you.

    Yes, there is a chance, but it's not looking like a good chance at the moment. You should probably switch away from Permissions 3, even if you don't choose to use PermissionsBukkit (there are at least two other options).

    True but misleading. At least one of the * nodes in his post (permissions.*) will work. I'm guessing the two citizens ones will work too. The '*' node will not work, though.
     
  31. Offline

    efstajas

    Thank you for the really fast reply. :) I'll take a look in PermissionsEx.

    I do since months without a problem.

    And sorry for trolling a bit, I'm just a little angry that the config got deleted. :oops:

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

Share This Page