QuakeC

From Wikipedia, the free encyclopedia

QuakeC is a scripting language developed in 1996 by John Carmack of id Software to program parts of the computer game Quake. Using QuakeC, a programmer is able to customize Quake to great extents by adding weapons, changing game logic and physics, and programming complex scenarios. It can be used to control many aspects of the game itself, such as parts of the AI, triggers, or changes in the level.

1 Overview
2 Limitations
3 Modified compilers and syntaxes
4 External links

[edit] Overview

The QuakeC source to the original id Software Quake game logic was published in 1996 and used as the basis for modifications like capture the flag and others. QuakeC source code is compiled using a tool called qcc into a bytecode kept in a file called progs.dat. The programmers of Quake modifications could then publish their progs.dat bytecode without revealing their source code. Most Quake mods were published this way. However, since Quake has been released under the GPL license, publishers of Quake modifications that contain a binary compiled progs.dat are required under the terms and conditions of the GPL to release the sources of their QuakeC modifications as well as provide the relevant GPL license text under penalty of law.

QuakeC allowed the Quake engine to dominate the direction of the first-person shooter genre. Thanks to Carmack's idea of extending computer game life by adding unlimited expandability, an enormous Internet community of gamers and programmers alike has arisen and nearly every modern multiplayer game is completely expandable.

[edit] Limitations

The syntax of QuakeC is based on that of the C programming language, explaining its name, although it is much more limited. For example, QuakeC does not allow the implementation of new types through either structures or objects. QuakeC also suffers from the fact that many builtin functions (functions prototyped in the QuakeC code but actually defined within the game engine written in C) that return strings in a temporary string buffer, which can only hold one string at any given time. In other words, a construct such as

SomeFunction (ftos (num1), ftos (num2));

will fail because the second call to ftos (which converts a floating-point value to a string) overwrites the string returned by the first call before SomeFunction can do something with it. Other prominent examples of these quirks include the fact that QuakeC does not contain any string handling functions or file handling functions, which were simply not needed by the original game. Although other programmers certainly could have used them, APIs for things like file manipulation were purposely left out to prevent security concerns when downloading a precompiled progs.dat bytecode.

Most computer games have their game logic written in plain C(++) and compiled into the executable, which is faster. However, this makes it harder for the community to create mods and it makes the process of porting the game to another platform (such as GNU/Linux) more costly.

Despite its advantages, the concept of implementing the game logic in a separate scripting language and writing an interpreter for it was soon dropped (even by John Carmack who had implemented this concept) because of the overall inflexibility of an interpreted language, the increasingly complex game logic and the fact that releasing part of the source code would be sufficient for the mod community.

[edit] Modified compilers and syntaxes

As is their custom to do with nearly everything they make, id Software released the source of qcc, their QuakeC compiler, along with the original QuakeC code in 1996. Modified versions soon sprung up, including Jonathan Roy's fastqcc and Ryan "FrikaC" Smith's FrikQCC. These added functionality, optimizations, and compiling speed boosts.

In 1999 when id Software released the code from Quake's engine under the GPL, the workings of the bytecode interpreter were examined and new QuakeC compilers were released, such as J.P. Grossman's qccx and a new version of FrikQCC. These compilers took advantage of newly discovered features in a backwards-compatible way so that the bytecode could still be properly interpreted by unmodified Quake engines. New features include arrays, pointers, integers, for loops and string manipulation.

With the Quake engine source code now able to be changed, further features were added to QuakeC in the form of new builtin functions. Features long yearned for by QuakeC coders finally reached realization as QuakeC now had file and string handling functions, enlarged string buffers, more math functions, and so on. However, programmers taking advantage of these changes lost backwards compatibility with the unmodified Quake engine.

See also: Computer programming