In the latest build Version 318 of Redprotect we notices all our players have empty Flag-GUIs
and cant use many commands.

after a bit of testing arround with the permissions, we found out that
the parrent permission redprotect.user does not work.

This is including all permisions for commands and flags of it.

• we added the direct permissions to add the flag gui
  in the Flag-GUI you see 3 icons. these flag where added extra with direct permission

we added redproct.flag.defaults

it looks normal now.

The interesting point is: if we test it on the server WITHOUT Vault plugin
then all works fine and also the redprotect.user is recognized correctly
So this issues just appears with Vault on the Server (and maybe also only with Pex?)

Server: Spigot 1.15.2
Redprotect Version: RedProtect-7.6.6-b318-Universal
other Plugins: Vault_1.7.2, Multiverse-Core-4.1.1-SNAPSHOT, PermissionsEx-1.23.4

I have the same problem.

You can disable vault permissions on config. Use vault only if you need to control redprotect permissions per world.

I'll investigate this issue.

I only found the line in the list that indicates Vault.
Is the line misspelled?

 use-valtapi = true

If this is True, the users under /rp flag have no flags to select.

If I now set this to false, you have no authorization to use this command even though the zones are owned.

I may have an idea.
can't you make it easier as a server owner in the world?
For example, give /rp guizone WORLD. Then the server owner gets all flags displayed in the gui that exist in the world. Now the server owner can activate and deactivate which flags are displayed to the user under /rp zone.

Is that doable?

As an extension, you can also assign rank-based flag rights with the gui z.b / rp guiZone WORLD RANG/GROUP

For the moment we design it fitting to the vault permissions.
The problem isself not solved but for it that way

For our server it does because we are using the way vault handles it now - so with the per world permissions.

we also notriced in the plugin.yml the redprotect.user redprotct.admin does not exists anymore so we are using the other partent permissions now related to plugin.yml

If you want, you can close this issues.

Well ok, we accepted the new way permissions are handled