Planet Nebula: The Personal Website of Jeff Weiner


Portfolio: Jazz Jackrabbit 2 List Server

Back in 1998, Epic MegaGames (now Epic Games, creators of the Unreal/Gears of War franchises) released a video game named Jazz Jackrabbit 2.  A sequel to one of the most popular shareware games in 1994, Jazz Jackrabbit, it did a great job at expanding the series.  One of the notable features of the sequel was bringing it to the Windows environment; the original was designed for MS-DOS.  Another notable feature was the introduction of multiplayer over local area networks, and the internet.

While local area networks allow video games to contact other machines in the immediate vicinity by broadcasting packets to the local network subnet, this obviously isn't feasible for the internet.  As such, a "list server" daemon was also created by the game developers to run on a pre-determined server that would help coordinate playing games online.  The game would contact this server to obtain a list of all the currently active games, and it would also contact the list server to notify it that the user was hosting a game themselves.

There was a problem with the original build of the list server created by the developers, however.  It had an issue where malicious users could cause a Denial of Service attack by connecting to the server as if it was going to inform it that it was going to host a server, but then not send any data.  The server would stop accepting connections of any kind while it waited for data from the malicious user (a normal instance of the game would send this data immediately), but the server was not prepared to handle a situation like this, either due to a threading issue (or lack of threading), or some other   The original developers couldn't be reached by the time this problem was discovered and had begun to be abused, so the community had to take matters into their own hands.

I was fairly involved with the community around the time this decision was made (centered around a website Jazz 2 Online), and took it upon myself to redesign the list server to fix these issues, using Java.  The most pressing issue to fix was that the server needed to properly handle situations where these malicious clients would connect and not send any data when the server was expecting it.  Every time a socket was opened, it was given its own thread of execution, so even if an individual thread stalled, it didn't affect the rest of the server, which continued on it's own as if nothing was wrong.  After the initial framework for the server was set up, it was put into production by the heads of the community, and all the problems vanished.  It was very gratifying to see my code being so well received.

In replicating the list server, there were (more or less) five different ways of communication I had to implement in the server to have it behave as if it was the original server.  These were:

After the original functionality had been more or less recreated, we (the group managing the list servers) decided to get creative.  I had been designing the server to be fairly modular, so that new functionality could be added without any real changes needing to be added to the core of the list server.  The neatest feature we added was a remote administration interface.  Upon authenticating, the admin was presented with a list of options; servers could be delisted if needed, and malicious users could be added to a ban list, among other smaller features.  This helped with various other issues with malicious users; just like we had figured out how the games communicated with the server and vice versa, so had other people, who wrote programs to send false information about hosted games to the list servers.  The admin interface allowed us to fix these issues without affecting the rest of the hosted games; with the original list server, it was necessary to restart the server, which also had the unfortunate effect of delisting any current games.

Overall, redesigning the list server was a great experience, and I learned a lot, and had the chance to make something that was actually useful to people.  Since it's a server daemon, and not exactly a program for end-users, it didn't have much of an interface (indeed, the interface it does have isn't fully-functional as is), since we realized a graphical interface wasn't really needed, since it was run on a computer, and then left alone for extended periods of time.  We invested our effort in designing a management layer over a telnet session instead of through the GUI (as mentioned earlier).  I have included a screenshot of it below, but I'm sorry for not posting more...there's just not much to post.


Main Window