Playing Video Games One Frame at a Time
summary
Shows a reproducible pipeline: running Doom demo files to get deterministic outputs and gate refactors with an automated demo-check CI, using C++ to parse frame-by-frame inputs. Tries OpenCV template matching then abandons it for hue+RGB centroid voting to classify gems, enumerates 32 move patterns and scores moves by board position. For non-cooperative games injects a DLL with Detours DLL injection, hooks DirectX endScene, emits per-frame key scripts, and gets levels completed reliably though occasional stuck states remain.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 4:15Play games programmatically
- 5:38Games with input recording
- 15:25Automating match-3 games
- 34:14Hacking unsupported games
- 53:20Summary and applications
- 55:29Q&A
related talks
43mNo More Jank: Escaping the Matrix of Frame Drops
30mVisualizing process evolution
08mCreative Console: A Player-driven Game Based on A Modular Fast-Evolving-And-Verifying Framework
01h 03mWhat I Talk About When I Talk About Cross Platform Development
01h 05mDDD, event sourcing and CQRS – theory and practice
17mHow We Got DOOM Running on Zephyr (And Why You Should Try It)
36mBuilding Strong Code Through Patterns
23mProgrammingArt++