A simple trigger crashes warcraft

[feelingparty]

Can anyone tell me why does wc crash when i use this:

• ResourseLumber
  • Events
    • Unit - A unit Is issued an order targeting an object
  • Conditions
    • (Destructible-type of (Target destructible of issued order)) Equal to Summer Tree Wall
  • Actions
    • Unit - Order (Ordered unit) to Attack (Target destructible of issued order)

 

[laxperson808]

Is the unit able to atted destructibles?

 

[feelingparty]

Yes he is a peasant.

 

[laxperson808]

Peasnts cant att trees.. if you look at there combat targets destructibls/debris arnt check.. if u want them 2 harvest try this

• Unit - Order (Target unit of issued order) to Harvest (Target destructible of issued order)

 

[feelingparty]

No I don't want it to harvest. And no I have debris checked and the peasant originally has it checked. Combat Attack 1 - Units allowed - Ground, Structure, Debris, Item, Ward

 

[laxperson808]

Mabye you should also check the thing called tree

 

[Weep]

Can anyone tell me why does wc crash when i use this:

Infinite loop: the trigger runs when a unit is given an order targeting a destructable, and you are giving the unit such an order in the actions, causing the trigger to run itself over and over, freezing WC3.

You could either filter out the "attack" order in your conditions, or you could turn the trigger off before giving the order and on again afterward.

 

[laxperson808]

Well see i wonder about an infinate loop.. becuase when i have
Unit enters region (x)
move unit to region (y)

Unit enters region (y)
move unit to region (x)

It creates a loop were unit keeps moving back and forth but that doesnt cuase game 2 crash?

 

[roaaaarrrr]

Well in that example there is a delay. The next command isnt executed until you have finished the first. i.e. Your unit wont be ordered to go back to region x until he has left region y.

But in the first it is just a constant loop. A unit attacks, and this causes it to be ordered to attack, which causes it to be ordered to attack, which causes it to be ordered to attack, which causes it to be ordered to attack (you get the point). So once this happens enough the game crashes.

Also, this trigger seems absolutely pointless...

 

[Bird]

Weep is correct. This is an infinite loop.

If you tell us what the trigger is supposed to accomplish, then we can help you make it *not* be an infinite loop.

 

[feelingparty]

I figured this one from what Weep said but something was wrong with my internet and i couldn't post. Anyway thanx and sorry for the obvious question.