Challenges

Overview

Challenges comprise the core of how the Control team will contribute to the game. These are Jeapordy-style challenges and are broken into two primary forms, Core and Edge.

Requirements

• Challenges must be stored as individual directories under the challenges directory.
• Challenges must contain in their directory root an info.yaml file which contains the relevant information. There are examples for this in this repository.
• a content directory with an index.html must be supplied. Whatever is to be presented as the Challenge must reside within this directory.

Core Challenges

• Description: Core challenges are worth points and are distributed by a certain amount per area chosen by the configurator of the server.
• Trigger: Area Hackswitch activated by the Marines. This will unlock all Area Core Challenges.
• Database:
  • name: name of Challenge.
  • area: Area associated with Challenge.
  • flag: plaintext solution key.
  • points: value of the Challenge.
  • category: type of Challenge.
  • hint: plaintext hint.
  • locked: Boolean value of whether it is locked, default "true."
  • solved: Boolean vlue of whether it has been solved, default "false."

Edge Challenges

• Description: Edge challenges are worth no points and have one per Area of the level.
• Trigger: Secret found in an Area. This will unlock all Edge Challenges.
• Database:
  • name: name of Challenge.
  • area: zero.
  • flag: plaintext solution key.
  • points: zero.
  • category: type of Challenge.
  • hint: plaintext hint.
  • locked: Boolean value of whether it is locked, default "true."
  • solved: Boolean vlue of whether it has been solved, default "false."