Staredit Network

If you put all of your hyper triggers below all of your other triggers, any trigger with wait actions will work normally. I think triggers that are at the top of the list of in each player's menu are given higher priority over those below. What I do with my hyper triggers is as follow:


All other triggers above--^

Hyper Trigger (x10)
CONDITION
Switch "Hyper Triggers On" is set.

ACTION
Wait "0" milliseconds. (x20)
Preserve trigger.
Comment: Hyper Trigger


So this means that there are 10 hyper triggers below all of your other triggers in a player's slot. Each hyper trigger has 20 'Wait "0" milliseconds.' actions. Again, this makes all triggers with wait actions work NORMALLY if hyper triggers are BELOW all the other triggers. A new set of 10 hyper triggers must be made for each player's slot that requires them.

WARNING:
- 'Wait "0" milliseconds.' is equivelant to 'Wait "1" millisecond.'
- It is hazardous to execute two large wait triggers at the same time.

This may be your problem with waits and hyper triggers. Using this method could quite easily fix your dilemmas with waits and hyper triggers.

---------------------------------------------------

Here's the explanation if you want to read it:

Hyper triggers make normal triggers work about 12 times as fast. When a wait command is initiated, it exits the current trigger to check if any conditions can be met within other triggers for however long you told the wait action to wait for. That is how hyper triggers work. They repeat many times per second to check if conditions can be met. If a trigger is above the hyper triggers, like I mentioned above, it will check if anything can be done during mid-trigger. Therefore once the time has elapsed that it must wait to continue the trigger, it can simply continue without interuption. If the hyper triggers were above all the other triggers, they'd do the same thing because they triggers below would not have the higher priority (assuming they have waits in them). The hyper triggers would have to repeat many times before waits below it could be completed.

---------------------------------------------------

ADDITION:
Hmm... I posted this topic twice by accident. Sorry about that. This is the good version.

http://www.staredit.net/index.php?act=tuto...yper%20Triggers
http://www.staredit.net/index.php?act=tuto...r%20Triggers%20[Conceptual]

SEN already has tutorials on nearly everything,
You did a nice job except

[quote= It is hazardous to execute two wait triggers above 1 millisecond at the same time.[/quote]
StarCraft would have rounded it up to the amount of time a frame takes, so it's really just having lots of waits of any kind being stacked, no matter the time.

Well then, here's another explanation by me.
Fixed the error you mentioned.

So you can use wait 1 millisecond instead of wait 0 millisecond as they both get you the same result? Just getting clarification before I play with hyper triggers on the next map I get around to finishing .

I just fill up the whole trigger with waits, I think its 63 + 1 preserve, and then just copy it 3 times. Which is what it says to do in the tutorial

Yea I read the tutorial, it said wait 0 but I've seen people use wait 1's before so I just wondered if it totally doesn't matter which one you use. And you only want it above the triggers your going to use as hyper with all the non-hyper triggers above your hyper triggers. Still seems kinda wierd you leave all those waits all alone... oh yea having them there means all your triggers below don't need any wait commands right?

All triggers are affected by hyper triggers.
Waiting 1 and waiting 0 are the same thing if you read the conceptual hyper trigger tutorial.
Putting triggers above the hypers is the same thing as below the hypers unless they have waits.
You should always put triggers with waits above the hypers.

Exactly. The point is to have the hyper triggers below everything else. Better organization if you don't care about mixing waits and non-waits. Which is unorganized...

Ah thanks, I've got it now. Nice to have clarification .

So much information is wrong and/or extreamly missleading I don't know where to start.

Try locking the topic?

Try pretending your not the Mod.

I was just making a suggestion. You "didn't know where to begin".

I'll make this easier for both of you.

» Topic Locked