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

    toastieness

    How do i get prefixes to work?
     
  3. Offline

    Stormbow

    Post your plugin list, config.yml for chatmanager, and permissions.yml and we can try to help you.
    I suspect there's a chat plugin conflict going on.

    Post your permissions.yml (in CODE tags).

    I believe it's because your admin group has 100% access to everything (which includes ban-ip immunity).

    I don't understand what you're asking. You want to add a builder group to your server? What do you mean about text turning red?

    Please be more specific: include config and permissions files (in CODE tags) and screenshots if possible.

    In the ChatManager folder's config.yml, set
    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Sep 9, 2018
  4. Offline

    Enykey

    Code:
        Admins:
            prefix: '&0(&4Admins&0)&7 '
            options:
                rank: '0'
            permissions:
            - -modifyworld.mobtarget.*
            - -bukkit.command.op.give
            - -bukkit.command.op.take
            - -bukkit.command.op
            - '*'
    
    Yes admin group has 100% access to everything, but ban by admin group nickname is worked. Wich permissions give ban-ip immunity?
     
  5. Offline

    Stormbow

    Which other plugins are you using? The
    permission you are giving your admins gives them EVERYTHING from ALL plugins.

    Some plugins, like Essentials, have permissions like
    which are included in
    and keep whoever has those permissions from being affected. The permission
    may be what is causing you to be unable to ban your admin's ip address. (Why you would want to ban your admin's IP is beyond my understanding however. If someone does something that makes me want to ban them, I would definitely
    their butt and THEN I would ban them. heh)
     
    Justin The Cynical likes this.
  6. Ok, I'm a bit confused. The post you linked to (http://forums.bukkit.org/threads/ad...row-is-today-1-0-0.18140/page-145#post-867381) is asking about multiverse access (which the debug log shows the nodes, multiverse.portal.access.* and multiverse.access.* if the player is trying to visit the world via portal), and a mention of a mod not being able to add a user to a group (to which there isn't any nodes listed as being checked for that command). The node for group management is permissions.manage.membership.<groupname>. Replace groupname with the group you want them to manage. If it's all of them, use * to cover all the groups in your permissions.

    For reference, https://github.com/t3hk0d3/PermissionsEx/wiki/Commands#wiki-users-group-management covers the nodes (and I just verified the nodes and updated it to match:)).
     
  7. Offline

    Enykey

    Plugins: Backup, CraftBukkitUpToDate, Fast Mining, iConomy, KitPlugin, Lockette, LogBlockQuestioner, MCSL, Pail, PermissionsEx, PlgDisableCmd, Questioner, Rakamak, Sortal, WorldEdit, WorldGuard, ChatManager, Modifyworld, Permissions, AdminCmd, BaseBukkitPlugin, ChestShop, Dynmap-WorldGuard, dynmap, Jobs, LogBlock, MobArena, Towny, TownyChat

    Stormbow you little dont understand me. let see step by step:
    We have nickname "Admin" in admin group with ip 192.168.0.10 (for ex.)
    and some user "User" with ip 192.168.0.5.
    When i make ban-ip 192.168.0.5 he CANT login under nick name "User" from banned ip 192.168.0.5

    BUT he CAN login under nick name "Admin" from banned ip 192.168.0.5
     
  8. Modifyworld doesn't do IP level banning, only player name.

    Bukkit can do IP level banning, but what you are describing is something I've never seen or heard of.

    1. Two machines: server on .9, the client on .2
    2. Start up bukkit and PEX (whitelist in modifyworld turned off)
    3. Connect
    4. Run the command "ban-ip X.X.X.2"
    5. Disconnect/reconnect, client is denied.
    6. Turn on allow-ops in the config.yml for PEX, repeat step 5, still can't connect
    If you have someone able to connect just by using a different username, you have something else going on, I don't see this as a PEX issue. :eek:
     
    Stormbow likes this.
  9. Offline

    Enykey

    Client connect under Nickname from admin grop PEX?
    Code:
    05:31 PM [INFO] Enykey [/91.185.49.160:4524] logged in with entity id 304438 at ([world] 229.86651274526605, 65.0, 966.3294149436547)
    05:31 PM [INFO] [Rakamak] Enykey is identified.
    05:31 PM [INFO] Connection reset
    05:31 PM [INFO] Enykey lost connection: disconnect.quitting
    05:31 PM [INFO] [Backup] Last player left, backing up!
    05:32 PM [INFO] CONSOLE: Banning ip 91.185.49.160
    05:32 PM [INFO] [Backup] PLAYERS: 0
    05:32 PM [INFO] [Backup] Stopped last backup, start with normal backup cycle!
    05:32 PM [INFO] Enykey [/91.185.49.160:4528] logged in with entity id 305342 at ([world] 229.86651274526605, 65.0, 966.3294149436547)
    05:33 PM [INFO] [Rakamak] Enykey is identified.
     
    as you can see i can logon after ban-ip
     
  10. Yes.
    Code:
        Admins:
            prefix: '&c[Admin]&2'
            suffix: '&f'
            options:
                rank: '0'
            permissions:
            - '*'
            inheritance: null
    allowOps is set for true
    ops.txt has the player name in it
    banned-ips.txt has the IP address of the client in it
    Player name is a member of the Admins group
     
    Stormbow likes this.
  11. Offline

    Lemon200

    Hi! I'm having a weird problem with this plugin. I have set 3 groups, default, Moderators and Admins. My problem is that the players in default group can destroy blocks but can't build. This is causing me some serious issues, cause they can destroy also buildings which i have protected with WorldGuard. There is my permissions file:
    Code:
    groups:
        Default:
            default: true
            permissions.build: true
            permissions:
            - commandbook.who
            - commandbook.rules
            - commandbook.spawn
            - commandbook.home.teleport
            - commandbook.home.set
            - commandbook.mute
            - commandbook.bans.isbanned
            - multiverse.access
            - multiverse.teleport.self.NAME
            - multiverse.core.spawn.self
            prefix:
        Moderaattorit:
            default: false
            inheritance: default
            permissions:
            - day.command.day
            - day.command.night
            - commandbook.teleport
            - commandbook.teleport.other
            - commandbook.locations.coords
            - commandbook.slap
            - commandbook.kick
            - commandbook.bans.ban
            - commandbook.bans.unban
            - worldguard.god
            - worldguard.region.define
            - worldguard.region.addowner.own
            - worldguard.region.addowner
            - multiverse.sleep
            prefix: VALVOJA
        Adminit:
            default: false
            permissions:
            - '*'
            prefix: ADMIN
    
    Hope you can help!
     
  12. I'm going to try. :)

    Can not build but can destroy? This is weird. Are you using modifyworld and is it enabled?

    FYI, the "permissions.build: true", it does nothing under PEX, I'd remove it. Modifyworld is the plugin that you want to use for allowing and denying building.
     
  13. Offline

    Pomme72

    Stupid. :p
     
  14. Offline

    Lemon200

    Thanks for you reply! I removed that permission and disabled modifyworld, still no change. I removed all my WorldGuard regions, no progres. And i noticed that default players can't build inside my spawn building. They can build about 17 blocks away of it. But still, they can destroy it. I didn't find any permissions related settings from WorldGuard's config.
     
  15. Offline

    Killer_Klownz

    I just started using this is. Here's my permissions.yml. Im pretty sure it's not right. Can some one take a look at it?
     
  16. Umm, that wasn't what I meant when I asked about modifyworld. :)

    Under PEX alone, modifyworld and it's permission nodes are the way to allow or deny building. If it's not enabled and the nodes are not present in a group definition, members of that group should not be able to build or destroy anything.

    In fact, I just tried your permissions:
    ops.txt was empty
    the config.yml in the modifyworld directory had enable set to true

    I connected and tried to place a block and was denied the ability.

    As for the spawn building, I think that's bukkit/minecraft and the spawn radius setting in the server.properties file. I turned mine to 0 and let my plugins deal with protecting any spawn buildings.:)

    Put it in single quotes. (- '*' not - *):)

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

    Killer_Klownz

    I fixed, but it's still red. Take a look here. (Also... Did I set it up right?)
     
  18. Offline

    Lemon200

    Ok i got some progres. I enabled modifyworld, and gave the default group all the permissions for modifyworld. Still same problem, but now there shows up an error message to chat: ''Sorry, you don't have enough permissions.'' Very weird cause i pasted ALL the permissions(not - modifyworld.*) Before there were no error messages.

    UPDATE: Ok i set the spawn redius to zero and now the default groupers can't build anywhere. The same message appears. And i set the inform setting from mofifyworld to true.
     
  19. Offline

    Flamers

    I am trying to get it so that when in the second world you can only use basic permissions (ban etc) But it still lets me have all perms (as admin)

    Code:
    groups:
        User:
            default: false
            info:
                prefix: '&b'
                build: true
                suffix: ' MOD'
            permissions:
            - admincmd.player.afk
            - admincmd.player.roll
            - admincmd.player.list
            - lockette.user.create.*
            - factions.kit.fullplayer
            inheritance:
            - default
        Default:
            default: true
            permissions:
            - factions.join
            - factions.claim
            - factions.help
            - factions.home
            - modifyworld.chat
            inheritance: []
            info:
                prefix: ''
                build: true
                suffix: ''
        SemiAdmin:
            default: false
            info:
                prefix: '&b'
                build: true
                suffix: ' MOD'
            permissions:
            - '*'
            inheritance:
            - VIP
            worlds:
                glacier_city:
                    permissions:
                        - -'*'
                        - admincmd.player.afk
                        - admincmd.player.roll
                        - admincmd.player.list
                        - admincmd.player.ban
                        - admincmd.player.kick
                        - modifyworld.*
        Admins:
            default: false
            info:
                prefix: '&b'
                build: true
                suffix: ' MOD'
            permissions:
            - '*'
            inheritance:
            - semiadmin
            worlds:
                glacier_city:
                    permissions:
                        - -'*'
                        - admincmd.player.afk
                        - admincmd.player.roll
                        - admincmd.player.list
                        - admincmd.player.ban
                        - admincmd.player.kick
                        - modifyworld.*
        VIP:
            default: false
            info:
                prefix: '&b'
                build: true
                suffix: ' VIP'
            permissions:
            - multiverse.tp
            - multiverse.list
            - worldedit.navigation.*
            - admincmd.weather.*
            - worldguard.region.bypass.*
            inheritance:
            - user
            worlds:
                glacier_city:
                    permissions:
                        - -'*'
                        - admincmd.player.afk
                        - admincmd.player.roll
                        - admincmd.player.list
                        - modifyworld.*
    users:
        flamers1500:
            group:
            - Admins
            permissions: ''
        aparke1:
            group:
            - SemiAdmin
            permissions: ''
        hrbfcrule:
            group:
            - SemiAdmin
            permissions: ''
    
    (Removed users to shorten post)
     
  20. Offline

    GOKUSSL4

    Code:
        Legend:
            default: false
            permissions:
            - antihack.canblockinvalidlocation
            - antihack.caninfinityitem
            - antihack.canunknownitem
            - bcs.commands.toggle
            - cf.allowfly
            - essentials.clearinventory
            - essentials.kill
            - essentials.tp
            - essentials.unlimited.item-all
            - essentials.weather
            - FullChest.create
            - jail.modifyjail
            - lwc.Admin
            - mobdisguise.*
            - multiverse.access.Arvina
            - war.*
            - worldedit.*
            inheritance:
            - Mod
        Admin:
        default: false
        permissions:
            - '*'
        inheritance:
            - Legend
    your spacing for Admin at the bottom doesn't match the rest.
    Code:
        Legend:
            default: false
            permissions:
            - antihack.canblockinvalidlocation
            - antihack.caninfinityitem
            - antihack.canunknownitem
            - bcs.commands.toggle
            - cf.allowfly
            - essentials.clearinventory
            - essentials.kill
            - essentials.tp
            - essentials.unlimited.item-all
            - essentials.weather
            - FullChest.create
            - jail.modifyjail
            - lwc.Admin
            - mobdisguise.*
            - multiverse.access.Arvina
            - war.*
            - worldedit.*
            inheritance:
            - Mod
        Admin:
            default: false
            permissions:
            - '*'
            inheritance:
            - Legend
    this should give you an idea what went wrong.
     
  21. Offline

    marsthegod1

    hi im having some trouble between chatmanager/permissionsEX and factions, for somereason on the console when a person has joined a faction and talks, there message shows up but no name, i was wondering if anyone else has had this issue or knows how to repair it.

    thanks in advance, marsthegod1.
     
  22. Offline

    fullofcash

    Can someone help?
    Getting this error.
    [​IMG]
     
  23. What do you mean still red? As in the line is red in notepad++? If so, verify that you don't have a tab where there should be spaces.

    Also, the link goes to a 404 equivalent message.:)

    Greetings flamers. Good to see you, you do really good work in the mobarena thread.:)

    Now, on to your question. I'm assuming you are using a file backend for the permissions.

    Looking over your permissions, you are running into one of the 'quirks' of PEX, especially when dealing with multiworld permissions.

    PEX, as you may know, uses a top to bottom method of permissions checking (think of it as a permissions firewall). Once it finds a match, it stops looking. PEX will also consider globally defined permissions first before world specific permissions. As you have * defined globally for the admin and semiadmin, PEX finds that first and never checks the list for glacier_city.

    What I would do in this case is:
    • Remove the inheritance from the semiadmin and admin groups as they have * for global permissions and identical permissions for glacier_city (You could have admins inherit from semiadmins as well and use the admins group to specify additional permissions, if any). Treat groups with everything as stand alone groups when thinking of inheritance. This is what I do as a * node covers everything already and inheriting from another group makes for redundancy and overly complicated output when checking permissions from the console/in-game.:)
    • Remove the global entry and put * in it's own world specific entry. Assuming the primary world name is survival, I believe this will work as you want:
      Code:
          Admins:
                  default: false
                   info:
                       prefix: '&b'
                       build: true
                       suffix: ' MOD'
                   permissions:
                   worlds:
                       survival:
                           permissions:
                           - '*'
                       foo:
                           permissions:
                               - -'*'
                               - admincmd.player.afk
                               - admincmd.player.roll
                               - admincmd.player.list
                               - admincmd.player.ban
                               - admincmd.player.kick
                               - modifyworld.*
    Does that work for you?

    Please don't post sc
    Please don't post screenshots, it's not necessary and makes it harder to read the forum.:)

    What you are seeing in game, "an internal error has occurred while attempting to perform this command" could be any number of things. We need to know exactly what command you tried to run, the error from the server.log (or console), your permissions if you are using a file backend, and your config.yml files for PEX at a minimum.

    Please either link to them in a pastebin, pastie, or equivalent, or here in code tags (use the {}# button at the top of the editor window).

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

    Zaeici

    Hey everyone, I'm getting an error: http://pastebin.com/J9LvpQ0q
    Heres my permissions.yml file: http://pastebin.com/0UzFgmeH
    I'm using the CraftBukkit Auto Installer by ImminentFate so I don't know if thats causing the problem. I have googled and searched on the CraftBukkit forum but I don't really understand how this all works. Please help!
     
  25. Offline

    Flamers


    Thanks, I try and help others! Ok the permissions kind of work.... The glacier_city perms work fine but the main world perms don't work at all...

    This is the current set up:

    Code:
    groups:
        User:
            default: false
            info:
                prefix: '&b'
                build: true
                suffix: ' MOD'
            permissions:
            - admincmd.player.afk
            - admincmd.player.roll
            - admincmd.player.list
            - lockette.user.create.*
            - factions.kit.fullplayer
            inheritance:
            - default
        Default:
            default: true
            permissions:
            - factions.join
            - factions.claim
            - factions.help
            - factions.home
            - modifyworld.chat
            inheritance: []
            info:
                prefix: ''
                build: false
                suffix: ''
        SemiAdmin:
            default: false
            info:
                prefix: '&b'
                build: true
                suffix: ' MOD'
            permissions:
                worlds:
                     mainworld:
                         permissions:
                         - '*'
                     glacier_city:
                         permissions:
                         - admincmd.player.afk
                         - admincmd.player.roll
                         - admincmd.player.list
                         - admincmd.player.ban
                         - admincmd.player.kick
                         - modifyworld.*
                         - multiverse.tp
                         - multiverse.list
        Admins:
            default: false
            info:
                prefix: '&b'
                build: true
                suffix: ' ADMIN'
            permissions:
                worlds:
                     mainworld:
                         permissions:
                         - '*'
                     glacier_city:
                         permissions:
                         - admincmd.player.afk
                         - admincmd.player.roll
                         - admincmd.player.list
                         - admincmd.player.ban
                         - admincmd.player.kick
                         - modifyworld.*
                         - multiverse.tp
                         - multiverse.list
        VIP:
            default: false
            info:
                prefix: '&b'
                build: true
                suffix: ' VIP'
            permissions:
                worlds:
                    mainworld:
                        permissions:
                            - multiverse.tp
                            - multiverse.list
                            - worldedit.navigation.*
                            - admincmd.weather.*
                            - worldguard.region.bypass.*
                            - admincmd.player.afk
                            - admincmd.player.roll
                            - admincmd.player.list
                            - lockette.user.create.*
                            - factions.kit.fullplayer
                            - modifyworld.*
                    glacier_city:
                        permissions:
                            - -'*'
                            - admincmd.player.afk
                            - admincmd.player.roll
                            - admincmd.player.list
                            - admincmd.player.ban
                            - admincmd.player.kick
                            - modifyworld.*
                            - multiverse.tp
                            - multiverse.list
    (I'm an Admin)
     
  26. Merry X-mas !
     
  27. Hmm, looking at the log (thank you for posting that as well, it helps narrow down problems quickly!), it appears that something is knocking PEX out. It could be a config file problem, and not necessary the permissions.yml file.

    *checks permissions file formatting at http://yaml-online-parser.appspot.com/ *

    Ah, you have a config problem in it. The admin section is missing the dash for the wildcard node. Also, the * needs to come last so the negation nodes are found. Once PEX finds that * node (which allows everything), it will stop checking. And since you are trying to take away some permissions to that group, it will never do so with the current setup. Make it look like this:

    Code:
            permissions:
            - -craftbukkit.command.stop
            - -craftbukkit.command.op
            - '*'
    Subtle formatting issue in your config. :)

    The worlds: line for the VIP, SemiAdmins and Admins groups is indented too far, and PEX is parsing the world specific permissions as part of the global permissions dataset. Lining up the worlds: line with the previous permissions: line seems to be good enough for PEX (at least on my test server).
    Code:
            permissions:
            worlds:
                mainworld:
    Gotta love YAML at times, eh?:)

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

    Flamers

    Oh yes <3 I ran it through the parser and it's obviously "correct" so gave me no error.

    Getting Trolled on Christmas Eve! YAY!

    EDIT: Got it working! I might write a wiki page on multi world if I get the time :) (and if I can?)
     
  29. Offline

    Zaeici

    Justin I LOVE YOU! Thanks so much :)
     
    Justin The Cynical likes this.
  30. Glad to help.:)
     
  31. Offline

    fullofcash

Share This Page