Inactive [ADMN/DEV] Permissions v2.7.4 (Phoenix) - DISCONTINUED! 3.0 has a new home!

Discussion in 'Inactive/Unsupported Plugins' started by TheYeti, Feb 25, 2011.

Thread Status:
Not open for further replies.
  1. Offline

    TheYeti

    Permissions 2.7.4 (Phoenix) - Now with AntiBuild built in!
    Download:
    Latest Stable: Full Zip | Jar Only
    Latest Dev Build: Full Zip | Jar Only
    Previous Versions: 2.7.3 (JAR) | 2.7.2 (JAR) | 2.7.1 (JAR) | 2.7 (JAR) | 2.6 (JAR) | 2.5.5 (JAR) | 2.5.4 (JAR) | 2.5.3 (JAR) | 2.5.2 (JAR) | 2.5.1 (JAR) | 2.5 (JAR) | 2.4 (JAR) | 2.3 (JAR) | 2.2 (JAR)

    Plugin Authors: How to hook into Permissions

    Permissions 2.x is being discontinued! 3.0 can be found HERE!!!


    I am discontinuing Permissions 2.x and leaving the project. Permissions is not going away though! Since 2.6 I have been working closely with another developer and added them to the team. For the past several version they have not only been assisting with 2.x but also doing a lot of the development of much anticipated 3.x. rcjrrjcr will be taking over as lead developer of Permissions from 3.x forward. I have full faith in them and after working closely with them on the development on the last few version and the next major version I feel that I am leaving this project in more than capable hands. I put way to much work into this project to just leave it with anyone, and this is one of the few programs that I am incredibly proud of.

    Many people will probably wonder why I am leaving again after taking over the project just a few months ago. I could quote drama and headaches, of which there were quite a few with this project. Unfortunately real life happens. Many people already know that I have been having medical issues here lately. Unfortunately while they have gotten better, they have not gone away. This coupled with other real life commitments, going to school full time, and starting up my own company, I am currently in the process of being laid off from work. At this point I have so much stuff going on in my life and am being pulled in so many directions that I am not able to get any work done on anything. This has lead to me missing commitments and letting people down on multiple things.

    Permissions is also a very high maintenance plugin that requires a lot of attention and time. Right now I am not able to devote that time and do not feel it is fair for me to try to continue to be the lead developer on it. I had originally thought that adding other members to the team would be helpful, but unfortunately this just lead to frustration for them and myself as I just was not able to commit to the project enough. Hence, 3.0 has been rewritten almost exclusively by rcjrrjcr with minimal contributions by myself.

    At this point I will be stepping away from the project to focus more on real life and to try to free up some time for other projects and to work with more individual like the wonderful HeroCraft Coding team to fulfill some commitments that I made to them a long time ago and sadly did not come through on. I feel that this is the best for all involved, both myself and the other Permissions developers, as well as the community who deserve someone who can contribute more time and attention to them and supporting them. I do not want to see Permissions end up like many other plugins with an absentee programmer and just slowly wasting away from a great plugin with a lot of potential to a headache with no support.

    I will still be active in the community, just not as much as not in the same way. I'm sure my server will be more than happy to have their head admin back and active again as well.

    Thank you and happy gaming.




    Changelog
    • 2.7.4
      • Added overload of has() and permissions() for plugin devs
    • 2.7.3
      • Fixed negate node add/remove bug.
    • 2.7.2
      • Fix for small subtle bug introduced in last minor version.
    • 2.7.1
      • Commit by DThielke to fix several bugs with programmatic modifications of user permissions.
    • 2.7
      • Further commits by rcjrrjcr
        • Removed negatedNode checks
        • Temp fix for NULL issue
        • WorldConfigurationModification to save only modified configs
        • Fix for cache problems
    • 2.6
      • Pulled in commits by rcjrrjcr
      • Fixed versioning. Last version should have technically been 2.6
      • Fixed invalid config file being written
      • Fixed erroneous conversion message.
    • 2.5.5
      • Updated to be compliant with CB600+
      • Further Maven Integration and Autobuilding
      • Better handling of configuration file errors.
        • If you do not have a world config file for the default world at startup it will now look for config.yml
        • If it cannot find that it will look for world.yml instead in case you named it that when that is not what is in level-name:
        • It will rewrite the config file to be the proper name. At this time it does not delete the old one though.
      • Removed defunct public abstract calls. If your not using the right one by now you should be shot anyway.
    • 2.5.4
        • Added Command aliases for perms and pr
        • Changed the way directories are handled.
        • Stopped it from creating an empty <world>.yml file in base directory
        • Moved project to using Maven.
    • 2.5.3
      • Change from File.pathSeparator to File.separator to fix multiworld perms
    • 2.5.2
      • Added more instructions to the included config file within the plugin
      • Added a check that will use the default world permissions if a world specific config file cannot be found.
      • Added a function to get only the group that a player is assigned to without checking for group inheritance.
      • Added a change to colorize() to fix it hopefully not adding an extra unneeded ascii character and thus creating a linebreak/color switch issue
      • Removed permissions.info as it was not needed and was a artifact of testing I was doing.
    • 2.5.1
      • Fixed a bug that could cause a group to be returned as null for getGroups()
    • 2.5
      • Added in AntiBuild functionality to Permissions
      • Minor code tweaks
      • Added getGroups(world, player) to PermissionHandler so that plugins can call it to get all of a users groups
      • Fixed the inability to use the permissions -reload all command from within the console. I still need to do some more work on this as it doesn't seem to like to accept anything other than all from console.
    • 2.4
      • Refactored namespaces to keep in line with Java & Bukkit policy
        • This was cancelled as it ended up being not needed
      • Fixed setupPermissions()
    • 2.3
      • Undid removal of some code that I had overzealously purged during cleanup
      • Merged in last of Nijikokun's changes
      • Re-ordered the main class to attempt to fix the problems with Plugin API
    • 2.2
      • Developer change
      • Fixed reloading of configuration files
      • Moved commands to registering with plugin.yml
      • Commands now use onCommand instead of onPlayerCommand
      • Command is now /permissions instead of /pr
    [/SPOILER]
     
    mruczek, kahlilnc, Pii and 58 others like this.
  2. Offline

    armoreddice

    I know several people have brought up the issue where there is nothing in the permissions.yml and that it doesnt appear in the right place when you restart the server. What exactly am I supposto copy and paste into the yml?
     
  3. Offline

    zakcng

    Code:
    # System is no longer used, but may become used in the future
    # Copies is for multiple-world support
    #   Put the name of the world you wish for it to be a clone of, otherwise leave it empty.
    #   If this file is for your default world (the one in server.properties) then you must
    #   leave copies blank.
    #  Example: copies: Derp    -  This will clone the permissions of the world Derp
    #
    # Make sure to rename this file to the name of the world that is in sever.properties under
    # level-name.  So if it is level-name: world  then this should be world.yml and in the
    # plugins/Permissions directory (ie. plugins/Permissions/world.yml)
    #
    # NOTE: Do not use tabs while editing this document.  Use only spaces.  A good way to avoid
    # doing this is to use Notepad++ and replace the tab with 4 spaces.
    plugin:
        permissions:
            system: default
            copies:
    
    ##
    # AntiBuild is included with this.  To disable a group from being able to build then
    # set the build: flag to false (build: false).  If you want a group to be able to build
    # then set it to true.
    ##
    # Groups can contain inheritance.
    #   To make a group inherit the permissions from another
    #   group simply place the groups name in the "inheritance:" like so:
    #
    #   Example:
    #       inheritance:
    #           - Default
    ##
    #   All permissions including the asterisks must be placed in single quotes.
    #   like so:
    #
    #       - 'foo.bar'
    #
    #   Otherwise errors will happen!
    ##
    #   Globalized Permission settings:
    #
    #       If a permission contains periods (.) you can denote a globalized parameter:
    #
    #           - 'foo.*'
    #
    #       This will allow you to use all general commands.
    #
    ##
    #   Single Asterisk denotes all commands:
    #
    #       - '*'
    #   If you give a group this permissions, do not have the group inherit any permissions
    #   from other groups.  Any users assigned to this group should NOT be given any additional
    #   permissions either.
    ##
    #   To exempt a node use the - prefix like so:
    #       - '-foo.bar'
    ##
    #   prefix: and suffix: do not do anything on their own.  You need another outside plugin
    #   such as iChat or HeroChat in order for these to do anything.
    groups:
        Default:
            default: true
            info:
                prefix: ''
                suffix: ''
                build: true
            inheritance:
            permissions:
                - 'foo.bar'
        Moderator:
            default: false
            info:
                prefix: ''
                suffix: ''
                build: true
            inheritance:
                - Default
            permissions:
                - 'bar.foo'
        Admins:
            default: false
            info:
                prefix: ''
                suffix: ''
                build: true
            inheritance:
            permissions:
                - '*'
    
    ##
    # Users denote which users are included in which group.
    # TheNo1Yeti is in the Admin group
    # Herpina is a member of the Moderator group but also has access
    # to the herp.derp permissions
    # Derpina is a member of the admin group but does not have access
    # to the derp.derp permission node
    # Users can also have a prefix and suffix as seen with Herpina
    ##
    users:
        abc111:
            group: Admins
            permissions:
                - '*'
        Herpina:
            group: Moderator
            info:
                prefix: 'Moo'
                suffix: 'Cow'
            permissions:
                - 'herp.derp'
        Derpina:
            group: Admins
            permissions:
                - '-derp.derp'
     
  4. Offline

    lycano

    @zakcng:
    Try this one (open)

    Code:
    plugin:
        permissions:
            system: default
            copies:
    groups:
        Default:
            default: true
            info:
                prefix: ''
                suffix: ''
                build: true
            inheritance:
            permissions:
        Moderator:
            default: false
            info:
                prefix: ''
                suffix: ''
                build: true
            inheritance:
            permissions:
        Admins:
            default: false
            info:
                prefix: ''
                suffix: ''
                build: true
            inheritance:
            permissions:
            - '*'
    users:
        abc111:
            group: Admins
            permissions:
    


    You dont have to add * to a users permission when the group Admins already included *

    Do you really want that the Default group can build? All users not listed are automatically added to the default group (default: true). Furthermore no one should inherit the default group because of that reason ^^
     
  5. Offline

    Celtic Minstrel

    Nothing wrong with inheriting from the default group.
     
  6. Offline

    lycano

    I dont say it is wrong. But if you inherit the group with default: true into Moderator then you'll end up in messing around with your permission setup. Default is a user that has no group assigned. Why should a Moderator that is probably assigned to at least one user inherit this group? You'll more likely do things like "add stuff to default and disallow other stuff for moderator that default has" ... failed. Create a group for safety permissions and do not assign it to any user. Use this group for inheritance as Safepermissions and you are fine.

    If a new user now joins your server (probably someone you dont know) you would normaly dont want that he can build or do anything. Until he is assigned to a known group like a group that inherit SafePermissions he can do stuff not before. If group with default:true set has the same permission like any other user that is known to the server .. youll more likely scream if a griefer joins your server.
     
  7. Offline

    Celtic Minstrel

    Normally, whatever permissions you give default are permissions you want everyone to have. When you consider that, it makes perfect sense to make every group inherit from Default (unless it inherits from a different group instead). Well, apart from that supposed glitch from having duplicate entries.
     
  8. Offline

    lycano

    I hope you mean the group named Default and not the one who is set to default:true ^^ It doesn't make sense to use the "Default" group as a group where any unassigned user is in because of security reasons (see my example above).

    _If_ I consider but i don't agree because with this setup Permissions will only prevent users from accessing other plugins. The option default: true (assign unassigned users to that group not all!) build: true (prevent users from building) Is essentially a light Anti-Grief option.

    If a Griefer joins you have still time to watch what he is doing IF you use the group named Default as default:true and build:false.

    Thats why i said setup a trusted group that inherits SafePermissions.

    You see? It doesn't makes sense to use permissions that way. Maybe if you dont care about griefers .. but if you meet one seeing your buildings destroyed after minutes and dont have a backup you'll think about what i said.
     
  9. Offline

    Maxis010

    Has it occurred to you that perhaps some people don't rely on permissions as an Anti-Grief
    Sorry to advertise another plugin but I use GuestPrev and permissions, default group has build: true BUT if they aren't authorised by GuestPrev then their options are limited to walking around, interacting with doors, using buttons and switches
    This way I only need to add admins to the permissions file and I can use /guestprev add and /guestprev remove to authorise and de-authorise without a shutdown
     
  10. Offline

    tahu

    Code:
    17:48:27 [SEVERE] Could not load 'plugins\Permissions.jar' in folder 'plugins
    
    java.lang.reflect.InvocationTargetException
            at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Meth
    
            at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Sour
    
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown
    rce)
            at java.lang.reflect.Constructor.newInstance(Unknown Source)
            at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoade
    ava:136)
            at org.bukkit.plugin.SimplePluginManager.loadPlugin(SimplePluginManag
    java:158)
            at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginMana
    .java:106)
            at org.bukkit.craftbukkit.CraftServer.loadPlugins(CraftServer.java:84
            at org.bukkit.craftbukkit.CraftServer.reload(CraftServer.java:285)
            at org.bukkit.command.SimpleCommandMap$ReloadCommand.execute(SimpleCo
    ndMap.java:196)
            at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java
    )
            at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.jav
    46)
            at net.minecraft.server.MinecraftServer.b(MinecraftServer.java:391)
            at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:377)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:283)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:375)
    Caused by: while scanning for the next token
    found character         '\t' that cannot start any token
     in "<reader>", line 58, column 1:
                group: ad
        ^
    
            at org.yaml.snakeyaml.scanner.ScannerImpl.fetchMoreTokens(ScannerImpl
    va:360)
            at org.yaml.snakeyaml.scanner.ScannerImpl.checkToken(ScannerImpl.java
    3)
            at org.yaml.snakeyaml.parser.ParserImpl$ParseBlockMappingValue.produc
    arserImpl.java:592)
            at org.yaml.snakeyaml.parser.ParserImpl.peekEvent(ParserImpl.java:163
            at org.yaml.snakeyaml.parser.ParserImpl.checkEvent(ParserImpl.java:14
            at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:132
            at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.j
    :230)
            at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:160
            at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.j
    :230)
            at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:160
            at org.yaml.snakeyaml.composer.Composer.composeDocument(Composer.java
    2)
            at org.yaml.snakeyaml.composer.Composer.getSingleNode(Composer.java:1
    
            at org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseC
    tructor.java:124)
            at org.yaml.snakeyaml.Yaml.load(Yaml.java:264)
            at com.nijiko.configuration.NotNullConfiguration.load(NotNullConfigur
    on.java:58)
            at com.nijikokun.bukkit.Permissions.Permissions.<init>(Permissions.ja
    132)
            ... 16 more 
    Thanks in advance ;)

    EDIT: OOPS i found tabs!!! solved... sorry everybody for me being [zombie]
     
  11. Offline

    lycano

    It has but i think this isnt effective and if you tell me that in this context i would say you are lazy to do it right or you dont care. Whatever it is im a perfectionist and i dont trust functions i dont know. Imagine if you want to deactivate this guestprev plugin or it would not load properly because of an update or you have found another that does it better.

    If you would have done it right in the first place you dont have to rethink your permission design in that matter. Thinking of the worst case guestprev is failing then what? You dont have a safe net everyone can do what the default:true group can do ... without your knowledge e.g. you're not at home ... simply you cannot act directly IF it happens then what?

    Im looking ahead not only one step forward.
     
  12. Offline

    gilgatex

    It would be very useful if we could exclude commands from plugins that don't 'use' permissions. Just the commands themselves. Like:

    - '-/auction'
     
  13. Offline

    lycano

    hmm ... if the plugin isnt asking for permission you have to listen on command PLAYER_COMMAND_PREPROCESS on High. Additionally permissions has to know what the plugin will do to overwrite it... Inverting this: Listen on PLAYER_COMMAND_PREPROCESS on Low and hope that the Plugin that is not supporting permissions will check for event.isCanceled(). As far as i know many "fast written" plugins are not checking for it so this will then be executed regardless what Permissions would say.

    But thats my opinion im not the maintainer, maybe they have other thoughts about it.
     
  14. Offline

    Maxis010

    Seeing as Permissions fails more often than GuestPrev, usually due to permission files being blanked by the plugin then I don't see Permissions as an optimal system to handle it, on top of that I do have a fallback from GuestPrev, it's not perfect but in the event of a total CraftBukkit failure this fallback is still an option
    Regardless of that fact, don't start calling people lazy just because they take an alternative method to yours, to each their own, your method works, so does mine
     
  15. Offline

    deluxxee

    pls Group Invite Command for 1.5
     
  16. Offline

    Godofallcows

    I updated from 670 to 684 and permissions stopped working.

    I downgraded it to 677 and 670 again and neither of them work either?
     
  17. Offline

    Celtic Minstrel

    No, I mean the group with default:true. The only permissions you would give that group are the permissions you want everyone on the server to have... so, it's perfectly logical to have the other groups inherit from it.
     
  18. Offline

    DaffyDuckinator

    nice work but gets kinda hard to add each plugins permissions code thing (e.g. foo.bar) I dont know how to code, but how easy would it be to make a permissions manager that automatically added each possible permission code thing to a list which you can easily add to any group or user by just a few clicks. i know your probably busy with the coding and the shoulder pain but it would be really nice to consider that for me

    p.s. get well soon
     
  19. Offline

    Taranis01

    I have a problem with the settings of the server i'm hiring.
    The "level.dat" and the "region" folder are in the same folder as the "craftbukkit.jar" and the "server.properties" (and so on)!
    The "level-name=" in the server.properties is blank (and if i try to change it, it rechanges).
    Is there a way get Permissions work anyway?

    thanks for this awesome plugin

    /edit: solved!
     
  20. Offline

    Broekan

    Hello :)
    I have been through hell to get permissions working on my server.

    but i think its finally done.

    But i have a question, I cant seem to get it right.

    If I put the * under admin permissions, does it count for Default or Everything including my plugins?
     
  21. Offline

    Taranis01

    @Broekan If u put the '*' under admin the admin have the rights for all commands (including plugincommands)
     
  22. Offline

    MagicHereos

    How can I give somebody /tp and /whitelist commands?;>
     
  23. Offline

    Psycho Robot

    Each group definition has a "build:true/false" line on it. make sure that its true where appropriate

    There are a large amount of plugins which incorporate teleport. Essentials is a big one, another is DefaultCommands. As far as in-game whitelist management, this seems to be what you're looking for.
     
  24. Offline

    Ambedrake

    Was wondering how hard it would be to have permissions use an SQL DB instead of a file. This idea is due to the fact we use a forum system to maintain a list of players on our servers and to make an automated link between the two and allowing the forum admins to remotely change a persons group would be nice and simple. If there is a plugin that fits this gap between SQL and permissions please tell me as I've been looking and haven't found any yet >.<

    The idea is :

    Guests/Unregistered users - No build rights
    Tier 1/Registered - Basic rights
    Tier 2/Contributors - Added commands

    etc...

    Anyways just an idea ^_^ if anyone is interested I am using PHPBB since I am used to writing mods for it, but as the PHP file write is annoying I prefer to run as much as possible via DB's
     
  25. Offline

    Broekan

    Fantastic :D

    Thank you for clearing that up :)
     
  26. Offline

    icomeinpieces

    awesome plugin thnx for your efforts TheYeti, sorry to hear your not doing well, get well soon
     
  27. Offline

    Seven50six6

    This compatible with the new update?
     
  28. Offline

    fightknight

    ok not 100% what fixed my problem, it was one of 2 things, maybe someone can tell me for sure, I just want to get back to setting up my server :D LOL but I can now build and destroy blocks. I installed essentials and *poof* I was destroying and building with blocks! I did notice after installing essentials that a radius around the spawn point seems to be protected, I'm not sure if I was always trying to remove and build in that radius b4 installing essentials or not.
     
  29. Offline

    Zilerations

    To Help People Out ill Put My Permssions On
    Code:
    plugin:
        permissions:
            system: default
            copies: null
    groups:
        Guest:
            default: true
            info:
                prefix: '&7'
                suffix: ''
                build: false
            inheritance: null
            permissions:
            - essentials.rules
            - essentials.balance
            - essentials.help
            - essentials.motd
            - commandSigns.use
            - sortal.warp
            - essentials.sell
            - iJobs.user.menu
            - iJobs.user.join
            - iJobs.user.browse
            - iJobs.user.payday
            - iJobs.user.info
            - BetterShop.user
            - essentials.spawn
            - xauth.admin.changepw
        Trusted:
            default: false
            info:
                prefix: '&2'
                suffix: ''
                build: true
            inheritance:
            - Default
            permissions:
            - essentials.help
            - essentials.sethome
            - essentials.warp
            - essentials.home
            - essentials.sell
            - essentials.balance
            - essentials.rules
            - essentials.motd
            - essentials.afk
            - essentials.msg
            - essentials.mail
            - essentials.mail.send
            - essentials.list
            - essentials.tpa
            - essentials.tpaccept
            - essentials.tpdeny
            - iJobs.user.menu
            - iJobs.user.join
            - iJobs.user.browse
            - iJobs.user.payday
            - iJobs.user.info
            - magiccarpet.mc
            - honeypot.create
            - commandSigns.use
            - multichannel.user
            - slots.buy
            - slots.create
            - sortal.warp
            - lockette.create
            - xauth.admin.changepw
            - iConomyChestShop.shop.create
            - iConomyChestShop.shop.buy
            - iConomyChestShop.shop.sell
            - iConomyChestShop.command.iteminfo
        VIP:
            default: false
            info:
                prefix: '&6'
                suffix: ''
                build: true
            inheritance:
            - Trusted
            permissions:
            - essentials.help
            - essentials.sethome
            - essentials.warp
            - essentials.home
            - essentials.sell
            - essentials.balance
            - essentials.rules
            - essentials.motd
            - essentials.afk
            - essentials.msg
            - essentials.mail
            - essentials.mail.send
            - essentials.list
            - essentials.tpa
            - essentials.tpaccept
            - essentials.tpdeny
            - iJobs.user.menu
            - iJobs.user.join
            - iJobs.user.browse
            - iJobs.user.payday
            - iJobs.user.info
            - magiccarpet.mc
            - honeypot.create
            - commandSigns.use
            - multichannel.user
            - slots.buy
            - slots.create
            - sortal.warp
            - iConomyChestShop.shop.create
            - iConomyChestShop.shop.buy
            - iConomyChestShop.shop.sell
            - iConomyChestShop.command.iteminfo
            - xauth.admin.changepw
        Donator:
            default: false
            info:
                prefix: '&d'
                suffix: ''
                build: true
            inheritance:
            - Trusted
            permissions:
            - essentials.help
            - essentials.sethome
            - essentials.warp
            - essentials.home
            - essentials.sell
            - essentials.balance
            - essentials.rules
            - essentials.motd
            - essentials.afk
            - essentials.msg
            - essentials.mail
            - essentials.mail.send
            - essentials.list
            - essentials.tpa
            - essentials.tpaccept
            - essentials.tpdeny
            - iJobs.user.menu
            - iJobs.user.join
            - iJobs.user.browse
            - iJobs.user.payday
            - iJobs.user.info
            - magiccarpet.mc
            - honeypot.create
            - commandSigns.use
            - multichannel.user
            - slots.buy
            - slots.create
            - sortal.warp
            - essentials.item
            - xauth.admin.changepw
            - iConomyChestShop.shop.create
            - iConomyChestShop.shop.buy
            - iConomyChestShop.shop.sell
            - iConomyChestShop.command.iteminfo
        Mod:
            default: false
            info:
                prefix: '&b'
                suffix: ''
                build: true
            inheritance:
            - Trusted
            permissions:
            - essentials.item
            - essentials.kit
            - worldedit.wand
            - worldedit.region.set
            - worldedit.history.undo
            - magiccarpet.mc
            - commandSigns.create
            - nocheat.speedhack
            - nocheat.moving
            - nocheat.airbuild
            - nocheat.bedteleport
            - nocheat.notify
            - nocheat.flying
            - multichannel.admin
            - bar.foo
            - permissions.group
            - essentials.time
            - essentials.unlimited
            - essentials.ban
            - essentials.unban
            - essentials.kick
            - essentials.mute
            - VIP.add
            - VIP.remove
            - xauth.admin.changepw
            - iConomyChestShop.shop.create
            - iConomyChestShop.shop.buy
            - iConomyChestShop.shop.sell
            - iConomyChestShop.command.iteminfo
        Admin:
            default: false
            info:
                prefix: '&4'
                suffix: ''
                build: true
            inheritance: null
            permissions:
            - null
            - '*'
        Owner:
            default: false
            info:
                prefix: '&8'
                suffix: ''
                build: true
            inheritance: null
            permissions:
            - nocheat.speedhack
            - nocheat.moving
            - nocheat.airbuild
            - nocheat.bedteleport
            - nocheat.notify
            - nocheat.flying
            - '*'
    users:
        Venom:
            group: Owner
            info:
                prefix: ''
                suffix: ''
            permissions: null
        Herpina:
            group: Moderator
            info:
                prefix: Moo
                suffix: Cow
            permissions: null
        CjJcPro:
            group: VIP
            permissions:
            - essentials.item
            - essentials.god
        Player_9000:
            group: Trusted
        Fubie_:
            group: Admin
        Player:
            group: Mod
        JaggerNotchas:
            group: Admin
        Fizzy:
            group: Trusted
            permssions: null
        Damon:
            group: Trusted
        HPOTTEST:
            group: Trusted
    
     
  30. Offline

    fightknight

    whats the / command to reload permissions?
     
  31. Offline

    Conan1981

    u wont get that running without even reading the install quote in the description or the rename me file ... dont be lazy on that ....
     
Thread Status:
Not open for further replies.

Share This Page