Set up an event

You need Manage Server to create a game. Once it exists, your chosen moderator role can open, start and manage it too.

1. Invite and prepare. Use Add to Discord to install the bot. Approve Manage Channels plus View Channel, Send Messages, Embed Links, Attach Files, Read Message History and Use Application Commands. If the bot is already installed, grant it Manage Channels in Server Settings.
2. Create your channels. Choose an existing reviewer role, make it mentionable and assign your reviewers to it. Run /server setup moderator-role:@YourReviewers to create a game channel and a private evidence-review channel. You need Manage Server and Manage Channels. The bot uses your existing role; it does not need Manage Roles. Optional game-channel and review-channel choices use existing channels whose permissions are already configured.
3. Build your board. Run /game setup in a channel with no unfinished game. Choose 50 or 100 tiles, a theme and an evidence mode. Quick board takes one challenge per line; follow the selected layout's required count. Templates offer ready-made 100-tile boards. You can also import a CSV or start from a completed event using the options below.
4. Preview, then confirm. Set the event name and capacity (1–20 players). Check the preselected review channel and moderator role, or choose different ones. Fix any permission issues the bot lists. Check the private board preview, then choose Confirm within 24 hours, or Cancel to discard the draft.
5. Open the lobby and start. Open the linked board and choose Open lobby (host). Ask everyone to choose Join game. Once at least one player has joined and everyone is ready, choose Start game (host). Starting closes joining.

Before you start: tell players what counts as proof and when moderators will review it. Use the board customisation guide to choose a layout and write clear challenges.

Already have channels? Keep using manual setup. Your review channel must explicitly deny View Channel to @everyone and allow the bot and reviewers. Server owners and administrators retain access. Rerunning /server setup reuses saved channels; it does not change existing permissions or recreate deleted channels.

Command alternatives: /game open, /enter (or /join), then /game start.

Run another event from a completed game

In /game setup, choose the option that matches what you want to keep. Both use completed games from this server and start a fresh event, with no players, evidence or progress carried over.

• Copy board only: keep a completed board's challenges and effects. Select the matching board size, then choose your theme, evidence mode, review channel and moderator role for the new event.
• Reuse setup: keep the board, size, theme, evidence mode, review channel and moderator role together. Choose a completed game from the newest-first list, then edit the prefilled name and capacity. Check the saved settings before continuing to the private preview.

To change the saved settings, return to /game setup and choose Copy board only. Use this route if the saved review channel, moderator role or theme is no longer available. If permissions have changed, fix the listed issues before trying again.

No completed games yet? Start with Quick board, Templates or Import CSV. If this channel already has an unfinished event, use a free game channel for the new one.

Make the board yours

Start with Quick board in /game setup to keep a preset's snakes and ladders and supply your own tasks. Choose 50 tiles for one of these four layouts. The artwork is a separate theme choice.

Paste exactly the requested number of non-blank lines, one challenge per line, up to 120 characters each. The bot fills the task tiles in order and keeps the effects and finish. The 100-tile Balanced layout needs 75 challenge lines.

Choose your game's backdrop

Choose RuneScape, Counter-Strike 2, Dota 2, Minecraft, GTA 6, Fortnite, Elden Ring or The Witcher IV in /game setup. Every theme supports 50 and 100 tiles. The theme changes the artwork; choose or write your challenges separately. Upcoming-game CSVs may contain draft gameplay tasks; check their availability in the released game before hosting. Preview the boards.

Start with a themed challenge board

These upload-ready examples each contain 50 tiles: 20 easy challenges, 20 moderate challenges and automatic movement, extra-roll and finish tiles. They use modest game-specific targets on the Gentle layout, including combat, robberies and getaways for GTA 6. Choose 50 tiles and Mix of text and uploads in setup, then Import CSV.

• GTA 6: Vice City CSV (pre-release draft) ↓
• Fortnite: Storm Island CSV ↓
• Elden Ring: Golden Ruins CSV ↓
• The Witcher IV warm-up: Witcher 3 CSV ↓

The GTA 6 draft uses generic kills, wanted-level escapes, store holdups and vehicle theft informed by published previews. Check the tasks after release. The Witcher IV example remains a The Witcher 3 warm-up. Download the host rules, sources and tile-by-tile evidence guide (.txt). Review available content and agree fallback tasks before starting.

Write a task players can prove

Give each task a specific action and a clear success condition. Match the proof to your event's Upload, Text or Mixed evidence mode. For an image-based event, a challenge could be:

Win a match using only the starter loadout. Submit a result screenshot showing your loadout.

Choose tasks your community can actually complete and explain any game-specific restrictions before launch. Keep rare or lengthy tasks deliberate: review timing and challenge difficulty affect event length as much as the layout.

Edit a CSV for more control

Download a full 50-tile starter, replace its placeholder challenge titles, then save as CSV. Keep the effect columns as supplied unless you want to change the movement rules.

• Balanced CSV ↓
• Sprint CSV ↓
• Challenge CSV ↓
• Gentle CSV ↓

The columns control each tile:

number and title

One unique row for every tile from 1 to 50 (or 100). Titles must be non-empty and at most 120 characters.

move_to

A higher destination makes a ladder; a lower one makes a snake. Leave blank for no movement. On 50-tile boards, ladders must stay in the same visual column, so retain the starter's destinations unless you have checked the board layout.

extra_roll

Set to true to grant another roll. A snake or ladder does not grant one by itself.

requires_evidence

Set to true for a task needing approval, or false for an automatic tile. The starters use automatic effect tiles and an automatic finish.

Import and check: run /game setup with the matching board size and choose Import CSV. Keep every tile row, keep destinations inside the board, and don't move away from the finish or create movement loops. Let the bot validate the file, inspect its private preview, then confirm. Return to the setup steps.

Play your first turn

1. Join while the lobby is open. Choose Join game on the board or run /enter. Wait for the host to start the event.
2. Read your challenge. Choose My turn on the running board or use /status for your private turn panel. You start on tile 1; complete its task before your first roll.
3. Send your proof. Choose Submit evidence in the panel or use /evidence submit. Upload mode needs an image; Text needs written evidence; Mixed accepts either or both. Proof goes to the private review channel.
4. Wait for review, then roll. Approval grants one roll credit. Choose Roll on the approval message, refresh your private panel, or run /roll. If rejected, read the reason, improve your proof and choose Resubmit evidence. Only you can use the buttons for your submission.
5. Follow your next tile. The shared board updates after your roll. Check My turn for what comes next and use /standings to follow the race. Everyone progresses at their own pace; there is no global turn order.

Near the finish? You need to land exactly on the final tile. An overshoot spends the roll and leaves you in place. Snakes and ladders move you, but only tiles configured for an extra roll grant one.

Check your progress and find the results

• Trace a turn: use /history in the game channel for your ten most recent game events. Select a player in the optional user field to see their recent events instead. The reply is visible only to you.
• Check the race: /standings gives you a private view of recorded finish places, followed by players still on the board in order of their current tile. A board position is not a finishing place.

These commands use the channel's unfinished game. After a moderator ends the event, look for the published final results or the event's final board message. They show recorded finishers and the final positions of players who remained on the board.

Keep reviews moving

Open the private review channel. Each review card brings together the player, tile, challenge and submitted proof so you can check the task before deciding. Choose Approve to grant one roll, or Reject and give a clear reason the player can act on. Keep reasons suitable for the game channel: the bot announces decisions there.

• After a decision, the card shows who reviewed it and the outcome. Choose Next pending submission to find the next review; the bot tells you when the queue is clear.
• Run /evidence queue in the game channel to find outstanding reviews. Agree review windows with your community so players know when to expect a decision.
• Use /game pause to stop evidence, rolls, joins and leaves while resolving a problem. Use /game resume when ready.
• Check /admin audit for the event timeline before making a correction. Use /admin set-position or /admin grant-roll only when needed, with an explanatory reason.
• When the event is over, /game end asks for confirmation and publishes final results. Ending is permanent; use Pause for a temporary break.