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

    Megalanias

    Okay now it shows like this :
    Code:
     users:
        Megalanias:
            group:
            - admins
            permissions:
            - permissions.*
            worlds:
                world:
            permissions:
            - "*"
            group:
            - admins
                    Prefix '&5[YARR]&f'
        maarg:
            group:
            - admins
            permissions:
            - permissions.*
            worlds:
                world:
            permissions:
            - test.*
            group:
            - admins
                   prefix '&5[YARR]&f'
    groups:
        default:
            default: true
            permissions:
            - modifyworld.blocks.place.tnt
            - modifyworld.chat
            - lwc.deny
        admins:
            default: false
            inheritance:
            - user
            permissions:
            - '*'
            options:
                test.test: '100500'
            worlds:
                nether:
            permissions:
            - nocheat.fly
                    prefix '&7[ADMIN FROM HELL]'
        user:
            default: false
            inheritance: null
            permissions:
            - multiworld.miniu
        - supernatural.command.classes
        - supernatural.command.help
        - supernatural.command.list
        - supernatural.command.power
        - supernatural.command.killlist
        - dreamland.goto
        - dreamland.fly
        - dreamland.nowakeup
        - niftywarp.use.add
        - niftywarp.use.home
        - niftywarp.use.homeset
        - niftywarp.use.list
        - niftywarp.use.set
        - niftywarp.use.warp
        - lwc.protect
        - iConomy.holdings
        - iConomy.help
        - iConomy.payment
        - iConomy.accounts.create
        - iConomy.accounts.remove
        - towny.town.resident
        - towny.town.toggle.pvp
        - towny.town.toggle.public
        - towny.town.toggle.explosions
        - towny.town.toggle.fire
        - towny.town.toggle.mobs
        - towny.nation.grant-titles
        - towny.wild.*
        - simplenews.read
        - jail.usercmd.jailstatus
        - jail.usercmd.jailpay
        - jail.modifyjail
        - jail.openchest
    options:
    null
    worlds:
        nether:
            inheritance:
            - world
    and don't works .....
     
  3. Offline

    Drei Gyuu

    Does this have the same feature as bpermission?
    Where you can disable the permission node by typing adding the "^" in the config - ^essentials.tp
    Will basically disable the TP command for essentials.
     
  4. Offline

    juli7796

    hmmm, its spamming my console with things like this:

    Code:
    [SEVERE] Error occurred while enabling dynmap v0.22.1 (Is it up to date?): Permissions manager is not accessable. Is the PermissionsEx plugin enabled?
    java.lang.RuntimeException: Permissions manager is not accessable. Is the PermissionsEx plugin enabled?
        at ru.tehkode.permissions.bukkit.PermissionsEx.getPermissionManager(PermissionsEx.java:140)
        at com.nijikokun.bukkit.Permissions.Permissions.getHandler(Permissions.java:80)
        at org.dynmap.permissions.NijikokunPermissions.<init>(NijikokunPermissions.java:27)
        at org.dynmap.permissions.NijikokunPermissions.create(NijikokunPermissions.java:22)
        at org.dynmap.DynmapPlugin.onEnable(DynmapPlugin.java:211)
        at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:126)
        at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:920)
        at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:278)
        at org.bukkit.craftbukkit.CraftServer.loadPlugin(CraftServer.java:173)
        at org.bukkit.craftbukkit.CraftServer.enablePlugins(CraftServer.java:156)
        at net.minecraft.server.MinecraftServer.e(MinecraftServer.java:297)
        at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:284)
        at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:152)
        at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:348)
        at net.minecraft.server.ThreadServerApplication.run(SourceFile:417)
    
    or, a little different:


    Code:
     edit: not different :D 
    actually, PEX IS enabled :/
     
  5. Offline

    3x3mpt

    What is the permissions 2.x schema
     
  6. Offline

    Onlyme

    Just bringing this back to the last page, since someone else liked it.
    Also, the Ticket on github here: https://github.com/t3hk0d3/PermissionsEx/issues/66

    If you could address something about this, that would be awesome. Thanks!
     
  7. Offline

    SmartyGeek

    Me too!!!!! I took down my server until I get it fixed, and I have waiting customers.....
     
  8. Your options: line is still incorrect and "it doesn't work" isn't nearly descriptive enough to be able to narrow down the problem.

    @juli7796 @SmartyGeek
    Something isn't starting up right or you have a misconfiguration in PEX. I've experimented with dynamap and it never failed with PEX running. Look in your server.log for PEX lines and see what they say.

    Also, dynmap doesn't use permissions that I know of, so there isn't any reason why it should be trying to talk to PEX. I would also check with the dev for dynmap and see why it's apparently trying to access a permissions layer.

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

    paroxysm11

    Hey - this is a brilliant plugin and I'm trying to convert over to it from Permissions 3.x - unfortunately, it's not going exactly wonderfully.

    I follow the steps in the wiki after converting it to Permissions 2.x format - but when I do 'pex dump...permissions.yml' command, it throws a Null error. Means nothing to me. I think my problem might be that I'm not converting the permissions format over - could someone provide a sample Permissions 2.x world.yml?
     
  10. Offline

    ZacTheDead

    Can we Have Prefixes?
    Under
    <groupname>:
    <PERM>
    options:
    Prefix?
     
  11. Offline

    daemitus

  12. Offline

    ZacTheDead

  13. Offline

    daemitus

    Short answer, yes. Its not under options, its directly under the groupname. same for suffix: ''
     
  14. uhm is there a option to revoke a single permission like it was with the yeti permissions?
    Code:
    - "*"
    - "-plugin.command"
    
    PS: github is down at the moment, cant read wiki
     
    rlddlck likes this.
  15. Offline

    erickingsr

    Please give me a donation link!
     
  16. Offline

    t3hk0d3

    look for example in OP post
     
  17. Offline

    asmdz

    what are the permission nodes for vanilla server commands?(like /gamemode /time set <value> etc.)
     
  18. Offline

    Xmillsa

  19. Offline

    asmdz

  20. Offline

    Haribo98

    Do we still need something like HeroChat to use this?
     
  21. Offline

    jmcgee611

    So I'd like to upgrade from GroupManager to PermissionsEx on my server (cause it seems better), but for some reason when I tried to config the groups it wouldn't seem to work right...ever. So I scrapped and went back to GroupMan. Is there a tutorial out there on how to convert from GM to PE? Cause google wasn't my friend this time.
     
  22. Offline

    Dev909

    is there a way to have a default group? For say if someone joins for the first time, they are automatcially added to a group?

    EDIT:
    Nevermind firgured it out, does anyone know how to allow the default group to chat?

    EDIT2:
    Nevermind again....found it..lol
     
  23. Offline

    Onlyme

    Your reply from Ticket #66:
    I just tested this, and it does not work.
    PEX v1.14
    CB 1185
    ChatManager (Bundled with PEX v1.14)

    Paste of Default config on my test server: http://pastebin.com/fTp6P6Db

    Steps to Reproduce:
    Created prefix for myself ingame.
    Changed the user's prefix in the file.
    Logged out, waited, logged in.
    User tag should still be the same.

    If I need to add a line in the config file, please tell me the exact line it is.
     
  24. Offline

    austin101

    I'm having trouble getting my prisoner rank to work, they are only supposed to break cobble stone but it does not let them.

    It only works when modifyworld.* is enabled, but then they can break everything which is what not what I want.

    Code:
        prisoner:
            prefix: '&8[Prisoner]&f '
            default: false
            options:
                rank: '11'
            permissions:
            - modifyworld.blocks.interact.4
            - modifyworld.chat
            - modifyworld.blocks.destroy.4
            - modifyworld.blocks.place.4
     
  25. Offline

    ZacTheDead

    Are We Able To Remove a Command Eg:
    permissions:
    - essentials.*
    - (you don't Want them to have) essentials.god
    is there a way?
     
  26. Offline

    nichiatu

    Why aren't prefix colors working? D: I've tried like every color plugin there is, does anyone know? Do I have to use Essentials?
     
  27. Offline

    Emiya Shirou

    I never have any permissions system on my server. Do I need to install both PermissionsEx.jar and Permissions.jar (is the compatibility layer to TheYeti's Permissions 2.7) or I can just put PermissionsEx.jar without the other one?
     
  28. Sure, add the item codes you want to the line.
    Code:
            permissions:
            - -modifyworld.blocks.interact.(23|25|54|61|62|84)
            - modifyworld.blocks.interact.*
            - modifyworld.usebeds
            - modifyworld.chat
            - modifyworld.items.have.(260|296|297|319|320|360|363|364|365|366|367)
            - modifyworld.items.drop.(260|296|297|319|320|360|363|364|365|366|367)
            - modifyworld.items.pickup.(260|296|297|319|320|360|363|364|365|366|367)
    I use this permissions set for guests. This allows them to have food and eat it, but not break or have any other items in their inventory, and keeps them from looking inside containers (chests, furnaces, etc).

    The key is that PEX, when reading a permissions file, works like a (good) firewall. It checks from the top down, and as soon as it hits a line that matches what it's looking for, it stops, which is why the line that takes away interactions with chests (- -modifyworld.blocks.interact.(23|25|54|61|62|84)) and such is before the line that allows all interactions (- modifyworld.blocks.interact.*).

    For example:
    1. A guest tries to open a chest
    2. PEX looks at the list and finds that it is not allowed because the - -modifyworld.blocks.interact.(23|25|54|61|62|84) line has the item code for a chest (54).
    3. The same person tries to open a door (324). PEX bypasses the -modifyworld.blocks line above because it doesn't have the item code and doesn't match. The next line, - modifyworld.blocks.interact.*, matches due to the wildcard and the guest is allowed to open the door.
    Does that help you figure it out?

    Yes, specify the line that takes away the permission before the one that gives them access to the other ones. Look at my reply to austin101 for more details.


    Only if you have plugins that don't use superperms (and you turned off supoerperms support for some reason) or support PEX natively.

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

    Vezorock

    Its fine... which is strange because permissions 3 stopped working on my server all of a sudden
     
  30. Can you post your permissions.yml file in code tags?
     
  31. Offline

    dxwarlock

    anyone else having strange lag issues with the newer builds?
    if I revert to older builds its fine...and it only effects people with '*' perms.

    anyone else can loggin quickly, use MV portals fine, me or a mod logs in..we have a 5-6 lag of actually getting past "loading terrain" and it lags everything on the server until we finish...and if we use a portal, it also takes 6-7 seconds to transfer, while lagging the server until we load in the new world.

    it SEEMS its something to do with loading/changing/going to a map...and its weird it only applies to permission people that have '*' somewhere in the permissions. be it only '*', or people with
    - -whatever
    - -somethingelse
    '*'
     

Share This Page