[quake3] Supported protocols

[Stephan Reiter]

Ah, I think I didn't express myself clearly when I wrote that. I was 
refering to Chris' suggestion when I suggested that trying "that" was 
pointless, as in changing PROTOCOL_VERSION and hoping that it works.

Of course Id used the version to distinguish between versions of the 
protocol and give informative error messages when there's a mismatch. That's 
pretty much the standard approach to this sort of problem.

Stephan

----- Original Message ----- 
From: "LinuxManMikeC" <linuxmanmikec at gmail.com>
To: <quake3 at icculus.org>
Sent: Saturday, April 19, 2008 4:52 PM
Subject: Re: [quake3] Supported protocols


> Unless he's worked with a Licensed copy of the 1.17 source, Chris has
> only the SDK to compare to.  There is still the rest of the engine
> where changes could have been made that affect the protocol.  One
> obvious change I could point out is when they released Team Arena.
> Before that it was bug fixes.
>
> Stephan, just letting the changes in the protocol allow a session to
> blow up is very bad software design.  There is no guarantee it will
> blow up immediately upon encounter of a discrepancy.  It would
> probably keep going for a while with corrupted data and then fail with
> no explanation, all while ruining the game for everyone else.  With
> the version identifier, you have something to test for.  I wouldn't
> expect id to be incrementing protocol versions without good reason.
> One reason I can think of (and agree with) for incrementing the
> version without obvious changes to the protocol is to push critical
> bug fixes on the users.  Users don't often think or care about bug
> fixes, so make them care.
>
> Mike
>
> On Sat, Apr 19, 2008 at 3:13 AM, Stephan Reiter
> <stephan.reiter at gmail.com> wrote:
>>
>>
>> What sense would it make for id to change this definition and not modify 
>> any
>> headers or networking functions? Trying this is pointless in my opinion 
>> ...
>> Even if it worked for a while, I'm sure that at some point discrepancies
>> would crop up and in the best case you would be kicked from the server.
>>
>>
>>
>> ----- Original Message -----
>> From: Christopher Bunting
>> To: quake3 at icculus.org
>> Sent: Saturday, April 19, 2008 3:48 AM
>> Subject: Re: [quake3] Supported protocols
>>
>>
>> Hello,
>>
>> What happens if your change PROTOCOL_VERSION in qcommon.h to the protocal
>> version that the server supports? Look at the 1.17 source code or 1.30, 
>> it's
>> all pretty much the same, the numder is all that seems to be updated.
>>
>> Chris
>>
>>
>> On Fri, Apr 18, 2008 at 1:10 PM, Mariusz Przybylski <pay7n at o2.pl> wrote:
>>
>> > Hi,
>> >
>> > Which protocols ioq3 currently supports ? Yesterday i've tried to 
>> > connect
>> to one of the NoGhost 1.16n servers, and received wrong protocol error.
>> >
>> > Currently NoGhost is 3rd most played q3 mod today, right after Urban
>> Terror and CPMA. However it uses protocol version 43 (point release 
>> 1.16n)
>> thus forbidding ioq3 to connect.
>> >
>> > What I thought of is that it would be a very good idea to give a 
>> > support
>> for older protocols (like 1.16, 1.31 etc.), to make ioq3 client actually
>> USEFUL for real gameplay. I don't really know how much work it would take 
>> to
>> have multiple network codebases, but surely it would pay off, by gaining
>> more players' attention, not only developers. And there are at least half
>> hundred players on 1.16 platform.
>> >
>> > Would it be possible to have older protocol(s) supported? And if yes, 
>> > by
>> what means?
>> >
>> >
>> > --Mario
>> >
>> > ---
>> > [Attachement]
>> >
>> > Protocol version, Point release version
>> > 68, 1.32
>> > 67, 1.31
>> > 66, 1.30
>> > 66, 1.29h
>> > 48, 1.27g
>> > 46, 1.26
>> > 45, 1.17
>> > 43, 1.16n
>> >
>> > ---
>> > To unsubscribe, send a blank email to quake3-unsubscribe at icculus.org
>> > Mailing list archives: http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?50
>> >
>> >
>> >
>>
>>
>
> ---
> To unsubscribe, send a blank email to quake3-unsubscribe at icculus.org
> Mailing list archives: http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?50
>
>