ok so have been making a few Random Defenses ( eg.individual random def.) and when I try to have the chooser to create the random unit to go in the location, it takes a few seconds to read the trigger. I am using Scmdraft 2.0 and everything works but I cant get the "Steps" to be read in milliseconds instead of seconds. How do I change this? :dontgetit:

ok so have been making a few Random Defenses ( eg.individual random def.) and when I try to have the chooser to create the random unit to go in the location, it takes a few seconds to read the trigger. I am using Scmdraft 2.0 and everything works but I cant get the "Steps" to be read in milliseconds instead of seconds. How do I change this?

Do you have hyper triggers? And waits are always in milliseconds. Just put 1000 for every second. But shouldn't it be 100? On timer's and stuff it's always 100 ms to one second.

Do you have hyper triggers? And waits are always in milliseconds. Just put 1000 for every second. But shouldn't it be 100? On timer's and stuff it's always 100 ms to one second.

I've never heard of hyper triggers? How do you use them?

I've never heard of hyper triggers? How do you use them?

you know, they make triggers go faster [where have u been?] Condition Always Action Wait 0 milleseconds x 63 [you need 63 of these to fill up the trigger, the last slot is to repeat] preseve trigger Create 3-5 of these

you know, they make triggers go faster [where have u been?]

Condition
Always
Action
Wait 0 milleseconds x 63 [you need 63 of these to fill up the trigger, the last slot is to repeat]
preseve trigger

Create 3-5 of these

You might want to make 62 waits so you can save 2 for preserve and a comment.

You might want to make 62 waits so you can save 2 for preserve and a comment.

[quote=name:blacklight28]Do you have hyper triggers? And waits are always in milliseconds. Just put 1000 for every second. But shouldn't it be 100? On timer's and stuff it's always 100 ms to one second.[/quote] Well then your timers are incorrect. It's based off the correct metric system. Milli<Cent<Deci<Second<Deka<Hecto<Kilo Each using a x10 of the last. Milli being 1/1000 of a second.

Quote from blacklight28

Do you have hyper triggers? And waits are always in milliseconds. Just put 1000 for every second. But shouldn't it be 100? On timer's and stuff it's always 100 ms to one second.

Well then your timers are incorrect. It's based off the correct metric system.
Milli<Cent<Deci<Second<Deka<Hecto<Kilo
Each using a x10 of the last. Milli being 1/1000 of a second.

[quote=blacklight]You might want to make 62 waits so you can save 2 for preserve and a comment.[/quote] It can be both, either 63 waits or 62... its what he would want

Quote from blacklight

You might want to make 62 waits so you can save 2 for preserve and a comment.

It can be both, either 63 waits or 62... its what he would want

Lol, I grew up knowing centiseconds as milliseconds...

Lol, I grew up knowing centiseconds as milliseconds...

w8 so ive i have a trigger that says: Condition: if Player1 brings 1 any unit to location 0 Action: Create 1 Terran Marine at location 1 kill all any unit owned by Player1 at location 0 (then the waits 61 of them?) Preserve Trigger

w8 so ive i have a trigger that says:
Condition:
if Player1 brings 1 any unit to location 0
Action:
Create 1 Terran Marine at location 1
kill all any unit owned by Player1 at location 0
(then the waits 61 of them?)
Preserve Trigger

No, make seperate triggers for hyper triggers. Hyper triggers sould be their own triggers.

No, make seperate triggers for hyper triggers. Hyper triggers sould be their own triggers.

No, make a seperate trigger for hypers

No, make a seperate trigger for hypers

k does it matter if they r owned by any player?

k does it matter if they r owned by any player?

they have to be owned by someone... like Player 8 [if he is a comp] or i think u can have it as a human or neutral

they have to be owned by someone... like Player 8 [if he is a comp] or i think u can have it as a human or neutral

[color=#1af]Allow me to explain. Hyper triggers function as their own unit, and for whatever reason (I'm sure someone around here knows) they make triggers run approximately 12.2 times more often (I believe, again I'm sure someone around here knows the exact numbers). With hyper triggers you rarely have to wait for anything to occur, unless you specify it. Be careful with wait blocks though, these occur when more than one wait is running at the same time for the same player. You'll want to invest some time into learning about using death counts as timers to avoid wait blocks. Hope I helped. Edit: Player does not matter, but the player has to be in the game so the triggers can run. I'd suggest using a computer player for them.[/color]

Allow me to explain. Hyper triggers function as their own unit, and for whatever reason (I'm sure someone around here knows) they make triggers run approximately 12.2 times more often (I believe, again I'm sure someone around here knows the exact numbers). With hyper triggers you rarely have to wait for anything to occur, unless you specify it. Be careful with wait blocks though, these occur when more than one wait is running at the same time for the same player. You'll want to invest some time into learning about using death counts as timers to avoid wait blocks. Hope I helped.

Edit: Player does not matter, but the player has to be in the game so the triggers can run. I'd suggest using a computer player for them.

I just use all players, all my random triggers and things like hyper triggers go into all players.

I just use all players, all my random triggers and things like hyper triggers go into all players.

http://www.staredit.net/wiki/Wait_Blocks If you didn't know how hyper triggers worked you might need to know about that also.

http://www.staredit.net/wiki/Wait_Blocks

If you didn't know how hyper triggers worked you might need to know about that also.

http://www.staredit.net/wiki/hyper_triggers Every time there is a wait, it causes all other triggers to run immediately. The first hyper trigger runs immediately, waits 0, then goes on to the next hyper trigger, which then waits 0. It then goes back to the first hyper trigger and waits the first wait again. tl;dr it makes ur trigs run faster just cuz. Triggers normally run once every 2 seconds on normal because there is a delay in between each trigger run. This can't really be avoided, but it can be pushed away (4 hypers pushes this into days inbetween NEOs). Hyper Triggers essentially prevent this delay from ever happening, making them run every 84 ms on fastest until the "NEO", which is calculated based off of the number of waits in your triggers. This should be explained in the wiki. With hyper triggers, the triggers run eight times a game second, which means 16 times faster than normal speed. That's about it. Read the wiki for more.

http://www.staredit.net/wiki/hyper_triggers

Every time there is a wait, it causes all other triggers to run immediately. The first hyper trigger runs immediately, waits 0, then goes on to the next hyper trigger, which then waits 0. It then goes back to the first hyper trigger and waits the first wait again.

tl;dr it makes ur trigs run faster just cuz.

Triggers normally run once every 2 seconds on normal because there is a delay in between each trigger run. This can't really be avoided, but it can be pushed away (4 hypers pushes this into days inbetween NEOs). Hyper Triggers essentially prevent this delay from ever happening, making them run every 84 ms on fastest until the "NEO", which is calculated based off of the number of waits in your triggers. This should be explained in the wiki.

With hyper triggers, the triggers run eight times a game second, which means 16 times faster than normal speed. That's about it. Read the wiki for more.

[url=http://Falkoner.CoW.GooglePages.com/Hyper_Triggers.html]Here's[/url] another tutorial on them, if you still don't get it, note that if you are using excessive amounts of waits in your map, you're going to have to replace them with [url=http://Falkoner.CoW.GooglePages.com/Death_Counts.html]Death Count Timers[/url] so you don't get [url=http://www.staredit.net/wiki/Wait_Blocks]Wait Blocks[/url], and wait blocks aren't just caused by hypertriggers, multiples waits running at the same time can cause them.

Here's another tutorial on them, if you still don't get it, note that if you are using excessive amounts of waits in your map, you're going to have to replace them with Death Count Timers so you don't get Wait Blocks, and wait blocks aren't just caused by hypertriggers, multiples waits running at the same time can cause them.

Also keep in mind a game second (like in elapsed time and countdown trigs) is not a real second (though I think the recorded time after a match is real time). Hyps typically run your trig cycles at about 12x per real second, and run somewhere around once per real second normally without them. If I were to give an EASY, summed up explanation of what to do, here it is: Put 3 triggers each with Always as condition, Preserve Trig and Comment "Hyper Trigger," and fill the rest up with waits (62). No need for 63. Making it take up less visual space is much more important. You must put them in a player that will be present in the game at all times, hence why a computer (not neutral or defeated) is a good choice. Then you are able to use the Wait action for other players without worrying about a "wait block," which basically stops triggers from running for that player, often ever again if there are many waits (like hypers) running in a single player. Please keep in mind, sometimes units don't move immediately when ordered to. That's just how it is. But this will be much faster usually. The good thing about hyper trigs is that it affects every player, even though wait blocks can only occur in the player that has them.

Also keep in mind a game second (like in elapsed time and countdown trigs) is not a real second (though I think the recorded time after a match is real time). Hyps typically run your trig cycles at about 12x per real second, and run somewhere around once per real second normally without them.

If I were to give an EASY, summed up explanation of what to do, here it is:

Put 3 triggers each with Always as condition, Preserve Trig and Comment "Hyper Trigger," and fill the rest up with waits (62). No need for 63. Making it take up less visual space is much more important. You must put them in a player that will be present in the game at all times, hence why a computer (not neutral or defeated) is a good choice. Then you are able to use the Wait action for other players without worrying about a "wait block," which basically stops triggers from running for that player, often ever again if there are many waits (like hypers) running in a single player.

Please keep in mind, sometimes units don't move immediately when ordered to. That's just how it is. But this will be much faster usually. The good thing about hyper trigs is that it affects every player, even though wait blocks can only occur in the player that has them.