⚠️ Historical Document. This captures the Session 17 breakthrough that reoriented the project. The design questions it poses have since been answered (Sessions 18–22). For current locked truths, see Vault Knowledge. Do not use this document as a reference for active decisions.
New Direction
This document captures the core clarity from Session 17.
The Root Problem
Sixteen sessions of design produced real playtest friction. Session 17 identified why:
The mechanics have been working against the game, not for it.
The Chef RPG theme is right. The restaurant world came directly from the players — it was their first idea when they wanted to play DnD. That spark is valid and worth building on.
The problem is what got built on top of it: stat systems, card battles, point distributions, phase mechanics. All of it borrowed from traditional RPG frameworks that the players don’t want.
What Players Actually Want
From direct observation and playtest feedback:
- Collaborative storytelling — everyone shouting ideas, riffing off each other
- Creative expression — drawing scenes, inventing dishes, building monsters
- Weird and funny — the comedy IS the game
- Simple entry — no rulebooks, no backstory, just start playing
- Everyone active — short attention spans, needs constant engagement
- Not win/lose focused — they don’t care about job completion
They do NOT care about:
- Job completion or pass/fail conditions
- Stat optimization
- Complex mechanics
- Phase structure for its own sake
What the Game Should Be
A creative prompt engine dressed in the Chef RPG world.
Cards (or something) don’t resolve outcomes — they spark imagination. A flip tells you what you encounter. The group decides what happens together. Players draw it, act it out, make it funny.
Characters are narrative lenses, not stat blocks. A Brewer notices things a Butcher doesn’t. That’s a storytelling permission, not a +2.
Structure exists to give the session shape and momentum, not to adjudicate success or failure.
What to Preserve
- ✅ The restaurant and cooking world — the Chef RPG theme is right
- ✅ Fantasy ingredient gathering in strange locations
- ✅ Cozy, funny tone — no death, comedic disasters only
- ✅ 45-60 minute sessions
- ✅ Group of 3+ as primary use case (solo as secondary bonus)
- ✅ Back-of-house class identities (Baker, Butcher, Barbaquere, Brewer)
- ✅ The idea of a job as a loose container for a session
What to Rebuild From Scratch
- ❌ Stats and point distribution systems
- ❌ Card battle mechanics (high vs low)
- ❌ Phase-based win/lose conditions
- ❌ Oracle resolution tables
- ❌ Nose / Hands / Voice stat framework
Starting Questions for Next Session
- What is the simplest possible structure that gives a session a beginning, middle, and end?
- What do the prompts generate — creatures? dishes? situations? all three?
- How do characters feel distinct without stats?
- What does “draw your own dish” or “build your own monster” look like as an actual mechanic?
- Is there any win/lose condition at all, or is the story itself the point?
- What does the physical experience at the table look like — cards, paper, drawing, acting?
Created end of Session 17 — March 1, 2026