Put them last in your trigger list so that they won't disrupt other waits you have, though you shouldn't be using any waits other than hyper triggers.
I already used them, and its too much work too change it. but i seperated them over the players, and i'll put the hyper triggers at another player, on the bottom the trigger list of that player. then it should be ok right?
Suck it up bitch. (And when I say bitch I mean that in the most humorous non offensive way possible
) My map has over 10000 triggers. Ahli made a map with over 65000 triggers. Kaias and Lethal Illusion made a map with 20k? There are numerous other maps with shit tons of work put into them, I just can't name them all off the top of my head. Just suck it up and redo it. It's part of mapping.
Sounds harsh, but really, that's what you gotta do.
Edit:
On a more helpful note, do you edit triggers in text format or solely in classic format? If you don't know how to edit text-wise you should learn, if you need help with that I'd be happy to help, its great to know and extremely useful especially for things like this where you're going to end up doing a lot of copy+paste on triggers.
Post has been edited 1 time(s), last time on May 10 2011, 6:04 pm by Vrael.
None.
4x4 pixels is pretty small but still should be small enough.
Interceptors are the fastest air unit, with muta/scourge/wraith/etc... being second. Scourges are probably the ones to test, as they are the smallest.
I think you're encountering wait blocks because you're using waits elsewhere.
i used them only at the other players, so the player with the hypertriggers doesnt have them at all. i thought it shouldnt interfere?
None.
SDE, BWAPI owner, hacker.
The Nuclear Missile is the fastest unit. It practically has no speed limit, just a long acceleration.
Your hyper triggers must be set for an active player (Non-human preferably). It only needs to run for 1 player, not all of them.
As far as your issue is concerned, if you still can't detect the air unit, then it's either an issue with your trigger or a Starcraft limitation.
Note: Putting a trigger in "All Players" will just copy the same trigger to each of the 8 players. There are only triggers owned by 8 players in the end.
Post has been edited 1 time(s), last time on May 12 2011, 7:03 pm by Heinermann. Reason: Remove incorrect info
The condition Bring owned by a player can't be met until the wait for that specific player finishes its execution.
Are you sure about this part? If I've understood you right, do you imply that any bring condition in any trigger owned by player P won't return true until wait for P finishes? Haven't encountered this in practice, but probably just haven't payed much attention.
Some.
SDE, BWAPI owner, hacker.
Sorry my bad, I was mistaken.
Wait. How do you use the text trigger editor?
None.
I do stuff and thingies... Try widening and reducing the number of small nooks and crannies to correct the problem.
Wait. How do you use the text trigger editor?
Scmdraft has a text trigger editor.
The button in the top right with a blue diamond on it (not to far top right, that's the window exit button) compiles and saves the triggers, if they could be compiled (-> no errors).
Use a text editor like notepad++ to easily modify the text triggers.
There are even makros for notepad++ for faster trigger writing and some people even created an own text trigger creation program (makrotriggers?) with loops and stuff to produce many triggers within a short time.
Just ask Vrael!
We can't explain the universe, just describe it; and we don't know whether our theories are true, we just know they're not wrong. >Harald Lesch
The condition Bring owned by a player can't be met until the wait for that specific player finishes its execution.
Are you sure about this part? If I've understood you right, do you imply that any bring condition in any trigger owned by player P won't return true until wait for P finishes? Haven't encountered this in practice, but probably just haven't payed much attention.
Sorry my bad, I was mistaken.
But it will prevent conditions of the trigger executing the wait to be met, right?
That's what I thought he implied in the first place.
SDE, BWAPI owner, hacker.
Yes if there's a wait in a trigger, that one trigger can't be executed again until ALL waits for that player are over.
When it's over, it will execute from where the wait left off, until all the actions have been performed, and then re-enable the conditions.
rockz
