You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description: Requesting the implementation of a chest lock limit feature that can be applied to individual players or player groups. This would allow server admins to set a maximum number of locked chests per player or group, adding more control to gameplay and resource management.
Proposed Functionality:
- Introduce a permission node (e.g., bolt.locklimit.<#>), where <#> is the maximum number of locks a player or group can apply.
- Ability to configure lock limits globally or by player groups/individual players using the permission node.
- Players receive a notification when they hit their lock limit, preventing further locking.
- Admins should have a permission to override the lock limit.
Use Case: This feature would improve gameplay balance by ensuring no player or group can dominate the use of locked containers, while offering flexibility for different group or player configurations.
Thanks for considering this feature!
The text was updated successfully, but these errors were encountered:
Using permission nodes for this is inconvenient, because permissions aren't really meant for this. It'd be a lot more straightforward to have a separate config for this. This is what LWCX did, actually!
This could be definitely be a separate plugin as an add-on to Bolt, instead of a part of Bolt specifically. While this feature existed in LWCX, Bolt rather takes a philosophy to keep the main plugin minimal and put things that are used less commonly in separate add-ons. For example, WorldGuard support was built-in to LWCX but is a separate plugin for Bolt.
Description: Requesting the implementation of a chest lock limit feature that can be applied to individual players or player groups. This would allow server admins to set a maximum number of locked chests per player or group, adding more control to gameplay and resource management.
Proposed Functionality:
Use Case: This feature would improve gameplay balance by ensuring no player or group can dominate the use of locked containers, while offering flexibility for different group or player configurations.
Thanks for considering this feature!
The text was updated successfully, but these errors were encountered: