[Trigger] Just a simple question

[Kanadaj]

Hey guys!

I have a very simple question: I had a loop trigger with wait and it worked perfectly, but after I made some more, they stopped to work correctly. So if I have 2 loop with 0.01 wait running then they "kill" each other, right?

 

[Adiktuz]

Hey guys!

I have a very simple question: I had a loop trigger with wait and it worked perfectly, but after I made some more, they stopped to work correctly. So if I have 2 loop with 0.01 wait running then they "kill" each other, right?

it depends... I just have one thing to say, PUTTING WAITS INSIDE LOOPS ARE BAD...

 

[Chewii]

I agree with Adiktuz putting waits inside loops isn't very good :/

But why should they kill eachother ? lol

 

[Adiktuz]

I agree with Adiktuz putting waits inside loops isn't very good :/

But why should they kill eachother ? lol

maybe he has a variable which is used by both... I guess both of them are IntegerA loops and so running both loops with a wait will cause overwrites of the IntegerA hence, bugs...

 

[Chewii]

But if he uses integerA in one loop and integerB in another ?

 

[Adiktuz]

But if he uses integerA in one loop and integerB in another ?

then no bugs, supposedly... also sometimes even without waits, using simultaneous or even just successive integerA loops causes triggers to stop... IDK why though, maybe an instance of those weird wc3 bugs...

 

[Kanadaj]

I know I know, wait in loop is not rly good and I remade it with timer (but so much easyer with an integer A/B than with a variable Integer counter!) But it's good to know that Blizzard didn't solved seperate Integer A/B for seperate triggers (oh s**t)

 

[Adiktuz]

I know I know, wait in loop is not rly good and I remade it with timer (but so much easyer with an integer A/B than with a variable Integer counter!) But it's good to know that Blizzard didn't solved seperate Integer A/B for seperate triggers (oh s**t)

well, there are a lot of unsolved bugs in wc3 which I guess Blizzard would not fix anymore...