http://talks.golang.org/2013/bestpractices.slide#25

Removed unused global

The bug here was that when you would try to start a game it would still be nil
after the block where g was redefined. Just me being sloppy.

Added some debugging

Create new bserv binary

Herein lie the following ideas:

- change package visibility of many things
- try to stash the globals into structs
- the code is far from correct; it merely compiles

This finalizes the work on getting the server to support multiple encodings for
players and spectators.

Typically client offers supported encodings, then the server chooses the
optimal one.

This is the first step involved in letting go clients talk gob to the game
server.

Still missing: actually use the client's prefered encoding

I just realized that there is no need to pass around a slice to something to
which protoTalker already has access.

I could never remember the url, so I print it out now.

unfortunately there is an issue with how these are calculated, and they don't
decrease as things quiet down. Well, the bad numbers are their for your
consumption, and should Just Work TM when appropriate changes in
bitbucket.org/smcquay/bandwith land. And they will. But I'm tired now.

As it turns out there are other citizens of this world, not just the botclient.
So I have properly labeled the payload with a type. This makes the web
front-end less breaky.

This was a problem before when the probe hit an object that was further than
another object first. Now we traverse all objects all the time to find the
closest one. \o/