I have made a Windows installer of the latest development code, and a couple other people made various versions of an OSX build. During that time, there might be some temporary outages.īZFlag 3.0.0 is in the “alpha” stage right now. So, I’ll be working on the migration over the weekend here. It’s not that we’ve outgrown the server, but there is just a couple resource hungry processes (cough irssicough) on the old server that chew up lots of RAM (hundreds of MB) and make everything else very slow. The existing server has been less than ideal for a long time and has hit various resource limitations. We’re also going to work on migrating all of the web services (forum, list, wiki, main site, etc) to a different server that will be a bit more … responsive. Here’s a wiki page that we’re working on that covers the plan: It won’t be BZFlag 3.0, but it will be a new version that has features worth upgrading for. Less new features = less chance of breaking stuff. This will mean there is less time for feature creep to take over again, which in turn will reduce how much testing we have to do. The idea is to push for getting a release out in a month or so. Then we’ll start to bring back specific low-risk features from 2.99.x and put them into 2.3.x, which we’ll release as 2.4.0.0 (or whatever we decide on). Now the plan is to move trunk (2.99.x/3.x.x) out of the way, copy v2_0branch (2.0.x) into trunk, and then relabel the new trunk as 2.3.0.0. Feature creep from the last five or six years caused us to end up with something we couldn’t easily fix. We got lost in all of the bugs and features and couldn’t get a release out. Essentially it’s been decided that version 3.0 was too big of a jump with far too many big changes. Some serious thought is being put into getting a new release of BZFlag out. BZFlag 2.4.0 Universal Binary for Mac OS X.BZFlag 2.4.0 for 64-bit Windows (Only works on 64-bit Windows).BZFlag 2.4.0 for 32-bit Windows (Also works on 64-bit Windows).Polls only count users that are able to voteĬheck out the ChangeLog for more changes.The ID flag identification was moved to the server.The screenshot code does not lag the client badly anymore.Ability for the server to force flags to be hidden on the radar.Per-object ricochet, which lets map authors selectively enable ricochet for individual objects.The OpenFFA game mode which is a teamless FFA, meaning you can shoot anyone regardless of color. The ability to turn off teamkilling on the server.We have documented the upgrade procedures here: They will also have to update any of their third-party plugins to the new BZFS API format. Server owners will have to make some minor changes to their configuration files for BZFlag 2.4. Linux users will have to do a bit more work for that, but it’s still possible. Windows and OSX users will be able to easily keep both versions of the game installed and in use. There will be a transition period of several months. Servers will slowly upgrade to the new version, and some may run both versions of their maps for a while. You cannot use a BZFlag 2.4 client on a 2.0 server, nor can you use a 2.0 client on a 2.4 server. The big thing to note is that BZFlag 2.4.x is not compatible with BZFlag 2.0.x. We also, of course, put in some other fixes and features. So what we did was bring back selective features from the 3.0 development tree that were low risk so that we could get a successful release out. After BZFlag 3.0 development hit a brick wall, Bullet Catcher helped get the project motivated again by producing a plan to get a new release out that was based on 2.0.x. BZFlag 2.4.0 “Wake the Dead” has been released.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |