Inside 3D
 Main Page -

 

Logo by MattCake

Introduction

- HexenC is a programming language based on QuakeC developed by John Carmack expressly for use with Quake. HexenC is used for Hexen 2. The semantics of the language itself resemble a stripped down version of C. Some examples of HexenC modifications are new weapons, monsters, player skins, the possibilities are endless. HexenC is everyone Hexen2 Players dream come true...

What Do I Need To Get Started?

- The first step is to download the HexenC source codes and a compiler. The official way would be to download the Hexen2 Utilities from ftp.cdrom.com or its mirrors (The file is H2_UTILS.EXE and sized 3mb), but it contains also the level editing utilities so it would be a waste of time.

Therefore, we have put up an archive containing only the HexenC files here. It contains not only Win32 HexenC compiler, but a decompiler too! Compliments to Pob the Impaler for providing us with the file.

What Do I Need To Edit?

- When you come to the part where you should edit a .hc file, you can do this in a normat text editor. You can use DOS EDIT or WORD PAD. The only Text editor I know of that does't work, is NOTE PAD since it can only handle 64k files. (Only client.hc is actually bigger, but it is a very important HexenC file..).

Setting Up

- After you have edited a .hc file, and you have executed hcc.exe IN the src dir, you will find a file named PROGS.DAT In the /hexen2/mygame/ directory. You can then exit to the root Hexen2 dir, and run Hexen2 with the -game mygame line, which will cause Hexen2 to look for data in the mygame directory before falling back to data1. You can then play with your patch.

Your Directory Structure

- Your directory structure should then look like this.. 

   /hexen2/h2.exe
   /hexen2/data1/
   /hexen2/mygame/src/hcc.exe
   /hexen2/mygame/src/world.qc
   /hexen2/mygame/src/progs.src
   /hexen2/mygame/src/... etc ...
- You should also change progs.src to make the progs.dat file in "../progs.dat" instead of "progs.dat".

Comments

- Comments are little notes used by a programmer in order to help others to understand his code. They do not affect the program at all if written correctly. There are two ways to denote comments in HexenC. One way is with doubles slashes (//). The double slash comment only works behind the slashes and on the same line. With every new line that you want a comment on you must include double slashes.

void() pal_purifier_fire =      // Hello this is a double slash comment
Another way to write comments are with the slash-star (/*). With this type of comment, every line after the /* is a comment until ended with */.

void() pal_purifier_fire =      /* Hello this is a slash-star comment
This is still part of the comment */

Operators and IF Statements

- Operators are the little signs we usually find in IF statements. Signs like ==,>=,<, etc. here is a table of the important operators in HexenC:

"=="equal to
"!="not equal to
"="becomes
">="greater than or equal to
"<="less than or equal to
">"greater than
"<"less than

The basic structure of an IF statement is as follows: 

if (condition)
        {
        True-part;
        }
else
        {
        False-part;
        }


Variables to Know

- Here is a table of the important variables to know in HexenC and what they are:

.healththe health of an entity (must have prefix like "self")
.classnamethe classname of an entity (must have prefix like "self")
.originthe origin of an entity (must have prefix like "self")

HexenC is very similar to QuakeC. If you know QuakeC, you will have no problems with HexenC.



Inside 3D is Šopyrighted the Inside 3D team, 1997-'98. All rights reserved
Site Hosted by the one and only Telefragged The one-stop Quake page
Feedback? Suggestions? Flames? Hate mail? Send it to all of us now !
Any information found on these pages, may NOT be re-produced before mailing us.