C# Script
PlayerController
Unity workflow
EngineForge is the AI platform for game development, with Unity support built in. Open your Unity project (2021.3 or later, URP not required) and let the Crew work across C# scripts, scenes, GameObjects, components, editor state and the running game.
Project context
EngineForge indexes the project on your computer and reads the Unity editor directly: scenes, GameObjects, components, prefabs, references and editor state.
EngineForge Unity context
Structures and relationships relevant to the current task
C# Script
PlayerController
Scene
Level 01
GameObject
Player
Component
PlayerMovement
Prefab / Reference
Player Prefab
Current task
Context across Unity
Relevant relationships, not a fixed hierarchy.
Unity capabilities
The Crew reads the project in Unity, makes changes in the editor, and enters Play Mode to check them.
Inspect, create and change scenes and GameObjects.
Work with components, serialized properties, references and configuration.
Work with prefabs and Unity-native systems, including Particle Systems.
Use editor actions, compile, enter Play Mode, and watch what happens while the game runs.
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
From understanding the project to a change in Unity, then Play Mode when the change affects how the game plays.
Existing project
Start with the Unity project already on disk.
Unity context
Read the GameObjects, components, prefabs and editor state the task touches.
Unity action
Make the change in the project and the Unity editor.
Your call
Try it yourself or send the Playtester when the change affects how the game plays.
When observable
Watch for the specific behavior in the running game.
Developer decision
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
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
Does walking into the enemy cause the expected player death?
Valid observation
The player entered the dead state and returned through the project's respawn flow.
Developer review
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
Maestro leads the session and brings in Builder, Juicer, Systems Smith or Playtester as the Unity task needs. Plan mode stays read-only; Forge lets each specialist use the tools of its role within your approval settings.
Explore EngineForge Crew →Inspectable work
Everything the Crew does in your Unity project stays available to review: the changes, the evidence, and your decision.
Change
Inspect files, diffs and the changes made in the editor.
Evidence
Review compiler messages and what was seen in Play Mode.
Review
Keep approvals and captured code checkpoints visible.
Unity support and boundaries
Available now
Unity 2021.3 or later is supported today, through your own Unity editor.
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
Explore the integration, read the first-hand workflow, or download EngineForge.
Read the first-hand workflow →