Primary external links

ioquake3 is divided into two general parts, the client part and the server part, with a networking system that connects the two. The client mainly takes care of user interface. That is, it displays the 3D rendering of the game world and also collects keyboard, mouse, and joystick input events. The server is responsible for taking care of everything else: moving the user's position and view based on keyboard/mouse/joystick inputs, detecting collisions, processing bot AI, determining hits and frags, etc.

Program Flow

During startup of a standard game, the top-level flow of control goes like this:

Depending on whether you're using a unix environment or Windows, program control will start at either main() or WinMain().

Subversion Windows Builds

These are weekly subversion builds of ioquake3 for Windows. Thanks to Ludwig Nussel and SUSE for providing the build service for the Linux and Windows versions! Thanks to Ryan “icculus” Gordon for providing the build service for OS X!