Skip to main content

Challenge optional fields and tips

Optional fields​

Launchable (Docker/container) - Enable for challenges that run in a container when players click Launch. Set or verify the image and confirm the organisation has enough launch runtime minutes for the event.

Conquest link - For conquest challenges: URL the system checks to determine which team holds the target.

Review email - For text and file upload challenges: email address where submissions are sent for review.

Challenge file - File or URL for participants to download, such as a PCAP, archive, image, binary, or source bundle.

Company / sponsor - Logo, name, and website for attribution.

Difficulty - Label such as Easy, Medium, or Hard for the Challenge Bank and UI.

Location - Optional URL shown with the description. Use it for external targets, references, or hosted challenge entrypoints.

Prerequisites and choice groups - Set in the challenge form or in the Progression editor. Choice groups make challenges mutually exclusive (e.g. pick one of three).

Timebomb - Set a start and end window for challenges that should only be available for a limited period.

Penalty - Deduct points for wrong attempts. Use carefully: high penalties can discourage testing and learning.

How optional fields interact​

  • Hidden + prerequisites - Hidden challenges can remain invisible even if prerequisites are met, depending on how you configure visibility.
  • Prerequisites + timebomb - Teams must be able to unlock the challenge before or during the timebomb window.
  • Launchable + runtime minutes - Launch controls consume included monthly launch minutes first, then prepaid launch-minute top-ups.
  • Hint + hint cost - A hint can reduce score when revealed. Explain hint cost in event rules if players should plan around it.
  • Review email + text/file upload - Use review email when submissions need human review rather than immediate scoring.

Tips​

  • Test before going live - Confirm the intended solution works and the challenge is solvable.
  • Hints - Use hints to nudge without giving the answer away.
  • Clear instructions - Descriptions should be clear so players struggle with the challenge, not with understanding the task.
  • Points - Keep point values consistent with other challenges of similar difficulty.
  • Player view - Check the live preview and, where possible, test the challenge through the same map flow players will use.
  • Imported content - Review Challenge Bank imports before launch; do not assume every imported value fits your event.
  • Support load - The more optional behaviour you combine, the more likely players are to need clear rules, announcements, or support.