Crashing causing me to be placed in lower tier.

Gr0wnBalanced··1 votes·207 views

I can not begin to tell you how upset i am with all the problems i have been having with league of legends. All i want to do is provide feedback and not feel like I'm being treated unfair by riot. I was unable to connect until the 18 minute mark and it happens quite often. When i connected, it lead to a loss, of course because i was gone for 20 minutes. Now i am being placed for 5 games in lower que BECAUSE OF AFK. This it not right and as i said, is not the first time this exact problem happened.

4 Comments

Gr0wnBalanced1 votes

P.S. Its 20 minutes each game. 20 minutes x 5 is nearly 2 hours of my time waiting to play a game of entertainment. WHEN ITS NOT MY FAULT.

RISE Shlack1231 votes

Well, your computer or your internet is the cause. If Riot was to blame for your crashes, then we'd all be having similar issues. But since the forums aren't littered with application crash QQ threads, I have to assume it's on your end, i.e. your fault.

Open a support ticket with Riot, like Deep Terror Nami said. And stop complaining on the boards because there is nothing that can be done about YOUR computer issues.

Deep Terror Nami1 votes

If it happens a lot, why do you keep playing? You need to fix the problem before you queue up. Even if it's on Riot's end that doesn't absolve you from the responsibility of figured out how to get it fixed before you ruin the game for your teams.

If you can't fix your problem by following the Connection Troubleshooting Guide then submit a Support Ticket to try and get help. You can also post your issues on the Help & Support board.

RISE Shlack1231 votes

If you're constantly having issues playing League, then you either have issues with your computer or possibly your internet provider. Either way, after the first couple of crashes, you should have stopped playing Ranked at the very least so you could investigate why your PC can't run League.

If you've done it enough to get demoted and/or sent to low-priority queue, then that's your fault.

More from Report a Bug