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

    t3hk0d3

    [​IMG]
    Version: 1.19.5

    PLEASE USE BUKKIT-DEV FORUM FOR DISCUSSION/HELP
    http://dev.bukkit.org/server-mods/permissionsex/
    THANKS IN ADVANCE.

    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.

    [​IMG]

    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.


    Documentation
    Wiki

    Basic setup tutorial (Thanks to lycano)

    Nice tutorial made by Bennetman


    Download
    Stable version

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

    Sources
    https://github.com/PEXPlugins

    Builds
    http://webbukkit.org:8080/

    Maven Repository
    http://repo.tehkode.ru/browse/ru.tehkode

    IRC
    Join us on #permissionsex, irc.esper.net. Feel free to ask any related questions.

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


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


    v1.19.4
    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
    v.1.19.3
    Modifyworld improvements (configurable messages, now independent from PEX)
    /pex help command
    Minor improvements and bugfixes
    v.1.19.2
    New modifyworld permissions
    Some bugfixes
    v.1.19.1
    Bugfix release
    v1.19
    Bukkit R6 compatible.
    Several bugfixes!
    Permissions now case-insensetive.
    v1.18
    Users logging and cleanup feature.
    Non-inheriting nodes feature.
    Several Bugfixes.
    PermissionsCompat is finally remove from default bundle.
    v1.17
    User/group specific management permissions (permissions.manage.group.Admin)
    Fixed some superperms compatibility issues
    Fixed several bugs
    v1.16
    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)
    v1.15
    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
    v1.14
    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.
    v1.13
    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.
    v1.12
    API get slightly improved
    Ranking ladders.
    User/group name case-insensetivity.
    World-inheritance.
    Timed permissions.
    Modifyworld rules are get improved.
    Tons of minor improvements and bugfixes.
    v1.11
    Many bugfixes and improvements.
    MySQL connection stability improved - reconnection mechanism.
    v1.10
    Promotional/Demotional system.
    Perfomance improvement, with new low-level caching system (thx Joy)
    Modifyworld improved.
    Many lesser improvements and bugfixes.
    v1.06
    New p2compat backend, for easy migration from Permissions 2.x to PEX.
    v1.05
    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.
    v1.04
    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.
    v1.03
    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!
    v1.02
    Compatibility layer loading order issue fixed. Now most of plugins should work.
    Tested with new CB 803 build.
    v1.01
    Regular expression permissions support.
    Newer permissions now added above (bugfix).
    Several bugfixes.
    v1.00
    Initial public release.
     
    BRampersad, grid21, MrRazull and 71 others like this.
  2. Offline

    Topma4

    i have find error, it's in permissions.yml :) but thanks.
     
  3. Offline

    danthonywalker

    When is PEX going to be 100% compatible with 1.3.1. It seems like everyone, but one, is having trouble with it. It seems like I either have to go with bPermisions or GroupManager. ._.
     
  4. Offline

    AndreaLibman

    Why are there two permission.yml files when you run your server? One is blank and the other has all the permissions/nodes/groups etc. What are you supposed to do with the blank one?
     
  5. So far, every problem I've seen has been due to another plugin or a misconfiguration. :)

    Are you talking about the permissions.yml in the main server directory and the one in the PEX directory? That's normal, the one in the server directory is made by bukkit itself. Leave it blank.

    Your inheritance line is incorrect. The wiki has an example or two of a proper inheritance line. :)

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

    revo96

    For some reason people just still are able to use Enderchest when i add the permissions node
    - -modifyworld.block.interact.130:*
    - -modifyworld.block.place.130:*
    - -modifyworld.item.use.130:*
    - -modifyworld.item.have.130:*
    But they can still use the enderchest without anything being blocked
    You know why this is?
     
  7. Offline

    AndreaLibman

    Okay, so I leave the one in the main server directory blank and the PEX one with all the permissions. Thank you
     
  8. Offline

    joshworx

    So, what your saying is; The inheritance line in my initial file is incorrect, and that's why it changes.

    This thing just seems to be full of bugs.

    Edit: I meant my .yml file.

    I fixed it by the way. I just had to change up the users format, and put the inheritance sub-section underneath the permissions sub-section

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

    Bobbosells32

    ModifyWorld (comes with PEX) does it
     
  10. Offline

    joshworx

    That's very strange, I would think that would be a part of ChatManager's job... Hmm
     
  11. Offline

    revo96

    Nope Chatmanger manage the chat colours/text type's and modifyworld gives a permission for chat
     
  12. Offline

    Tomex009

    how to make that all groups using default commands?

    etc. hightest donor rank is Lord, i wanna to lord use all perks from rank above lord + default perks ?

    Thanks

    ps. in group manager it was:
    lord:
    default: false
    permissions:
    - some lord perks..
    inheritance:
    - g:group1
    - g:vip
    - g: donorgroup 2
    - default
     
  13. Offline

    Zenhara

    Is there an up to date guide for it? Because I still get an error on it. And do I need the modifyworld and chatmanager enabled?
     
  14. Offline

    Tomex009

  15. Offline

    Darkfard

  16. Offline

    APhilosopher

    oh rly?

    http://pastie.org/4464121

    few pages back someone said this is a known bug with modifyworld and they are working on fixing it in the next release, but to see you saying there are no known bugs with pex or modifyworld makes me nervous that maybe they arent actualy working on this one,

    ive been waiting patiently for this one to be fixed, how bout an eta? or some communication atleast, what is holding up that bug fix? is it gonna require a change by craftbukkit or something? cause i would REALY love it if this server performance effecting bug could be squashed
     
  17. Offline

    Chrisski3

    Kind of confused on the Ranking. Trying to setup ranks in this order: The Default group will be the first, then Builder, then Donor, then Moderator, then Founder. If someone could help me step by step, that would be great. Im very new to permissions.
     
  18. Yes, really. :)

    The issue you are referring to is not something that breaks the ability for PEX to work with 1.3.1. No where did I say there were no bugs in PEX, what I said, not taken out of context, was that all the problems I've seen where 'PEX is broken with 1.3.1', they have been due to misconfiguration. I've yet to see any new problem appear that shows that PEX does not work with 1.3.1.

    What you are mentioning is well known. See https://github.com/PEXPlugins/PermissionsEx/issues/513

    There are multiple tickets opened and referenced in that one as well.

    Most of the guides that are out there still work fine and about 90% of what is in them still applies. The last few updates of PEX were primarily node changes (adding one or two new ones) and a few bug fixes.

    As for your permissions...
    You still have tabs in it according to the yaml parser at http://yaml-online-parser.appspot.com/

    What part are you stuck on? Post any attempts you have currently on pastebin or pastie and link to them here so we can see what you have and can offer advice on what to look at. :)

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

    Zenhara

    Here's my current build: http://pastebin.com/0iaDa52s yet I still get an internal error when I try to use the Permissions plugin. Would some of my plugins be interfering with it? I have ChatManager, CoreProtect, Essentials, Modifyworld, TreeAssist, and a non-working xAuth. I seriously don't understand why it's not working for me and I apologize for my nooby knowledge of these plugins. But I do appreciate every help I can get.
     
  20. Offline

    revo96

    For some reason people just still are able to use Enderchest when i add the permissions node
    - -modifyworld.block.interact.130:*
    - -modifyworld.block.place.130:*
    - -modifyworld.item.use.130:*
    - -modifyworld.item.have.130:*
    But they can still use the enderchest without anything being blocked
    You know why this is?
     
  21. Offline

    Chrisski3

    I have since figured it out, I was just over thinking it, haha
     
  22. No, an internal error when you try to use a PEX command is usually due to PEX not loading. The cause of this will be in your server log. However, running your permissions through a YAML parser shows that you have tabs in the file, which are forbidden in YAML, and will cause this problem.

    *test*

    Yep, I do. :)

    You are specifying metadata on those lines, which it appears that the enderchest doesn't have per the PEX debug.

    You can either remove the colon and asterisk at the end of the nodes, or change it to :?*

    The change I listed can be looked at like an and/or thing, where if it's there, it will match, but if it's not, it's still going to match.

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

    Zenhara

    After countless tries with the parser, I have now gotten it to work. Thank you for being patient with me and running things through. I appreciate every single bit. :)
     
  24. Offline

    VokusX

    I need help, I've tried multiple times to get my permissions working. The prefixes don't show up, and guests have acsess to any command.
    My permissions.yml file
    http://pastebin.com/gfHvFMv4
     
  25. Offline

    Zork766

    Try this:

    Code:
    groups:
      guest:
        default: true
        permissions:
        - bukkit.command.version
        - bukkit.command.tell
        - bukkit.command.me
        - jcommands.afk
        - jcommands.protection.placing.bedrock: false
        - jcommands.protection.placing.fire: false
        - jcommands.protection.placing.ice: false
        - jcommands.protection.placing.lava: false
        - jcommands.spawn
        - jcommands.suicide
        options:
          rank: ‘1000’
        prefix: '&4[Guest] &f'
     
      member:
        inheritance:
        - guest
        permissions:
        - jcommands.burn
        - jcommands.clear
        - jcommands.mute
        - jcommands.ping
        - jcommands.location
        - jcommands.spawn
        - jcommands.suicide
        - jcommands.unmute 
        - bukkit.command.seed
        options:
          rank: ‘700’
        prefix: '[Member] '
     
      mod:
        permissions:
        - worldedit.*
        - jcommands.*
        - bukkit.command.*
        - -bukkit.command.stop
        - -bukkit.command.timings
        - -bukkit.command.ban.player
        - -bukkit.command.ban.ip
        - -bukkit.command.op
        - -bukkit.command.ban.deop
        - -bukkit.command.save.disable
        - -bukkit.command.save.enable
        - -bukkit.command.whitelist.enable
        - -bukkit.command.whitelist.disable
        - -bukkit.command.whitelist.add
        - -bukkit.command.whitelist.remove
        - -bukkit.command.time.add
        - -bukkit.command.time.set
        - -bukkit.command.defaultgamemode
        options:
          rank: '500'
        prefix: '&2[Moderator] &f'
     
      Admin:
        permissions:
        - '*'
        options:
          rank: '200'
        prefix: '&9[Admin] &f'
     
      Owner:
        permissions:
        - '*'
        options:
          rank: '1'
        prefix: '&6[Owner] &f'
    
    Wonder to know, is pex working fine for thoose who have passed servers in 1.3.1 R5.0?


    Try this:
    Show Spoiler

    Code:
    groups:
      guest:
        default: true
        permissions:
        - bukkit.command.version
        - bukkit.command.tell
        - bukkit.command.me
        - jcommands.afk
        - jcommands.protection.placing.bedrock: false
        - jcommands.protection.placing.fire: false
        - jcommands.protection.placing.ice: false
        - jcommands.protection.placing.lava: false
        - jcommands.spawn
        - jcommands.suicide
        options:
          rank: ‘1000’
        prefix: '&4[Guest] &f'
     
      member:
        inheritance:
        - guest
        permissions:
        - jcommands.burn
        - jcommands.clear
        - jcommands.mute
        - jcommands.ping
        - jcommands.location
        - jcommands.spawn
        - jcommands.suicide
        - jcommands.unmute
        - bukkit.command.seed
        options:
          rank: ‘700’
        prefix: '[Member] '
     
      mod:
        permissions:
        - worldedit.*
        - jcommands.*
        - bukkit.command.*
        - -bukkit.command.stop
        - -bukkit.command.timings
        - -bukkit.command.ban.player
        - -bukkit.command.ban.ip
        - -bukkit.command.op
        - -bukkit.command.ban.deop
        - -bukkit.command.save.disable
        - -bukkit.command.save.enable
        - -bukkit.command.whitelist.enable
        - -bukkit.command.whitelist.disable
        - -bukkit.command.whitelist.add
        - -bukkit.command.whitelist.remove
        - -bukkit.command.time.add
        - -bukkit.command.time.set
        - -bukkit.command.defaultgamemode
        options:
          rank: '500'
        prefix: '&2[Moderator] &f'
     
      Admin:
        permissions:
        - '*'
        options:
          rank: '200'
        prefix: '&9[Admin] &f'
     
      Owner:
        permissions:
        - '*'
        options:
          rank: '1'
        prefix: '&6[Owner] &f'
    


    Else, is pex working fine for thoose who have passed servers in 1.3.1 ?

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

    VokusX

    There was a problem with your code. In the console, this happens:

    [Server] SEVERE Ranking Error (console > VokusX): User are not in this ladder
     
  27. Offline

    APhilosopher

    well what you said word for word is "So far, every problem I've seen has been due to another plugin or a misconfiguration"

    so i am sorry if i made an error in assuming that a known bug could be considered a "problem" the post of yours i read did not initialy say anything about problems that specificaly break pex, but rather just problems in general, thank you for clarifieing further that you meant pex BREAKING problems, and NOT just problems in general.

    i sure hope it gets fixed :D not that it breaks the plugin, but if it is effecting server performance (as the error itself says it is) then it realy discourages me from continuing use of the plugin,

    1.3 brought lots of bugs and lag definitely increased, i am hoping that is going to be worked out as more updates to bukkit and my various plugins come out.

    if not then i will just have to attempt an alternative to pex to see just how much this bug realy is effecting performance, not that it TOTALY breaks pex or anything....... :p :p
     
  28. Offline

    GhOsT_935

    Where can i get PEX and ModifyWorld for 1.3.1
     
  29. Offline

    UltraFaceguy

    I really need PEX 1.3.1, my server is still pretty much broken without it, and the MyMcAdmin incompatibility makes it crash every time with PEX 1.2.5...

    Normally I don't bug devs about the speed of updates, but in this case, I really need this...

    So please hurry.
     
  30. Offline

    Grahambo

    Bukkit version: 1.3.1
    OS: Ubuntu 12.04 64-bit
    JVM: Oracle 1.7 64-bit JDK

    Using PEX 1.19.3 or the latest dev build, I get the following error when I try to "pex dump file permissions.yml":

    http://pastebin.com/ebvpvsFB

    Does this work for anyone else using the MySQL backend? I'd like to switch back to file-based, if I could get it to export properly.
     
  31. Offline

    Tanite

    The dev versions seem to work fine for me on 1.3.1. Use the link at the top of the original post :)

    EDIT: ModifyWorld still spitting errors. I put in a ticket. The permissions themselves are working.
     

Share This Page