Semi-breaking changes to /pub/player/{username}/games/{yyyy}/{mm} endpoint

Game URL format update:

The `/pub/player/{username}/games/{yyyy}/{mm}` endpoint now uses a uuid for the url instead of large integer and has a slightly different path. So `https://www.chess.com/game/live/4795281310` is now `https://www.chess.com/game/a6e9f7d8-8b7f-11ea-9bde-eb3d40010001` although both urls still work and the legacy url is still present in the pgn data. This was first reported two weeks ago but I'm not sure exactly when it was changed as I couldn't find an official change log aside from the inactive pinned topic.

Potentially new values in the results:

I got these based off an old blog post I made where I put an example of what the endpoint returns but I'm not sure if I removed any values for brevity when I posted. Please correct me if you happen to have a more accurate version of the endpoint.

rated - Boolean:

true/false value probably representing if the user was playing rated chess?

eco - String:

This is a url to the chess.com wiki for the opening in the game, this was and still is available via the pgn data but it's nice that they put it there so we don't have to parse pgn data to get it. I should note that this was previously available and documented but was removed at some point.

white.uuid and black.uuid - String:

I'm not sure what these do but they are present.

tcn - String:

Possibly an encoded string representing the moves of a game. I'm not sure what encoding was used but it might be related to the implementation of web based stockfish https://github.com/lichess-org/stockfish.wasminitial_setup - String: I have been unable to find an example where this was populated but I'm guessing it has something to do with custom games with a custom setup
---
In this image I've underlined what I think they added in green and what they changed in red

Thanks for posting this. I notice the new URL using a UID also doesn't include 'live' in the path:
> `https://www.chess.com/game/live/4795281310` is now `https://www.chess.com/game/a6e9f7d8-8b7f-11ea-9bde-eb3d40010001` 

The api just updated a load of these UUID urls to the normal live/<number> urls which caused my app to duplicate all the games.

It appears the UUID change was temporary? It's now back to /live/<number> everywhere, I was using that string as a unique identifier in another project and didn't notice until now, I guess it still works as a unique identifier lol. 
"every change breaks someones work flow"
https://xkcd.com/1172/

It seems to be reverted now