ABOUT MEKWARS VERSIONING:
------------------------
MekWars uses a compatibility versioning scheme in place of
more traditional "milestone/maintainance" versioning. Small
version number changes may include complex features, while
large versions may be nothing more than typo corrections.

Versions are declared using 4 numbers, as follows --
A.B.C.D

Examples: 0.0.1.4, 1.0.54.6, 0.1.0.9

(A) will remain 0 for the indefinite future. It will be
incremented when the software is deemed feature complete.

(B) is a STREAM NUMBER. It will me incremented when
all open TODO's for a B-Stream have been completed, tested
and declared stable.

(C) is the COMPATIBILITY NUMBER. Clients and Servers MUST
MATCH through the Compatibility Number. 0.1.1.x Clients will
not function on an 0.1.0.x Server. This number is incremented
whenever a change breaks Client/Server compatibility, no
matter how minor the change. Both your MekWars server and the
clients you distribute MUST be updated if you are upgrading to
a version with a new Compatibility Number, even if the number
has been decremented or zero'ed.

(D) is the PACKAGE NUMBER. Clients and Servers with different
Package Numbers will be compatible. This number is incremented
when changes are made which do not break interoperability, no
matter how major. A complete overhaul of Server calculations
which  requires no Client changes would result in a Package
Number increase, as would small bug fixes to the Client GUI
which do not touch server files.

All lower numbers will be re-zeroed when larger numbers are
incremented. For example, if it is determined that 0.0.23.56
is stable and completes Stream TODO's 0.1.0.0 would be declared.