Quake II Server Browser (beta 3)

[R1CH]

http://r-1.ch/qsb-beta3.zip

[Pogo´]

YAY FLAGS!
The only things i'm missing now is the ability to copy ips with ctrl-c and an option to not shut down the program after connecting to a server. With those 2 things it would be the ultimate server browser imo, no bloat and good overview. A buddy list would also be cool, but it's more of an extra if you ever feel like it

Thanks alot for this, it really fills the shoes of the all-seeing eye!

[Pogo\\\']

Uh i somehow managed to miss that it already has a buddy list =)
Nevermind me, carry on  

[wision]

- show scores of all the players
- F5 / ctrl+r as "update"

[Gen]

nice thanks

[R1CH]

- show scores of all the players

Right click the playerlist?

[Newbie]

Could you add a dday filter?

[Muerte]

unfortunate qsb show WallFly[BZZZ] as servers with players instead empty
bigger font for playerlist?

looks promising

[mhanor]

Right click the playerlist?

it's not an obvious feature... it should display a tip or you could add a check box or a button

[SquiSHeR]

Hello R1CH.

Could you please make the source code available so others have the ability to port it to other systems like linux or Mac OS? Or do you have any code examples on how to query Q2 servers and extract game data from their reply?

[QwazyWabbit]

Servers are pinged and queried via UDP frames containing strings.
A ping frame consist of the word "ping" preceded by the Out-Of-Band flag, the 32-bit hex value of -1 as a string
"FFFFFFFF"

#define OOB_SEQ "\xff\xff\xff\xff" //32 bit integer (-1) as string sequence signifying out of band data

      sendto (socket, OOB_SEQ"ping", 8, 0, (struct sockaddr *)&addr, sizeof(addr));

The server responds with an "ack" frame:

      sendto (listener, OOB_SEQ"ack", 7, 0, (struct sockaddr *)&addr, sizeof(addr));

The time delay between the transmitted ping and the received ack is used to estimate the ping to the server.

The same framing principle applies to getting an out-of-band status frame:

      sendto (socket, OOB_SEQ"status", 10, 0, (struct sockaddr *)&addr, sizeof(addr));

The server responds with a server info frame consisting of the elements:
OOB_SEQ"print\n"
followed by a series of hashes, (paired variable/value strings delimited by backslashes:
\variable1\value1\variable2\value2\variable3\value3 ... etc. finally ending with "\n"
followed by player information strings (if any) consisting of:
score<space>ping<space>"playername" each player info string ends with "\n" (note: quotes are required around the player name)

You can find the creation of the server info frame in R1ch's r1q2 source in the SVC_Status and SV_StatusString functions.
You can get the socket structures and other information you need from r1q2 source also.

[resor]

WTF?

[R1CH]

Install this:
http://www.microsoft.com/downloads/details.aspx?familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en

[resor]

Thanks. Working

[Nicholas]

what is the master server  r u gathering servers information?