Visualize, trace, diagnose and repair serialized Unity references across scenes, prefabs, components and assets, with direct and detected indirect impact paths, coverage reporting and focused navigation.
Refnexa is an Editor-only Unity tool for visualizing, tracing, diagnosing and repairing serialized references across supported scenes, prefabs, components, ScriptableObjects and assets.
Use Refnexa to understand how serialized objects are connected, inspect direct serialized dependents and explore detected indirect serialized dependents within the declared analysis coverage.
Key workflows include:
• Visual Reference Graph
Navigate serialized relationships between supported Unity objects and assets.
• Direct Serialized Impact
Inspect serialized fields that directly reference a selected target.
• Detected Indirect Impact Paths
Detect indirect serialized dependents and inspect one shortest detected path per dependent.
• Focused Impact View
Temporarily isolate a target, dependent and detected path without altering your normal graph layout.
• Diagnose and Repair
Identify missing or unassigned serialized references, navigate directly to their owners and fields, and make explicit repairs using standard Unity editing and Undo workflows.
• Project Reference Index
Index supported project assets to complement live analysis of loaded scenes.
• Analysis Coverage
Refnexa reports whether results are based on Live, Indexed or Mixed data and exposes relevant scope, traversal and truncation information.
• Reporting
Export analysis and validation information for review, debugging and project maintenance.
Refnexa is designed for developers, technical artists, designers and other Unity team members who need greater visibility into serialized project relationships without requiring runtime components.
Refnexa is Editor-only. It adds no runtime components, requires no external services or accounts, and does not send project data anywhere.
Important coverage note:
Refnexa analyzes serialized references within the declared coverage. It does not perform general C# static analysis or runtime dependency tracing.
Closed scenes are not opened automatically. Always review the reported analysis coverage when interpreting results.
