Q
Q
Q
Q
W
Like.... You could build a five story parking garage with the amount of space that is sometimes between you and these abilities landing. If it doesn't visually connect with my champion, it shouldn't hit, end of story.
Nayzumi48 votesYou forgot 
Q. He's the worst culprit.
Sraeg201347 votesAt least it's a big-ass anchor not a fart of light or a drunk who is so fat he has his own gravitational field.
Steelflame9 votesGragas's E has a far more fair hitbox now. It lost an astonishing amount of it's hitbox, a grand total of about 40% of it's total hitbox IIRC.
fox only fd4 votesTechnically all matter has a gravitational pull. Hate to ruin your fun, but science.
PapaGreg211 votesI have played hundreds of Naut games and I can confirm there is an invisible extended part of his hook that reaches that extra inch that always grabs people. On the flip side, Riot nerfed him to the ground last season so I don't know if he is bothering anybody right now.
General Esdeath 4 votesIt's a tiny Naut hooking someone from the end of his hook, hence why the CD is reduced for hiting a wall. The tiny Naut does all the work.
e46 Fanatic31 votesYeah these issues have gone for too long, I've even got a few vids of what I think to be hitbox errors. Some of these I took months back but same stuff as today
In this first one you can even see where clearly the varus Q went in the same path as Lux Q but only the bs lux hitbox hit me https://youtu.be/xmoK-yiR4K0
this second is lux's ult (hit but no damage) https://youtu.be/MGr-KJYuFp0
the lawd knows this thresh q was supposed to hit sivir https://youtu.be/ZR9u1CpqD1A
Gragas bodyslamming people from behind https://youtu.be/fQLkupeh0qU
this one is questionable, possibly actually hit me https://youtu.be/-rSVoJZHfeg
CloakAndGrenade19 votesThat last one definitely did not hit you lol.
FreshAsFebreze3 votesYou sir, are an awesome video maker. But, with regards to Blitz, I dont think Riot will ever change that hit box......cause ya know.......#plays
Steelflame6 votesThat lux ult wasn't a hit though. It clearly went between both Azir and Ashe. The only reason it looks like it should have hit is the perspective makes it look like an overlap, it was clean down the middle of them though if you follow the red line (which is what the actual center of the hitbox is).
e46 Fanatic2 votesThat lux ult wasn't a hit though. It clearly went between both Azir and Ashe. The only reason it looks like it should have hit is the perspective makes it look like an overlap, it was clean down the middle of them though if you follow the red line (which is what the actual center of the hitbox is).
I wouldn't say clearly... Possibly? sure There's a reason I stopped walking in-game(where there was a better and more clear perspective) after it happened because I was like 'wtf'. Maybe I'm trippin.
Final Spark Lux26 votesWhile I do agree that skillshots can be buggy at times, I don't think it's that straight forward. Latency on both sides can effect the way things seem. I've had instances where my skillshots have traveled perfectly through the middle of an enemy, only to not hit them completely. I thought it was a massive bug, but upon watching the replay, I realized I had in fact missed my target altogether, and this is with me sitting at a stable 50~ MS ping.
The point I'm trying to make here is things aren't as clear cut as they seem. We also can't take into account just how big / what shape a champions hitbox is / spell is with accuracy. The way things are coded (I believe) are if 2 hitboxes overlap even slightly, it counts as a hit. Since we have no indication of actual champion / spell hitboxes, it's hard to accurately say that any of these should be considered hit / miss. Just my 2 cents.
DemonBoneJangles4 votesthen there should be an option to turn on hitboxes, at least for your team so you can see if an ability connects with you or not
lofi n chillhop1 votes[{quoted}](name=Final Spark Lux,realm=NA,application-id=3ErqAdtq,discussion-id=lyRMpnva,comment-id=0003,timestamp=2017-12-17T21:05:34.060+0000)
While I do agree that skillshots can be buggy at times, I don't think it's that straight forward. Latency on both sides can effect the way things seem. I've had instances where my skillshots have traveled perfectly through the middle of an enemy, only to not hit them completely. I thought it was a massive bug, but upon watching the replay, I realized I had in fact missed my target altogether, and this is with me sitting at a stable 50~ MS ping.
The point I'm trying to make here is things aren't as clear cut as they seem. We also can't take into account just how big / what shape a champions hitbox is / spell is with accuracy. The way things are coded (I believe) are if 2 hitboxes overlap even slightly, it counts as a hit. Since we have no indication of actual champion / spell hitboxes, it's hard to accurately say that any of these should be considered hit / miss. Just my 2 cents.
the map angle view also effects this, and so does your elevation - especially noticeable with river's dip and bases' rise.
I feel both these could be improved tho - but these three main things - elevation, view angle, and latency have significant impact on hitboxes.
things like gragas body slam, and skill shot box sizes matching the spell's effect size, however, are things that need to be fixed.
invisiblecat17 votes
E
Sometimes I will see people walk over it, while others walk next to it and get hit
Master Noct1 votesOne ARAM I had dropped a Zoe bubble to the left hand side of a turret, three people walked over the edge of it and nope. Nothing.
But sometimes I hit people with it a Teemo or two away from the area it's supposed to work in.
My Heartshaker6 votes is the worst offender.
I swear to god his Q range is about 1.5x longer than its indicator
Z3Sleeper5 votesHonestly the hitboxes don't need to be fixed. The visuals do.
Northmund5 votesZoe E, Lux R, Ashe R, Amumu Q, Le Blank E.
strut4 votesI would honestly be more excited for a patch of hitbox fixing than a new champion
Kushinada3 votesForgot Ashe/Fizz ult, though Riot said something about how the skillshot will target the closest target in the vicinity if the skillshot reaches max range (or something like that)
underscores22214 votesFizz's fish was a special exception, where if it missed on the skillshot path, it would land and if someone was in "pickup" range of the fish, it would snap to them. Since the "pickup" range was bigger than the skillshot width, this caused some interesting problems.
PopcornBunni3 votesThis is a functionality of all projectiles, not just catches. Probably to do with lag compensation and hitbox interpolation that leaves your character's collision bubble one frame behind every movement; It's a common methodology to make attacks connect in favor of the attacker in games. It's just more noticeable with roots/pulls because you get hit with a long cc when it happens. 
and other instant or near-instant hitboxes showing up for just a few frames all have the same hit situations as the ones you mentioned.
Daddy Ants3 votes
Q
LegitBusinessman3 votes Q Is a big offender as well.
Glory ln Death1 votesSion's Q isn't an issue at all. The problem is with how champion hitboxes work. Because his Q indicator lies along the ground, people naturally look at their champion's feet when trying to get out. However, that isn't where your hitbox is. Your hitbox has to encompass your entire champion, so if your arms/shoulders/belly or whatever are wider than your feet, your hitbox is, as well. That's why it looks like you're just outside of the indicator, when you actually aren't.
SuperRiceBoi3 votesYou forgot R.
Hehe Lux misse- RIP Rito Game plz fix.
Also, how can you admire the outbox for the 
R. Not only when it misses you on the side, but also that feels bad moment where you are in between the blades according to the animation but still die.
4262873 votesThe answer is always 
ChuShoe3 votesJhin's W hitbox is pretty clear to me
Wafflè2 votes
he's the worst one
Sraeg20132 voteshttps://screenshots.firefoxusercontent.com/images/5af8d35f-a719-4050-afb2-c3ea583566a5.png
Actually that game was a fucking gem.
I had people in the middle of Kayn's W not getting hit whatsoever at least twice.
FaZe lllllIII2 voteslux hit boxes are perfectly fine you jsut have a shitty connection
I play on 16 ping so I know much better than you
Barkley5 votesI play on 8-15 ping (chicago) and I can tell you lux hitboxes are bullshit.
FaZe lllllIII1 votes[deleted]
Barkley10 votesAh, the old "someone made a point I can't argue or disproved a point I made so I'd better bring up their rank to make myself seem superior" move.
A classic.
FaZe lllllIII1 votesAh, the old "someone made a point I can't argue or disproved a point I made so I'd better bring up their rank to make myself seem superior" move.
A classic.
beginners get disoriented in the action but I perceive every slight movement accurately
so actually yes being a superior player + borderline korea ping > people saying "WOWOWOW the 40% win rate lux hit box is SO op"
lux is a wheelchair tier champ with unlimited counterplay and I have no problem going entire games without being hit by a single ability of hers I also know just how easy it is to dodge her stuff when I play her in high elo vs good players and they dodge mine
Barkley10 votesThe superiority complex is strong with this one.
LiL Bunnie FuFuu4 votesGold isn't low elo You have no argument You are an asshole
Sexy Jack Rabbit2 votesJhin W is the absolute worst.
When he first came out I thought he was able to move during it's cast, hence why it always hit me in such a bs way.
Athenes Lulu2 votes"but we want players to feel good about landing skillshots by lollipopping those!!!!!!!11111" -riot
Though Jhin's is a weird case with elevation, where from one side of the map, his hitbox is super weird and extends to spots that you don't want to touch but touches anyway, and from the other side it doesn't always touch when it should.
Pinkaj2 votesI'm not sure about Nidalee's spears. I've seen them pass through champions without damage, even though the hitbox says it'll hit. By through I mean it passes over their shadow. Tails don't count.
RainbowIcee2 votesHitbox are one of those things you can't expect them to ever fix. As time goes on i only expect more culprits rather than fixes.
EssenceOfPoo2 votes
Faceroll Tactics1 votesDo you want to code the new hit boxes for riot?
Everything is a circle, if you don’t like that too bad because you’ll have to rewrite so much of the code to make it not so
Whisper871 votes[{quoted}](name=Faceroll Tactics,realm=NA,application-id=3ErqAdtq,discussion-id=lyRMpnva,comment-id=0021,timestamp=2017-12-18T12:23:47.029+0000)
Do you want to code the new hit boxes for riot?
Everything is a circle, if you don’t like that too bad because you’ll have to rewrite so much of the code to make it not so
Is it really a lot of time commitment to make an irregularly shaped hit box? I don't understand why the data determining where graphics appear and the data determining where the hitbox is can't just match pixel by pixel. Like whatever engine/algorithim you are using to tell the system where to make the champions look like they are, just copy and paste that to inform the system where the hitbox is too.
AdeBug1 votesand if a piece of a cape or hair flutters in the wind as its animation shows, you really want that to happen to the hitbox? :D
?
