Pourquoi on s'ennuie dans le JdR narratif ? (s'inspirer de l'OSR)

Main ideas / lessons

• “Personal and visceral” roleplaying needs an “engine” (the gameplay driving force), not only narrative presentation.

  • Narrative GMs often focus on structure and staging (the “fuselage”), but neglect the underlying gameplay engine that makes players feel things intensely.
  • Without this engine, the game becomes an empty shell that can’t produce immersive, emotional participation.

• A narrative game only works if player actions create real consequences.

  • Simply moving from scene to scene, adding emotional music, or preparing story beats doesn’t create gameplay if players don’t:
    • solve problems,
    • face meaningful challenges,
    • make impactful choices whose outcomes reshape the world.

• Inspiration for the engine can come from OSR (Old School Revival), even for narrative-focused styles.

  • The speaker contrasts “narrative school” play with OSR, but argues there are many shared principles.
  • The OSR philosophy is presented as a way to ensure the engine produces choices, decisions, and tension.

The “OSR engine” in three pillars

Rules support the engine secondarily; the engine itself is built on three pillars.

1. Choices (options presented in a world that functions even without PCs)

   • The world should feel alive and continue evolving.
   • Players need clear, visible options (not ambiguity that wastes time searching).
   • Options can be generated via rumors, points of interest, and sandbox-style structure.
   • Choices become more engaging when the PC/player has personal reasons to pursue them (not just generic hooks).

2. Decisions (what players ultimately commit to, with tangible impact)

   • Decisions must change the world in observable ways.
   • The GM should capitalize on player decisions, not force players back onto a predetermined track.
   • Because OSR often avoids scripted sequences, the GM improvises based on what players do.
   • Decisions are also driven by player intelligence and creativity, not by scanning a character sheet first for mechanical solutions.

3. Tension (often tied to time and stakes)

   • Tension is frequently produced by the passage of time (similar to clocks in PBTA).
   • Actions take time, allowing other factions/world elements to respond.
   • Tension comes from costs/stakes:
     • fast actions can create noise or risk,
     • careful actions can take longer and still carry danger.
   • The GM can use procedures/random tables (and timed turns) as tools to generate tension—though the speaker is not blindly pro-randomness.

Rules: simple and secondary

• Rules should be simple and not the primary engine.
  • Dice rolls should be infrequent and used where there is doubt or uncertainty.
  • Rolls must produce tangible results; “filler” rolls that don’t matter don’t create gameplay.
  • Example concept: if the negotiation already implies factual consequences (e.g., the NPC is the other party’s son), the outcome can follow world logic rather than extra dice.

Prepare situations, not rigid scenes

• Prepare situations, not rigid scenes/sequence paths.
  • Put yourself in the players’ shoes and ask:
    • “What options would I have?”
    • “What alternatives exist?”
  • If you can only find 1–2 options, it may become corridor-like and offer little player agency.
  • If you find several (3–5+), trust that players will likely find even more—this supports meaningful choices, decisions, and tension.
  • The speaker warns against trying to maintain total control; more options are not necessarily a problem.

A “hybrid” stance: OSR engine + narrative framework

• Hybrid approach: OSR engine + narrative framework, with some differences.
  • Keep narrative logic as an element the GM can arbitrate with (rules can be adapted/modulated situationally).
  • The GM’s relevance and intelligence remain crucial to inject narratively interesting, coherent consequences.

Key disagreement: character death frequency

• Disagreement with OSR proponents: character death frequency.
  • OSR often has higher mortality, based on the idea the world doesn’t care about PCs.
  • The speaker partially agrees but argues:
    • very frequent, trivial death can weaken tension and the personal/visceral connection.
    • tension can come from other penalties too: ally death, lost resources, world changes that harm player objectives.
  • PCs can be “main characters” without being invincible; spotlight should remain variable and tied to narrative choices and tension.

Methodology / instruction-style bullet points (how to build the “engine”)

1. Step 1: Build the gameplay engine first (not the narrative fuselage).

   • Temporarily set aside large narrative staging/structuring (“fuselage”).
   • Focus on enabling gameplay that generates:
     • choices,
     • problems to solve,
     • challenge,
     • impactful decision points,
     • tension created through consequences.

2. Step 2: Create a clear menu of player options (OSR “Choices” pillar).

   • Design the world so it can act without PCs.
   • Provide visible, usable options (avoid over-reliance on ambiguity).
   • Use tools like:
     • rumors,
     • points of interest,
     • sandbox-style hooks that relate to what players can actually do.
   • Ensure hooks become meaningful by giving PCs personal reasons/interests to pursue them when possible.

3. Step 3: Make sure “Decisions” have real, tangible world impact.

   • When players commit to an action, change the world accordingly.
   • Do not merely “pretend” choices will matter while steering players back to the preplanned sequence.
   • Be ready to improvise consequences directly from player actions (since you may not plan exact next scenes).

4. Step 4: Encourage player-led problem solving (player creativity before character-sheet searching).

   • Position players as the main drivers of solutions through:
     • strategy,
     • ideas,
     • creativity,
     • interaction with each other.
   • Then consult character abilities/rules to adjudicate how those ideas work.

5. Step 5: Generate tension (often via time, costs, and stakes).

   • Tie actions to time passage so other world elements can respond.
   • Use tension tools such as:
     • turn/time procedures,
     • reaction/cost mechanics,
     • (optionally) random/procedural methods to create pressure.
   • Ensure every meaningful action has a trade-off (faster vs safer; loud vs quiet).

6. Step 6: Use rules as a secondary support, not the engine.

   • Dice are for uncertainty; avoid constant rolling.
   • When dice are called for, the result must materially affect the situation/story/world.

7. Step 7: Prepare “situations,” not strict “scene sequences.”

   • Ask what options exist from the players’ perspective.
   • Aim for enough options (not corridor behavior):
     • too few options → linearity,
     • several options → branching agency.
   • Don’t try to micromanage control; manage coherence and consequence instead.

8. Step 8: Reintroduce narrative fuselage gradually, after the engine works.

   • Once the engine produces good gameplay, add narrative elements.
   • Avoid stacking too many complex narrative mechanics at once.

Speakers / sources featured (as mentioned)

• Speaker/host: The narrator of the RPG Stats channel (no personal name provided in subtitles; referred to as “I” / “me”).
• Channel/source referenced: RPG Stats
• Games referenced:
  • Shadow Dark (as an example of OSR returning into fashion)
  • PBTA (Powered by the Apocalypse; referenced via “clocks”)
  • Basic/Extreme Dungeons & Dragons (example of 10-minute turns / wandering monsters procedure)
• System referenced by the speaker:
  • The speaker’s “minimalist decimation system” (V2) (mentioned as a 3-page system used for sessions)
• Style/framework references:
  • OSR (Old School Revival)
  • OSR proponents / old-school role-playing gamers (YouTube community referenced generally)