Weirdest bug: Component set to null after constructor completes

[LXFrontier]

@Slayemin

Update:
I seem to have found a fix. Right click on your offending blueprint, go to “Asset Actions”, and then “Reload”.

make sure you save everything else before you do this because the reload will cause dependencies to reload themselves as well, which has a chance of having unchecked null references which cause an editor shutdown.

Update 2:
Oh wait, no, the above update is hit and miss.

Duplicate the blueprint and replace the old one with the duplicated one. Doing stuff in the constructor after you created a bp child of it sometimes causes problems.