04 · Build & Maintain

Foundation Models for Game Development and Maintenance

How coding and tool-using agents turn specifications into executable scenes, mechanics, engine projects, repairs, and maintainable software.

Direct answer

How is AI used in game development?

AI game development applies foundation models to the engineering work required to turn ideas and specifications into running, revisable games. Systems can generate or edit code, create scenes, configure assets, invoke engine tools, inspect runtime output, diagnose failures, repair bugs, and coordinate changes across a project.

Tool-using development agents go beyond code completion by acting inside engines and editors, where scripts, prefabs, scene graphs, resources, input mappings, physics, and build settings must agree. Execution feedback is essential: plausible code may compile yet fail at launch, violate a requirement, break another mechanic, or become difficult to maintain. Strong systems therefore work in a loop—propose a change, run or observe the game, interpret errors and behavior, then revise the project.

Long-term usefulness also depends on maintenance. Models should cope with changed requirements, regression tests, multiple project versions, documentation, and handoff to another developer. Evaluation should measure launchability, functional requirements, repair success, regression safety, iteration cost, and whether the result can be understood and modified later. This differs from design: proposing a level or mechanic defines an artifact, while development must implement it within executable engine constraints.

This topic is surveyed in AI for Games in the Foundation Model Era.

Research scope

What this topic covers

01

Code, scenes, and engine projects

Implementation across scripts, assets, bindings, components, resources, and project configuration.

02

Execution, debugging, and repair

Agents that run projects, inspect feedback, locate failures, and revise implementations.

03

Maintenance and handoff

Regression-safe revision, multi-version work, documentation, and reproducible project transfer.

Evidence

What should evaluation establish?

A development system should be evaluated on executable outcomes rather than screenshots or code plausibility alone. Strong tests exercise requirements, failures, later revisions, and whether another developer can reproduce and continue the work.

  • Launchability and requirement completion
  • Debugging and repair success
  • Regression safety across revisions
  • Maintainability, reproducibility, and handoff

Starting points

Representative anchors