I think there was a problem on one of my previous maps that when I had two overlapping waits the wait lasted for longer than expected. If such a problem occurs, how do I fix it?
None.
The 'wait' Issue
I'm wondering, because I'm aiming thinking a map that is heavily spell oriented, what happens when there's too many wait triggers going on. (as you have to use the wait trigger to enable the spell to last for a duration of time. The countdown timer is already being used.
I think there was a problem on one of my previous maps that when I had two overlapping waits the wait lasted for longer than expected. If such a problem occurs, how do I fix it?
I think there was a problem on one of my previous maps that when I had two overlapping waits the wait lasted for longer than expected. If such a problem occurs, how do I fix it?
The problem you are encountering is called a wait block. The main way to avoid encountering this problem is to use many death counters instead of waits. For example, instead of waiting for 6000 milliseconds when a condition is met and then doing something, you add 1 to the "death counter," for example, deaths of a psi emitter. Then, when the player has suffered a number of deaths of the psi emitter which is the same as 6000 milliseconds, (72 or 3, depending on whether you are using hyper triggers or not), you make the appropriate action. It seems more bulky at first because each "wait" when using a death counter takes multiple triggers, but once you understand the system you realize how much more flexible it is.
You can read more here, feel free to ask questions:
http://www.staredit.net/wiki/Wait_Blocks
http://www.staredit.net/wiki/Hyper_Triggers
http://www.staredit.net/wiki/Death_Counters
You can read more here, feel free to ask questions:
http://www.staredit.net/wiki/Wait_Blocks
http://www.staredit.net/wiki/Hyper_Triggers
http://www.staredit.net/wiki/Death_Counters
None.
Instead of using waits, death counters is the best option. Death counters are now usually a better alternative for switches and timer. If you are making spells, you should use death counters along with hyper triggers.
1000 milliseconds is known to be one second
11.8 (or 12) death counters with hyper triggers is 1 second.
So about 120 deaths of a certain unit = 1 second in a game speed of fastest with hyper triggers.
Here is an example of a simple spell from my map.
While it might take more than 1 trigger to make a spell and takes a lot of organization, it is the best way. Organization is really important and you should never use the same death counter as the wait for each spell, unless you allow only 1 spell casting at a time.
1000 milliseconds is known to be one second
11.8 (or 12) death counters with hyper triggers is 1 second.
So about 120 deaths of a certain unit = 1 second in a game speed of fastest with hyper triggers.
Here is an example of a simple spell from my map.
Collapse Box
While it might take more than 1 trigger to make a spell and takes a lot of organization, it is the best way. Organization is really important and you should never use the same death counter as the wait for each spell, unless you allow only 1 spell casting at a time.
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
Keep in mind that waits are measured in real time, while death counts (like the countdown timer) are measured in game time.
This is important for single player maps where it's very likely that the player alters the speed.
With hyper triggers triggers are checked 8 times per game second which translates to ~11.8 times per real time second on fastest.
This is important for single player maps where it's very likely that the player alters the speed.
With hyper triggers triggers are checked 8 times per game second which translates to ~11.8 times per real time second on fastest.
Options
Pages: 1
Back to forum
Please log in to reply to this topic or to report it.
Members in this topic: None.
[2026-7-18. : 2:27 am]
Symmetry -- https://staredit.net/topic/18903/ THE REVIEWS ARE HERE! "ok these are pretty good memes" - ssj9Kevin[2026-7-17. : 2:58 pm]
Ultraviolet -- SymmetrySymmetry shouted: Man I wish we had this tech back in the day when people played ums lmao
fr fr[2026-7-17. : 2:39 am]
Symmetry -- Man I wish we had this tech back in the day when people played ums lmao[2026-7-16. : 6:28 am]
NudeRaider -- EUD actions, specifically. The conditions remained. Today we can even have actions again, but they're all virtualized/whitelisted (not sure on the actual technical implementation) so you can only use them for specific intended purposed, not arbitrary code injections.[2026-7-16. : 6:26 am]
NudeRaider -- I mean yes, maps - through EUDs - were theoretically able to do that as well, but that was patched quickly.[2026-7-16. : 6:25 am]
NudeRaider -- SymmetrySymmetry shouted: Ohhh imagine a SC map that could delete itself
not the map, the editor[2026-7-16. : 2:28 am]
Symmetry -- I vaguely remember Voy doing some ACE back in the day, but I had no idea EUDs could do that kind of shit. I am very much catching up on the technology[2026-7-15. : 8:51 pm]
NudeRaider -- SymmetrySymmetry shouted: NudeRaider Is EUD editor capable of writing shit onto the player's harddrive? That seems like it would be dangerous
yeah an editor that isn't allowed to write files sounds rather pointless, so I'd assume it can. Like most other programs too btw. and yes, obviously that's dangerous, but also kinda necessary. MS introduced that virtualization for exactly that reason.[2026-7-15. : 4:10 am]
Ultraviolet -- I don't think so. I think they shut that shit down after 1.16, maybe even earlier