When Ubi released for the first time the script tools, i remember that while testing this spawn/unspawn function, trying the word "alpha" with the letters, each time it would spawn properly but after, via delay, when trying to trigger with the unspawn script, one "a" of the word alpha will still be there.Originally Posted by Steve64b Go to original post
So yeah, duplicate objects are an issue, even when you choose them from the library twice, (no copy) (id objects seems messed up at this point for some scripts)
I seem to have noticed that too in my Evil Dead map. Turns out a copy of the object was made in the map when I linked the object to a script action. I think this happens when you deal with objects that are already linked to some (other) scripts. Sometimes the editor loses track of which object(s) you mean, and maybe decides to throw in a copy of the object you're referring to for it to make sense.Originally Posted by FlyingSpiritus Go to original post
Technically each trigger can only be triggered once. Aside from that, this one shot already _always_ works.
It's the script execution that is the problem; scripts can't execute in parallel, so it's one after another. Plus new AI won't spawn until less than 12 AI are active in the map. And finally, Trigger Event triggers execute prematurely when tied to multiple copies of the same asset that were spawned from the same script.
You can simulate randomness by having 2 animals in a death pit fighting it out. Each one's kill event triggering a different script.
But yeah, ideally we shouldn't have to workaround things by using such exploits. I'm even resorting to unspawning scripts to prevent them from running sometimes. No clue what that does to the engine, but in gameplay it seems to work.