Weird error related to non-component subobjects in inherited blueprints.

It seems to still have the same issue. It looks like it is only an issue when you start trying to inherit things from the class you’ve added them to. I’m wondering if this might just be a weird case that might not be tested because it doesn’t happen often enough as you’d usually be sticking those things in a component, which seems to not trigger any of these checks.

Digging a bit more, what seems to be happening is that the base class (In my project MyCharacter) creates a default class object at compile time with its default sub object (TestSubObject in the project), and then when you try to inherit from it the Subclass of MyCharacter that you create uses the reference in the MyCharacter default object’s TestSubObject instead of its own.

Don’t have a huge amount of time to keep looking right now, but I’ll poke around some more when I get some free time and see if I can figure out why it’s referring to it’s parent CDO instead of its own. If I had to guess it’s some kind of optimization to reuse CDOs, but then the component checker probably just has to test against this case also.