Web portal — for operators

The /admin/* tree is the day-to-day cockpit for running a Splintertree cluster: account moderation, realm + game lifecycle, patches and build pipelines, shop / economy, tunables, tickets, anti-cheat, bots, and the LLM control surface. Every route is gated by the gm_level >= 3 extractor in auth_mw.rs.

The cockpit is intentionally split from the game-design tree (/admin/design/*) because the people running a realm are usually not the same people designing its content. Both share the database browser and the read-only character / guild views, but the mutating surfaces are separate.

What's in this section

• Accounts & moderation — list / search accounts, ban, mute, password reset, GM grants, character roster.
• Realms & games — cluster.games + auth.realmlist CRUD, region / locale / phase admin, per-realm patch pinning.
• Patches & build pipeline — patch-graph editor, preload / active windows, build jobs, OCI artefact pulls.
• Shop & economy — shop categories, item catalogue, Splintertoken balances, gametime keycodes, redemption audits.
• World config & tunables — world.world_config knobs and tunables.rs-driven DB-backed values.
• Tickets & support — GM ticket queue, LLM-assist draft replies, calendar of operator on-call shifts.
• Anti-cheat & audit — Warden logs, cheat detections, IP / login audit, position history.
• Bots & matchmaking — bot accounts, AI personalities, battleground / arena queues.
• LLM, moderation & translation — provider + model assignment, per-use-case system prompts, moderation thresholds, chat-translate config.

Database browser

/admin/database is a generic Postgres editor (table list, row inspector, foreign-key follow-through) for any schema in the cluster. Surfaces every column, including those without a dedicated admin page. Useful for ad-hoc fixes, debugging migrations, and operator-only maintenance — but always preferable to use the dedicated pages above when one exists, because they enforce the same business rules the public API does.