Plugin Help Default group [member] has no perm for /fly and is being allowed the perm HELP!

Ok, so my issue here is that PermissionsEx my default group is [Member] so now if a new player joins my server PermissionsEx auto sets the group to the default [Member] the permissions for that group does not have essentials.fly but is allowed to run the command /fly and enable and disable fly. But if I run the command /pex user {user} set group default although they're already the default group they are not able to run the command /fly anymore please reply this is urgent I do not know why the permissions do not load correctly if thats the problem what do i do????????

When I Set the Player to Member after already being in that group.
[18:51:04] [Server thread/INFO]: Rageskk issued server command: /pex user _KillAurq group set default
[18:51:11] [Server thread/INFO]: _KillAurq issued server command: /pex
[18:51:14] [Server thread/INFO]: _KillAurq issued server command: /pex user
[18:51:14] [Server thread/WARN]: [PermissionsEx] User _KillAurq tried to access chat command "pex user", but doesn't have permission to do this.
[18:51:26] [Server thread/INFO]: [AntiCheat+] [0;31;1m_KillAurq attempted to attack faster than normal. (min=85 | them=0[m
[18:51:28] [Server thread/INFO]: [AntiCheat+] [0;31;1m_KillAurq attempted to attack something without looking at it.[m
[18:51:29] [Server thread/INFO]: [0;37;1mUser groups set![m
[18:51:32] [Server thread/INFO]: [AntiCheat+] [0;31;1m_KillAurq attempted to send packets too fast![m
[18:51:33] [Server thread/INFO]: _KillAurq issued server command: /fly
[18:51:33] [Server thread/INFO]: §c_KillAurq §4was denied access to command.
[18:51:35] [Server thread/INFO]: _KillAurq issued server command: /fly
[18:51:35] [Server thread/INFO]: §c_KillAurq §4was denied access to command.
[18:51:36] [Server thread/INFO]: [AntiCheat+] [0;31;1m_KillAurq tried to ascend on the y-axis without hitting the ground.[m
[18:51:38] [Async Chat Thread - #0/INFO]: [0;33;22m[[0;32;22m0[0;33;22m][m<[0;37;1m[21m**[m[0;37;1mZzZPvP [0;37;1m[0;30;22m[21m[[0;37;22mMember[0;30;22m[21m][0;37;22m_KillAurq[m> g[m

WHY ARE THESE ONES NOT GETTING DENIED?

[18:51:45] [Server thread/INFO]: _KillAurq issued server command: /fly
[18:51:49] [Async Chat Thread - #0/INFO]: [0;33;22m[[0;32;22m0[0;33;22m][m<[0;37;1m[21m**[m[0;37;1mZzZPvP [0;37;1m[0;30;22m[21m[[0;37;22mMember[0;30;22m[21m][0;37;22m_KillAurq[m> l[m
[18:51:52] [Server thread/INFO]: _KillAurq issued server command: /fly

Again, my issue down to the basic is New players that PermissionsEx sets to member as default group they are allowed perms that are not listed in that group. But if i set there group to the same group [Member] as PermissionsEx did as the default group it removes the commands that are not in that group. BUT there group hasnt been changed?!?!?!?!

 

www.pastebin.com with your permissions yml file, please

From the sounds of things, you have a group called Default with a suffix denoting a member, and a group called Member and one of those is the actual defaulted true rank, and your command is doing something else

 

Here is the pastebin
http://pastebin.com/KVmDxreR

 

In your pastbin there isn't the perm for /fly Go over and double check your perms and you will see!

 

But the issue is that they have /fly and shouldnt. but when they first join they do until i set there rank to the same rank like they come in as Member. and i do /pex user {username} group set member and then they dont have perms. I dont know if im expaining it correctly.

 

You have multiple groups marked as "default: true" (your member rank and the rank that has fly)
which causes the permissions system to say "Everybody gets everyrhing, weeeeeeeee, I dont give a rats arse!"

Only one group can be default: true

 

Omg.. I knew it had to be somthing stupid but it had not crossed my mind that... Exotic had the default true... thats were it is coming from and why they could also use /kits and open exotic.
THANK YOU. . . for dealing with this stupidity lol!

 

Psssst......
If its solved mark as solved!

 

New to this how? xD

 

Its only obvious once you've seen the solution to that problem before. Permission systems do really weird things with the default: true that a truely friendly plugin should handle differently, and while parsing at load up, should detect multiple trues and just self-destruct and be all "I refuse to work until you fix this" rather than just saying "well, the instructions say only one is default: true, I warned them, they clearly must know what they're doing ..."