---
title: Publish your first challenge
description: 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](/organizers/tutorials/host-your-first-ctf); everything here happens in that event's dashboard.

1. **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.

2. **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.

3. **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.

4. **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.

5. **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.

    :::warning[Enter only the secret: no prefix, no braces]
    Your event wraps every flag in its flag prefix, like
    `athena{s0me_s3cr3t_fl4g}`. In **Flag Content**, type only the inner
    secret (`s0me_s3cr3t_fl4g`). The platform strips the prefix and braces
    from player submissions before comparing. If you type the full wrapped
    flag here, the flag you intended will never match.
    :::

    Leave **Case Sensitive** unchecked to accept the flag in any casing;
    check it to require an exact-case match.

6. **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.)

7. **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.

:::note
If you later edit a published static challenge, you won't see the flag
you set: the **Flags** section shows **A flag is already set** instead of
the input, noting that the stored flag can't be displayed again. You don't
need to re-enter it; saving keeps the existing flag. To change it, click
**Replace flag** and type the new one; **Keep existing flag** backs out of
that and leaves the stored flag untouched.
:::

## 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](/organizers/tutorials/run-a-container-challenge).
