this trigger causes server splits

SPAWN_WAIT_TIME is .5 seconds

spiders
Events
Time - Elapsed game time is 40.00 seconds
Unit - A unit enters Region 097 <gen>
Conditions
Actions
Custom script: call DestroyTrigger(GetTriggeringTrigger())
Set ang = 0.00
Set r = Region 074 <gen>
Set ut = Brood Mother
Unit - Create 1 ut for Neutral Hostile at (Random point in r) facing ang degrees
Unit Group - Add (Last created unit) to spiderxpgroup
Set witchmonsters[2] = (Last created unit)
Wait SPAWN_WAIT_TIME game-time seconds
Set ang = 20.00
Set r = Region 073 <gen>
Set ut = Giant Spider
Unit - Create 1 ut for Neutral Hostile at (Random point in r) facing ang degrees
Unit Group - Add (Last created unit) to spiderxpgroup
Wait SPAWN_WAIT_TIME game-time seconds
Set ang = 0.00
Set r = Region 074 <gen>
Set ut = Spitting Spider
Unit - Create 1 ut for Neutral Hostile at (Random point in r) facing ang degrees
Unit Group - Add (Last created unit) to spiderxpgroup
Wait SPAWN_WAIT_TIME game-time seconds
Set ang = 0.00
Set r = Region 074 <gen>
Set ut = Spitting Spider
Unit - Create 1 ut for Neutral Hostile at (Random point in r) facing ang degrees
Unit Group - Add (Last created unit) to spiderxpgroup
Wait SPAWN_WAIT_TIME game-time seconds
Set ang = 0.00
Set r = Region 075 <gen>
Set ut = Brood Mother
Unit - Create 1 ut for Neutral Hostile at (Random point in r) facing ang degrees
Unit Group - Add (Last created unit) to spiderxpgroup
Wait SPAWN_WAIT_TIME game-time seconds
Set ang = 0.00
Set r = Region 075 <gen>
Set ut = Spitting Spider
Unit - Create 1 ut for Neutral Hostile at (Random point in r) facing ang degrees
Unit Group - Add (Last created unit) to spiderxpgroup
Trigger - Add to spider xp <gen> the event (Unit - A unit owned by Neutral Hostile Dies)

That trigger could be shortened a lot, ya know.

i set the variables over and over cause of the waits (they're global...). i use waits cause i thought they might help it not server split.

Probably the creeps themselves are causing the splits because of their high hit points?

I dunno how destroy trigger works, but calling it and then running the rest of the trigger could cause a problem, I haven't tested it nor do I know how war3 destroys triggers...

nah that's not the problem, i do that on half my triggers.

destroying it does just that. gets it totally out of memory i think/hope. or at least makes it do nothing. but if any copies of the trigger are currently executing destroy doesn't effect them.

Oh, okay, so it's not like C++