🕸️ Dependency Graph

The Dependency Graph is not just a pretty picture—it’s an X-Ray for your project.

Deep Scan Technology

Nexus Graph goes deeper than Unity’s built-in “Select Dependencies”.

1. Reflection Analysis

We scan your C# MonoBehaviours using System.Reflection.

  • Private Fields: Found.
  • Lists/Arrays: Found.
  • Properties: Found. Even if you don’t drag-and-drop the reference in the Inspector, if your code types it, we track it.

2. Smart Caching

Scanning 100,000 assets is slow. Nexus Graph uses Differential Hashing:

  • We store a hash of every file’s dependencies.
  • On Scan, we only re-process files that have changed.
  • Result: Sub-second refresh times for massive projects.

Visual Diagnostics

Heatmaps (The “Impact” Metric)

Click Toggle Heatmap to see the weight of your project.

  • Thick/Yellow Borders: These nodes are “High Impact” (High Fan-In).
  • Why it matters: If you change a High Impact script, you trigger recompilation for active dependents. If you change a High Impact prefab, you risk breaking hundreds of instances.

Cycle Detection (Red Borders)

Circular dependencies (A -> B -> A) are the silent killers of serialization depth and memory cleanup. Nexus Graph highlights these chains in Red instantly.

Isolation Mode

Working on a specific subsystem? Right-Click -> Isolate Dependency Chain. Focus only on the InventorySystem and ignore the rest of the noise.


This site uses Just the Docs, a documentation theme for Jekyll.