Something is missing...

[elwizprezley]

Ok guys im gonna try explaning as simple as possible and understandable
let says i am making a trigger

EVENT:
Unit enters a rect called <rect1 gen>
CONDITION:
Entering unit equals to a hero
ACTION:
Create 2 Footmans at <rect2 gen>

Now this working perfectly btw this is example it might be diffrent way sayings on real trigger making this is just example

NOW ----> I always either put Trigger turn off or trigger Turn On there is many more like destroy trigger blah blah BUT how do i reset the trigger so it goes from the top again?

 

[dansaDisco]

Uu, you wouldn't have to do anything as far as I know?

A trigger should run every time the event is happening, unless it's turned off.

 

[ap0calypse]

• Your trigger
• Events
  • Unit enters a rect called <rect1 gen>
• Conditions:
  • Entering unit equals to a hero
• Actions:
  • set TempLoc = Center of <rect2 gen>
  • Unit - Create 2 Footman at TempLoc
  • Custom Script: call RemoveLocation(udg_TempLoc)

Notes:

• You do not need to reset the trigger, it activates when a unit enters rect 1
• The trigger I have given will not leak and therefore won't cause any lag
• The custom script is case sensitive!

If you've got any further questions, feel free to ask.

 

[Amigurumi]

maybe this:

• Actions
  • Trigger - Run (This Trigger) ignoring conditions

and this trigger is over the whole time <On> and runs every time a unit enters yourrect, until you make

• Actions
  • Trigger - Turn off (This Trigger)
• OR
  • call DestroyTrigger(GetTriggeringTrigger())

 

[dansaDisco]

maybe this:

• Actions
  • Trigger - Run (This Trigger) ignoring conditions

Unless he wants to run the trigger until the whole map crashes in lagging, no way.

That runs the trigger, no matter what the events are, and if it ignores conditions as well, then.. guess what!

and yeah, you shall NEVER destroy a trigger. NEVER, EVER.

 

[Amigurumi]

I know, Run the same trigger ignoring conditions will immediatly close warcraft without any error message. But you can use it in an other trigger
Map initialisation triggers should be destroyed as far as I know

 

[dansaDisco]

If that's what you mean, that he should use it in another trigger, then please say that. But I see no reason to use that, at all.

Triggers still run even after all the actions are done, and if you remove a trigger while it's thread is still running, you should end up with a handle stack corruption.
Sound good?

You never need to reset a trigger.
The trigger ap0calypse posted works just fine.

 

[ap0calypse]

maybe this:

• Actions
  • Trigger - Run (This Trigger) ignoring conditions

and this trigger is over the whole time <On> and runs every time a unit enters yourrect, until you make

• Actions
  • Trigger - Turn off (This Trigger)
• OR
  • call DestroyTrigger(GetTriggeringTrigger())

this would almost be a fine solution, I can see what you were thinking, but:

• Destroying triggers is not recommended (not in this case, where he uses the event "unit enters a region").
• This will result in an enormous, infinite loop which creates 1 unit without a wait (real wait / timer wait / normal wait or whatever).
  If you create units at that rate and turn the trigger off after a few seconds, an incredible amount of units have been spawned

It was worth the try, though but for it to work you would have to add a little wait before running the trigger again.

 

[Amigurumi]

I just want to show him, what solutions exist
and destroy trigger is only for triggers, where you don't need them anymore, ofc