Session 16: Core Mechanics Redesign - Oracle Card System
Focus: Addressed dice/prompt friction through complete architectural redesign
Key Decision: Cards-Only Oracle System
Problem Identified: Playtesting revealed friction between prompt difficulty (easy/difficult) and d20 rolls. When a prompt says “easy” but you roll a 3, it breaks narrative immersion. Cards should “do the talking.”
Solution: Unified single-deck oracle system
- One standard deck per session - serves dual purpose throughout
- Remaining cards after exploration setup become oracle deck for all resolution
- Red/Black polarity - Red = proceeds as intended, Black = complication/scene interrupt (inspired by Mythic GME)
- Rank (A-K) determines magnitude/intensity of outcome
- Narrative-driven - player creates story tied to card results
Locked-In Architectural Changes
UNLOCKING (no longer relevant):
- ❌ Dice + cards mechanic
- ❌ Grid-based exploration (5x3, 5x4, 5x5 card layouts)
- ❌ Three exploration stats (Foraging, Combat, Social with +2 bonuses)
- ❌ d20 + stat bonus resolution system
- ❌ Typed ingredients (Protein/Vegetable/Fruit/Spice categories)
- ❌ Mechanical cooking phase with quality tiers and d20 rolls
- ❌ Equipment Die progression (d4→d12)
LOCKING IN (new foundation):
Core Mechanic
- Single-deck oracle system - one standard deck per session, unified for exploration + resolution
- Card-only resolution - no dice ever
- Red/Black + Rank determines outcomes (simple, narrative-focused)
- Character-driven adventure - exploration/gathering/cooking are narrative beats, not separate mechanical systems
Exploration Redesign
- Job-based scaling (not character-based stat scaling)
- 1★ job = 1-2 exploration opportunities
- 5★ job = 4-5 exploration opportunities
- Multiple exploration scenes per session (not one big grid)
- Oracle table lookups for what’s available at each location
- High-beats-low card play during exploration (simple Colostle-style mechanic)
- Simple inventory - generic “ingredients” (no typing/categories)
- Distance/resource system TBD - how each exploration opportunity “costs” cards/draws
Cooking Redesign
- High-beats-low card battles (inspired by Colostle combat)
- Job specifies dish count (3 dishes for typical job, scales by tier)
- Hand of ingredient cards drawn from exploration
- Must have minimum ingredient count to attempt cooking (no ingredients = auto-fail)
- Win majority of dish battles = job succeeds
- Narrative-driven - players describe what’s happening while playing cards
- Character abilities - now cooking-focused only (Pastry Chef pastry bonuses, Butcher protein bonuses, etc.)
Character System Implications
- Six roles still exist - Chef (required) + 5 specialists
- Abilities now cooking-focused (not exploration stat-based)
- No more exploration stat system - exploration uses oracle deck, not character bonuses
- TBD: How specialist cooking bonuses work in new system
What This Fixes
✅ Prompt/outcome alignment - card result is the truth, no friction ✅ Card economy - single deck sustainable throughout session ✅ Simplicity - one mechanic (card comparison) across all resolution ✅ Narrative focus - story-driven with cards supporting narrative, not replacing it ✅ Beginner-friendly - fast, easy to teach, high-school compatible ✅ Character-driven - characters matter in cooking/narrative, not abstract stat rolls
What Needs Work
Pending design decisions:
- Distance/resource system for exploration (how turns/draws are limited)
- Specific oracle table structures for exploration
- How job tier scales exploration opportunities (1★ = 1-2, 2★ = 2-3, etc.)
- Character specialist cooking bonuses (exact mechanics)
- Review/Service phase (with new card-based system)
- Progression phase (restaurant upgrades, equipment progression)
Previously abandoned work:
- Cooking Card Tables (52 dishes) - now obsolete with new mechanic
- Character stat system - replaced by job-based exploration scaling
- Dice mechanics documentation - no longer needed
Next Session
Priority 1: Exploration Redesign
- Define distance/resource system
- Create oracle tables for exploration
- Playtest simplified exploration to validate card economy
Priority 2: Cooking Specifics
- Define specialist cooking bonuses
- Create dish count scaling by job tier
- Design Review phase for new system
Session ended with solid architectural foundation. Major rebuild required, but solves core design problem.