Only allows 6 slots even though I have it at everyone enabled!
Only allows 6 slotsNot An Issue
Can you paste your config? Also, what permissions have you assigned?
All players have 1234 enabled so Its bugged.
Can you share the output of running
Is this your first time using the plugin, or did this only start happening recently? If it's a new issue, did you recently update the plugin?
Have you tried reloading the plugin to see if the sizes change? This is not a permanent solution because permissions are designed to be dynamic, but knowing whether this works will help us debug the issue.
Merged post
Looking at the code, it seems if you grant multiple size permissions to a player, only the lowest one will apply. Can you try revoking the 123 permissions and just grant the 4 permission?
Merged post
Correction to my previous post: Granting multiple size permissions should apply the largest one. Testing has confirmed this, and it's also apparent from the code which is designed for that case.
Usually when people report this sort of problem, there turns out to be an issue with their permissions setup, such as mistyping the commands or corrupted Oxide permissions. The next troubleshooting steps would be to try revoking the permissions twice, granting them twice, to the default oxide group, and to paste the output of those commands here.
o.grant group default backpacks.use.4?Is this your first time using the plugin, or did this only start happening recently? If it's a new issue, did you recently update the plugin?
Have you tried reloading the plugin to see if the sizes change? This is not a permanent solution because permissions are designed to be dynamic, but knowing whether this works will help us debug the issue.
Merged post
Looking at the code, it seems if you grant multiple size permissions to a player, only the lowest one will apply. Can you try revoking the 123 permissions and just grant the 4 permission?
Merged post
Correction to my previous post: Granting multiple size permissions should apply the largest one. Testing has confirmed this, and it's also apparent from the code which is designed for that case.
Usually when people report this sort of problem, there turns out to be an issue with their permissions setup, such as mistyping the commands or corrupted Oxide permissions. The next troubleshooting steps would be to try revoking the permissions twice, granting them twice, to the default oxide group, and to paste the output of those commands here.
Locked automatically