pplpod

Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode!

In 2000, a video game with a rumored $30 million budget, helmed by the co-creator of Wolfenstein 3D, Doom, and Quake, sold barely 40,000 copies in its first months. This episode traces the complete history of Daikatana, from John Romero's departure to found Ion Storm with a $13 million advance from Eidos Interactive, through the 400-page design document spanning four time periods, the fatal mid-development engine switch after a 1997 trade show, and the sidekick AI that kept walking into lava.

We examine the collapse of Ion Storm's Dallas studio culture, the infamous 1997 print ad that promised the director would dominate the player, the 12-frames-per-second 1999 demo, and the brutal May 2000 reviews that compared the game unfavorably to Half-Life. Then the story pivots to the surprisingly well-received Game Boy Color version that never launched in North America, and the decade-long fan effort that produced the unofficial 1.3 patch, which Romero himself publicly endorsed.

• How total creative freedom and a blank check produced dozens of weapons per episode and feature creep baked in from day one
• Why switching to an unfinished engine forced the team to throw out or rework nearly everything they had built
• The sunk cost fallacy behind keeping sidekicks Mikiko and Superfly even as their deaths triggered automatic level failures
• Over 50 staff departures, a public resignation of nine core members, and only two people remaining for the full project
• What modders like Frank Sapone fixed, from sidekick AI and load times to modern OS support, and what that says about digital conservation

Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode!

When Hello Games founder Sean Murray released his sci-fi universe in August 2016, his reward was bomb threats, death threats, and phone calls with Scotland Yard. This episode traces how a team that started with four people and grew to about a dozen, inspired by the vibrant cover art of 1970s and 1980s science fiction paperbacks, built a deterministic procedural generation engine capable of 18 quintillion planets, landed center stage at Sony's E3 presentation, and then collapsed under the weight of hype the studio could not control.

We unpack the launch-day numbers, the live stream that exposed the missing multiplayer, the procedural oatmeal critique, and Murray's controversial decision to go completely silent. Then we follow the decade of free updates, starting with the Foundation update in November 2016, that turned the industry's cautionary tale into one of the most celebrated comebacks in media history and forced digital storefronts like Steam to ban misleading pre-rendered marketing materials.

• Why the team rewrote their engine from a 32-bit to a 64-bit seed after online skeptics questioned the 4.3 billion planet claim
• The trademark dispute with Sky Group and a Dutch patent claim over a plant-based super formula that consumed the small studio's time
• How Hello Games planned for 10,000 concurrent players and got hit with over 500,000, melting their servers
• Journalist Geoff Keighley's private warning that expectations were out of control and his suggestion of an early access release
• Base building, freighters, full multiplayer, VR, mechs, settlements, sandworms, and fishing: the updates that rebuilt trust over ten years

Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode!

The savior of the video game industry was a slow, finicky plastic robot. This episode gives R.O.B., the Robotic Operating Buddy, a proper biography, starting with the North American video game crash of 1983, when shovelware from companies outside the industry drove revenues down nearly 97 percent and made the words video game toxic to toy retailers. It explains how Nintendo's computer-with-keyboard pitch failed at the 1985 Consumer Electronics Show and why a Gunpei Yokoi photosensing robot became the Trojan horse for the Nintendo Entertainment System.

It covers the gray VCR-style redesign of the console, the 1985 Manhattan test market where R.O.B. was bundled into the Deluxe Set, the optical technology that only works with CRT televisions, and his six commands executed at the speed of grass growing. The episode walks through the Rube Goldberg setup of Gyromite, with spinning tops, a floor motor and a tray pressing a second controller's A button, and Stack-Up, and why kids simply reached over and pressed the button themselves. It ends with a 1986 survey showing the robot was the top reason kids wanted the NES, his quiet retirement after Super Mario Bros., and his second act in Mario Kart DS, Super Smash Bros., amiibo figures and the 2026 Super Mario Galaxy movie.

• Why retailers in 1984 treated video game consoles as a dead fad
• How industrial disguise separated the NES from the word Atari
• Why R.O.B.'s eyes cannot read a modern LCD or OLED screen
• How Gyromite required a robot to press a button a human could reach
• How a failed peripheral became a Smash Bros. fighter and a movie character

Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode!

The father of home video games was not a garage hacker in 1970s California. He was Ralph Baer, a Jewish teenager who fled Nazi Germany in 1938, worked in a New York factory for $12 a week, and taught himself electronics through a correspondence course he spotted at a bus stop. This episode follows his path through Army military intelligence in London, an 18-ton collection of foreign weaponry he donated to museums, a 1949 degree in television engineering, and early jobs designing surgical devices and power-line signaling equipment.

It explains how that background let him see a passive CRT television as something whose synchronization pulses could be hijacked locally, why his 1951 pitch for a game module was rejected, and how in 1966 at defense contractor Sanders Associates he secured $2,500 and two engineers to build the Brown Box. The episode covers the patent office demonstration that stopped work for a ping pong game, the 1972 Magnavox Odyssey, the rivalry with Nolan Bushnell and Atari, the pioneer patent that Magnavox used to sue across the industry, the invention of Simon in 1978 with Howard Morrison, the failed follow-up Maniac, his more than 150 patents, and the workshop now preserved at the Smithsonian.

• How surviving an authoritarian regime built a tolerance for rewiring rigid systems
• Why a Cold War defense contractor was the perfect place to invent a toy
• How fake wood veneer disguised military-grade electronics as living-room furniture
• Why Baer's fight with Atari was about historical erasure as much as royalties
• What Simon and Maniac reveal about cognitive load and feedback loops

Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode!

The man who built the modern video game industry almost never picked up a controller. This episode profiles Hiroshi Yamauchi, Nintendo's third president, from a Kyoto childhood marked by his father's abandonment and wartime factory work, to taking over the family hanafuda card company at 21 on the condition that he be the only family member employed there, firing a cousin and then the striking veterans who protested his youth.

It follows the Disney licensing deal that sold 600,000 packs of cards in a year, the failed ventures into instant rice, taxis and hotels that pushed Nintendo toward bankruptcy, the discovery of Gunpei Yokoi playing with a mechanical claw that became the Ultra Hand, and the pivot to electronics through the Magnavox Odyssey, competing R&D departments, Donkey Kong, Game & Watch and the Famicom. The episode covers the third-party quality controls that answered the 1983 crash, the cartridge decision on the N64, the Virtual Boy failure, his estrangement from his father and later grief, his love of Go, the $75 million he put up to keep the Seattle Mariners in Seattle without ever attending a game, and his choice of Satoru Iwata over his own son as successor.

• How childhood abandonment shaped an executive's need for absolute control
• Why the Disney card deal bypassed the gambling stigma and dominated the Japanese market
• How pitting R&D1, R&D2 and R&D3 against each other fueled innovation
• Why limiting publishers to three titles a year restored consumer trust after 1983
• What the Mariners purchase and the Iwata succession reveal about his philosophy

Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode!

Fortnite began as a 2011 internal game jam idea at Epic Games after Gears of War 3, then limped through six years of development, an engine swap from Unreal Engine 3 to 4, an art-style overhaul and executive shakeups after Tencent bought a large stake. This episode follows the troubled cooperative zombie game Save the World to its July 2017 early-access launch, and the two-month pivot that followed when PUBG popularized battle royale and Epic realized its building system could support the format.

It covers the free-to-play September 2017 launch, 10 million players in two weeks and 125 million by June 2018, the Ninja and Drake stream that broke Twitch records, emotes on football fields, the $30 million 2019 World Cup, and the anxieties of parents and schools as the game became a third space for teenagers. The episode then turns to V-Bucks and the Battle Pass, Epic's August 2020 trap that got the game removed from Apple and Google's app stores, the antitrust lawsuits and their outcomes, the 2023 and 2026 V-Bucks price hikes, and the transformation into a platform through Unreal Editor for Fortnite, LEGO Fortnite, Rocket Racing, Fortnite Festival and Fortnite Ballistic.

• Why changing engines mid-development is like swapping a house's foundation
• How accessibility and building mechanics let Fortnite eclipse the game that invented its genre
• What the third space concept explains about fear of missing out among teenagers
• How the in-app steering ruling and the Google jury verdict changed mobile economics
• Why Epic is building racing, rhythm and tactical games inside one application

Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode!

A medieval executioner with two broken arms bites off the limbs of the condemned; a farmer accidentally plants his bed in a field. Nobody scripted these moments. They emerged from Dwarf Fortress, the simulation Tarn Adams and his brother Zach have built for over two decades. This episode follows Tarn from a BASIC game called Dragslay and self-taught C in high school, through the abandoned 3D project Slaves to Armok, to the 2006 decision to turn down a $50,000 postdoc stipend at Texas A&M and live on $15,000 in savings to finish a text-based dwarf simulator.

It explores the mathematics behind procedurally generated worlds, Zach's ancient-history background driving centuries of simulated lore, ASCII graphics where a green G is a goblin, PayPal donations that brought in $300 in five months, the $300,000 licensing deal Tarn refused, and the obsessive systems underneath: rain shadows, tracked anatomy, fluid pressure and dwarf psychology. The episode closes with the 2019 family health crisis, the partnership with Kitfox Games, the December 2022 Steam release with pixel art that hit a two-month sales target in under 24 hours, over $7.2 million in a single month, one million copies by 2025, and Tarn's plan to keep developing for another 20 years.

• How midpoint displacement turns a straight line into a mountain range
• Why the game's motto is losing is fun and there is no way to win
• How a stabbing is calculated through velocity, material density and organ layers
• Why Tarn's isolation from publishers and focus groups was the secret ingredient
• Whether adding graphics and a price tag counted as selling out

Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode!

What dollar amount makes a creator want to walk away from his own creation? For Markus Persson, known as Notch, it was $2.5 billion. This episode follows Minecraft from Persson's after-hours prototypes while working at King, the isometric base-building experiment RubyDung that he almost abandoned for looking too blocky, and the moment Infiniminer convinced him uniform cubes were a technical shortcut rather than a flaw.

It covers the May 2009 forum upload of Cave Game, the community-driven alpha and beta era, creepers that forced players to build shelters, redstone circuits that made the game capable of logic gates and in-game computers, C418's ambient music, procedural generation and the floating-point breakdown known as the Far Lands. The episode then turns to Persson stepping down as lead developer after the 1.0 release, the 2014 EULA fight with pay-to-win server owners, the burnout post that led to Microsoft's acquisition, 400 million copies sold, the Uncensored Library built by Reporters Without Borders, and Persson's brief 2025 flirtation with a spiritual successor that he dropped to avoid a sad nostalgia dump.

• Why blocky graphics made hitboxes, building and memory storage far simpler for a solo developer
• How redstone turned a sandbox into a Turing-complete logic toy
• What happens to terrain generation 12 million blocks from the starting point
• How a user agreement dispute over server monetization fractured the community
• How a Minecraft server became a sanctuary for censored journalism

Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode!

Robert Kurvitz failed as a musician, published a novel that sold around a thousand copies, and spent three years in alcoholism and depression. Then he turned that experience into Disco Elysium, a 2019 role-playing game that has sold over five million copies. This episode traces the Estonian creator's path from a rock band and a world-building idea sparked while listening to trance music, through years of tabletop sessions with friends including painter Alexander Rostov, to the 2013 novel Sacred and Terrible Air and the collapse that followed.

It then covers how Kaur Kender pushed him toward video games, the founding of ZA/UM in a squatted Tallinn art gallery, and how personal trauma became mechanics: 24 internal skills that argue with the player, the thought cabinet, and failure as a narrative feature. The episode looks at the game's literary and political influences, its Game Awards sweep and Final Cut expansion, and then the ousting of the creators in late 2021, the competing narratives of a fraudulent buyout versus a toxic workplace, the lawsuits, the canceled sequel, the underperforming 2026 release Zero Parades for Dead Skies, and the four splinter studios now chasing the original's spirit.

• How a failed novel and a recovery friendship led to a video game pitch
• Why the Hobocop thought is a perfect example of the thought cabinet mechanic
• The Zola, Strugatsky and historical materialism influences behind Revachol
• The one-pound sketches, the 4.8 million euro sale and the studio's counterclaims
• What Red Info, Longdue, Dark Math Games and Summer Eternal each took from the original team

Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode!

In May 1997 Garry Kasparov paced and sweated on a global stage after a chess computer made a move so strange he assumed it saw something beyond human comprehension. It was a bug. This episode treats IBM's Deep Blue as a biographical subject, from a Carnegie Mellon doctoral project called ChipTest in 1985, through Deep Thought's 1989 defeat by Kasparov, to IBM's mandate to build a machine that could beat the reigning world champion.

The episode explains how Deep Blue worked as an expert system: an evaluation function split into 8,000 parts tuned with grandmasters like Joel Benjamin, an opening library of over 4,000 positions, a database of 700,000 games, and 480 custom VLSI chess chips that let it evaluate 200 million positions per second. It covers Kasparov's 1996 comeback through closed positions, the 1997 rematch, the game one random move that came from a failsafe in an endless counting loop, the cheating accusations, IBM's refusal of a rematch, the dismantling of the machine, and why later systems like AlphaZero made Deep Blue's architecture a dead end.

• Why early chess computers struggled with closed positions and human long-term strategy
• How human chess knowledge was translated into decimal scores the machine could tally
• What hardwiring chess logic into silicon did for search depth and ELO strength
• How a software glitch became accidental psychological warfare
• Why Kasparov later compared Deep Blue to an alarm clock, and where its racks sit today