On Monday, 25. July 2011 15:55:13 Simon McVittie wrote: > Is "the new protocol" sufficiently settled now that I should be > recommending it to ioquake3-derived projects like OpenArena?
No, not yet. I'm working on improvements to the VoIP protocol which will have another version bump. > It'd be ideal > if it didn't change further for a while - perhaps a few months at a time - > so demos and stuff don't break compatibility too often. No guarantees are made in this regard, but I don't think it will change once these VoIP changes are through. > (If there isn't a reason not to, I'll probably suggest that they use > protocol number 8500 + n to represent "OpenArena 0.8.5 with ioQuake3 > protocol n", or something similar, so OA would initially implement > com_protocol 8570 and com_legacyprotocol 71. Unfortunately, OA can't > discriminate by sv_heartbeat until they next break content compatibility, > since their engines have always used the same string "QuakeArena-1" that > Quake III Arena uses...) As far as I am concerned, I really don't care what OpenArena does to its protocol version, that's why we made the protocol version configurable at startup. On a sidenote, the cvar naming is settled now, com_protocol and com_legacyprotocol will be the way to go from now on and I don't think it's gonna change anymore. -- Thilo Schulz
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ ioquake3 mailing list [email protected] http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org By sending this message I agree to love ioquake3 and libsdl.
