Parent Child Help please

[Nicholas Martin]

I have been learning to better optimize my eventing and do things in simpler ways. I used to use many events to get enemy health bars above and to be destroyed when fighting an enemy. Using the parent child feature I have simplified this except... Probably super simple to do.. When I destroy the parent object and the health bars, every health bar instance gets destroyed. Maybe I am just not understanding the proper was to use parent/child. Any help would be great. Look at attached example.

[Nicholas Martin]

Well I solved my own problem. I didn't know you simply had to destroy the parent to destroy the child objects. Funny how you think you know everything and yet you don't even know some of the simplest features of Fusion Anyways here is a completed example.

This uses actives instead of counters and it will work with any number of instances of enemy objects.

Each health bar has a container.

Enemies use a group qualifier.

Uses enemies max health vs current health to decide the percentage of the health counter filled.

I hope this example helps some of our new clickers.

[wpd]

cool, I didn't know it could be this easy... no loops and all

[Nicholas Martin]

Glad you found it helpful I was just researching some techniques on how to simplify things.

[BartekB]

You're not actually destroying the health bars of the destroyed parents, they are just out of frame so they aren't visible, look at the debugger and see how one object is destroyed when you destroy a parent.
I might mess around with this to see if this can be fixed.

[Nicholas Martin]

Actually... Watching in the debugger it is not actually destroying the health actives so this is not yet resolved. Anyone have an idea how to destroy the health actives without the use of loops? Trying to keep it as simple as possible.

[Nicholas Martin]

Thanks I had just noticed that myself

[BartekB]

I hope Fusion 3 gets a better parenting feature, like folders and items inside it. A parent is a folder which can contain objects, which can also have items inside. If you clone or create the first parent, the children will get cloned / created with it. Similar to what Roblox does with its objects:


Roblox also has a feature for things to call their Parent to get their variables, like x and y and other things, which require no loops.

Using a for each loop to attach objects to other objects for it to feel like a parent / child behaviour, is just a workaround for something Fusion doesn't have built in.

[schrodinger]

^ definitely, +1 for parent/childs in F3 (I think I read something like that in the AMA though!)

You can simply store some reference to health bars in the parent,
and then filter those right before destroying:

enemy health bars_paired.mfa

[Nicholas Martin]

Awesome that works perfectly! Thanks dudes