This wiki is archived and useful information is being migrated to the main bzflag.org website

Difference between revisions of "Development RoadMap"

From BZFlagWiki
Jump to: navigation, search
(3.2)
Line 12: Line 12:
 
The development goals are listed here [[BZFlag 2.3]]
 
The development goals are listed here [[BZFlag 2.3]]
  
===2.4.2 (What was once lost)===
+
===2.4.2===
 
2.4.2 will be the first maintenance release of the 2.4.x compatibility line. Its primary function is to fix bugs found in the 2.4.0 release and to include non breaking items that were not ready during the initial release including:
 
2.4.2 will be the first maintenance release of the 2.4.x compatibility line. Its primary function is to fix bugs found in the 2.4.0 release and to include non breaking items that were not ready during the initial release including:
  
Line 20: Line 20:
 
* Joystick fixes
 
* Joystick fixes
  
===2.4.4 (Making the stride)===
+
===2.4.4===
 
* New Death effects
 
* New Death effects
 
* HTTP Management plugins
 
* HTTP Management plugins

Revision as of 02:45, 8 June 2011

Overview

This document discusses the general development road-map for Future BZFlag Releases.

Features

Individual features may move up or down the roadmap depending on how/when they get done. Entire releases may be pushed up the roadmap or merged depending on how development goes.

2.4

Goals: Get a release out

2.4 will be the next release of BZFlag and is protocol incompatible with all previous versions.

2.4.0 (Wake the dead)

The development goals are listed here BZFlag 2.3

2.4.2

2.4.2 will be the first maintenance release of the 2.4.x compatibility line. Its primary function is to fix bugs found in the 2.4.0 release and to include non breaking items that were not ready during the initial release including:

  • BZFScron
  • Fastmap
  • Push Stats
  • Joystick fixes

2.4.4

  • New Death effects
  • HTTP Management plugins
  • Bug fixes
  • New Font System
  • New Server List
  • New Translations
  • Download Authorization Dialog
  • GM lock-on markers on the radar.

2.4.x (Maintenance)

Continuing releases to fix critical bugs. New features should go into 2.6 at this point.

2.6 (Next Breaking Release)

Goals: Continue Development

This version may be rolled into the 3.0 release if that code base is still usable. If the code is extended from 2.4 it may have these features;

  • Lua (Client side)
  • Acceleration changes
  • Flag Drop "Zone" feature
  • XFire
  • OpenAL/Support, OGG, Hardware mixing and 3d (replace bzaudio?)

3.0 (Next Major)

Goals: Get back to where V3 wanted to be.

Using the 2.99 continuing branch, or the 2.6 branch with a lot of back-ports depending on code-base stability.

  • Have BZFS convert all world objects into mesh representations for consistent client collisions.
  • Point in Polyhedron tests to remove inside/outside points.
  • New Simulation
  • Shot Type/Flag Type split
  • Things added in V3 that were not back-ported.

3.0.2

Goals: End user experience

Compatible release ( if possible ) that makes the game easier for new users to play and for servers to manage players.

  • UI Cleanup
  • New Group and User Management.
  • In game registration
  • Tutorials

3.2

Goals: Modernization

Goals for this release are to bring the game's networking and simulation system up to par with modern games.

  • Lag compensation
  • Threaded Networking
  • Threaded Simulation
  • UI customization
  • General Resource Updates and Downloads (sounds, scripts etc..)?
  • External model loading ( for tanks )

3.4

Goals: Server State

  • Server Side Radar
  • Server Side Shots
  • Server Side Deaths
  • Server Side Bot API
  • Removal of Client Side Logic

4.0

Goals: Graphics Upgrades

  • Third party graphics engine? Ogre? CS?
  • Patching?
  • Shader Support?
  • OpenGL 2+?
  • Tank skins

5.0

Goals: Extensibility

  • Server defined game logic and settings
  • Game mode plug-ins/scripts on the server
  • Server defined graphics elements ( shots, models, etc)
  • List server separation by game mode
  • Require Registration and limit server choices until verified?