Know what Runekist manages
Total Battle user-created rooms are public. Runekist can observe a room, compare exact player IDs with an authoritative clan roster, manage supported room capabilities, and record bounded operational evidence. It cannot make a public room private, authorize someone by display name, or guarantee provider behavior.
Open Leadership → Access & sharing → Total Battle chat. The page is for an active Leader or Superior when the server integration is enabled. Runekist checks the current clan, role, binding, room state, and exact target again when each queued change executes.
Choose the guide for the decision in front of you:
| If you need to… | Start here |
|---|---|
| create or attach a room, choose Chat/Readonly chat/Ancient vaults, set access, or read health | Set up room access and health |
| invite exact players, use rank actions, manage operators, or send a Runekist message | Manage members, operators, and messages |
| mute, kick, ban, restore access, review rules, handle spam, or clean up messages | Moderate and respond to incidents |
| understand recognized vault posts, participation, no-post reporting, or history import | Use Ancient vault participation and history |
| freeze, diagnose, detach, reattach, destroy, or understand privacy and retention | Recover or remove a room |
Before any remote change, decide all five independent controls: the channel type, access policy, local read-only safety guard, restrictive-moderation switch, and whether the binding is enabled for scheduled work. No single switch substitutes for the others.
Choose Chat or Ancient vaults
The channel-type decision now includes Chat, Readonly chat, and Ancient vaults. It is separate from Runekist's local read-only guard. Compare the types and safe examples in Set up room access and health.
Add a room safely
Created and attached rooms have different ownership and destruction boundaries. Keep third-party or shared rooms locally read-only unless the owner has explicitly authorized changes. Follow Create or attach a room safely.
Choose Open, Clan only, or Clan + invited
These are best-effort membership policies for a public room, not privacy modes. They require exact SUIDs. Clan only and Clan + invited require a fresh authoritative roster; Invite only is roster-independent and retains only the Runekist account, protected room operators, configured allowlist entries, and active invited-access grants. Switching between the two invited policies keeps grants active; Open and Clan only retain them as inactive records. Use Choose an access policy.
Read health and refresh room data
Refreshing may leave a complete last-known-good snapshot visible while stricter actions fail closed. Diagnose health, snapshot freshness, credentials, permissions, and rate limits in Read health and snapshots.
Review and invite current players
Use the roster picker when authoritative data is fresh; use exact-ID entry only for an intentional, confirmed exception. Display names and rank badges do not grant Runekist authority. See Choose players by roster or exact ID.
Find your Total Battle ID
On mobile, open Menu → Accounts. On desktop/web, open Accounts from the top-right account area. In the account switcher, find the intended subaccount or progress and use the copy icon beside that subaccount's ID. Do not copy an unrelated overall account or profile identifier. The full invitation workflow is in Find and verify the exact Total Battle ID.
Promote or remove room operators
Operator capability belongs to the remote room; Runekist roles and Total Battle clan ranks are separate. Review protections and consequences in Manage room operators.
Moderate deliberately
Manual Mute/Kick, automatic rules, one-hour Ban, restorative actions, optional recent-message hiding, and destructive cleanup have different authorization and safety gates. Use the tested decision table in Moderate and respond to incidents.
Read restrictions, rules, and audits
Room-specific Runekist bans, provider-reported muted members, observe-only rule evidence, and action audits have different provenance. The current clan UI only creates disabled observe-only rules. See Read restrictions and rule evidence.
Read Ancient vault participation
Participation comes only from supported typed payloads. Prose mentions are ignored, and no-post coverage is unavailable rather than guessed when no authoritative eligible roster exists. See Read participation by reset window.
Import and recover older history
History import is capped, cursor-based, duplicate-safe, and never triggers historical moderation. See Import older history.
Detach, recover, or permanently destroy a channel
Freeze and detach are recoverable; eligible permanent channel destruction is a separate, exact-name-confirmed remote deletion. Compare the blast radius before acting in Choose a lifecycle action.
Troubleshoot common states
For disabled/read-only rooms, stale snapshots, operator loss, invalid credentials, rate limiting, partial actions, and queued work after a freeze, follow Recover from common failures.