| Requirement | Minimum |
|---|---|
| Unity | 2022.3 LTS or later |
| Platform | Windows, macOS (Intel + Apple Silicon) |
| Dependencies | None — CompileScope has zero package dependencies |
CompileScope is Editor-only. It has no Runtime/ assembly and adds nothing to any player build.
Import CompileScope through the Unity Asset Store window, or via the Package Manager's My Assets tab. Everything installs directly under Assets/CompileScope/ in your project.
1. Menu item exists
Tools
└── CompileScope
2. No compile errors
Open the Console (Window → General → Console) and confirm zero errors attributed to CompileScope.
3. Window opens
Click Tools → CompileScope. With no analysis run yet, the Overview tab shows an empty state with Analyse Now and Load Demo Data actions.
CompileScope stores compilation and domain reload history relative to the project root:
<ProjectRoot>/
└── Library/
└── ToolsStudio/
└── compilescope/
└── history.json
This lives under Library/, which Unity regenerates automatically and which most teams already exclude from version control — no additional .gitignore entry is needed in the typical case.
CompileScope adds a page under Project Settings → Tools Studio → CompileScope covering display filters, auto-rebuild-on-compile, cache management, and Markdown report export. See Configuration for the full reference.
- Delete the
Assets/CompileScope/folder from your project. - Optionally delete
Library/ToolsStudio/compilescope/from the project root to clear stored history. - Unity recompiles. No other cleanup is required.
Next: Getting Started