Abstract
Problem: How do you create quests with multiple solutions, and what does that cost in development effort?
Approach: Tim Cain walks through a single Fallout quest — rescuing Tandi from the Raiders — and enumerates all seven known solutions, ordered by implementation complexity.
Findings: Three of the seven solutions emerged entirely from systemic gameplay (combat, stealth, lockpicking, explosives) with zero additional scripting. The remaining four required dialogue scripting, which revealed redundancy problems that directly inspired Arcanum's generated dialogue system.
Key insight: Systemic game design gives you multiple quest solutions for free; the easier you make the non-systemic ones to implement, the more your designers will create.
The Quest: Rescuing Tandi
The example comes from Tim's 2017 Reboot Conference talk. In Fallout, the player visits Shady Sands, meets Tandi, and later returns to find she's been kidnapped by Raiders. Her father Aradesh asks you to rescue her. The map is simple — one building, a couple of tents, some guards — but it plays very differently depending on your character's skills. Tim compares this to his early GURPS tabletop days, where a simple dungeon would play completely differently depending on who went through it.
The Seven Solutions
Solution 1: Kill Everyone
Walk in, kill all the Raiders, free Tandi. The straightforward brute-force approach. Requires no special implementation — hostile NPCs, combat system, done.
Solution 2: Stealth + Lockpick
Sneak around the back, quietly kill the two rear guards, enter through the back door, and pick the lock on Tandi's cell. Requires decent Sneak and Lockpick skills.
Solution 3: Stealth + Explosives
Same stealth approach to the back entrance, but instead of lockpicking, use Dynamite to blow the cell door open. The explosion makes noise, so timing matters — wait until patrolling Raiders have moved away from the building.
Solution 4: Intimidate Garl (Speech)
Enter dialogue with the Raider leader Garl. With at least 45 Speech skill, you can intimidate him into releasing Tandi.
Solution 5: Purchase Tandi
Also through dialogue with Garl — offer to buy Tandi's freedom. No Speech skill requirement, but you need enough money.
Solution 6: One-on-One Unarmed Combat
Challenge Garl to unarmed single combat. If you win, you take Tandi. No hard skill gate to initiate it, but you practically need high Unarmed skill, decent Strength, and enough hit points to survive — Garl hits hard.
Solution 7: Pretend to Be Garl's Father
The most complex and hidden solution, added by a scripter. Prerequisites: male character, Luck of at least 9, wearing leather armor or using a Stealth Boy. This lets you get past the guards. When you talk to Garl, there's a chance he thinks you're his dead father. Then with minimum Intelligence (around 6) and a Charisma/Speech check, you can convince him to release Tandi. Tim notes he'd now make this work for female characters too (posing as Garl's mother), since the dialogue system already supported gender-split dialogue. He wonders if anyone ever found this organically or only discovered it by digging through data files.
Systemic vs. Scripted
This is Tim's core analytical point. The seven solutions break cleanly into two categories:
Solutions 1–3 (systemic): Once you place the building, set guard factions, put Tandi in a locked room — these three solutions just work. No additional code, no scripting, no dialogue. The combat system, stealth system, lockpicking, and explosives handle everything. Tim considers this one of Fallout's genuine successes — three quest solutions emerging from base systems alone.
Solutions 4–7 (scripted): All four require dialogue trees and associated scripts. Whether it's speech checks, money transactions, unarmed combat challenges, or the elaborate father-disguise scenario — each needed custom writing and scripting.
The Path to Generated Dialogue
The scripted solutions revealed a pattern that bothered Tim. Across Fallout, the same dialogue subtrees kept recurring — asking for money, making threats, attempting persuasion, telling lies — but each scripter implemented them differently. The "ask for money" flow was never written the same way twice. Sometimes insufficient funds hid the option entirely; sometimes the NPC would reject you; sometimes you could offer and then admit you couldn't pay. This inconsistency annoyed Tim on two levels:
Localization waste: Near-identical strings had to be translated separately across every quest because they were never quite the same text.
Behavioral inconsistency: The same simple interaction (e.g., a bribe) worked differently throughout the game because each scripter had their own approach, making the game feel inconsistent.
This directly led Tim to create generated dialogue in Arcanum — a system that standardized these common interaction patterns, making them easier and more consistent for narrative designers to implement.
The Virtuous Cycle
Tim's closing principle: the easier you make things, the more your designers will do. More tools lead to more content. In Fallout, systemic design gave free quest solutions. In Arcanum, generated dialogue lowered the barrier for adding scripted solutions. Both approaches serve the same goal — making multiple quest solutions practical to ship, not just aspirational.