Obsolete Game Design Wisdom: How Devs Thought Up Concepts in the 80s/90s¶
A collection of design heuristics, rules-of-thumb, and assumed knowledge from the 8/16-bit and MS-DOS era. Most of this knowledge died out as teams grew, storage got cheap, and design became its own discipline. It's preserved here not for nostalgia, but because constraint-driven thinking is a genuinely different — and often faster — way to generate game concepts.
Start From the Verb, Not the World
Experiment 1 The benchmark the simplest
Design by Subtraction, Not Addition
The Arcade Economics Rule - Design for the Quarter
Enemies as Palette, Not Characters
The Kishotenketsu Boss Structure
Procedural Generation as a Space-Saving Trick
The Manual Did Design Work the Game Couldnt
High Score Tables as the Entire Metagame
Genre as Constraint Satisfaction
The Can I Explain It on the Cabinet Art Test
Playtesting Was Just Playing It Yourself A Lot
The Meta-Lesson¶
Almost none of this was written down as "game design theory" at the time — it was tribal knowledge, passed through cracked-open ROMs, magazine postmortems, and trial and error. The unifying thread across all of it:
Constraints aren't the enemy of creativity — they're a forcing function for it. When you can't add more, you're forced to find out what's actually fun about what you already have.
That's arguably the most transferable piece of "obsolete" wisdom here: even with unlimited storage and teams today, deliberately imposing artificial constraints early (one mechanic, one screen, one week) is often the fastest way to find out if a concept has a real core.