Blueprint Insight Documentation

Recommended First Steps

1. Run analysis from the Tools menu.
2. Open the Saved/BlueprintInsight output folder.
3. Share Markdown or JSON reports with teammates or AI assistants when reviewing Blueprint structure.

Install the Plugin

1. Close Unreal Editor.
2. Copy the plugin folder into your project's Plugins folder.
3. Confirm the plugin folder is directly under <YourProject>/Plugins/.
4. Reopen the project in Unreal Editor.
5. If Unreal asks to rebuild modules, allow the rebuild.

Enable the Plugin

1. Open Edit > Plugins.
2. Search for Blueprint Insight.
3. Enable the plugin if it is not already enabled.
4. Restart the editor if Unreal asks you to do so.

Run Blueprint Analysis

1. Open your Unreal Engine project.
2. Go to Tools > Blueprint Insight > Run Blueprint Insight Analysis.
3. Wait for the analysis to complete.
4. Open the generated reports under <YourProject>/Saved/BlueprintInsight/.

This creates Markdown and JSON files intended for developer review and documentation.

Generated reports are intended to be inspected by developers and may also be shared with AI assistants for technical discussion.

Review Boundaries

• Blueprint Insight performs static editor-side analysis.
• It does not modify Blueprints, gameplay logic, runtime behavior, assets, or project settings.
• It does not simulate gameplay execution.
• Generated outputs are intended for review, documentation, onboarding, and AI-assisted discussion.

Static reports should be treated as evidence-based review material. Runtime behavior, branch conditions, dynamic data, and project-specific design intent may require manual verification inside Unreal Editor.

Do NOT Give AI Only The Full Project Export

When using Insight Ecosystem outputs with AI-assisted workflows, we strongly recommend providing both the full project export and a focused Runtime Package for the specific system currently being modified.

providing BOTH:
- the full project export
- a focused Runtime Package

This is extremely important for long Unreal Engine implementation sessions.

Why?

During large Blueprint-driven workflows, AI may gradually drift from:

system-level runtime reasoning

toward:

localized patch reasoning

especially during manual Blueprint wiring, runtime suppression work, BT/EQS modifications, montage-related implementation, and dispatcher-heavy systems.

The problem is often not lack of information. The problem is:

loss of topology focus

Recommended Workflow

1. Full Insight Export

This provides overall project structure, global topology, and cross-system visibility.

2. Focused Runtime Package

This stabilizes runtime ownership awareness, convergence tracking, orchestration understanding, and cleanup path awareness for the system currently being modified.

Example

For a melee combat modification, a Combat Runtime Package might include:

• related BTTasks
• related BTServices
• related Blackboard assets
• combat orchestration Blueprints
• related AnimBP sections
• related dispatcher / notify data
• related hidden_dependencies excerpts
• related comment_clusters excerpts

while excluding unrelated systems such as UI, unrelated locomotion, unrelated player systems, and unrelated vehicle systems.

Important

This is not primarily about reducing file size. It is about:

stabilizing the AI's runtime attention topology

In practice, this can significantly reduce local patch drift, screenshot anchoring, orchestration confusion, cleanup-path mistakes, and runtime ownership loss during long AI-assisted Unreal Engine sessions.

For more detailed discussion about AI reasoning drift, synchronization rules, structure-first workflows, and runtime orchestration safety, please see:

AI Workflow Discipline & Synchronization