Skip to main content

Before you launch

Use this checklist before sharing an event link widely. It is designed for organisers doing a final pass over dates, access, teams, challenge visibility, scoring, and the player experience.

Event basics​

  • Correct organisation selected: the world belongs to the organisation that should own the event.
  • Event title and objective are clear: players can recognise the event and understand what it is for.
  • Registration Period is correct: registration opens early enough and closes when you expect.
  • Event Period is correct: play starts and ends at the right time.
  • Timezone checked: dates and times make sense for your participants.
  • Access Type checked: Open, Invite Only, Organisation Only, or Workshop matches the event plan.
  • Join access code checked: invite-only events use the right event access code if you need one.

Homepage and player instructions​

  • Homepage content is ready: rules, schedule, support channel, prizes, and any joining instructions are visible.
  • Discord or support link works if you are using one.
  • Prize copy is correct if prizes are shown.
  • Organiser content does not leak answers.
  • Any external links open in a normal browser session.

Teams and registration​

  • Team size limit is final before players register.
  • Team mode is clear: players know whether to create their own teams or join assigned teams.
  • Pre-created teams are ready if you are assigning teams.
  • Team invite codes are copied and shared with the right people.
  • Event access code and team invite codes are clearly labelled in your joining instructions.
  • World user limit is high enough for the expected participants.
  • Boosts are active if this event needs extra capacity or a plan-gated feature.

Users and staff access​

  • World admins or moderators have access if they need to help run the event.
  • Organisation collaborators have the right role if they need repeated access across worlds.
  • Pending invites have been resent if key helpers have not accepted.
  • Test organiser can enter the world control panel.

Challenges​

  • At least one challenge is visible at event start.
  • Every visible challenge has a category, country/location, description, answer or review flow, and point value.
  • Imported Challenge Bank content has been reviewed for this event.
  • Challenge files and links work for a normal player.
  • Hints are useful and hint costs are intentional.
  • Wrong-answer penalties are intentional.
  • Hidden challenges are hidden on purpose.
  • Difficulty labels and point values match the event design.

Progression and timing​

  • Prerequisites unlock in the intended order.
  • Choice groups are intentional and do not block required challenges.
  • Timebomb windows fall inside the event period.
  • No core path depends on a timebomb unless that pressure is deliberate.
  • A normal player account can reach the expected first challenge.
  • A test team can complete the intended early progression path.

Scoreboard and logs​

  • Show scoreboard is set correctly for the event rules.
  • Anonymous scoreboard is on or off intentionally.
  • Point scheme is correct: static or dynamic.
  • First strike bonus is correct, or set to 0 if unused.
  • Manual score process is clear if you expect judged text or file submissions.
  • Logs are checked after test solves so you know scoring is recorded as expected.

Announcements​

  • Welcome/rules reminder is scheduled if you want one.
  • Breaks, final warnings, and close messages are scheduled if useful.
  • Announcement times match the event timezone and schedule.
  • Clarification messages do not reveal challenge answers.

Launchable challenges​

If the event uses launchable/container challenges:

  • Launch runtime minutes are available for the expected number of running instances.
  • World launchable instance mode is correct: one per team or one shared.
  • Each launchable challenge has valid image/container configuration.
  • Required secrets, environment variables, ports, and URLs are configured.
  • A non-admin test account can launch the target.
  • Launch, solve, and teardown have been tested.

Final player test​

Before launch, run through the event as a player:

  1. Sign in with a normal player account.
  2. Open the event from Events or the direct event link.
  3. Register during the registration period.
  4. Enter the event access code if one is required.
  5. Create or join a team.
  6. Use Access when the event should be available.
  7. Open the map.
  8. Open a challenge.
  9. Submit a correct answer.
  10. Confirm score, scoreboard, and logs behave as expected.