Staredit Network

Staredit Network -> UMS Assistance -> Hyper Triggers
Report, edit, etc...Posted by Haemogod on 2005-01-11 at 04:54:48
i dont get the point of a trigger that does ntoing but wait, does this speed up all the triggers on the map, or do you have to link it to a specific trigger somehow.
Report, edit, etc...Posted by sckor on 2005-01-11 at 06:45:13
for some wkward strange reason tongue.gif , if you put those series of wait triggers under a player with no other wait actions, then it will speed up, not the triggers, but will check the triggers more frequently.
so let's say you made this trigger

always

set resources: add 1 ore
wait 10000 ms
preserve
comment: give ore

Then, it will sort of well sharpen the trigger.

however if it is like

always
create one carrier at biggie
preeserve

It will build carriers much faster then usual

so waht you do, is check a specific player, not force of all players, and creatre those hypers... that should speed things up.
Report, edit, etc...Posted by AqoTrooper on 2005-01-11 at 06:54:58
QUOTE(sckor @ Jan 11 2005, 02:45 PM)
for some wkward strange reason...[right][snapback]123007[/snapback][/right]

The reason is not that weird - blizzard created the trigger system that way that it'll check the triggers every two seconds or so but if there's a wait the program will stop doing the current trigger in the middle and check other trigger - so that if you have a trigger with wait it won't disable all the other triggers till the wait ends.
if you have many waits of 0, the cumputer will go thru your other triggers faster than every two seconds - since it's wait 0 not 2000.
if you put many hyper triggers, it'll have not a double effect but a 62^62 effect (I comment my hypers) since it goes from one 0 is one hyper to one 0 in the other hyper and than the second and third till you go thru all 62 (I comment my hypers) and than it'll move to the 2nd wait in the first hyper.
Some other people calculated the time takes till the hyper ends and you get a singal two seconds delay so they an tell exactly how better 4 hypers than 2 are.
but basicly, create 4-5 hypers for every map of yours and it'll run with no notisable delay.
Report, edit, etc...Posted by sckor on 2005-01-11 at 06:59:02
alright, maybe the reason isn't so awkward. wink.gif
Good luck with your map...
Report, edit, etc...Posted by chuiu on 2005-01-11 at 09:58:35
Heamogod, basically waits for each player happen seperate from each other player. And if you have a two waits for one player happening at the same time, the newest one will overide the older one. Hyper triggers force specific players, or all players to work on the same trigger timming. It is, for most poeple, wait 0 miliseconds. While it doesn't not actually wait that long, it is fast enough to help create some nice effects in game.

Be careful when using these, though.
Report, edit, etc...Posted by Haemogod on 2005-01-11 at 13:40:53
so i do them for players 1-8 or non at all?

or just 1 in all players or 8 in all players or what. cus ppl call them hyper triggers, but am i understanding correcly that there is only one type of "Hyper trigger" and all u change for it is the player that it effects? basically i understand how to draw one up(the tutorial) but not how many to do or where to put them.
Report, edit, etc...Posted by (U)Bolt_Head on 2005-01-11 at 14:26:20
QUOTE(Chu @ Jan 11 2005, 08:58 AM)
And if you have a two waits for one player happening at the same time, the newest one will overide the older one.
[right][snapback]123038[/snapback][/right]


the newer one doesn't override the existing one. If a wait is already running then the new one is delayed until the first is finished. Then it will have a chance to run IF it has priority over any other waits ready to fire.

Haemogod: make them for a computer player at the end of there list of triggers.
Also making a trigger for players 1-8 or All players is EXACTLY the same. There are no differances, between the two except how the editor displays the trigger to you.
Report, edit, etc...Posted by chuiu on 2005-01-11 at 14:38:59
QUOTE((U)Bolt_Head @ Jan 11 2005, 01:26 PM)
the newer one doesn't override the existing one.  If a wait is already running then the new one is delayed until the first is finished.  Then it will have a chance to run IF it has priority over any other waits ready to fire.
[right][snapback]123091[/snapback][/right]


Not from my experience.
Report, edit, etc...Posted by SA_Max71 on 2005-01-13 at 05:05:22
QUOTE(AqoTrooper @ Jan 11 2005, 03:54 AM)
The reason is not that weird - blizzard created the trigger system that way that it'll check the triggers every two seconds or so but if there's a wait the program will stop doing the current trigger in the middle and check other trigger - so that if you have a trigger with wait it won't disable all the other triggers till the wait ends.
if you have many waits of 0, the cumputer will go thru your other triggers faster than every two seconds - since it's wait 0 not 2000.
if you put many hyper triggers, it'll have not a double effect but a 62^62 effect (I comment my hypers) since it goes from one 0 is one hyper to one 0 in the other hyper and than the second and third till you go thru all 62 (I comment my hypers) and than it'll move to the 2nd wait in the first hyper.
Some other people calculated the time takes till the hyper ends and you get a singal two seconds delay so they an tell exactly how better 4 hypers than 2 are.
but basicly, create 4-5 hypers for every map of yours and it'll run with no notisable delay.
[right][snapback]123010[/snapback][/right]

Unless your running the map for more than 2 weeks straight. (That is according to the tutorial database on hyper triggers.)
Next Page (1)