<div>Hello,</div>
<div> </div>
<div>You are correct. But as the original poster mentioned, he has 1.32 and wanted to connect to a 1.17 server to play the mod. So it can be done. Yes, you can't have 1.17 specified and then connect to a 1.32 server. You can however support all protocals up to 1.32. If you need some kind of proof since everyone on this list seems to want to debate what ppl say, then search google for DXQuake3 and look at it's source code. It's a rewritten directx version of quake using DirectPlay for it's network. It doesn't check for the protocol version and there are no problems on any server version.</div>
<div> </div>
<div>This would be the same if you were to write a Quake 3 client which uses Rakknet. Well, would be the same for anyone if you know what you are doing.</div>
<div> </div>
<div>Chris<br></div>
<div class="gmail_quote">On Sat, Apr 19, 2008 at 1:10 PM, Stephan Reiter <<a href="mailto:stephan.reiter@gmail.com">stephan.reiter@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div bgcolor="#ffffff">
<div><font face="Arial" size="2">If you try to connect with an old 1.17 client to a new 1.32 server you will be dropped because the protocol versions don't match. Rest assured that the Q3 engine only supports a single version of the protocol. The version number is only transmitted to allow checks if both the client and the server "speak the same language".</font></div>
<blockquote style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<div class="Ih2E3d">
<div style="FONT: 10pt arial">----- Original Message ----- </div>
<div style="BACKGROUND: #e4e4e4; FONT: 10pt arial"><b>From:</b> <a title="cbunting99@gmail.com" href="mailto:cbunting99@gmail.com" target="_blank">Christopher Bunting</a> </div>
<div style="FONT: 10pt arial"><b>To:</b> <a title="quake3@icculus.org" href="mailto:quake3@icculus.org" target="_blank">quake3@icculus.org</a> </div></div>
<div>
<div></div>
<div class="Wj3C7c">
<div style="FONT: 10pt arial"><b>Sent:</b> Saturday, April 19, 2008 7:01 PM</div>
<div style="FONT: 10pt arial"><b>Subject:</b> Re: [quake3] Supported protocols</div>
<div><br></div>
<div>Hello,</div>
<div> </div>
<div>You asked what protocals were supported. They are all supported. What I mentioned was a suggestion simply because if you are using version 1.32 source, then you still have support for the 1.17 protocal.. But you won't be telling the server that unless you specify which version. </div>
<div> </div>
<div>Chris<br><br></div>
<div class="gmail_quote">On Sat, Apr 19, 2008 at 12:18 PM, Stephan Reiter <<a href="mailto:stephan.reiter@gmail.com" target="_blank">stephan.reiter@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">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.<br>
<br>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.<br><br>
Stephan<br><br>----- Original Message ----- From: "LinuxManMikeC" <<a href="mailto:linuxmanmikec@gmail.com" target="_blank">linuxmanmikec@gmail.com</a>><br>To: <<a href="mailto:quake3@icculus.org" target="_blank">quake3@icculus.org</a>><br>
Sent: Saturday, April 19, 2008 4:52 PM
<div>
<div></div>
<div><br>Subject: Re: [quake3] Supported protocols<br><br><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px; BORDER-LEFT: #ccc 1px solid">Unless he's worked with a Licensed copy of the 1.17 source, Chris has<br>only the SDK to compare to. There is still the rest of the engine<br>
where changes could have been made that affect the protocol. One<br>obvious change I could point out is when they released Team Arena.<br>Before that it was bug fixes.<br><br>Stephan, just letting the changes in the protocol allow a session to<br>
blow up is very bad software design. There is no guarantee it will<br>blow up immediately upon encounter of a discrepancy. It would<br>probably keep going for a while with corrupted data and then fail with<br>no explanation, all while ruining the game for everyone else. With<br>
the version identifier, you have something to test for. I wouldn't<br>expect id to be incrementing protocol versions without good reason.<br>One reason I can think of (and agree with) for incrementing the<br>version without obvious changes to the protocol is to push critical<br>
bug fixes on the users. Users don't often think or care about bug<br>fixes, so make them care.<br><br>Mike<br><br>On Sat, Apr 19, 2008 at 3:13 AM, Stephan Reiter<br><<a href="mailto:stephan.reiter@gmail.com" target="_blank">stephan.reiter@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px; BORDER-LEFT: #ccc 1px solid"><br><br>What sense would it make for id to change this definition and not modify any<br>headers or networking functions? Trying this is pointless in my opinion ...<br>
Even if it worked for a while, I'm sure that at some point discrepancies<br>would crop up and in the best case you would be kicked from the server.<br><br><br><br>----- Original Message -----<br>From: Christopher Bunting<br>
To: <a href="mailto:quake3@icculus.org" target="_blank">quake3@icculus.org</a><br>Sent: Saturday, April 19, 2008 3:48 AM<br>Subject: Re: [quake3] Supported protocols<br><br><br>Hello,<br><br>What happens if your change PROTOCOL_VERSION in qcommon.h to the protocal<br>
version that the server supports? Look at the 1.17 source code or 1.30, it's<br>all pretty much the same, the numder is all that seems to be updated.<br><br>Chris<br><br><br>On Fri, Apr 18, 2008 at 1:10 PM, Mariusz Przybylski <pay7n@o2.pl> wrote:<br>
<br>> Hi,<br>><br>> Which protocols ioq3 currently supports ? Yesterday i've tried to > connect<br>to one of the NoGhost 1.16n servers, and received wrong protocol error.<br>><br>> Currently NoGhost is 3rd most played q3 mod today, right after Urban<br>
Terror and CPMA. However it uses protocol version 43 (point release 1.16n)<br>thus forbidding ioq3 to connect.<br>><br>> What I thought of is that it would be a very good idea to give a > support<br>for older protocols (like 1.16, 1.31 etc.), to make ioq3 client actually<br>
USEFUL for real gameplay. I don't really know how much work it would take to<br>have multiple network codebases, but surely it would pay off, by gaining<br>more players' attention, not only developers. And there are at least half<br>
hundred players on 1.16 platform.<br>><br>> Would it be possible to have older protocol(s) supported? And if yes, > by<br>what means?<br>><br>><br>> --Mario<br>><br>> ---<br>> [Attachement]<br>><br>
> Protocol version, Point release version<br>> 68, 1.32<br>> 67, 1.31<br>> 66, 1.30<br>> 66, 1.29h<br>> 48, 1.27g<br>> 46, 1.26<br>> 45, 1.17<br>> 43, 1.16n<br>><br>> ---<br>> To unsubscribe, send a blank email to <a href="mailto:quake3-unsubscribe@icculus.org" target="_blank">quake3-unsubscribe@icculus.org</a><br>
> Mailing list archives: <a href="http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?50" target="_blank">http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?50</a><br>><br>><br>><br><br><br></blockquote><br>---<br>To unsubscribe, send a blank email to <a href="mailto:quake3-unsubscribe@icculus.org" target="_blank">quake3-unsubscribe@icculus.org</a><br>
Mailing list archives: <a href="http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?50" target="_blank">http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?50</a><br><br><br></blockquote><br><br>---<br>To unsubscribe, send a blank email to <a href="mailto:quake3-unsubscribe@icculus.org" target="_blank">quake3-unsubscribe@icculus.org</a><br>
Mailing list archives: <a href="http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?50" target="_blank">http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?50</a><br><br><br></div></div></blockquote></div><br></div></div></blockquote></div>
</blockquote></div><br>