just wanted to share for no reason at all.
edit: this reminds me of the lux bug where her ult just went through you if she didnt see her target.
riots coding is really weird when it comes to "super long range stuff" thats out of sight
Quinzley7 votesRiot is a small indie company.
Arammus4 voteseven 1 man games fix more bugs than riot. which is just so fucking sad. riot has so good teams, especially the music team is godlike. and then they have employees that are just licking their own dick the entire day and dont do anything. i'd love to work in the "bug fix" team of riot. jerking of the entire day and laughing at posts that report 5 year old bugs.
DuskDaUmbreon4 votesIt's...rather sad you think of it like that.
A lot of the bugs come from old, shit coding, and it's a massive headache to actually sift through a lot of that, and then you have to isolate the error and figure out how to do it without rewriting half the game.
Some of them they're just not sure how to fix without telling the VGU team to handle it, because the underlying code is so faulty that there's just no reasonable way to fix it without rewriting everything in relation to it (See: Mordekaiser. His R in particular just has so many issues with every new item/champion that it's clear there's no way to actually fix it without a total rework).
Some bugs are just impossible to isolate properly and fix. Maybe they just can't reproduce it, or maybe they just can't figure out what is causing it. You can't fix something you can't pin down properly.
And some things are just too trivial, inconsequential, rare, or easily worked around to bother the time and effort to fix. Pathing at long range being weird like that is...well...I've just never seen anything even resembling it before (Edit: Looking at the vide, I have a vague idea how this would happen. It falls into 1 or 2 on my list, because it's just old sphagetti coming up again. Odds are something similar has been fixed with Anivia, or it was already patched in. We'll also probably see an issue like it with Ornn).
Arammus4 votesobviously i know with over 140 champs several items etc this isnt easy. but as you said yourself "it comes from old shit coding". you said it yourself. if you'd keep up with your work 24/7 then it would never be as bad.
and ofc theres always the argument that you just cant beat in this discussion: why is mordekaiser not disabled? its a pile of bugs.
DuskDaUmbreon1 votesobviously i know with over 140 champs several items etc this isnt easy. but as you said yourself "it comes from old shit coding". you said it yourself. if you'd keep up with your work 24/7 then it would never be as bad.
Different people made the original code for it. People come and leave. And the oldest code is a lot of shit from other games, too.
and ofc theres always the argument that you just cant beat in this discussion: why is mordekaiser not disabled? its a pile of bugs.
Because Mordekaiser, despite the numerous bugs, is still rather functional. Nearly every single one of his bugs applies to the ghost spawned by his ultimate, meaning his Passive, Q, W, E, and R damage are all still 100% working.
He's not bugged out enough to warrant immediately devoting resources to fixing him yet. If a bug that caused massive issues were to happen, Riot could then fix it, but since almost everything is related to the spaghetti code that is his ghost...
KFCeytron4 votesRiot is a small indie company.
EasternBladeStar1 votesStill new in the business, still learning.
SociopathFriend4 votesAh yeah, remember Warframe? The game that still has game-breaking bugs? I don't mean "Oh it's harder to beat the mission" bugs I mean "Oh, the enemy spawned like 50 meters below the level and we can't finish the mission until he dies" bugs.
Clearly, they don't care because they haven't fixed it. It's not that their resources are spent better elsewhere for some reason or another- they must just not care what with the awesome E-sport scene the game doesn't have...
Teridax685 votesWarframe fixes its bugs routinely, and has done some truly insane overhauls to their tech. Look at how they updated the game's lighting, particle effects, etc., and made many of their higher-end graphics options viable on lower-end machines. One of the running jokes is that the devs code in assembly to get to such fine degrees of optimization. For sure, the game has its fair share of bugs still, but Digital Extremes genuinely does make an effort to update their older tech, and even when they don't solve bugs immediately, they still find ways to make them less game-breaking (for example, their changes to Extermination, where you only have to kill a certain number of enemies, rather than every single enemy on the map, thereby preventing the issue you mentioned).
By contrast, Riot does not appear to be touching their legacy code at all, with what few changes they've made seemingly worsening problems such as unit collision. When changes do happen, it's usually a change to a single feature every few years, and said change is hailed as revolutionary by the developers. Warframe is also a much larger game than League in terms of assets, and there are many more things that can go wrong on a massive set of maps with a full parkour system constantly enabled, compared to a handful of maps with much more basic rules with regards to pathing, geometry and isometric movement.
SociopathFriend1 votesElimination yes (thankfully) but however this same bug exists for Defense.
My only point is that a bug existing does not mean the developers don't care. It's confirmation bias and not much else.
Teridax681 votesSure, but there's a difference between one bug existing, and a whole set of major bugs remaining unaddressed for years, despite being requested as a priority by many players. Even if a bug like this happens in Defense, for example, most players would still not go to the forums to complain, and aren't as frustrated in general. By contrast, stuff like pathing and unit collision has had a massively detrimental impact upon players' enjoyment of League, and has harmed the competitive integrity of the game. It is embarassing when a developer has to arrest an entire game session because of a bug, and unprofessional when this arises from issues that have well-known among players for some time.
SpecterVonBaren3 votesYes, let's overlook the bugs that have been fixed in favor of just pretending that Riot does nothing so we can shit talk them more.
Jesus is Savior2 votesPathing has been messed up ever since Riot reworked walls when they reworked Talon.
GayFluffyUnicorn1 votesAnyone here playing Kled? Unlike morde is not old and slated for a ground up rework... Every single game his W bugs out, E, Ult. This champ sometimes is actually unfun to play at times when he keeps bugging out. How long took it riot to fix the GP barrel bug? I'm not even talking about minion pathing that probably takes my CS average down 1/min or let's me die more often than it helps me.
KFCeytron1 votesPyke ult.
