StarCraft II API stale data / teams mmr thresholds

Hello,

After the successful implementation of the API fix due to the previous post on the issue by Irri, it has been noted that the API is still experiencing some issues. Here is a list compiled by Nephest. Links have been removed due to inability to post links here.

Problem: The KR ladder endpoint returns stale data. The stats(like mmr and games played) and member list are not updated.

Example: the player with /profile/6056956/1/llllllllllll profile has 6883 mmr and 10 games, while their actual stats are 6936 mmr and 18 games atm.

Problem: KR league endpoint returns stale league ids.

Example: the API returns max KR ladder id as 75523, while the actual max ladder id is 75525 atm.

Problem: League endpoints return stale ladder ids for season 45.

Example: does not contain ladder id 295688, but you can fetch that ladder from. You can also see a valid league key in the response: league_key":{“league_id”:2,“season_id”:45,“queue_id”:201,“team_type”:0}

Additional data: missing ids(approximate):

US 295688 - 295939

EU 233768 - 234027

KR 75280 - 75316

Problem: US mmr thresholds for 2v2 are invalid

Example: Diamond3 mmr range is 3600-3840, and Masters1 mmr range is 4421-4548. The thresholds are disconnected and there is a huge rating gap between them, which makes it very hard to promote to masters.

Game client bug: the game client will show 0-0 league tier mmr threshold if the player has an mmr in 3840 - 4421 range.

Please advise when this issue has been officially noted and being explored.

Thank you for your continued support for the API, and receptiveness to feedback.

Sincerely,
Osiris

9 Likes

I’m not a tournament organizer or developer myself but I would like to ask someone over there at Blizzard to look into this issue and get the API working for the sake of our small but dedicated scene. Please help out some of your most loyal customers.

6 Likes

Adding relevant pieces of JSONs

Stale ladder bug

KR and EU /data endpoints return stale data

KR

The player with /profile/6056956/1/llllllllllll profile from kr.api.blizzard.com/data/sc2/ladder/75512

{
      "rating": 6883,
      "wins": 10,
      "losses": 0,
      "ties": 0,
      "points": 432,
      "longest_win_streak": 10,
      "current_win_streak": 10,
      "current_rank": 3,
      "highest_rank": 100,
      "previous_rank": 0,
      "join_time_stamp": 1612184353,
      "last_played_time_stamp": 1612284491,
      "member": [
        {
          "legacy_link": {
            "id": 6056956,
            "realm": 1,
            "name": "llllllllllll#13526",
            "path": "/profile/6056956/1/llllllllllll"
          },
          "played_race_count": [
            {
              "race": {
                "en_US": "Terran"
              },
              "count": 10
            }
          ],
          "character_link": {
            "id": 6056956,
            "battle_tag": "메구#31309",
            "key": {
              "href": "https://kr.api.blizzard.com/data/sc2/character/%EB%A9%94%EA%B5%AC-31309/6056956?namespace=prod"
            }
          }
        }
      ]
    }

while their fresh stats from us.api.blizzard.com/sc2/profile/3/1/6056956/ladder/75522 are

{"points":343,"wins":20,"losses":2,"mmr":6930"}

You can see that the player has already changed their division from 75512 to 75522, but the /data/ endpoints do not return this information.

EU

https://eu.api.blizzard.com/data/sc2/ladder/234881
Serral’s stats:

"id": 16147182660324687872,
"rating": 7160,
"wins": 80,
"losses": 24,
"ties": 0,
"points": 1904,
"longest_win_streak": 13,
"current_win_streak": 5,
"current_rank": 2,
"highest_rank": 200,
"previous_rank": 3,
"join_time_stamp": 1612555174,
"last_played_time_stamp": 1614174714,
"member": [
  {
    "legacy_link": {
      "id": 315071,
      "realm": 1,
      "name": "Serral#769",
      "path": "/profile/315071/1/Serral"
  }
]

while his actual stats are 98 wins, 29 losses, 7113 mmr.

Absent ladder bug

us.api.blizzard.com/data/sc2/ladder/295688 headers

{
  "_links": {
    "self": {
      "href": "https://us.api.blizzard.com/data/sc2/ladder/295688?namespace=prod"
    }
  },
  "league": {
    "league_key": {
      "league_id": 2,
      "season_id": 45,
      "queue_id": 201,
      "team_type": 0
    },
    "key": {
      "href": "https://us.api.blizzard.com/data/sc2/league/45/201/0/2?namespace=prod"
    }
  }
}

This ladder is absent in us.api.blizzard.com/data/sc2/league/45/201/0/2 league

League Tier bug

US 2v2 arranged masters 3 tier

{"id":2,"min_rating":4421,"max_rating":4548}

US 2v2 arranged diamond 1 tier

{"id":0,"min_rating":3600,"max_rating":3840}
4 Likes

I’m really glad many of the API issues got fixed, i hope this gets fixed soon (not soon™)

1 Like

As someone who plays small tourneys and teams for fun, would like to see this resolved :slight_smile:

1 Like

Bumpppppppppppppppppppp. Yes, it’s a complete sentence.

2 Likes

Would be great to see the API continue to stay fixed :slight_smile:

1 Like

Please Bliz, if we could just get a little focus on the API so your amazing, passionate community can continue to thrive, it would be appreciated.

1 Like

Can I piggyback a request to add the in-game chat log to the Client API? So you could go to http://localhost:6119/game or /chat to see the last X chat messages (only the all- and ally-chat that gets recorded in replays). Would be useful for EU customs and region hopping (for machine translation).

1 Like

I hope this get fixed soon.

1 Like

Hello all,

Thanks for the reports and the information shared. Our Starcraft 2 team is aware and investigating.

It may take some time to fully investigate and resolve these due to the nature of the problem, but they will definitely be working on it. We appreciate the heads up!

5 Likes

Hello,

Is there any update on where things stand with this issue?

2 Likes

Hello again,

It’s been a little over two weeks now. Has any progress been made on this issue?

2 Likes

The EU /data ladders return stale data too. I’ve updated my original bug report with more details for EU region.

2 Likes

Anyone knows if there’s any news regarding this topic ?

1 Like

This is happening again. I do not know how your internal systems are organized, but it might be possible that the distorted MMR boundaries are also affected by whatever is causing the API data to return stale.

Please fix.
-samsim

1 Like

It’s mindblowing how often there is an issue with the api. Please fix the issue Blizzard!

2 Likes

Come on guys, this is basic stuff.

Jesus christ blizzard, you could be honest at least - if you’re not planning on fixing it then just admit it and pass the game to the community that actually cares. There are people who would fix it for free on a lunch break, come on.