Narrative, mastery, and character bleed in games, with Ricki Heicklen

Ricky and Patrick use Metagame, a small conference held the weekend before this October 16, 2025 episode, as a live laboratory for serious games: Ricky describes evolving simple, iterative game systems to teach quantitative trading concepts in her trading boot camps, while Patrick approaches the problem from a software-and-infrastructure angle. Both explain why a deliberately broad definition of “game” (any immersive experience where choices matter) allowed them to pull in radically different practices—board games, escape rooms, puzzle hunts, larps, tabletop RPGs, and indie videogames—so the event felt part hobbyist-convention and part professional conference.

Concrete sessions illustrated that breadth. One highlight was a Build-Your-Own-Escape-Room workshop that a dozen amateur designers used to assemble a playable escape room: the team built the set in under two hours on Saturday and ran eight playtest iterations Sunday, iterating away most puzzles across those tests. Ricky and Patrick emphasize the value of rapid prototyping and “pretend” props (e.g., a drawn lock and a pretend pinpad) to test mechanics before committing to expensive physical builds. Another high-engagement installation was a 25-foot crossword that cost roughly $15 to produce and became the most-used attraction—an object lesson that low-cost, highly-visible interactive elements can outperform more elaborate projects in raw engagement.

Patrick deep-dives into his own contribution: a CRPG-like roguelike he built in ~25 days (~300 hours). He leaned on LLMs to generate character sheets, dialog trees, and encounter text, and wrote a caching proxy to avoid repeated API latency/cost for frequent queries to popular NPCs or scripted prompts. That engineering approach let him iterate quickly on emergent narrative and mechanical systems, but it also created last-minute integration headaches: he enabled the “lose” condition shortly before release and later discovered the win path produced a 404 for early players, forcing log forensics to reconstruct winners. Patrick also describes design tradeoffs—long paragraphs of flavor text are great for immersion but many players skip them, so designers must make mechanical cues legible while preserving narrative reward for readers.

The conference’s overarching Mega Game divided attendees into purple and orange factions and treated the venue map as a board. Subgames reported back a binary outcome (which team won this territory) and organizers provided a deliberately simple API that could specify an intended advantage (no advantage, small, medium, large) translating roughly to a 50/50 up to an 80/20 skew. That constraint was chosen to prevent any single subgame’s scoring economy from overwhelming the meta-game. But playtesting problems still emerged: the organizers underestimated how fast expert solvers could clear puzzles (one team solved 17 Sudoku nodes almost immediately), while other mechanics—like a hidden team headquarters that required four distinct bag tokens to unlock—proved too opaque and led many attendees to miss collaborative opportunities. Logistics and coordination were recurring themes: managing subgame state, synchronizing badge/card upgrades, and placing events where foot traffic would create a crowd were as important to player experience as the core rules. Both hosts conclude that running a live, multi-subgame event is essentially running an iterative playtest of a social system: the default is to fail in subtle ways, but the data and attendee feedback yield practical fixes—simplify APIs between modules, reveal collaborative hooks earlier, and favor low-cost, high-visibility play elements for engagement.