RefSafe Pro overview

RefSafe Pro is a Unity editor tool that scans your project for the breakage Unity stays quiet about: missing scripts, broken serialized references, invalid layers, missing prefab instances, broken UnityEvents, broken Addressables, invalid materials, shader errors, duplicate components, huge transforms, and scenes still listed in Build Settings after being deleted from disk.

It’s built for production projects that need full-project validation, CI-friendly reporting, in-editor visibility, and extension points for studio-specific workflows.

The problem it solves

Unity fails silently far more often than it errors. Rename a MonoBehaviour without its .meta file and every GameObject using it carries a “Missing (Mono Script)” — with no console error until that scene loads. Delete an asset a prefab references and the field just reads None, indistinguishable from one that was never assigned. Remove a scene from disk but not from Build Settings and the build breaks at the worst moment.

None of this surfaces while you work. All of it surfaces in front of players.

The four tabs

RefSafe Pro is one editor window with four tabs:

Tab	What it does
Issues	Scan results — filter, group, search, fix, snooze, annotate, and export
Cleaner	Unused assets, empty folders, duplicate assets, import-settings audit, build-weight analysis
References	Find what references an asset, what an asset depends on, and view the dependency graph
Trends	Health score over time, issue trend charts, and comparison between any two scans

What it scans

• Open scenes
• Every scene in the project, without opening them
• Every prefab in the project
• Every ScriptableObject in the project
• Materials
• Build Settings, for scenes deleted from disk
• Addressables group entries, for orphaned entries
• Changed assets only, for fast incremental re-scans
• Individual assets and GameObjects, via context menu or drag-and-drop

What it detects

Reference issues — missing scripts, missing serialized object references, missing prefab instances, broken UnityEvent callbacks, broken Addressable AssetReference fields, orphan Addressables group entries.

Structural and content issues — duplicate components, invalid layers, invalid materials, shader compilation errors, huge transform position or scale values, deleted build scenes, prefab variant component overrides.

Cleaner findings — unused assets, empty folders, duplicate assets, heavy textures with Read/Write enabled, heavy audio clips set to Decompress On Load, and the heaviest assets reachable from your Build Settings scenes.

Every issue is classified Critical, Warning, or Info. See the issue type reference for what each one means and how to fix it.

Where to go next

• Installation — import the package and open the window
• Your first scan — from import to a clean result in a few minutes
• Command line and CI — fail a build when validation fails
• API reference — the public scripting surface