World settings field reference
These sections appear on the world Settings tab. Open Worlds, click View details on the world, and open Settings. After editing settings, use Save changes at the bottom of the form to apply them.
Quick section guide
- Details - Event title, objective, registration period, event period, access type, invite-only join access code when relevant, and team size limit.
- Personalization - Color scheme, event logo, company logo, and world subdomain. Some logo/subdomain options can depend on the organisation plan or boosts.
- Homepage - Player-facing homepage content, including organiser content and first, second, and third prize copy.
- Launchable challenges - Launchable challenge instance mode, such as one instance per team or one shared instance, plus custom hosting fields when available.
- Scoreboard - Whether players can see the scoreboard, whether team names are anonymous to players, the point scheme, and first strike bonus points.
- Integrations - Discord invite link, Discord webhook URL for solve posts, and music playlist URL.
The sections are part of one Settings form. Make edits in the relevant sections, then use Save changes at the bottom of the form.
Details
| Field | Type | What it does |
|---|
| Event Title | Text | Title shown to players on the event page and event cards. |
| Event objective | Textarea | Short objective shown in the event header. |
| Registration Period | Date range | Start and end date/time when users can register. Outside this window, Register is not available. |
| Event Period | Date range | Start and end date/time when the event is live. Players can play during this window; Access may also open shortly before start for the countdown surface. |
| Access Type | Radio | Who can discover and join the event: |
| Team size limit | Number | Maximum members allowed per team. Defaults to 6; valid range is 1 to 100. |
Access Type options:
| Option | Behaviour |
|---|
| Open | Anyone can discover and join. Event appears in public listings. |
| Workshop | Anyone with the link can play without creating an account. |
| Invite Only | Users can join through invites, a public QR/link, or an optional shared join access code. Event does not behave like a fully public listing. |
| Organisation Only | Only users from your organisation can join. |
When Invite Only is selected, an additional Join access code field appears. The code is optional and is separate from team invite codes. If a code is already set but cannot be displayed, enter a new value to replace it.
For player-facing behaviour and when to use each access type, see Access and visibility types.
Personalization
| Field | Type | What it does |
|---|
| Color scheme | Select | Visual theme for the event (map, UI). One of: Cyberpunk, Matrix, Tron, Sin City, Vaporwave, DMU Hackers. |
| Event Logo | File (image) | Logo shown on the event page and event cards. |
| Company Logo | File (image) | Logo shown in the event header. |
| World subdomain | Text | Custom subdomain for the event (e.g. myevent.biterra.co). |
Company logo and world subdomain can be plan-gated. If the field is locked, use the plan/boost CTA shown in the form or update the organisation plan.
Homepage
| Field | Type | What it does |
|---|
| Organiser content | Textarea | Homepage content block for rules, sponsor notes, participant instructions, or embed code. HTML is allowed and sanitised before display. |
| 1st prize | Textarea | First-place prize copy shown on the homepage podium. |
| 2nd prize | Textarea | Second-place prize copy shown on the homepage podium. |
| 3rd prize | Textarea | Third-place prize copy shown on the homepage podium. |
Launchable challenges
Only relevant if your world uses launchable (container/Docker) challenges and your plan supports them.
| Field | Type | What it does |
|---|
| Launchable challenge instances | Radio | How many instances of each launchable challenge exist: |
| DigitalOcean API Key | Text | Optional custom hosting key for launchable challenges. This field appears only for worlds that have custom launch hosting enabled. |
| Option | Behaviour |
|---|
| One per team | Each team gets its own challenge instance (isolated). |
| One shared | All teams use the same instance (shared target). |
Scoreboard
| Field | Type | What it does |
|---|
| Show scoreboard | Checkbox | When on, the scoreboard is shown to players (e.g. in the event UI). Often used to show it after the event ends. |
| Anonymous scoreboard | Checkbox | When on, team names on the scoreboard are randomized for players. Admins still see real names. |
| Point Scheme | Select | Static - fixed points per challenge. Dynamic - points decrease as more teams solve (first solvers get more). |
| First strike bonus points | Number | Extra points awarded when a team is first to solve a challenge. Set to 0 to disable. |
Integrations
| Field | Type | What it does |
|---|
| Discord Server Invite Link | Text | Invite link to your event's Discord server (e.g. for participants to join). |
| Discord Webhook URL | Text | Webhook URL used to post messages when challenges are solved (e.g. to a Discord channel). |
| Music Playlist URL | Text | URL for a playlist (e.g. Spotify) used as background music during the event. |