When Bugs Become Features

Systemic vs. Scripted Design

Tim draws a clear distinction between systemic and scripted approaches. Systemic means handling behavior in code through flags and rules; scripted means attaching unique one-off scripts to individual pieces of content.

He illustrates this with quest items. The scripted approach: attach a "no drop" script to every quest item. The systemic approach: add a single "quest item" flag, then have the code check that flag everywhere it matters — dropping, selling, inventory weight, display. The systemic approach is superior because:

• New rules propagate automatically to all existing content
• Designers only need to check one box ("this is a quest item")
• Late design decisions don't require touching every item individually
• Fewer bugs from human error (forgetting to attach a script)

The Emergent Magic

The real payoff of systemic design: once you have many rules, they interact in unpredicted ways. This is where bugs become features.

Fallout: Reverse Pickpocketing

Fallout's stealing system reused the barter UI, which allowed transfers in both directions. Tim didn't anticipate (or didn't prioritize) that players would put items into NPC inventories rather than take them out.

QA discovered you could place lit dynamite or ticking grenades into NPC pockets via pickpocketing, then run away. QA infamously made a game of planting grenades on children in Shady Sands and scoring points based on how many other kids were nearby when they detonated.

This unplanned mechanic was so compelling that it became an official quest solution in Fallout 2 — you could plant explosives on a character's child, then use a dialogue option to send the kid running to their father.

Arcanum: World Map Drop-In

In Arcanum, players could click to exit the world map at any point during travel, which would generate the local sector and place them there. Players exploited this to enter areas they weren't supposed to access — most notably the city of Tula, which Tech-focused characters normally couldn't enter.

The technique: travel across the world map over the restricted area, drop out, and if you land outside the walls or on invalid terrain, just try again until you land inside. Players also used this to reach a mysterious walled-off area containing a chest with no intended entrance — a random encounter placed by one of the designers.

Neither the development team nor internal or external QA ever discovered this exploit. Tim learned about it years later from player reports.

The Outer Worlds: Combat Flag Reset

In The Outer Worlds, leaving a mapped instance cleared the combat flag on that map. Players discovered they could step outside and immediately back in to reset combat, allowing them to skip fights entirely.

Tim observed players doing this in the Edgewater power plant — ignoring all the automechanicals, and when chased to the exit, simply stepping out and back in to clear combat, then using the computer terminal (which requires no active combat).

Fun Over Balance

Tim acknowledges these are technically bugs. A strict balance pass would remove all of them. But he deliberately chooses fun over balance — these moments are cool precisely because players discovered them on their own.

He views games as toys rather than challenges, simulations, or story vehicles. Games can be all of those things, but fundamentally they're toys, and players should be free to play with them however they want.

Summary

Bugs become features when they are:

• Unplanned — emergent from systemic interactions, not designed
• Discoverable — players find them organically
• Fun — they enhance the experience rather than break it

Tim's blessing: if players find creative ways to exploit systemic interactions, let them. It's what makes games worth playing with.