Staredit Network

Staredit Network -> UMS Assistance -> Hmm damn hypers arent working well
Report, edit, etc...Posted by aE(Sniper) on 2005-07-11 at 02:33:45
I would make hyper trigs while doing a map and heres wat would happen:
Trigger
Description:
The Hyper...
Players:
¤ All Players
Conditions:
¤ Always();
Actions:
¤ Wait(0);
¤ Wait(0);
¤ ...
¤ Wait(0);
¤ Comment("HT");
¤ PreserveTrigger();

Id copy it 5x and if i put a wait anywhere it would freeze at the waits
Report, edit, etc...Posted by Ultimo on 2005-07-11 at 02:42:18
Since you either don't use waits, or the hyper triggers are owned by someone without waits.
Report, edit, etc...Posted by DT_Battlekruser on 2005-07-11 at 02:48:12
Give you hypers to a player (NOT a force) that was no other triggers with waits. This is the easiest and simplest method to eliminate the 'wait block' problem that you are experiencing.
Report, edit, etc...Posted by Deathknight on 2005-07-11 at 08:41:18
This belongs in the concepts forum HOW?..

You can not have any other waits except for the hypers owned by the same player. This is called a "wait block" and prevents your triggers from running properly.
Report, edit, etc...Posted by chuiu on 2005-07-11 at 09:56:25
move(mapMakingAssistance);

Try putting hypers for one player, and any trigger with waits for another. That way you make triggers that need the hypers for the first player.
Report, edit, etc...Posted by DaMiNaToR on 2005-07-11 at 10:52:55
I've always put my hypers in "All Players" and never had trouble with them... mellow.gif

EDIT: Wait!!! OMG!!!! THAT'S WHY SST DAMINATOR GO SO censored.gif ED UP!!!! THE HYPERS CRUSHED THE CINEMATICS!!!!! OMG!!!!! SOO HAPPY!!!! HAHAHAHA!!!! blink.gif
Report, edit, etc...Posted by Centreri on 2005-07-11 at 11:10:23
Happy because ure cinematics got crashed ermm.gif now that is kind of strange..
Report, edit, etc...Posted by Trusting_Stylus on 2005-07-12 at 20:45:33
Okay, what you want to do is this:

Players:All players
Condition:Always.
Actions:Wait (0) milliseconds.
Then what you want to do is add as many preserve triggers as possible, then delete one. Save and you got urself a hyper trigger.
Report, edit, etc...Posted by ShadowBrood on 2005-07-12 at 20:49:10
Try to make a player without waits and set the hyper triggers for that player.
Report, edit, etc...Posted by KaboomHahahein on 2005-07-12 at 21:07:42
QUOTE(Trusting_Stylus @ Jul 12 2005, 07:45 PM)
Okay, what you want to do is this:

Players:All players
Condition:Always.
Actions:Wait (0) milliseconds.
Then what you want to do is add as many preserve triggers as possible, then delete one.  Save and you got urself a hyper trigger.
[right][snapback]261378[/snapback][/right]


Uhh aE(Sniper) knows how to make Hypper triggers. Making the hypper triggers were not the problem, it was getting them to work.

And put your triggers at the bottom of the trigger list.
Report, edit, etc...Posted by Heimdal on 2005-07-12 at 21:17:08
QUOTE(Trusting_Stylus @ Jul 12 2005, 07:45 PM)
Okay, what you want to do is this:

Players:All players
Condition:Always.
Actions:Wait (0) milliseconds.
Then what you want to do is add as many preserve triggers as possible, then delete one.  Save and you got urself a hyper trigger.
[right][snapback]261378[/snapback][/right]
You should NEVER make hyper triggers belong to "All Players" if you intend on using any other waits. This is the problem he was trying to fix.

And WTF? Copy "Preserve trigger" multiple times? That does absolutely nothing. You need to copy the "Wait 0" as many times as possible.

By the way, everyone tends to put their preserve triggers at the bottom of the action list. This might make sense in your head, but it actually doesn't matter where it goes. I find that putting comments and preserve trigger at the top help when editing triggers later.
Report, edit, etc...Posted by pimpinelephant on 2005-07-13 at 05:15:30
That Heimdal, he's so hot right now!

and everyone else already explained everything.
Report, edit, etc...Posted by Mini Moose 2707 on 2005-07-13 at 11:13:59
Quit with the wussy Hyper Triggers. wink.gif

Players:
¤ Player 1
Conditions:
¤ SwitchX is set.
Actions:
¤ Wait 0
¤ Clear SwitchX
¤ Preserve trigger.

Trigger
Players:
¤ Player 2
Conditions:
¤ Always
Actions:
¤ Wait 0
¤ Set SwitchX
¤ Wait 0
¤ Preserve trigger.
Report, edit, etc...Posted by (U)Bolt_Head on 2005-07-14 at 01:23:31
LoL your so bias Minimoose,

The non wussy hyper triggers your refering to don't offer any useful functional advantage over the 'wussy' kind.
Report, edit, etc...Posted by DaMiNaToR on 2005-07-16 at 17:50:37
No, I'm just happy because now I can finally fix my damn map! biggrin.gif
Report, edit, etc...Posted by Urmom(U) on 2005-07-18 at 22:29:42
For some reason, I remember somebody saying not to use that method of hypertriggers(mooses). I cant seem to remember why though... confused.gif Anybody remember?
Report, edit, etc...Posted by Spartan-004 on 2005-07-18 at 23:54:13
Well, try for players: ALL Players,
Conditions: Always,
Actions: ... Obvioulsy Wait 0 milliseconds 62 times, and then you do preserve,
then comment: Hyper Trigger.

This is my method, and its never failed.. ;D
Also, there might b a prob with them, which has happened to me alot,
after a certain amount of waits, u must delete the hypers, and do th exact same thing as you did the ones you deleted, quick way to do so: do the same thing once, select the trigger, copy 3-4 times, you will now have 5 hyper triggers that work.
Keep using this method alot, because if you dont, hyper screw up and every goes slooooow.

Spartan-004
Report, edit, etc...Posted by UED77 on 2005-07-19 at 00:12:07
Spartan-004... How many times have people told others NOT to give hypercheck to "All Players"? It's even on this same page! If you were to scroll up six posts — you should've read the entire thread anyway — you would've seen Heimdal telling people not to do that.
Please read intermediary posts in the thread before you post, and strive not to spread misinformation.

UED77
Report, edit, etc...Posted by SC-MapMaker on 2005-07-19 at 01:41:59
HAHAHAHAHAHAHAHAHA. I've never seen so many posts on something that GOT ANSWERED ON THE FIRST REPLY.
Report, edit, etc...Posted by (U)Bolt_Head on 2005-07-19 at 02:14:19
QUOTE(UED77 @ Jul 18 2005, 11:12 PM)
Spartan-004... How many times have people told others NOT to give hypercheck to "All Players"? It's even on this same page! If you were to scroll up six posts — you should've read the entire thread anyway — you would've seen Heimdal telling people not to do that.
Please read intermediary posts in the thread before you post, and strive not to spread misinformation.

UED77
[right][snapback]265286[/snapback][/right]

theres nothing wrong with his method as long as he realizes that when there before other waits they will be blocked.

There are some instances when i would actually suggest having the hyper triggers owned by all players.
Report, edit, etc...Posted by Spartan-004 on 2005-07-19 at 02:47:02
QUOTE((U)Bolt_Head @ Jul 19 2005, 12:14 AM)
theres nothing wrong with his method as long as he realizes that when there before other waits they will be blocked.

There are some instances when i would actually suggest having the hyper triggers owned by all players.
[right][snapback]265367[/snapback][/right]


Thank you (U)Bolt_Head, with the all players, it works perfectly fine with me, maybe you put all players and made mistake in actions or something, because it works, as I have said before, perfectly fine.

Spartan-004
Report, edit, etc...Posted by Heimdal on 2005-07-19 at 19:39:44
In some cases (like with 8 human players) you would need the hyper triggers to be owned by all players, and then you need to make sure that they're the last triggers in the list. But in most cases, giving them to all players and then making triggers with waits will cause wait blocks. Then people come to the forum like "omg wtf my hyperz rnt working!!oneone." Hence this thread.
Report, edit, etc...Posted by 007Torrasque on 2005-07-20 at 00:05:28
No offense, but ive found it more useul to copy the wait 6 times and copy the trigger 5 times, always works as well as filling up the whole list for me...
Next Page (1)