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

Editing V3RCChecklist

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==
−
V3.0 has some major problems that prevent it from being close to a release candidate. This page will list the remaining items that need to be addressed before an RC can be made.  
+
V3.0 is very close to a release candidate. This page will list the remaining items that need to be addressed before an RC can be made.
  
 
==RC Critical fixes.==
 
==RC Critical fixes.==
−
# Dead-reckoning / lag-compensation testing / message loop / lag.
+
# MsgPause fix
−
# MsgPause fix.
+
# MsgJoinServer fix
−
# Team flag disappears while the tank that was carrying it is dead.
+
−
# Some letters are not rendered in certain font sizes.
+
  
 
==RC Critical Tasks==
 
==RC Critical Tasks==
 +
# Windows installer review (install VC9 runtimes etc..)
 
# Linux Package review (new files in the right places )
 
# Linux Package review (new files in the right places )
 
# Mac installer review (check it in)
 
# Mac installer review (check it in)
 
# Readme Updates
 
# Readme Updates
 
# Docs for V3 changes (-a missing, caps on server, lag comp, etc..)
 
# Docs for V3 changes (-a missing, caps on server, lag comp, etc..)
 +
# Replay System tested.
 
# API review (spelling, consistency)
 
# API review (spelling, consistency)
  
 
==RC 'really nice' features ==
 
==RC 'really nice' features ==
−
# Implement map features to define proper "flag pass" behavior in maps that want it
+
# Ask user to accept non bzflag.org images
−
# Ask user to accept non bzflag.org images  
+
−
# Ask user to join non bzflag.org servers (MsgJoinServer)
+
−
# Parity mesh checks to replace inside/outside points
+
  
 
==RC 'really nice' Fixes/Tasks==
 
==RC 'really nice' Fixes/Tasks==
 
# Webadmin template review ( for style )
 
# Webadmin template review ( for style )
−
 
−
==Notes==
 
−
 
−
===Flag "pass" issues===
 
−
The current method of using the flag respawn on drop to pass a team flag was never a defined 'feature' of the game. Many maps have been designed to turn this into a gameplay feature. In order to be able to maintain this type of gameplay a real feature has to be implemented to support it. Current development code has already "broken" teleporter passing by improving the definitions of the teleporter geometry and making no longer a "bad" place to put a flag. Similar enhancements are expected to be made in other parts of the world that would break other types of passing.
 
−
 
−
To properly support the desired behavior a set of map defined zones or faces needs to be implemented that can detect when specific flags are dropped on them and define a respawn target zone or area. This will allow maps to fully define pass zones in an arbitrary way for any flag. Defining the a real feature will prevent new code from changing the defined behavior in adverse ways.
 
−
 
−
[[Category:BZFlag 2.99]]
 

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)
Retrieved from "https://wiki.bzflag.org/V3RCChecklist"