Yeah I guess I have to do that, couldn't get it to work the way I wanted.

alright

I want the boss to stop doing any functions when it is hit by a rocket

...

How do i share my game file lmao

Easiest way is probably getting a drop box account, save your project to your computer, transfer to drop box, enable sharing of that file in drop box, create a download link with drop box and post the link here.

Hi,

I've had some trouble with trigger once conditions. Let's say you have a main condition like Boolean = True, and a subconditions under it, some of what are supposed to trigger once while true and others that have other conditions. Do trigger once conditions work reliably in such subconditions or are you supposed to always use them in the main condition?

I have tested this in different situations and seem to get conflicting results, sometimes it seems the subcondition is run only once and other times not..or maybe I'm just setting the conditions wrong somehow.

Does anyone know what it the best practice regarding this issue?

A few things:

Do the objects need to be global for this to work if you place them in another layout?

Do you mean that if an object is referred to in an event it is loaded to memory in the start of the layout even if there is no instance of the object placed in the layout editor?

If you place every object type you need in the layout in the layout editor it is supposed to make the layout load faster.

Also you can store info in the initial objects' variables and effect parameters that the later created objects can use automatically. That is very useful.

I have set up a condition using the "create object by name" condition that every time when a normalmapped object is spawned from a normalmapped family creates the right normalmap for that object from the normalmaps family. I'm using one instance of all the normalmaps as a storage instance since the effect has tons of conditions and they differ for different objects.

However, I'm finding it a bit tricky to deal with the fact that I want to destroy the storage objects at the layout start so they won't get on the way. If I simply destroy them all at the start then the other normalmaps that automatically get created at the layout start (using the automated method I described previously) for my normalmapped objects get destroyed as well.

The best way I currently have to deal with it is having the initial storage items in a "destroy at start" family and placed in their own layer, and the storage objects of that family in that specific layer get destroyed at the start. It seems a bit crude.

Are there better methods for dealing with initial data storage objects? I know using data arrays is one solution, but I think it's actually more cumbersome overall than my current method.