Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
The game only updates the screen in these intervals but it's doubtful that you can already read the new value in code directly after the action. That depends on whether the specific action waits for the first interval or notices it and cuts it off in the start function.
The game only updates the screen in these intervals but it's doubtful that you can already read the new value in code directly after the action. That depends on whether the specific action waits for the first interval or notices it and cuts it off in the start function.
the new flying height is set instantly with that function
change unit flying height to 3600 with speed 1 will be 3600 even if it takes an hour to reach it
the stuff between is just animation
the new flying height is set instantly with that function
change unit flying height to 3600 with speed 1 will be 3600 even if it takes an hour to reach it
the stuff between is just animation
Well, we spoke in general. But no, I not only meant the mapmaker (GetUnitFlyHeight) with reading the value. When you start a second SetUnitFlyHeight while the first is still running, the graphic won't begin at the target height of the first call, rather from where it's currently at and even not change the add rate.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.