Happy 10th Error-aversary

JamesfokingBond·11/4/2019, 8:44:30 PM·15 votes·9,245 views

Straight to the point: You find a match, choose a champion, you are in the loading screen, it reaches a 100%, you wait and wait until you find yourself being stuck in that screen forever, completely locked out of your computer while the game has actually started, you are unable to end task or even exist the lovely game and end up losing the match with a possibility to ruin your precious machine and nerves as a bonus!

Thousands of players are complaining of the same error for the past years, yet - surprisingly? - nothing has been remotely fixed nor effectivly addressed.

And the waiting for a wizard to fix the problem continues ... Happy Error-versary everyone!

5 Comments

Big Tiddy Fox GF11/5/2019, 4:54:38 AM2 votes

Inb4 someones says "iT's YoUr GaEm I nEvEr HaD tHaT iN mY eNtIrE cArReEr Of LeAgUe JuSt UsE hExTeCh ToOl RePaIr"

Btw the famous "Hextech Tool Repair" that fix stuff like just one time out of an hundred time.

The JigSAW11/5/2019, 3:13:27 AM1 votes

I've had this happen about three times in the last month alone. Had to restart the computer and log back in, luckily I was able to make it in before 2 minutes - other people have had the same issues in several games this week alone. For me, though, it started with the change to this horrid new client launcher. I don't know why they decided to release an untested, unreliable launcher so close to the end of the season but its another dumb decision in a long line - hope they look into it.

Its the FREEDOM11/6/2019, 10:23:11 PM1 votes

I still get this bug every now and then. I spent a whole two weeks talking to A riot employee. Tried everything they could think of. Tried everything I could think of. Eventually The guy sent me over to ANOTHER riot employee and guess what? He wanted me to repeat the processes we did all over again. So I said "fck that. fck you and get back to me when you actually find a fix. That was ...this summer I believe? 6 months ago ish.

So aside from the lack of knowledge Riot's support team has on this bug. "A" for effort at least?