World overview

The world control panel is where you build and operate a single event. Enter it from Worlds, select a world, then click Enter control panel.

Use the world control panel to

• Monitor event metrics from Dashboard.
• Create, edit, and review challenges from Challenges.
• Import reusable challenges from Challenge Bank.
• Organise challenges with Categories.
• Set challenge dependencies and choice groups in Progression Editor.
• Create timed participant messages from Announcements.
• Review and approve score activity from Logs.
• Configure world-wide operational features from Add-ons.
• Open the map builder and player map when those controls are available for the world.

World settings such as event dates, registration, access type, teams, participant invites, and homepage content still live on the Customer Portal World details page.

Control panel sections

• Challenges - Making/editing a challenge, challenge types, timebombs
• Challenge Bank - Import challenges (single or bulk)
• Categories - Making/editing a category
• Progression - Dependencies and choice groups (flowchart); see Progression examples
• Announcements - Making an announcement
• Dashboard - Using the dashboard - event metrics
• Add-ons - Primary world launch target, Dungeon Master, assistant mode, and other world-wide controls
• Score logs - Manual scores; approve or deny pending entries (world Logs tab)
• Map Builder - Preview and adjust map presentation when available in the control panel.

Recommended build order

1. Create categories first so challenges have clear grouping and map styling.
2. Add or import challenges.
3. Review each challenge's points, answer, hint, file/link, country, and optional fields.
4. Use the Progression Editor to set prerequisites and choice groups.
5. Schedule announcements for important event notices.
6. Configure any shared operational features in Add-ons, such as the primary world launch target or Dungeon Master.
7. Use the dashboard and logs during the event to monitor activity and score changes.

Pre-launch checklist

• At least one challenge is visible and available at event start.
• Categories have readable colours and icons.
• Challenge points, penalties, hints, and answers have been checked.
• Files and external links open correctly.
• Launchable challenges have the right instance mode and enough launch runtime minutes.
• If several challenges share one backend, the primary world launch target is configured and tested.
• Timebomb windows fall inside the event period.
• Progression does not create circular dependencies or accidental dead ends.
• Choice groups are intentional and documented for players when needed.
• Scoreboard visibility and anonymity match the event rules.
• Announcements are scheduled for known milestones.
• A test team can register, access the map, open challenges, submit answers, and see scoring.

During and after the event

• Use Dashboard to monitor challenge availability, active users, active teams, categories, difficulty spread, and event status.
• Use Add-ons to manage shared launch targets, Dungeon Master behaviour, and similar world-wide features.
• Use Logs to approve, deny, remove, or add score entries.
• Use Announcements for participant-wide notices and clarifications.
• Use Challenges and Progression Editor carefully during live play; changes can affect what teams can see or solve.
• After the event, review final scores, logs, challenge performance, and any support issues before reusing the world setup.