[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

    Matthias2000123

    My Players cannot build! Pls help!
    You do not have permission to build here.

    black_ixx

    With The Plugin Wordrank?

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

    black_ixx

    WordRank dont works with PermissionsBukkit, so I wanna create my own plugin, which ranks with commands.
    And for it I have to know, how plugins can set groups
     
  4. Offline

    coolo1

    Anyone know how to fix my problem?
     
  5. Offline

    Grifhell

    I need tocreate a group, the playersin this grouphave the rightto moveto another group.In another group,theydo nothave the right togobackorto another group(another another group ).
    Is it possible?
    I think if this plugin was this permission:
    Permissions.ChangeGroup.Me.Hunters (go to the group of "Hunters")
    in which:
    Permissions.ChangeGroup.*.* (change the group for any player, the player can move to any group)
    Permissions.ChangeGroup.Me.* (change only your group, you can move yourself into any group)

    Group "Hunters" will not be this permission
    as a resultwe obtain a systemof transitiongroup/clan /race
    PS:
    I have not founda plugin forthe clans,which couldchange thefile
    ... \ plugins \ PermissionsBukkit \ config.yml
    And, it isa functionI want, what wouldthe clanshave differentrights.
    If you know ofaplugin,whereclans havedifferent rightsfromother plug-insor
    Do you knowhow to implement itin thisplugin
    Thentell me, please.

    Maybe the author thispluginwill add feature
     
  6. Offline

    Beauseant

    How do i give permissions for the normal OP commands? Like /time set ?
     
  7. Offline

    Grifhell

  8. Offline

    coolo1

    Someone? Anyone?
     
  9. Offline

    youwereout

    Is there anyway to prevent a user from being added to the default group when added to a group from in game? ie. Add user to an "admin" group via the in game commands. The permissions.yml file shows the added user and has them in two groups, default and admin.
    My admin group inherits the default group so there is no need for the duplication. However I am using another plugin that takes the group the user is in and changes the coloring of the username in chat. When it checks which group the user is in default is first and is the group used.
     
  10. Offline

    Lixah

    hey, first, im sorry if this is in an incorrect section.

    First, i am VERY new to all this, and just started messing around with Bukkit/Plugins a few days a few days ago.

    Basically, i installed craftbukkit latest version, and permissionsbukkit. now I wanted to setup my permissions, im hoping to open this server to the public in the future (maybe).

    I have attached my permissions.yml and config.yml files. Please tell me where im screwing up.
    (im sure they're messy/wrong, but im new to this, so i muddled through how to write these files etc

    Code:
    users:
        Lixah:
            permissions:
                permission.test: true
            groups:
            - admin
    groups:
        admin:
            permissions:
                server.default: false
            inheritance:
            - vip
        vip:
            permissions:
                permissions.build: true
            inheritance:
            - user
        user:
            permissions:
                permissions.build: true
            inheritance:
            - default
        default:
            permissions:
                server.default: true
    messages:
        build: '&cYou do not have permission to build here.'
    Code:
    server.default:
        children: 
            bukkit.command.version: false
            permissions.build: false
            bukkit.command.plugins: false
            bukkit.command.me: false
            permissions.interact: false
            bukkit.command.tell: false
            spamhammer:* false
    edit: no idea why i wouldn't work for me, i've since switched too Essentials Group Manager, and i have my permissions working perfectly.
     
  11. Offline

    coolo1

    I converted my Groupmanager files and put them in the config, set up simple prefix, and then its like simpleprefix and PermissionsBukkit are ignored and your either op or not. No prefixes and if you are not op you cant use commands. If I try and set anyones group it just shows the permmisionsbukkit commands and does nothing else. Here is my PermmisionsBukkit config: http://pastebin.com/mKjfXQVm
    Here is my Simple Prefix config:http://pastebin.com/D8euzQD6
     
  12. Offline

    Liger_XT5

    I'm not sure about Simple Prefix, but I use iChat for my prefixes.
    Here is my PB config, everything, except xwarp permissions, work just fine.
    http://hgs883.hostedd.com/misc/PB1-26-2012.txt
     
  13. Offline

    coolo1

    Thanks, I will try that now.

    [Edit] It works! Thank you so much!
    [Edit] Now what have I done? The prefixes became [] and nicknames disappeared...
     
    Liger_XT5 likes this.
  14. Offline

    ferrybig

    is it just me, or get every user an error from this plugin if an user if kicked, I got it since mc 1.8
     
  15. Offline

    ndvenckus1

    Well, to put it briefly...
    My permissions simply seem to refuse to work. I am running the "PermissionsBukkit v1.1 (jar)" (listed toward the top of this page). There is a more recent download just above it called "Krinsdeath's Fix Build (1.2) (jar)." But to my knowledge, they are both stable builds for craftbukkit 1.0.1, which I downgraded to due to incompatibility issues with the 1.1 build. I am not running any plugins at the moment (aside from this one, of course), although I did leave the "SimplePrefix" nodes in the config.yml. I don't see this as a problem as Bukkit should simply skip past them. Upon start-up, it appears to run perfectly fine:
    Code:
    2012-01-27 03:54:34 [INFO] Starting minecraft server version 1.0.1
    2012-01-27 03:54:34 [INFO] Loading properties
    2012-01-27 03:54:34 [INFO] Starting Minecraft server on *:25565
    2012-01-27 03:54:35 [INFO] This server is running Craftbukkit version git-Bukkit-1.0.1-R1-b1597jnks (MC: 1.0.1) (Implementing API version 1.0.1-R1)
    2012-01-27 03:54:35 [INFO] Preparing level "world"
    2012-01-27 03:54:35 [INFO] Default game type: 1
    2012-01-27 03:54:35 [INFO] Preparing start region for level 0 (Seed: 8357399210857255150)
    2012-01-27 03:54:35 [INFO] Preparing start region for level 1 (Seed: 8357399210857255150)
    2012-01-27 03:54:36 [INFO] Preparing start region for level 2 (Seed: 8357399210857255150)
    2012-01-27 03:54:36 [INFO] Preparing spawn area: 56%
    2012-01-27 03:54:36 [INFO] PermissionsBukkit v1.1 is now enabled
    2012-01-27 03:54:36 [INFO] Done (0.121s)! For help, type "help" or "?"
    
    Here is my config.yml setup:
    Code:
    users:
        ndvenckus1:
            groups:
            - admin
        ZPWR22:
            groups:
            - regular
        _Flagellum:
            groups:
            - regular
        GCupcake:
            groups:
            - regular
        gcupcaque:
            groups:
            - regular
        pyrotastica:
            groups:
            - regular
        andrewstar123:
            groups:
            - regular
    groups:
        default:
            permissions:
                permissions.build: false
                Permissions.*: false
        admin:
            permissions:.*: true
            simpleprefix.admin: true
            inheritence:
            - moderator
        moderator:
            permissions:
            simpleprefix.mod: true
            permissions.help: true
            permissions.group.help: true
            permissions.group.list: true
            permissions.group.players: true
            permissions.player.help: true
            permissions.player.groups: true
            inheritance:
            - regular
        regular:
            permissions:
                permissions.build: true
                permissions.help: true
                permissions.group.help: true
                permissions.group.list: true
    messages:
        build: '&cYou do not have permission to build in this area.'
        help: '&cYou do not have access to that command.'
        group: '&cYou do not have access to that command.'
        player: '&cYou do not have access to that command.'
    I have watched tutorial after tutorial, and from what I've seen, there's absolutely nothing wrong with my permissions. Like I said and showed, upon initial start-up, bukkit seems to recognize these permissions just fine and presents me with no errors at all. But when I go in game, to start off, several permissions commands cease to work at all, they are:
    • /permissions info (I'm actually not positive on this one. I've only tested it with /permissions info build and it gives me the in-game error message, "Permission build not found." Am I misusing the command?)
    • /permissions dump (another mixed one. When I use it on myself, while online, it seems to work just fine. But when I use it on someone else, say "ZPWR22," from the above code, it says, "Player ZPWR22 not found." As I have shown above, he is very clearly in the config.yml, I belive in the correct format. Is it simply because he is not online?
    One last thing. One of my initial errors previous to this was that in my bukkit.yml, 'permissions-file' was set to point to the default 'permissions.yml' rather than 'config.yml.' When I discovered this, I changed it so that it looks like this:
    Code:
    Permissions-File: Craftbukkit/plugins/permissionsbukkit/config.yml
    This should work, correct?
    Any help is appreciated, thanks! :D

    I am currently trying to create a node in the permissions.yml file (the root permissions) to prevent ops from having access to all commands. Admittedly, I am fairly new to permissions coding, but I think I've got the gist of it down pretty well. Here's the code:
    Code:
    server.forops:
        description: Ops don't deserve everything!
        default: op
        children:
            permissions.*: false
            worldedit.*: false
    As you've probably noticed, all that I've got installed is WE and permissions :p
    I basically want this node to disable all of the ops permissions and then I want CraftBukkit to go back to the config.yml in the PermissionsBukkit folder and give out commands based on groups. The main purpose of this is because I want my mods to be ops so that they can ban, kick, etc., but I don't want them to have access to all of the goody admin commands.

    So, how do I make this work? What have I done wrong in the permissions.yml? Should I instead put this in config.yml? Thanks :)

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

    Liger_XT5

    Are you using iChat? if so, can I see your config and variable file settings?
     
  17. Offline

    footlongburgers

    when will permissionsbukkit be released for 1.1 RB??
     
  18. Offline

    ndvenckus1

    He hasn't worked on development for this plugin in a looong time :/
     
  19. Offline

    NixonInnes

    Is it possible to set a governing "You don't have permissions!" message?
    i.e. In config.yml:
    Code:
    messages: 
        *: '&cNo. Now get back to your digging, peon.'
     
  20. Offline

    5000 People

    ok the word 'official' hooks me but why should i switch from pex to this
     
  21. Offline

    Mercury

    PHP:
    modvip:
      
    permissions:   
      
    inheritance:
      - 
    mod
      
    vip
    Is it possible?
     
  22. Offline

    coolo1

  23. Offline

    dj_rawscratch

    deafault group contains unknown value????? unknown value.png someone help me please!!!


    HERES MY PERMISSIONS.YML /CONFIG.YML

    Code:
    users:
        dj_rawscratch:
            permissions:
            groups:
            - admin
        link12121212:
            permissions:
            groups:
            - admin
        deathmind30:
            permissions:
            groups:
            - user
        magicaltomb:
            permissions:
            groups:
            - user
        allshamnowow123:
            permissions:
            groups:
            - admin
        serocy:
            permissions:
            groups:
            - admin
        dancing_duck3:
            permissions:
            groups:
            - user
        chekhov01:
            permissions:
            groups:
            - user
        andythederp:
            permissions:
            groups:
            - admin
        googly_goo:
            permissions:
            groups:
            - admin
        nyancat114:
            permissions:
            groups:
            - user
    groups:
        default:
            default: true
            permissions:
                permissions.build: true
                deathtpplus.deathtp.deathtp: true
                deathtpplus.deathtp.streak: true
                deathtpplus.deathtp.deaths: true
                deathtpplus.deathtp.kills: true
                deathtpplus.tombstone.use: true
                deathtpplus.tombstone.find: true
                deathtpplus.tombstone.list: true
                deathtpplus.tombstone.reset: true
                deathtpplus.tombstone.time: true
                deathtpplus.tombstone.large: true
                deathtpplus.tombstone.lwc: true
                deathtpplus.tombstone.lockette: true
                permissions.build: true
                essentials.spawn: true
                essentials.rules: true
                essentials.motd: true
                essentials.list: true
                essentials.helpop: true
                essentials.help: true
                myhome.econ.free.*: true
        admin:
            permissions:
                permissions.*: true
                deathtpplus.admin: true
                deathtpplus.admin.list: true
                deathtpplus.admin.find: true
                deathtpplus.admin.remove: true
                deathtpplus.admin.time: true
                deathtpplus.admin.version: true
                deathtpplus.admin.tombStoneDTP: true
                essentials.ban: true
                essentials.ban.notify: true
                essentials.banip: true
                essentials.broadcast: true
                essentials.clearinventory: true
                essentials.delwarp: true
                essentials.eco.loan: true
                essentials.ext: true
                essentials.getpos: true
                essentials.helpop.recieve: true
                essentials.home.others: true
                essentials.invsee: true
                essentials.jails: true
                essentials.jump: true
                essentials.kick: true
                essentials.kick.notify: true
                essentials.kill: true
                essentials.mute: true
                essentials.nick.others: true
                essentials.realname: true
                essentials.setwarp: true
                essentials.signs.create.*: true
                essentials.signs.break.*: true
                essentials.spawner: true
                essentials.thunder: true
                essentials.time: true
                essentials.time.set: true
                essentials.protect.alerts: true
                essentials.protect.admin: true
                essentials.protect.ownerinfo: true
                essentials.ptime: true
                essentials.ptime.others: true
                essentials.togglejail: true
                essentials.top: true
                essentials.tp: true
                essentials.tphere: true
                essentials.tppos: true
                essentials.tptoggle: true
                essentials.unban: true
                essentials.unbanip: true
                essentials.weather: true
                essentials.whois: true
                essentials.world: true
            inheritance:
            - user
        user:
            permissions:
                permissions.build: 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.shout: true
                essentials.chat.question: true
                essentials.compass: true
                essentials.depth: true
                essentials.home: true
                essentials.ignore: true
                essentials.kit: true
                essentials.kit.tools: true
                essentials.mail: true
                essentials.mail.send: true
                essentials.me: true
                essentials.msg: true
                essentials.nick: true
                essentials.pay: true
                essentials.ping: true           
                essentials.powertool: true
                essentials.protect: true
                essentials.sethome: true
                essentials.signs.use.*: true
                essentials.signs.create.disposal: true
                essentials.signs.create.mail: true
                essentials.signs.create.protection: true
                essentials.signs.create.trade: true
                essentials.signs.break.disposal: true
                essentials.signs.break.mail: true
                essentials.signs.break.protection: true
                essentials.signs.break.trade: true
                essentials.suicide: true
                essentials.time: 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
            worlds:
                creative:
                    coolplugin.item: true
            inheritance:
            - default
    messages:
        build: '&cYou do not have permission to build here.'
    
     
  24. Offline

    Liger_XT5

    Check all your permissions for each group
    It should look like:
    - plugin.permission.node.
    Not
    plugin.permissions.node.

    It's a bit late for me. (past midnight, long day with work and college.)
    Try to compare yours with mine, If you can't figure it out, I'll take a closer look.

    config.yml
    Code:
    handle-me: true
    date-format: HH:mm:ss
    message-format: '+iname: +message'
    me-format: '* +name +message'
    iname-format: '+prefix+name&f[+healthbar]+suffix+message'
    
    variables.yml
    Code:
    # iChat Variable Config
    # This is now the only method for defining variables
    users:
        LigerXT5:
            prefix: '&f[&2Admin&f]&2'
            suffix: '&2'
        MosDes:
            prefix: '&6[&dBan&2Hammer&6]&b'
            suffix: '&f'
        RIky_516:
            prefix: '&f[&6TigerMod&f]&4'
            suffix: '&6'
        ibmoodysniper:
            prefix: '&f[&0SniperMod&f]&0'
            suffix: '&f'
        soulspirtofawolf:
            prefix: '&5'
            suffix: '&f'
        haudini20020:
            prefix: '&4'
            suffix: '&f'
        StrikerX5:
            prefix: '&f[&5Player&f]&2'
            suffix: '&f'
        turttlez:
            prefix: '&f[&2No&40b&f]&f'
            suffix: '&f'
        killaj0069:
            prefix: '&f[&2fAiL&f]&f'
            suffix: '&f'
    #Note: No &9 for Chat Text. Hard to Read on Textures and Console.
    groups:
        GOD:
            name: GOD
            prefix: '&f[&6GOD&f]'
            suffix: '&f'
        admin:
            name: admin
            prefix: '&f[&2Admin&f]'
            suffix: '&f'
        Smoderator:
            name: Smoderator
            prefix: '&f[&eS&3Mod&f]'
            suffix: '&f'
        moderator:
            name: moderator
            prefix: '&f[&3Mod&f]'
            suffix: '&f'
        founder:
            name: founder
            prefix: '&f[&6Fndr&f]'
            suffix: '&f'
        donatorDiamond:
            name: donatorDiamond
            prefix: '&f[&bDD&f]'
            suffix: '&f'
        donator:
            name: donator
            prefix: '&f[&6D&f]'
            suffix: '&f'
        member:
            name: member
            prefix: '&f'
            suffix: '&f'
        MCBans:
            name: MCBans
            prefix: '&aMCBanned -> &f'
            suffix: '&9'
        Jailed:
            name: Jailed
            prefix: '&aJailed -> &f'
            suffix: '&9'
        default:
            name: default
            prefix: '&f[&aGUEST&f]'
            suffix: '&9'
    
    
     
  25. Offline

    coolo1

  26. Offline

    abbacab

    could I set permissions for level say: 10, 20, 30, 40, 50? giving each its own user group?
     
  27. Offline

    dj_rawscratch

    wait, what? wheres that, i dont see it, and i kinda/kinda not getting what your saying, thanks for replying though, if you could just make yourself a bit more clear, like an example? Thanks
     
  28. Offline

    coolo1

    Also, when I am not op I do not have access to most commands.
     
  29. Offline

    Liger_XT5

    At the beginning of each of your permissions, you are missing the "-".
    Your permissions should look as:
    groups:
    Group1:
    permissions:
    - Name.Of.Permission: true (or false)
    Simply just put a "-" followed by a space. Don't take out any extra spaces before the permissions. Should be a total of 12 spaces before the "-"

    Make sure your name is linked to the proper group.
    If you have your name set as Admin, the admin group has to have the permissions you need, or the group inherits the permissions from the previous group. Check my config of the permissions on how I have my name linked as Admin, and how the admin group is set up.
     
  30. Offline

    dj_rawscratch



    Wow. Thanks :D [cake] [cake][cake][cake][cake][cake][cake][cake][diamond][diamond][diamond][diamond][diamond][diamond][diamond][diamond][diamond][diamond][diamond]
     
  31. Offline

    Musaddict

    SpaceManiac I see that you were online today at 3:17 pm, so hopefully you will see this, lol. Just wondering... What's the progress of updating this to 1.1-R3? It worked fine for 1.0.1-R1, but now Im getting some strange aesthetic errors. Just hoping that since you are still an active member, if you are still gunna be working on this. I've grown weary of needing to switch dead perm plugins.
     

Share This Page