Publish your first challenge
Author a static challenge with its description, flag, hints, and files, then publish it to players.
In this tutorial you’ll author a static challenge (one with a fixed flag you choose) as a draft, then publish it to your players. You’ll need an event from Host your first CTF; everything here happens in that event’s dashboard.
Check your categories and difficulties
Every challenge needs a category and a difficulty, and the challenge form only offers ones that already exist. New events come pre-seeded with the categories Web, Crypto, Pwn, Reversing, Forensics, and Misc, and the difficulties Easy, Medium, Hard, and Insane. You can skip straight to the next step if those suit you.
To customize them, open Categories or Difficulties in the event sidebar. Each page has an add form (a Name field and a Create button) and a table where you can rename or delete entries. Names must be unique, and you can only delete an entry once no challenges are assigned to it.
Open the challenge editor
Open Challenges in the sidebar and click Add challenge.
You can publish straight from here with Create Challenge, or save your work as a draft at any point and come back to it. Drafts are private working copies. They never appear to players, no matter how long they sit.
Fill in the basics
Under Basics:
- Challenge Title, for example
Warmup: Inspect the Source. - Description: a rich-text editor with headings, lists, code blocks, links, and images. What you see is what players get.
- Category and Difficulty: pick from your event’s lists.
- Points: the challenge’s value; defaults to 100. The default scoring method, Static (Fixed Points), keeps this value constant no matter how many teams solve it, which is fine for a first challenge.
- Enable Attempt Limit: optional; when on, a Max Attempts field caps how many submissions each team gets on this challenge. Correct and incorrect submissions both count against it.
Add hints and files (optional)
Under Hints and Files:
- Hints: each row is a hint plus a Penalty, the points a team gives up to reveal it (0 means free). Click Add Hint for more rows; empty rows are dropped when you save.
- Challenge Files: drag and drop attachments or click Select
Files. Accepted types are
.zip,.tar,.gz,.txt,.pdf,.md, and.json, up to 10 MB per file. After a file uploads you can edit the filename players will see, or remove it.
Set the flag
Under Flags, fill in Flag Content. On events sized Small and larger, leave Flag Type on its default, Static; Extra Small events don’t show that selector, since every flag there is static.
Leave Case Sensitive unchecked to accept the flag in any casing; check it to require an exact-case match.
Publish it
The editor’s footer has two buttons:
- Save as Draft: saves your progress as-is, validation-free, and opens the draft editor, where further edits autosave. Come back any time from the Challenges list by clicking the draft’s row.
- Create Challenge: validates the form, saves, and publishes the challenge to your event. If anything required is missing, an alert lists the fields to complete.
Click Create Challenge. On success you’ll land back on the Challenges list. (From the draft editor the same action is called Publish Challenge, and confirms with a “Challenge published” toast.)
Verify it's live
On the Challenges list, your challenge now shows its category,
difficulty, points, and a Status of Visible. Click the row for
a detail view: the rendered description, hints, files, and the flag’s
settings (its type and case sensitivity, never the flag value itself).
There’s no in-dashboard player preview. To see exactly what players see, open your event URL and view the challenge board there.
Next steps
Static challenges are the backbone of most events, but Athena can also run each team its own live containerized target. Continue with Run a container challenge.