Akash Bhatt.
RefSafe Pro v2.2.0
Documentation menu

Getting started

Your first scan

This walks through a first pass on a real project: scan, triage, fix, and confirm.

1. Open the window

Tools → RefSafe → Pro. The Issues tab is selected by default.

2. Pick a scope

The scope dropdown controls how much of the project gets scanned:

  • Open Scenes — only the scenes currently loaded. Fastest, good for a tight edit loop.
  • Entire Project — scenes, prefabs, and ScriptableObjects. Start here for a first pass.

On a large project the first Entire Project scan takes a while, because RefSafe has to build its asset map from scratch. Later scans reuse the cache and are substantially faster.

3. Scan

Click ▶ Scan. A progress bar appears with a cancel button — scanning is incremental and yields to the editor, so Unity stays responsive and you can cancel at any point without losing the results already gathered.

4. Read the results

Results group by scene or asset. Each row carries a severity chip:

  • Critical — genuinely broken. A missing script or missing prefab source is unrecoverable without intervention.
  • Warning — probably wrong. A broken UnityEvent will fail silently at runtime.
  • Info — worth knowing. An unused asset may be intentional.

Click a row to select and ping the affected object in the Hierarchy or Project window. Expand the inline help to see what the issue means, which Component.field it came from, and how to fix it.

A first scan on an established project usually returns a lot. Don’t try to clear it in one sitting — sort by Critical and work down.

5. Fix

Rows with an available automatic fix show a Fix button. RefSafe ships fixers for missing scripts, missing references, duplicate components, missing prefabs, and deleted build scenes.

For missing references, the Replace with… dropdown suggests likely replacement assets ranked by relevance — useful after a folder move that broke a batch of references at once.

Multi-select rows and use Fix Selected, or Fix All from the toolbar. Every fix is wrapped in an Undo group, so Ctrl/Cmd + Z reverts it.

See fixing issues for the full workflow.

6. Deal with what you can’t fix now

Not everything gets fixed today. Three ways to keep the list honest:

  • Snooze — hides the issue for 1, 7, or 30 days, then it returns.
  • Ignore — hides it indefinitely. Stored per-user, so it won’t affect teammates.
  • Note — attach free-form text explaining why it’s still there.

Anything you snooze or ignore lives in Library/RefSafePro/UserSettings.json, outside version control.

7. Re-scan with ChangedOnly

After fixing, switch the scope to Changed Only and scan again. RefSafe tracks which assets changed since the last scan and re-validates just those — fast enough to run repeatedly while you work.

The results panel shows a diff against the previous scan, so you can confirm your fixes closed issues without opening new ones.

Next steps