back-end code bug / missing critical feature: loss prevention

Srednal·12/12/2014, 1:33:32 AM·2 votes·943 views
League of Legends Match History

bug: 4 leavers in 1 game, not loss prevented. Ideally, back-end code should detect this situation and auto-end the game. However, if this is difficult to implement for some reason, at least detect the situation and don't subtract from the ranked score of players on the losing team. As I see it, this game should have been auto-ended by the server after the first few minutes started out as 2v3. 2 of the enemy team returned, making it 2v5. This is not fair. I should not lose points on my ranked account because of Riot's poor back end code. Additionally, it's annoying waiting 20 minutes for an auto loss. It's not like the game started and people left. Only a few people even played at all. This condition is simple to detect.

10 Comments

RiotEambo12/28/2014, 7:19:46 AM2 votes

Hi Srednal,

Loss Forgiven is only activated for server-side problems affecting a large amount of users. This technology has a much larger impact than just giving loss forgiven, including:

  • Reduced LP for winning teams
  • Disabling of Ranked Queues
  • At times, disabling of the login entirely

This is not enabled on a per-game basis, and cannot be retroactively added unfortunately.

The reason for it not being automatically implemented is the abuse potential. If Riot forgave/stopped losses for people disconnecting or AFKing, teams could abuse it to stop a portion of their team/friends getting a loss. Riot are always implementing systems to try and tackle leavers and AFKers and toxic players - but with the added complication of avoiding abuse too.

Srednal12/28/2014, 7:12:54 AM1 votes

here's another one. Fix this already. This should be a ridiculously easy back end fix. http://matchhistory.na.leagueoflegends.com/en/#match-details/NA1/1679296056/32832530?tab=overview