Trace a bug across Blueprints and C++ in Unreal Engine

Use an editor agent that reads Blueprint graphs, your C++, the engine source and the editor log to follow a bug from the symptom to the line that causes it.

6 min read

Why these bugs take so long

The hard bugs in an Unreal project rarely sit in one place. An event fires in a Blueprint, calls a function declared in a C++ parent class, which depends on something the engine does internally. Finding the cause means switching between the graph editor, your IDE and the engine source, and holding the whole chain in your head.

Kismet’s agent can read all of those from inside the editor, in one conversation:

  • Blueprint graphs, as an execution-flow description with the node list.
  • Your project’s C++ and plugin source: finding files, outlining a class’s declarations, and reading implementation by line range.
  • The engine source, in the same way.
  • Any class’s Blueprint-visible properties and callable functions, with their pin types.
  • The current editor session log: compile messages, Blueprint runtime errors, asset load warnings and Play In Editor output.
  • Asset references: what an asset depends on, and what refers to it.

A workflow that works

  1. 1.

    Reproduce the bug in the editor first

    Run the level in Play In Editor until the problem happens. That puts the runtime error or warning in the session log, where the agent can read it.

  2. 2.

    Describe the symptom, not your guess

    Say what you did, what you expected and what happened. Name the asset if you know it. Leave the theory out so the agent follows the evidence.

  3. 3.

    Ask for the evidence with the answer

    Ask it to cite the Blueprint node, or the source file and line, for each step of its explanation. An answer you can check takes seconds to verify.

  4. 4.

    Check the cited lines yourself

    Open the file and the graph. If the explanation holds, ask for the fix. If it does not, say which step is wrong and why.

  5. 5.

    Fix, compile and rerun

    For a Blueprint fix, the agent edits the graph and compiles it. Then run the level again and ask it to read the log once more.

Prompts to try

Prompt to try
OnDamaged never fires on BP_Enemy when the player hits it. I just reproduced it in PIE. Read the log, the Blueprint and its C++ parent, and tell me where the chain breaks. Cite the node or the file and line for each step.
Prompt to try
I get "Accessed None trying to read property WeaponRef" in the log. Find which graph reads it, where it is supposed to be set, and why it is not set by then.
Prompt to try
In the engine source, what has to be true for ACharacter::Jump to do anything? Then check whether BP_Player meets those conditions.
Prompt to try
I want to rename the Health variable on BP_Player. What references it, and what would break?

What the compiler adds

Compiling a Blueprint through Kismet returns structured errors and warnings, not only pass or fail. It also reports unreachable nodes: chains that are wired to each other but have no execution path from any event or function entry. A handler that never runs because nothing leads to it is a common cause of "nothing happens" bugs, and this catches it without running the game.

Limits to know

  • The agent reads C++. It does not edit it. C++ editing is on the roadmap. For now, apply C++ fixes yourself, or connect a coding agent such as Claude Code through Kismet’s MCP server and let it edit the source while Kismet handles the assets.
  • Source reading is bounded. Very large files are refused and long files are read in pages, so a deep trace through the engine takes several steps.
  • The log covers the current editor session.
  • The agent does not run or play your game. You reproduce the bug, it reads the result.
  • An explanation is a hypothesis until you check it. Read the cited lines before you accept a fix.

In the docs

Try it in your own project.

Kismet is free and open source. Install the plugin, connect a model, and ask for one small change.

Related guides