Dice rolls in RedM roleplay: when to roll and how to read a d20

Why wild west RP scenes need dice

Roleplay has no referee. When two cowpokes each swear their character throws the harder punch, resolution comes down to who types faster or argues louder, and that sours a scene quick. A dice roll is the neutral party: both players agree to abide by the number before it lands, and suddenly there is nothing left to fight about out of character.

Dice also keep you honest as a storyteller. If you always decide your own outcomes, you will always pick the flattering ones. A fate roll in RP forces surprise back into the scene. The stagecoach job goes sideways, the bluff at the poker table collapses, the leap across the ravine comes up a boot short. Failed rolls fork the story into places you would never have steered it on purpose, and those forks are where the best sessions live.

The /dice command in RedM versus a web roller

Most RedM servers ship an in-game dice command, usually /dice or /roll depending on the framework. Type it and a number prints in local chat for the folks standing near you. It is fast, it is built in, and for quick table calls it is all you need. Check your server's rules for the exact command and any etiquette around using it.

The limits show up in bigger scenes. A chat roll is a bare number with no meaning attached, it is only visible to players in range, and it scrolls away the moment somebody types. A web roller does a different job. The d20 roller at d20rp.com pairs the number with a written outcome: pick a scenario from its 133 fate tables, roll once, and the whole posse reads the same graded result, twenty distinct outcomes instead of one integer you still have to interpret.

• Use /dice for fast, low-stakes calls: who buys the round, who takes first watch, whether the rusty lock gives
• Use a web roller for injuries, fates and anything with lasting consequences, where the wording of the outcome matters as much as the number
• Use whichever your server mandates for contested PvP, and ask staff if you are not sure

Reading a d20 as a fate ladder

A raw number means nothing until your table agrees what it buys. The severity ladder the roller uses reads every d20 as a band of fortune, from disaster at the bottom to a tale you will retell for months at the top.

Two habits make the ladder work. First, commit to the bands before you see the number, no quietly downgrading a 3 to a scratch after the fact. Second, play low rolls as gifts. A catastrophic result hands you a limp, a scar, a debt or a grudge, and every one of those is plot.

• 1, catastrophic: the worst version of events. The wound is grave, the fall is bad, the plan collapses
• 2 to 4, severe: serious harm or hard failure, with consequences that linger
• 5 to 8, serious: it went wrong, and your character will feel it for a while
• 9 to 13, moderate: the middle of the ladder. A real setback, recoverable with care
• 14 to 17, minor: scraped, shaken and bruised, but walking
• 18 to 19, lucky: you got away with it, mostly
• 20, miraculous: the story nobody at the saloon believes

When to roll and when to just play it

Not everything needs dice. Walking into the saloon, chatting up the barkeep, riding the trail to town, just play it. Reach for a luck roll when the outcome is genuinely uncertain and both answers would be interesting.

One roll per story beat is plenty. Roll, honor the result, and move the scene forward. Rolling again until the number flatters you defeats the entire point of asking fate in the first place.

• Contested actions: two characters grab for the same rifle, arm wrestle, race their horses, or square off where your server's rules allow rolled duels
• Injuries: after a gunfight, a horse wreck or a bad fall, roll to find out how badly your character is actually hurt instead of deciding it yourself
• Story forks: the trail splits, the fuse is lit, the only doctor in town is drunk. Let the die pick the branch nobody controls
• Long shots: lassoing a runaway wagon, calming a spooked bull, sweet talking a lawman who already has the irons out

House rules: building a dice system your crew agrees on

RP dice rules only work if everyone agreed to them before the lead starts flying. Five minutes around a campfire or in a Discord channel settles it. Write the answers down where the crew can see them, and treat them as table law until everyone agrees to change them.

Keep in mind that most servers leave fate rolls to player agreement and only mandate dice in specific contested situations. Your crew's system rides on top of the server's rules, never over them, so check what staff require before you formalize anything.

• Who can call for a roll: anyone in the scene, only the player acting, or a designated referee
• What each band means at your table: does a 5 to 8 mean a broken bone or just a bad afternoon
• Modifiers: does a trained field medic, a drunk character or a midnight storm shift the roll, and by how much
• Contested rolls: highest wins, or does the defender take ties
• Rerolls: never, once per session, or only when everyone agrees the first result made no sense

Rolling without powergaming

A die can decide what happens to your character. It cannot force an outcome onto somebody else's. That line is the whole difference between a fate roll and powergaming. Roll to learn whether your punch flies true, then give the other player room to describe how it lands on them. And consent comes before consequences: for anything that maims, scars or captures another character, get an out of character yes before the dice ever leave the cup.

The /me convention carries the same principle. Describe the attempt and your character's state, never the result on the other person.

• /me squares up and swings a wild haymaker toward the drover's jaw
• /me tries to wrench the scattergun out of the stranger's grip
• /me fumbles at the knot with rope-burned fingers, trying to work a hand free

Sharing roll results so nobody can fudge them

The oldest trick in any dice game is claiming the roll went your way when nobody saw it land. Private rolls invite exactly that suspicion, even between honest players, and suspicion is poison to a long-running rivalry.

The fix is visibility. Roll where the scene can see it: in local chat where the command prints for everyone present, or on a shared page where every player reads the identical result. The roller at d20rp.com keeps rolls logged on a shared page with a leaderboard, so the whole posse can point at the same catastrophic 1 and nobody can quietly promote it to a 15. When a roll decides something that matters, a screenshot in the crew's Discord settles future disputes before they start.

Questions from the floor

Keep reading