How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix an Unreal Blueprint That Stays Dirty and Recompiles Every Launch

Q: What causes an Unreal Blueprint that stays dirty and recompiles on every launch?

A node depends on a struct, enum, or parent Blueprint whose layout changed without a recompile, so Unreal flags the Blueprint as out of date and rebuilds it each time the editor loads.

Quick answer: Force a full recompile of the dependency chain, save all assets, and use Fix Up Redirectors so the cached compiled data matches the current node graph and stops being marked dirty.

Every time you open the project, certain Blueprints show the orange “needs compile” badge and recompile, even though you changed nothing. Their cached state no longer matches their dependencies.

How to fix it

1. Recompile the dependency chain

Open and Full-Compile the parent Blueprint, any referenced struct or enum, then the child. Compiling children before parents leaves stale bytecode that re-dirties on load.

2. Save and fix redirectors

Save all assets after compiling, then right-click the content folder and Fix Up Redirectors in Folder so renamed dependencies do not force perpetual recompiles.

3. Clear derived data if needed

If it persists, close the editor and delete the project's DerivedDataCache so Unreal rebuilds the compiled Blueprint data from a clean state.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Unreal Engine error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.