You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Protocol 10002 was the first(?) protocol extending Quake's limits. In the last years Fitzquake's protocol 666 has become a new standard at least for mappers. Please use 666 rather than 10002.
reQuiem already supports playback of 666 demos from what I know, maybe it would be a small and easy task.
Look into protocol 999 too, it might be overkill though. No idea where it is used and why it was needed.
The text was updated successfully, but these errors were encountered:
I got a bit more into this topic when looking at issue #45 and issue #16.
reQuiem currently only supports setting sv_protocol to 15 (standard) or 10002 (BJP3).
References to the other protocol versions almost exclusively are contained to cl_parse.c. It looks like reQuiem only deals with those versions as an multiplayer client or in demo playback, and not as a host.
So it's not completely trivial to make it support Fitzquake protocol as a host... although I agree it would be a good thing. With the examples we have available of using that protocol in other engines, it probably wouldn't be too tricky. Famous last words?
The most fiddly part would be making it behave nicely with reQuiem's current auto-host-protocol-selection behavior that chooses between standard/BJP3.
Protocol 10002 was the first(?) protocol extending Quake's limits. In the last years Fitzquake's protocol 666 has become a new standard at least for mappers. Please use 666 rather than 10002.
reQuiem already supports playback of 666 demos from what I know, maybe it would be a small and easy task.
Look into protocol 999 too, it might be overkill though. No idea where it is used and why it was needed.
The text was updated successfully, but these errors were encountered: