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

Event settings

Every attack/defence event field, when it can change, and its limits.

An attack/defence event has the shared event fields (name, slug, flag prefix, schedule, branding, rules and FAQ, sign-in) described in Event settings, plus the fields on this page. Settings that exist only for jeopardy events, such as event size, team mode, cooldowns and build minutes, don’t apply.

Two shared fields read differently here:

  • Freeze is labelled Feedback opens. It opens player feedback and nothing else: the game keeps running and the scoreboard keeps updating until the event ends.
  • Require email verification works as for any event, and the event site sends its sign-up verification and password-reset mail.

Emails players receive

Besides account mail, the event site emails players when their team’s box is ready, when the network opens, when the game pauses, and when the event ends with their team’s final placing. It also tells a player when their account is suspended, restored or deleted, or when their team membership changes, and emails the addresses you set for report notifications when a player files a report. A mail that could no longer be true by the time it would arrive, such as a pause notice after play has resumed, isn’t sent. Failed sends are retried for up to a day. The Player email card on the event overview counts each kind by whether it was sent, is still pending, or failed.

Fixed at creation

Field Limits Notes
Format Jeopardy or Attack/defence Attack/defence needs the Pro or Enterprise plan.
Host region Regions where a supported host size is offered Where the event host runs.
Host image A qualified host image The software every box and the host itself run.
Network profile Offered profiles The network policy the host applies.
Declared host size Sizes offered in the region A starting point; the quote picks the size from the locked roster.
vCPU per team 1 to 16 CPU each team’s box receives.
Memory per team (MiB) 320 to 65,536 Memory each team’s box receives.
Disk per team (GiB) 1 to 512 Disk each team’s box receives, shared by every service inside it.
Admitted teams (cap) 1 to 256 The most teams the roster may admit.

A box keeps 250m of CPU, 256 MiB of memory and 256 processes for its own system, and its services split the rest of the team’s budget equally. Each service needs at least 100m of CPU, 64 MiB of memory and 64 processes, so one vCPU carries at most seven services. A host quote refuses a budget its services can’t share, whatever the host size, before anything is held.

Game settings

Change these under Settings → Game until the network opens. From then on they are frozen for the rest of the event.

Field Limits Notes
Roster deadline A date and time Team creation closes and the roster locks at this time if you haven’t locked it.
Tick (seconds) 60 to 300 Length of one round.
Flag validity (ticks) 1 to 20 How many ticks a flag stays submittable, counting the tick it was placed in.
Checker timeout (seconds) Shorter than a tick How long one check may run. A service can set its own, of at least 5 seconds.
Scoring weights See Scoring SLA, defence and attack weights, and rank reduction.

Each save is applied to the event and then confirmed; the page reports it saved only once both have happened. While a change is synchronizing, further game-setting changes, host quotes and the network-open request wait for it.

Service limits

Limit Value
Ports per service 8, each tcp or udp, never 22
Port and protocol pairs across enabled services Each pair published by at most one enabled service
Flag stores per service 1 to 8
Checker state per team, service, store and tick 64 KiB
Flag ID and noise ID length 128 bytes, UTF-8 encoded
Checker message length 4,096 bytes, UTF-8 encoded; longer messages are cut
Diagnostic output kept 8,192 bytes per stream; longer output is cut
Source archive 512 MiB
Submission line length 256 bytes

Lengths are counted in bytes, not characters: a non-ASCII character takes two to four bytes. A flag or noise ID over the limit, or state over 64 KiB, isn’t cut: the check is recorded as Faulty, or as Cancelled for a checker built on an Athena base image.

Was this page helpful?