BUG CATCHER COMPILATION 2019
Вставка
- Опубліковано 6 вер 2024
- Compilation of all recorded bugs Sneaky encountered (or was involved in) in the year of 2019.
Disclaimer: some of these might not be bugs, but intended mechanics/feature.
Footage from: the entirety of 2019
▼Editor
/ snipinghobo
▼Time Stamps
[0:09] Bug #1 - Client: Audio
[0:39] Bug #2 - Visual: Some spell effects
[1:44] Bug #3 - (Old) Death Recap: false information
[2:10] Honorable Mention #1 - Mothra
[2:31} Bug #4 - Cassiopeia: Ult Hit Detection
[3:47] Bug #5 - Game Freeze
[4:13] Bug #6 - Karthus: Passive having unit collision
[4:50] Bug #7 - Spectator Mode
[5:00] Bug #8 - Client
[5:13] Bug #9 - Blitzcrank: Never-ending Passive Animation
[5:42] Bug #10 - Caitlyn: Recall Animation
[5:59] Bug #11 - Kalista: E icon doesn't properly show OoM
[6:14] Bug #12: Red Buff untargetable
[6:28 & 7:03] Bug #13 - Kalista: Silenced while mid-Q cast
[7:20] Bug #14 - Stats TAB: false information
[7:42] Bug #15 - Game Timer is not correct (wtf, how?)
[8:02] Bug #16 - Red Buff doesn't spawn in time ... or maybe bug #15 again
[8:25] Bug #16 - Untargetable Baron (or maybe unsync'ed spawn)
[8:48] Bug #17 - Ornn: First half of ult is... unusual
[9:11] Bug #18 - Client (seemed like he properly picked?)
[9:58] Bug #19 - Dragon Kill Announcement in the chat
[10:10] Honorable Mention #2 - Kalista: Charmed while mid-jump
[10:53] Honorable Mention #3 - Hail of Blades' tooltip stats is... impossible
[11:17] Bug #20 - Client "error" in pro play (LCS)
[11:51] Bug #21 - Visual: Bizarre Champion pop up
[12:09] Bug #22 - Visual: Black line appears on screen?
[12:31] Bug #23 - Client: Champion Select lobby chat dissapears
[12:49] Honorable Mention #4 - Client: Game Countdown delayed
[13:31] Bug #24 - Black Screened
[14:10] Bug #25 - Jinx: Invisible Ults (sometimes)
[16:09] Honorable Mention #5 - Morgana: Q Hitbox
[17:07] Bug #26 - Draven: Movement Animation
[17:19] Bug #27 - Nautilus: Ult's target indication
[17:42] Bug #28 - Client: Replay Crash
[18:42] Bug #29 - Yuumi: Partly invisible Q
[19:01] Bug #30 - the "96 AP" bug?
[19:32] Bug #31 - Baron icon showing on mini-map despite being dead
[19:43] Bug #32 - Client: black screened
[20:39] Bug #33 - Jhin: Shooting a blank shot (no damage, but proc'd Fleet Footwork rune)
[21:04] Bug #34 - Varus: Q insta-shooting backwards, instead of charging
[21:28] Bug #35 - Visual: Caitlyn seemingly passing through terrain
[21:53] Bug #36 - Qiyana: Ult's hit detection?
▼Editor's Added Music
[22:19] Windows XP Error Remix
▼Join Sneaky's Discord
/ discord
▼ Follow Sneaky:
Twitter: / sneaky
Twitch: / c9sneaky
#BugCatcher #LoLBugs #Sneaky
Mentions claw, but doesn't notice the smoke flying around everywhere 1:10
Color blindness has entered the chat
Yep that's his color blindness
caioxify You need Jesus
@@basselz8187 hed still see blobs on his screen
@@Zhiroh
Yes he does but sometimes it's hard to notice, if you go back to the first time with the akali bug you will see that he doesn't notice it right away
The scariest 'bug' I experienced this year was my antivirus telling me League accessed my webcam monkaS
maybe you use the webcam as your microphone?
@@IIIner0III it only accessed it once, in november, and I don't use voice chat, and on my laptop the camera and mic have 2 distinct names
monkaS
The butterfly was beautiful: The essence of the BUG catcher.
The Morg Q and other hitboxes are just features at this point
Kinda depressing but... True...
Its because of elevation difference. Morg stood higher than him, hitbox flies straight but the particles look like they shouldn't hit because they are higher up, therefore seemingly closer to the midlane than they were due to the perspective.
Specialties of Rito Games to spice up their game..
@@System-zu7np no, that was not going to hit him it shouldn't have. sneaky was not moving upwards, nor was he even in morg's Q line to begin with.
@@Bunkabusta73 System32 is right look at 15:12 in 0,25 speed and you will understand ~~
How many bugs are in your game?
Riot: yes.
the "missed morgana q" at 16:20 is really just the problem with having a height axis in a 2d game. The perspective makes it look like it misses but you can actually see that it's just "above" kaisa.
No, not even close
@@zacharyyiliang2417 That is actually exactly what is happening. League has always had trouble with this. It's a known thing.
They've started adding ground based rectangles to show the "true" hitbox to these kind of abilties like lux R, but theres a lot of abilities that still need it
League is a 2.5D game.
They should change it to be 3D at some point. The lack of a y-axis can be annoying at times.
Sneaky unofficial quality control riot team member since forever 😂 loves these anual recaps
*Annual :)
With the amount of Vayne he plays im surprised her tumble hitbox didn't show up in this video. It's pretty much been busted since release. Tumble animation registers in the game as a blink rather than a fluid motion... If a skill shot hits where you just tumbled from before your tumble animation finishes... it will still hit you even if it visibly looks like it should miss... Basically Vayne's hit box doesn't actually move from the spot where you cast the ability until she finishes the tumble animation... granted... the tumble animation is VERY quick, so it is hard to replicate this in game. I have footage of a few times where a skill shot that I 100% dodged with tumble still hit me because my hit box hadn't moved yet. I havent tested it recently but to my knowledge this was never fixed.
Riven's E works the same way.
He is so chill but gets so tilted with ghosting and bugs lmao
obviously - id take losing because someone is better than me, but im not gonna take losing because of some random spaghetticode D:
those untargettable red and barons is just cus his monster spawn animation seems to be disabled...
The Zac’s E animation bug is what annoys me the most. It’s been a while and still unfixed .
"Been a while"
That zac bug and being stuck in the air when you are knocked up has litterally been in the game for many years
@@ralleks true
Its been there since the champ was released in season 4
The last clip of Qiyana R was because when she ults in brush, it stuns, but keeps a hitbox similar to her brush Q, all blocky and rectangular, from point of cast (Qiyana's model) so when he flashed it, the hitbox was still next to her and he got clipped by it.
I recently got hit by the spell/damage category "Unknown" in new death recap - that somehow is a thing Riot
You just wait till you get killed by apheli :D That recap is suuuuper dumb.
I got hit by the removed summoner spell "revive", it's all fine.
I was more surprised that the summoner spell icon was still in the game data
My death recap says Vegiar moused over me and pressed R for 2000 damage when I only have 2000 health at max level... oh wait... that's actually in the game...
At one point i took 42 damage from NaCl. not quite sure what that was about but it definitely had the desired effect.
@@sclom5676 weird names are usually names of enemy that delt dmg
When I look up sneaky cosplays I get a huge bug: my heterosexuality is gone help
Pretty sure 21:05 is not a bug, if you watch in x0.25 speed his mouse is literally behind his character
But the animation of releasing the arrow started when his mouse was still in front of him, so it should've fired in front
@@derrickh.5902 the animation you're talking about is just an auto. He tapped his q after that. You have to look at the exact moment varus stiffens up for his q, since tapping the q is an instant cast. There are keys that watch the video frame by frame so you can see that the mouse was a bit behind his model when pressing q
21:20 You can see he activates the ability, then moves to turn around. Because the ability charges before it fires, he pressed the ability (starting the charge for a very short while) and immediately turns around. The ability fires off in the new direction, and then he moves to turn back towards the tower. All of this happens within the span of a few milliseconds, so it makes it look like it fires backwards.
Then, with the Qiyana one; it hits you him just as he flashes, making the game register him as being in the ult when it hits the wall, applying the stun. It’s no more different then being hit with any other form of CC as you flash or otherwise move. It’s hard to tell if that is a bug or if they purposely coded it in.
here's the issue with that though, Qiyana has two parts to her ult. The first is the knockback, the second is the wall stun. The lucian was unaffected by the push, but he still took the stun when the explosions happened. If he got pushed from the first part, I can understand a broken hitbox in that scenario, but not this one. That's just spaghetti code. The push is pretty long before the actual stun, too, as you can see. The stun begins as soon as the hitbox emerges.
What you say is true, he wasn’t effected by the push, but the game registers him as being hit by the spell. He got hit by the spell, flashed away (therefore avoiding the knockback) but was still treated as being hit into the wall. This isn’t a property unique to Qiyana, as many other champions with abilities like this (Such as Hecarim’s E) also act the same way. It could be spaghetti code, it could be an error in how the code is written, or it could be designed that way. We can’t know unless either A: a Riot employee tells us or B: someone looks into the code.
That is wrong. The Qiyana one is because the wave stuns if it hits bush/river. He was barelly inside the AoE of the bush stun. Its funny, a lot of people forget that Qiyana ult doesn't stun just on walls and then thinks the AoE of the ult is retarded.
OH he got me, there must have been a MIrrOR in front of me
hahah lost it
pretty sure it was the corner of the exploding bush at 22:00
Yes you're correct.
The hail of blades bug, isn´'t actually a bug, is a feature, when you reset autoattacks while you still have HoB buff on, those attack are included on the count and extend the buff duration (And Vi has 2 auto resets, so that's perfectly possible)
17:52 That happened to me too, but in-game several times over the patch cycle. Same thing through and through. Here's what I noticed about it, in case anyone wants to know:
So basically, the error message pops up behind the screen, and refuses to let you do anything until the box is clicked. However, the screen won't disappear no matter what. It's stuck there... but it's not interactive, it's just a window glued to your face. You're still allowed to alt+tab out and go somewhere, you just can't see anything. You can go to your browser, and click stuff like normal, but good luck seeing anything.
The only way to fix it is exactly as Sneaky did. You have to restart your computer. There is no alternative. I had it happen several times, until the new patch came and fixed it (I think, can't remember). This was the worst offender of crashes I've ever seen. I never want to go through it again. It's not fair to the people you're playing with/against that this ruins the game for you, especially if it's early in the game or at the loading screen. It sure as hell isn't fair to the person the crash happens to, because they have to wait until their computer restarts and log back into league (thank you auto-login) to have their game resume as it was.
F*** That crash for all it's not worth!
This happens in tons of games, and there definitely are alternatives to restarting. The best way is just to set your task manager to always on top, but you can also just click it while it's "underneath" the game or force kill the process with a shortcut.
11:07
its because her E gives an extra hail of blades proc so its just showing shes auto auto e auto'd before.
18:00
This crash here where the screen feels burned to the monitor, I've ran into that over 30 times already. But the way you have to fix it for me is either to literally completely reset the computer(cause it won't let me interact with anything else.) or keep another desktop open on windows 10 so I can open up task manager on that desktop while the crashed desktop window 1 stays in the background. Hopefully this helps next time. Peace.
That's not really a specific bug with league though, more so when a full screened application crashes it won't let you tab out. Because to tab to a different application it has to minimize itself out of full screen mode, which it can't do if its not responding.
zeek awesomecus i never said it was specific to league. This fix works with this happening to league or any other program. Which is kinda the point lol. It will be handy to know that if you already have windows 10, and another virtual desktop open, using the keyboard shortcut Windows Key + CTRL + Left arrow, will also help you immensely. As well as using the right arrow. They are interchangeable. These virtual desktops I don’t use often, but when a application does as you said, this remedies it in almost all cases of this happening.
@@purpledude1580 If it happens that often, set your task manager to always on top, that's a much simpler fix for the bug.
last clip wasnt a bug, qiyanas r stuns on bushes too and he was barely inside the hitbox for it
The Cassiopeia one at around 3:40, he took the damage while having only turned half way so the game saw it as a stun.
Well in that jhin skin he does have goggles. Maybe the glare of ult reflected on them and got you... its the skins fault
Untargetable monsters are caused by client-server desync. The client sees them as existing, but the server recognizes it isnt there, so the hitbox doesnt exist yet. This normally happened (I think it's a lot better now) when you alt tabbed or left and rejoined. I had it all the time where the map showed we had vision where there was none.
Varus getting hit by Cassiopeia ult is just latency. Client-side, Varus turns around immediately, but server side is a bit slower because the game needs to register information from Cassiopeia's player and you, so when Cassiopeia's ult goes off, your server-side Varus is still facing Cassiopeia even though the client-side Varus is not. This can be considered a visual bug.
21:48 "Did he E?" Yes Kayn E :P
In 3:03 when he is caught in cass ult looking back:
There is an option in-game that allows you to simulate "zero" ping in the game (it's used by some pros to get used to playing on-stage that has zero (zero ping in league = 8) ping. With the "movement prediction" option what you get to see in your screen isn't whats is actually happening in the game, that's why for him, he was already looking back but in the actual game he's in the process of turning around but still looking forward.
I think this gets worse with higher ping and would never happend if that option was disabled or he had sub 20 ping.
As I watch the video I've noticed that a lot of other "bugs" are due to that feature like the untargetable red buff and the kalista Q while silenced.
(in the options menu there's a advice that explain that feature just as I did)
Sneaky is the master of bugcatchers
11:05 That's not a bug, when you use auto resets (like Vi E) it adds an additional 4th auto to your hail, so the extra percentages are from that.
That might be how it works but it's definitely a bug because it should only be counting that as 1 hit, not 2.
@@TaIathar nah that's intended because you actually can get more then 3 hits with the as bonus active so you go over 100%
It's because basic attack resets doesn't consume 1 hit as the reset is faster than the basic with just more as
Was made so champs like xin vi jax don't lose dps while playing well with their kit
21:12 he moved his cursor behind himself as he cast it. Not a bug. Although they have had mouse direction delay bugs on a bunch of stuff at some point
the one where the cait walked threw a wall 21:40 is not a bug thats actually possibel or at least was and vandiri proved that on his yt vid
Well even if it's possible it's still a bug as it should be a WALL
@@gashferohira2635 Its not a Bug its a Feature
I like how bug #18 is just titled "Client". What a good summary of league
at 21:08 you just moved your mouse ever so slightly behind your character the moment you pressed q, slow down the vid to see what i mean
6:04 This is not a bug. Kalista can Rend with no mana. It’s a mechanic. Her E consumes mana when used but if you don’t have enough mana it just consumes all you have.
-Veigar's stun is the stupidest thing in the game because if you are anywhere near it, it counts as Veigar getting an assist even if you never got hit by it. I want to believe it's a bug, but I'm pretty sure it's intentional in the worst of ways
-Hail of Blades percentage is intended because of the attack reset giving more than 3 attacks of HoB
-Qiyana ult hit the bush, so it exploded there, and the hitbox is way too large, so it hit you, even though it 100% should not
I really like the windows error sound remix at the end lmao
gotta love how half of those bugs are with the client
The hail of blades thing isn't a bug. If you use an auto-attack reset during hail of blades it extends it by 1 attack. Darius was going Auto > W > Auto > Auto. An extra 1/3rd of procs makes it proc 133%.
Edit: It was Vi. Still, it's Auto > E > Auto > Auto.
Oh damn didn't know Sneaky listens to Ben Bohmer lol, I was like wait did I left my playlist on?
17:45 Ben Bohmer - After Earth
I love when he went from WAIT WHAT RIOT to guess im dead :)
When the client randomly kicks you out of the lobby and promotes you to grandmaster lmao
That line on the screen I have constantly on tri brush on top lane, lol
18:12 is pretty easy to fix. Just Alt+Tab to the error message tab on the left, press Tab and hit Space. That will close the error message, the client will shut down and you can quickly restart.
Riot gamedevs: Thats not a bug, thats a feature :)
10:53 auto resets give one more atack with hail of blades.
meaning that akali had utilized hail of blades perfectly with 3 hits + 1 reset every proc. still impressive.
Sneaky: how many bugs can u show me?
Rito: Yes!!!
Watching this video while I was queuing for a game, and it wouldn't let me ban and forced me to dodge. RITO COME ON NOW.
Sneaky seems so different nowadays lol, I think now that he just streams 12 hours a day he seems wayyyy more chill, I do really like it tho lol
Imagine trying to run League and literally anything else at the same time and not expecting one or the other to crash. It's honestly digusting lmao. Especially Firefox or Steam VR
Sneaky: how did that hit? i was turned around!
Me: You must have forgotten, Jhin has eyes in the back of his head, therefore he isn’t immune to Cassio ult by turning around.
133% is possible, because attack resets do not consume a stack of hail of blades, they do however benefit from it, so attack resets can give you more procs of hail of blades than the total you should have. 4 out of the possible 3, gives you 133%
So as far as visual bugs go, ive noticed this bug for the past year maybe longer where there's a black dot following my champion near the bot lane tower as i start walking back bot from the fountain. Happens every champion. Edit: that morgana Q isn't a bug, it's the elevation difference of the map when you are in river. Hella stupid, I know.
The Varus Q wasn't a bug though
he tried to charge it too, so it was
16:12 is a combination of the camera angle and the high ground altering skillshot thing. It's dumb but that's the reason
the qiyana ult isn a bug, he just got stuned with the bush element not the wall
i feel like theres a conspiracy where sneaky messes with his computers clock to make weird things happen on purpose
That qiyana thing wasnt a bug, it stuns when it goes through grass too, you can see the little hitbox on the ground. He was unfortunate and flashed into it
21:22 that didn't look like a bug, he put his mouse barely behind varus
the last one wasnt a bug though, he was hit by qiyana's ult while in the brush
What bug 7# at 4:50 ? I don't get it
It shows lucian moving towards the enemies (which is not really happening)
@@vmamarcucci thanks I'm blind
I honestly thought that this was gonna be a small compilation of sneaky getting oneshot by kha
i thought theres one where he is statikk shiv by dragon?
What game is he playing in the first clip?
Path of exile
Well shit I just woke up and I see a new sneaky video uploaded 8 mins ago. Perfect
@4:20 is jhin passive flower explosion.
what's the game he was playing on the start of the video?
lol #18... maybe don't wait until 0 to select your champion, and -2 to hit lockin lol
Smoking on some sneaky OG
The last clip wasn't a bug, qiyana ult cc works on bush too
the ult only stuns if you are inside the bush, but he flashed
@@ene01 that's the hitbox i men that is not a bug
Last clip wasn't a glitch. Her ult explodes bushes it touches too, and he's pretty clearly in the spell visual
12:00 New fiddle lookin' spooky
Get your hot spaghetti code here bois!
About that invisible jinx, how the fuck did the ult come from the base, and then jinx walks out from mid? :o
Whens the last time sneaky reinstalled league and when is the last time he re installed windows lol
I feel like sneaky had his pc clock desynced to cause bugs for the memes
Did you catch the bug on Jay3 though?
Great compilation sneakers
4:20 is Jhin passive trap from killing karthus, unlucky
12:38 scared the hell out of me...the greatest bug ever
Sneaky looks pretty still wtf
whats the music at bug 6?
And this is just one person and so many different bugs
36 bugs in a year of constant playing is not a lot at all. Plenty of people on YT make gag videos showcasing more bugs than this in big name titles like MGS and AC after playing them for less than 100 hours. People just think League is overly buggy because they play it so often.
@@longlivenc7235 There is lot of bugs . Evrytime they reliese new patch there is new bugs. After latest one there was big problems and ppl couldnt see chat at all.
Its still just pretty much one map and 150 champions (some been there 10 years already)
@@penapenanen5116 There are lots of bugs in literally every modern game. You're moving the goalposts from your original claim. And you're contradicting yourself as well. You're trying to argue that the map/champs don't change while also telling me bugs come with the regular patches that change them.
@@longlivenc7235 i witness different bugs evry week on game or in client. Sometimes two on same day. Its still 2 little maps and new client that is hella worse than old one.
I've been recently getting a bug about 3 times a game where the client just closes forcing me to leave game and having to reconnect losing around 2 mins
It's worse on PBE.
This is actually funny how he reacts to them
Sneaky is the best
Man I was preparing for a kha'zix montage from the eyes of an adc main.
What game was that at the beginning. Diablo?
Path of Exile, aka Diablo on steroids
karthus unit collision = jhin trap blossom from karthus death
2:15 song?
Nobody:
Sneaky: "WHAT????"
is this an NA thing, I dont see that many bugs in LAN.
Wait a second sneaky listens to dance Gavin dance? 8:35
New job offer incoming from Riot : QA (Quality Assurance) :D
last one with the qiyana isnt a bug the bush explosion got u
Kalista seems to be a theme
what's this game in the start of the video??
Path of exile
That recorder fail one was painful to watch. Alt-Tab + Enter/Space woulda cleared that error and closed out of it
4:27 isn't a bug. When jhin kills someone, captive audience trap slows everyone near the death site
The bug isn't that he was slowed on Jhin's trap, it was that Karthus' dead body was bodyblocking him in passive.
What game was he playing in the first clip
Path of Exile