Add-ons

The Add-ons tab in the world control panel holds world-level operational features that do not fit inside a single challenge, category, or announcement.

Use Add-ons for optional event behaviour such as:

• Primary world launch target for shared launchable backends.
• Dungeon Master for player-facing score toasts.
• Assistant mode for the in-product docs assistant.
• Pause, team-specific flags, integrations, and other world-wide controls when available.

Which add-ons appear

The exact cards depend on the kind of world you are running.

Standard worlds

Standard worlds currently show:

• Pause CTF
• Assistant
• Dungeon Master
• Integrations
• Primary world launch target
• Team-specific flags
• Scoreboard freeze

Recruitment worlds

Recruitment worlds currently show:

• Assistant
• Next steps
• Primary world launch target
• Team-specific flags
• Scoreboard freeze

Primary world launch target

The primary world launch target is the shared backend that linked challenges in the same world can point to.

Choose one challenge as the Shared app source. That challenge becomes the source of truth for the shared target:

• If the selected challenge is launchable, the shared target uses that challenge's own launch configuration.
• If the selected challenge already has a saved location in the world, organisers can use that location as the shared target reference.
• Challenges marked to use world launch target will send players to this shared target instead of launching or showing their own separate backend.

When to use it

Use a primary world launch target when:

• Multiple challenges are really different tasks against the same app or service.
• You want one shared web app or backend for the whole world.
• Players should land on the same target even though they open different challenges.

How it works now

You only choose the challenge that powers the shared target. The world no longer needs a separate backend or port override in this tab.

The selected challenge's own backend setup is used automatically:

• App Platform vs droplet behaviour follows the challenge's launch configuration.
• The main player-facing port comes from the challenge's configured launch ports.
• If no explicit droplet port is set on that challenge, the default shared target port is used.

What organisers should check

• The chosen challenge is launchable or has a valid saved location in this world.
• The challenge's container image, launch ports, and runtime settings have been tested.
• Any challenge that should reuse the shared backend has Uses world launch target enabled.
• The player-facing challenge copy makes it clear that several tasks may refer to the same backend.

Pause CTF

Pause CTF lets organisers pause the player experience without ending the event.

When the world is paused:

• Challenges are hidden from players.
• Player submissions are blocked.
• Hint usage is blocked.
• Launchable challenge launches are blocked.

Use this when you need a temporary stop for maintenance, incident response, or a controlled break during a live event.

When to use it

Pause the world when:

• A major challenge or infrastructure issue affects everyone.
• You need to stop play briefly without changing the event schedule.
• You want to investigate a fairness issue before participants continue.

What to watch out for

• Pausing is a player-facing interruption, so announce it if the event is live.
• Pausing is not the same as ending the event.
• Resume only after checking that solves, hints, and launches behave normally again.

Assistant

The Assistant card controls how the in-product assistant can help players with challenge questions in this world.

Modes

Mode	Behaviour
Off	The assistant only helps with docs and product questions. It does not help solve challenges.
Competition	The assistant can only use already-unlocked built-in hints when helping with challenge questions.
Coaching	The assistant can provide more guided challenge help for practice or training-style worlds.

When to use each mode

• Use Off for strict competitive events.
• Use Competition when you want the assistant available but limited to the same hint material players have already unlocked.
• Use Coaching for practice, onboarding, workshops, or learning-focused events.

What to watch out for

• Assistant mode affects challenge-help behaviour, not general product or docs questions.
• Changing the mode during a live competitive event can change what help players receive.

Dungeon Master

Dungeon Master is the player-facing toast narrator for score events in a world.

When enabled, players see themed celebration or event toasts when teams score. Organisers can choose the writing theme and optionally enable voice narration for players who opt in to it.

Dungeon Master settings

The Add-ons card lets organisers control:

• Whether Dungeon Master toasts are enabled at all.
• Which theme the toast copy uses.
• Whether voice narration is enabled for eligible player toasts.
• A preview action so you can hear the current voice/theme style before saving.

What players experience

When Dungeon Master is enabled:

• Players receive themed toasts for supported score events.
• Voice playback can be available when voice is enabled and the player has opted in.
• The feature is presentation and feedback only; it does not change scoring rules.

Related logs

When Dungeon Master is enabled, the Logs tab can also show a Dungeon Master log so organisers can review every toast that was actually sent.

Integrations

The Integrations card controls player-facing links and optional outbound solve notifications.

Fields

Field	What it does
Discord Server Invite Link	Shows players where to join your event Discord server.
Discord Webhook URL	Posts solve notifications to the configured Discord webhook.
Music Playlist URL	Provides a playlist link for event background music.

When to use it

Use Integrations when you want to:

• Send participants to a Discord community or support server.
• Mirror solve activity into a Discord channel.
• Share a music playlist as part of the event atmosphere.

What to watch out for

• Discord invite links should be current and accessible to participants.
• Webhook URLs should point to the right destination before the event goes live.
• Playlist links are optional and should be player-safe and appropriate for the event.

Team-specific flags

Team-specific flags give each team a unique runtime flag for compatible Challenge Bank services.

This add-on only applies to compatible runtime-backed challenges and is meant for launchable flows where each team gets its own isolated instance.

How it works

When enabled:

• Compatible launches receive a team-specific FLAG value.
• Different teams can receive different valid runtime flags.
• Organisers can test a flag value in the built-in checker without creating a submission, solve, or penalty.

When to use it

Use team-specific flags when:

• Teams should not all share the same final runtime flag.
• A launchable service is provisioned per team.
• You want to reduce copied solves between isolated instances.

Requirements and limits

• This only applies to compatible Challenge Bank runtime challenges.
• It is intended for one per team launchable setups.
• Incompatible challenges continue to use their normal flag behaviour.

Next steps

Next steps appears on recruitment worlds and controls what applicants see after finishing the assessment in that world.

Fields

Field	What it does
Completion title	Headline shown after the applicant finishes the assessment.
Completion message	Longer follow-up copy shown after completion.

When to use it

Use this card to:

• Tell applicants what happens next.
• Share timelines or review expectations.
• Point applicants to follow-up actions, links, or contact channels.

What to watch out for

• Keep the message aligned with your real hiring or review process.
• Avoid promising timelines you cannot reliably meet.

Scoreboard freeze

Scoreboard freeze freezes public scoreboard displays while leaving the admin dashboard live.

When enabled:

• Public scoreboard pages use the saved freeze time.
• In-map scoreboard views also stay frozen for players.
• Admins can keep monitoring the event normally.

When to use it

Use this when you want to:

• Preserve suspense near the end of an event.
• Stop live public ranking updates without stopping play.
• Keep organiser visibility while hiding late-event score movement from players.

What to watch out for

• This affects player-facing scoreboard views, not the organiser dashboard.
• Freezing the scoreboard does not pause the event or block solving.

Related guides

• World overview
• Launchable challenges
• Launchable challenge operations
• Score logs