| Time | Attacker | A Faction | Defender | D Faction | Result | Respect | FF | Chain | Type | 🔗 |
|---|
Attacks per active member, per chain. Members with zero attacks in a chain show —. Newest chain on the left, older chains scroll right. Rows include all active members, sorted by chains-participated descending.
How often each worker pulls fresh data from Torn. Lower frequencies during quiet periods to conserve API key quota.
/faction/attacks.
/chainreport while tracking is enabled. This uses a single request to update the chain and happens independently of collect-worker frequency.
Health of Torn API keys used by the collection workers above. Keys with 3+ consecutive failures are auto-skipped.
Detects whether the faction currently has an active chain and starts tracking it. The worker polls /chainreport on the cadence set below until the chain ends. Pause/resume polling from the live status banner above.
Pulls the final snapshot for the chain currently being tracked. Use this if the chain ended between worker polls and the row still shows live, or if you want to refresh the totals on a finished chain.
Controls what members see in the Chain Summary tab — whether the tab appears at all, and which chain it displays. Admins always see the tab (preview mode) regardless of the toggle.
Import a specific historical chain by ID. Same UPSERT path as live sync — safe to re-run. One chain per click; bulk import isn't supported.
Toggle whether each tracked or backfilled chain is included in the Dashboard chains scorecard and the Chain Performance matrix. Hidden chains stay in the database — flip them back on at any time. Newly added chains are included by default.
Export tools — currently empty.
Not authorised
This section is admin only. Pick a tab above to continue.