Staredit Network

This is kind of a simple idea, and im not sure if anyone has thought of this (probably have) but you can make hypper triggers owned to a force that doesn't have any players in it!
Lets say 'Force 1' has 6 players and 'Force 2' has 2 players, all the players are used up. So when you make your hypper triggers, assign them to a Force that isn't being used, such as 'Force 3'. They will still work and every player (including all the computer players) will benifit
This is pretty handy.

I don't know about others but i already knew this. I never bothered posting because it's not very useful. It's just putting your hypers in a different area.. you could still have them at the bottom of the force2 triggers.

Just know that hypers are most succesful nehind all other triggers, so if they come before certain triggers, they mess up waits.

Ya, i thought some people would have figured this out. but its a useful way to put your HT's somewhere else; out of the way of everything

yes that is true triggamaster. i made a map with hyper triggers. you must put anykind of hyper triggers at the bottom of the trigger list or else things will freeze or make a glitch or crash things. you can hyper trigger health to make the wireframes jump and you an make the controller of the unit or building or etc to make it rainbow color, or you can make things spawn faster for faster game play.

StarForge can't do that so it is ing me up and i want hyper triggers
The hyper trigger with switchs need two players, and if you want the map to be played with 1player, or just imagine if the 2 players change place from player1 & 2 to player 3 & 4 , your hyper triggers are in the void, and i don't want to write p1 & 2 required and i know if a computer is in the same force as players, they can't move, but if i want a 8players map, playble with only 1 player, it's dead, so thanks l)ark_13 if your concept work !!! Because i don't want to use SCXE anymore ! (to move down HT)

Wow this would work if it weren't for one minor flaw!

Only players that exist can run triggers. If you run a trigger for a force with no players in it, then the triggers won't run because nobody owns them. Players 9+ cannot run triggers because as chu said,
"Players who don't need a start location and be set as active and units still appear when preplaced, cannot run triggers."

Want proof? Test it. Obviously the creator of this thread did not.

i dont use hypa triggaz all together... to risky... i think itll just ruin my map...

If you are careful and test often, they can work; but they will mess up other waits sometimes. Have them owned by a player with no waits in their other triggers, and if they mess up some other triggers still, set the hyper triggers to switches, and turn them off during the time they mess things up, if it wouldn't stop other things from happening. You can get around that though by being careful of order of your actions and triggers.

That doesn't really work, your hyper triggers can take a very long to 'turn off' once they are activated. Your better making it owned by a player with no waits like you said. It can't mess up if you do that, unless you consider the triggers running faster an error. Or you might make a mistake and think 'all players' isn't player 8 or something similer.

My mistake. Is there a useable formula for how long it would take for the effect of the hyper triggers to wear off? Such as each of the Hyper Trigger waits to an action or time the triggers are run down the list? or is it pretty much impossible to incorporate it to stop when you want it to.

It would vary depending on how far 'into' the hyper trigger it is. If i had to guess the normal 3 trigger hyper trigger would take about 15 seconds to stop if you just started it.

Does anyone use this type of hypertrigger? (the ones i'm talking about are at the very bottom of the tutorial)
The tutorial also explains that it takes (63^3)*84 milliseconds for a 3 trigger hypertrigger block to run through completely - that is, 5.8 hours from start to finish, before looping.

The tutorial itself is tough to understand, but the hypertrigger system works and only uses 3 wait actions in total! So if you wanted to stop it, it would probably stop much faster than the traditional hypertrigger block.

Personally, when I use hypertriggers, I avoid the use of the wait action altogether in the rest of my triggers (because same player wait actions still interfere with each other). Instead, I'll probably use a death counter to time actions instead.

ADDITION: actually, come to think of it, if you put a switch condition on your 3 hypertrigger block, and you flipped the switch to turn it off, it would probably stop very quickly (within a few seconds). This is because hypers work off the fact that wait actions run the other triggers, and the next hypertrigger requires the condition of the switch, a condition which is now false. So at most 62 more 'hypercycles' will occur after you flip the switch. That makes 62*84 milliseconds = 5.2 seconds.
By the way, if you didn't know already, 84 milliseconds is the minimum time that SC can wait for (i.e. if you have an action "wait 0 milliseconds", it will actually wait for 84 milliseconds. All wait amounts are rounded up to the next multiple of 84 milliseconds.)

limp, it would do that for each of the triggers. They all have to finish off there waits and only one can fire at a time. Thats why i said 15 seconds, As a rule of thumb the less waits you have the quicker your hyper trigger will stop. but the draw back is it won't last as long when it is going.

Dabbu's method that you mentioned would turn off almost instantly however. But theres really no point to turning hyper triggers off.

I've tested in by using it in a lot of maps I make. Don't think I would make a topic that made no sense and was useless. Someone else uses it too if you read.

Im also surprised that this topic is still on the front page

Weird, I'm 100% sure it doesn't work due to testing this map: