Rules coverage
Last checked against the code on .
Keystone Engine applies fifth edition as you play, so you never look a rule up. It does not apply all of it. This page is the full list, including the parts it does not do, because a product that publishes only the parts it is good at is asking you to take the rest on trust.
Of the fifth edition reference Rolegend is built from, 87 sections are enforced in code, 17 are partly enforced with the gap described below, and 39 are left to ROWAN to adjudicate in prose.
What the four statuses mean
- Enforced
- Keystone applies it. It happens whether or not anybody remembers it, and it cannot be talked out of.
- Partly
- Some of it is applied and some is not. Each row below says which half is which.
- Not enforced
- The rule exists in the reference and nothing in the code applies it. ROWAN may still describe it, which means it is narrative rather than mechanical.
- Not modelled
- Not implemented at all. Reference only.
The rules people ask about
These are the rows worth naming individually: the ones a rules-literate player will notice the absence of within an hour of play.
- Movement and distance (Not enforced)
- A speed is stored on each participant, but nothing spends it. There is no grid. Distance is narrated.
- Cover (Not enforced)
- Cover is not tracked in encounter state. A half-cover bonus is applied by the Game Master or not at all.
- Opportunity attacks (Not enforced)
- Not triggered automatically. The Game Master has to notice the trigger and call the roll.
- Flanking (Not enforced)
- No positional model, so adjacency is a narrative judgement.
- Mounted and underwater combat (Not modelled)
- Neither ruleset is implemented. Both are reference only.
- Grapple and shove (Partly)
- The condition can be applied. The speed-zero effect that makes it matter is not enforced.
- Encumbrance (Partly)
- Carried weight against Strength is enforced and imposes disadvantage. The speed penalties are not.
- Conditions (Enforced)
- Stored as rows, and the dice code applies them: auto-failed saves, attacker advantage, self disadvantage, the cannot-act block.
Where the rest of it is going
The gaps above are worked on in the open and none of them has a date attached to it. The roadmap on the home page is the short version.
Game data derives from the System Reference Document 5.1 under CC BY 4.0. The required statement is on the attribution page.