UPDATE: Around 2 hours ago Zyra got disabled, and right now she is playable again. Riot has managed to successfully HOTFIX her. The other champs are still bugged, but it's good to see the worst one hotfixed so fast. I'm still hoping for this Baron feature as a whole to be fixed, but that definitely needs more time.
Well to be fair, the spaghetti is so thick that numerous small bugs just get ignored because they presumably wouldn't be impactul. Turns out sometimes, they are.
I mean last I checked, that one bug that has been around for literal years aka the space x launch bug is STILL in the game. Its even shown up in tournaments and they won't fix it.
@@mr.someone5679 fixing bug doesn’t make the game more fun. And also sometimes noobs aren’t aware of bugs. So you can easily beat them by exploiting bugs. I am totally okay with it.
Riot is just negligent. Plagiarism, laziness take your pick. They don't care about the game anymore because people will not stop opening their wallets for them.
Unfortunately posting any bugs on /r/leagueoflegends is not allowed these days. Considering forums also got removed, we can catch much less bugs than before.
@@Vandiril Look at the bright side. It's more content for you to made. But I do question the game longevity if this kinda of Live bugs keep happen too often like this
I was just thinking this and I agree completely, the moderation on r/leaueoflegends is such a joke. Its even against the rules to address Riot in a post. No exaggeration. They shut down conversation so often and there's no hope in sight...
I remember the times when vandiril used to upload twice a month and only from pbe. Now all his uploads are from live servers and often he often posts daily. It's gold mine for vandiril, but it's laughable on riot's part.
Back in the day I still uploaded a lot of videos, but way less bug related I'd say. Had plenty of videos from other gamemodes, customs shenanigans, but most of it is simply not possible anymore (sadly). At least Riot is delivering when it comes to bugs, I guess? x)
@@ПОТРАЧЕНО-я1з naah bro community is like, ahh its on pbe, its supposed to be working 100% then wtff no bugs, haha i cant about this community, pbe is supposed to find bugs jezz
Considering Riot hotfixed Zyra but not the others, I can 100% guarantee that instead of finding out the core issue causing this bug, they just added some spaghetti code, like adding an invisible Teemo in the baron pit that checks if it's hit by the Zyra ult and her current distance, and if she is too far away it reduces the damage by 90% or something, and it will come bite them in the arse in another patch.
😂 though tbf, it’s possible this bug is some architectural problem, which in the very worst case means completely rewriting league code from scratch to properly fix, so you can see that an invisible teemo in comparison does not sound so bad
Doesn't matter. they're a billion dollar company, they get paid to provide a properly functioning game service, if they have to completely rewrite the codebase, so be it.@@rshackerpro1
Thing is, I hadn't even seen it used like that enough to realise what it was about. I think i saw it literally twice and just thought the person mishit a different ping, then riot removed it.
better yet, their solution to abuse in proplay is to just tell the players "hey dont pick XYZ champion, else we'll fine you." instead of, yknow, just fixing the problem.
@@internetgamer2My philosophy on this is really just use everything in the game. Riot is constantly patching the game, if they don't want something in the game then they can fix it. The pro play would also be more entertaining this way.
Ever since I obtained it, Gun Goddess Miss Fortune's taunt doesn't trigger its voice lines at all. She does the animation, but doesn't trigger the lines. If you do something that does trigger another voice line she'll immediately say it, so the taunt's audio trigger is just broken instead of muted because of other voice lines immediately doing it.
Nunu and Willump Bot is similar. The laugh emote triggers the animation but uses the taunt voice line. Game breaking bug because spamming Willump Bot laugh is the best part about the skin.
there were bugs in tournaments, even worlds, that didnt get fixed, because they arent frequent enough. unless a bug is ruining every game they just wont bother.
Friendly reminder that Mordekaiser had 200 Bugs, many of which were quite significant like his 3rd Q doing no damage when W reactivated, and Riot did not touch him for 4 years straight until they remade him.
I wonder about all the Varus Q Baron steals from worlds 2022. Does the bug even affect Varus and was it in the game that long ago? Throws so much up in the air
I doubt the bug is this old, but in season 4 or so i was a janna otp for 3 months or so, and i specificaööy remember stealing multible barons with qs from downtown. Tbh that can probably be put down to being silver or gold elo back then
I think the worst part is that this bug can easily be done unintentionally. Like, I can see a Zyra just dropping an Ult in the Baron pit because she expected the enemy to be there and walking away because she is alone and suddenly BAM, she has the Baron buff.
imagine Zyras on red team, they lost a team fight but theyve got a ward on baron, they see the fight happening, she walks over to ult and be annoying, the blue team Bard puts a portal on the wall so everyone can go through and kill her, shes caught all alone! she instantly flashes over the wall to red buff and Baron loses 8000 hp in a heartbeat. red team goes on to win the game, because Jax was splitting bottom and now hes got baron minions chomping through the blue base. Zyra could be banned for bug abuse, when she didnt do anything weird or strange, the baron just happened to unalive itself and she got credit for it.
When I quit playing myself and now just watch streamers sometimes, I've noticed tons and tons of random little bugs in the majority of games. Stuff like skill shots going directly through champs, abilities not working how they should, items not proccing, tower and minion aggro being mega wonky etc it happens way more than you would think. It is hard to notice while playing, but on RUclips I often slow down the speed to .25 and it is insane how much is broken in this game. I could never take it seriously again like I used to. Game is too competitive to be this broken and just feels like a waste of time.
i thought the no damage bug was just a feature put in to prevent you from taking camps behind the spawner because whenever id place an anivia ult in baron pit from behind the wall it would do no damage i had no clue it was part of a larger bug with baron
One thing I do want to mention is that some bugs can be ridiculously hard to find and fix. What Riot should do in those cases, is tell the players that the bug is at least being looked at. that would be infinitely better than saying nothing at all
The problem is, they don't even have to find the bugs. All they have to do is watch youtube content like Vandiril's videos, and then go about fixing what he finds for them. Instead, they do nothing, fix nothing, say nothing, and just expect people to keep playing their trash game
@@joefoulger3510 With finding bugs, I wasn't speaking about what the players see, but the location within the code itself. It's not that easy to figure which line of code causes things that you didn't intend to happen. I do see why it may have been confusing with the way I initially said
Generally, if something is reproducable, it might take some effort, but you *can* find the cause with a bit of time. When there's no reliable reproduction, it might be next to impossible. But a reproducable bug that can affect game outcomes this much (even the original no damage bug) and will easily be triggered in normal gameplay staying in the game for 10 Months really is not excusable.
@@LwL_ I'm not saying this situation is acceptable. You're definitely correct regarding the bug being reproducible. I would look into code regarding distance in conjuction with damage, but with thousands and thousands of lines of code, that could still be incredibly difficult to find. All I was suggesting is a bit more openness from Riot on whether this bug is even being looked at or not. Now we don't even know that, which inadvertently suggests it's being ignored
@@messorix2033 Sounds rather easy to find, as the dmg calculation won't be thousands of line of code. Since it is reproducible, any debug mode should just be able to look at those damage instances and whatever triggered them. Wouldn't be surprised though, if rito didn't have such a debug mode.
@@dabioji7096 I hate his entire rework. He was so much fun before. They gave all my favorite champions shitty reworks. Galio. Yorick. Morde. I quit playing after they all got turned into dogshit
I have to assume this has something to do with Baron being cleared from an ability's "already hit" list? It looks like the abilities are hitting multiple times. The range that this bug occurs at might be Baron's de-aggro range (outside of which he'll stop attacking you and begin healing). Maybe part of the code that handles the initiation of his "de-aggro" is somehow clearing him from these active hitboxes?
In that case you wouldn't expect abilities to not deal damage at all, or maybe no damage for Rumble's continuous damage R, but Ahri's Q should hit multiple times as well. Lee and Rumble are both somewhat old champions that haven't had a significant rework, so I doubt it'd be just an issue of old code and new code breaking each other.
@@La4geas I'm guessing continuous damage hitboxes like Lissandra R and Rumble R are just a hitbox that keeps deactivating and reactivating. It seems like any hitbox that is activated after leaving the range doesn't work. For Ahri Q, maybe it has something to do with the damage changing to true damage on the way back.
@@groggylark4876 Ahri's Q and Q2 are functionally 2 independent spells but yes it does appear to be an issue with Baron's aggro/leash range, as the moment Rumble is close enough it starts doing damage but does nothing when hes far away. With Zyra it seems its continuously checking if a target is in the hitzone (presumably for Zyra's plants to get buffed) and as Baron is resetting many times per second since there is no valid attacker/target in his range, its also resetting Baron's interaction with the AoE? but the thing that confuses me is this behavior would logically behave normally if any champions other than Rumble/Zyra etc. are near the Baron but as shown with the lee Q and the dummies behind Baron this isnt the case.
Im pretty sure Riot does'nt even understand how the game works. I remember hearing something about them having problems understanding the really old programming/code used for league. I think they have reached a point where they should just redo it compleatly in order to have a bug free game/client again.
The latest dev blog they said they are transitioning to windows 8+ etc. so they won't run on older systems meaning they should be able to redo the code for newer OS.
I'm pretty sure it has to do with like projectile property and fog of war. Like hecarim heimer and ashe dealt dmg according to the number of missiles that hit nashors. But for zyra and Lee sin their abilities check multiple time sending multiple missile since it's old abilities to check if poeple should get hit or not. He talked about how he used missiles to check for hitbox on vi's Q for example
It definitely seems to be that, in the cases where present, being far enough away from baron prevents abilities from not multi-hitting when they're supposed to not multi-hit. It's interesting Zyra and Lee Sin's abilities that trigger this both have hard CC attached, which Baron is innately immune to.
I wonder if this sort of too far away inconsistency was originally intentional from league devs to free up resources and prevent abilities from using excessive cpu time trying to calculate something that doesnt matter, but they forgot about it and now instead of not showing a scx when its not on your screen it instead impacts how much dmg something deals if it deals any at all because the game is guessing what the effect is supposed to be, due to using less resources to guess. While this mightve been fine 10 years ago, it probably should be fixed today
There’s a minor bug rn where if you buy an item with a unique passive twice by accident like an aether wisp and then refund it you lose unique passive entirely
I'm gessing the initial intention was to make global baron steals look more impressive. Probably to make it more hype for spectators of esports, but implemented as an untold mechanic. However, with the coding of so many abilities, it seems like some do more damage then they're supposed to while others don't at all.
As far as rumble ult not hitting baron when far away, I thought it was because baron's health regen is high and constant if no enemies are close to it.
IF you paid attention to the video, no damage numbers showed up AT ALL from the rumnble R. So it isn't because baron was out-healing it, it wasn't doing any damage to begin with.
There's also a yorick bug, happened to slogdog earlier. So the what happened is yorick dies and he or the maiden or the ghoul destroyed the nexus tower, and then the maiden didn't die.
heimer and cassio have always been known to do increased dmg on nash, heimer with the turret and staying out of range, and also the nash debuff mecanic that cassio avoided, or even the yasuo wall preventing nash to apply said debuff, it may be a bug, but it's been played around for years.
That looks like an optimization that has a side effect rather than a straight up "bug", so my guess is the fix is probably far from trivial as it would require them to question things much deeper than the actual issue in order to solve it.
There has been a pixel wide gap underthe back button on the UI for as long as i have played so i wouldn't hold my breath about them fixing anything if they can release another lux skin or rework jungle again instead.
This bug looks like what they did to stop jungle pets from hitting epic monsters when doing scuttle. I remember a time when if you hit scuttle when it not far away from herald, the pet hit the camp, but didn't aggro it to the champ who had the pet. So you got double pet healing. Riot probably added a thing to champions that make you not be able to damage epic with your jungle pet, but a bug had it accidentally bleed into certain champion abilities. Probably ones that would trigger the pet to hit a camp outside of the range believed to be what the pet should be hitting. Ekko and sivir Q probably works like go from A to B, then from B back to character. While for ahri it's probably just go forwards then back to the character. Similarly, currently on live servers, it looks like your jungle pet can only hit one camp at a time. So it's probably something to do with stopping the pet from interacting with far away jungle camps (or just when far from epic monsters), but for some reason also affects certain abilities. The abilities that benefit are ones that are "secretly" checking for any changes to their status. Ashe and hemier missiles dissappear upon hitting something. Mord's E is checking is someone in range to pull, hecarim's ghost horses are probably a type of clone that's checking if there is a unit it needs to damage and pass through with ghosting. Zyra's R is checking who is about to be knocked airborne. Maybe this even works with Aatrox W, Cait Q, Jinx W, and Azir R.
I feel the need to go back and watch old rumble vods anywhere I can find them in the last season to see if he ults baron from range…. It probably happened in pro play already…..
Normally ashe w fires multiple arrows however hitting multiple arrows on a single target deals no additional damage, it seems when far away , this rule becomes inactive, allowing for more damage than usual. something similair happens with all other instances.
i'm confused from a mechanical standpoint... walking away must change something about Baron's hurtbox... but nothing i can think of would cause these results. 1) maybe Baron's hitbox is blinking... causing Zyra to hit multiple times, and Rumble to miss. nope, because then the projectiles should work at least sometimes 2) Minion vs Champion? nope Rumble's Ult and Zyra's Ult damage minions. 3) Both? nope, projectiles should work it has to be a ID thing... which League shouldn't even have more than 4 hurtboxs. (Minions, Champs, Walls and Gwen) and 3 Hitboxs (Projectile, Non-Projectile and unErasible Projectile) but no combination fits these results.
I hate how negligent Riot are to fixing bugs. Sometimes the launcher crashes and you can hear champion select after loading into the game, or the fact that I get a notification about new tft season every time I open a tft lobby, even after playing tens of games, same for arena, or the fact that sometimes in game you have no sound of aa/skills, lock in button at the same position as the show/hide champions (multiple times I've accidentally locked a champion because of it) and I haven't even started with gameplay issues where Kayle, for example, has her character model on the edge of her hitbox and not in the center...
Wasn’t a bug. Just dumbass coding. It’s the same thing with the Rumble E bug. Results were checking for conditions at time of impact instead of time of cast
It looks like its allowing the ability to hit the baron multiple times because you reached some distance away from it. Probably some spaghetti code that was meant to prevent some abilities from damaging baron from a certain distance away turned into infinite procs on the baron
I mean the Neeko community still has the Bel Veth bug where we literally cant dmg anything while disguised as her xD. This was happening even before rework.
I stg that "no damage" thing has been around for years, I just thought it was a normal feature for when baron was out of combat and with no valid target in range (which looking back is a bit dumb to assume)
At this point, they should just rebuild the whole game + client on a new engine cuz it's just slowly crumbling. I constantly encounter client bug on the client from different computers, may I add. Some of those are: the game doesn't show up even when the client is still there, black out the entire screen in lobby/game, client refuse to connect to the server even tho internet is still doing fine. Oh yeah, I still have the invisible Nunu W bug from time to time too, yay Riot
honestly next season instead of some meta changing things or changing the jungle again if all they did was take the time to rewrite 90% of the spaghetti code, it would be the best preseason change ever.
I like how league of legends adds new champions while finding new bugs this amazes me the fact that they don’t want to fix all bugs before releasing new champions
How is it even possible that a bug this game breaking exist in a competetive game?! And they even think about releaseing new skins and champs before addressing this is absurd greed imo and they deserve to lose a big portion of their player base or at least rp sales...... Its up to us the players to put greater demand and not support them not fixing it. The projectiles not giving vision 100% is the biggest bug imo that can really screw up an entire game easy by thinking ur not face checking and then be jumped on = throwing a game.. This NEEDS TO GET FIXED BEFORE ANYTHING ELSE HAPPENS.
Sometimes fights are so hard to see every little action and ability that I just assume most games have game changing bugs that people don't even notice.
Even an indie game developer can fix this so easily, I know that they intended to make it that way due to the reason of distance but they can just add a condition there whether a hero is within the baron's range then enable all of the damage that are thrown to baron.
I wonder if this is how GP has been out smiting people with his ult. His ult doesn’t do much per wave, but I’ve seen it kill Baron/dragon before smite range
I left League about a couple years ago, and I still amazed how things like this still happens. Maybe It's time for riot to stop comming with a new champ every month and focus on the problems of the game... but ofc that don't give them that much money
This is about as bad (if not worse) than the bug a year or two ago where Poppy's Q could damage every opponent on SR just because she flashed into the fountain wall. Riot REALLY needs to keep a closer eye on their games.
There are others issue including the robot issues, it understandable that they were not professional engineers at beginning, but now it’s like 14 years, they still having the old spaghetti code, like I always think, riot programmers are like graduate student level.
UPDATE: Around 2 hours ago Zyra got disabled, and right now she is playable again.
Riot has managed to successfully HOTFIX her. The other champs are still bugged, but it's good to see the worst one hotfixed so fast.
I'm still hoping for this Baron feature as a whole to be fixed, but that definitely needs more time.
To me, this is proof that the bug has been ignored and not worked on during its whole existence. Such a shame
they fixed hers so fast but cant do the others
they fixed the outcome of the issue but not the source...
Cant wait to see what new bugs have been created with zyra, also love to see they patch a champ instead of fixing the root issue
Riot only works when someone on Reddit or RUclips complains. Yikes
Nothing is more iconic than Riot ignoring small bug that turns into a massive exploit. It is their signature move
Well to be fair, the spaghetti is so thick that numerous small bugs just get ignored because they presumably wouldn't be impactul. Turns out sometimes, they are.
I mean last I checked, that one bug that has been around for literal years aka the space x launch bug is STILL in the game. Its even shown up in tournaments and they won't fix it.
At some points bugs become a feature and you need to live with that. You just learn how to exploit those.
@@berryesseen sure bro, like the poppy exploit, or one shotting baron exploit, lmaoooooo, bro stfu, bugs should get fixed, if they dont its lazy devs
@@mr.someone5679 fixing bug doesn’t make the game more fun. And also sometimes noobs aren’t aware of bugs. So you can easily beat them by exploiting bugs. I am totally okay with it.
Riot is always negligent when it comes to bug management.
Except when it's about the shop
Riot is just negligent. Plagiarism, laziness take your pick. They don't care about the game anymore because people will not stop opening their wallets for them.
Elevation bug still exists after all, though that seems like a logic bug rather than a coding bug.
Unless communities go crying about it on social media and send death threats.
balance management too
it is so disgusting that bugs like these get reported on their reddit, and riot instantly removes the threads
Unfortunately posting any bugs on /r/leagueoflegends is not allowed these days.
Considering forums also got removed, we can catch much less bugs than before.
@@Vandiril Look at the bright side. It's more content for you to made. But I do question the game longevity if this kinda of Live bugs keep happen too often like this
I was just thinking this and I agree completely, the moderation on r/leaueoflegends is such a joke. Its even against the rules to address Riot in a post. No exaggeration. They shut down conversation so often and there's no hope in sight...
@@Salmagrosit's actually less content for him since he has less ways of finding bugs
Do they not take note of the bugs before removing the threads? Wtf
I remember the times when vandiril used to upload twice a month and only from pbe. Now all his uploads are from live servers and often he often posts daily. It's gold mine for vandiril, but it's laughable on riot's part.
Back in the day I still uploaded a lot of videos, but way less bug related I'd say.
Had plenty of videos from other gamemodes, customs shenanigans, but most of it is simply not possible anymore (sadly).
At least Riot is delivering when it comes to bugs, I guess? x)
As long as League continue to exist, Vandiril will not run out of content
@@VandirilI loved the “wet dream” videos. First one I’ve ever seen was the irelia one
@@gellertgyori9734sivir wet dream with unlimited bounces
@@Vandirilway is it not possible now?
A new season just isn't the same without a gamebreaking bug
It’s not that new of an issue, it’s cause Riot is too lazy to organize the code of the game.
The game is truly spaghetti code.
@@NocturnalPyro More features from those spaghetti codes 😂
new season started?
@@ricardohoang8452 I mean unintended features, however technically correct.
@@ПОТРАЧЕНО-я1з naah bro community is like, ahh its on pbe, its supposed to be working 100% then wtff no bugs, haha i cant about this community, pbe is supposed to find bugs jezz
Considering Riot hotfixed Zyra but not the others, I can 100% guarantee that instead of finding out the core issue causing this bug, they just added some spaghetti code, like adding an invisible Teemo in the baron pit that checks if it's hit by the Zyra ult and her current distance, and if she is too far away it reduces the damage by 90% or something, and it will come bite them in the arse in another patch.
😂 though tbf, it’s possible this bug is some architectural problem, which in the very worst case means completely rewriting league code from scratch to properly fix, so you can see that an invisible teemo in comparison does not sound so bad
or maybe made it so after getting hit once all the other hits do 0 damage or baron has the afk armor who knows what spaghetti is hiding there.
Doesn't matter. they're a billion dollar company, they get paid to provide a properly functioning game service, if they have to completely rewrite the codebase, so be it.@@rshackerpro1
yeah and every layer of shitty spaghetti code probably taxes more and more on the server and fps
League of Legends is the Spaghetti Code
Well at least they removed bait ping since people were getting offended by it XD
And limited some pings to only 3, top 10 best decisions by Riot
gone full corporate PR mode - everybody knows you never go full corporate PR mode
Yooooo I loved that bait ping ❤
@@whiskizyo2067 everyone except corporations
Thing is, I hadn't even seen it used like that enough to realise what it was about. I think i saw it literally twice and just thought the person mishit a different ping, then riot removed it.
At this point with it going for 10 months without mention by riot I would just assume it’s a feature
Its crazy that this game has one of the most popular pro play scene, but riot refuses to work in insane bugs like this
That's cause they give the pro scene lists of skins and bugs they can't use.
better yet, their solution to abuse in proplay is to just tell the players "hey dont pick XYZ champion, else we'll fine you." instead of, yknow, just fixing the problem.
Zyra got fixed today
@@internetgamer2My philosophy on this is really just use everything in the game. Riot is constantly patching the game, if they don't want something in the game then they can fix it. The pro play would also be more entertaining this way.
Idk how anyone takes this game serious. In a skill based competitive game, the code can't be this much of a disaster.
Ever since I obtained it, Gun Goddess Miss Fortune's taunt doesn't trigger its voice lines at all. She does the animation, but doesn't trigger the lines. If you do something that does trigger another voice line she'll immediately say it, so the taunt's audio trigger is just broken instead of muted because of other voice lines immediately doing it.
Half of Pulsefire Caitlyn's lines aren't working properly or aren't working at all either and it's been like that since her VU
Thats rammus for me, i hear the laugh emote like once every full moon
Nunu and Willump Bot is similar. The laugh emote triggers the animation but uses the taunt voice line. Game breaking bug because spamming Willump Bot laugh is the best part about the skin.
I always feel Gun goddess Miss Fortune does less damage, so I use other skins
As a Zyra main I see no issues. Just the buff she needed. ;)
That's just her canon power level!!!
You heard of Brungle now get ready for Zungle
Unless it doesn't happen on a big tournament. They simply ignore bugs.
there were bugs in tournaments, even worlds, that didnt get fixed, because they arent frequent enough. unless a bug is ruining every game they just wont bother.
They just tell pros, don't use/do this, or we will fine you...
or if Vandiril makes a video about it.
Like the neeko canon? 😂
Hexdrinker didn't work last worlds and a team got eliminated because of it RIP
200 years of collective game experience
400 years of experience in working at a circus. Nothing surprising here.
2 Hours after the video got realeased --> "We have disabled Zyra due to in game issues and are currently working on a resolution"
Friendly reminder that Mordekaiser had 200 Bugs, many of which were quite significant like his 3rd Q doing no damage when W reactivated, and Riot did not touch him for 4 years straight until they remade him.
I agree it was absurd, but they were probably already working on the remake and thinking it would be a waste to fix the bugs
good old mid morde lol
I still play him Mid Lane only to this day, Emerald II right now omw to Diamond, God willing@@sametekiz3709
In that case, i wonder why a small indi company like Riot Games needs four years to come up with a solution @@perep_
Friendlier reminder: Old Mordekaiser is still in the code, since removing him will cause a flood of issuesx
To think all the Ashe W baron steals happened due to an exploit makes me question how how long did this bug exist without anyone seeing it
I wonder about all the Varus Q Baron steals from worlds 2022. Does the bug even affect Varus and was it in the game that long ago? Throws so much up in the air
I doubt the bug is this old, but in season 4 or so i was a janna otp for 3 months or so, and i specificaööy remember stealing multible barons with qs from downtown.
Tbh that can probably be put down to being silver or gold elo back then
I think the worst part is that this bug can easily be done unintentionally. Like, I can see a Zyra just dropping an Ult in the Baron pit because she expected the enemy to be there and walking away because she is alone and suddenly BAM, she has the Baron buff.
imagine Zyras on red team, they lost a team fight but theyve got a ward on baron, they see the fight happening, she walks over to ult and be annoying, the blue team Bard puts a portal on the wall so everyone can go through and kill her, shes caught all alone! she instantly flashes over the wall to red buff and Baron loses 8000 hp in a heartbeat. red team goes on to win the game, because Jax was splitting bottom and now hes got baron minions chomping through the blue base.
Zyra could be banned for bug abuse, when she didnt do anything weird or strange, the baron just happened to unalive itself and she got credit for it.
If they're missing stuff this obvious all the time it makes you wonder how many bugs there are under the radar.
When I quit playing myself and now just watch streamers sometimes, I've noticed tons and tons of random little bugs in the majority of games. Stuff like skill shots going directly through champs, abilities not working how they should, items not proccing, tower and minion aggro being mega wonky etc it happens way more than you would think. It is hard to notice while playing, but on RUclips I often slow down the speed to .25 and it is insane how much is broken in this game. I could never take it seriously again like I used to. Game is too competitive to be this broken and just feels like a waste of time.
Riot: Please don't hesitate to contact us if there is something wrong.😊
Also riot: No.🙂
i thought the no damage bug was just a feature put in to prevent you from taking camps behind the spawner because whenever id place an anivia ult in baron pit from behind the wall it would do no damage i had no clue it was part of a larger bug with baron
One thing I do want to mention is that some bugs can be ridiculously hard to find and fix. What Riot should do in those cases, is tell the players that the bug is at least being looked at. that would be infinitely better than saying nothing at all
The problem is, they don't even have to find the bugs. All they have to do is watch youtube content like Vandiril's videos, and then go about fixing what he finds for them. Instead, they do nothing, fix nothing, say nothing, and just expect people to keep playing their trash game
@@joefoulger3510 With finding bugs, I wasn't speaking about what the players see, but the location within the code itself. It's not that easy to figure which line of code causes things that you didn't intend to happen. I do see why it may have been confusing with the way I initially said
Generally, if something is reproducable, it might take some effort, but you *can* find the cause with a bit of time. When there's no reliable reproduction, it might be next to impossible. But a reproducable bug that can affect game outcomes this much (even the original no damage bug) and will easily be triggered in normal gameplay staying in the game for 10 Months really is not excusable.
@@LwL_ I'm not saying this situation is acceptable. You're definitely correct regarding the bug being reproducible. I would look into code regarding distance in conjuction with damage, but with thousands and thousands of lines of code, that could still be incredibly difficult to find. All I was suggesting is a bit more openness from Riot on whether this bug is even being looked at or not. Now we don't even know that, which inadvertently suggests it's being ignored
@@messorix2033 Sounds rather easy to find, as the dmg calculation won't be thousands of line of code.
Since it is reproducible, any debug mode should just be able to look at those damage instances and whatever triggered them.
Wouldn't be surprised though, if rito didn't have such a debug mode.
Riot 2024: we decided to completely remove the baron from the game. Instead, it'll be the old dragon where you only get gold
I'm fine with this if they revert Morde and let us have a ghost dragon again
@@joefoulger3510 always hated the "you are going to brazil" ultimate
@@dabioji7096 I hate his entire rework. He was so much fun before. They gave all my favorite champions shitty reworks. Galio. Yorick. Morde. I quit playing after they all got turned into dogshit
I have to assume this has something to do with Baron being cleared from an ability's "already hit" list? It looks like the abilities are hitting multiple times. The range that this bug occurs at might be Baron's de-aggro range (outside of which he'll stop attacking you and begin healing). Maybe part of the code that handles the initiation of his "de-aggro" is somehow clearing him from these active hitboxes?
In that case you wouldn't expect abilities to not deal damage at all, or maybe no damage for Rumble's continuous damage R, but Ahri's Q should hit multiple times as well. Lee and Rumble are both somewhat old champions that haven't had a significant rework, so I doubt it'd be just an issue of old code and new code breaking each other.
@@La4geas I'm guessing continuous damage hitboxes like Lissandra R and Rumble R are just a hitbox that keeps deactivating and reactivating. It seems like any hitbox that is activated after leaving the range doesn't work. For Ahri Q, maybe it has something to do with the damage changing to true damage on the way back.
@@groggylark4876 Ahri's Q and Q2 are functionally 2 independent spells but yes it does appear to be an issue with Baron's aggro/leash range, as the moment Rumble is close enough it starts doing damage but does nothing when hes far away.
With Zyra it seems its continuously checking if a target is in the hitzone (presumably for Zyra's plants to get buffed) and as Baron is resetting many times per second since there is no valid attacker/target in his range, its also resetting Baron's interaction with the AoE? but the thing that confuses me is this behavior would logically behave normally if any champions other than Rumble/Zyra etc. are near the Baron but as shown with the lee Q and the dummies behind Baron this isnt the case.
I remember years ago I saw eve delete baron with R from 3.2k HP she had full build but still...
Senna E still doesn't work inside Mord R every single time, 11 months without fix now
Im pretty sure Riot does'nt even understand how the game works. I remember hearing something about them having problems understanding the really old programming/code used for league. I think they have reached a point where they should just redo it compleatly in order to have a bug free game/client again.
The latest dev blog they said they are transitioning to windows 8+ etc. so they won't run on older systems meaning they should be able to redo the code for newer OS.
I'm pretty sure it has to do with like projectile property and fog of war. Like hecarim heimer and ashe dealt dmg according to the number of missiles that hit nashors. But for zyra and Lee sin their abilities check multiple time sending multiple missile since it's old abilities to check if poeple should get hit or not. He talked about how he used missiles to check for hitbox on vi's Q for example
you just unlocked a core memory of 3clicksphilip saying valve please fix
It definitely seems to be that, in the cases where present, being far enough away from baron prevents abilities from not multi-hitting when they're supposed to not multi-hit. It's interesting Zyra and Lee Sin's abilities that trigger this both have hard CC attached, which Baron is innately immune to.
I wonder if this sort of too far away inconsistency was originally intentional from league devs to free up resources and prevent abilities from using excessive cpu time trying to calculate something that doesnt matter, but they forgot about it and now instead of not showing a scx when its not on your screen it instead impacts how much dmg something deals if it deals any at all because the game is guessing what the effect is supposed to be, due to using less resources to guess. While this mightve been fine 10 years ago, it probably should be fixed today
Zyra is currently disabled. Good work Riot! You finally decided to do something
but they still didnt fix any of the Rumble issues, or Lee Sin being able to one shot baron.
They should add more features to the testing tool. Thresh lantern would be a good way to consistently test something like this
Mark my words: when they "fix" this bug, 10 new ones will rise from the spaghetti.
There’s a minor bug rn where if you buy an item with a unique passive twice by accident like an aether wisp and then refund it you lose unique passive entirely
Riot looking out for our boy Vandiril to make sure he always has enough content
Zyra is now disabled in game
I'm gessing the initial intention was to make global baron steals look more impressive. Probably to make it more hype for spectators of esports, but implemented as an untold mechanic. However, with the coding of so many abilities, it seems like some do more damage then they're supposed to while others don't at all.
Riot's code logic is amazing lol. How tf do 90% of these bugs happen?
game is held together by chewing gum and butchers twine
As far as rumble ult not hitting baron when far away, I thought it was because baron's health regen is high and constant if no enemies are close to it.
IF you paid attention to the video, no damage numbers showed up AT ALL from the rumnble R. So it isn't because baron was out-healing it, it wasn't doing any damage to begin with.
chosing to play dota instead was the best decision I ever made
My computer science symptom makes me wonder what’s the codes behind in every bug manifest clip.
riot took "increased damage dealt base on distant" to a whole new level.
I bet it's a damage reduction check for Baron's gaze and being outside of a check range. it probably also interacts with it's leash range IDK
There's also a yorick bug, happened to slogdog earlier.
So the what happened is yorick dies and he or the maiden or the ghoul destroyed the nexus tower, and then the maiden didn't die.
Game breaking bugs: Riot sleeps
People communicating via in game chat: REAL SHIT
and now zyra is disable
heimer and cassio have always been known to do increased dmg on nash, heimer with the turret and staying out of range, and also the nash debuff mecanic that cassio avoided, or even the yasuo wall preventing nash to apply said debuff, it may be a bug, but it's been played around for years.
Mark my words, when they try to fix this there are going to be barons randomly insta dying to some champs aoe skills on the other side of the map.
There was a bug in Wild Rift where Sol could just infinite Q baron or dragon from max range without drawing ANY aggro. Wild
That looks like an optimization that has a side effect rather than a straight up "bug", so my guess is the fix is probably far from trivial as it would require them to question things much deeper than the actual issue in order to solve it.
finally we got lore accurate zyra
There has been a pixel wide gap underthe back button on the UI for as long as i have played so i wouldn't hold my breath about them fixing anything if they can release another lux skin or rework jungle again instead.
This finally explains why is so scary an ult of ezreal, Jinx and more in barón.
This bug looks like what they did to stop jungle pets from hitting epic monsters when doing scuttle.
I remember a time when if you hit scuttle when it not far away from herald, the pet hit the camp, but didn't aggro it to the champ who had the pet. So you got double pet healing. Riot probably added a thing to champions that make you not be able to damage epic with your jungle pet, but a bug had it accidentally bleed into certain champion abilities. Probably ones that would trigger the pet to hit a camp outside of the range believed to be what the pet should be hitting. Ekko and sivir Q probably works like go from A to B, then from B back to character. While for ahri it's probably just go forwards then back to the character.
Similarly, currently on live servers, it looks like your jungle pet can only hit one camp at a time. So it's probably something to do with stopping the pet from interacting with far away jungle camps (or just when far from epic monsters), but for some reason also affects certain abilities.
The abilities that benefit are ones that are "secretly" checking for any changes to their status. Ashe and hemier missiles dissappear upon hitting something. Mord's E is checking is someone in range to pull, hecarim's ghost horses are probably a type of clone that's checking if there is a unit it needs to damage and pass through with ghosting. Zyra's R is checking who is about to be knocked airborne. Maybe this even works with Aatrox W, Cait Q, Jinx W, and Azir R.
I feel the need to go back and watch old rumble vods anywhere I can find them in the last season to see if he ults baron from range…. It probably happened in pro play already…..
Happy to see Riot's old traditions haven't been lost.
Zyra got disabled an hour ago i dont know why it took this video specifically for them to do something
Normally ashe w fires multiple arrows however hitting multiple arrows on a single target deals no additional damage, it seems when far away , this rule becomes inactive, allowing for more damage than usual. something similair happens with all other instances.
Just watched the video and wanted to try out the bug, but they disabled Zyra for now. Riot can be fast sometimes
Was testing some champs out after seeing this. It works with Diana Q too, if your full build you can deal 2.6k damage with q+flash.
as long as you don't hurt someone's feelings in the chat, everything's fine.
-riot, probably
i'm confused from a mechanical standpoint... walking away must change something about Baron's hurtbox... but nothing i can think of would cause these results.
1) maybe Baron's hitbox is blinking... causing Zyra to hit multiple times, and Rumble to miss. nope, because then the projectiles should work at least sometimes
2) Minion vs Champion? nope Rumble's Ult and Zyra's Ult damage minions.
3) Both? nope, projectiles should work
it has to be a ID thing... which League shouldn't even have more than 4 hurtboxs. (Minions, Champs, Walls and Gwen) and 3 Hitboxs (Projectile, Non-Projectile and unErasible Projectile)
but no combination fits these results.
i can imagine 3 weeks later a bug with Zyra that *heals* baron somehow with the aggro mechanic.
I hate how negligent Riot are to fixing bugs. Sometimes the launcher crashes and you can hear champion select after loading into the game, or the fact that I get a notification about new tft season every time I open a tft lobby, even after playing tens of games, same for arena, or the fact that sometimes in game you have no sound of aa/skills, lock in button at the same position as the show/hide champions (multiple times I've accidentally locked a champion because of it) and I haven't even started with gameplay issues where Kayle, for example, has her character model on the edge of her hitbox and not in the center...
If it's double for half of the champions and it's 0 for the other half, on average everything is fine 👍
That hecarim ult is still basically a guaranted steal if you replicate this precisely
Nidalee used to have a mechanic where if she ran away/dashed away after throwing spears they would do more dmg. Likely a bug in the first place.
Wasn’t a bug. Just dumbass coding.
It’s the same thing with the Rumble E bug. Results were checking for conditions at time of impact instead of time of cast
I remember people flashing away for the oneshot 🤣
It looks like its allowing the ability to hit the baron multiple times because you reached some distance away from it. Probably some spaghetti code that was meant to prevent some abilities from damaging baron from a certain distance away turned into infinite procs on the baron
I mean the Neeko community still has the Bel Veth bug where we literally cant dmg anything while disguised as her xD. This was happening even before rework.
I stg that "no damage" thing has been around for years, I just thought it was a normal feature for when baron was out of combat and with no valid target in range (which looking back is a bit dumb to assume)
At this point, they should just rebuild the whole game + client on a new engine cuz it's just slowly crumbling. I constantly encounter client bug on the client from different computers, may I add. Some of those are: the game doesn't show up even when the client is still there, black out the entire screen in lobby/game, client refuse to connect to the server even tho internet is still doing fine.
Oh yeah, I still have the invisible Nunu W bug from time to time too, yay Riot
honestly next season instead of some meta changing things or changing the jungle again if all they did was take the time to rewrite 90% of the spaghetti code, it would be the best preseason change ever.
Shoutout to Riot. They consistenly give content for Vandril to talk about. They a real one.
tbh i think the whole burning flash to solo baron/chunk baron bug tech is kinda cool
I like how league of legends adds new champions while finding new bugs this amazes me the fact that they don’t want to fix all bugs before releasing new champions
Bug so serious he stopped using the intense music
A certain riot dev has to main zyra
now i need to go vod review on how many rumble ults were on baron for worlds (im getting dejavu from azir bugs at worlds)
And Baron goes "Pasta-lavista"
less go a new vandril vid everyone drop everything
How is it even possible that a bug this game breaking exist in a competetive game?! And they even think about releaseing new skins and champs before addressing this is absurd greed imo and they deserve to lose a big portion of their player base or at least rp sales...... Its up to us the players to put greater demand and not support them not fixing it.
The projectiles not giving vision 100% is the biggest bug imo that can really screw up an entire game easy by thinking ur not face checking and then be jumped on = throwing a game.. This NEEDS TO GET FIXED BEFORE ANYTHING ELSE HAPPENS.
The more its abused, the faster they should try to fix it. Just make it more well known
I assume this works cause baron increases resistances when you walk up to it and has little to no resistance when no one's around.
You forgot, they need all 2500 workers to make 1 rework in 2 years.
Sometimes fights are so hard to see every little action and ability that I just assume most games have game changing bugs that people don't even notice.
I remember seeing this as a Fiddle main multiple times. I'd try and E from max distance on rift herald or baron and they just....don't hit lol
Even an indie game developer can fix this so easily, I know that they intended to make it that way due to the reason of distance but they can just add a condition there whether a hero is within the baron's range then enable all of the damage that are thrown to baron.
I wonder if this is how GP has been out smiting people with his ult. His ult doesn’t do much per wave, but I’ve seen it kill Baron/dragon before smite range
Id watch : All champs interactions with max range plus Sylas for extra cheese on top
as long as rito exists your channel will never run out of bugs to show...
Zyra's already been temporarily disabled.. 2 hours after this video was posted!
They never fixed the client bug where you can't press the "play" button without closing the client or switching to play tft so you can press it.
I left League about a couple years ago, and I still amazed how things like this still happens. Maybe It's time for riot to stop comming with a new champ every month and focus on the problems of the game... but ofc that don't give them that much money
This is about as bad (if not worse) than the bug a year or two ago where Poppy's Q could damage every opponent on SR just because she flashed into the fountain wall. Riot REALLY needs to keep a closer eye on their games.
4:31 ironic, as sylas himself say: "you're part of the problem".
This seems like a deep structural issue they’re just not willing to fix
Small indygame company incident
There are others issue including the robot issues, it understandable that they were not professional engineers at beginning, but now it’s like 14 years, they still having the old spaghetti code, like I always think, riot programmers are like graduate student level.
did you guys noticed the amount of gold he is gaining after he use the bug
it only worked on zyra for some reason
It is actually from fast forwarding in Practice Tool - so this is not the issue fortunately x)