Unity Integration
EngineForge integrates with the open Unity project to use relevant project and editor context, perform supported work inside Unity, and observe specific runtime behavior when useful.
Connect a project
- Open the Unity project folder in EngineForge, or select it as the Game Folder when the workspace contains more than one project.
- Open the same project in Unity Editor.
- Allow EngineForge to install or update the integration, then wait for Unity to finish importing and compiling it.
- Open Engine Status and confirm that Unity reports connected before requesting editor actions.
EngineForge-managed integration
EngineForge installs the bridge DLL and a companion version marker under Assets/Plugins/Editor. When the shipped bridge version changes, EngineForge updates those managed files and Unity imports them again.
The generated bridge files are added to the project gitignore. These files are managed by EngineForge and should not be edited or committed as project source.
Editor and compilation workflow
Specialists can use the Unity actions advertised by the running integration for project, scene, GameObject, component, prefab, asset, script, console, selection, and related work, subject to their Forge permissions and approvals.
Script edits can trigger compilation and an assembly reload. The bridge may disconnect briefly during that cycle and is designed to reconnect after Unity settles. Inspect compilation errors before asking the Crew to continue with dependent work.
Runtime verification
When a task has observable runtime behavior, Unity workflows can enter Play Mode and collect bounded evidence such as traces, watches, logs, screenshots, and input results. This is a verification path, not proof by itself that feel, visuals, or every target platform is correct.
Troubleshooting
- Disconnected while Unity is compiling: wait for compilation and any assembly reload to finish; EngineForge should reconnect automatically.
- Compilation errors remain: resolve them in Unity or with the Crew before retrying bridge operations that depend on the new scripts.
- Unity is open but the bridge stays disconnected: verify both apps point at the same project, then use Retry Connection or restart Unity Editor.
- The integration is repeatedly redeployed: check that the project files are writable and that security software is not blocking the managed DLL.
- An expected action is unavailable: confirm the integration is connected and consult Capability Reference. Availability depends on the current Unity project and the capabilities supported by the integration.