Skip to content
EQLabs EQLabs

Blueprint Inspector

Blueprint Inspector

Section titled “Blueprint Inspector”

Module: Tech · Category: QA · Tool ID: BlueprintInspector

Three-tab Blueprint analysis suite. Complexity scans Blueprints for node counts, nesting depth, tick usage, cast count, etc. Interfaces audits Blueprint Interface conformance — which Blueprints implement which interfaces, where conformance is incomplete. Event Timeline traces event execution order — useful for debugging “BeginPlay race condition” type issues.

Screenshot 01 — Hero shot — Inspector on Complexity tab with mixed-severity Blueprints listed, top entries sorted by node count.

When to use it

Section titled “When to use it”
  • Project-wide Blueprint complexity audit
  • Pre-shipping QA — finding Blueprint complexity hot spots
  • Interface conformance review — confirming Blueprints actually implement what they claim
  • Debugging event-ordering bugs

When not to use it

Section titled “When not to use it”
  • Don’t expect this to refactor Blueprints — surfaces issues; fixes happen in the Blueprint editor

Opening the tool

Section titled “Opening the tool”
  1. Open the EQLabs Hub and search for Blueprint Inspector (or browse to Tech → QA)
  2. Click the tool card
  3. Use the tab bar: Complexity / Interfaces / Event Timeline

Tab 1 — Blueprint Complexity Analyzer

Section titled “Tab 1 — Blueprint Complexity Analyzer”

Per-Blueprint metrics: total node count, nesting depth, tick usage, cast count, common anti-patterns.

Tab 2 — Blueprint Interface Auditor

Section titled “Tab 2 — Blueprint Interface Auditor”

Audit conformance:

  • Which Blueprints implement Blueprint Interfaces
  • Where implementations are incomplete (missing functions, signature mismatches)
  • Orphan interfaces (no implementers)

Tab 3 — Blueprint Event Timeline

Section titled “Tab 3 — Blueprint Event Timeline”

Trace event execution order — BeginPlay, BeginPlay (Actor), BeginPlay (Component), custom events. Useful for catching race conditions where two Blueprints depend on each other’s BeginPlay.

Settings reference

Section titled “Settings reference”

Persists via standard tool framework.

Output

Section titled “Output”
  • In-panel results per tab
  • Click-to-navigate — single-click pings, double-click opens BP editor

Tips & gotchas

Section titled “Tips & gotchas”
  • High node count is often legitimate — a complex character BP can have 500+ nodes. Use as signal, not absolute rule
  • Tick usage on every Blueprint is the common anti-pattern — finding which BPs tick when they don’t need to is high-value
  • Interface conformance gaps cause runtime cast failures — fix before shipping
Section titled “Related tools”
Report an issue with this tool

Opens our feedback form in a new tab with the tool name pre-filled.