Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate protocol 10002 in favour of 666 (or 999) #17

Open
SpiritQuaddicted opened this issue Jan 3, 2014 · 1 comment
Open

Deprecate protocol 10002 in favour of 666 (or 999) #17

SpiritQuaddicted opened this issue Jan 3, 2014 · 1 comment
Assignees

Comments

@SpiritQuaddicted
Copy link
Owner

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.

@neogeographica
Copy link
Collaborator

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.

@neogeographica neogeographica self-assigned this Jul 29, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants