Summary
The history of game AI is best understood as a sequence of changing priorities rather than a simple march toward “smarter” agents. Early game AI focused on believable control with limited hardware. Later production work formalised movement, pathfinding, and decision architecture. More recent AI-and-games research broadened the field to include procedural content generation, player modelling, machine learning, and games as benchmarks for AI itself. (Prof Charles, CRE341 Wks 5 and 7–9, see source-cre341-lectures; Millington, Artificial Intelligence for Games, see source-artificial-intelligence-for-games; Yannakakis and Togelius, Artificial Intelligence and Games, see source-ai-and-games)
Key ideas
1. Early and classical game AI
The earliest game-AI traditions were tightly constrained by memory, CPU budget, and design clarity. Simple rule systems, finite-state machines, search, and hand-authored behaviours dominated because they were understandable, cheap, and effective.
2. Production architecture era
As game worlds became larger and NPCs became more central, the problem shifted from “can an NPC do something intelligent?” to “can we structure many behaviours predictably?” This is where:
- ai-state-machine-pattern
- behaviour-trees
- goal-oriented-action-planning
- utility-ai
- navigation-mesh-construction
became important as production architectures rather than isolated tricks.
3. Broader AI-and-games era
Yannakakis and Togelius explicitly widen the scope. Game AI is no longer only NPC control. It also includes:
This broadening matters historically because it changes what counts as “game AI” in both research and teaching.
In practice
For teaching, the history suggests a useful sequencing principle:
- teach classical authored AI first because students can inspect and debug it
- then teach planners and optimisation methods
- then broaden outward into modelling, PCG, and learning systems
This is close to the route already emerging in CRE341 and in the vault’s newer synthesis pages.
Evidence
- Millington represents the strong mid-period production textbook tradition: movement, pathfinding, decision structures, and infrastructure. (Millington, Artificial Intelligence for Games, see source-artificial-intelligence-for-games)
- CRE341 lecture material explicitly frames classical NPC control, procedural generation, and ML as part of one widening curriculum rather than unrelated topics. (Prof Charles, CRE341 Wks 5–9, see source-cre341-lectures)
- Yannakakis and Togelius make the strongest field-level claim that AI in games includes not only agents but also generation, modelling, and games as AI testbeds. (Yannakakis and Togelius, Artificial Intelligence and Games, see source-ai-and-games)
Implications
- Students should not equate “game AI” only with enemies chasing the player.
- Historical awareness helps explain why some methods remain dominant in shipped games: reliability, cost, readability, and tooling often matter more than theoretical sophistication.
- It also clarifies why modern AI hype can be misleading: many of the most useful game-AI systems are still authored, constrained, and deliberately imperfect.
Open questions
- Which current generative-AI techniques will become stable production patterns, and which will remain experimental?
- How should history be taught so that older systems are not dismissed as obsolete when they are still the most shippable solutions?
Related
game-ai-agent-design · overview-artificial-intelligence-in-games · overview-cre341-agent-ai-route · ai-state-machine-pattern · behaviour-trees · machine-learning-games · procedural-generation · player-modelling