ActorComponents with the EditableWhenInherited property set to false will be stripped out of inherited BPs at cook time

Development Platform & Builds
, ,
1

While updating our engine from 5.4 to 5.5, I have noticed that that ActorComponents with the EditableWhenInherited property set to false will be now stripped out of inherited BPs at cook time. This manifests for us as the following error during cooking:

LogInit: Display: LogCook: Error: Content is missing from cook. Source package referenced an object in target package but the object was stripped out of the target package when saved.

[7/24/2025 4:41:39 PM] uat> Source package: /S1_Specializations/Gameplay/Specializations/NaturesEmbrace/Spells/EntanglingRoots/Item/Item_Spell_EntanglingRoots

[7/24/2025 4:41:39 PM] uat> Target package: /Game/Gameplay/Inventory/Item/Spell/Item_Spell_Base

[7/24/2025 4:41:39 PM] uat> Referenced object: /Game/Gameplay/Inventory/Item/Spell/Item_Spell_Base.Item_Spell_Base_C:Comp_Item_ApplyItemTags_GEN_VARIABLE

I haven’t yet dug further into why this component appears to be stripped out of the build. I can investigate further if necessary but I wanted to start by asking if this is a known and/or resolved issue?

2

Steps to Reproduce
*I have not yet tried to reproduce this in a small test project; there might be more nuance to this. Sorry!

  1. Create a new Blueprint Actor
  2. Set the DefaultSceneRoot bEditableWhenInherited property to false.
  3. Create a second actor that inherits from the first.
  4. Place the second actor in a level.
  5. Cook a build containing that level.
3

Hello [mention removed]​

Thank you for reaching out and bringing this issue to our attention.

I’ve tried to reproduce this behavior in a repro project, but no error was logged.

Some details might be missing.

It would be great if you could provide a stripped-down project that reproduces this behavior, but if that’s not possible, could you elaborate more on the specifics of your setup, so I can try to reproduce it on my end?

I hope to hear from you soon.

All the best,

[mention removed]​

4

Thanks for taking a look! I’m quite busy this week but I should have more time next week to try to set up a smaller repro and/or potentially dig further.

5

Hello [mention removed]​

No worries, we can continue when you have the time.

All the best,

[mention removed]​