WhiteThunder

Goldie, as stated earlier, the "design flaw" you described is not a design flaw as this plugin is already designed to sync permissions without reloading. You are either experiencing a bug with the plugin or an issue with your oxide permission groups, likely the latter.

Have you reproduced this when granting permissions to individual players? Have you reproduced it with other groups such as default and admin? Have you reproduced this on multiple servers using the same configuration (such as a local test server)? Can you also paste your configuration? Are you opening the backpack before the permission is granted?

I always clone my live server and then remove myself from admin so i'm like any other player and then I will grant myself the group permissions that should have access to the extra backpack rows. And it only started showing extra rows of packpack space after I reloaded the plugin.

If you say that it should already been built in then maybe it has been a bug from my side. So far I havent had any complaints about it so it might work. But ill ask around to my players.

WhiteThunder

Following up with @Goldie to confirm I misunderstood. This plugin hooks when permissions are granted/revoked to individual users or groups, in order to update the backpack capacity, but it does not detect when a user's group membership changes. The plugin examples you provided are mostly stateless so while they don't specifically hook events around group membership, they don't need to because they simply check permissions on demand (e.g., when a kit is redeemed). The simplest solution here would be to just check the permissions at the time a backpack is opened and change the capacity if needed. Then we can even remove some of the hook code around permissions being granted/revoked.

I see your point that group membership often changes as players join or lose groups due to payments or other events, so I'll see about making this change for an upcoming update.

Amazing, thanks alot!