Scoring
How an attack/defence event scores each tick, with the formulas and their default weights.
Athena scores attack/defence events with a model derived from ECSC 2023, applied per flag store at the end of every tick. Each store earns three point streams per team per tick; a service’s score is the sum of its stores’, and a team’s total is the sum over every service and tick.
A store’s state each tick
Each tick, every store of every team gets one state from its checker results:
| State | Meaning |
|---|---|
| Up | Every current check passed. |
| Recovering | Every current check passed, but a check about an earlier, still-valid flag failed. |
| Flag missing | The service works, but a flag it should hold is gone. |
| Faulty | The service answered wrongly. |
| Down | The service didn’t answer in time, refused, or dropped the connection. |
The worst current result decides: Down, then Faulty, then Flag missing, then Up. A service-wide check (Check service, Havoc) affects every store of that service; a flag or noise check affects only its own store. A cancelled check carries no evidence either way.
A store is also treated as Down for a tick when a filtering verdict was confirmed against it, and as unavailable (no SLA, no defence) in every tick a restore of its box overlaps, from the request until the box is healthy again. Retrying the same restore doesn’t add a second penalty, and a restore doesn’t change the team’s attack points.
Pauses
No tick runs while the game is paused. Checks that hadn’t finished when it paused are cancelled and run again on resume, so the paused time never counts against a team. Published attack info keeps the expiry it was published with.
The three streams
| Stream | Earned per tick | Default |
|---|---|---|
| SLA | The store is Up or Recovering. | 3 when Up, 1.5 when Recovering, 0 otherwise |
| Defence | The team’s flag was placed this tick, the store has SLA, and nobody captured that store’s live flags during the tick. | 2 + 1 / d |
| Attack | Paid for each distinct flag the team captured during the tick. | 1 + 1 / f + 1 |
dis the number of teams that qualified for defence on the same service and store this tick. A store where nobody qualified pays no defence.fis the number of teams that captured that exact flag during this tick.
With your own weights, the formulas are:
SLA = SLA (up) or SLA (recovering)
defence = defence base + defence weight / d
attack = attack base + attack weight / f + rank weight × rank term
Defence is gated on SLA so that switching a service off is never a defensive move.
Rank reduction
With Rank reduction off (the default), the rank term is 1. With it on, capturing from a lower-ranked team pays less. Ranks come from the scoreboard at the end of the previous tick. With N scored teams and scoreboard position p (1 is the leader), a team’s rank is r = N + 1 − p, so a larger r is better. When the attacker ranks above the victim:
rank term = 1 − (min + (max − min) × ((r_attacker − r_victim) / N)²)
where min and max are the down-rank cost settings (defaults 0 and 0.8, both between 0 and 1, with min below max). Capturing from a team ranked the same or higher always has a rank term of 1.
When a capture counts
A capture belongs to the tick in which it was submitted, not the tick the flag was placed in. It moves that tick’s attack points, that tick’s f, and the victim’s defence for that tick. A later capture never reopens a tick that has already been scored, and submitting the same flag twice scores once.
Ties
Teams with equal totals share a rank and are listed by team handle.
Weights
Set the weights under Settings → Game before the network opens; see Event settings. They are frozen for the rest of the event once it opens.