Max Move Speed - Max Attack Range

[Faestus]

Seems these two values are limited in the WC3 World Ed.

Is there a way to change this? Or cheat the max range/speed limit?

 

[Zwiebelchen]

Move speed is capped, yes.

Max range, however, can be 99999, so basicly across the whole map. There's no limit to this.

There was a system that allowed higher movement speeds. It achieved that by moving the unit periodically a step forward to the current moving direction. I don't know if it's still around, though. You might search for it.

 

[neo_sluf]

Ok here you go bro

http://www.hiveworkshop.com/forums/...0-a-207607/?prev=search=Movespeed&d=list&r=20

 

[Ezekiel12]

Yep, no practical cap on attack range, movespeed cap is 522.

 

[Zeatherann]

practical cap: around 1000, system cap: full float range.
Remember that each tile of terrain is 128 across, with 256 tiles thats a range of 32,768 from one side to the other, however the corner to corner distance is 46,341.
Anything beyond that is rare, and usually useless. The only exception to that is when you have map sizes beyond 256 in either direction.

 

[deathismyfriend]

ya max map size is 480 x 480. so thats a big difference lol. also just use the system that was posted. there is another system i believe that is GUI.

 

[Faestus]

You guys forgot to mention that Acquistion Range limits the range.

 

[deathismyfriend]

^ thats true nice catch

 

[Zeatherann]

Acquisition Range's ability to limit range is very weird; and note that sometimes that the range is greater than this.

I don't understand how the max is 480x480 that's 231,361 terrain points.

 

[deathismyfriend]

JNGP has the ability to break the normal limits of a map. It makes 480 x 480 the new max.

 

[Zeatherann]

I ment since isn't terrain 'indexed' on a 16bit integer?

 

[deathismyfriend]

ooo that im not to sure about.

 

[Almia]

Just like neo_sluf posted, http://www.hiveworkshop.com/forums/...-a-207607/?prev=search=MoveSpeedX&d=list&r=20 is the only solution to delimit the movespeed.

Blizzard did the limitations because the unit might move outside the map if the speed value is so high.

 

[Ezekiel12]

Blizzard did the limitations because the unit might move outside the map if the speed value is so high.

That sounds like a wild guess to me..

 

[Dr Super Good]

I ment since isn't terrain 'indexed' on a 16bit integer?

Both X and Y width of the map are stored as 32 bit little endian unsigned. So I am guessing they use something similar in the game itself to compute the index of the terrain node.

Blizzard did the limitations because the unit might move outside the map if the speed value is so high.

I am guessing the limit is because of how the pathing system works. It calculates unit pathing in increments (1 unit of each player per game frame?). Each micro move order that is issued probably only covers a maximum of 522 distance. Setting speed to something stupid like 50000 would mean a single unit would overload the pathing system for that player.

 

[Zeatherann]

Line based collision to count 'skipped' collisions sucks in code. I bet DSG is close to the assumptions made by Blizz.

 

[Almia]

Both X and Y width of the map are stored as 32 bit little endian unsigned. So I am guessing they use something similar in the game itself to compute the index of the terrain node.



I am guessing the limit is because of how the pathing system works. It calculates unit pathing in increments (1 unit of each player per game frame?). Each micro move order that is issued probably only covers a maximum of 522 distance. Setting speed to something stupid like 50000 would mean a single unit would overload the pathing system for that player.

Oh ok.
I was actually imagining the movement is actually a polar projection movement.