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

Editing DevelopmentPlans/2.6.0

Jump to: navigation, search

Warning: The database has been locked for maintenance, so you will not be able to save your edits right now. You may wish to copy and paste your text into a text file and save it for later.

The administrator who locked it offered this explanation: Archived wiki

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
 
==Overview==
 
==Overview==
  
2.6.0 will be a new breaking release that is not compatible with the 2.4.x line. A strong focus of this release should be improving the user experience and improving the flexibility of the user interface.
+
2.6.0 will be a new major release that is not compatible with the 2.4.x line. A strong focus of this release should be improving the user experience and improving the flexibility of the user interface.
  
 
==Goals==
 
==Goals==
 
This list covers the major goals of this release, and the features related to each goal.
 
  
 
* Tutorial Mode (1.1.1, 1.1.2, 4.1, 4.2, 4.3, 5.1, 5.2, 5.3, 6.1, 6.2, 6.3, 7.1, 7.2)
 
* Tutorial Mode (1.1.1, 1.1.2, 4.1, 4.2, 4.3, 5.1, 5.2, 5.3, 6.1, 6.2, 6.3, 7.1, 7.2)
Line 16: Line 14:
  
 
# Add new UI elements
 
# Add new UI elements
## [[DevelopmentPlans/Dialogs|Dialogs]]
+
## Dialogs
 
### Modal dialogs are featured front and center, and require being dismissed by the user. They support hotkeys, server-specified buttons, or freeform menu items. Keyboard, mouse (including clicking items), and joystick interaction is supported.
 
### Modal dialogs are featured front and center, and require being dismissed by the user. They support hotkeys, server-specified buttons, or freeform menu items. Keyboard, mouse (including clicking items), and joystick interaction is supported.
 
### Unobtrusive dialogs show up as smaller semi-transparent boxes towards the edge of the screen and support only hotkeys (keyboard, mouse button, joystick button) for interaction.  
 
### Unobtrusive dialogs show up as smaller semi-transparent boxes towards the edge of the screen and support only hotkeys (keyboard, mouse button, joystick button) for interaction.  
Line 33: Line 31:
 
## BZDB controlled attributes
 
## BZDB controlled attributes
 
## Mesh bases/teleporters
 
## Mesh bases/teleporters
## Better define/group support
 
### Links (with relative and absolute names)
 
### World weapons and entry zones (with transforms)
 
### Physics drivers (with transforms and copying)
 
### Texture matrices, dynamic colors, transforms, materials
 
 
# Server Side Players
 
# Server Side Players
 
## Server-side shot path tracking
 
## Server-side shot path tracking
Line 47: Line 40:
 
##* Locale
 
##* Locale
 
## Implement MsgAllow from 2.99.x (or should this be part of the per-player name/value pair system?)
 
## Implement MsgAllow from 2.99.x (or should this be part of the per-player name/value pair system?)
## [[DevelopmentPlans/ShotIDCleanup|Shot ID cleanup]]
 
## Make client aware of shot limit so it can display count and can know when the flag is going to drop
 
## Allow switching teams without rejoining
 
## Rework the joining process
 
### Handle all ban checks (including DNS resolution and hostban checks) before allowing the player to pull the world or enter.
 
### Move team selection to after the join (start off in observer, and have a dialog)
 
## List server indication of game options that are per object or zone ( rico, jump, etc..)
 
## Generic server-controlled marker and hunt system.
 
## Use BZID for all saved user identifiers not names.
 
 
==Misc==
 
 
# Clean up platform code. For instance:
 
## Make the ResInfo class also contain a depth value so that Windows doesn't have to have it's own custom Resolution class, and then sort based on the ResInfo items instead of platform specific sorting methods (Windows and Linux platform code have their own very similar methods).
 
## Make the Linux platform code build again (which may be solved by just doing the ResInfo change). Note that SDL is the normal platform for Linux systems, so the 'Linux' platform code is for Linux systems without SDL.
 
 
[[Category:Development Plans]]
 

Please note that all contributions to BZFlagWiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see BZFlagWiki:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel | Editing help (opens in new window)