Movement - Unit Speed - Maximum Constant with latest patch

[lolreported]

With the latest patch Blizzard changed this constant (or fixed it to actually work if it didn't before).

I can't remember if the value has always been at 400 by default; but apparently the latest patch now caps the movement speed at 400 for all maps, unless the map have a custom value set already.

Map makers must now manually set this value to "522" in order to be able to use the maximum movement speed in their map.

 

[deepstrasz]

It's like that in 1.31 too, probably in most patches from 1.29 onward if not even before.

 

[lolreported]

It's like that in 1.31 too, probably in most patches from 1.29 onward if not even before.

It has never been an issue before. Players recently started reporting their builder in my tower defense map started moving really slow compared to a week ago and it was because the movement speed was capped at 400, instead of the usual 522.

 

[deepstrasz]

So it goes like this in previous patches. You can set it to 522 in the unit editor but in the game constants the max is 400 unless changed. That probably means the 522 in the object editor won't work unless the game constants also has that field to 522.

 

[lolreported]

In previous patches the constant didn't need to be changed, units would have their movement speed set to 522, with no cap. So either the previous patches had this constant at 522 and they reduced it to 400 in this patch or it had always been at 400, but they fixed an issue with the constant not working properly.

 

[deepstrasz]

but they fixed an issue with the constant not working properly.

Most probably.

 

[Strydhaizer]

I create maps in 1.30 and that constant is set to 400 by default.