unity-project-scout

To analyze an existing Unity project architecture before refactoring, run a project scout to inspect Unity versions, render pipelines, installed packages, asmdef layouts, and Assets/ folder structures. This surfaces architectural signals and risks early.

You can detect architectural signals in a Unity3d codebase by scouting folder layouts, asmdef configurations, Unity versions, and rendering pipelines. It also identifies usage patterns like ScriptableObject configs, services, events, and custom inspectors.

Yes, you can inspect asmdef layouts and folder structures in mid-sized Unity projects by running a scout to map the Assets/ directory. This identifies architectural risks and recommends constraints before proposing changes.

Yes, the Unity project scout works across different Unity versions and packages. It inspects the specific Unity version, rendering pipeline, and key installed packages to establish a project baseline for architecture assessment.

The best way to establish a baseline for a Unity project assessment is loading a reconnaissance advisor first. It inspects versions, packages, asmdefs, folders, and coding patterns like ScriptableObject configs and tests to surface risks.

You should use a Unity project scout instead of directly modifying code when approaching existing codebases. Scouting first surfaces architectural constraints and usage patterns, preventing unintended breaks before you propose architecture changes.