Skip to content

Asking for rolls

The resolution system handles the back-and-forth between the GM and players when an action needs rolls, choices, confirmations, or other input before its outcome is determined. Think of it as the structured conversation that happens between “I cast Fireball” and “14 damage to all targets”.

This guide covers how resolutions work for both players and GMs.

A resolution is a pending item that collects input from one or more players before the GM determines the outcome. It can represent:

  • An attack roll or saving throw
  • A skill check or ability check
  • A choice between options
  • A confirmation (yes/no reaction)
  • Any other game action that needs player input

Resolutions are shared across the session. Everyone can see what is being resolved, and the GM manages the queue.

When the GM creates a resolution and assigns you a response request, a response panel appears at the bottom of your screen. It shows:

  • The title of the resolution (for example, “Fireball – DEX Save”)
  • A prompt telling you what to do
  • An input area appropriate to the type of response needed

If you have multiple pending responses, arrow buttons let you navigate between them.

For roll requests, you have two options:

  1. 3D Dice – Click the “Roll” button. The dice animate on screen, and the total is filled in automatically. Click “Submit” when you are ready.
  2. Manual entry – Type a number in the “Total” field if you prefer to roll physical dice or use another tool. You can also add an optional “Degree” label (like “critical hit”).

The formula shown (for example, 1d20+5) is a hint from the GM – it tells you what to roll. If a difficulty or target number is shown (for example, DC 15), that is what you need to meet or beat.

After rolling, click Submit to send your result to the server.

For choice requests, you see a list of options. Click one to select it (or multiple if the request allows). Then click Submit Choice.

For confirmation requests, you see two buttons: Confirm and Decline. Click whichever applies.

Some requests ask for a text answer or a number. Type your response and click Submit.

Your response is locked in and visible to the GM. Once all requested responses have been submitted, the resolution moves to a “ready” state, and the GM can determine the outcome.

You cannot change your response after submitting. If you made a mistake, ask the GM – they can cancel your response request and create a new one.

The Resolution Panel is available in two places:

  1. Actions tab in the sidebar (the crosshair icon in the tab bar) – scroll down past the Targeting section
  2. Floating on the canvas if you pop it out using the “Pop out” button

Both locations show the same live state. You can interact with either one.

Click the + button in the Resolution Panel header to open the create form.

  1. Enter a title (for example, “Attack Roll” or “DEX Save”)
  2. Choose the type (Roll, Check, Contest, Choice, Confirmation, Action, Effect, or Custom)
  3. Optionally add a description
  4. Optionally add response requests inline before creating (see below)
  5. Click Enqueue (or “Enqueue + N requests” if you added inline requests)

You can also create resolutions from:

  • The “Targeting Confirmed” card that appears after a targeting request is confirmed (pre-fills targets from the confirmed targeting)
  • The activity console with /resolve new [title]
  • The command console with the resolution.enqueue template

After creating a resolution, expand it by clicking the arrow, then click Add Response Request. A form appears with:

  • Assign to – dropdown of room members (players listed first, GM and others in a separate group)
  • Kind – Roll, Choice, Confirmation, Text, Number, or Custom
  • Label – short name shown to the player (for example, “DEX Save”)
  • Prompt – longer text the player sees (for example, “Roll a Dexterity saving throw”)

For Roll requests, additional fields appear:

  • Formula – dice notation hint (for example, 1d20+5)
  • TN – target number the roll needs to meet
  • Difficulty – human-readable label (for example, “DC 15”)

For Choice requests, an option builder appears:

  • Add options with labels (minimum 2)
  • Set min/max number of picks

Click Send Request to assign it to the selected player.

To avoid adding one request at a time:

  • Inline requests on create – The create form has per-player buttons at the bottom. Click a player’s name to add a request row for them. Click “All players” to add one for everyone. During combat, “All combatants” adds one for each non-defeated combatant with a player controller.
  • “All players” / “All combatants” on the add form – These buttons appear at the bottom of the response request form and send the same request (same kind, label, formula, etc.) to each player or combatant in one click.

When a player submits a response, their entry in the panel updates:

  • Roll responses show the total in a highlighted badge. If a target number was set, a pass/fail indicator appears: 18 vs DC 15 pass (green) or 12 vs DC 15 fail (red). If the player included a degree (like “critical hit”), it shows in italic.
  • Choice responses show the selected option labels (resolved from the options you defined, not raw IDs).
  • Confirmation responses show “Confirmed” or “Declined”.
  • Text responses show the text (truncated if long).

When all response requests are submitted (or cancelled), the resolution automatically moves to Ready status and highlights in green.

Click the Resolve button on a ready resolution. A form appears with:

  • Outcome status – Success, Failure, Partial, Mixed, or Custom
  • Summary – optional text describing what happened (for example, “Hit! 18 vs AC 15. 8 slashing damage.”)

Click Resolve to finalize. The resolution is removed from the active queue, and the outcome appears in the activity log.

Click the X button on any resolution to cancel it. This removes it from the queue. You can also cancel individual response requests without cancelling the whole resolution.

Five /resolve commands are available in the activity console:

Command What it does
/resolve list Lists all active resolutions with status and response progress
/resolve new [title] Creates a new roll resolution
/resolve done <title> [summary] Resolves the named resolution with a success outcome
/resolve cancel <title> Cancels the named resolution
/resolve history Shows the last 10 resolved or cancelled resolutions

Title matching is fuzzy – you can type part of the title or the first few characters of the ID.

In the Actions sidebar tab, a History section at the bottom shows recently resolved and cancelled resolutions. Click the header to expand it. Each entry shows:

  • Resolved (green check) or Cancelled (gray X) icon
  • Title and optional outcome summary
  • Timestamp

This history is built from the event log and updates automatically.

A resolution goes through these stages:

Status Meaning What happens
Pending Just created, no response requests yet GM can add response requests or resolve immediately
Waiting Has pending response requests Players see the response overlay, submit their input
Ready All responses are in GM can review results and resolve
Resolved GM determined the outcome Removed from active queue, recorded in history
Cancelled GM cancelled it Removed from active queue, recorded in history

The transition from Waiting to Ready happens automatically when every response request has been submitted or cancelled.

The typical flow for a combat action:

  1. Targeting – The GM starts targeting (from the GM Targeting Panel). The player selects targets and confirms.
  2. Bridge – A “Targeting Confirmed” card appears in the Resolution Panel. The GM clicks “Create Resolution” to enqueue a resolution with those targets.
  3. Resolution – The GM adds response requests (for example, a saving throw for each target). Players roll and submit.
  4. Outcome – The GM reviews the results and resolves with an outcome (for example, “14 fire damage, half on save”).

Steps 1 and 2 can be skipped – resolutions can be created independently of targeting.

Resolution events appear in the activity log with a purple checklist icon:

Entry What it means
“Attack Roll enqueued” A new resolution was created
“DEX Save requested” A response request was sent to a player
“DEX Save submitted – 18 vs DC 15” A player submitted their roll
“Attack Roll resolved – Hit!” The GM resolved with an outcome
“Attack Roll cancelled” The GM cancelled the resolution
Colour Status
Yellow Pending – waiting for the GM to act
Blue Waiting – response requests are out, waiting for players
Green Ready – all responses collected, waiting for GM to resolve
Gray Resolved or Cancelled (only shown in history)
Role What you can do
GM Create, update, cancel, and resolve any resolution. Add and cancel response requests. Submit responses for anyone.
Player Create resolutions for your own tokens. Submit responses assigned to you. Cannot modify other players’ responses or manage the queue.
Observer View resolutions in real time, but cannot interact.
  • There may be no pending response request assigned to you. The panel only appears when you have something to respond to.
  • Make sure you are connected to the room. The panel requires a live connection.
  • If you are an observer, you will not see the panel.
  • Check that the response request is still pending. It may have been cancelled by the GM.
  • Make sure you are filling in the correct input. Roll requests need a number in the total field. Choice requests need at least one option selected.
  • The 3D dice system sometimes takes a moment. Wait for the animation to complete.
  • If it times out, use the manual entry field to type your total.
  • If the dice button is grayed out, the dice system may still be loading. Wait a moment and try again.

You cannot change a submitted response. Ask the GM to cancel your response request and create a new one for you.

The resolution says “Ready” but nothing is happening

Section titled “The resolution says “Ready” but nothing is happening”

The GM needs to click the Resolve button to determine the outcome. “Ready” means all player input has been collected – the GM has not acted yet.

  • If you are a player, you only see your own response requests (via the bottom overlay panel). The full resolution queue is visible to the GM in the Resolution Panel.
  • If you are the GM and the panel is empty, no resolutions have been created yet. Click + to create one.

The Targeting Confirmed card disappeared before I could create a resolution

Section titled “The Targeting Confirmed card disappeared before I could create a resolution”

The card dismisses when a new targeting request starts or when you dismiss it manually. You can still create a resolution manually using the + button or the /resolve new slash command.

Yes, but only for their own tokens. The resolution’s source token must be one the player controls (listed as a controller on the token, or linked to a character they own) — the app checks this before accepting it.

No. The resolution system is game-system-agnostic. It collects input and records outcomes, but it does not know what “success” or “failure” means for your game. The GM interprets the results. Future game system modules can add automatic evaluation on top of this foundation.

Can I use resolutions without targeting first?

Section titled “Can I use resolutions without targeting first?”

Yes. Resolutions are independent of targeting. You can create a resolution directly from the panel, slash commands, or command console without any targeting step.

Yes. Resolved and cancelled resolutions are removed from the live queue but recorded in the event log. The History section in the Actions sidebar tab shows recent ones, and /resolve history lists the last 10.

Can multiple resolutions be active at the same time?

Section titled “Can multiple resolutions be active at the same time?”

Yes. The queue supports multiple concurrent resolutions. Each one tracks its own response requests and status independently.

The 3D dice system supports standard notation including:

  • Basic rolls: 1d20, 2d6, 3d8
  • Modifiers: 1d20+5, 2d6-1
  • Advantage/disadvantage: 2d20kh1 (keep highest), 2d20kl1 (keep lowest)
  • Multiple dice: 4d6kh3 (roll 4, keep 3 highest)
  • Exploding dice: 4d6!!

The formula shown in a response request is a hint – you can always type a total manually instead.