Abstract
Problem: How did the Fallout team replace GURPS — a deeply integrated character system — with the SPECIAL system just four to five months before the game shipped?
Approach: Tim Cain recounts the two key factors: modular engine architecture that isolated game mechanics into swappable library calls, and Chris Taylor's pre-existing homebrew RPG system that was ready to adapt.
Findings: The replacement took roughly two weeks. Modular programming meant combat and skill checks were abstracted behind library calls, making the swap surgical. Chris Taylor's system (attributes + unified traits + skills) solved several design problems GURPS had introduced, and the team iterated quickly with contributions from Brian Fargo (perks) and Jason Swinn (the "SPECIAL" acronym).
Key insight: Modular architecture isn't just good engineering — it's insurance. The ability to swap an entire character system in two weeks saved Fallout from a licensing crisis.
Background: Tim Cain's GURPS History
Tim Cain had been playing GURPS since graduate school — four years before he joined Interplay. He was a passionate evangelist for the system, introducing it to colleagues and running campaigns across multiple settings: GURPS Fantasy, GURPS Space, GURPS Time Travel, and a memorable "GURPS Everything" campaign where players could use any sourcebook they wanted. He even ran "GURPS Nothing" — stripped down to only the most basic skills and attributes.
His enthusiasm led him to build tools for the system. He created a GURPS Star System Generator for GURPS Space that let users click through generated galactic sectors and explore planets. He also built a GURPS Character Editor — and this is where the seeds of SPECIAL were planted. The editor was completely modular: skills, advantages, disadvantages, and even attributes were defined in editable text modules that could be swapped depending on the campaign. This modular thinking would prove critical.
The Engine Was Already Modular
When Fallout was built, Tim carried over his modular instincts. GURPS was integrated into the game not as a monolithic system but as isolated library calls. When the combat system needed to resolve a hit chance, it would call into a GURPS module: "How far away are they? What weapon? What skills and attributes?" But that logic was tucked behind an interface.
When the order came to replace GURPS, Tim spent two days auditing the codebase. He found that most of the system was already cleanly isolated. A few things weren't quite modular enough, and he cleaned those up — though he suspects he didn't catch everything.
Chris Taylor's System
Chris Taylor, Fallout's lead designer, had been developing homebrew RPG systems on his own. When Tim told him they might need to replace GURPS, Chris asked for two days and came back with a complete proposal.
The system had three pillars:
Attributes: S.P.E.C.I.A. (Originally)
The original attributes were Strength, Perception, Endurance, Charisma, Intelligence, and Agility — everything except Luck. The acronym at this stage was "ASLIPS" or similar, based on the first letters.
Traits: A Clever Merger
Chris combined GURPS advantages and disadvantages into a single concept: traits. This solved a persistent problem from their GURPS campaigns. In tabletop play, GMs constantly had to police disadvantage combinations — you couldn't take Colorblindness if you were already Blind, certain combinations were mutually exclusive, and tracking these exclusions was painful.
With unified traits, the problem vanished. Players simply chose zero, one, or two traits and moved on.
Skills
The skill list was a clean selection that mapped well to the existing library call structure. Redirecting the code from GURPS skill modules to the new system's skill module was straightforward.
Tim's Contribution: Luck
Tim insisted on adding Luck as a seventh attribute. He had fond memories of buying "Ridiculous Luck" and "Phenomenal Luck" in GURPS Supers campaigns. Luck became the "L" that completed the attribute set.
Brian Fargo's Contribution: Perks
When the system was presented up the chain, Brian Fargo had one piece of feedback: leveling up shouldn't just mean buying skills. He wanted players to gain something more exciting.
Chris Taylor responded with perks — ability-like bonuses earned every three levels. Since there were no disadvantages to balance against (traits had absorbed that role), perk design could be more generous and creative. Chris designed perk trees, and Brian loved them.
Jason Swinn's Contribution: The Name
After the team presentation, programmer Jason Swinn approached Tim with an observation. The attribute initials could be rearranged from the awkward working acronym into a real word: SPECIAL.
Tim hesitated — "special" had some negative connotations, he thought. But by the next day, he was convinced. The old acronym was out. SPECIAL was in.
Lessons
Tim identifies two takeaways:
- Chris Taylor did the heavy lifting — designing a complete, functional RPG system in days, drawing on years of homebrew experience.
- Modular programming saved the day — the architecture that isolated game mechanics behind library calls made a system-level swap possible in two weeks rather than two months.
References
- Tim Cain. YouTube video. https://www.youtube.com/watch?v=kgPwfHXiBjw