Fix your broken game, Riot

JuiceBoxP·3/16/2019, 4:05:22 PM·94 votes·21,855 views

"Learn to side step"

https://youtu.be/_PSOFzVu-ig https://imgur.com/XhOnjST https://imgur.com/tSfZBVP

https://youtu.be/GZEqBwQOpnE https://imgur.com/XoXnDkd

this all happened in one game there were more occasions on said game... i just didn't find them

https://youtu.be/4F88hGB4XNc https://imgur.com/920NyVO

https://youtu.be/9cfskBD4hbI https://imgur.com/l0jBVd7

[zombie-brand-facepalm]

edit: added 2 more

Special thanks to the trolls that took the time and downvoted every single comment i made, i appreciate the effort and dedication <3

120 Comments

Warwick Main3/16/2019, 4:51:31 PM36 votes

Try playing a champion with numerous bugs that have been present for more than a year. Even worse Riot is aware of them. 3 out of 4 of Warwicks abilities have some serious bugs:

q: Dmg not going off when vision lost but still using mana and going on cd, not being able to use the dash through units, dmg going off delayed as well as the heal causing you to straight up die and still do q dmg after death. w: pathing issues where you're in the blood trail, not in combat but still losing the bonus movespeed R: Dash cancels mid flight if enemies OR ALLIES summoner 4 in it's radius. This occurs 100% of the time. I've personally ulted THROUGH players who were feared happens rarely but still.

Not as bad as some champions whose numerous bugs have become a meme Mordekaiser but still utterly ridiculous that bugs are permitted to last so long.

14daysuspensionk3/16/2019, 5:48:17 PM28 votes

Meanwhile you can see Nidalee javelin do the opposite anytime of the day (goes fucking straight through targets often).

Jamaree3/16/2019, 5:30:24 PM15 votes

I think that the game works on hit and hurt boxes more then actual models so that is why.

Hypochondria93/16/2019, 5:26:35 PM12 votes

Thresh has a lollipop hitbox.

Xela Syab3/16/2019, 5:22:48 PM12 votes

There's a weird coding in animations and actions and it seems like some abilities take priority over others, I once ulted a Tristana casting her rocket jump and she continued to jump while in stasis glowing gold and everything. It's the same if you hook Ez with Blitzcrank, he can still cast his e mid hook. This is the same with Amumu and Leona, his q and her e latches on the the previous walking animation of where champions were and it still hit detects.

Fondling Gems3/16/2019, 7:45:49 PM6 votes

Actually those are all pretty reasonable hits; if you look closely every time you were hit Cait's current animation was making her lean away from the center of her hitbox, which doesn't actually change the hitbox location.

https://i.imgur.com/920NyVO.png[/img]

For example in this one you can clearly see where your last auto attack originated from. Cait leans back very far in her headshot animation, and you then input a turn command which swiveled your model around so that it looked like you were leaning very far away from where you had been standing when you hadn't actually moved.

Also worth noting that Pool Party slims down a model that was already pretty thin, but that doesn't change your hitbox size at all.

wolvius3/16/2019, 8:56:31 PM5 votes

I'll just quote a comment from previous threads on this issue that explain why this happens.

{quoted}

There's another example working against you in your Deadly Flourish example that you didn't replicate in your Curtain Call example: "Low Ground to High Ground"

As far as the mechanics of the game are concerned, League of Legends is a 2D game. The graphics portray it as a 3D game. This creates some visual dependencies - particularly in the case of firing skillshots from low ground (the River) to high ground (the lane or the jungle around the river). Skillshot graphics don't curve upwards and continue their path when they're fired out of the river, they continue straight in the direction they had been fired. As a result, the visual and the hit box are desynced every time a spell is fired from river to land (or vice versa).

Fire Curtain Call from the River and you'll likely see similar problems with the hitbox.

####from this thread https://boards.na.leagueoflegends.com/en/c/gameplay-balance/n4V0dLys-artrequires-hitboxes-to-be-fixed

Your saying how the hook didn't hit cait's model, as far as the game is concerned cait is a 2D circle on the ground that if intersects with thresh Q will be CC'd and then chain visually snap to a set position on the champ model, which is not the champs hitbox.

AeroWaffle3/16/2019, 7:05:56 PM5 votes

In the first video, the champion model is leaning forward while running. This does not mean the hitbox should be leaning forward as well. The screenshot you posted was not the closest that the blades came to your shadow, it practically was touching it as it first returned.

The thresh example is more obvious and easier to spot. Look at the shadows of the two things (champion and the hook). Just because the character model is higher in elevation and doing some sort of yoga pose doesn't mean that the hitbox is also going to float in the air and distort. It's going to move, yes, but it's all in a 2d environment and static in shape. Once those two hitboxes collide, threshes hook model snaps to the center of the enemy champion model for aesthetic purposes. Blitz hook is the same way.

The animation of the model doesn't have a bearing on what is actually happening for collision or ability interactions. Heck, the champion suffering in all of those videos has their own way of abusing that themselves. Caitlyn's E->Q combo wouldn't fire from the void if things were based off the model location instead of where she started the ability.

OneMustFall3/16/2019, 8:07:10 PM4 votes

Those Thresh hooks were money and right on the hitboxes.

Fail.

Sir Saltarin3/16/2019, 10:12:43 PM4 votes

That Caitlyn skin has some big thighs, that's why you get hit by the skillshots

Doombot3/18/2019, 11:25:41 AM3 votes

Thresh Q hit box is way too generous imo. It clearly does not connect but then just latches onto you because the invisible hitbox demands it.

DarwinTheory3/17/2019, 7:36:30 PM3 votes

Your mistake was picking Caitlyn.

If you picked Yasuo and posted this RIOT would have him hotfix by tomorrow.

I am Bardo Bard3/17/2019, 12:56:26 PM2 votes

I could rip out my hair how Bard's Cosmic Binding (Q) bends the rules. I should collect screenshots and the replay from now on, but when the stun does not count and "vaporizes" despite there is another enemy closely following, or stuns of extra long range that should not happen (even the binding visual effect was interrupted as the A and the B point was so large RIOT didn't intend it I guess) or, my favourite, the "Oh, let's don't stun in a line, but sideways" bullshit when you hit a Minion and a chmp is behind it, it will not stun the champ as supposed, but a minion standing LEFT or RIGHT to it, missing the champ.

So, hitboxes are shit in this game.

sphinxthelion73/16/2019, 8:01:04 PM1 votes

I wish I had captured the video of Nocturne literally walking through my q when I was playing Lux. He then killed me. I hit him squarely in the face. He walked straight at me. It went through him. He had no items to explain this. I died.

Also, notice no one from Riot replies to bug threads or customer service tickets anymore...