Skip to content

Rumble and Viktor disabled for 6 days

Polish Kielbasa··3 votes·949 views

To add insult to injury, the notification has been removed also.

11 Comments

EndlessSorcerer3 votes

It can take a while to hunt down, correct, and test the correction of bugs. Have some patience.

DisasterSola1 votes

{quoted}

It can take a while to hunt down, correct, and test the correction of bugs. Have some patience.

Zed has bug that makes his ult do 0 damage to champions with shields. Fixed within 6 hours of disable. Yorick has gamebreaking bug that makes his Q not work occasionally. Never fixed (and taken out of the champion rotation for years, for other reasons) Nidalee has gamebreaking bug that makes her traps not do any damage to enemies below a certain amount of HP. Fixed within three hours of disable. Zac has gamebreaking bug that makes him bounce out of the map. Not disabled and not fixed for 17 days. Lee sin has gamebreaking bug that reduces his W sustain. Fixed within an hour of disable. Vi has gamebreaking bug that lets her E stack infinitely with a specific item. Not disabled and not fixed for three days. Malphite has gamebreaking bug that makes his ult not apply CC or damage occasionally. Not disabled and not fixed for two days. Yasuop has gamebreaking bug that lets him ult from fountain. Not disabled and not fixed until the next patch. Morgana shield has gamebreaking bug that blocks all damage associated with magic damage (Nashors tooth, wits end, etc). Not disabled and not fixed for three weeks. Nidalee has gamebreaking bug that makes her spears go under terrain in specific places. Discovered and reported over a month ago. Still not fixed.

Riot picks and chooses who gets fixed and when based on their LC$ priority. Yorick was disabled in the shurima event too, because riot didnt want to fix the problem.

Polish Kielbasa1 votes

To add onto this, the Viktor and Rumble bug are minor and non-abusive, so it is absurd to disable them. The bug is that Rumble R and Viktor E will change to smartcast even if smartcast is disabled in options. The interaction is shown here: http://gfycat.com/MiserableAccomplishedBrocketdeer

Meanwhile, Kha'zix was able to teleport across the map and he wasn't disabled.

EndlessSorcerer2 votes

Riot picks and chooses who gets fixed and when based on their LC$ priority.

Riot doesn't prioritize bug-fixes based on LCS priority; asserting otherwise is simply ignorant.

Software bugs may sometimes be caused by an obvious and simple error. However, in many cases finding the cause and solution for a bug is non-trivial. The time required to find and solve a bug can vary greatly in practice and one cannot accurately estimate how long doing so will take. In addition, even when you have found a solution, you must test to ensure that it has not created more issues in the system.

Most of the bugs you have listed deal with specific champion abilities. Depending on how the game is code, any fixes will likely be contained within the code for that ability or champion, which reduces potential complications.

IIRC, the bug plaguing Victor and Rumble has to do with the code for the targetting system of their E and ultimate respectively. Fixing this bug will likely require changes to the champion's abilities and code for targeting those abilities. Any changes made to fix the bug may potentially have far-reaching consequences, which means that any related functions will have to be extensively tested and that there is a far greater amount of code which may have potentially caused the bug.

Chron Burgundy1 votes

Your response does not address the discrepancy in not disabling more heavily bugged champions like Nidalee, but disabling these champions for what is a relatively minor bug. This bug isn't even abusive or severe its simply a problem that forces the spells to smartcast which many players already do anyway (I don't, but I'd rather learn how than wait over a week and who knows how much longer to play my mains). Why do other champions go un-dsiabled, but these two don't?

The undeniable fact of the matter is that Riot plays favorites with their champs and they'll constantly rework, debug, make new skins etc. for the most played champions and fully neglect the ones that are less played. Not enough people play Rumble and Victor to make them care.

Also the utter lack of communication on Riot's part is inexcusable and there really is not reason for it. An update, even if it said that they haven't made any progress but are working on it, would be simple and easy to do and make a lot of users at least feel better about the whole thing. Instead we get utter radio silence as if for them to even dignify our concerns with a response is beneath them. Like I said, there is simply no reason for this type of behavior from Riot.

EndlessSorcerer2 votes

We don't know the full ramifications or how entrenched the bugs are.

If you are referring to Nidalee's invisible spears, it is an issue that has existed for a long time and occurs for many champions (i.e. Mundo's invisible cleavers, etc). We don't have access to the code, so we have no idea how to find it or how much of the system would have to change to fix it. If they disabled champions for this bug, it's possible we might not have access to them for months or years. The bug seems to be hard to consistently reproduce or to track down in the code, since we don't know what factors affect it and the code required for a game like this is massive. The bug doesn't appear consistently, so it isn't that large a hindrance; honestly, I don't think I've ever had this bug occur in my games when player with or against the affected champions.

Similarly, we don't know the full consequences of the bug on Victor and Rumble or how greatly it affects them. If the bug essentially means that Rumble's R or Viktor's E can't be used as desired by the player, disabling them was probably the correct decision. Those abilities are major portions of their kits and if they can't be used correctly, it's better to have the champions disabled than to have games ruined because players unknowingly chose bugged champions. We don't know the full ramifications of the bug and even simple solutions can be time-consuming to identify and test.

While Riot could be more open on communication, the community tends to react harshly when Riot changes their stance or goes back on a previous statement. It can be hard to predict how long certain bug-fixes may take when developing software, so if Riot announced that they were looking for or had found the bug, the community would be in an uproar against them if they later found the fix was more complicated than anticipated or that they had not found the correct/only cause of the bug. Staying silent on this matter until a solution has been found and implemented is, in my opinion, the correct decision for them to make.

Software development, especially when working with a large-scale project, is far more complicated than many people believe.

Still waiting to be able to play Rumble again. However, I am willing to be patient and I have plenty of other champions to satisfy me in the meantime.

Meserion2 votes

[{quoted}](name=Valkyrie Witch,realm=NA,application-id=3ErqAdtq,discussion-id=inYBg9hE,comment-id=0000,timestamp=2015-05-20T22:14:16.416+0000)

http://status.leagueoflegends.com/?en_US#na

I happen to own both champions, your argument is invalid, I wish to play them...

Deep Terror Nami1 votes

What argument? I provided the link to view the Service Status after a notification is no longer being shown up top...

OperationDEEZ11 votes

It's a fucking bug with the smartcast, I use smartcast for those abilities anyway...

More from Gameplay

More by Polish Kielbasa