Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Classic arcade games were not always executed from a finished master plan. Accounts of Hunchback, The Pit, Donkey Kong, Gauntlet and Triple Hunt show how playtesting, team decisions, technical limits and business pressures could reshape a game as it was made. These stories complicate the lone-genius version of arcade history without suggesting that every hit came from an accident.
How were classic arcade games actually made?
Often, through a mixture of an initial idea and decisions made along the way. A player might reveal that a game’s opening was confusing; a software bug could suggest a mechanic; a programmer or artist could expand what a designer had sketched; and the coin-operated business could influence how many people played at once.
That pattern emerges in accounts collected by Paul Drury and in museum histories, but the evidence is not all the same. A creator’s later recollection is valuable testimony, not a contemporaneous development log. A surviving drawing can show a proposed cabinet or screen, but cannot by itself establish why the team chose it. Keeping those distinctions in view makes the stories more useful than a simple tale of happy accidents.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallWhen a player exposed a confusing opening
Hunchback: simplifying the first minutes
In Paul Drury’s account, Hunchback creator Peter Robinson watched a player die quickly, misunderstand the controls and leave. The team responded by simplifying the opening and introducing hazards more gently. It is a small but revealing example of observation changing a finished experience: the issue was not simply whether a challenge was difficult, but whether a new player could understand how to begin.
#1 Best Overall
Drury’s feature reports this as a remembered story, not as a preserved play-test record. Even with that qualification, it captures a practical design loop: watch what someone does, notice where the game fails to communicate, and adjust the early experience.
When a bug or suggestion changed the game
The Pit: a trail that became a mechanic
According to the recollection reported by Drury, Andy Walker and Tony Gibson were working on a space game when a bug caused the ship’s trail to remain on screen until the ship doubled back over it. Rather than treating the behavior only as something to eliminate, they saw a possible game mechanic in it. The feature traces that idea toward The Pit, a game with a digging-and-pursuit feel often compared with Dig Dug.
The point is not that bugs automatically produce good games. The useful step was recognizing that an unintended behavior could create an interesting rule, then shaping it into something playable.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
Donkey Kong: the jump and the people behind it
Drury’s feature recounts an interview from a book in which Shigeru Miyamoto’s early concept is described as a gorilla and a sketch of one screen; the hero could not jump. The account credits programmer Hirohisa Komanomi’s team at contract developer Ikegami Tsushinki with arguing for a jump and designing additional screens.
This version of the story puts collaboration back into the frame. A famous game may be closely associated with a lead designer, while its mechanics and implementation also reflect suggestions and work from a development team. Because this account reaches readers through a reported book interview, it should not be mistaken for a complete record of every contribution or decision.
When business pressure became part of the design
Gauntlet: four players, one cabinet
The Strong’s history says Ed Logg began work on Dungeons in late 1983, inspired in part by his son’s interest in Dungeons & Dragons and by the Atari 800 game Dandy. The project became Gauntlet, whose four-player format also addressed a commercial question: how could an arcade earn more during the same playing time?
Rank #3
- Features contributions by: Python Anghelo, Larry Day, Damien McFerran, Tim Nicholls, and Dan Soulsby
As The Strong explains, Atari wanted greater revenue from the time people spent playing, while operators faced more difficult returns and customers resisted paying more than a quarter per game. Logg described the challenge as “how to get more money for the same amount of time.” The museum also says field testing helped address doubts about groups of strangers playing together. Multiplayer, then, was not only a creative feature; it had to work socially and commercially in an arcade.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →The cabinet was part of the experience
The Strong’s collection of Atari concept art includes more than 250 drawings acquired by the museum in 2012. Examples include Gran Trak 10, Touch Me, Red Baron and Gauntlet. The museum notes that cabinet shape, monitor tilt and player positioning were design decisions. For a four-player game, the physical arrangement helped determine whether people could gather around and play together.
A sketch is direct evidence of what someone drew, not conclusive proof of what was built or why. Read alongside creator accounts, however, design art helps show that the arcade machine surrounding a game was part of its design rather than disposable packaging.
When hardware shaped sound and ambition
Triple Hunt: tape, modes and limits
In an interview with the American Classic Arcade Museum, creator Owen Rubin says Triple Hunt began as a video version of Seeburg’s Shoot the Bear, then gained raccoons and a haunted-mansion mode. He explains that the game used tape for sampled sound because the hardware could not produce the sound he wanted. Swapping tapes to change modes was simpler than switching tracks electronically.
Rubin also recalls ideas for more complicated play and varied flight paths that were not implemented. His account shows how a game could grow in stages while practical limits determined which ambitions survived. He describes early development this way: “I hand-assembled the entire program–it was only 2K, but still took several months–including self-test and saving the code on punched paper tape.” That is Rubin’s recollection of his work on this game, not a measure of every arcade programmer’s process.
Free tools Windows power users keep installed
One-click scans. No signup required.
What these stories change about arcade history
- Iteration was part of the craft. The Hunchback story shows how a player’s behavior could lead to a gentler introduction.
- An accident still needed interpretation. In the reported The Pit account, the trail bug mattered because the developers recognized its potential.
- Credit can be more complicated than a famous name. The Donkey Kong account highlights a contract team’s input alongside Miyamoto’s concept.
- Design answered constraints as well as ideas. Gauntlet responded to coin-op economics and social play, while Triple Hunt reflects limits in sound and mode switching.
These are examples, not proof that all games from the period were improvised. Their value is in making the production process visible: decisions came from people working together, responding to machines, players and practical demands.
Best Value
- Page Count: 272 pages
- Binding: Softcover
- Images: 408 illustrations
- Release Date: October 10, 2019
- Dimensions: 23.0 x 17.0 cm
How to read creator memories and surviving artifacts
Oral histories preserve details that finished games and cabinets cannot: what a creator remembers trying, rejecting or changing. But memories are recollections, often recorded years later. Artifacts such as concept drawings preserve a different kind of evidence: a design proposal in visual form. Neither automatically supplies the whole story.
The Smithsonian National Museum of American History lists a Video Game Pioneers Oral History Collection with born-digital interviews and transcripts from people involved in early game development. Its collection description establishes that the archive exists; it does not, on its own, substantiate any particular anecdote above. Using these forms of evidence carefully helps resist nostalgia’s tendency to make a complicated process look inevitable.
For readers interested in creator accounts across coin-op games, Creative Bloq reported in 2026 that Bitmap Books’ The Arcade 1971–1999: The Stories Behind Classic Coin-Ops, Told by Their Creators is 408 pages, covers 120 games and includes more than 90 programmers, designers, artists and musicians. Those figures describe the book, not the arcade industry as a whole.
Quick Recap
Sources and further reading
- Creative Bloq’s feature on the stories behind retro gaming’s golden age
- The Strong: “Gauntlet by Design: Creating the Four-Player-at-Once Arcade Game Experience”
- American Classic Arcade Museum interview with Owen Rubin about Triple Hunt
- The Strong: Atari concept-art collection
- Smithsonian National Museum of American History: Video Game Pioneers Oral History Collection
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
