developer-relations icon indicating copy to clipboard operation
developer-relations copied to clipboard

[DOCS] Clarify what `gameEndedInEarlySurrender` field means in match-v5 API

Open chulman444 opened this issue 2 years ago • 2 comments

Bug Description
Its vagueness in name and lack of description has confused many developers.

Problem Description
Spread of non-official information on how you can tell if a game is a remake or not with game duration:

  • (2022) https://discord.com/channels/187652476080488449/379429593829867521/1050783327600251021
  • (Today) https://discord.com/channels/187652476080488449/379429593829867521/1152203007656730715

But this has been 'verified' by a user who collects his matches or has his own data or something in 2011:

  • https://discord.com/channels/187652476080488449/379429593829867521/922583114587439124
  • https://discord.com/channels/187652476080488449/379429593829867521/922595018206773328

Lists 235s=3m55s and 248s=4m8s games with gameEndedInEarlySurrender: true, but even with this non-official information is spread, at least on Discord.

Expected Result
No confusion on what gameEndedInEarlySurrender is. Either rename it to be isRemake or something, or add description like "if gameEndedInEarlySurrender is true, it means there was a summoner who disconnected, and that team agreed to remake the game."

Actual Result
Nothing. Vague field name, no discription.

Developer Impact
Misinformation and non-official information spread for almost 2 years or more.

The field name becoming useless.

Player Impact
Well ... in game won't have impact, but if players decided to use a website that uitilized misinformation, the players would be confused.

Preconditions
A dev wants to know how to know if a game was a remake, because doc is missing information.

Issue Comments
The 235s and 248s games that someone else posted is missing match id. Besides remake games with more than 3min or 3m30s, I have the following matches that support my opinion that gameEndedInEarlySurrender: true means a remake:

  • EUW1_6590987185 18 min game with gameEndedInEarlySurrender: false, gameEndedInSurrender: true despite the 2022 message above saying 15~20 min game being an early surrender game.
  • KR_6688164075 13m48s surrender with gameEndedInEarlySurrender: false, gameEndedInSurrender: true despite the 2022 message above saying 15~20 min game being an early surrender game. It's not, even when the game is even shorter than 15 min
  • KR_6693584833 1m40s early surrender game with gameEndedInEarlySurrender: true, gameEndedInSurrender: false, as it should be.

I just want to see actual remake games that are past 3m30sec in duration.

From Fandom wiki "surrendering > remake" says:

Casting a remake vote is available from at least 1:30 and until at most 3:29 game time (when the 90 consecutive seconds of idling are completed by 1:30 and 2:59, respectively) for teams to decide if they want to remake a game or not.

And it also says that

Initiating a surrender vote will display a pop-up menu of the type of surrender for 60 seconds.

So the latest remake game is longer than 4m29s if the vote was initiated at 3:29 and ended at 4m29s. And adding that extra time before the Nexus goes boom.

Please add description. Rito

chulman444 avatar Sep 15 '23 13:09 chulman444

Hi - I'll see what clarification I can get and comment back when I have additional info!

tisbells avatar Oct 10 '23 15:10 tisbells

Hi @tisbells, and progress on this?

ThreeHoolagins avatar Mar 17 '24 06:03 ThreeHoolagins

Hi! Here is what I've heard:

gameEndedInEarlySurrender refers to games that are remakes. Remakes can only occur when a player is disconnected/AFK for more than 90 seconds in the first 3 minutes of the game.

A remake can only occur if the game was terminated in the first 3 minutes of the game. Any surrender after that will be recorded as a loss. When a player goes AFK after 3 minutes, the other players on the team have the option to surrender, but it will be counted as a loss. Some more information about remakes can be found here.

The team is aware the field name is misleading and they hope to update this in the future, but for now we will update the description in our docs.

tisbells avatar Apr 29 '24 19:04 tisbells