C# Script
PlayerController
Unity workflow
AI Assistant for Unity Game Development
Work with an existing Unity project across C# scripts, scenes, GameObjects, components, editor state, and the running game—inside EngineForge.
Project context
Work with the Unity project, not just the files.
EngineForge indexes the project locally. Through the Unity integration, supported workflows can use the scenes, GameObjects, components, prefabs, references, and editor state relevant to the task.
EngineForge Unity context
Structures and relationships relevant to the current task
Scene
Level 01
GameObject
Player
Component
PlayerMovement
Prefab / Reference
Player Prefab
Current task
Context across Unity
Relevant relationships, not a fixed hierarchy.
Unity capabilities
What the Unity integration enables.
Use the Unity integration to understand relevant context, work with supported Unity structures, and run the game to observe specific behavior when useful.
Scenes & GameObjects
Inspect, create, and modify supported scene structures and GameObjects relevant to the task.
Components & Properties
Work with supported components, serialized properties, references, and configuration.
Prefabs & Engine-Native Systems
Work with supported prefab operations and Unity-native workflows, including Particle System work.
Editor & Runtime Actions
Use supported editor operations, compilation and Play Mode workflows, and bounded runtime observation when useful.
These are capability families, not a complete command catalog. See the Unity integration docs for current capability coverage and limitations.
From Unity context to running behavior
One possible path through a Unity task.
Move from project understanding into supported Unity actions. Enter Play Mode and use runtime verification only when the task benefits from those stages.
Existing project
C# and project structure
Start with the Unity project already on disk.
Unity context
Scenes and relationships
Use relevant GameObjects, components, prefabs, and editor state.
Unity action
Work inside Unity
Make the supported project or engine change relevant to the task.
When relevant
Enter Play Mode
Run the game only when the task benefits from observing behavior.
When observable
Collect bounded evidence
Observe a named condition through supported runtime capabilities.
Developer decision
Review the result
Inspect the change and any relevant compilation or runtime evidence.
Not every task needs every stage. This is one possible path using only the Unity context, actions, and observations relevant to the work—not a fixed autonomous pipeline.
A real Unity example
Does enemy contact trigger death and respawn?
In an evidence-backed Unity platformer scenario, EngineForge inspected the existing collision logic, used the relevant Unity project and editor context, then exercised the behavior in Play Mode.
Read the first-hand workflow →Question
Collision behavior
Does walking into the enemy cause the expected player death?
Valid observation
Death and recovery
The player entered the dead state and returned through the project's respawn flow.
Developer review
Bounded result
Review the result and confirm that no speculative gameplay fix was introduced.
The observation answers the named collision and respawn question. It does not claim exhaustive gameplay testing or full-game correctness.
Crew inside the workflow
Bring in the specialist the Unity task needs.
The selected specialist can work on the current Unity task. Plan remains read-only; Forge enables appropriate actions within approval boundaries; and bounded delegation is available when another specialty is useful.
Explore EngineForge Crew →Inspectable work
Review the result, not just the response.
Work performed through EngineForge and the Unity integration remains available for developer review. Project changes, supporting evidence, and the developer decision stay connected.
Change
Files and project work
Inspect files, diffs, and supported project or engine changes.
Evidence
Relevant feedback
Review compilation feedback and supported runtime observations where relevant.
Review
Developer judgment
Keep approvals and captured code checkpoints visible.
Unity support and boundaries
Supported Unity workflows, with documented boundaries.
shipping
Unity editor and runtime workflows ship with the upcoming EngineForge release.
Exact coverage
See the Unity integration docs for current version support, capability coverage, and limitations.
Independent product
EngineForge is an independent product and is not affiliated with or presented as Unity Technologies' official assistant.
Continue with Unity
Take a Unity task beyond the code change.
Explore the integration, read the first-hand workflow, or download EngineForge.
Read the first-hand workflow →