Projects and Engines

Workspace and Game Folder

• Workspace: the folder or multi-root workspace open in EngineForge.
• Game Folder: the Unity or Godot project used for engine integration and engine-scoped project context.
• Nested project: an engine project inside a larger repository.
• Multi-root workspace: several top-level folders, with one resolved Game Folder.

How EngineForge identifies the game

EngineForge checks each workspace folder and one level of child folders for Godot’s project file or Unity’s project folders. A saved Game Folder selection takes priority while it remains inside the current workspace.

Choose the correct context

1. Open the repository or game project in EngineForge.
2. Confirm that the detected Game Folder is the project you intend to change.
3. Use Set as Game Folder when the project is nested more deeply or automatic detection selected the wrong candidate.
4. Open that project in Unity or Godot and confirm the integration status before engine-specific work.

Why the distinction matters

File tools, project indexing, engine actions, checkpoints, and change review need a consistent project root. In a larger repository, paths outside the Game Folder can still belong to the workspace, but engine-specific work remains anchored to the selected game project.

Troubleshooting boundary

Detecting a game project and connecting its editor are separate states. If the project is detected but the integration is not ready, use Engine Status rather than changing folders without evidence.

Related documentation