[Trigger] Die master ! I don't wanna Order - Stop !

[Exum]

Hi everyone !

I am front of a huge problem :
In my map, some spells have to be stoped in some cases, so i use a

• Unit - A unit Starts casting a spell

event, and after checking conditions, a

• Unit - Order (Triggering unit) to Stop

trigger.

It worked well, but today units don't want to listen this order anymore
I made a test trigger :

• Test bug
  • Events
    • Unit - A unit Starts casting a spell
  • Conditions
  • Actions
    • Unit - Order (Triggering unit) to Stop

And units still start the effect of an ability when using it !

Have anyone an idea about why does it happen ?
I checked everything i did before the bug appears and i can't find the problem :/ Maybe some kind of leaks ? Lags ?
I don't know where to search, that's why i'm asking if this is a known bug due to a specific thing.

Btw : i can upload the map if needed.

Thank you in advance !

 

[deathismyfriend]

If u move units w ur spells make sure the stop command is being issued after the move command. U can also try doing pause unit then issue stop order then I pause unit and that may fix it

 

[Exum]

Thanks, using pause and instantly unpause before using "Stop" order seems to solve the problem.

But still, i'm really curious, why does it happen ? ^^
Maybe triggers are longer to work than the time between "Starts" and "Inits effect" of an ability ?

 

[Maker]

There is a small internal dealy.

 

[Exum]

Any idea of what did i do wrong to make the bug appears ? As it wasn't the case a few days ago.
Knowing it would helps me not having this problem again ;p
And i bet this isn't the only bug due to this, if i created some kind of delay, it may also be a problem for other things in my map, no ?

Btw : t4i Maker

 

[deathismyfriend]

it wasnt something u did its just like maker said there is a slight internal delay w the action move. pause and unpause slowed it down and allowed the issue order stop to fire after the move order rather than b4. hopefully i explained that correctly

 

[Exum]

I think i understand it, even if the "why now and not a few days ago" keeps being a mistery to me

I was a bit scared about seeing another bug due to this latency, that's why i asked

Thank you for answers !

 

[deathismyfriend]

np glad i could help

 

[defskull]

Add a wait of 0.00 second, it works.
And yes, the trigger will still be MUI.

 

[MasterTrainer]

0.00 huh... and all this time I thought is should be 0.01.

 

[UndeadImmortal]

0.00 huh... and all this time I thought is should be 0.01.

Minimum time of wait is 0.27 secs.

 

[Maker]

Minimum time of wait is 0.27 secs.

Maybe in multiplayer, but in single player the minimum is 0.1 seconds.

 

[defskull]

Putting 0.00 wait and 0.01 has its difference (didn't test it yet but I kinda know this fact based on experiment).

Well, time to get some experiment running.

 

[Maker]

Start testing:

Wait Events Player - Player 1 (Red) skips a cinematic sequence Conditions Actions Countdown Timer - Start timer as a One-shot timer that will expire in 30.00 seconds Wait 0.00 seconds Game - Display to Player Group - Player 1 (Red) for 60.00 seconds the text: (String((Elapsed time for timer))) Trigger - Run (This trigger) (checking conditions)

 

[MasterTrainer]

Start testing:

Wait Events Player - Player 1 (Red) skips a cinematic sequence Conditions Actions Countdown Timer - Start timer as a One-shot timer that will expire in 30.00 seconds Wait 0.00 seconds Game - Display to Player Group - Player 1 (Red) for 60.00 seconds the text: (String((Elapsed time for timer))) Trigger - Run (This trigger) (checking conditions)

That's weird... I tested both 0.00 wait and 0.01 wait but the results were the same...

 

[defskull]

Wait more than 0.00 second will cause the trigger to become un-MUI, perhaps.
I've always use 0.00 second of wait to create small delay and it always turns out to become MUI trigger.

 

[Maker]

Wait more than 0.00 second will cause the trigger to become un-MUI, perhaps.
I've always use 0.00 second of wait to create small delay and it always turns out to become MUI trigger.

Dude...no. The length of the wait doesn't affect if the thing is MUI or not. All waits are >0.0 of actual game time.