Skip to content
Athena User Guide
Esc
↑↓navigate↵open⌘Jpreview
On this page

How an attack/defence event runs

The phases of an attack/defence event, the dedicated host behind it, and what happens when something fails.

An attack/defence event has two parts. The event site is where players sign up, read the scoreboard, download their access and submit flags by hand; it runs from creation to the end, like any Athena event. The event host is one machine dedicated to your event, where every team’s box and your checkers run. The host exists only between reservation and the end of the event.

From creation to the end

  1. Setup. The event site is up. You register services; teams form. Nothing is scored and no host exists yet.
  2. Roster lock. At the roster deadline, or earlier by hand, the teams that exist are admitted and numbered. That roster is final.
  3. Host allocation. You get a quote sized from the locked roster and reserve it. The host is created, pulls your images, and builds one box per admitted team. Until the network opens, you can replace the host to change the services it runs.
  4. Network open. Every box is snapshotted, the network policy is applied and ticks start. Game settings freeze.
  5. Play. Every tick, checkers place and read back flags, teams attack and defend, and scores are committed at the tick’s end.
  6. End. New ticks and captures stop, running checks finish, final scores are committed, the host is destroyed and the final export is built.

Before the network opens, teams can prepare: each team can reach its own box, but not anyone else’s.

One dedicated host

Every box shares one host. That keeps the game fair, since every team runs on identical hardware, and keeps your event isolated: no other event and no other customer runs on that host, and it holds no credential that works anywhere but your event.

Each box is a container with root access for its team. Boxes share the host’s kernel, so a team that escapes its box has reached the host. Because the host is dedicated and disposable, the response is to stop play and destroy it; see Respond to a host compromise.

Boxes have no internet access unless your event’s network profile allows a specific destination. Services that need a package mirror or an external API must be built with everything they need.

When something fails

  • A box breaks. The team or you restore it from its clean snapshot. Only that box is affected.
  • Your checker fails. A checker that crashes, stops answering or runs past its deadline is recorded as Down against the team, exactly as a broken service would be, so test it before the network opens. Imported checkers are the exception: a crash or an unexpected result inside the imported checker is recorded as cancelled and counts neither way; see Fair checking. If the checker runner reports that it can’t run checks, for example because an image is missing, the game pauses until you resume it.
  • The host stops answering. When the event host or the checker runner stops reporting in, the game pauses by itself, so no team is scored down for an outage none of them caused; checks that hadn’t finished are cancelled and run again on resume. If the host comes back, it picks up where it left off and you resume. Before the network opens, a lost host can be replaced; see Replace the host. Once the network has opened, the event can’t move to another host, because rebuilding every team’s box elsewhere would need copies of state the event doesn’t keep.
  • The event site restarts. Ticks and scores are stored as they happen, so a restart loses no tick and scores nothing twice.

Billing

Creating the event holds its site at the Small event rate for its schedule. The host is billed separately, by the hour from the moment it is created until it is confirmed deleted; its hold is taken when you reserve it. Cancelling a host before the game returns the hold and charges only the time it existed. If your wallet can’t cover that final charge when the host is deleted, the charge waits with its amount fixed at the deletion time, and Event host shows it; it is taken once you top up, and nothing more accrues in between. A replacement host can be reserved, and the event’s cleanup finishes, only after it is paid. See Manage billing and credits.

Your data after the end

The event’s database is kept until its final export has been verified, however many attempts that takes, and for a few minutes after the end while the final player emails and Discord posts go out. The host holds no data the export needs, so it is destroyed as soon as the game has ended.

The export records the game as it was scored: every tick’s store states, including the ones a restore made unavailable, every restore, and every filtering finding with its evidence, so a score can still be explained after the event is gone.

Was this page helpful?