Slash commands
Slash commands are typed into the Log tab of the Table panel. They let you execute quick actions – rolling dice, managing combat, requesting rolls from players, and more – without leaving the panel.
- The GM types them into the input bar at the bottom of the Activity Log, the Log tab’s Activity page.
- Players and observers type them into the game log’s message box. A line that starts with a table command runs it instead of posting; anything else posts to the log as usual. The GM can do this too.
- Away from a room (a scene on its own), the Log tab is a live, unsaved log with the same command line at its foot.
Type /help to see a quick reference of all commands, or read on for full details.
Using the input bar
Section titled “Using the input bar”On the Activity page, the input bar is at the very bottom of the log. It shows a / prompt on the left. Type your command and press Enter to execute it. In the game log, type the command into the message box and press Enter or the send button: the result shows above the box for a few seconds, and /help shows the command list there.
The autocomplete, @mention lists and command history below belong to the Activity page’s input bar. In the game log’s message box, the / list is chat’s own, and there is no command history.
Autocomplete
Section titled “Autocomplete”As you type a command, a dropdown appears above the input bar showing matching commands. Each entry shows the command name, its arguments, and a short description.
- Arrow keys – navigate up and down through the suggestions
- Tab – accept the highlighted suggestion (fills it into the input bar)
- Enter – submit the command as typed (ignores the dropdown)
- Escape – clear the input and close the dropdown
Autocomplete activates as soon as you type /. The list narrows as you type more characters. /play, /as, /loc and /scene commit don’t appear in it – type them in full.
@mention autocomplete
Section titled “@mention autocomplete”When using commands that accept @target arguments (like /rollrequest), typing @ after the command shows a second autocomplete dropdown listing available targets:
- Combatants – non-defeated tokens in the active combat, labelled “combatant”
- Room members – all players and GMs in the room, labelled “GM” or “player”
The list filters as you type after the @. For example, @gob narrows to combatants matching “gob” (like “Goblin King”). Press Tab or click to accept a suggestion.
You can chain multiple @mentions in a single command: /rr 1d20+5 @Fighter @Wizard Dex Save.
Matching priority: When you type @name, the system first tries an exact match, then falls back to a substring match. If two names overlap (for example, “Archie” and “wily_archie”), the exact match wins. Combatant names are checked before member usernames.
Command history
Section titled “Command history”Press Arrow Up to cycle back through previously executed commands. Press Arrow Down to cycle forward. History is stored per browser tab and cleared when you close the tab. Up to 20 commands are remembered.
Command history only activates when the autocomplete dropdown is not showing. When the dropdown is open, the arrow keys navigate suggestions instead.
Feedback messages
Section titled “Feedback messages”After executing a command, a feedback banner appears above the input bar showing the result (green for success, red for errors). The banner disappears after a few seconds. Hover over it to keep it visible – it will dismiss 1.5 seconds after you move your cursor away.
/help is the exception: instead of a banner, it swaps the activity feed for a Command reference card, grouped by family. Close it with the × or press Escape in the input bar.
/rewind and /revert work only on the Activity page, where the preview lives. Typed into the game log, they point you there.
Command reference
Section titled “Command reference”| Command | Description | Role |
|---|---|---|
/roll <notation> |
Roll 3D dice with full animation and multiplayer broadcast | All |
Examples:
/roll 2d6+3– roll two six-sided dice plus 3/roll 1d20– roll a twenty-sided die/roll 2d20{a}– roll with advantage (keep the higher of two d20s);2d20{d}for disadvantage
/roll uses the 3D dice notation, which has no kh / kl keep syntax. See Rolling dice for everything it accepts.
The roll lands on everyone’s dice results at the bottom left of the map, in the game log, and in the GM’s activity log.
Roll requests
Section titled “Roll requests”| Command | Description | Role |
|---|---|---|
/rollrequest <formula> [@target...] [title] |
Request rolls from combatants or members | GM |
/rr <formula> [@target...] [title] |
Shorthand for /rollrequest |
GM |
Roll requests create a resolution with roll response requests for each target. Players see a response panel at the bottom of their screen where they can roll and submit their result.
Without @targets – sends to all non-defeated combatants in the active combat:
/rr 1d20+5 Perception Check– everyone in combat rolls perception/rr 1d20 Dex Save– everyone makes a dexterity save
With @targets – sends only to the named combatants or members:
/rr 1d20+3 @Fighter Str Check– only the Fighter rolls/rr 1d20 @Fighter @Wizard Con Save– Fighter and Wizard roll/rr 1d20+2 @Alice Insight– target a player by username (uses their user ID)
Mixing combatants and members – you can target both token names and player usernames in the same command:
/rr 1d20 @Goblin @Alice Stealth vs Perception– the Goblin token and the player Alice both roll
When no @targets are specified, combat must be active. When @targets are specified, you can target room members even without combat running.
Combat
Section titled “Combat”| Command | Description | Role |
|---|---|---|
/combat start |
Start a combat encounter | GM |
/combat end |
End the current encounter | GM |
/turn next |
Advance to the next combatant in initiative order | GM |
/turn set <name> |
Set the active combatant by name | GM |
/turn set uses case-insensitive partial matching. For example, /turn set gob matches “Goblin King”.
Playing cards
Section titled “Playing cards”| Command | Description | Role |
|---|---|---|
/play <card name> |
Play any card’s effect at the selected tokens | GM |
/as |
Play the next cards as the selected token; /as clear stops |
GM |
/loc (or /source) |
Click the map to set where the next card starts from; /loc clear resets |
GM |
/play finds the card by name and fires it at whatever you have selected, without attaching it to anyone.
With /as, the card is played by that token: its numbers are used, it’s where the card starts from, and in combat it pays that creature’s actions (and its multiple attack penalty, in Pathfinder and Starfinder). Select one token, type /as, then select the targets and /play. Use it to run a monster’s turn from the console.
Resolutions
Section titled “Resolutions”| Command | Description | Role |
|---|---|---|
/resolve list |
List all active resolutions with status and response progress | All |
/resolve new [title] |
Create a new roll resolution | GM |
/resolve done <title> [summary] |
Resolve the named resolution with a success outcome | GM |
/resolve cancel <title> |
Cancel the named resolution | GM |
/resolve history |
Show the last 10 resolved or cancelled resolutions | All |
Title matching is fuzzy – type one word of the title or the first few characters of the resolution ID. Only the first word after done or cancel is used to find the resolution; with done, everything after it becomes the summary.
For full details on the resolution system, see the Resolution Guide.
Conditions
Section titled “Conditions”| Command | Description | Role |
|---|---|---|
/condition apply <key> [to <token>] [duration <N> rounds] [stacks <N>] |
Apply a condition to a token | GM |
/condition remove <key> |
Remove a condition | GM |
/condition clear [token] |
Remove every condition from a token | GM |
/condition tick |
Count every timed condition down by one | GM |
/condition list |
List the active conditions in the scene | GM |
Examples:
/condition apply poisoned– poison the selected token until you remove it/condition apply frightened to @Goblin duration 2 rounds– frighten the Goblin for two rounds/condition apply bleeding duration 3 turns stacks 2– two stacks of bleeding for three turns
The condition is labelled with the key you type. For a nicer label, a colour or an icon, use Apply Condition in the Status tab. Always write the unit after the number – duration 2 rounds or duration 3 turns. Without a duration, the condition lasts until you remove it.
/condition remove takes the first condition in the scene with that key, whichever token it’s on. To take it off one particular token when several have it, use the × in the Status tab.
/condition tick is for running time by hand. A condition that reaches zero ends. In combat you don’t need it – conditions count down as turns and rounds pass.
Resources
Section titled “Resources”| Command | Description | Role |
|---|---|---|
/resource create <key> [value] [max <N>] [on <token>] [recharge short] |
Create a resource on a token | GM |
/resource adjust <key> <delta> [on <token>] |
Add to or take from a resource | GM, or a player on a token they control |
/resource set <key> <value> [on <token>] |
Set a resource to an exact value | GM, or a player on a token they control |
/resource remove <key> |
Remove a resource | GM |
/resource list |
List the scene’s resources | All |
Examples:
/resource create hp 30 max 30– give the selected token 30 hit points (and a health bar)/resource create ki 4 max 4 recharge short– a ki pool that refills on a short rest (recharge longfor a long rest)/resource adjust hp -7 on @Kaelan– take 7 off Kaelan’shp/resource set hp 30– put the selected token back to 30
/resource remove, like /condition remove, takes the first one in the scene with that key.
Choosing the token. Wherever a command takes a token (to <token>, on <token>, or the token after clear), you can type @ and part of its name, or leave it out to use the selected token. If nothing is selected and the scene has only one token, that one is used.
Fog of war
Section titled “Fog of war”| Command | Description | Role |
|---|---|---|
/fog reveal |
Reveal all fog of war | GM |
/fog reset |
Reset fog to fully hidden | GM |
| Command | Description | Role |
|---|---|---|
/scene commit |
Save the live scene back to your scene library now | GM |
The live scene already saves back to the library on its own while you play, and when the session closes. /scene commit does it straight away. It saves the map, tokens, walls, lights and fog; conditions, resources and combat belong to the session and aren’t saved to the library.
If the same scene is running in another of your rooms, the automatic save leaves the library copy to whichever room saved it first. /scene commit saves this room’s version regardless.
Rewind and revert
Section titled “Rewind and revert”| Command | Description | Role |
|---|---|---|
/rewind <version> |
Preview the scene at a past event version | GM |
/rewind off |
Exit preview and resume live state | GM |
/revert <version> |
Permanently revert to a past version (destructive) | GM |
Rewind is non-destructive – it shows you what the scene looked like at a past point without changing anything. Use /rewind off or the Resume Live button to return to the current state.
Revert is permanent – it deletes all events after the target version. Use with caution. See the Activity Log guide for full details on rewind and revert.
| Command | Description | Role |
|---|---|---|
/help |
Show a quick reference of all commands | All |
Permissions
Section titled “Permissions”| Role | Available commands |
|---|---|
| GM | All commands |
| Player | /roll, /resolve list, /resolve history, /resource list, /help – plus /resource adjust and /resource set on tokens they control |
| Observer | /resolve list, /resolve history, /resource list, /help |
GM-only commands return an error message when used by players or observers.
How commands work
Section titled “How commands work”Commands dispatch through the server-authoritative command pipeline. When you execute a command:
- The command is parsed and validated locally
- If it requires a server action (combat, resolution, fog), it is sent through the command gateway to the server
- The server validates and applies the command, then broadcasts the resulting event to all connected clients
- The event reaches everyone’s table, and the GM’s activity log, automatically
This means the results of your commands (starting combat, advancing turns, resolving) are visible to everyone in the session in real time.
Dice rolls go through a separate multiplayer dice system that handles 3D animation and broadcasting.
Troubleshooting
Section titled “Troubleshooting”The command input is disabled
Section titled “The command input is disabled”You are in rewind preview mode. The input bar is disabled while previewing a past version. Click Resume Live in the amber banner at the top of the log.
My command returned “Command gateway unavailable”
Section titled “My command returned “Command gateway unavailable””/condition and /resource say “Not in authoritative mode” for the same problem. The server-authoritative pipeline is not active for this room. This can happen if the room is not configured for authoritative mode, or if the connection dropped. Try refreshing the page.
My @mention matched the wrong person
Section titled “My @mention matched the wrong person”The matching system checks for exact matches first, then falls back to substring matching. If two names overlap, type enough characters for an exact match. Use the @mention autocomplete dropdown to verify which target is highlighted before accepting.
The autocomplete is not showing
Section titled “The autocomplete is not showing”- Make sure you are typing
/as the first character. The autocomplete only activates for slash commands. - For
@mentionautocomplete, you need to be past the command name (for example,/rr 1d20 @– the@must come after at least one argument).
I cannot use combat commands
Section titled “I cannot use combat commands”- Combat commands (
/combat,/turn) are GM-only. If you are a player, ask the GM to manage combat. /turn setrequires an active combat encounter. Start combat first with/combat start.
Roll requests say “No active combatants”
Section titled “Roll requests say “No active combatants””When using /rr without @targets, combat must be active and have at least one non-defeated combatant. Either:
- Start combat with
/combat startand add combatants - Use
@targetsto specify room members directly:/rr 1d20 @Alice @Bob Save