Description

Sometimes, behavior like wildcards permissons take priority over more specific permissions is needed in some cases.

For example, consider such a situation:
There are 3 levels of permisson groups in server: default, admin, super_admin

• default is applied to common players.
• admin is applied to OPs, but some vanilla commands (such as fill, setblock, summon, etc.) are disabled via Vanilla Permissions mod, in order to limit these admins' permissions.
• super_admin is applied to some specific OPs. Players in this group can execute all commands without any limitation.

Clearly, there is a natural permission group track like default->admin->super_admin, which means the extension of admin permissions.

However, when I:

• Set minecraft.commands.xxx (specific permissions) denied in admin
• Set minecraft.commands.* (wildcard permissions) allowed in super_admin

Players who are in both admin and super-admin groups still cannot use those specific commands.
Even when I set the weight of group super_admin > admin, the wildcard permissions are still ignored.

Proposed Behaviour

I think it's better to add something like an option in config to change this default specific-wildcard permission overwrite rule.

Extra Details

No response

Sure, the inherit from admin to super_admin is not proper. Actually, I set these perm groups separately, but let those super-players have both parent groups admin and super_admin.

My actual meaning is that, generally, permissions in super_admin should override admin unconditionally, as I have given it higher weight than admin.
However, the default behavior of specific permissions take priority over wildcards breaks this expectation.

if you want your super_admin group to have every permission, there is no reason for you to make it inherit the permissions from your admin group