Error during cooking. To the rescue. "Custom Property List Not Initialized"

I found a solution!!!

At first, simply renaming or reparenting didn’t fix the error. The real solution came when I focused on removing as many direct references as possible from the blueprint.
Here’s what was happening:

  • MyComponent had a reference that kicked off a cooking process for another blueprint.
  • That blueprint had its own references, which eventually triggered cooking for MyComponent again. A circular reference.
  • This created a long dependency chain.

If this chain gets too long or messy, the cooking process can’t always resolve it in the correct order, and it fails. Probably because one of the assets wasn’t ready or “cooked” in time.

To fix it:

  • I removed some direct references in MyComponent.
  • I replaced them with blueprint interfaces.
  • I used the Reference Viewer to confirm the links were fully gone.

The error message in the editor includes this line:

if (GBlueprintNativePropertyInitFastPathDisabled
    || !ensureMsgf(bCustomPropertyListForPostConstructionInitialized, TEXT("Custom Property List Not Initialized for %s"), *GetPathNameSafe(this))) // Something went wrong, probably a race condition
{

So… is this truly a race condition? Or is it just bad blueprint dependency management that looks like a race?

1 Like