Interview with
summary
Claims that game teams deliberately tolerate inefficiency because art assets are binary assets that break Git merges, so workflows use Subversion, giant branches and Excel five years ahead planning with fancy colors instead of Trello. Demonstrates a Java-made demo that "isn't a game" and argues game AI is deliberately imperfect — AI tuned to be imperfect — producing buggy emergent behavior that can surprise players and even teach ideas via chaos theory.
AI-written summary · about
chapters (6)
- 0:00Intro
- 1:10What does the world need
- 2:05How to sabotage efficiency
- 3:15AI
- 4:40Boring people
- 6:10Control
related talks
52mThe Journey of AI in Games: A Technical and Philosophical overview
20mStudio Speaks: The Reality of AI Adoption in Games
34mGame Developers Are Becoming Directors, Not Coders
39mEmbarrassing Mistakes: a short story about AI
59mGame AI 4N00bz
58mCurrent challenges for game developers
01h 01mIntroduction to Practical AI
51mWhat AI Can, Can’t, and Shouldn’t Do for Games
