Maniaplanet Forum

While I can still retrieve player login information via the web services API for logins that were created longer ago, it appears that new logins (created within the last few days) are unknown in the API. E.g. avacast gives an exception in the get method of \TrackMania\WebServices\Players, returning getHTTPStatusCode response '404 Not Found' and getMessage response 'Unkown player' (which should be 'Unknown', btw).

Is this related to the recent server crash? Can Nadeo please look into it?

This was quietly fixed about 2 days ago, thanks Nadeo.

The typo in 'Unkown player' wasn't, though.

Xymph wrote:The typo in 'Unkown player' wasn't, though.

Because it's a "won't fix"

Xymph wrote:While I can still retrieve player login information via the web services API for logins that were created longer ago, it appears that new logins (created within the last few days) are unknown in the API. E.g. avacast gives an exception in the get method of \TrackMania\WebServices\Players, returning getHTTPStatusCode response '404 Not Found' and getMessage response 'Unkown player' (which should be 'Unknown', btw).

This problem has returned: since a few days newly created logins like tsounas21 and bestpower97 (and more) return the above errors via the API. Nadeo, please fix again?

Xymph wrote:

Xymph wrote:While I can still retrieve player login information via the web services API for logins that were created longer ago, it appears that new logins (created within the last few days) are unknown in the API. E.g. avacast gives an exception in the get method of \TrackMania\WebServices\Players, returning getHTTPStatusCode response '404 Not Found' and getMessage response 'Unkown player' (which should be 'Unknown', btw).

This problem has returned: since a few days newly created logins like tsounas21 and bestpower97 (and more) return the above errors via the API. Nadeo, please fix again?

Even logins (such as cheater 'libacsergeto') created two weeks ago are not yet known on the API server. Nadeo, please FIX this problem!
Thanks.

It appears this was quietly (again, sigh...) fixed, thanks Nadeo.