PEX per world permissions not working
01Andi opened this issue · 8 comments
Hello everyone
I'm trying to use PEX for setting up some per world permissions but only the normal permissions work. Tho ones specified for a single world don't work.
My permissions.yml file:
] Edit by Stormbow: Moved permissions.yml file contents to Pastebin: https://pastebin.com/5envpFBk [
Check out my Multiworld Example. You're missing inheritance sections in all of your groups. This can cause PEX to malfunction on Minecraft 1.9+ servers.
In your unedited post, you had the line schema-version: 1
near the end of the file. This line needs to come before the users:
section, as shown in the example above. This error can cause PEX to malfunction in Minecraft 1.6.4+ servers.
Also, be sure you're using the latest version of PEX (1.23.4) found on this page.
Once you have the above errors corrected, use PEX Debug Mode to find out which permission node(s) are missing from your setup. If you have any trouble interpreting the Debug output, copy it to Pastebin and I'll tell you what you need to do with it.
I'm going to test your solutions this evening. It's a MC 1.8 server.
Anyway i'm going to try it with both of your solutions.
Thank you very much for your fast answer.
Did you use PEX Debug Mode to see what was missing?
You still haven't told me exactly what is not working.
@Stormbow
The best example is the /gamemode command. If I want to allow it for a specific world, it doesn't work. If I set the same permission node to the global permissions, it works. This is the same for every permission specified only for one or two worlds.
In the debug mode I see, that every permission specified in the "worlds" section doesn't work.
So:
global perms work but the world specific ones don't.
@Stormbow
Now my config.yml looks like this, but it's still not working.
https://pastebin.com/TKsCgqxX
Now we're getting somewhere. ;-)
In one case/group/world— bauarbeiter > Lobby —you misspelled "essentials", so the node wouldn't grant access to the /gamemode command in that instance. (The node actually wouldn't do anything, positive or negative, as I mention in the next paragraph.)
Next, we look at the Multiverse permission nodes and compare those to the nodes that you've negated and we find out that mv.bypass
.anything doesn't exist, so none of those negated nodes or granted nodes would do anything at all on the server, especially not allowing (or disallowing) the use of the /gamemode command. They simply have no effect at all, positive or negative; they just make the file longer. (I think what you may have been attempting to do was bypass Worldguard, which has a real permission node.)
If you would use the PEX Debug Mode that I mentioned twice— three times, as of this comment ;-) —you'd get server console output that tells you, in detail, which permission nodes are being checked for the user when they attempt to use the (essentials.gamemode
) /gamemode command. And then, when a permission node prevents the /gamemode command from functioning, you'd see that node mentioned in the server output also. You add that node to the group and then the group can— usually, most likely —use the /gamemode command. And if they can't, Debug Mode a second time would tell you what else is preventing the command.
If you have any problems interpreting the Debug Mode output, Pastebin it for me and I can tell you what to give the group. :-)