Using Parent-Child relation instead of creating new objects

[sh4itan]

Hey there,

just wanted to ask if it wouldn’t be more in scope with the course to use oBat as parent for oBatHard, instead of creating a new object? Might not be a big problem for small enemies, but with more complex Events is would be easier to make changes if both are of the same logic and just differ in the create event setup?

We already did the c/p route from bat to slime, I think having parent-child relations explained might be a benefit for the course?

Cheers!

[Marc_Carlyon]

In our case as we are only making one variant of the bat then the logic is fine to have them decoupled like this but if we were making multiple variants it would be better to have the parent and child relationship to have the logic coupled so that the changes propagate and can be overridden if needed.