How is it that every single rework or new champion you've made in what, the last 4 months, has had a bug on release that was reported and documented on the PBE forums multiple times by multiple different people that always makes it to live and results in the champion being disabled.
I know you guys are pretty incompetent most of the time, but this is a new level of fail even for you.
EvilRabbitt3 votesAnd I read that in Buzz's voice. Thank you good friend, you caught a wild Giggle. Train it well, it may win you the Champion title pokemon trainer.
idoki7 votesHis peers are lazy, Knees weak arms are heavy, There's bugs in his game already, Code's Spagetthi
Desiderium1 votesIt's not the code. There's no one to blame but Riot if there's a bug found well before a product's release. I don't understand why you have upvotes.
RedCyclone34 votesPBE testing grounds
AKA - wooooo yay new skin gotta look
Ancestor0074 votesAnd new champions.
BoxOfDOG3 votesPBE testing grounds
AKA - wooooo yay new skin gotta look
Well.. That's true..
But we do report a lot of bugs! Though when a bug shows up 50 people report the same thing when Riot has already been made aware of it by the first 2 people that posted. If they released stuff like Bard and the GP rework without running it by the PBE first, complain-y board goers would be having a heyday.
Watch91 votes+1 If Tahm Kench hadn't been on the PBE before live, his W would have global range again.
Trylobyte25 votesCatch-22...
If they release the patch and disable the broken part we get 'Rito y u disable, fix ur broken shit b4 patch!' If they don't release the patch to fix the problem first we get 'WTF Rito, y u taek so long 2 patch?!'
They can't win really.
Enosetc10 votesCatch-22...
If they release the patch and disable the broken part we get 'Rito y u disable, fix ur broken shit b4 patch!' If they don't release the patch to fix the problem first we get 'WTF Rito, y u taek so long 2 patch?!'
They can't win really.
what if they fix the problem while it's on the PBE and don't ship it with the next patch until the bug has been fixed?
gubigubi1 votesDoes ANYONE even know what the bug was? I can't find anywhere that says why she was disabled.
EvilRabbitt2 votesSomeone said her E had infinite resets on an inhibitor. So you basically spam tapped e for free inhibs.
gubigubi2 votesWhat would happen is you press E 1 time and it makes your attack speed like maxed while attacking the inhibitor. I thought that was fixed in the PBE though not sure how that could have made it to live if thats the case.
TheFirstGokun1 votesBecause, unfortunately, the Live and PBE are coded slightly differently in ways that may allow some bugs to slip through in the transition from PBE to Live. They fix a metric shit ton of problems on PBE, but when one problem slips through to live they get a lot of backlash.
AMYS GRAVE1 votesBecause, unfortunately, the Live and PBE are coded slightly differently
My next question is why?
TheFirstGokun1 votesI don't know, I'm just a guy T - T
Tusutaki7 votesIf they don't release the patch to fix the problem first we get 'WTF Rito, y u taek so long 2 patch?!'
I really, really doubt the same amount of people who complain about a buggy or broken updates would complain about a certain update being held back from being live to be _not _ buggy or broken.
KoKoboto1 votesCatch-22...
If they release the patch and disable the broken part we get 'Rito y u disable, fix ur broken shit b4 patch!' If they don't release the patch to fix the problem first we get 'WTF Rito, y u taek so long 2 patch?!'
They can't win really.
I dont think anyone has complained about waiting for stuff on PBE to get to live A lot of the community wants Riot to put the bestest thing onto live server, pretty sure nobody wants to play a bugged out champion on live lol
Count Buffon1 votesThis isn't Catch-22. People would rather wait for a patch that isn't broken. The only time we want to break a champion is when it's 
.
Silents4296 votesTo quote a Reddit user named onelamefrog
As someone who has worked QA for a major game company, I'd like to say a few things.
This happens all the time. Almost every bug you encounter in a retail game was known. Most of the obvious ones anyway. Of course there are bugs QA didn't pick up, but a million players tends to make bugs come out you'd never expect or could possibly design a test case for.
The problem is expectations. There are deadlines that have to be met and basically fuck all the small bugs that don't majorly destroy the game. Just ship it and fix it afterward if it's especially egregious. Basically - most of these bugs are not worth the effort or can easily be removed later. The important part is getting the game/content patch out on schedule to avoid negative public perception (believe me, a few bugs are much better than a delay) and extraneous fees (such as certification).
From what I've seen it looks like Riot uses the PBE for stability testing. That means they push the content out solely to make sure it works with the system. Their main concern is that new content doesn't cause the entire game to crash by having people use the content in a running system. If there are any gamebreaking (as in the game stops working at all) bugs it is a huge concern and will be fixed before live.
That being said it's still not that simple. Yes, Riot will ignore some bugs in favor of ironing them out later. Still, it's impossible to account for every bug and fix them immediately. Fixing a bug requires 1) reliable steps to reproduce them 2) a programmer/designer who even knows where to look 3) more testing. Without enough information they cannot even attempt to solve a bug, if they have the resources at the time at all. Your average user will write something like "game crashed when bought Tiamat" when the actual bug may be putting any AD item in slot 3 at 25:00 minutes on a specific champion. If a profressional QA tester doesn't catch it, it's incredibly unlikely that 12 year old Timmy will track it down, write accurate reproduction steps in a literate manner, and fully report the problem with detailed descriptions to Riot.
With not enough information about the bug, it may slip through, be pushed through anyway, or even become a bigger problem with live data - depending on what caused it. Pushing from closed to live system isn't a simple task either! They're not the same thing! You can't sustain a 1:1 clone of both systems - which would be ideal, but impossible with Riot's scope. So there's differences you compensate for when patching to the live system. This may introduce or exacerbate new bugs. For example the current problem for Fiora - missing tooltips. Someone just plumb forgot to add those changes into the patch. It happens.
TL;DR: PBE is for stability testing, bugs can even pop up after the fact, and the amount of information from PBE is insufficient to catch all bugs. Companies are likely to take fewer losses (monetarily and public perception) by just pushing the content out.
Celeste Benal1 votesThere is this little Icelandic company called Crowd Control Productions (CCP, hf). They decided to do away with the strict release date format and only release polished content when it was actually ready, rather than on day x of month y because "schedule".
The majority of the player-base have shown an overwhelmingly positive reaction to the new release cadence. There have been far less bugs and content is getting out on at nice reliable pace. It works.
edit: CCP also has a number of publicly available test servers that anyone can access. No fancy mailing lists or waiting for years for someone to manually grant access. Any player that wishes to participate in the QA process or even us it for sandbox-style practice can do so.
DirkTarTar5 votesYes, you are correct that if bugs are found on the PBE release, they need to be addressed as soon as possible. You are wrong in that they should push back patch releases based off a few bugs that can be easily fixed by disabling a champion for a short time while the hotfix is compiled to be released.
Deadlines are a huge aspect of good business practices, especially in technology. A good company will hit their deadline with the best possible results for the time given. There is no excuse for a deadline not to be reached and quality to not be ensured. Don't think for a minute that, if there is proper blame to be placed, Riot isn't coming down on those responsible within the company.
What you will not ever get is an apology from the company with a list of names for those responsible and actions being taken to ensure that it never happens again UNLESS something EXTREMELY tragic happened.
Don't believe for a moment that Riot is laughing at their desks at "all those stupid kids that take the game way too seriously" because "who cares, we will just hotfix it anyways after we disable the problem for as long as we feel like it and eventually get around to fixing it."
Celeste Benal1 votesA looming deadline is not a good enough reason to release unplayable or broken content.
TheFirstGokun1 votesBut they didn't release a buggy champion. They caught it and disabled her. Then they hotfixed it the very next day. "NO EXCUSES," you say, but there's really nothing they can do about it. Think about it as the rest of the patch going out and her coming out slightly after the deadline.
Kuroi864 votesFrom what I've seen, they do a last patch in an attempt to knock out such bugs as they are going live. Sadly, it seems they have been hitting the wrong section of code lately, it's sadly all too easy to do.
Remlap12234 votesI have no clue why the PBE still exists. I think after Azir we can say with certainty that they don't care about bugs if it conflicts with their release schedule.
Shadow Puppet1 votesPBE does at least give them a head start on fixing bugs. If we only found bugs once they reached the live server then riot might not even be able to fix them in time for the next patch.
ShadowParker2 votesThey also knew that Azir was going to be super buggy. They straight up said it when they released him on PBE. He had shit ton more bugs before he went to live. So the PBE was immensely useful.
Krys Star3 votesSaddest thing is, updated champions/exciting changes are always disabled on my days off. Obviously Riot doesn't intend to do this against me, but with my luck, the best part about new patches only happen during the days that I work. Meanwhile, the days that I'm off, it's me being bummed out I can't enjoy it on those days. :(
Narog3 votesriot used to care about PBE , now is just like something they do just for the sake of it.
Oerba No Naja2 votes
NewFoundAbility1 votes
But then again. It's about Deadlines, not Bugs.
sp4412 votesMan, Riot has just gone full fucking retard this week. Between the crap reworks on PBE, the buffs to LCS darlings with pretty clear cynical motivation behind them, and Fiora being disabled on live day one after two weeks on PBE.
Erockandroll1 votesWell Yes, PBE is a testing ground. But fixes don't just happen over night. Riot possibly had their hands tied where the patch cycle was fixed before they could implement a fix to the new champion. (most PBE changes are locked a week in advanced)
Still, this is better than, holding off Fiora for another patch cycle. pretty sure this fix won't take two entire weeks.
ZephyrDrake3 votesWell Yes, PBE is a testing ground. But fixes don't just happen over night. Riot possibly had their hands tied where the patch cycle was fixed before they could implement a fix to the new champion. (most PBE changes are locked a week in advanced)
Still, this is better than, holding off Fiora for another patch cycle. pretty sure this fix won't take two entire weeks.
guess what then? DO NOT RELEASE THE REWORK IF A WELL KNOWN BUG IS PRESENT! not that hard to do, just take a few days or whatever time you need to actually get rid of the bugs instead of releasing the damn rework and disabling the champion so that NO ONE CAN PLAY THE CHAMPION!
This isn't better than holding off, it's WORST. There is literally no excuse to release a rework just to disable the champion due to a bug
ColdMiller1 voteshey at least you didnt have a time where you couldnt play for like almost a month cause of a bug on the Miss fortune release patch >_>. so shush we had server crashes for up to a week, one champ. being disabled wont hurt you.
ZephyrDrake2 voteshey at least you didnt have a time where you couldnt play for like almost a month cause of a bug on the Miss fortune release patch >_>. so shush we had server crashes for up to a week, one champ. being disabled wont hurt you.
so just because things were worst before it means that any bad things that happen now is ok because it's not as bad as before? sorry but what?
it's really stupid when a champion has just been reworked and gets disabled pretty much immediately, what is the point of releasing the rework if you are going to disable the champion so quick? just take some extra time and release the rework at a later date when there are no more bugs that will cause you to disable the champion
NewFoundAbility1 votesit's really stupid when a champion has just been reworked and gets disabled pretty much immediately, what is the point of releasing the rework if you are going to disable the champion so quick? just take some extra time and release the rework at a later date when there are no more bugs that will cause you to disable the champion
Do you know how to design a game? No? Then don't talk like you do.
From a game designer to a gamer. It's irritating to see comments like this.
ZephyrDrake1 votesDo you know how to design a game? No? Then don't talk like you do.
From a game designer to a gamer. It's irritating to see comments like this.
why? because it's the damn truth? there is no point in releasing something that has a well known bug, if all you are going to do is disable it pretty much immediately. Sorry but that's just common sense, unless you are under pressure of having the game release by contractors there is 0 reason for you to do it and not simply wait until the bugs get iron out
NewFoundAbility1 votesunless you are under pressure of having the game release by contractors\
Everyone has deadlines, and if you don't hit them that isn't good for the company, no matter how many bugs.
Jari1 votesThey can leave that part out and push it in during the middle of the patch once it's fully set. They've proven that they can.
woobee1 votesLittle Mac has horrible recovery,
But you don't play Little Mac, do ya?
NewFoundAbility1 votes#This isn't Smash Bros., dude.
http://www.quickmeme.com/img/34/3470092d46da13c669b6a1f07cda4b469273a65533f9512ad261fb284183d2cc.jpg
woobee1 votesMan, I thought he would recognize me...
This doesn't concern you, mortal. This is between Little-Mac-Is-Op and me.
I saw him in a previous game and thought he would recognize me.
L Rayquaza1 votesStill have all the Tahm Devour bugs, I really want to love Tahm but the bugs make him too risky =\
Kaelnor1 votesIt's quite annoying at the least. Rito seems to be dropping the ball sometimes. Personally I hope that Fiora goes live tomorrow or something...but I still have my doubts.
JohnnyNoxid1 votesBugs are not that easy to find, contrary to the popular belief of those that never program.
