This wiki is archived and useful information is being migrated to the main bzflag.org website
Difference between revisions of "BZFlag 2.99"
m (BZFlag 2.2 moved to BZFlag 3.0: Changes to the versioning system) |
|||
| Line 1: | Line 1: | ||
| − | BZFlag version | + | BZFlag version 3.0 is the next planned release of BZFlag. |
==Overview== | ==Overview== | ||
| − | Version | + | Version 3.0 is currently in development and marked as version v2.99.x. Upon release it will be marked as version v3.0. The primary goals for this version are improved server side stability and security in an effort to minimize the impact of clients that have been modified to provide their users benefit ( aka, cheating ). Additional efforts are being made to extend the server side customization of the game. v3.0 will be completely incompatible with all previous versions of the game. Users of v3.0 will only be able to play on 3.0 servers. This is similar to how v2.0 was incompatible with 1.10. |
==Development== | ==Development== | ||
| − | Development began on | + | Development began on 3.0 on October 25th 2005. After an initial rush of changes, development stalled, as a number of bugs were found in the current release build of the time ([[BZFlag 2.0.4|v2.0.4]]). These bugs and problems, as well as a number of graphical changes from [[trepan]] necessitated the release of a compatible [[BZFlag 2.0.6|v2.0.6]] and [[BZFlag 2.0.8|v2.0.8]] releases. |
Development has picked up some, but is still slow. | Development has picked up some, but is still slow. | ||
| + | |||
| + | ==Version Number Change== | ||
| + | v3.0 is the first version to use the new version numbering system. With previous releases the minor version number in the 3 part version (major.minor.revision) represented the protocol computability version. With 3.0 it is moved to the major version. This new scheme gives more "room" to deal with minor packaging revisions and patches. | ||
==Features== | ==Features== | ||
| Line 26: | Line 29: | ||
The new Experimental mode includes new shot and flag graphics. Examples of the new shots (internally called, GeoBolt and GeoLaser) can be seen here. | The new Experimental mode includes new shot and flag graphics. Examples of the new shots (internally called, GeoBolt and GeoLaser) can be seen here. | ||
<gallery> | <gallery> | ||
| − | Image:Geo_bolt_example1.jpg|A shot in experimental in 2. | + | Image:Geo_bolt_example1.jpg|A shot in experimental in 2.99 |
| − | Image:Geo_bolt_example2.jpg|Another shot in experimental in 2. | + | Image:Geo_bolt_example2.jpg|Another shot in experimental in 2.99 |
| − | Image:Geo_laser_example1.jpg|The thief beam in 2. | + | Image:Geo_laser_example1.jpg|The thief beam in 2.99 |
</gallery> | </gallery> | ||
It should be noted that the new shot graphics are not for people with older or slower video cards. | It should be noted that the new shot graphics are not for people with older or slower video cards. | ||
| Line 34: | Line 37: | ||
A full list of changes can be found in the [http://bzflag.svn.sourceforge.net/viewvc/*checkout*/bzflag/trunk/bzflag/NEWS NEWS] file in the [[BZFlag Source]] code in [[BZFlag SVN|SVN]]. | A full list of changes can be found in the [http://bzflag.svn.sourceforge.net/viewvc/*checkout*/bzflag/trunk/bzflag/NEWS NEWS] file in the [[BZFlag Source]] code in [[BZFlag SVN|SVN]]. | ||
| − | |||
| − | |||
==Known Issues== | ==Known Issues== | ||
Revision as of 07:00, 21 November 2007
BZFlag version 3.0 is the next planned release of BZFlag.
Contents
Overview
Version 3.0 is currently in development and marked as version v2.99.x. Upon release it will be marked as version v3.0. The primary goals for this version are improved server side stability and security in an effort to minimize the impact of clients that have been modified to provide their users benefit ( aka, cheating ). Additional efforts are being made to extend the server side customization of the game. v3.0 will be completely incompatible with all previous versions of the game. Users of v3.0 will only be able to play on 3.0 servers. This is similar to how v2.0 was incompatible with 1.10.
Development
Development began on 3.0 on October 25th 2005. After an initial rush of changes, development stalled, as a number of bugs were found in the current release build of the time (v2.0.4). These bugs and problems, as well as a number of graphical changes from trepan necessitated the release of a compatible v2.0.6 and v2.0.8 releases.
Development has picked up some, but is still slow.
Version Number Change
v3.0 is the first version to use the new version numbering system. With previous releases the minor version number in the 3 part version (major.minor.revision) represented the protocol computability version. With 3.0 it is moved to the major version. This new scheme gives more "room" to deal with minor packaging revisions and patches.
Features
v2.1 has a number of server side features that make for a much improved gameplay experience. Features such as
- Flag pickups
- Identify
- Pausing
- Water Death
- Shot type
- Bots
have all been moved to the server, preventing a modified client from changing the outcome of the game logic. Additional features are planed to be moved server side, including shot, hit, and death detection.
A number of small checks and fixes have been put in to verify the game state as well.
Changes have been made to the graphical quality settings. What was Experimental quality in 2.0.8 is now High quality. Medium quality is between the old High and Medium, and Low has remained mostly unchanged.
The new Experimental mode includes new shot and flag graphics. Examples of the new shots (internally called, GeoBolt and GeoLaser) can be seen here.
A shot in experimental in 2.99
Another shot in experimental in 2.99
The thief beam in 2.99
It should be noted that the new shot graphics are not for people with older or slower video cards.
A full list of changes can be found in the NEWS file in the BZFlag Source code in SVN.
Known Issues
A lot of stuff needs testing, and probably doesn't work.
Release Date
2.2 will be released when it is done. At present a number of major features need to be implemented before the release has enough "stuff" to warrant a new release.
