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

    Toasty

    Does PEX make use of the root permissions.yml file?

    If it doesn't, then I would highly suggest adding support for it. It would make the configuration of permissions much easier, and would make switching between permissions plugins much more simple and straightforward. Instead of having to completely rebuild the plugin's permissions.yml file when switching plugins, you could simply build it using your own custom nodes that encompass logically grouped sets of permissions.

    If it does, awesome. But I'd like to see some reference to it in the wiki.
     
  3. Offline

    cruisecho

    Does using MySQL offer a performance advantage to using the yml file?
     
  4. Offline

    Buckethead

    it does thats how bridge works

    yes but sql is really meant for if u have like alot of people like hundreds of peole on at once

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

    cruisecho

    Thanks, I'll convert it over then.
     
  6. Offline

    Buckethead

    do u know sql cuz if u dont ur work is cut out

    someone plz help with this no preffix. what do?

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Sep 9, 2018
  7. According to the YAML parser, your permissions code looks like this:
    Code:
    {
      "options": {
        "prefix": "&c<Citizen>&f"
      }, 
      "Citizen": {
        "default": false, 
        "inheritance": [
          "Guest"
        ], 
        "permissions": 
    Looks like your placement and/or indentation for the prefix is incorrect.

    Also, it looks like you have a lot of extra entries in there. For example:
    Code:
    - deadbolt.user.*
    - deadbolt.user.create.*
    The deadbolt.user.* will match deadbolt.user.create.*, and I believe that essentials.warp.list and essentials.warp.* overlaps as well.
     
  8. Offline

    Buckethead

    i know im just lazy from migrating permissions and changin them. still preffix dont work. and i loooke at example it shows perms then options then preffix idk what i missed
     
  9. Offline

    ratty

    I'm still trying to track this down, but sometimes some permissions will not work for only some users. Then if I restart the server, everything is fine. It only started happening after I upgraded to RB1240. The plugins I have seen the behavior in was LogBlock and VanishNoPacket. It doesn't always happen either, if I can find a way to reproduce it reliably, I'll post it, but in the meantime I was curious if anyone else is seeing weird permissions problems too.

    Is there a way to query a permission node? Like /pex user <name> check <permission node> and have say true or false. I can't see any command like that in the help. Then I could simulate a plugin checking a permission to see if its actually getting set. I can do /pex user, and it dumps all the nodes that are set, but I just see '*' along with some of the negative ones, but that doesnt mean if a plugin actually checks a permission it will work. Then I can figure out if its PEX or the plugin misbehaving.
     
  10. Offline

    cruisecho

    Thanks, I've been working with MySQL for a few years now and have a nice Percona + XtraDB install hungering for more data. :D

    I just find the yml file really easy to work with. I'd much rather have the performance though.
     
  11. Offline

    Buckethead

    yeah but again like i said more work then needed if u have a smaller number of people

    yes i have this problem with a few to and it seems to be if theres alot of activity and i dont reload for a few days or so

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

    RaesWolf

    im still having issues with my prefix as well. I have provided information in previous posts and even looking at others who are having the same problem I still dont see an answer that will fix the problem...
     
  13. Offline

    Buckethead

    is it us? this plugin? WHAT. yo AUTHOR READ DIS ^^^^^^^^.
     
  14. I don't know if there is a way to check for a specific permission for a given user, but there is a debug toggle that will have PEX print the permission node that is requested/checked when a user tries to do something. Might that work?

    And we don't know what your current config is now, or what it presents to PEX (the output of a YAML parser). :)

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

    14forrest14

    thanks for your response, i tried what you said, including disabling superperms completely, but it still restarted when players joined, any other ideas on how to maybe fix this? Also, there are no error messages, it just restarts. thanks
     
  16. Offline

    Kanurame

    Is there a way to make it so that when a person logs on for the first time, they get put in the default group?
     
  17. Offline

    kawiz

    iChat for 1185 is working great with PEX, confirmed. :)
     
  18. Offline

    The3vilm0nk3y

    Anyone have thoughts on this:

    I am looking for the same answer yet the wiki does not contain a sample of this. Please explain in a lil more detail how i would revoke a command to someone that has the - '*' perm.

    This should help:
    Code:
    groups:
        default:
            default: true
            permissions:
            - essentials.help
            - essentials.helpop
            - essentials.list
            - essentials.motd
            - essentials.rules
            - essentials.spawn
            - modifyworld.chat
            options:
                rank: '1000'
    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Sep 9, 2018
  19. https://github.com/t3hk0d3/PermissionsEx/wiki/Configuration

    File backend config section
     
  20. Offline

    t3hk0d3

    Check /pex user <playername>

    Funny, but you mention exactly command what existed in PEX to check node:

    /pex user <name> check <permission> <world>

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

    soferal

    I need help urgently
    SO what happened was i decided to get logblock and i have got it but i see this on my log when i start it up
    i Have permissionsEX installed and it works with other plugins but this

    21:33:35 [INFO] [LogBlock] Permissions plugin not found. Using Bukkit Permissions
    21:33:35 [INFO] [LogBlock] Scheduled consumer with bukkit scheduler.
    21:33:35 [INFO] LogBlock v1.32 by DiddiZ enabled.
    PLz help i hope permissionsEX can help me
     
  22. Offline

    Valtos

    I everybody

    I have a crazy problem with permissions.

    I have a login-Command to login into the Communty Database.
    This Command works fine if I have the permission
    But this is not the right solution. I can't give any users all permission of my plugin.


    Here my plugin.yml:

    Code:
    name: Management
    main: de.nysoft.management.Management
    version: 0.87b
    depend: [Spout, PermissionsEx, iConomy, Towny]
    commands:
        pos:
            description: Get your current Position
            usage: /pos
            permission: management.command.pos
        robot:
            description: Use the Robot to easy modify Blocks
            usage: /robot
            permission: management.command.pos
        login:
            description: Login CommunityUser of No-FM-Community
            usage: /login [email] [password]
            permission: management.command.login
        management:
            description: Get Statistics about Management-PlugIn
            usage: /management
            permission: management.command.management
        location:
            description: Set or teleport to Starting- and Waiting-Location
            usage: /location [set|tp] [starting|waiting]
            permission: management.command.location
        npc:
            description: Create, delete or rename NPCs
            usage: /npc [create|delete|rename|types|status|tp|animate|move] [name] [type|newname]
            permission: management.command.npc
    permissions:
        management.command.*:
            description: Gives access to all Management Plugin Commands
            children:
                management.command.robot: true
                management.command.pos: true
                management.command.login: true
                management.command.management: true
                management.command.location: true
                management.command.npc: true
        management.teamcommand.*:
            description: Gives access to Management Plugin Team-Commands
            children:
                management.command.robot: false
                management.command.pos: true
                management.command.login: true
                management.command.management: false
                management.command.location: false
                management.command.npc: true
        management.command.pos:
            description: Allows you to see your position
            default: false
        management.command.robot:
            description: Allows you to use the robot
            default: false
        management.command.login:
            description: Allows you to login into community-database
            default: true
        management.command.management:
            description: Allows you to see Management-Statistics
            default: false
        management.command.location:
            description: Allows you to set or teleport to Starting- and Waiting-Location
            default: false
        management.command.npc:
            description: Allows you manage NPCs
            default: false
    A user of group
    should be have this permission.

    If i check the permission:

    Code:
    >pex user trinkmilch check management.command.login
    18:58:45 [INFO] Player "trinkmilch" have "management.command.login" = true
    

    but i can't use the command!

    If i print the group "default" i get this:
    Code:
    >pex group default
    19:00:11 [INFO] default are member of:
    19:00:11 [INFO]   @[URL='http://forums.bukkit.org/members/null.69298/']Null[/URL]:
    19:00:11 [INFO] Group default's permissions:
    19:00:11 [INFO] 1) management.command.login @[URL='http://forums.bukkit.org/members/null.69298/']Null[/URL] (own)
    19:00:11 [INFO] 2) modifyworld.chat @[URL='http://forums.bukkit.org/members/null.69298/']Null[/URL] (own)
    19:00:11 [INFO] Group default's Options:
    19:00:11 [INFO]   rank = "1000"
    
    All what i test... i get:
    permissions of the user:
    Code:
    >pex user trinkmilch
    19:07:36 [INFO] trinkmilch are member of:
    19:07:36 [INFO]    default (rank 1000 @ default)
    19:07:36 [INFO] trinkmilch's permissions:
    19:07:36 [INFO]    management.command.login @[URL='http://forums.bukkit.org/members/null.69298/']Null[/URL] (from default)
    19:07:36 [INFO]    modifyworld.chat @[URL='http://forums.bukkit.org/members/null.69298/']Null[/URL] (from default)
    19:07:36 [INFO] trinkmilch's options:
    
    Can anyone tell me, what is the problem in here?!
     
  23. Offline

    squeezer

    have problems with pex and multiverse-portals. player of default group can't use portals.
    i set multiverse.portal.access.PORTALNAME for default group...
     
  24. Offline

    ratty

    How embarassing. :-/
    When I type /pex without args it gives help, and check is not listed there. I never thought to just try the command that I would have named it to see if there was a hidden command. Oh well, now I have a new tool to use in figuring out this problem, thanks!
     
  25. Offline

    Icelaunche

    if tomorrow is today wouldnt today be yesterday tomorrow? (i hope i worded that right)
     
  26. Offline

    Renagade

  27. Offline

    Icelaunche

    you need to add somthing like prefix: [titlehere] I think you need to do 1 more thing but i dont have my perms file atm so i can post it later if no one answers before me :p

    Edit: Found it in the forums! Heres what it should look like:

    Code:
    Admins:
            default: false
            info:
                prefix: '&4[ADMIN]'
                suffix: ''
                build: true
            inheritance:
            permissions:
                - '*'
    (Thats an example - you can change colors (&4 - code fore red) group names (Admins:) and tags ([ADMIN]) and of course permission nodes ( '*' ))
     
  28. Offline

    The3vilm0nk3y

    Just did this again.... none of the nodes are appering yet they still have the permissions to the op, deop, time, give, gamemode and all the other bukkit commands. i can post my config file for u and permissions file.
    Code:
    Perms:
    groups:
        default:
            default: false
            permissions:
            - essentials.help
            - essentials.helpop
            - essentials.list
            - essentials.motd
            - essentials.rules
            - essentials.spawn
            - modifyworld.chat
            options:
                rank: '1000'
        admins:
            permissions:
            - '*'
            - bukkit.command.reload
            options:
                rank: '1'
            inheritance:
            - Moderator
        owner:
            permissions:
            - '*'
            - bukkit.command.op.give
            - bukkit.command.op.take
            - bukkit.command.stop
            - bukkit.command.save.perform
            - bukkit.command.save.enable
            - bukkit.command.whitelist.enable
            - bukkit.command.whitelist.disable
            - bukkit.command.gamemode
            options:
                rank: '0'
            inheritance:
            - admins
            prefix: '&0(&4Owner&0)&7'
        builder:
            default: true
            permissions:
            - bukkit.command.tell
            - modifyworld.*
            - bukkit.command.version
            - bukkit.command.plugins
            - bukkit.command.kill
            - bukkit.command.me
            - bukkit.command.help
            - backpack.size9
            - backpack.upgrade18
            - backpack.clear
            - essentials.afk
            - essentials.balance
            - essentials.chat.shout
            - essentials.compass
            - essentials.depth
            - essentials.mail
            - essentials.mail.send
            - essentials.me
            - essentials.msg
            - essentials.pay
            - essentials.sethome
            - essentials.signs.use.*
            - essentials.suicide
            - essentials.tpaccept
            - essentials.tpdeny
            - essentials.worth
            - stargate.use
            - commandSigns.use
            - spoutessentials.joinmessage
            - spoutessentials.leavemessage
            - multiverse.access.world
            - multiverse.access.world_nether
            - citizens.questers.use.help
            - citizens.questers.use.quests.help
            options:
                rank: '900'
            inheritance:
            - default
        constructor:
            permissions:
            - essentials.home
            - backpack.upgrade27
            - backpack.upgrade36
            - essentials.tpa
            - essentials.tpahere
            - essentials.signs.create.disposal
            - essentials.signs.break.disposal
            - backpack.workbench
            options:
                rank: '800'
            inheritance:
            - builder
        mechanic:
            permissions:
            - falsebook.blocks.lift
            - falsebook.blocks.gate
            - falsebook.blocks.hiddenswitch
            - falsebook.blocks.hiddenswitch.create
            - falsebook.blocks.lightswitch.create
            - falsebook.blocks.lightswitch
            - falsebook.destroy.blocks
            - essentials.back
            - backpack.upgrade45
            options:
                rank: '700'
            inheritance:
            - constructor
        technician:
            permissions:
            - falsebook.ic.standard
            - falsebook.ic.detection
            - falsebook.ic.selftriggered
            - falsebook.cart.*
            - backpack.upgrade54
            - spoutessentials.cape
            options:
                rank: '600'
                inheritance:
                - mechanic
        Master:
            permissions:
            - worldguard.heal
            - godpowers.gaia
            options:
                rank: '500'
                inheritance:
                - technician
        moderator:
            permissions:
            - bukkit.command.kick
            - bukkit.command.ban.player
            - bukkit.command.unban.player
            - bukkit.command.ban.ip
            - bukkit.command.unban.ip
            - bukkit.command.teleport
            - bukkit.command.list
            - bukkit.command.say
            - essentials.itemspawn.item-all
            - essentials.give.item-all
            - essentials.ban
            - essentials.banip
            - essentials.broadcast
            - essentials.delwarp
            - essentials.eco
            - essentials.ext
            - essentials.getpos
            - essentials.jump
            - essentials.kick
            - essentials.kill
            - essentials.setwarp
            - essentials.signs.create.*
            - essentials.signs.break.*
            - essentials.spawner
            - essentials.thunder
            - essentials.togglejail
            - essentials.top
            - essentials.tp
            - essentials.tphere
            - essentials.tpo
            - essentials.tpohere
            - essentials.tppos
            - essentials.tptoggle
            - essentials.unban
            - essentials.unbanip
            - essentials.whois
            - essentials.world
            - essentials.afk
            - essentials.back
            - essentials.back.ondeath
            - essentials.balance
            - essentials.chat.shout
            - essentials.compass
            - essentials.home
            - essentials.depth
            - essentials.mail
            - essentials.mail.send
            - essentials.me
            - essentials.msg
            - essentials.pay
            - essentials.portal
            - essentials.powertool
            - essentials.sethome
            - essentials.signs.use.*
            - essentials.signs.create.disposal
            - essentials.signs.create.mail
            - essentials.signs.create.trade
            - essentials.signs.break.disposal
            - essentials.signs.break.mail
            - essentials.signs.break.protection
            - essentials.signs.break.trade
            - essentials.suicide
            - essentials.tpa
            - essentials.tpaccept
            - essentials.tpahere
            - essentials.tpdeny
            - essentials.warp
            - essentials.warp.list
            - essentials.worth
            - commandSigns.create
            - worldedit.*
            - essentials.backondeath
            - spoutessentials.title
            - spoutessentials.playmusic
            - spoutessentials.playgmusic
            - spoutessentials.stopgmusic
            - spoutessentials.music
            - multiverse.access.*
            - worldguard.god
            - worldguard.ungod
            - worldguard.heal
            - worldguard.heal.other
            - worldguard.stack
            - worldguard.stack.illegitimate
            - worldguard.region.*
            - vanish.standard
            - godpowers.godmode
            - godPowers.godmodeonlogin
            - godPowers.jesus
            - godPowers.heal
            - godPowers.superjump
            - godPowers.demigod
            - essentials.clearinventory
            - falsebook.anyic
            options:
                rank: '200'
            inheritance:
            - constructor
            worlds:
                Clean:
                    permissions:
                    - essentials.item
                    - essentials.give
                    - essentials.time.set
                    - essentials.time
                    - godPowers.zeus
                    - godPowers.gaia
                    - godPowers.vulcan
                    - bukkit.command.time.add
                    - bukkit.command.time.set
        VIP:
            permissions:
            - bukkit.command.whitelist.add
            - bukkit.command.whitelist.remove
            - bukkit.command.whitelist.reload
            - essentials.nick
            - null
            options:
                rank: '100'
            inheritance:
            - moderator
            prefix: '&0(&eVIP&0)&7 '
    users:
        xxxxxxxxx:
            group:
            - owner
        xxxxxxxx:
            group:
            - VIP
        xxxxxxxx:
            group:
            - admins
        xxxxxxxx:
            group:
            - VIP
        xxxxxx:
            group:
            - VIP
        xxxxxxx:
            group:
            - admins
        xxxxxxx:
            group:
            - admins
        xxxxxxx:
            worlds:
                admins:
                    group:
                    - admins
            group:
            - moderator
            options:
                group: builder
        xxxxxx:
            group:
            - admins
        Darkscathe:
            group:
            - builder
    worlds:
        world_nether:
            inheritance:
            - world
        omfg:
            inheritance:
            - clean
        testing:
            inheritance:
            - clean
    
    Config:
    permissions:
        backends:
            file:
                file: permissions.yml
        backend: file
        superperms:
            disable-unmatched: false
            enable: true
            matched-permissions: true
            raw-permissions: true
            debug: false
        allowOps: false
        debug: false
        basedir: plugins\PermissionsEx
        createUserRecords: false
    
    I xxxxx the names to keep confidentiality :) Please help as we are in preparations to go public and cannot till this is fixed. TY [diamond][diamond][diamond]'s for your help
     
  29. I see some weirdness in your config.

    The worlds section:
    Code:
    {
      "worlds": {
        "omfg": {
          "inheritance": [
            "clean"
          ]
        }, 
        "testing": {
          "inheritance": [
            "clean"
          ]
        }, 
        "world_nether": {
          "inheritance": [
            "world"
          ]
        }
      }, 
    There isn't any world defined as clean.

    One of the users has data for a world named admins (which doesn't exist), and the VIP group inherits permissions from the moderator group (and others), which has access to all the commands (kick, ban, etc).

    The inheritance chain looks like this, and within this chain, those bukkit.command nodes are listed: VIP <- Moderator <- constructor <- builder <- default

    I'm also seeing some redundancy in the commands as well (permission nodes following a * node). I don't know how many nodes essentials uses, but it might be worth looking at changing it to essentials.* at the end of the list and putting the removal nodes before the wildcard to take away the commands that you don't want each group to have. If the denied commands list is shorter, it would make it a lot easier to keep track of (and debug).

    As I don't know exactly what you have in mind for your server, I can't really suggest much except to start small. Define perhaps three groups for a single world and add permissions in smaller batches. From what I can tell of your config, it's somewhat complicated (especially with all the inheritance you set up) and it would be very easy to get things mixed up.
     
  30. Offline

    goodoletom

    wat r /kick and /ban nodes?
     
  31. When dealing with permissions, each command on a server has it's own permission setting, called a node.

    For example, the /kick command built into the multiplayer server has the permission node named bukkit.command.kick (if you are using the built-in bukkit permissions).

    If you are wondering what the nodes are for those commands, the link to the default bukkit commands page has been posted earlier in the thread and it's also linked from the old DefaultPermissions plugin that was made obsolete when bukkit added said commands to the server code.
     

Share This Page