Warzone 2100 is a 3D real-time strategy game, developed by Pumpkin Studios (Archived website) and published by Eidos-Interactive. In late 2004 Warzone was released by its copyright holders, Eidos-Interactive, to the public under the GNU General Public License and the Warzone 2100 Resurrection Project was born.
In Warzone 2100, you command the forces of "The Project" in a battle to rebuild the world after mankind has almost been destroyed by nuclear missiles. The game offers campaign, multi-player and single-player skirmish modes. An extensive tech tree with over 400 different technologies, combined with the unit design system, allows for a wide variety of possible units and tactics.
Although comparable to Earth2150 in many significant aspects, it does contain some features that are unique. These include various radar technologies, a greater focus on artillery and counter-battery technologies, more frequent in-game cinematic updates as gameplay progress, as well as a different vehicle design method.
What's New in version 2.2.1:
General:
* Change: No longer require space between rearm pads, allow dragging pad production with mouse, and droids may drive over inactive rearm pads (r7701, ticket:569)
* Fix: Various crashes related to failing orders (r7699)
* Fix: Show translations for finished research display (r7730)
* Change: Add more information to the crash dump file (r7740, 7745)
* Fix: Mac users can read in .wz files (r7754)
* Fix: Experience speed adjustment happens after max speed limit; fix bug with speed calculation. (r7761)
* Fix: Numerous issues with NTW mod (r7676-7677, r7713-7716)
* Fix: fix to *never* control the transport in SP games. (really this time!) (r7776, ticket:568)
* Change: Allow droids to grab artifacts and oil drums from up to 1 tile away (r7779)
* Change: Bump up MAX_RESEARCH to 500 from 450. (r7774, ticket:599)
* Fix: Make sure we take xOffset into account, we don't always start at 0 for the FMV text. (r7780, ticket:625)
* Change: When host drops from the lobby, abort the game. (r7787 ticket:583)
* Fix: Make sure either parameter isn't below the minimum screen res. that we support. (r7786)
* Fix: Make sure we take xOffset into account, we don't always start at 0 for the FMV text. (r7780, ticket:625)
* Fix: Clear the keyboard/mouse input on lost focus correctly. (r7797, ticket:515)
