How readily punished is a cut-and-dry AFK?

Jo0o·9/9/2016, 1:27:06 PM·1 votes·513 views

Hey all, had an interesting game last night. I was in a 4-man premade with friends, and the single rando was our jungler who decided to take first-time Yorick. Dude played poorly, complained (we either ignored this or attempted to cheer him up, we aren't a stereotypical toxic premade), attempted to surrender despite my crew carrying us about ten kills up at that point, stated he was "busy" despite only being 26 minutes into a game, complained some more, and then AFK'd. He was about 2/7. Hilariously, this isn't a sad story, as my friends and I continued to stomp the enemy team and wound up winning the 4v5 handily with a huge kill margin, and I got my S+ for my third level 7 mastery token with Bard =D

But this behavior does piss me off, and it also strikes me as one of the more cut-and-dry AFK cases. The Yorick clearly was tilting himself and had some sort of issues going on IRL, clearly stated his intention to leave the game, attempted to surrender a winning game for no good reason, and then bailed on us. It's obvious that he wasn't just disconnecting. So, color me somewhat surprised that our reports didn't get any feedback response.

I absolutely understand that we wouldn't get a feedback response from Riot unless our reports actually triggered a punishment, but given how flagrant this infraction was, I really thought we'd get it. Does this kind of behavior operate on a "strikes" system? I'd have expected it to be similar to hate speech, in that it's deserving of quick and decisive action from Riot to curtail.

4 Comments

DrCyanide9/9/2016, 1:35:15 PM1 votes

It's a tolerant system. It realized stuff comes up every now and again, so it won't punish for AFK'S few and far between. If someone regularly tilts and goes AFK, they'll start to get penalties, mostly having to wait before finding a game (up to 20 minutes before the queue timer will even start).