Attack info format
The JSON document listing the flag IDs in play, served at /api/attack-info on the event site.
GET /api/attack-info on the event site returns the current attack info as JSON. It needs no sign-in and is never cached. It follows the ctf-gameserver teams.json convention, with two added fields: schema_version and expires_at.
{
"schema_version": 1,
"expires_at": "2026-09-18T12:01:00Z",
"teams": [12, 13],
"flag_ids": {
"notes": {
"12": { "0": ["alice81"], "1": ["bob22"] }
}
}
}
| Field | Type | Meaning |
|---|---|---|
schema_version |
integer | The document format’s version. Currently 1. |
expires_at |
string or null |
When this document stops being current (UTC, ISO 8601). null when nothing has been published yet. |
teams |
array of integers | The team number of every team in play. |
flag_ids |
object | Flag IDs, nested service slug → team number → flag store index → list of flag IDs. |
Team numbers and store indexes are JSON object keys, so they arrive as strings. Store indexes start at 0.
Which flags are listed
A new document is published when each tick starts. It lists the flags successfully placed in earlier ticks that are still valid: with a flag validity of v ticks, the document for tick n covers ticks n − v + 1 to n − 1. Flags placed in the current tick never appear. An event whose flags are valid for one tick publishes documents with no flag IDs.
While the game is paused, expired documents aren’t served. After it resumes, new documents expire on the resumed clock.