AFK Rules are Unfair, Riot Standing Right There

Heez Tiger·1/31/2016, 1:29:42 AM·2 votes·347 views

I feel like I am a pretty good person in League. I'm not toxic. I don't intentionally feed. I play games in their entirety. That is, however, when my internet router decides to comply. When it doesn't (now I'm getting to the point) I am forced, unwillingly, to AFK. This gives my AFK strikes, which in turn gives me low priority. I don't have the money to buy a router that doesn't do this, so there is really nothing I can do about the problem.

 I don't want to wait 20 minutes before I can play again because I did something that I couldn't help doing.  I am all for the idea of low priority, I think it is a great way to punish people who rage quit often without being too serious.  Although, when someone can't hep but leave - even if they come back and finish the game - they get punished the same way that the rage-quiters do.

 The system that decides who needs to be punished for being AFK needs to change.  I thought a system that bases whether or not person should be convicted should be based on ping.  For instance, if a person has had 600 ping for the past five minutes and they disconnect, they should be let off the hook.  In all cases, if a person uses the "exit" button to leave a game, that should be an automatic AFK strike.

 It should also be based on score.  Say, if a person is 20/0 and they disconnect, there is most likely a good reason for it, and they certainly didn't feed the entire enemy team and then left out of anger or spite.  This person should be let free.  Also, if a person leaves early in the game, comes back later, and does relatively well for their team, they should not receive low priority, especially if they win.

 Now, I am not a programmer, I don't know what is possible to do, and I haven't extensively observed AFK patterns among many different players, I don't know if any of this will work.  But I do think that the current low priority system is flawed and unfair, and I hope to see it changed in the future.

0 Comments