VG Community Forums

API/VGP Don't Transfer with Name Change?


#1

I recently decided to spend the ice and change the name. I’m really against Smurf accounts to pad stats or what not. I noticed that now on my VGPRO account, my game total has been cut in almost more than half which has also effected my stats. Big time. Why is this? Can it not register/transfer stats? Why did it carry some of my games from my last name?

EDIT: on my profile in the VG app and UI, it still has my at my 731 wins. VGP has me around 230 now. :face_with_monocle:


#2

I just queried the API directly, and your stats are intact after your name change.

So what’s probably happening is that VGPRO stores your data indexed by IGN, and since that’s changed, some of your previous data is no longer connected to your new IGN. (The data retrievable from the API only goes back a few months. For data prior to that, VGPRO is relying on information they’ve stored in their own database.)

I do recall that they once DID track people’s stats across name changes, but a lot of people – pros, it seems – objected to that, so Pierre stopped doing it.


#3

But isn’t strange that it has over 200 games logged for my new name, when I’ve likely played 20-30 on it? Why do you think it transferred some of my old IGN games and not my new?

Also, as a side note, not sure if this is the case with anyone else: my stats from games from the last 6 hours haven’t been posted.


#4

Nope, that’s what I was trying to explain above: A call to the API with your current name will retrieve those 200+ matches as long as they’re within the retention window (which is around 100 days). Matches older than that don’t exist as far as the API is concerned.

VGPRO was able to show you more data because they were aggregating the stats on their own. When you changed your name, those aggregated stats are NOT transferred to your new name, because VGPRO no longer tracks name changes for the reason I mentioned above.

LATEST MATCHES IN ALL API SHARDS:
---------------------------------

na - 2019-03-07T19:13:31Z (end: 5h 03m 33s ago) - id: 0deea770-71ae-420b-b9cd-f6a9b8d14998
eu - 2019-03-07T19:16:02Z (end: 5h 03m 09s ago) - id: 4d4358b3-9d52-4c60-bb7d-ddd6a3684025
sa - 2019-03-07T19:12:13Z (end: 5h 03m 47s ago) - id: f3d3335c-f58d-4f22-98e3-d4f97a2bee0c
sg - 2019-03-07T19:13:09Z (end: 5h 04m 51s ago) - id: 44365018-dd76-474c-8aad-1f52809885dc
ea - 2019-03-07T19:12:46Z (end: 5h 04m 12s ago) - id: 9a50a608-8a35-485d-ac5c-6894050b4c19
cn - 2019-03-07T19:10:59Z (end: 5h 05m 05s ago) - id: 9e38adb1-0a34-464a-bd75-441b23f994d9

Looks like the API data is delayed more than 5 hours at this point. No idea if it’s just delayed or down. There’s nothing on the SEMC Slack channel about it.


#5

A lot more time has passed… any news from SEMC about the API?


#6
LATEST MATCHES IN ALL API SHARDS:
---------------------------------

na - 2019-03-07T19:13:31Z (end: 41h 21m 14s ago) - id: 0deea770-71ae-420b-b9cd-f6a9b8d14998
eu - 2019-03-07T19:16:02Z (end: 41h 20m 50s ago) - id: 4d4358b3-9d52-4c60-bb7d-ddd6a3684025
sa - 2019-03-07T19:12:13Z (end: 41h 21m 28s ago) - id: f3d3335c-f58d-4f22-98e3-d4f97a2bee0c
sg - 2019-03-07T19:13:09Z (end: 41h 22m 32s ago) - id: 44365018-dd76-474c-8aad-1f52809885dc
ea - 2019-03-07T19:12:46Z (end: 41h 21m 53s ago) - id: 9a50a608-8a35-485d-ac5c-6894050b4c19
cn - 2019-03-07T19:10:59Z (end: 41h 22m 46s ago) - id: 9e38adb1-0a34-464a-bd75-441b23f994d9

Their community relations person posted yesterday that he was relaying the information to the devs, but obviously the problem hasn’t been fixed yet :point_up: