Why does a disconnected "Parent: Construction Script" run anyway?
I'm following the Endless Runner tutorial for my first project (https://www.youtube.com/watch?v=E8D3TMvrYiM). 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?
asked Jun 19 '18 at 03:33 AM in Blueprint Scripting
Follow this question
Once you sign in you will be able to subscribe for any updates here