← All documentation

Players · Chronicle staff

Roll dice & use result buttons

Roll from Discord or the website, use reroll presets, and inspect the complete result history.

Checked against the live application · 2026-09-20

Roll from Discord

  1. Use /dice inside the Chronicle's Discord server.
  2. Choose one of the dice systems enabled for that Chronicle.
  3. Choose a character when you want the result tied to its sheet, or choose the characterless option for a general pool test.
  4. Enter Pool, Difficulty, and Reason. Pool is the final total, including modifiers you have already calculated; Blood Surge is added by its own procedure.
  5. Check the displayed Dice Channel and submit. The saved result is posted there in an embed.

A linked character supplies its own Hunger or Rage. Character choices are your eligible, accepted sheets in that Chronicle. Without a character, enter the relevant Hunger or Rage value yourself. Characterless pool tests still require current server membership but can be available before character-application setup is finished.

The workflow uses Discord selections, buttons, and forms, so it is available in both desktop and mobile Discord. This guide documents the controls; it does not claim testing on every phone or Discord client version.

Difficulty accepts whole numbers from 0 through 10. Use it when you want the rolled success count without a positive target. The saved result and any reroll retain Difficulty 0 and report the margin; Hunger and Rage outcome rules still apply. Negative Difficulty is rejected.

Back to top ↑

Roll from the website

  1. Open the Chronicle and select Roll Dice.
  2. Choose Dice system and Roll type, then the optional character and applicable fields.
  3. Read the channel destination and any validation messages before submitting.
  4. Open the result to inspect faces, outcome, tracker changes, and delivery status. The bot posts the same saved result to the configured channel.
Back to top ↑

Choose a reroll action

Choose a reroll action
ButtonHow the preset chooses dice
Willpower Re-RollUp to three eligible failed dice.
Max CritsEligible failures first, then ordinary successes if slots remain, keeping existing 10s.
Avoid MessyRegular 10s whose reroll could remove the critical pairing, when this is possible within three dice.
Risky AvoidThose regular 10s, with remaining slots filled by eligible failed dice.

Vampire pool results display all four presets, with unavailable ones disabled. Werewolf and ordinary V5 pools use the two applicable Willpower presets. Checks and procedures without Willpower rerolls do not show these controls.

Only the player who made the roll can use its buttons. Confirm the chosen dice and the Willpower cost in the private confirmation. Hunger dice are protected; Rage dice showing 1 or 2 are protected. A reroll can produce a worse result.

Back to top ↑

Willpower and expiry

For a linked character, an accepted reroll applies one superficial Willpower damage through the tracker service and shows the updated tracker. It also handles applicable damage overflow.

For a characterless roll, explicitly confirm that you have Willpower available and will record the cost yourself. The result identifies manual tracking; no character sheet is changed.

The default reroll window is 24 hours. Staff can change Re-roll window (hours) for future rolls in Play & automation. Every reroll retains the original closing time. At expiry, the embed actions are disabled; a confirmation opened earlier cannot spend Willpower after the deadline.

Back to top ↑

Find logs and delivery problems

  1. Open Dice Logs on the Chronicle page or use /dice-logs.
  2. Filter by player, character, system, roll type, outcome, dates, or roll number.
  3. Open a result to follow its original roll, rerolls, inputs, and resource changes.
  4. Owners and Server Staff can inspect the Chronicle's full new dice log and export filtered results as JSON. Other members see their own results.

Resolution and Discord delivery are separate. A delivery retry reuses the saved faces; it does not roll again. If a result is saved but not delivered, inspect its delivery status and ask staff to check channel access. Avoid rerunning a resource-spending command just because an embed is delayed.

Back to top ↑