What is wrong with this trigger ?

[operator]

Look at this trigger:

• Cargo Sorter Work
  • Events
    • Unit - A unit enters Rect 293 <gen>
  • Conditions
  • Actions
    • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
      • If - Conditions
        • (Owner of (Triggering unit)) Equal to (Owner of Job 0240 <gen>)
      • Then - Actions
        • Unit - Create 1 Cargo Sorter (Male) for (Owner of (Triggering unit)) at (Center of Rect 295 <gen>) facing Default building facing (270.0) degrees
        • Unit - Move (Triggering unit) instantly to (Center of Rect 285 <gen>)
        • Wait 2.00 game-time seconds
        • Unit - Hide (Triggering unit)
      • Else - Actions
        • Game - Display to (Player group((Owner of (Triggering unit)))) the text: |cffff0000Emplyes o...
        • Unit - Move (Triggering unit) instantly to (Center of Rect 284 <gen>)

Now, whenever a unit enters that region, the game crashes..Why ?

 

[1)ark_NiTe]

Bad sign, a game crashing is NEVER good and from what I can tell those triggers are fine. Remake each of the regions you used there and try again?

 

[SFilip]

Any other triggers we should know about? For example the ones that handle regions 295 and 285, 284.

 

[Mini-Me]

Infinite loops crash wc3. You havent posted the triggers that have to do with the regions in that trigger but Im guessing there is an infinite loop.

 

[Christers]

Perhaps add that the unit cannot be the unit that is created, or else that trigger will run when the new unit is created, making it infinite.

Christers

 

[operator]

Well, those rects has nothing to do with the matter really

 

[blackchoas]

I think it might have to do with the wait. Something must be triggered during this that is interferred because the wait causes the stuff after to be delayed. idk. but in my experiences wait's just cause crashes.

EDIT// does it happen EXACTLY when the unit enters. or does it pause, and then crash. where in the trigger does it run to before it crashes?

 

[Hemlock]

Just to be safe, make your first action

Trigger - Turn of (this trigger)

That will atleast prevent the trigger from being runned at again. try that and see if that solves your problem, turn it on after you are done with all the actions

 

[operator]

Never mind guy, I just redid the trigger from scratch, and now it works fine

Thank you for your help

 

[Hemlock]

Good to hear that =D.

Closed.