# Why Game Development AI Needs Engine Context

> How code, editor and scene state, and runtime evidence answer different parts of a game-development task.

Canonical HTML page: https://engineforge.ai/blog/why-game-development-ai-needs-engine-context

This markdown is a representation of that page for agents. Site: EngineForge (https://engineforge.ai).

## What this page is for

Understand why file-only AI is insufficient for engine-based game work.

## Related pages

- [AI Game Development Software](https://engineforge.ai/): Build Unity and Godot games in a complete AI platform with an extensible specialist Crew, runtime verification, and reviewable changes.
- [Code Graph | EngineForge Documentation](https://engineforge.ai/docs/code-graph): Use the local Game Folder index, project overview, symbol search, and Code Graph to navigate code relationships.
- [Runtime Verification | EngineForge Documentation](https://engineforge.ai/docs/runtime-playtesting): Run Unity or Godot when relevant, validate the observation, and review bounded runtime evidence for a specific behavior.
- [Unity Integration | EngineForge Documentation](https://engineforge.ai/docs/unity-bridge): Use Unity project and editor context, supported engine-native actions, and conditional runtime evidence through EngineForge.
- [Godot Integration | EngineForge Documentation](https://engineforge.ai/docs/godot-bridge): Use Godot scene and editor context, supported engine-native actions, and conditional runtime evidence through EngineForge.

## Machine-readable resources

- [llms.txt](https://engineforge.ai/llms.txt): Entry point for agents: what EngineForge is, when to reach for it, and every other machine-readable file.
- [Agent instructions](https://engineforge.ai/agent-instructions.md): When to use EngineForge, which questions it answers, and how to call the public API to answer them.
- [OpenAPI description](https://engineforge.ai/openapi.json): OpenAPI 3.1 description of the public EngineForge API, with an operation id, typed parameters, and a response schema for every endpoint.
- [Developer resources](https://engineforge.ai/developers): Human-readable index of the EngineForge public API, machine-readable files, and integration notes.
- [Documentation](https://engineforge.ai/docs): Product documentation for Cockpit, Crew, Unity, Godot, runtime verification, and review controls.
- [Sitemap](https://engineforge.ai/sitemap.xml): Every indexable EngineForge page with its last modification date.
- [robots.txt](https://engineforge.ai/robots.txt): Crawl boundaries and the canonical sitemap location.