Warzone 2100 Forums

The Mac port is fairly easy to build, in general.  I use DarwinPorts to install the necessary libraries beyond what Tiger gives you.  There is a README.BUILD.txt in the macosx directory of the subversion sources that you can look at for more information. What needs to be done with the Mac port is th...

Networking is one of the items on the Mac that hasn't been worked on yet.  There are endianness issues up the wazoo and probably other things that cause network games to crash when Macs are involved.  Also, if you look at existing bug reports, Intel Macs are not supported at this time.  I am the onl...

This is not a build problem.  I don't have an Intel Mac, so I have no way of creating a universal binary, given the number of libraries and frameworks that Warzone 2100 depends on.  There have been crashes reported on Intel Macs running the game under Rosetta.  I have no way of debugging this situat...

You can change the resolution either with command-line options or in the configuration file, the location of which depends on which OS you run the game on.  As to playing with people and robots, there are essentially two multiplayer modes: Internet play and Skirmish play.  Skirmish play works by loa...

Pumpkin was a British studio.  I have noticed at least two spellings of "armor" in the game.  One is "armor" in American style, and the other is "amour" [sic] in misspelled style.  I remember the second one from the original game, and I have always wondered if "the...

I just played the game for a while and failed a mission (again!...I forgot what a challenge Warzone is), and here is the grand sum of the console output: error:      eventFireCallbackTrigger: script interpreter is already running error:      Assert in Warzone: event.c:977 : eventFireCallbackTrigger ...

I should add that the file/line reporting code requires the use of the function GetLastResourceFilename() from lib/script/ code.  I don't know if this is considered a major no-no or not.

I have spotted two so far, at least that come up on my system: 1. configure.ac called for AC_CONFIG_HEADER but automake requires the use of AM_CONFIG_HEADER instead 2. The same script bug I pointed out a while back.  Easily fixed by a check for whether psFunc->type >= VAL_USERTYPESTART before gettin...