Hi all, I'm new here but I've been lurking around these forums for about 2 months now. I need some help and believe me I looked at all other available options but I'm at a lost here.

I'm creating a map that requires hyper triggers. The problem is all of the players currently use wait actions. I was reading the wiki and I found out I can use death counters to well counter this conundrum. When I looked at the death counters wiki I was confused and lost.

The question I am asking is what is a way to use hyper triggers on a player with wait actions, and if I have to use death counters can someone give me a clear step by step? I would be extremely grateful.

Many thanks.

First of all you should replace waits with death counters. They don't produce wait blocks and are independent from speed (important in single player). If you manage to get rid of the waits for one player then you can use method a) described below.

Setting up hyper triggers is very easy: Create a trigger that has a preserve, maybe a comment and the rest of the actions (max. 64) only waits. Then copy this trigger 2-3 times. And that's all, your hypers are ready to go.

Now there are several methods how to avoid wait blocks:
a) Place the hypers under one player that has no other waits

b) Place the hypers under all players and put them at the bottom of the trigger list, which is automatically done if you create them last. This method only creates wait blocks if all players are executing a wait the same time.

c) Uses other triggers (switch hypers) spread among 2 players. These players also should not execute other waits, BUT the wait block is very short (usually negligible). The hypers are simply turned off while the wait is running (regular 2s trigger checks). You can also add another switch into both hyper's condition to switch them off manually. This will happen instantly as opposed to regular hypers which will need a minute or so to turn off.

Yes, the wiki tends to be confusing when people start mapping, one reason why I wrote my own tutorials, here's the tutorials on Death Counts and Hyper Triggers. Those are much simpler than the other tutorials, although there is still advanced information in them, if you don't understand something, just ignore it, you'll still get the general concept.

Lol I already linked hom to your death counters tutorial, just that here on SEN it has a nice introductionary sentence.
Also you should update your hyper trigger tutorial to explain how to use hypers under all players instead of calling it a bad idea.
But thx for removing the background.

I already say something about that:

But I definitely need to go a little more thorough into it, since when I made it I just knew that you could stop the blocks, I thought it had a slight delay before stopping though.

I just need some conformation. I want all players to have hyper triggers but you said I need to get rid of the waits using death counters. Right now I have this


What would I need to do?

Having hyper triggers for only one (any) player remaining in the game is enough. Triggers would execute faster for all players even if hyper triggers are placed only for one of them.

I have a question to you, why do you put the action Kill Unit("Player 1", "Terran Firebat") under the condition Command("Current Player", "Terran Firebat", Exactly, 0)? Player 1 always owns exactly 0 firebats when the condition is met.

You can make a wait using death counter ("Rhynadon" unit, I suppose it cannot be killed in your map) like this:


I will explain the expression round(1500/84)+1 (SCMD dont allow expressions so you should manually calculate it).
Hypper triggers cicles repeat every 84ms. +1 is because you execute your action (Set Switch("Red4thLife", set)) when the counter is 1, but not 0. This is made to make your first two triggers reuseable. This means that setting deaths of Rhynadon to some (probably other) value in another trigger will automatically start the timer which would execute the Set Switch("Red4thLife", set) action every time it reaches 1.

Post has been edited 1 time(s), last time on Apr 23 2008, 9:12 pm by Wormer.

You can also make the hypertriggers under All Players, and then make sure it is at the bottom of the trigger list, in that case, your waits will all run normally, but they will temporarily shut off the hypers for that player until they are done, putting it under All Players insures that only if every single player present in the game executes a wait at the same time(Or a wait under All Players) will the hypertriggers actually stop running.