[Trigger] Triggers aborting in game

[HarblMan]

EDIT: FIXED. It seems like it is auto-cleaning up some locations, so the location I am trying to spawn the unit in the example below is non-existant. I changed it to spawn at TempPoint2 and it worked. It seems to me like under some conditions, it will clean up locations. Not sure exactly what those conditions are yet.

The following is the original post:

I recently cleaned up a bunch of memory leaks, and a bunch of my triggers stopped working properly. All of them were either using a loop or recursive triggers and they always abort after the first thing they do...

Here's an example:

What happens is, it does this trigger once, but it seems like it fails to create the unit that would cause the trigger to fire again. There are a few other triggers that go with this, but they are working properly. This only stopped working after I fixed the location leaks.

It seems to me like removing a location that I just "instantly" moved a unit to will cause the trigger to abort. Why is this, and how can I fix it without leaving a memory leak in?

 

[Avator]

You need to set PusherAngle somewhere. Also use the

• tags to post triggers properly here. Use 'Copy as Text' in the Trigger Editor and past it between the trigger tags.

 

[HarblMan]

You need to set PusherAngle somewhere. Also use the

• tags to post triggers properly here. Use 'Copy as Text' in the Trigger Editor and past it between the trigger tags.[/QUOTE]
• I did set it, in another trigger that executes before this one. Even if I didn't, it would default to 0.0 and my unit would be moved towards the same angle no matter what.
• The problem is that it only moves once, and the trigger aborts.

 

[Soga-]

Are you SURE the custom value of that unit is 1?

 

[Vegavak]

Are you SURE the custom value of that unit is 1?

This.

 

[HarblMan]

Yes, I double checked the custom value, the variables, etc...

Fact is, this all worked until I fixed the location leaks.