I have taken so many Nidalee spears because of broken hitboxes. Try letting a spear go right past you really close, it'll sometimes hit you. You'll be like "HA- wait, what? FUCK!" It's really annoying when you take a 1000 damage that you shouldn't have.
Deep Terror Nami1 votesYou're concerned about Javelin width after its width nerf?
Woodakoodashooda1 votesThe concern isn't its width. The concern here is the hitboxes themselves, which are invisible and, depending on certain animations and visuals, can cause players to take or miss skills that should have either landed or missed because the plays can only be based on what is seen.
Take skins for example. Some skins make a champion smaller than their default without changing the hit boxes, but players will still take extra time aiming at them and will miss an additional 1 out of 25 times.
Deep Terror Nami1 votesIf you're talking to me, I was indeed referring to the hitbox width. I'm very well aware that hitboxes don't match the visible object/animation (otherwise is unreasonable in a top-down game like this).
Riot has 2 options if they wanted to make them match [for javelin];
Both of those cause a really stupid problem;
wolfax2 votesThey already reduced the width. There are always going to be a few rare cases where it looks like it shouldn't have been a hit. Honestly though I really don't see blatantly wrong hits all that often anymore after the changes though.
Deep Terror Nami1 votesI know, refer to the other comment below. I'm meaning reduce it further, which is ridiculous.
SmokingPuffin1 votesNidaspear width is pretty accurate right now.
If you are taking damage when you think you shouldn't have, the most likely problem these days is in the netcode. Your client estimates your position on the server, and periodically gets updated with your true position. It can easily happen that the client is wrong about where you are, especially if you're near other mobs and collisions happen.
The error won't be large, but even 10 units is enough to make you a sad panda.
