Inactive [ADMN/DEV] PermissionsEx (PEX) v1.19.5 - Tomorrow is Today! [1.4.6-R0.1]

Discussion in 'Inactive/Unsupported Plugins' started by t3hk0d3, May 21, 2011.

  1. Offline


    Version: 1.19.5


    PermissionsEx (PEX) is a new permissions plugin, based on Permissions ideas and supports all of its features. But PEX is more! It offers different backends, powerful ingame management, fine grained restrictions for world modification.


    Current features
    1. Bukkit Permissions (SuperPerms) compatible.
    2. Several backend support. Currently bundled backends is File (YAML) and SQL (MySQL, SQLite). Also it's possible to add your own.
    3. YAML backend, with new, fully rethinked, config schema. Now all user, groups and their permissions are stored in one file - permission.yml. BTW file name is adjustable too.
    4. SQL backend, most delicious. Currently MySQL and SQLite supported, but other DB (like Postgre) are possible too. PEX deploys the DB scheme (tables and initial data) automatically. This means, that you only need to provide data on how to connect to the db, everything else PEX will handle by itself.
    5. Flexible architecture and API - you can change a lot programmatically.
    6. Compatibility layer with TheYeti's Permissions (2.7.4) (as a separate part of the plugin). In most cases plugins, which use Permissions, will alsowork with PEX also.
    7. Rich chat/console command interface. You can do almost everything ingame. Command list below.
    8. Modifyworld - Embedded restrictions mechanism (we call it "modifyworld"), which provides the possibility to control players abilities, such as destroying/placing blocks, riding carts/boats or even getting spotted by mobs and much more. Disabled by default.
    9. Multigroup inheritance. User, as well as Group, can be member of several groups. And inherit their permissions, options and prefix/suffix.
    10. Permissions based upon Regular Expressions. This mean you can use regular expressions. Example: modifyworld.blocks.(destroy|place).(3|12) - this permission allow place or destroy only sand (12) or dirt (3) blocks. There is still limitation on dot usage in your regexps - dots are escaped by default.
    11. Multiworld permissions. Just don't specify world and permission would work in any world.
    12. Multiworld inheritance. You can inherit different groups in different worlds.
    13. Easy migration from Permissions 2.x. Converter for both YAML and SQL are embedded into PermissionsCompat. Just use simple instruction.
    14. Perfomance friendly. Low-level caching helps alot when you have 100+ online users :)
    15. Promotional/Demotional system. You can assign ranks to groups and promote/demote users to higher/lower ranked group.
    16. World-inheritance - permissions/option of one world can be inherited by another world.
    17. Timed Permissions - you can give user permission only for some amount of time.
    18. Chat Manager - small chat plugin, bundled with PEX. With prefixes/suffiex and colors. Check wiki for more details.


    Basic setup tutorial (Thanks to lycano)

    Nice tutorial made by Bennetman

    Stable version

    Development version (mostly stable) - always lastest dev build.



    Maven Repository

    Join us on #permissionsex, Feel free to ask any related questions.

    Tools !NEW!
    Pex Auto-Setup Tool - MySQL and FlatFile !

    Show Changelog (open)
    Proper intervals for timed commands (both group/permissions management), without pesky seconds calculations (like /pex user t3hk0d3 timed add cool.permission 10days)
    1.4.6 compatibility.

    Built for Bukkit 1.4.2-R0.1
    Added inventory permissions (modifyworld.items.put/take.<item>.of.<chest>)
    Added item hold permission (modifyworld.items.hold.<item>)
    Sdded monster egg spawn permission (modifyworld.spawn.<creature>)
    Few other minor fixes
    Modifyworld improvements (configurable messages, now independent from PEX)
    /pex help command
    Minor improvements and bugfixes
    New modifyworld permissions
    Some bugfixes
    Bugfix release
    Bukkit R6 compatible.
    Several bugfixes!
    Permissions now case-insensetive.
    Users logging and cleanup feature.
    Non-inheriting nodes feature.
    Several Bugfixes.
    PermissionsCompat is finally remove from default bundle.
    User/group specific management permissions (
    Fixed some superperms compatibility issues
    Fixed several bugs
    SuperPerms compatbility bridge were rewritten - no lags anymore and now with debug output (now you can view superperms checks).
    Numerous of bugs were fixed (Thanks you guys for reporting them)
    Modifyworld were improved (modifyworld.item.use)
    Compatiblity for 1317+
    Fixed perfomance issues with SuperPerms (if you still experience they try to disable "raw-permissions" in config.yml)
    Fixed issue with prefix inheritance
    Improved Options mechanism.
    Auto saving new users feature, disabled by default.
    SuperPerms bridge improved - more permissions supported by wildcards.
    File backend dumping now fully functional. SQL dumping is still bogus (do not dump world-specific inheritance and prefixes), will be fixed soon.
    Many bugfixes and minor improvements.
    Superperms (BukkitPerms) support
    Multiworld inheritance and prefixes/suffixes
    Groups weighting
    ChatManager, chat plugin which bundled with PEX.
    Modifyworld now separate plugin, but still bundled with PEX.
    API changed slightly, CustomEvents (PermissionsEntityEvent, PermissionsSystemEvent) introduced.
    Many lesser improvements and tons of bugfixes.
    API get slightly improved
    Ranking ladders.
    User/group name case-insensetivity.
    Timed permissions.
    Modifyworld rules are get improved.
    Tons of minor improvements and bugfixes.
    Many bugfixes and improvements.
    MySQL connection stability improved - reconnection mechanism.
    Promotional/Demotional system.
    Perfomance improvement, with new low-level caching system (thx Joy)
    Modifyworld improved.
    Many lesser improvements and bugfixes.
    New p2compat backend, for easy migration from Permissions 2.x to PEX.
    Users/Groups dumping (pex dump <backend> <file>).
    New commands pex promote/demote. Actually this is just aliases for "pex user group set/remove"
    Few bugfixes.
    Players now can be informed about changes (has been added to group, changed permission/option). Disabled by default - set "permissions.informplayers.changes" to "true"
    Config node "permissions.verbose", which responsible for player informing about modifyworld restrictions has been renamed to "permissions.infromplayers.modifyworld".
    Autocomplete has been improved.
    New command "pex config <node> [value]". This command help to manipulate configuration file (config.yml) from console/chat interface.
    Many bugfixes.
    Autocomplete for users (taken from registred users and online users) and groups names.
    New command for user removing (pex user <user> delete)
    Fixed several nasty bugs. Thanks for bugreports!
    Compatibility layer loading order issue fixed. Now most of plugins should work.
    Tested with new CB 803 build.
    Regular expression permissions support.
    Newer permissions now added above (bugfix).
    Several bugfixes.
    Initial public release.
    BRampersad, grid21, MrRazull and 71 others like this.
  2. Offline


    I setup the permiEX, but No one has the permissions to Set a home go to spawn or Buy from the chest shops can someone help and give me the permissions nodes or tell me what to do please?
  3. Offline


    How would i block eye of ender's from being placed? they are kind of lagging my server.
  4. Add the nodes to the permissions file to the groups that you want to have access to them? if you have already done that, lets see your permissions.

    Look at modifyworld, in particular, the blocks place node.

    I'm afraid I'm not seeing anything on your message. Try putting them on pastie and linking to it here

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: Sep 9, 2018
  5. Offline


    Hello, I just have started my server and I am having a HUGE problem I can't seem to resolve (It's not huge, but I just need a bit of help). Below is a link to pastebin and my permissions (Just the start). I know it isn't formatted correctly, but I would like help with it.


    Oh yeah, here's the link:
  6. Thank you, that pastebin link is perfect.


    Ok, according to the output of ...

    Line 102 is off (you are missing a space to line it up with the rest of the group)
    Line 104 suffers from the same problem.

    Fix those two things and it validates as valid YAML. :)
  7. Offline


  8. Offline


    I have a question, namely how to display HealthBar at ChatManager? can i have any chance? :)
  9. Offline


    Here, I think:
  10. Offline


    I actuay just fixed the permissions so I should be good right now:)
  11. Offline


    Maybe you can add permissions per world. It would be great. And with a global permissions file to for the ones who don't want it.
  12. Offline


    Hello, I would like to know why everyone that joins my server can do "/spawn" Or go to a warp? If someone can plz send me the permissions for it... ty
  13. Offline


    i know code is incorrect but you will get the idea of what im asking


    group noob:
    - -~command.two
    - command.two

    would give

    - -command.two

    but wud a group that inherits its comands have

    - command.two

    because doesnt (~) mean that the permission is never inherited?
    and is it
    - -~permission or
    - ~-permission?
    i assume for 'yes' nodes its

    - ~permission but i am confused as for the 'not' nodes

    thanks in advance

    also on a sidenote how does timed permissions work? does it work with groups as well as individual permissions? is there a way to set it to calibrate with server time or website time or anything as opposed to just time from the permission being added?

    oh and one suggestion;
    the ability to add perks which just have a few select permissions which can be easily added to a player. such as the /home perk which has /sethome and /home perks and certain cooldown times from a different plugin etc. etc. and again allow perks to be just like perms and all and give them the ability to work with time and stuff. i will probably end up doing this with groups anyway but it would be nice to have a seperate feature for this.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: Sep 9, 2018
  14. Offline


    I got a wierd error!
    Everything works fine untill someone login on my server. When someone login my server get 1000 of errors and crashes! Why??
  15. Offline


    I think you should give the Chatter instead of Chat Manager. It's better. Here, you can use the options defined in pex.
    And i think prefix and suffix should be in options.
  16. Offline


    Not working on R5?
  17. Offline


    Is there somebody who can offer some guidance with this issue?
    Thanks in advance!
  18. Offline


    So how do I set up a permission in default for a single group.
  19. hello, i really like this plugin.
    i have a question:
    how can i set i one command a player in a group in all the worlds?
    i think a command like:
    pex user <user> group set <group> *
    * = all worlds

    sorry for my bad english

    EDIT: the command works but i cant edit in my world
    check my config:
  20. Offline


    did that but it still just had my name oh but should i modify the chatmanager config.yml
  21. Got it.


    Well, what you posted has some errors in it according to the parser at

    The group default is missing it's closing quote on the prefix
    The group default negation node for modifyworld needs a space between the dash and the modifyworld keyword

    What is probably happening is that PEX is trying to load the file, then the YAML parser finds the errors and stops loading, thereby killing off all permissions.

    BTW, the owner group, you have assigned it *. That's everything already, you don't need the other nodes in the group, they are included with *.

    Multiworld, global and world specific support is already in PEX.

    If you are using PEX, there are a few possibilities:

    1. You gave them the nodes by accident. :)
    2. Your have a typo in your permissions, causing PEX to fail to start and the plugins are defaulting to some kind of fallback
    3. Everyone that has access is in the ops.txt
    Those are the three I can think of off the top of my head.

    Otherwise, there isn't enough info. Multiple plugins offer a warp or spawn command.

    1.18, no. The current dev builds of 1.19 do work under R5

    Not sure I fully understand the question.

    Looking at your config, you have some misconfigurations. :)

    First off, - -'*' isn't needed (and I don't think works). PEX assumes that all permissions are false to begin with, so if you don't assign a group any permissions, it shouldn't be able to do anything at all, unless the plugin automatically gives everyone permissions, in which case you would need to negate just those nodes.

    Second, your admin group has * assigned at a global level. You don't need the separate world specific sections, it already has everything from the *.

    Gah. Quite the setup there. Going to have to think on this one and do some experimenting later tonight. :p

    EDIT: I thought I had an idea on a way to do this, but then upon checking, I realized that it's not possible right now with the way PEX works (or at least I can't think of a way).

    The problem is that you are looking at setting world-specific groups within a group, which PEX doesn't handle. You can set world-specific groups at a user level, and world specific permissions within a group, but not world specific groups at a group level. (PEX doesn't support nested groups I guess one could say).

    If it did, I'd think that something like this would be viable:

            default: true
            inheritance: null
            prefix: '&6(&7Guest&6)&4 '
                rank: '1000'
                rank-ladder: User
            default: false
            - Guest
            prefix: '&6(&7Member&6)&4 '
                rank: '900'
                rank-ladder: User
                    - Member
                    - Survivor
            - -modifyworld.items.have.383.(50|56|58|61)
    How about it t3hk0d3, might this be something to add as a feature request on github?

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: Sep 9, 2018
    Lemonhands likes this.

  22. thanks for your help i changed my permissions.yml a bit:
    but i didn't change the

    1. griefer:
    2. - -'*'

    cause i do not want griefers from doing anything at all

    but i have still the same problem: i have set myself as an admin in world '*' (i think this means all worlds) but i cant edit any world. can any1 help me?

    sorry for my bad english

    edit: i found out that i can use the command
    pex user <user> group set <group>
    ] without setting a world. that makes it count on all worlds no more help needed!!
  23. Offline



    thank ya! i played with permissions a long time no one did work only this :'( its so beatyfull :)

    [creeper][glass] :oops: [wood]
    [mossy][wood][workbench][air] [wood] [pig] :'(<bye pig [pig]< roink? PermissionsEx great permissions plugin!
  24. Offline


    Hi! I have a problem since the begging...
    1) In the folder "plugins" after running server, i have only 2 folders: PermissionsEx and ChatManager. Normal for the missing of folder Modifyworld ?
    2) In the cmd window, i have this : [Modifyworld] Loading; [Modifyworld] disabled. check config.yml!
    3) Finally, in game i can't change the group of a player, i have the message "Sorry you don't have enough permissions"...

    For the 1), i try to create the folder with the config.yml like yours in the video. I have the same problem...
    For 2) and 3), i don't know what can i do...

    If someone know what can i do... :)

  25. Offline


    Thanks a lot, its working great now, also I didn't put those mistakes in, all I did was change two of the names, the rest was what Bennet man said to download
  26. Offline


    How to add Health Bar to ChatManager ? :)
  27. Offline


    We tried this, without a tutorial ,we know java and stuff but we did read wiki
    got over 80 000 errors in 3-5mins
  28. Offline


    How do I set per world permissions?
  29. Offline


    The Chat Prefix Wont Work For Me And I Have ChatManager Installed Anyone Know Why?
  30. Offline


    I was wondering where exactly I put the modifyworld: true node in the PermissionsEX config file. Wherever I put it, ModifyWorld enables but the -modifyworld.* node does not work

      log-players: true
          file: permissions.yml
      backend: file
        parent-nodes: true
        enable: true
        strict-mode: false
      createUserRecords: true
      allowOps: false
      debug: false
      basedir: plugins/PermissionsEx
  31. The example in the first post has an example of multiworld/world specific permissions under the admin group.

    Is it enabled? By default, it is not. Check the config.yml to verify it's turned on. If it is, we need to see how your prefixes and suffixes are defined in your permissions

    You don't. :)

    To enable modifyworld, you just have to enable it in the modifyworld config.yml. If it's not working, we need to see your permissions.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
    Last edited by a moderator: Sep 9, 2018

Share This Page