196
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − == Goal and how to help ==+ − − One day, eventually, TrackMania will reach its EoL. This is about documenting as much as possible to eventually get the point of having a fully functional custom authentication server. If you want to give help, go ahead. Just grab fiddler and start tweaking around with the game. You can check what has already been done on the [[Web_APIs/Progress|Progress]] page. − + Line 258:
Line 256: + + +
use proper intro and more encyclopedic tone
The TrackMania Forever game client uses a {{wp|XML-RPC}} based '''web API''' to communicate with the master server. This article attempts to document the API with the potential goal of eventually having a fully functional custom master server.
== Basic concepts ==
== Basic concepts ==
TrackMania uses a XML-RPC-like API to authenticate players, load server lists, load rankings, etc... Here is some documentation about what has been reversed engineered. A lot is still left to be documented.
TrackMania uses a XML-RPC based API to authenticate players, load server lists, load rankings, etc. Below is some documentation about what has been reversed engineered. A lot is still left to be documented, as logged on the [[Web_API/Progress|Progress]] page.
The game sends HTTP(s) POST requests to
The game sends HTTP(s) POST requests to
* UploadOfficialRecord
* UploadOfficialRecord
* ValidateSoloAccount
* ValidateSoloAccount
== How to help ==
Use a {{wp|packet analyzer}} to see the game's communication while experimenting with client features, and describe requests and responses in as much detail as possible.
[[Category:Specifications]]
[[Category:Specifications]]