Fallout Director Explains “Spaghetti Code” Isn’t About Laziness, But Time Constraints: “This Isn’t Just Hypothetical”

Timothy Cain, one of the minds behind Fallout, wants to set the record straight about the infamous “spaghetti code” in video games. It’s not about a lack of skill or discipline; it’s simply that developers are often pressed for time.

Cain shares this insight in a recent YouTube video, using a real-world example to illustrate his point. “Imagine you’re developing a role-playing game,” he starts. “You have a mechanic called damage resistance (DR). It’s straightforward: if you have 10% DR and take a hit of 20 damage, you only suffer 18 damage.”

To implement this, the programmer—Cain himself—creates a function named ‘item armor get DR.’ This function checks the armor the player is wearing, retrieves the DR value, and returns it. “It’s clean, efficient code,” he notes. “But then, changes start rolling in.”

As the project evolves, the inventory UI designer raises concerns about discrepancies in the inventory display. “You realize the issue stems from additional values tied to status effects,” Cain explains. The designer, frustrated, insists that this wasn’t part of the original plan, leading to a cascade of adjustments.

“This is where the spaghetti code phenomenon begins,” Cain emphasizes. He stresses that games are not just products; they are a blend of art and engineering. While he appreciates that his RPGs are viewed as “flawed masterpieces” rather than just “buggy games,” he cautions developers that adding new features can often complicate existing systems.