[{DvT}JonahHex]

I use Borland C++ Builder 6 for the DvT Tools. If I weren't too lazy to rewrite the code, I'd switch it over to Borland Delphi, but I am, so I haven't.

The UnrealAdmin info on the Unreal server protocols is exactly the reference source I've used since I first wrote the ServerQuery program. The wiki link clearly shows the limitations of the new Gamespy protocol: a couple of bugs are listed and the absence of player info is glaring.

Converting the 2K4 version over to the UT3 version is pretty simple. As I indicated, I've already got the query code converted, now I just need to decide how I want to have the program format and display it. I don't plan to change the UI - it will still display in 2 window panes...server info on the left and (now) a nasty note on the right pointing out the failings of Gamespy to provide player info.

Part of what I'm doing now is trying to decide whether to assume that the servers will always return the info in the order listed on the wiki page (which they seem to do now) or whether to do it the safe way and make no assumptions and cycle thru the returned code to compare the returned params with the expected params before displaying the returned values. The latter is the best way but it makes the code longer - so the question is how lazy will I be? . I've already got the params and the values in separate arrays, p[i] and v[i] so the info is all available to use. Like I said, the hard part is making up my mind on how to use (display) it.

I've always said the hardest part of programming is the UI: what do I want to display? where do I want to put it? what color should it be? should the button be labeled "next" or "continue"? etc etc etc ...All those personal preference, aesthetics, usability questions.