Howard Chung

So for /matchPlayers, this appears to be data that could be assembled with the existing APis. Is the number of calls too high to do this by making individual calls?...

I believe we can't get around the 10 players part, since even if we aggregate the logic on the server side it'll still make the same queries to the database...

Note that the purchase data is actually the sum of the purchase times, since I think I was trying to compute "average time of purchase" for each item. This may...

* node_modules: Yes, once you install a module via `npm install ml-random-forest` you can import it via `require` * Check out the `store/queries.js` file for the functions that do database...

I believe this was due to a temporary bug that was fixed later, we didn't backfill the correct data.

Yeah, I'm not sure how many people would use this if you had to input all the data manually. It wouldn't be much more beneficial than the spreadsheet approach, especially...

The problem is that we can't link the match IDs with the changes in MMR.

Previously, we were able to check a player's current MMR at any point. Since we also know when a player finishes a game, we can just associate that MMR change...

yes, it was removed along with introduction of medals

Without any data verification I'm not sure we shouldn't store this data server-side since we won't know whether it's accurate. Maybe it could be done client side and saved in...