Talk:Attack Range

Motion Buffer Range mechanic
How does the so-called "motion buffer range" exactly work? The 6.84 patch which introduced this mechanic states: "Melee attacks now miss if the target is farther than 350 range more than their attack range."

So this means the maximum range for a melee unit to hit its attack target should be the unit's attack range + 350, right? However, the wiki sometimes only states 300 range instead of 350, so which is the correct value for that?

(Note: I couldn't find any other changes related to this mechanic in the subsequent changelogs.)

--Psion1C (talk) 20:59, 15 January 2017 (UTC)


 * There are 2 different buffer ranges. You can test the first one with Tiny and Enchantress. If you attack Ench who has lvl 4 untouchable with a Tiny with level 3 grow, and make the Ench walk away from Tiny, you should notice how the attack cancels when the distance gets too great. This is the motion buffer range. I think this range ways 300.
 * But sometimes, an attack starts while the target is too far away. The motion buffer range does not cancel these attacks for some reason. But these attacks are coded to miss if the target is more than 350 range away.
 *  Bu3ny  (talk) 23:20, 15 January 2017 (UTC)


 * So it can be changed to 350 everywhere it's referring to the guaranteed miss chance of melee heroes? And also, it shouldn't be called "motion buffer range" in such cases (see e.g. True Strike), right? --Psion1C (talk) 23:27, 15 January 2017 (UTC)


 * If it's refering to the miss, yes, can change it to 350. And I don't know how else to call it. Valve called both motion buffer range.  Bu3ny  (talk) 23:35, 15 January 2017 (UTC)


 * Since you're saying they called both "motion buffer range", do you know where they called the miss thing like that (cause it's not called like that on the 6.84 patch website)? Ofc, if you don't remember where they called it like that, but you are sure they did, that would suffice as well. (--Psion1C (talk) 23:42, 15 January 2017 (UTC)


 * They may have not called the miss one motion buffer range. It's nameless then, I don't know.  Bu3ny  (talk) 23:53, 15 January 2017 (UTC)


 * So, I can remove "motion buffer range" wherever it's regarding to the miss? (primarily to avoid confusion) --Psion1C (talk) 23:59, 15 January 2017 (UTC)


 * I guess so  Bu3ny  (talk) 00:07, 16 January 2017 (UTC)