etcfg

You have never heard of Return to Castle Wolfenstein nor of its free predecessor (or rather mod) Wolfenstein: Enemy Territory? Well, you should. Being developed by id software, the inventors of the first-person shooter, in the early 2000s, they both had a great impact on other games and still have. W:ET was my first fps and is likely to be my last one. (I stopped playing in early 2009 and haven’t felt the need to try out any other game since.)

What makes it so special is the combination of a steep learning curve in terms of movement and accuracy with trickjumping and a unique game mode that keeps you playing it over a long time (which doesn’t consist of boring capture-the-flag or last-man-standing). The proof: W:ET was released in 2003 and is still one of the top online multiplayer fps, today. I suggest you try it out yourself or to read more about it at Wikipedia. The rather old-fashioned graphics (it’s based on the Quake3 Engine) should allow you to play it even on old hardware.

Now, writing good configuration scripts for W:ET is quite a challenge. Consider that the scripting language features no control structures (e.g. if/else, for, while) at all but just assignments and procedures. It still seems to be Turing complete, though, because you can achieve those missing things indirectly (which I did).

Head on to my cfg, now. :) If, in fact, you play W:ET, this is what you were desperately looking for, although you may not have known it. ;)

Side note: I’m sorry that you won’t find old revisions of the configuration in the repository. In fact, I was constantly working on the scripts over years but the idea of version controlling it crossed my mind quite recently.