|
Turns out I didn't fix it. I saw it once (I swear) where it did it correctly. I DID NOT CHANGE IT after that, yet on all test runs after that time, only the first message showed up. However, the timer works. Also, in the run where it worked correctly, the timer showed up after the messages. I don't have a clue why this happened.
![]() ![]() ![]() ![]() ![]() ![]() |
|
Write your own destiny, or else someone will write it for you!
|
Lol you are not making much sense
However its almost sure you are experiencing wait blocks. Don't execute ANY wait (includes hypertriggers) while another wait is running. Replace the waits with Death Counters. ![]() ![]() ![]() ![]() ![]() ![]() ![]() http://sonsofwar.pyrom.net/index.html___0% 100% |
|
Write your own destiny, or else someone will write it for you!
|
As I said... some other triggers' condition(s) must be met which is executing a wait. Find it, remove the wait or fix the condition and it will work fine. When you can't find it then copy all triggers via scmd's text base trig edit to the notepad and search for all waits. Ignore the waits in triggers that don't run for the player with the msgs. The best would be to remove ALL waits and ALL Transmissions (uses wait) to avoid the wait block. Saves you the search. Or double check all conditions on what they depend. Maybe a 3rd trigger is creating a unit, modifying a dc or w/e when it wasn't supposed to... Its a bit of work, but we would have to do the same to find it if it isn't obvious. And when it was obvious you would have found it already. ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() http://sonsofwar.pyrom.net/index.html___0% 100% |
|
Taking StarCraft Map Making to the Limit!
|
Host it at mediafire then.
|
|
Write your own destiny, or else someone will write it for you!
|
Jeez, I guess you haven't followed my guide on how to find the less obvious wait blocks or you would have found it easily. In fact I laughed about it when I found it because it's quite obvious. Now go back to your map and check which preserved triggers for Force 'Diddy KongZ' contain at least 1 wait (ignore the conditions, just check which have waits). Use the textbased trigedit for this and copy the triggers into notepad and search for 'wait'. Then you will find out that there's 1 trigger that runs always with a very long wait. So when your animated text/wait combos kick in you get the block. The fact that it's a very long wait explains the "random" blocking behaviour you experienced, since the block isn't as long when you hit the wait when it's almost finished. Replace the long wait with a dc that counts from 1613 down to 0. ![]() ![]() ![]() ![]() ![]() ![]() ![]() http://sonsofwar.pyrom.net/index.html___0% 100% |
|
I found three waits besides the ones in text messages: one in winning the game, another for losing, and one in the music. I removed the two in the winning and losing triggers. The music wait is the only one that is constantly running. Is that screwing up my map? I don't understand why because it doesn't mess up the intro text messages.
![]() ![]() ![]() ![]() ![]() ![]() |