From Quake Wiki
The game engine (a.k.a. Quake engine or just engine) is the 'executable' program you run to actually play Quake. It loads the game's maps/models/skins/etc., figures out what to draw on the screen, responds to your keyboard/mouse input, sends sounds to your sound device, and communicates over the network. The game engine normally resides in the root Quake folder and expects to have access to the ID1 subfolder which contains, at the very least, the files needed to play Episode 1 (normally pak0.pak).
Quake engines operate on a client-server model. Depending on the engine, the client and server can be in the same file, or can be separate.
If they're in the same file, then when you run the engine, the server always runs. The client normally runs, too, unless you did something special to launch the engine in a server-only mode (e.g., for other people to connect to for playing over a network). So when you play a single-player game of Quake, the client portion of your engine communicates with the server portion. When you play a multiplayer game over a network, the client portion of your engine instead communicates with a remote server, which naturally will be subject to speed limits and delays inherent in the network.
If they're separate programs, then you only run the client, and you tell it where a server is running that you want to connect to. A server browser can help you locate servers where you can join a game and play with other people.
Networking and graphics
Engines generally fall into two categories:
- "NetQuake" engines: engines with networking code compatible with that of the original Quake engine.
- "QuakeWorld" engines: engines with networking code compatible with that of the original QuakeWorld engine.
Additionally, all engines use one of two graphics rendering technologies:
- Software rendering: rendering is done entirely in software, without the help of graphics hardware, as in the original Quake and QuakeWorld engines.
- OpenGL rendering: rendering is done with the help of graphics hardware, as in the original GLQuake and GLQuakeWorld engines.
QuakeWorld-style networking code and OpenGL-style rendering are standard nowadays in pretty much every first-person shooter, but at the time Quake was released in 1996, both were new technologies.
You will probably want to use an engine with OpenGL support, if your hardware is compatible (pretty much any computer built after 1997 will be). And you will probably want to use a QuakeWorld engine for playing over the Internet. However, for single-player games, especially when you're just getting started, a NetQuake engine may be ideal, for the simple reason that QuakeWorld engines often don't support single-player games.
Wikipedia has a Quake engine article containing more technical info about Quake engines, and nice diagrams showing all the engines and how they're related.
Instead of messing with these engines, most new Quake users, unless running on very old hardware (pre-1997), should probably start with one of the unofficial engines.
These three are NetQuake engines:
- QUAKE.EXE aka DOS Quake — for DOS or Win95/98/Me only; software rendering
- WinQuake — Win32 (Win95 through 7) version of QUAKE.EXE; software rendering
- GLQuake — Win32 (Win95 through 7) and Linux 2.0 version of QUAKE.EXE; OpenGL rendering
And then there's the original QuakeWorld engine:
- QuakeWorld — Win32 (Win95 through Vista), Linux 2.0, BSDI 3.0, Solaris 2.5.1; software or OpenGL rendering (clients for both are distributed together)
Mac OS engines
- Quake for Mac is the official port of GLQuake 0.97 / Quake 1.09 for the classic Mac OS (not OS X). It was released on CD-ROM in 1997 by MacSoft, now owned by Atari. For multiplayer play, it supports TCP/IP or IPX via AppleTalk or Ethernet. It is commercial software, not free.
- Quake 1.1 is an unofficial port of both the OpenGL and original software renderer versions of both Quake and QuakeWorld for Mac OS X. It is available for free from the developers, Fruitz of Dojo.
Quake ports exist for various Unix-like operating systems, such as those based on the GNU/Linux kernel. If you need one of these, check with your particular OS's software package or port archives; chances are, someone has already made it easy for you to install and at least run a port of the basic Quake engine, if not an OpenGL one.
There were a few official, unsupported distributions released around the same time as GLQuake in late 1997:
- Quake & QuakeWorld 1.09 for Solaris 2.5.2 is in quake1.09-sparc-sun-solaris2.5.1.tar.Z.
- SVGALib Quake for Linux is in quake.x11-1.0-i386-unknown-linux2.0.tar.gz. It runs in an X11 window and requires libc 5.2.18, X11R5, and kernel 2.0.24 or later.
- GLQuake 0.97 for Linux 2.0 is in glquake-0.97-i386-unknown-linux2.0.tar.gz.
You probably don't want any of these old distributions; your OS's current package or port archive is the place to look for an unofficial engine that will work with a modern system.
Other engine mods are made by customizing the original id Quake source code. Nearly all of them are based on GLQuake. There quite a few and each one has there different features, fixes, additions, and changes to the original source. Some require very little to do on your part to make them work with Quake. Some of them may not work with your hardware, even if your hardware is very new.
TODO: This section will help people step by step to get, install, and run these Quake engine replacements.
Unofficial engine list
- Enhanced Winquake/glQuake/NehQuake (BJP)
- DirectQ - Direct3D port
- ezQuake - a QuakeWorld engine with limited single-player support.
- Fitzquake - probably the most widely compatible OpenGL NetQuake engine for Windows; SDL port available for Linux & Mac OS X.
- Vengeance r2