Question How do I remove all permissions for Guest using PEX

Hi,

I have a group in my permissions called Guest. I plan on using this group for players who have been banned and then allowed back onto the server. This means I want the Guest group to be able to build stuff in my world and chat in the public chat but I don't want them to be able to send private messages to anyone or be able to protect their builds or chests with land claims

I want Guests to be able to

• Build things in the world on unclaimed land
• Place chests to store their stuff in
• Mine in the designated mining areas within the world but nowhere else
• Chat in public open chat
• Use /help
• User /rules
• see the motd

I don't want Guests to be able to

• Mine anywhere except the designated mining areas
• Protect their builds or chests with with a land claim
• Send private messages or whispers to anyone
• Use any kits
• Purchase anything (once my world's economy has been set up - basically I want a guests balance to be constantly zero)
• Be able to trade items with other players or NPCs
• use /sethome
• use /teleport
• Set their spawn point
• /tp to a player
• Request that a player /tp to them
• User /back
• Recover their items after they have died

Basically I want all of features that members have access to, to be disabled for guests.

The idea behind this is - everyone joins as a Member with all the Members benefits right off the bat but if they don't behave, they will be banned for 30 days and lose all of their benefits as a Member, being demoted to Guest and having to earn their way back up to Member level by showing that they have changed their ways. (this will take a period of time, weeks, months depending on what they were banned for.

Then, if they continue to misbehave or if they try to subvert the 30 day ban by using another account, they will then get a permanent IP ban.

I have tried to set this up using PEX but when I got a test user to login and demoted them to Guest, they were still able to make land claims, teleport to spawn. As you can also see from the paste of my permissions.yml file below, I have also tried to negate permissions for guest using this format - -name.name.name

Here is a paste of my PEX permissions.yml file https://pastebin.com/xjFdVJFx

However, even with the permissions negated, it still did not work when my test user was put into the Guest group, they still had access to the permissions I had tried to negate.

The plugins I use: PermissionsEx, Vault, GriefPrevention, Citizens, Essentials, EssentialsSpawn
Server version: CraftBukkit version git-Bukkit-d219213 (MC: 1.11.2) (Implementing API version 1.11.2-R0.1-SNAPSHOT)

Here is the config.yml file for PEX - https://pastebin.com/PkcSXttD
Here is a paste of my PEX permissions.yml file https://pastebin.com/xjFdVJFx
Here is my config.yml file for EssentialsX - https://pastebin.com/bjeda108
Here is my config.yml file for GriefPrevention - https://pastebin.com/987sHPfX

 

@KitsuneBoy
Are you sure the test player is not OP, since ops have access to all permissions (even if you try to take them away)? That's the only reason I can think of for ignoring permission removal.

 

Thanks @Zombie_Striker my test user was not OP but I have managed to solve the problem anyway by removing all of their user data from the server and getting them to rejoin. I am not sure what was going on there but it seemed that the old user data was interfering with my ranking system.

They were definitely ranked correctly and in the right group on the ladder, so I don't know what happened. Perhaps it was because I have two ladders that users join automatically when they first join the server

default
patreon

and the ranks on the patreon ladder are higher (Guest rank = 1000, while Not-Patreon = 700) than the guest rank on the default ladder. However, after deleting their user data and having them rejoin, they once again automatically joined the default groups from both ladders.

Member
Not-Patreon

Then demoting them to Guest on the default ladder, while leaving them as Not-Patreon on the patreon ladder, set their permissions as they were before I deleted their user data. Only this time they had the correct permissions as set by those groups

I will have to investigate that further before moving on the next stage of development as it appears I have a major flaw in my design.