Admin commands, backups and recovery

Visual overview

Diagram of reported mechanics. The text retains the full conditions and settings.

Exact custom commands

Only the following seven executable leaves were reported under /civic admin. No custom /town, /nation, /claim, /pay or /civic help implementation was found. Bare intermediate roots have no execute handler and no inspected aliases.

The amount parser is LongArgumentType.longArg(1) with no smaller command-specific parser maximum; runtime ledger/arithmetic checks can still reject it. EntityArgument.player requires one online player. Bill/grant/check/crashtest do not add the stronger Admin Book permission check. This is a reported static access distinction; no commands were executed for this wiki.

Ordinary civic management uses screens. Vanilla /place structure civic_frontier:prison_gate is a testing convenience and does not expand this custom-command count.

Save layout and complete-world backups

State lives beneath the world’s civic_frontier/ directory: journal, snapshots and history. Server-thread transactions append CRC-protected committed journal records, flushed at tick end or immediately for crossings. Snapshots occur on world save and at 15-minute intervals, retaining 24 historical generations. Startup loads domain snapshots and replays later journal transactions.

The 26 saved domains are meta, account, player, town, claim, offer, job, sjob, trade, zone, zonework, marker, bag, vault, camp, nation, dovecote, flight, warrant, prisoner, jailworld, lease, culture, cmsg, devproj, district. Plans showing other shard/export folder names are not the exact current layout.

Back up the complete world, including civic records, player saves and chunk data, as a consistent set. Keep a copy before testing recovery. This wiki has not verified every recovery button or a full mismatched-backup reconciliation workflow.

Inventory crossing limits

Crossings stamp players with civic_frontier:crossing_seq and save them immediately. Unsaved nearby chunks are also saved within default 4-chunk radius. On login, a journal crossing newer than the saved player stamp can be reversed.

Historical kill-process tests found duplicate redemption from container-chunk lag; the nearby-save mitigation was followed by 15 passing cycles. Unsaved distant loaded containers and separately saved dropped-item entities remain documented boundaries. This is crash mitigation, not an absolute no-duplication guarantee.

Networking and troubleshooting evidence

Protocol version 1 has four payloads: view, map_data to clients; action, map_hello to server. UI checks sessions/anchors/actions and rate limits. When reporting missing items or stale screens, record the exact builds, quote/action, inventory/deliveries state and restart timing. Do not treat a partial Civic-only backup as proof that Minecraft inventory and custody agree. Historical tests and gaps explain what has actually been observed.