Unity Asset Store · v2.2.0

RefSafe Pro

Unity fails silently. A renamed script, a deleted asset, a scene removed from disk but not from Build Settings — none of it errors while you work, and all of it surfaces in front of players. RefSafe Pro finds it first.

Get it on the Asset Store Read the manual API reference

What it detects

Missing scripts Deleted or renamed MonoBehaviours leaving "Missing (Mono Script)" slots
Missing references Serialized fields pointing at assets that no longer exist
Broken UnityEvents Button handlers whose target or method is gone — they fail silently
Missing prefabs Prefab instances whose source asset was deleted
Broken Addressables AssetReference GUIDs and group entries that no longer resolve
Invalid layers Objects on layer indices with no name in the Tag Manager
Invalid materials Null materials and shaders that failed to compile
Duplicate components The same component added twice to one GameObject
Deleted build scenes Build Settings entries whose scene file is gone
Huge transforms Positions and scales past the float-precision danger zone

One window, four tabs

Issues

Scan results you can actually work through — filter, group, search, fix, snooze, annotate, and export.

Cleaner

Unused assets, empty folders, duplicates, import-settings audit, and build weight — with dry-run preview and automatic backup.

References

What references this asset, what it depends on, and a pan/zoom dependency graph.

Trends

Health score over time, issue trend charts, and comparison between any two scans.

Built for CI

A batchmode entry point turns validation into a build gate — broken references fail the pipeline instead of reaching a store submission. Reports export as CSV, JSON, HTML, TXT, and Markdown, plus GitHub Actions annotations and GitLab Code Quality.

Unity -batchmode -nographics -quit \
      -projectPath "$PROJECT_PATH" \
      -executeMethod RefSafe.Pro.CliRunner.RunScan \
      --scope EntireProject \
      --format github \
      --fail-threshold Warning

Full setup, including GitHub Actions and GitLab CI config, is in command line and CI.

Extend it

Custom validation rules, issue fixers, report exporters, and fix-suggestion providers are all first-class. Everything is discovered by reflection — drop a class into an assembly that references RefSafe.Pro.Editor and it's picked up on the next domain reload, with no registration code. Custom exporters even work as --format values on the CLI.

See extending RefSafe Pro and the API reference.

Documentation

Installation Your first scan Issue type reference Settings reference Command line and CI Troubleshooting

Questions or bug reports: [email protected]. The free, MIT-licensed companion RefSafe Lite is on GitHub.