to do list for bzflag
---------------------

* remove MsgClientVersion as it contains
   the wrong version anyway

* build a prototype(4) for bsd, solaris

* fix up irix idb

* build a tar as output that supports "rpm -tb <tar>"

* one tcp port. Tim Riker is working on this code. 1.7e4
  included playerid mangling support to get ready for this.

* break the net compatibility to allow some fixes
   including:

* player ids to one byte synced on server and clients

* ipv6 support

* version as strings as in 1.9.0-cvs20030604

* if we stay with tcp/udp then use the same ports for the
   udp pipe as for the tcp pipe on both client and server

* consider using ENet http://enet.cubik.org/ for
   the network protocol

* encapsulate stuff requiring platform #ifdef's:
   networking API into libNet.a.
   fork/exec (used in menus.cxx) into libPlatform.a
   file system stuff (dir delimiter, etc.)
   user name stuff

* consider moving to LGPL instead of GPL

* clean up libraries that could be reused by other games

* allow the worlds to be resized as a server option

* implement texture cache on client and have server offer
   new textures as part of the world.

* allow loadable meshes as "tanks"

* supply tank "meshes" from the server

* allow client to choose a mesh from the server list

* implement one way cross server teleporters

* implement a visual "server list" game server

* auto-generated dependency support in makefiles
   manual dependencies cause too much trouble

* move robots to separate binaries and allow either the
   client or server to exec them. Have a server option
   to keep n players in the game which auto spawns/kills
   enough bots to do it. Get rid of bot player type
   completely. bots should get all message types.

* smarter robots

* add type of shot (normal, gm, sw, etc) to killed message

* more flag types

* mines:
   not necessarily a good idea.  if mines are visible
   then they're fairly useless.  if invisible then they're
   not fun because you're destroyed without warning and
   no amount of skill will help you.  someone suggested
   making them visible within a certain range.  another
   possibility is damage before destruction.

* radio chat:
   allow players to communicate via low-quality audio.
   already some support built into the server for this.

* pre-game waiting room:
   provide a means for players to gather before and after
   a game.  basic text chat facilities.  allows players
   to wait for enough players for a game and to discuss
   strategy, etc.  could build this into bzfs easily.
