freebsd port of quake 1 server

[Chris Edwards]

anyone know where i can find one?.. need to get this quake online multiplayer thing going.

[Paul]

yup, made a note of that too. i wanna put a list of the maps and whatever we've got running on the server when it goes up. <br><br>is it possible to make a hyperlink which loads pq and directs it to a particular server? could you just make a link like "\Quake\PocketQuake.exe -connect xxx.xxx.xxx.xxx" or something?

[Moose or Chuck]

Yes, but I think it's a plus sign, not a minus sign, to change console vars like that. But connect could be one of those that takes a minus instead.<br><br>Hey, maybe that's the problem with that one guy's obot shortcut!

[Paul]

no i think thats meant to be -game... i think

[OrBy]

there should be the source to this available on any major ftp.cdrom.com mirror as q1 has been around so long ya just gotta do a little looking.<br><br>question - is the current version of pq network compatable with gl/win quake 1.09 ? (un official version 1.13a from Keith Harrison)

[Dan East]

Yes, via TCP/IP (not IPX).<br><br>Dan East

[Dan East]

Technically, Quake only uses TCP, as it uses only UDP packets and not IP protocol.<br><br>Dan East

[Paul]

i thought tcp and udp were complete opposites - one requiring acknowledgement of the packet being recieved and the other not?

[Dan East]

After I posted that yesterday I realized I was wrong. It uses IP packets (UDP), and not the TCP portion of the protocol.<br><br>Dan East

[Paul]

am i right then? i dont want to go around saying stuff to find out its rubbish.

[Paul]

well, not where computers are concerned...

[Dan East]

You're right. IP is just raw packets, addressed to and from a particular IP address. The packets must be fairly small, and that protocol contains no mechanism to report if the packet was received, truncated or corrupted. TCP adds all that in, plus it allows a larger chunk of data to be broken up into many IP packets, which it the reassembles into the correct order on the receiving end. If two packets are sent sequentially, it is possible for the second packet to arrive first, because it may have taken a different physical route through the network, etc.<br><br>Dan East