Why does a disconnected "Parent: Construction Script" run anyway?

I’m following the Endless Runner tutorial for my first project (Endless Runner: Turning Corners | 06 | v4.7 Tutorial Series | Unreal Engine - YouTube). That tutorial was written for 4.7 but I’m running 4.19

I’m creating the FloorTile_RightCorner component, which inherits from FloorTile. The instructor goes into the Construction Script and disconnects “Construction Script” from “Parent: Construction Script”, and that causes the coins and blocker to stop spawning. When I disconnect those nodes in the FloorTile_RightCorner script, it seems that that has no effect, and the parent construction script still fires and spawns the coins and blockers.

However, if I manually connect the “Construction Script” node to ANYTHING else (for example “Execute Console Command” with no command string) then the blueprint seems to ‘notice’ that it’s not connected to the Parent: Construction Script and correctly never spawns coins/blockers.

Of course, I don’t want to have to run an empty command to prevent running the parent script. I thought simply disconnecting them would be enough. What’s going on here? Why does the Parent: Construction Script fire despite not being connected in my Construction Script?

Thanks,

Devon

have you found the answer to this? I have the same issue in 4.20

There is a comment under that video with some solutions Endless Runner: Turning Corners | 06 | v4.7 Tutorial Series | Unreal Engine - YouTube

I prefer this method: “… To fix the issue, I delete the Parent Construction Script call, and put a dummy Action (I think I put a Compare Int, 0 with 0). This fixed the issue. Seems that the engine thinks that not having anything NEW in the Construction Script will automatically call the Parent, even if it’s not linked O_O” (Endless Runner: Turning Corners | 06 | v4.7 Tutorial Series | Unreal Engine - YouTube)