Management access
Tune the wipe without touching JSON.
Enter the admin token configured on the management service.
Development default: dev-admin-token
Live ruleset
Server control panel
Checking Rust server connection…
Wipe lifecycle
World wipe and standings
The host creates the fresh Rust save first. You then archive the old competition and activate the new one.
Multipliers
Server pace
1.0 is vanilla. Changes apply when the plugin next polls.
Production QOL
Furnace automation
Players can opt out with /fs off and re-enable it with /fs on. Existing excess fuel is never removed.
Inventory QOL
Stack profiles
Vanilla single-stack and condition-bearing items remain single regardless of category. Default: supplies 2x; weapons, equipment, building items, and other categories 1x.
Progression
Blueprints
Lock actions intentionally clear blueprint ownership server-wide, then restore every tier still marked unlocked. Ordinary wipes retain blueprints unless you explicitly select a BP reset.
Team QOL
Automatic access
Night vote
Skip the dark
Combat QOL
Private team death notes
Messages go only to the killer, victim, and enabled current-team recipients. Nothing is broadcast globally.
Competition
Leaderboard scoring
Materials are ranked separately. TC, Bradley, and helicopter credit follows the highest recent damage team and its top contributor; prize-team deltas stay with the team that earned them.
Audit a player's score
Reconcile current totals against the server-authoritative event ledger and see why each event was awarded, recorded without points, or ignored.
Prize-team roster integrity
Team membership follows current Rust rosters immediately. Points already earned stay with the team that earned them; future activity follows the player's current team.
Loot editor
Container rules
Loading loot table…
Loot editor
Container rules
Import a loot table
Dry run first. The file stays in this browser and never publishes automatically. Supported inputs are Grim's JSON v1, BetterLoot LootTables JSON, and the documented CSV columns.
Prefab patterns are case-insensitive substrings and the first enabled match wins. “Replace” suppresses vanilla generation; “Add” keeps it. Published changes affect future population events.