Quake Servers Info 

 
[Blues News] Version 1.1.1 Final Released! 

Information 
Screen Shots 
Current Features 
Future Features 
Download

[Slipgate Central]
 


MRJ 2.0 and the Future of QSI

Well, I found the bug in MRJ 2.0, sent a bug report to the MRJ team, and made a workaround for QSIónot bad for an afternoon's work, eh? There's still an annoying bug left in MRJ that I can't get around, but it only affects memory usage and you shouldn't see its affects. You'll need to download the new 1.1.1 version to use MRJ 2.0. However, if you go through the trouble, you'll notice that MRJ 2.0 makes QSI look fairly nice now with more traditional platinum-scheme controls. Also, a fairly serious thread bug was fixed in MRJ 2.0 that substantially speeds up QSI server queries!

Next, I'll be updating QSI to Java 1.1. Since Java is apparently a front-line language in Rhapsody, I will also attempt to move QSI to Rhapsody. With luck, I may again be able to release a version before the Quake (2!) port so that we can pound the servers as soon as we get the game! Stay tuned!


Information

QSI is a Java application that manages lists of Quake Internet servers. QSI features many of the traditional server-query-tool features such as a sortable multi-column list, queries for current player information and server rules, list filtering, ping-time coloring, and the ability to save local lists of favorite servers. QSI can launch Quake and connect to the selected server. On the Mac, QSI can tell an active Quake process to connect to a new server.

I wrote QSI because, at the time, there appeared to be no movements to port any of the popular query tools to the Mac. There are a few alternatives developing now, but I hope you will find QSI to be the most mature of these tools right now.

Why Java? Well, first of all, I wanted to try my hand at Java programming. More importantly, it's free :), portable, and has networking built in. This allowed me to rip the initial versions out in about a week that convinced me this project was worth pursuing. Keep in mind that this is a Java application, not an applet and does not run in a browser. Java security in 1.0.2 does not allow applets to access network resources other than those from the serving host.

I go by the Quake name Charon*RS* of the Rocket Scientists Clan and can be found most often at QClan.CAE.wisc.edu or breese.doit.wisc.edu, which have been running excellent CTF 3.5 games for the last few months. The grappling hook is the "impulse 97/98" one that I find much nicer to use than the traditional CTF version. 


Screen Shots

[QSI Mac Screenshot]
Mac (Click shot for a larger version)
 
[QSI SGI Screenshot]
SGI
[QSI Win32 Screenshot]
Windows 95/NT

Current Features


Future Features


Download

Disclaimer

QSI has been tested by me on a PowerComputing PowerBase 180 (MacOS 7.5.5, 8.0, & 8.1), a 9500/200 (with 7.5.5), a 7100/80 (with 7.5.3), and a SGI O2 running IRIX 6.3. Java Virtual Machines (JVMs) are not the most stable creatures yet. I cannot account for all platforms and JVM combinations. Please try a different JVM if you are having troubles before contacting me. See the JVM/QSI comments page for the latest information.

Files

Requirements

QSI is a Java application, not an applet. It does not run in a web browser! To use QSI, you need a Java Virtual Machine (JVM) capable of running applications . For Mac users, I recommend MRJ 2.0, which will allow to to use the double-clickable application, but you can try any JVM that can handle non-compressed zip archives. For SGI users, you'll need the latest JVM released by SGI. See my page on which JVMs work with QSI. Java "portability" is relative still, I guess. :) I'd like to hear of any other experiences with other JVMs.

Special Mac Instructions

QSI runs in a 512k memory partition, however, this is a bit misleading. MRJ uses System memory for almost all Java operations, so this is where you'll see the bite. In MacOS 8, this memory is grouped with QSI so you can see how much it's really taking. Typical usage is 2-4 MB in my experience. I know this takes a bunch away for Quaking, but it's the best I can do right now with Java. Giving QSI more memory does nothing, so don't bother. It might be possible to have QSI quit before Quake is launched, freeing up some memory. If folks are interested in this option, drop me a line.

Since MRJ does not yet include AppleScript support, an AppleScript helper application called QSI Launcher is needed to launch and talk to Quake. As a result, make sure AppleScript is installed on your machine, even if you have a minimum extensions set for Quaking. QSI writes out an intermediate file called Quake Command that gets passed to the launcher. The first time you connect to a server, you will be asked to locate the Quake executable on your drive. If you mess this up and select, say, Asteroids, you'll have to either edit the script or load a fresh version of the launcher from the Stuffit archive and try again. If you have the demo and upgrade to the full version or if you switch from the software to hardware accelerated version, you'll also need to redo the script, hide (in an archive) or delete the demo, or get a fresh copy of the launcher script.

As compensation for this run-around, Mac users can connect to a new server with QSI without quitting Quake! Simply switch back to the QSI process and select another server and hit 'Connect'. Keep in mind that the resolution switching that Quake does will also be present when you want to do this. Thus, you might want to start QSI up at the resolution that Quake uses to avoid having half the window off the screen.

Special Unix Instructions

Let me know what works and doesn't since I don't have access to many other Unix platforms.

Special Windows 95/NT Instructions

If you want want the newest version of QSI: or, See the JVM/QSI page for more details about Windows.

Matt Haffner <haffner@uwast.astro.wisc.edu>

Last modified: Monday, October 20, 1997