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

    Jäsef

    -command.you.want.to.block
    i.e put a minus (-) infront of the permission you want to block
    ex:
    groups:
    Admin:
    permissions:
    - '*'
    - -command.you.want.to.block

    hope this helps :)


    EDIT:
    if that doesn't work try to put the command you want to block above '*'
     
  3. https://github.com/t3hk0d3/PermissionsEx/wiki/Basic-Permissions-Setup

    Slightly incorrect.:)
    https://github.com/t3hk0d3/PermissionsEx/wiki/Basic-Permissions-Setup
    Negating nodes on a file backend have to come before the allow nodes.

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

    GODnWOLF

    Code:
    groups:
        default:
            default: true
            permissions: null
            options:
                build: false
        hun:
            default: false
            permissions:
            - essentials.help
            - essentials.helpop
            - essentials.list
            - essentials.motd
            - essentials.rules
            - modifyworld.login
            - modifyworld.chat
            - modifyworld.chat.private
            - modifyworld.usebeds
            - modifyworld.bucket.fill.lava
            - modifyworld.bucket.fill.water
            - modifyworld.bucket.empty.lava
            - modifyworld.bucket.empty.water
            - modifyworld.digestion
            - modifyworld.blocks.destroy.*
            - modifyworld.blocks.place.1
            - modifyworld.blocks.place.2
            - modifyworld.blocks.place.3
            - modifyworld.blocks.place.4
            - modifyworld.blocks.place.5
            - modifyworld.blocks.place.6
            - modifyworld.blocks.place.12
            - modifyworld.blocks.place.13
            - modifyworld.blocks.place.14
            - modifyworld.blocks.place.15
            - modifyworld.blocks.place.16
            - modifyworld.blocks.place.17
            - modifyworld.blocks.place.18
            - modifyworld.blocks.place.20
            - modifyworld.blocks.place.22
            - modifyworld.blocks.place.23
            - modifyworld.blocks.place.24
            - modifyworld.blocks.place.25
            - modifyworld.blocks.place.29
            - modifyworld.blocks.place.30
            - modifyworld.blocks.place.27
            - modifyworld.blocks.place.28
            - modifyworld.blocks.place.33
            - modifyworld.blocks.place.35
            - modifyworld.blocks.place.37
            - modifyworld.blocks.place.38
            - modifyworld.blocks.place.39
            - modifyworld.blocks.place.40
            - modifyworld.blocks.place.41
            - modifyworld.blocks.place.42
            - modifyworld.blocks.place.44
            - modifyworld.blocks.place.45
            - modifyworld.blocks.place.47
            - modifyworld.blocks.place.48
            - modifyworld.blocks.place.49
            - modifyworld.blocks.place.50
            - modifyworld.blocks.place.53
            - modifyworld.blocks.place.57
            - modifyworld.blocks.place.58
            - modifyworld.blocks.place.61
            - modifyworld.blocks.place.65
            - modifyworld.blocks.place.66
            - modifyworld.blocks.place.69
            - modifyworld.blocks.place.70
            - modifyworld.blocks.place.72
            - modifyworld.blocks.place.76
            - modifyworld.blocks.place.77
            - modifyworld.blocks.place.80
            - modifyworld.blocks.place.81
            - modifyworld.blocks.place.82
            - modifyworld.blocks.place.84
            - modifyworld.blocks.place.85
            - modifyworld.blocks.place.86
            - modifyworld.blocks.place.87
            - modifyworld.blocks.place.88
            - modifyworld.blocks.place.89
            - modifyworld.blocks.place.91
            - modifyworld.blocks.place.96
            - modifyworld.blocks.place.98
            - modifyworld.blocks.place.101
            - modifyworld.blocks.place.102
            - modifyworld.blocks.place.103
            - modifyworld.blocks.place.106
            - modifyworld.blocks.place.107
            - modifyworld.blocks.place.108
            - modifyworld.blocks.place.109
            - modifyworld.blocks.place.112
            - modifyworld.blocks.place.113
            - modifyworld.blocks.place.114
            - modifyworld.blocks.interact.261
            - modifyworld.blocks.interact.262
            - modifyworld.blocks.interact.268
            - modifyworld.blocks.interact.281
            - modifyworld.blocks.interact.282
            - modifyworld.blocks.interact.319
            - modifyworld.blocks.interact.298
            - modifyworld.blocks.interact.299
            - modifyworld.blocks.interact.300
            - modifyworld.blocks.interact.301
            - modifyworld.blocks.interact.297
            - modifyworld.blocks.interact.320
            - modifyworld.blocks.interact.321
            - modifyworld.blocks.interact.322
            - modifyworld.blocks.interact.323
            - modifyworld.blocks.interact.324
            - modifyworld.blocks.interact.325
            - modifyworld.blocks.interact.326
            - modifyworld.blocks.interact.327
            - modifyworld.blocks.interact.329
            - modifyworld.blocks.interact.328
            - modifyworld.blocks.interact.330
            - modifyworld.blocks.interact.331
            - modifyworld.blocks.interact.332
            - modifyworld.blocks.interact.333
            - modifyworld.blocks.interact.334
            - modifyworld.blocks.interact.339
            - modifyworld.blocks.interact.340
            - modifyworld.blocks.interact.345
            - modifyworld.blocks.interact.346
            - modifyworld.blocks.interact.347
            - modifyworld.blocks.interact.349
            - modifyworld.blocks.interact.350
            - modifyworld.blocks.interact.352
            - modifyworld.blocks.interact.354
            - modifyworld.blocks.interact.355
            - modifyworld.blocks.interact.356
            - modifyworld.blocks.interact.357
            - modifyworld.blocks.interact.358
            - modifyworld.blocks.interact.360
            - modifyworld.blocks.interact.363
            - modifyworld.blocks.interact.364
            - modifyworld.blocks.interact.365
            - modifyworld.blocks.interact.366
            - modifyworld.blocks.interact.367
            - modifyworld.blocks.interact.373
            - permissions.modifyworld.enable
            prefix: '&a[Hunter]&f'
            suffix: ''
        war:
            default: false
            permissions:
            - essentials.help
            - essentials.helpop
            - essentials.list
            - essentials.motd
            - essentials.rules
            - modifyworld.
            prefix: '&c'
            suffix: '&c'
            worlds:
                god:
                    permissions:
                    - user
        alc:
            default: false
            permissions:
            - CaptureThePortal.red
            - essentials.help
            - essentials.helpop
            - essentials.list
            - essentials.motd
            - essentials.rules
            - essentials.spawn
    
    Smth wrong, please help!
    Hunter group canot place block or break it.
     
  5. Offline

    noneandnonly

    I think ModifyWorld is buggy on 1.0.0 at the moment. There is no release for 1.0.0 if you're using it (and I think so).
    It's not working on my server either and I'm waiting for an update, too ;)
     
  6. Offline

    GODnWOLF

    Oh, thank you. Dont you know if there another plugin that will allow or disallow to use different items?
    Cuase i want to create somekind of a class system on my serever)
     
  7. Offline

    Jäsef

  8. Offline

    Dargan

  9. Offline

    Jäsef

    actually, PEX, along with ModifyWorld, works flawlessly on my server. grab a dev build and it should work just fine, if you set it up properly;)
     
  10. Offline

    GODnWOLF

    Can i ask to make an example code or to post yours?
    It will be usefull for me, because i think that i made a mistake somewhere in my code)
     
  11. Offline

    Jäsef

    this is my PEX config:

    Code:
    groups:
        Guest:
            default: true
            permissions:
            - modifyworld.blocks.interact.*
            - modifyworld.blocks.place.*
            - modifyworld.sneak
            - modifyworld.sprint
            - modifyworld.usebeds
            - modifyworld.blocks.destroy.*
            - modifyworld.items.drop.*
            - modifyworld.items.pickup.*
            - modifyworld.vehicle.enter.*
            - modifyworld.vehicle.collide.*
            - modifyworld.chat
            - -modifyworld.items.use.271
            - modifyworld.items.use.*
            - CommandBin.general.warp
        Builder:
            inheritance: Guest
            permissions:
            - modifyworld.*
            prefix: '&2[Builder]'
        Moderator:
            inheritance: Builder
            permissions:
            - worldedit.*
            prefix: '&4[Mod]'
        Admin:
            permissions:
            - '*'
            prefix: '&3[&6Admin&3]'
        Owner:
            permissions:
            - '*'
            prefix: '&4[&2O&8W&9N&3E&7R&4]'
    users:
        NyanKitteeh:
            group:
            - Guest
            suffix: '&5'
        emilmoo:
            group:
            - Admin
        senecalaxer:
            group:
            - Admin
        shraakx2:
            group:
            - Builder
        sieberj:
            group:
            - Builder
        assassin1940:
            group:
            - Builder
    
    EDIT: note that this is just a test config, im not entierly done with permissins for Mods and the Builders, just sayin'

    please read the wiki before asking questions
    PEX doesn't have a build node (build: true/false), instead it has modifyworld that comes with it. read the wiki on how to use modifyworld.

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

    GODnWOLF

    Thanks. Gonna try to write the code again....
     
  13. Offline

    blokzeil1

    i need realy support for this, i have closed my second world, people are not happy... andybody?​
     
  14. Offline

    Crafting-miner

    HAHA i knew i would get at least one reply, thanks for making me laugh :)
    maybe i should have tagged it
    [sarcasm]
    [/sarcasm]
     
  15. First off, thank you for using code tags. And I have to mention that your permissions file looks very good in it's structure. You have the global and multiworld permissions broken up nicely.

    Now as for your LWC problem, I see that you have a typo in the default and RE group for the multiworld permissions. You have Worlds: when it should be worlds: (all lowercase).

    I didn't see anything about what permission system LWC supports on the plugin page for it (permissions 2/3, PEX native, super perms?), so if it only supports the old permissions 2/3 series, you will have to install the PEX compatibility layer (permissions.jar in the PEX archive you downloaded) for it to work.

    But first, try the capitalization fix and see if that takes care of it.

    Yes, that would have helped. ;)

    What don't you understand about it? I found it to be pretty clear, and the basic permissions section has a valid example of what it looks like after the basic setup commands are run.

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

    CakRochi

    how to restraint build?
    I written "build : false" then that doesn't work.
     
  17. Offline

    Adam_

    WHAT DOES '*' means in permissions ?
     
  18. Offline

    Jäsef

    it serves as an all-round-node which basically means that if a group has '*' as a permission, they have EVERY single permission. useful for the admin group...
     
  19. Offline

    noneandnonly

    I'm just waiting, so I don't know, sorry.

    '*' means you've got EVERY permission existing!
     
  20. Offline

    Shooty

    I use Superpermsbridge without any problem before :-(
     
  21. Offline

    ElementzYT

    Any way to disable the "You don't have enough permissions to promote on this ladder" for Guests when I add the command /pex promot <player> to a sign. I add the command using ServerSigns. I basically like them to use the sign at a certain cost and let them promote themselves without them having the command.
     
  22. Offline

    xandercage2

    ok i have a question i just put in PEX on my server and i dont have permissions set up for anything other then created groups set ranks and thats really about it but one of my guys can use factions..... and i havnt set that up yet... thers no errors or nothing that i see in console can anyone explane this to me?
     
  23. Offline

    Jäsef

    *sigh*
    could you please post your PEX config and specify your problem? is your guy an admin? a guest? Always post your pex config! :)
     
  24. Offline

    xandercage2

    sorry bout that also is there a way to take off the double title in gray im getting the [owner]then the colored prefix then the name?
    Code:
    groups:
        default:
            default: true
            permissions:
            - essentials.help
            - modifyworld.*
            options:
                rank: '1000'
            prefix: '&7(Default)'
        Owner:
            permissions:
            - '*'
            options:
                rank: '0'
            prefix: '&f(&6Owner&f)'
        Member:
            options:
                rank: '900'
            prefix: '&f(&bMember&f)'
        Copper:
            options:
                rank: '800'
            prefix: '&f(Copper)'
        Bronze:
            options:
                rank: '700'
            prefix: '&f(&7Bronze&f)'
        Silver:
            options:
                rank: '600'
            prefix: '&f(&8Silver&f)'
        Gold:
            options:
                rank: '500'
            prefix: '&f(&dGold&f)'
        Diamond:
            options:
                rank: '400'
            prefix: '&f(&9Diamond&f)'
        Master:
            options:
                rank: '300'
            prefix: '&f(&aMaster&f)'
        Grandmaster:
            options:
                rank: '250'
            prefix: '&f(&0Grandmaster&f)'
        Co-Owner:
            options:
                rank: '1'
            prefix: '&f(&3Co-Owner&f)'
        Mod:
            options:
                rank: '210'
        HeadMod:
            options:
                rank: '200'
        Admin:
            options:
                rank: '150'
        HeadAdmin:
            options:
                rank: '100'
    users:
        TheVasar:
            group:
            - Owner
        butterflyskiss87:
            group:
            - Member
        butterflykiss87:
            group:
            - Member
        akintravis:
            group:
            - Member
        hawkeyezs:
            group:
            - Co-Owner
     
  25. Offline

    Jäsef

    for the faction thing: since you are'nt using permissions for permissions(lol) you can restrain your players. my guess is that the player who can use faction commands is in your ops.txt-file.

    for the prefix stuff: install Chatter(a chat plugin). remove "+group" in the config, for both msg-format and name-format. disable chatmanager. done!
     
  26. Offline

    Dargan

  27. Offline

    Kevybevy

    Good but how do I add color to my prefixes?
     
  28. Offline

    Meteo

    How can u add only users? :O Or add people to a group?
     
  29. Offline

    Adam_

    thanks ! , now ive put myself as the owner , but i still dont get the permission to do commands like /bigtree from essentials . can someone please give me a link or whatever to a permissions.yml file , that have all the permissions and essentials commands in it .
     
  30. That's nice, but it doesn't change the fact that it's a separate plugin for a separate permissions manager. You can't run them both at the same time. If you were using PEX and the Superpermsbridge from Permissionsbukkit at the same time, more than likely PEX loaded before the bridge did, taking over the permissions listener, so the bridge plugin didn't actually do anything.

    PEX supports Superperms already, there isn't a need for a 'superperms bridge', as long as it's enabled in the config.

    I don't understand the question. If you are wanting to know how to add a user to the permissions file, you need to read the wiki, it's covered there.
    https://github.com/t3hk0d3/PermissionsEx/wiki/Basic-Permissions-Setup
    https://github.com/t3hk0d3/PermissionsEx/wiki/Commands

    This is probably one of the most common errors that appears with PEX, and 99% of the time, it's due to either a typo in a file that ends up with PEX disabling itself or some other plugin is taking over the permissions listener, keeping PEX from doing anything.

    Look at your server.log and post it in a pastebin (thank you for using it, it helps a lot). My first guess is the plugin route.

    Also, it's doubtful that anyone is 'ignoring' your posts. Remember, this is all volunteer work, we all have lives and day jobs. Trying to help figure out issues with bukkit and plugins is not our full time job.:)

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

    CakRochi

    O-oh. I'm sorry to not see the wiki.
    From now on i'll see wiki careful !

    I'm sorry to asking this.
    I'm not good at English well, so you may excuse me...
    I can't translate wiki's Modifyworld texts. :(
    How to setting modifyworld nodes : Enable every things, but disable destroy and place....

    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