Submit flags
Flag format, attempt limits, cooldowns, and when submissions close.
Every challenge page has a Submit Flag box. This guide covers the flag format, the feedback you get, and each of the limits that can slow a submission down: attempt caps, wrong-answer cooldowns, rate limiting, and the scoreboard freeze.
Get the format right
Flags are wrapped in the event’s prefix and braces, and the input’s placeholder shows your event’s exact format, for example flag{...}. Submit the whole thing, prefix and braces included. If the shape is off, the box tells you what’s wrong:
- “Flag must start with the event prefix.”
- “Flag must use { and } after the prefix.”
- “Enter a valid flag.” The flag contains unexpected characters or is far too long; check that you copied exactly what the challenge produced.
A few submissions are refused before the flag is even checked: “Captcha verification failed. Please try again.” if an automated anti-abuse check didn’t clear (just submit again), “The competition hasn’t started yet.” before the start time, “Create or join a team before submitting flags.” on team events if you haven’t joined one, and “Solve the "…" challenge first.” on challenges locked behind a prerequisite.
Read the result
A correct flag shows Correct! Challenge solved! The challenge gets a Solved badge, the points land on your score, and if you were among the first three solvers, the Bloods card records your first, second, or third blood. A wrong flag shows Incorrect flag. Try again!.
Solves are shared: once your team has solved a challenge, the form is replaced with “Your team has already solved this challenge.” (or “You have already solved this challenge.” when playing solo).
Watch the attempt counter
Organizers can cap attempts per challenge. The counter next to the submission box, Team attempt 2 / 10 (or Attempt 2 / 10 solo, and … / Unlimited when uncapped), shows the attempt you’re on: submissions your team has already spent, plus the one you’re about to make. Both correct and incorrect submissions count. When the cap is reached, the box is replaced with “You have reached the submission limit for this challenge.” and that challenge is over for your team, so don’t spend attempts on guesses.
Wrong-answer cooldowns
Events can also enforce a cooldown after repeated wrong answers on one challenge. It locks you on that challenge only, not your teammates and not your other challenges. Rack up too many incorrect submissions in a short window and the input locks with “Cooldown active. Try again in Ns.” counting down live. There’s nothing to do but wait; the box unlocks itself when the timer ends.
Rapid-fire submissions
Independently of cooldowns, submitting many flags in quick succession trips a rate limit: “Too many attempts. Try again in N seconds.” An event applies this both per player and, on team events, per team, so several teammates firing at once can trip the team’s limit even when no single player has hit their own. It clears on its own after the stated wait.
When submissions close
At the scoreboard freeze, flag submission ends for good, and every attempt after that point is refused with “Submissions are closed.” The freeze is also when writeups and feedback open; see After the freeze.
A single challenge can also stop accepting flags mid-event, with “This challenge is temporarily locked.” That one is temporary and specific to that challenge; see When a challenge is locked.