Narrative Systems Architecture
A Baldur's Gate 2-style living convention world where the entire game is side quests.
You're a volunteer errand-runner—a gopher—navigating a crowded, living convention floor modeled as a top-down retro pixel RPG. You signed up for the free staff badge for exactly one reason: to get into a tiny reunion panel celebrating Blip, a minor alien mechanic from a cancelled cult sci-fi show. You are one stamp away from getting into the room. You are always one stamp away, because every single step toward that panel decomposes into favors, lost badges, and room-block crises for the weird, wonderful, exhausted people of the convention floor.
Target Engine
Godot Engine
Top-down retro pixel art CRPG in the spirit of Baldur's Gate 2
World Architecture
Living Con Floor
Dynamic schedules, attendee flows, panel halls, and parking lot van
Methodology
Rapid Web Harness
Interactive slices to gut-check base mechanics before engine commit
Win/Loss System
Fail-Forward
Complication ripples & Goodwill progression with zero game overs
The Sideways Progress Paradox
Traditional RPGs treat side quests as distractions from the "real" story. In One More Thing, the main quest sits frozen at 99% all weekend. But progress is visceral and cumulative: a network of people who owe you favors, an inventory van filling with weird artifacts, and a quietly accumulating Goodwill meter that turns out to be the only thing that actually unlocks the ending.
Heart Underneath the Comedy
The convention app needles the hero with ridiculous bureaucratic ceremony ("Quest Log Updated: Deliver iced decaf latte"), but every character is an authentic costume and the tired human inside it. The Dark Lord has stage fright and needs throat lozenges; Greg the keykeeper keeps losing vital keys; Wayne the raccoon insists he only trades.
One More Thing key title art and retro convention visual aesthetic.
Turn Budgeting & Pacing
Pacing without clocks: 4 discrete beats per phase across three days.
Most narrative games struggle with timer anxiety. If a quest is on a real-time countdown, players rush dialogue; if there is no pressure, choice loses all friction. One More Thing resolves this with a Phase Economy.
Each day follows a 7-phase convention rhythm: Arrival → Morning Rush → Midday Crush → Afternoon Events → Dinner Lull → Night Events → Wind-Down. Each phase contains a strict budget of 4 beats. A standard call costs 2 beats, a quick call costs 1, an encounter chain scene costs 1, and a trip to your van costs 1.
Meaningful Scarcity
You cannot do everything on the board. Choosing which attendee to help, which call to ignore, and when to take a pit stop forces real prioritization.
Organic Pressure
Hunger, Bathroom, and Social Battery tick up each beat. Maxed needs create roll distraction (−3 to checks), naturally nudging you back to your van without punishment.
The Van Home Base
Your parked van is your sanctuary: swap your 5-item pocket loadout, recharge devices, patch your costume, and watch the cargo space visibly fill with weird trophies.
Strategic Trade-Offs: The Forks in the Road
De-risking game systems: Why rapid web slices precede the Godot build.
Designing an expansive top-down RPG requires disciplined validation. Heavy game engines and pixel art pipelines carry high overhead; changing a core rule after drawing dozens of sprite sheets and tilemaps is excruciating. By building lightweight, self-contained web harnesses first, we gut-check the mechanics, story beats, and win/fail loops in days.
Engine Commit Before Loop Validation
The Instinct: Jump immediately into Godot to build pathfinding, tilemaps, and character controllers before the social systems and narrative beats are proven.
Why It Fails: Mechanics debt is vastly more expensive to refactor inside a game engine. Prototyping the state machines and dialogue trees in a browser harness exposes pacing flaws immediately.
Binary Pass/Fail Skill Checks
The Premise: Standard tabletop checks where rolling under a difficulty number halts quest progress or forces save-scumming.
Why It Failed: Hitting dead-ends in a comedy game ruins the momentum. If a player fails to fix a prop sword, the story shouldn't stop—it should create an escalating mess.
Rapid Web Harnesses for Base Mechanics & Fail-Forward Complications
Every single check in the game fails forward. A missed roll or botched timing check leaves a mark (a witness, a spill, a debt, an escaped mascot) that immediately generates a follow-up encounter with a different verb and a different quest-giver. By testing this entire win/fail state tree in the browser harness, we prove the comedy and pacing work before executing the full top-down pixel experience in Godot.
Technical & Design Architecture
Four foundational systems powering the living prototype.
The Goodwill Economy & Favor Ledger
Rather than tracking standard XP or gold, the game tracks social capital across two ledgers: a persistent Goodwill Meter and a dynamic People Page tracking who owes who. When you help Greg find his lanyard, Greg is recorded as owing you a favor. In later encounters, having someone in your debt lights up exclusive dialogue paths and bypasses checks entirely.
Earned by helping attendees; silently unlocks the Sunday ending gate
Named relationships that unlock story bypasses and trades
Gopher-in-Training #0047 who trades shiny scrap for critical parts
Hybrid Resolution Engine (Thresholds, d20 & Live Action)
Encounter choices are resolved through a tiered probability framework. Crucial story beats use Deterministic Thresholds (Charm 5, Fandom Knowledge 4) so players are never blocked by bad dice luck on the moments that matter. Minor actions use transparent d20 rolls (Easy 10 / Standard 12 / Hard 15). Saturday introduces Live Action Timing Checks (foam sword parries, tipping crystals, claw machine drops) for tactile physical gameplay.
The Anti-Repetition Complication Rules
To prevent quest bloat from spiraling into frustration, the complication system is governed by strict mathematical laws: (1) Verb Mutation: If you failed a fetch quest, the follow-up cannot be a fetch—it must be an apology, a repair, or an impromptu stage performance. (2) Capped Depth: Maximum of 2 active complications simultaneously; no third-generation cascading debts. (3) Self-Resolving Legends: If an ignored complication ripens, it converts into a funny convention myth that grants partial Goodwill.
The Living Convention World (Top-Down Godot Architecture)
Modeled after classic top-down CRPGs like Baldur's Gate 2, the game's setting is a dense, living convention center rather than static menus. The world encompasses two interconnected layers: the indoor facility (Main Lobby, Fantasy Hall, Sci-Fi Deck, Artist Alley, Dealer's Room, and Panel Room 4 at the farthest wing) and the outdoor perimeter (Food Truck plaza, dumpster hideaways, and the remote parking lot where the hero's van is parked). In the target Godot build, attendees, exhibitors, and cosplayers navigate these zones dynamically according to the convention schedule. The interactive floor plan serves as our spatial wireframe and zone spec for the upcoming retro pixel art tilesets.
Mechanics & Story Harness
Gut-Checking the Base Systems in the Browser
Before committing to sprite animation and Godot scene trees, this browser-based vertical slice is used to gut-check base mechanics: testing d20 math, validating the Goodwill favor economy, tuning the 4-beat phase pacing, and outlining Friday & Saturday story beats.
Narrative Payoff & Design Philosophy
The Sunday Climax & The True Ending Gate
How the 99% main quest loop actually resolves. Because this payoff is the emotional and comedic core of the narrative, the full third-act story resolution is sealed behind the spoiler disclosure below for players experiencing the vertical slice first.
Major Spoilers Ahead
Reveal Sunday Climax & Final Quest Resolution
Click to Reveal ↓
On Sunday afternoon, the hero’s Goodwill finally hits the threshold. The door person, who has watched you run coffee, untangle registration lines, and rescue cosplayers all weekend, stamps your badge. You walk into Panel Room 4.
The twist: the panel is cancelled. The Blip performer has completely lost their voice from three days of autographs. The single event you chased all weekend doesn't happen.
In the chaotic hallway aftermath, their airport shuttle falls through. Because you have a van with jumper cables and empty seats, you offer them a ride. On the quiet drive down the highway, the performer turns to you, asks about your weekend, and shares the private, unvarnished behind-the-scenes stories of the show. The panel that never happened happens one-on-one.
The convention app flashes: "Main Quest updated: COMPLETE — see new Main Quest."
Why Game Mechanics Belong in a Systems Design Portfolio
Designing game mechanics is the purest form of user experience design. There are no corporate mandates or compulsory workflows forcing someone to play; the interaction must be intrinsically legible, rewarding, and emotionally coherent. The discipline of managing discrete turn budgets, preventing dead-end state trees, and translating complex rules into effortless interface feedback is the exact same discipline required to architect mission-critical enterprise systems.