PUBGTracker api returns a collection of the last 10 "changes" in stats, and adds a message if appropriate(new high rank, etc).
Each collection element looks like this:
{ "Match": 3, "MatchDisplay": "Squad", "Season": 2, "RegionId": 4, "Region": "oc", "Date": "2017-07-16T11:45:48.933", "Delta": 2.4909999999999854, "Value": 1840.197, "message": "Climbed to Rank #8,492 in oc!" }
Unfortunately the Match and Season values returned by the api look to be indexed from 1, and hence dont match up with the existing enums in PUBGSharp.
Fortunately they also provide the MatchDisplay which we can use, but the only clean solutions for Season is to either leave it as is, or adjust PUBGSharps enums(which isn't great obviously, as it would break things for people who have stored the previous enums somewhere).
Jinivus
commented
7 years ago
PUBGTracker api returns a collection of the last 10 "changes" in stats, and adds a message if appropriate(new high rank, etc).
Each collection element looks like this:
{ "Match": 3, "MatchDisplay": "Squad", "Season": 2, "RegionId": 4, "Region": "oc", "Date": "2017-07-16T11:45:48.933", "Delta": 2.4909999999999854, "Value": 1840.197, "message": "Climbed to Rank #8,492 in oc!" }Unfortunately the Match and Season values returned by the api look to be indexed from 1, and hence dont match up with the existing enums in PUBGSharp. Fortunately they also provide the MatchDisplay which we can use, but the only clean solutions for Season is to either leave it as is, or adjust PUBGSharps enums(which isn't great obviously, as it would break things for people who have stored the previous enums somewhere).