Originally Posted by Statikk

We actually finally got a recent consistent reproduction of this bug internally, so we can finally throw resources at this to try and fix it. This fix will not solve that problem, though hopefully we can get an engineer to look at it sooner or later once their hands aren't tied up.

Originally Posted by Wiksy

Some additional context on this: We found out that previously the math was flawed in that a champion's model size was taken into consideration only if the missile was hitting from the side, but not from the front. This means that previously if you shoot a skillshot right at an enemy, it would only hit when it hit the center of the target; but if you aim it at target's side it would hit if it touches the target's bounding circle. This was pretty inconsistent.

We changed it so that it will always use the target's bounding circle, but this means the potential reach of a skillshot is extended, and we have to slightly reduce the range of skillshots.

Originally Posted by Statikk

We actually finally got a recent consistent reproduction of this bug internally, so we can finally throw resources at this to try and fix it. This fix will not solve that problem, though hopefully we can get an engineer to look at it sooner or later once their hands aren't tied up.

Originally Posted by ßlaze

cool, Bigger target easier hit, Nidalee FTW.

Originally Posted by FeralPony

It is all calculated on a per-character basis. Skins do not impact this value. All skins will behave the same in respect to being hit by skillshots.

Originally Posted by Statikk

We actually finally got a recent consistent reproduction of this bug internally, so we can finally throw resources at this to try and fix it. This fix will not solve that problem, though hopefully we can get an engineer to look at it sooner or later once their hands aren't tied up.

Originally Posted by Statikk

We actually finally got a recent consistent reproduction of this bug internally, so we can finally throw resources at this to try and fix it. This fix will not solve that problem, though hopefully we can get an engineer to look at it sooner or later once their hands aren't tied up.