Conquest challenges
Use a conquest challenge for king-of-the-hill style play where teams capture and defend a target over time.
Instead of submitting a one-time answer, teams compete for control. The platform checks the configured target and awards points based on who controls it during each interval.
How conquest works
- The organiser configures the target or check URL.
- Teams attack or defend the target during the event.
- The platform checks the target at intervals.
- The team currently identified as controlling the target receives points for that interval.
Conquest is best for live infrastructure, attack-defense exercises, and challenges where ongoing control matters more than a single solve.
Before using conquest
Check that:
- The target can reliably identify the controlling team.
- The check endpoint is reachable from the platform.
- Teams understand the objective before the event starts.
- The scoring interval and point value match the event length.
- You have tested the target with more than one team identity.
Operating tips
- Keep conquest challenges visible only when the target is ready.
- Use announcements to explain rule changes or target maintenance.
- Watch the dashboard and score logs during live play.
- Avoid changing the target mid-event unless you have a clear operational reason.
Common mistakes
- Using conquest for a challenge that should be a normal flag.
- Not testing team identification before the event.
- Making intervals too short for the infrastructure to behave reliably.
- Forgetting that conquest can create score movement throughout the event, not just at solve time.
See also: Using the dashboard, Score logs, and Making/editing a challenge.