Admin Operations and Troubleshooting - AshleyThew/Bank GitHub Wiki
This page is an operator runbook for daily maintenance, incident response, and controlled config changes. Each operation maps to one or more Bank subsystems.
Common admin workflows are command-driven and backed by loaded account info + storage writes.
- Service control subsystem: reload/save/restart practices
- Account repair subsystem: lock/open/reset/fix username tools
- Balance correction subsystem: admin money/exp mutation commands
- Permission refresh subsystem: permission history/update workflows
- Access-route subsystem: block/NPC/open target operations
Admin-impacting keys:
Bank.Log.*Bank.Save.Auto.*Bank.Type.*Bank.Opentype.Subset.*
Operational notes:
- Keep logging higher during migrations and incidents.
- Validate subset and type keys whenever open-access behavior changes.
Core admin toolkit:
/bank admin reload/bank admin save/bank admin open <player>/bank admin force open <player>/bank admin lock <player> <true/false>/bank admin money add|subtract|balance .../bank admin exp add|subtract|balance .../bank admin slots add|set .../bank admin tax .../bank admin permission history|update <name>/bank admin reset <name>/bank admin fix usernames
Main admin nodes:
bank.adminbank.admin.reloadbank.admin.savebank.admin.openbank.admin.force.openbank.admin.lock
Most admin mutations write through the same account save paths as normal player actions.
-
Incident: player reports missing access.
- check world/gamemode restrictions
- check lock state
- force open for admin inspection
-
Economy correction:
- use admin money/exp add/subtract commands
- save and verify history inventory
Post-change validation workflow:
- Apply config change.
- Run
/bank admin save. - Run
/bank admin reloadwhen safe. - Validate with non-op player.
- Check logs for lock, backend, or permission warnings.
- Use reload for config-only updates, restart for conversion or non-runtime-safe timer keys.
- Always save before risky operations.