Official forums for BZFlag.org

Please report bugs that you find onto the bug tracker so that they can be tracked and fixed. (Also check to make sure that the issues aren't already known.)

http://beta.bzflag.bz/builds/2.99.x/bzf ... 090122.exe

You'll need the Microsoft Visual C++ 2005 SP1 Redistributable Package if you don't already have it.

Cool another one.

Wish other people would play

What are your normal business hours at the public servers?
Let's make a time table so one can find someone to play with.

There really isn't any regular activity on the development servers. This installer is also heavily outdated, so I'm doubting it will show any servers unless someone hasn't updated yet.

So basically, if you want to get in on testing 2.99.x, you need to build your own client, and then get on IRC to collect a few others to do the same.

If I figure out how to compile it to a non-root directory (like /home/<username>/bz_3_dev/) then I would play with you tony.

@Ratfink: Just compile it and run it without installing:

cd /home/<username>/bz_3_dev/bzflag && \
PATH=`pwd`/src/bzfs:$PATH && \
./src/bzflag/bzflag -dir data

blast wrote:There really isn't any regular activity on the development servers. This installer is also heavily outdated, so I'm doubting it will show any servers unless someone hasn't updated yet.

So basically, if you want to get in on testing 2.99.x, you need to build your own client, and then get on IRC to collect a few others to do the same.

I haven't really followed 2.99.x much since about September, back when just about every version I tried resulted in invisible tanks, but I just got 2.99.19.20090403 and couldn't see any servers, is this build of 2.99.x also too old to see server list or are there just no servers up at this time?

That build is too old to see servers. Trunk changes protocol a lot, so a client as old as one day might not work. Try downloading svn and compiling for yourself if you want to test it.

I'm sure this has been asked before, but why, exactly, does the trunk protocol change so often?

Because a new feature or a fix requires a change in the way the server and client talk to each other. Or functionality that is expected to be on one or the other no longer exists or new functionality is created.