Admin Operations and Troubleshooting

Admin Operations and Troubleshooting

Overview

This page is an operator runbook for daily maintenance, incident response, and controlled config changes. Each operation maps to one or more Bank subsystems.

How It Works

Common admin workflows are command-driven and backed by loaded account info + storage writes.

Admin operation subsystems

• 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

Configuration

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.

Commands

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

Permissions

Main admin nodes:

• bank.admin
• bank.admin.reload
• bank.admin.save
• bank.admin.open
• bank.admin.force.open
• bank.admin.lock

Data and Storage

Most admin mutations write through the same account save paths as normal player actions.

Examples

• 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:

1. Apply config change.
2. Run /bank admin save.
3. Run /bank admin reload when safe.
4. Validate with non-op player.
5. Check logs for lock, backend, or permission warnings.

Troubleshooting

• Use reload for config-only updates, restart for conversion or non-runtime-safe timer keys.
• Always save before risky operations.

Related Pages

• Commands and Permissions