-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request #32
Comments
I'll consider this suggestion. However, I'm skeptical that plugins such as Backpack Upgrader should be granting/revoking permissions at all. One design under consideration is to introduce a new mode to the Backpacks plugin where permissions are only used to assign capacity rulesets to players. A ruleset would define the minimum and maximum capacity. The actual capacity for a player would be stored by the Backpacks plugin in a data file, and that stored capacity could be optionally cleared when the map wipes. Other plugins such as Backpack Upgrader could call Backpacks APIs to determine the player's current/min/max capacity, as well as to increase or decrease the capacity |
I implemented something for this on a branch of my fork. Search the docs for "Dynamic size". https://github.com/WheteThunger/Backpacks/tree/capacity-management Would you be interested in experimenting with it? It will require integration work on the Backpack Upgrader side. |
I'll test it out and report back, thank you! |
Would it be possible to make
_sortedBackpackSizes
accessible via the API? Would make plugins like "Backpack Upgrader" able to read the new permission system without ReflectionThe text was updated successfully, but these errors were encountered: