Skip to content
Recluse Studio
← Field notes

The rulebook that assumes you already know another game

A short RPG publication may need an external rules system, shared conventions or simply an example. Those dependencies call for different kinds of support.

Two simple folded sheets meet at an incomplete green ink connection, with white splatter and purple washes across dark scratched paper.
Original illustration / OpenAI image generation

The Rap Sheet’s second issue proposes an initiative procedure for GUMSHOE games. Its instructions refer to an Athletics General Ability Test and to existing game concepts. The two-page fanzine is doing the work of a supplement. A reader needs the relevant rules context to use its proposal. The May 2009 issue

A small publication can depend on another game in that direct way. It can also supply its own rules while assuming familiarity with roleplaying conventions. Those are different conditions, and a librarian recommending the publication needs to know which one applies.

I am examining publishers’ descriptions and the explicit dependencies in the cited texts. The suggested preparation exercise below is my own method for identifying missing support, not a reported playtest or a claim about how all beginners learn.

Separate the rules source from the rules tradition

CBR+PNK Core identifies its relationship to Forged in the Dark and describes a GM Guide containing core rules and the steps for running a one-shot. Its Runner File contains player-facing material, while the Framework provides further guidance. A statement of design lineage does not establish that the reader must buy Blades in the Dark.

That distinction prevents a common descriptive shortcut. A game can borrow and adapt a rules framework while publishing the procedures needed for its own use. Conversely, an adventure can contain many pages of original writing while relying on a separately published rulebook. Page count cannot settle the dependency.

The practical question is what the selected publication says it supplies and what it explicitly requires. A catalogue note can record a named external system or edition where the source identifies one. A reader should not have to infer the requirement from an abbreviation in a product tag.

An edition matters because a familiar system name can cover changed procedures. If the library has a supplement and a rulebook, their relationship needs checking at the level relevant to use. Merely shelving the two together does not establish that their statistics or instructions correspond.

A complete procedure can still be unfamiliar

A reader may have all the required rules and still need to see how they are used, because describing a situation, choosing an action and interpreting a result involve conventions that a compact text may explain with varying amounts of detail.

The Cairn first-edition site offers an SRD alongside an example of play and a FAQ. Those routes make different kinds of support available. Their presence is not evidence that the rules have failed. It recognises that a reference text, a worked example and an answer to a recurring question do different jobs.

A library can make those routes visible without pretending to assess their effectiveness from their existence alone. The useful description says what support is available and where it can be found. A claim that the support works for a particular audience would require observing that audience’s use.

For a public session, the facilitator’s preparation should include the conventions that the opening activity will require. For an academic exercise, the same material can become an object of analysis: what knowledge does the text state, what does it demonstrate and what does it leave to a reader’s previous experience?

Assistance should follow the task

Wood, Bruner and Ross’s 1976 study of tutoring describes assistance shaped by both a task and a learner. Its account of scaffolding includes demonstrating, marking important features and temporarily reducing aspects of a task. The study concerned young children assembling a wooden structure, so it supplies concepts for thinking about assistance rather than evidence about RPG learning.

Applied cautiously, the useful question is what a participant needs help doing at a particular moment. Explaining every rule before play may supply information the person cannot yet place. Explaining nothing may leave the person unable to recognise what choices are available. The appropriate support has to be worked out through the activity and the participants.

Consider an invented opening scene in which a character tries to enter a guarded archive. Before using it in a library session, the facilitator can trace what the game asks the group to do. Who describes the obstacle? What information is available? Who decides whether a roll is required? Where is the relevant procedure?

If the answer depends on an external rulebook, that book needs to be available. If it depends on a convention, the facilitator needs a clear explanation or demonstration. If the game deliberately leaves the decision to the group, the facilitator should present that freedom accurately rather than inventing an official rule.

Record the support without rewriting the game

A brief preparation note can identify required materials, useful references and decisions the facilitator expects to explain. It should distinguish the publisher’s instructions from local adaptations. That distinction lets another facilitator understand what belongs to the game and what was added for a particular audience.

The note can also identify a point at which a participant might need another format. A dense reference sheet may be convenient for one reader and difficult for another. Providing an available accessible version is a different intervention from teaching a rule, even though both may be necessary for participation.

For collection development, I would record dependencies that materially affect use. A supplement requiring a particular system deserves that note. A game offering optional examples deserves links or references where appropriate. The description should help a reader make a decision without labelling every compact publication as suitable or unsuitable for beginners in the abstract.

The smallest book can carry a complete game, and a large book can assume substantial prior knowledge. What matters is the relationship between the text, the task and the reader. A good recommendation makes that relationship visible and provides the support needed for the intended use.