Closed Yaribz closed 10 years ago
the protocol was recently changed/extended very fast, so its not really possible to give a "current" protocol version.
clients/server also have a different implementation set, atm you have to read lobby server code / docs to get current implementation grade.
see https://github.com/spring/uberserver/blob/master/protocol/Protocol.py#L18
i know, thats not good, but atm all lobbies and servers are way behind the specs.
also as note: some commands where implemented wrong and specs didn't match current implentation, but this should improve over time.
note 2: why do you want to implement a new lobby? you should improve the existing ones, there are so many of them, but all of them are lack of some features :-|
You're mixing specs and proposals. The spec used to exist, and was very close to server implementation. Now this spec has been updated with various proposals from various sources, this makes it a proposal document and no longer a specification.
We used to have a specification document which was consistent with server implementation, and we should have kept this document available instead of replacing it with a proposal document.
I don't want to implement a new lobby, I'm just trying to show you that a protocol specification is useful (especially more than a proposal document).
ok, than this is a feature request at uberserver to make it currents specs available.
Where is the lobby protocol specification for protocol in use currently?
I know there is http://springrts.com/dl/LobbyProtocol/ProtocolDescription.html , but this is a specification full of change proposals, which differs more and more from current real protocol. This document isn't usable by a new lobby developer to code a lobby client compatible with current lobby server for example.
It is much more important to make available a specification of current lobby protocol than a specification full of proposals.