It will be a mess to drop, actually, because someone would need to go through all versions and decide if their code is needed for the newer version or not (thanks to C++ inheritance, the 1.3.2 protocol actually uses the 1.2.5 protocol's functions for the packets that didn't change). And as I've already written, it makes for an easier transition between two protocol versions - you can have both protocols enabled and only advanced users / testers try out the new protocol and report bugs, while others can keep working on other stuff.
If that is possible, it will be the best solution. But I'm afraid the server version is reported in the protocol sooner than a handshake (I suspect the "0xff server ping" packet will have the info, which is sent without the handshake)
(10-26-2012, 05:35 AM)Luksor Wrote: (D) Take client's version from the handshake and send it back to him as the server version to enable the client to connect.
If that is possible, it will be the best solution. But I'm afraid the server version is reported in the protocol sooner than a handshake (I suspect the "0xff server ping" packet will have the info, which is sent without the handshake)