game analysis

Stuart Ashen presents a talk at the 2017 Norwich Gaming Festival on Hareraiser, a notoriously bad video game tied to the Masquerade treasure hunt. He explores why it may be the worst game ever made.

Morphcat Games explains how they fit Micro Mages, a full-featured NES game, into 40 kilobytes. It covers compression of sprites and level layouts and other space-saving tricks.

Michael Steil's 33c3 talk explains essentially everything about the Game Boy: CPU, video hardware, peripherals, and the tricks used by games and demos. It revives the era of counting clock cycles around hardware limits.

Jonathan Blow speaks at UC Berkeley's CSUA about how to program independent games. He argues for keeping code simple, avoiding unnecessary work, and shipping.

Jonathan Blow's first talk on designing a new programming language for games, which became Jai. He explains the problems with C++ and why Go, Rust and D do not fit game development.

Jonathan Blow's CreativeMornings talk arguing that business models shape game design, drawing an analogy between 1970s TV and HBO and between free-to-play and premium games. He calls for games that inspire awe rather than chase constraints.

Jonathan Blow's 2010 Rice University talk argues that game designers refine their techniques in ways that can manipulate players, as with A/B-tested social games. He discusses the ethical responsibility of designers and what games can offer beyond addiction.

A 2017 GDC postmortem in which Sid Meier and Bruce Shelley tell how Civilization came together from board game design and sim game experience. They cover its development history and design decisions, including fairness and luck.

Eric Chahi's GDC 2011 postmortem of Another World (Out of This World), describing how he built the game. He shows his polygon art approach, rotoscoping and animation tools.

Jake Birkett of Grey Alien Games explains at GDC 2016 how an indie developer survived eleven years without a hit by building a long tail of games and redefining success.

Bob Nystrom, author of Game Programming Patterns, gives a Roguelike Celebration 2018 talk questioning whether entity component systems are the only way to structure a game. He walks through alternative architectures drawn from roguelike development.

At GDC 2019, Bennett Foddy and Zach Gage ask why game developers rarely sign their work. They argue that indie developers could benefit from putting their names on their games.

Zach Oakes explains why Clojure suits making games at runtime, so designers can experience their work as they build it. He combines abstract discussion with live demonstrations, drawing on his play-clj library and Nightmod tool.

RimWorld creator Tynan Sylvester explains at GDC 2017 how Ludeon framed the game as a story generator rather than a game. He covers the design methods that came out of that frame.

David Crane's 2011 GDC postmortem of Pitfall, the classic Atari 2600 game. He explains how he created the game under the severe hardware limits of the console.

Jonathan Blow gives a roughly 90-minute talk, followed by Q&A, on how video games could actually improve education, in contrast to what is currently being tried.

Google I/O 2011 session by Ray Cromwell and Philip Rogers on writing 2D and 3D games with HTML5 and GWT. It covers porting game libraries and physics engines, sharing code with Android, and publishing to the Chrome Web Store, and showcases the ForPlay library.

Ryan Gordon (Icculus) gives a high-level overview of SDL 2.0 at Steam Dev Days 2014. He covers its features and how it eases building, porting and maintaining games, including Linux ports.

A Strange Loop talk presenting an open-source library that integrates Clojure into the Unity 3D game engine. It covers REPL-based live coding, macros, DSLs and persistent data structures for game development.

A 2016 conference talk by a mobile game CEO on the tricks of free-to-play monetization, including player profiles and how to target high-spending whales.

David Brevik's GDC 2016 postmortem of Diablo covers how it went from a turn-based claymation DOS concept to a real-time action RPG, plus the story of Blizzard North and development anecdotes.

David Brevik's GDC 2016 post-mortem of the original Diablo, covering how it evolved from a turn-based claymation DOS game into the genre-defining action RPG. It includes development anecdotes and lessons learned.

Frederick Raynal gives a GDC postmortem of Alone in the Dark, the game that helped create the survival horror genre. He covers how the team built it and shows some of the old tools used.

Jonathan Blow's Reboot Develop 2017 talk on making game programming less terrible, discussing software bloat, slowness and the design goals behind his own programming language.

Vlambeer's Jan Willem Nijman shows how to make an action game feel great by stacking small effects like screenshake, recoil and particles onto a basic shooter. It was presented at INDIGO Classes 2013.

Jonathan Blow talks at Gamelab 2018 about the design decisions behind Jai, the programming language he is building for game programmers. He covers low-friction development, quality of life and the effects of compile times.

Blizzard's Timothy Ford explains in this 2017 GDC session how Overwatch uses an Entity Component System architecture for layered gameplay. He also covers its server-authoritative netcode with client-side prediction and how they keep the game responsive and fair.

A 2018 GDC panel where Raph Koster, Starr Long, Richard Garriott and Rich Vogel look back on what went right and wrong building and running Ultima Online. They share candid stories from the early days, including player behavior and server architecture.

Bungie's David Aldridge explains the networking programming behind Halo: Reach in a 2011 GDC session. It covers how gameplay stays in sync online, including forecasting and state reconciliation.

Civilization creator Sid Meier's GDC 2010 talk on applying psychology to game design. He discusses player perception, randomness, and win states, and why designers must account for how players experience events.

A HandmadeCon 2016 panel where Chris Hecker, John Miles, Sean Barrett and Chris Green give an oral history of software texture mapping in 90s games.

FOSDEM 2020 talk from Collabora on pressure-vessel, an experimental mechanism that puts Steam games in containers on Linux. It covers using namespaces to give games their own runtime library stack independent of the host.

David Crane, designer of Pitfall for the Atari 2600, gives a GDC 2011 postmortem on the game's design challenges. He covers how he fit a large world into the console's tiny memory. The session ends with Q&A.

Catherine West's RustConf 2018 closing keynote on building a game in Rust and organizing a large codebase. It builds up an entity component system and generational indices step by step.

Jason Turner's CppCon 2016 talk builds a simple Commodore 64 game using C++17, showing how constexpr and const let a modern compiler produce tight 6502 code. He walks through assembly output to show abstractions being optimized away.

Steve Yegge's Stanford seminar on GROK, Google's internal large-scale, cross-language source code analysis system. It covers how the system helps with code search and understanding across Google's huge codebase.

Raph Koster's 2014 GDC Next talk on what science says about creativity, with practical steps game designers and developers can use to be more creative. It frames creativity as applying existing patterns in new contexts.

Matt Might's Curry On talk on ending errors in code, both software and the human genome. He covers conservative approximation of the halting problem via static analysis and a computational approach to precision medicine.

Soren Johnson, a lead designer and AI programmer on Civilization games, discusses game AI design, including whether AI should cheat, behave like a human or be fun rather than strong. He uses the Civilization series as a case study.

Timothy Cain's 2012 GDC postmortem of the original Fallout, covering how he helped build the game and set the template for open-world RPGs. He talks through production, design and programming decisions.