Myth-Weavers Help

Dice Rolling

Myth-Weavers has a built-in dice roller wired directly into the posting experience. Rolls are server-side, timestamped, and tamper-proof. This makes it easy for GMs and players alike to keep track of previous rolls and combat in the play-by-post style.

The dice roller is designed to mimic the real table. You roll dice while crafting your post rather than having to wait for the post to save to see the results. Rolls are immediately permanent parts of the topic's timeline; they can't be hidden from the GM or other players (though hidden rolls can be later revealed). No cheating!

How to roll

In any topic, open the Dice Roller panel. Standard dice notation:

Type, click Roll, or use ⌘/Ctrl+Enter for the keyboard shortcut. Not sure of the syntax? The ? Syntax button on the dice panel opens a quick reference.

A single roll line is capped at 200 dice (counting any rerolls or exploding dice it generates) — well beyond any normal roll. If you exceed it, the roll is rejected with a "maximum of 200 dice" message and nothing is posted; split it into smaller rolls.

Notation in detail

The standard formula is [number]d[sides][operation][modifier]1d20+3 rolls one d20 and adds 3.

Functions

More complex rolls use function-call syntax: the function name wraps the dice in parentheses, e.g. keep(4d6,highest,3). Two rules apply throughout:

Throughout, order is highest or lowest and direction is above, below, or both.

keep / drop

keep(dice, order, number) rolls the dice and keeps the number highest or lowest; drop(dice, order, number) discards them instead. Omit number and one die is kept/dropped. keep and drop are inverses — keep-highest-3 of 4d6 equals drop-lowest-1.

sort

sort(dice, order) returns the rolled dice sorted highest-to-lowest or lowest-to-highest — sort(4d6,highest).

reroll

reroll(dice, threshold, direction, count) rerolls any die at or beyond the threshold. With below, dice at or under the threshold are rerolled; with above, dice at or over it. count caps how many times each die is rerolled — omit it (or use 0) for unlimited. Default direction is below.

explode

explode(dice, threshold, count) — for each die at or above the threshold, roll an extra die; if that one also reaches the threshold it explodes again. count limits the chain (omit or 0 for unlimited) — explode(3d6,6).

success / failure

success(dice, threshold, direction, cancel, bonus) counts how many dice meet the criteria. above counts dice at or over the threshold; below, at or under it. Set cancel to yes to let each 1 cancel a success, and bonus to yes to add a success for each maximum die rolled. Both default to no.

failure(dice, threshold) counts dice at or below the threshold — the same as success(dice, threshold, below).

repeat

repeat(expression, count) runs the whole expression count times and returns a list of results. Because the result is a list, you can't add to it at the top level — put any modifier inside: write repeat(keep(4d6,highest,3)+4,6), not repeat(keep(4d6,highest,3),6)+4.

Game systems

Several systems have dedicated roll functions:

Common rolls

Paste these straight into the panel (rename the label before the colon to taste):

Visibility

Decide who sees the result before you roll:

The pending-and-claim flow

After rolling, the result sits in your Pending Rolls panel. Pending rolls aren't attached to any post yet — they're staged.

This is the core dice mechanic: roll first, then write the post and claim the rolls you want to attach. The rolls appear inline in the timeline, timestamped to when they were originally rolled, not when you claimed them. That way the correct rolls show up when that action was taken, so the GM can see exactly when something was rolled.

Why pending-and-claim matters

PBP runs on trust, but pure trust scales badly across years and dozens of players. The pending-and-claim model makes the trust mechanical: every roll is permanently recorded and timestamped at the moment of rolling, not the moment of claiming. A GM can see that someone rolled six times in a topic and claimed two — visible, not necessarily punishable, but a basis for a conversation if the pattern matters. Most players never need to think about it; it's there for the rare case where it does.

In the timeline

Claimed rolls show up inline in the topic, in chronological order. Each displays:

[GM]

Adding a roll a player forgot. If a player wrote their post but forgot to claim the roll, you don't have to make them redo it. Roll the dice yourself in that topic's dice panel — the result lands in the timeline as an unclaimed roll. On that roll's card, Claim into player's post above attaches it to the post directly above (the buttons name whose post they target, so you always know where it's going). Because you're a GM you can claim into any member's post in your game, not just your own.

Undoing a claim. Claimed the roll into the wrong post? Open the roll's Show details (in the roll panel under the post) and use Detach from post. The roll pops back out to the timeline at its original spot, ready to claim again. Anyone who can edit the post can detach a roll from it.

Roll history

Every roll is permanently recorded. The full roll history for a topic shows every roll ever made there — who, what, the results, the visibility. Useful for the rare audit and for the always-interesting "wait, when did Jen's character last crit?" stats.​

Next steps

Your character probably needs a home. Characters, Resources, and Maps covers sheet linking, wiki pages, and the rest.