FAQ

Yes. EDP runs entirely within the Unity Editor and adds nothing to your build. There are no MonoBehaviours, no runtime scripts, no shader variants, and no GameObjects added to your scenes, so it never affects build size or runtime performance.

Yes. All checks support Built-in, Universal and High Definition render pipelines. Safe Delete in particular handles the full URP / HDRP entry-point set: UniversalRenderPipelineAsset, ScriptableRendererData, Renderer Features, Volume Profiles, Volume Components, and custom render passes, with no false positives.

Unity 6.0 LTS or later. Earlier versions such as 2022.3 LTS are not supported.

No. EDP works fully standalone with 120 native checks. Installing Scene Pilot Pro and enabling the bridge adds 64 in-scene checks across every scene and prefab in the project (185+ total).

Yes. Every EDP-applied action is captured in the Action History journal and can be reverted from there with one click, even across editor restarts. Soft-deletes go through the Trash with full restore. There is no operation that can't be reversed.

22 of the 120 native checks ship as Auto tier (~18%): 14 across Asset Health, 5 in Build Review, 3 in Prefab Drift. The remaining 98 are Manual - either because the right fix depends on intent (Code Audit) or because the action crosses ownership boundaries (SPP-bridged scene checks).

Yes. The CLI entry point Kronnect.EditorDoctorPro.CLI.EDPCommandLine.Run runs the same scan engine as the Doctor window, supports the same scope and suppression configuration, and emits the same JSON / CSV / HTML reports. The repo ships a reference GitHub Actions workflow at .github/workflows/edp-acceptance.yml.

Use --fail-on <severity> in the CLI. The flag controls the exit code threshold: error (default) exits non-zero on any error or critical finding; warn also fails on warnings; never always exits 0 (useful when a verifier script downstream owns pass / fail).

No. There is no telemetry, no anonymous launch ping, no opt-in usage stats. The only network calls EDP makes are documentation links you explicitly click.

No. EDP has no license gating - it works out of the box on any Unity install.

Code Audit uses com.unity.nuget.mono-cecil for IL inspection. The package is the official Unity-distributed Cecil; we cannot ship our own copy under the Unity EULA. The first time you open the Code Audit tab, EDP installs the package automatically. If the install fails, install version 1.10.2 manually via the Package Manager.

Three: per-issue (silence one specific finding), per-rule (silence every finding from a check), and per-scope (silence findings from a check on a path glob, e.g. suppress EDP-CODE-CONV-* on Assets/Plugins/**). Entries are stored as scope + check id + target in ProjectSettings/EditorDoctorPro/suppressions.json and shared via git. See Settings & Suppression.

Project settings and suppressions live under ProjectSettings/EditorDoctorPro/ (settings.asset, suppressions.json). That folder is gitignored by default, so rule overrides and suppressions are per-machine unless you choose to version-control them. The Action History journal lives in Library/EDP/journal.json; the soft-delete trash lives in .EditorDoctor/Trash/ at the project root. Both Library/ and .EditorDoctor/ are per-machine state and gitignored by default. Per-user view preferences (column widths/order/visibility) live in UserSettings/EditorDoctorPro/.