BZFlagWiki - User contributions [en]

Bz fireWorldGM

2012-02-16T07:20:47Z

L4m3r: added shot team param

{{apicall
| name = bz_fireWorldGM
| description = Fires a Guided Missile at a player.
| param1 = targetPlayerID
| param1type = int
| param1desc = Player to fire the GM at.
| param2 = lifetime
| param2type = float
| param2desc = How long the world weapon will "live".
| param3 = *pos
| param3type = float
| param3desc = Position the world weapon will fire from.
| param4 = tilt
| param4type = float
| param4desc = The tilt of the weapon.
| param5 = direction
| param5type = float
| param5desc = The direction of which to fire the world weapon. (rotation)
| param6 = dt
| param6type = float
| param6desc = Delay time. How many seconds to wait before firing the GM.
| param7 = shotTeam
| param7type = bz_eTeamType
| param7desc = Team color of the missile. (Rogue by default)
}}

Bz fireWorldWep

2012-02-16T07:17:23Z

L4m3r: /* Prototype */

{{BZFS_API_Doc}}
{{BZFS_API_Funcs}}
==Prototype==
BZF_API bool bz_fireWorldWep ( const char* flagType, float lifetime, int fromPlayer, float *pos, float tilt, float direction, int shotID , float dt , bz_eTeamType shotTeam = eRogueTeam );

==Parameters==
{| border="1" cellpadding="20" cellspacing="0"
!name
!type
!value desription
|-
|flagType
|const char*
|Flag type the world weapon will fire with
|-
|lifetime
|float
|How long the world weapon will "live".
|-
|fromPlayer
|int
|Player ID that fired the shot, or BZ_SERVER.
|-
|*pos
|float
|Position the world weapon will fire from.
|-
|tilt
|float
|The tilt of the weapon in radians.
|-
|direction
|float
|The direction of which to fire the world weapon in radians. (rotation)
|-
|shotID
|int
|Shot ID of the world weapon. Each shot is given a unique shot ID for shot tracking.
|-
|dt
|float
|Delay time. How many seconds the weapon waits before firing.
|-
|shotTeam
|bz_eTeamType
|Team color of the weapon. (Rogue by default)
|}

==Description==
This API function will fire w worldweapon at the specified location with the specified parameters.

Bz fireWorldWep

2012-02-16T07:16:52Z

L4m3r: /* Parameters */

{{BZFS_API_Doc}}
{{BZFS_API_Funcs}}
==Prototype==
BZF_API bool bz_fireWorldWep ( const char* flagType, float lifetime, int fromPlayer, float *pos, float tilt, float direction, int shotID , float dt );
==Parameters==
{| border="1" cellpadding="20" cellspacing="0"
!name
!type
!value desription
|-
|flagType
|const char*
|Flag type the world weapon will fire with
|-
|lifetime
|float
|How long the world weapon will "live".
|-
|fromPlayer
|int
|Player ID that fired the shot, or BZ_SERVER.
|-
|*pos
|float
|Position the world weapon will fire from.
|-
|tilt
|float
|The tilt of the weapon in radians.
|-
|direction
|float
|The direction of which to fire the world weapon in radians. (rotation)
|-
|shotID
|int
|Shot ID of the world weapon. Each shot is given a unique shot ID for shot tracking.
|-
|dt
|float
|Delay time. How many seconds the weapon waits before firing.
|-
|shotTeam
|bz_eTeamType
|Team color of the weapon. (Rogue by default)
|}

==Description==
This API function will fire w worldweapon at the specified location with the specified parameters.

Functions (API)

2012-02-16T07:11:55Z

L4m3r: /* World Weapon Management */

{{DoDoc|
Fill in articles for all API Functions<br>
Finish updating to 2.3.x<br>
Verify future API functions.
}}

{{BZFS_API_Doc}}

== Overview ==

The BZFS API provides a number of functions to plug-ins for use in querying the current game state. Functions are used both to get information about the game, and to trigger in game actions, such as activating a world weapon.

== Function Groups ==
Functions are broken into a series of groups based on the type of action or information they deal with.

=== Event Registration ===
2.0.x
BZF_API bool [[bz_registerEvent]] ( [[Event(API)|bz_eEventType]] eventType, [[Event(API)|bz_EventHandler]]* eventHandler );
BZF_API bool [[bz_removeEvent]] ( [[Event(API)|bz_eEventType]] eventType, [[Event(API)|bz_EventHandler]]* eventHandler );
2.3+
BZF_API bool [[Register]] ( [[Event(API)|bz_eEventType]] eventType );
virtual void Cleanup() {Flush();}

=== Non-Player Connections ===
2.3+
BZF_API bool [[bz_registerNonPlayerConnectionHandler]] ( int connectionID, [[bz_NonPlayerConnectionHandler]]* handler );
BZF_API bool [[bz_removeNonPlayerConnectionHandler]] ( int connectionID, [[bz_NonPlayerConnectionHandler]]* handler );
BZF_API bool [[bz_sendNonPlayerData]] ( int connectionID, const void *data, unsigned int size );
BZF_API bool [[bz_disconectNonPlayerConnection]] ( int connectionID );
BZF_API unsigned int [[bz_getNonPlayerConnectionOutboundPacketCount]] ( int connectionID );
BZF_API const char* [[bz_getNonPlayerConnectionIP]] ( int connectionID );
BZF_API const char* [[bz_getNonPlayerConnectionHost]] ( int connectionID );

=== Player Information ===
==== Player Information ====
2.3+
BZF_API bool [[bz_hasPerm]] ( int playerID, const char* perm );
BZF_API bool [[bz_getAdmin]] ( int playerID );
BZF_API bz_eTeamType [[bz_getPlayerTeam]] ( int playerID );
BZF_API const char* [[bz_getPlayerCallsign]] ( int playerID );
BZF_API const char* [[bz_getPlayerIPAddress]] ( int playerID );
BZF_API const char* [[bz_getPlayerFlag]] ( int playerID );
?
BZF_API const char* [[bz_getPlayerReferrer]] ( int playerID );
BZF_API const char* [[bz_getPlayerCustomData]] (int playerID, const char* key );

==== Player State Information ====
2.3+
BZF_API bool [[bz_isPlayerPaused]] ( int playerID );
BZF_API bool [[bz_canPlayerSpawn]]( int playerID );
BZF_API bool [[bz_getPlayerCurrentState]] ( int playerID, bz_PlayerUpdateState &state );
?
BZF_API bool [[bz_getPlayerPosition]] ( int playerID, float pos[3], bool extrapolate );
BZF_API bool [[bz_getPlayerRotation]] ( int playerID, float *rot, bool extrapolate );
BZF_API bool [[bz_getPlayerVelocity]] ( int playerID, float vel[3] );
BZF_API bool [[bz_getPlayerAngVel]] ( int playerID, float *angvel );
BZF_API bool [[bz_getPlayerPhysicsDriver]] ( int playerID, int* phydrv );

==== Player Lists and Records ====
2.3+
BZF_API [[bz_BasePlayerRecord]] *[[bz_getPlayerByIndex]] ( int index );
BZF_API [[bz_BasePlayerRecord]] *[[bz_getPlayerByCallsign]] ( const char* name );
BZF_API [[bz_BasePlayerRecord]] *[[bz_getPlayerByBZID]] ( int BZID );
BZF_API bool [[bz_updatePlayerData]] ( [[bz_BasePlayerRecord]] *playerRecord );
BZF_API bool [[bz_freePlayerRecord]] ( [[bz_BasePlayerRecord]] *playerRecord );

BZF_API [[bz_APIIntList]] *[[bz_newIntList]] ( void );
BZF_API [[bz_APIIntList]] *[[bz_getPlayerIndexList]] ( void );
BZF_API bool [[bz_getPlayerIndexList]] ( [[bz_APIIntList]] *playerList );
BZF_API void [[bz_deleteIntList]] ( [[bz_APIIntList]] *l);

==== Player Management ====
2.3+
BZF_API bool [[bz_grantPerm]] ( int playerID, const char* perm );
BZF_API bool [[bz_revokePerm]] ( int playerID, const char* perm );
BZF_API bool [[bz_validAdminPassword]] ( const char* passwd );
BZF_API bool [[bz_setPlayerOperator]] ( int playerId );
?
BZF_API bool [[bz_setPlayerSpawnable]]( int playerID, bool spawn );
BZF_API bool [[bz_setPlayerLimboMessage]]( int playerID, const char* text );
BZF_API bool [[bz_setPlayerCustomData]] (int playerID, const char* key, const char* data );

=== Team Management ===
2.3+
BZF_API unsigned int [[bz_getTeamPlayerLimit]] ( bz_eTeamType team );
BZF_API int [[bz_getTeamCount]] ([[bz_eTeamType]] team );
BZF_API int [[bz_getTeamScore]] ([[bz_eTeamType]] team );
BZF_API int [[bz_getTeamWins]] ([[bz_eTeamType]] team );
BZF_API int [[bz_getTeamLosses]] ([[bz_eTeamType]] team );
BZF_API void [[bz_setTeamWins]] ([[bz_eTeamType]] team, int wins );
BZF_API void [[bz_setTeamLosses]] ([[bz_eTeamType]] team, int losses );
BZF_API void [[bz_resetTeamScore]] ([[bz_eTeamType]] team );
BZF_API void [[bz_resetTeamScores]] ( void );
?
BZF_API void [[bz_changeTeam]]( int player, [[bz_eTeamType]] team );

=== Score Management ===
2.3+
BZF_API bool [[bz_setPlayerWins]] ( int playerId, int wins );
BZF_API bool [[bz_setPlayerLosses]] ( int playerId, int losses );
BZF_API bool [[bz_setPlayerTKs]] ( int playerId, int tks );
BZF_API bool [[bz_resetPlayerScore]] ( int playerId );
BZF_API int [[bz_getPlayerWins]] ( int playerId );
BZF_API int [[bz_getPlayerLosses]] ( int playerId );
BZF_API int [[bz_getPlayerTKs]] ( int playerId );
BZF_API float [[bz_getPlayerRank]] ( int playerId );

=== Latency Information ===
2.3+
BZF_API int [[bz_getPlayerLag]] ( int playerId );
BZF_API int [[bz_getPlayerJitter]] ( int playerId );
BZF_API float [[bz_getPlayerPacketloss]] ( int playerId );

=== Permission Group Management ===
2.3+
BZF_API [[bz_APIStringList]]* [[bz_getGroupList]] ( void );
BZF_API [[bz_APIStringList]]* [[bz_getGroupPerms]] ( const char* group );
BZF_API bool [[bz_groupAllowPerm]] ( const char* group, const char* perm );

=== Chat Messages ===
2.3+
BZF_API bool [[bz_sendTextMessage]] (int from, int to, const char* message);
BZF_API bool [[bz_sendTextMessage]] (int from, [[bz_eTeamType]] to, const char* message);
BZF_API bool [[bz_sendTextMessagef]] (int from, int to, const char* fmt, ...);
BZF_API bool [[bz_sendTextMessagef]] (int from, [[bz_eTeamType]] to, const char* fmt, ...);
?
BZF_API bool [[bz_sendFetchResMessage]] ( int playerID, const char* URL );
BZF_API bool [[bz_sendJoinServer]] ( int playerID, const char* address, int port, int team, const char* referrer, const char* message );
BZF_API bool [[bz_sendLuaData]] ( int dstPlayerID, int dstScriptID, int statusBits, const char* data, int len,
int srcPlayerID = 0, int srcScriptID = 0 );

=== Server Management ===
2.3+
BZF_API bool [[bz_restart]] ( void );
BZF_API void [[bz_shutdown]] ();
BZF_API void [[bz_superkill]] ();
BZF_API void [[bz_gameOver]] ( int playerID, bz_eTeamType = eNoTeam );
BZF_API void [[bz_reloadLocalBans]] ();
BZF_API void [[bz_reloadMasterBans]] ();
BZF_API void [[bz_reloadGroups]] ();
BZF_API void [[bz_reloadUsers]] ();
BZF_API void [[bz_reloadHelp]] ();
?
BZF_API int [[bz_getPlayerCount]] ( void );
BZF_API bool [[bz_anyPlayers]] ( void );

=== Rabbit Hunt ===
?
BZF_API void [[bz_newRabbit]] ( int player, bool swap );
BZF_API void [[bz_removeRabbit]] ( int player );

=== Map Management ===
2.3+
BZF_API void [[bz_setClientWorldDownloadURL]] ( const char* URL );
BZF_API const [[bz_ApiString]] [[bz_getClientWorldDownloadURL]] ( void );
BZF_API bool [[bz_saveWorldCacheFile]] ( const char* file );

=== Flag Management ===
2.3+
BZF_API bool [[bz_givePlayerFlag]] ( int playerID, const char* flagType, bool force );
BZF_API bool [[bz_removePlayerFlag]] ( int playerID );
BZF_API void [[bz_resetFlags]] ( bool onlyUnused );
BZF_API unsigned int [[bz_getNumFlags]] ( void );
BZF_API const [[bz_ApiString]] [[bz_getFlagName|bz_getName]] ( int flag );
BZF_API bool [[bz_resetFlag]] ( int flag );
BZF_API int [[bz_flagPlayer]] ( int flag );
BZF_API bool [[bz_getFlagPosition]] ( int flag, float* pos );
BZF_API bool [[bz_moveFlag]] ( int flag, float pos[3] );
BZF_API bool [[bz_RegisterCustomFlag]] ( const char* abbr, const char* name, const char* helpString, bz_eShotType shotType, bz_eFlagQuality quality );

=== Shot Type Control ===
?
BZF_API bool [[bz_setPlayerShotType]] ( int playerId, [[bz_eShotType]] shotType );

=== World Weapon Management ===
2.3+
BZF_API bool [[bz_fireWorldWep]] ( const char* flagType, float lifetime, int fromPlayer, float *pos, float tilt, float direction, int shotID , float dt, bz_eTeamType shotTeam = eRogueTeam );
BZF_API int [[bz_fireWorldGM]] ( int targetPlayerID, float lifetime, float *pos, float tilt, float direction, float dt, bz_eTeamType shotTeam = eRogueTeam );

=== Server Time ===
2.3+
BZF_API double [[bz_getCurrentTime]] ( void );
BZF_API void [[bz_getLocaltime]] ( [[bz_Time]] *ts );
BZF_API void [[bz_getUTCtime]] ( [[bz_Time]] *ts );

?
BZF_API float [[bz_getMaxWaitTime]] ( void );
BZF_API void [[bz_setMaxWaitTime]] ( float maxTime );

=== Global Database Management (BZDB) ===
2.3+
BZF_API double [[bz_getBZDBDouble]] ( const char* variable );
BZF_API [[bz_ApiString]] [[bz_getBZDBString]] ( const char* variable );
BZF_API bool [[bz_getBZDBBool]] ( const char* variable );
BZF_API int [[bz_getBZDBInt]] ( const char* variable );
BZF_API int [[bz_getBZDBItemPerms]] ( const char* variable );
BZF_API bool [[bz_getBZDBItemPesistent]] ( const char* variable );
BZF_API bool [[bz_BZDBItemExists]] ( const char* variable );
BZF_API bool [[bz_setBZDBDouble]] ( const char* variable, double val, int perms = 0, bool persistent = false );
BZF_API bool [[bz_setBZDBString]] ( const char* variable, const char *val, int perms = 0, bool persistent = false );
BZF_API bool [[bz_setBZDBBool]] ( const char* variable, bool val, int perms = 0, bool persistent = false );
BZF_API bool [[bz_setBZDBInt]] ( const char* variable, int val, int perms = 0, bool persistent = false );
BZF_API int [[bz_getBZDBVarList]] ( bz_APIStringList *varList );
BZF_API void [[bz_resetBZDBVar]] ( const char* variable );
BZF_API void [[bz_resetALLBZDBVars]] ( void );

=== Logging ===
2.3+
BZF_API void [[bz_debugMessage]] ( int level, const char* message );
BZF_API void [[bz_debugMessagef]] ( int level, const char* fmt, ... )
BZF_API int [[bz_getDebugLevel]] ( void );

=== Server Administration ===
2.3+
BZF_API bool [[bz_kickUser]] ( int playerIndex, const char* reason, bool notify );
BZF_API bool [[bz_IPBanUser]] ( int bannedByIndex, const char* ip, int duration, const char* reason );
BZF_API bool [[bz_HostBanUser]] ( int bannedByIndex, const char* hostmask, int duration, const char* reason );
BZF_API bool [[bz_IPUnbanUser]] ( const char* ip );
BZF_API bool [[bz_IDUnbanUser]] ( const char* bzID );
BZF_API bool [[bz_HostUnbanUser]] ( const char* hostmask );

BZF_API int [[bz_getLagWarn]] ( void );
BZF_API bool [[bz_setLagWarn]] ( int lagwarn );
BZF_API bool [[bz_pollActive]] ( void );
BZF_API bool [[bz_pollVeto]] ( void );

?
BZF_API bool [[bz_IDBanUser]] ( int bannedByIndex, const char* bzID , int duration, const char *reason );

=== Reporting ===
2.3+
BZF_API [[bz_APIStringList]]* [[bz_getReports]] ( void );
?
BZF_API unsigned int [[bz_getReportCount]] ( void );
BZF_API const char* [[bz_getReportSource]] ( unsigned int id );
BZF_API const char* [[bz_getReportBody]] ( unsigned int id );
BZF_API const char* [[bz_getReportTime]] ( unsigned int id );
BZF_API bool [[bz_clearReport]] ( unsigned int id );
BZF_API bool [[bz_clearAllReports]] ( void );
BZF_API bool [[bz_fileReport]] ( const char* message, const char* from );

=== Timed Game Management ===
2.3+
BZF_API bool [[bz_setTimeLimit]] ( float timeLimit );
BZF_API float [[bz_getTimeLimit]] ( void );
BZF_API bool [[bz_isTimeManualStart]] ( void );
BZF_API bool [[bz_isCountDownActive]] ( void );
BZF_API bool [[bz_isCountDownInProgress]] ( void );
BZF_API void [[bz_pauseCountdown]] ( const char *pausedBy );
BZF_API void [[bz_resumeCountdown]] ( const char *resumedBy );
BZF_API void [[bz_startCountdown]] ( int delay, float limit, const char *byWho );

=== Custom Text Commands ===
2.3+
BZF_API bool [[bz_registerCustomSlashCommand]] ( const char* command, [[bz_CustomSlashCommandHandler]] *handler );
BZF_API bool [[bz_removeCustomSlashCommand]] ( const char* command );

=== Plug-in Management ===
2.3+
BZF_API int [[bz_getLoadedPlugins]] ( [[bz_APIStringList]] * list );
BZF_API bool [[bz_loadPlugin]] ( const char* path, const char* params );
BZF_API bool [[bz_unloadPlugin]] ( const char* path );
BZF_API const char* [[bz_pluginBinPath]] ( void );
BZF_API bool [[bz_registerCustomPluginHandler]] ( const char* extension, [[bz_APIPluginHandler]] * handler );
BZF_API bool [[bz_removeCustomPluginHandler]] ( const char* extension, [[bz_APIPluginHandler]] * handler );

=== Public Server Information ===
2.3+
BZF_API bool [[bz_getPublic]] ( void );
BZF_API [[bz_ApiString]] [[bz_getPublicAddr]] ( void );
BZF_API [[bz_ApiString]] [[bz_getPublicDescription]] ( void );
BZF_API int [[bz_getPublicPort]] ( void );
BZF_API void [[bz_updateListServer]] ( void );

=== HTTP Transfer ===
2.3+
BZF_API bool [[bz_addURLJob]] ( const char* URL, [[bz_BaseURLHandler]]* handler = NULL, const char* postData = NULL );
BZF_API bool [[bz_removeURLJob]] ( const char* URL );
?
BZF_API bool [[bz_stopAllURLJobs]] ( void );

=== Callback Functions ===
?
BZF_API bool [[bz_registerCallBack]] ( const char* name, [[bz_GenericCallback]] *callback );
BZF_API bool [[bz_registerCallBack]] ( const char* name, [[bz_GenericCallbackFunc]] callback );
BZF_API bool [[bz_removeCallBack]] ( const char* name, [[bz_GenericCallback]] *callback );
BZF_API bool [[bz_removeCallBack]] ( const char* name, [[bz_GenericCallbackFunc]] callback );
BZF_API bool [[bz_callCallback]] ( const char* name, void *param );
BZF_API bool [[bz_callbackExists]] ( const char* name );

=== Inter-Plug-in Communications ===
2.3+
BZF_API bool [[bz_clipFieldExists]] ( const char *name );
BZF_API const char* [[bz_getclipFieldString]] ( const char *name );
BZF_API float [[bz_getclipFieldFloat]] ( const char *name );
BZF_API int [[bz_getclipFieldInt]] ( const char *name );
BZF_API bool [[bz_setclipFieldString]] ( const char *name, const char* data );
BZF_API bool [[bz_setclipFieldFloat]] ( const char *name, float data );
BZF_API bool [[bz_setclipFieldInt]] ( const char *name, int data );
BZF_API bool [[bz_addClipFieldNotifier]] ( const char *name, [[bz_ClipFiledNotifier *cb );
BZF_API bool [[bz_removeClipFieldNotifier]] ( const char *name, [[bz_ClipFiledNotifier *cb );

=== Game Recording ===
2.3+
BZF_API bool [[bz_saveRecBuf]] ( const char * _filename, int seconds);
BZF_API bool [[bz_startRecBuf]] ( void );
BZF_API bool [[bz_stopRecBuf]] ( void );

=== Map Management ===
==== Map Information ====
?
BZF_API void [[bz_getWorldSize]] ( float *size, float *wallHeight );
BZF_API unsigned int [[bz_getWorldObjectCount]] ( void );
BZF_API [[bz_APIWorldObjectList]]* [[bz_getWorldObjectList]] ( void );
BZF_API void [[bz_releaseWorldObjectList]] ( [[bz_APIWorldObjectList]] *list );
BZF_API unsigned int [[bz_findWorldObject]] ( const char *name );
BZF_API [[bz_APIBaseWorldObject]]* [[bz_getWorldObjectByID]] ( unsigned int id );
BZF_API bool [[bz_getTeleLinkIDs]] ( const char* teleName, int* frontLink, int* backLink );
BZF_API const char* [[bz_getLinkTeleName]] ( int linkIndex );
BZF_API int [[bz_getPhyDrvID]] ( const char* phyDrvName );
BZF_API const char* [[bz_getPhyDrvName]] ( unsigned int phyDrvID );
BZF_API bool [[bz_SetWorldObjectTangibility]] ( int id, const [[bz_SolidObjectPassableAtributes]] &atribs );
BZF_API bool [[bz_GetWorldObjectTangibility]] ( int id, [[bz_SolidObjectPassableAtributes]] &atribs );
BZF_API void [[bz_ResetWorldObjectTangibilities]] ( void );

==== Map Collisions ====
?
[[bz_eAPIColType]] [[bz_cylinderInMapObject]] ( float pos[3], float height, float radius, [[bz_APIBaseWorldObject]] **object );
[[bz_eAPIColType]] [[bz_boxInMapObject]] ( float pos[3], float size[3], float angle, [[bz_APIBaseWorldObject]] **object );

==== Custom Map Objects ====
2.3+
BZF_API bool [[bz_registerCustomMapObject]] ( const char* object, [[bz_CustomMapObjectHandler]] *handler );
BZF_API bool [[bz_removeCustomMapObject]] ( const char* object );

=== Utility ===
2.3+
BZF_API const char *[[bz_MD5]] ( const char* str );
BZF_API const char *[[bz_MD5]] ( const void* data, size_t size );
BZF_API const char *[[bz_getServerVersion]] ( void );
BZF_API const char *[[bz_getProtocolVersion]] ( void );

=== Misc ===
2.3+
BZF_API bool [[bz_getStandardSpawn]] ( int playerID, float pos[3], float *rot );
BZF_API bool [[bz_killPlayer]] ( int playerID, bool spawnOnBase, int killerID = -1, const char* flagID = NULL );
BZF_API bool [[bz_sendPlayCustomLocalSound]] ( int playerID, const char* soundName );
BZF_API [[bz_ApiString]] [[bz_filterPath]] ( const char* path );
BZF_API const char *[[bz_format]](const char* fmt, ...)_ATTRIBUTE12;
BZF_API const char *[[bz_toupper]](const char* val );
BZF_API const char *[[bz_tolower]](const char* val );
BZF_API const char *[[bz_urlEncode]](const char* val );
BZF_API [[bz_eGameType]] [[bz_getGameType]]( void );
BZF_API [[bz_eTeamType]] [[bz_checkBaseAtPoint]] ( float pos[3] );
BZF_API int [[bz_APIVersion]] ( void );
?
BZF_API bool [[bz_allowJumping]] ( void );

=== Server Side Players (Development) ===
? (In API for 2.3+, but will crash a server)
BZF_API int [[bz_addServerSidePlayer]] ( [[bz_ServerSidePlayerHandler]] *handler );
BZF_API bool [[bz_removeServerSidePlayer]] ( int playerID, [[bz_ServerSidePlayerHandler]] *handler );

== See also ==
[[BZFS API]]

[[plug-ins]]

[[Category:BZFS_API_Functions]]

Passion

2012-02-01T06:00:24Z

L4m3r: /* L4m3r's Re-work */

The 'Passion' map (previously known as 'christ.map'), was a popular map hosted by the group [[PlanetMoFo]] and other servers for some time. It is so called because when displayed on the list server, MoFo will title it as "Planet MoFo: The Passion Of The <game mode>". It has undergone constant modification and change since its introduction, though every incarnation of the map has been of the same general format:
* A three tiered central "cake" with crosses on the top, and tunnels running through the middle.
* Outer [[box|boxes]] at the corners and in the middle of the sides. The corner boxes can be substituted for bases and have flat pyramids above them.
* Two smaller [[pyramid|pyramids]] in each quarter of the map.
* [[teleporter|Teleporters]] on the outer [[box|boxes]]. Which outer boxes have [[teleporter|teleporters]] depends on the game mode.

==Map History ==
=== Early map ===
[[Image:Christ.jpg|thumb|right|Christ.map]]
The map was originally known as "christ.map" designed by Ducatiwannabe. This looks somewhat different from the current map, though the basic features are still recognizable.

=== "Classic" Passion ===
[[Image:classicmofo.jpg|thumb|right|Classic Passion map]]
This bears more resemblance to the map played on the sever now. The characteristic "MoFo in the sky" was added, as well as flat pyramids over the bases, more outer boxes and more pyramids.

The flat corner pyramids have developed into a well-known camping spot for guided missiles.

=== Current Map ===
[[Image:Moforabbit.jpg|thumb|right|Current Passion map in rabbit hunt mode.]]
The current map has been re-made using 2.0 objects, and is now almost completely [[mesh]]. The center cake has been changed to look more '2.0', with the slight change in its shape, as well as the Planet MoFo FFA logo on the side and an Oscillation Overthruster camping spot. There were also further minor changes to the map in general. It is currently in its second revision.

==== Billboards ====
In early 2007, billboards were introduced to display informative and amusing messages and pictures. They have been a great success since their launch, and Planet MoFo currently offer slots on the billboard rotation for those that have donated to the server. An archive of all the billboard images can be found at http://cbg.bzflag.org/images/billboards/

== Variations==

The map has been edited to cater for all the major game styles, as well as some of the less popular ones, such as [[HTF]]. Other than these, there have been several other maps based around the original.

=== L4m3r's Re-work ===

This was one of the first additions of 2.0 elements to the original map, and was popular for some time. The crosses on the central cake were colored dark red, skewed to lean outward, and extended down to the ground through the cake's 3 layers. The middle tier of the cake was made drivethrough, and the flattened pyramids over the corners were replaced with a one-way mesh that tanks could not land on. The "MoFo in the sky" was also redone, this time using a flat mesh that flashed red and black.

Originally, the map also included transparent "glass" floors in parts of the center cake, but these were later removed because players were falling through them.

=== Passion of the Polygon ===

L4m3r adapted the Passion layout into a hexagonal map to create the Passion of the Polygon. Somewhat larger than the square Passion, the hexagonal version has 6 corners and uses 6-sided boxes and pyramids. Like the other geometric variations that followed, Passion of the Polygon was only used on the main server briefly as a novelty. However, L4m3r also used the hexagon for the "Steal the Bacon" game mode due to its symmetry for 3-team CTF.

A rhombus-shaped Passion was also developed for two-team CTF, with bases at opposing corners.

=== Passion of the 3-way ===

Two triangular passion maps were made, one by Spazzy McGee, the other by L4m3r. They both triangulated most objects, though in l4m3r's version, meshed skins were applied to the bases to make them triangular. In Spazzy McGee's they remained square.

=== April Fools ===

Some amusing Passion variants have been designed for April Fools' Day.

One year, L4m3r constructed a "Tiny-Huge Passion", inspired by "Tiny-Huge Island" from ''Super Mario 64''. It was actually two copies of the standard Passion, one at 150% scale, and the other at 75%. The two Passions were connected only by their teleporters and set far apart in the game world, making it difficult to see one section from the other. The result was that players would travel through a teleporter to unknowingly arrive in the corresponding location of the other map, creating the illusion that the map had suddenly become much smaller or larger.

On April 1st, 2007, The MoFo team revealed a Hell-themed map which featured several changes. The usual "MoFo in the sky" was replaced with a giant pentagram, and the pyramids were made to spin. In place of the corner boxes were large, lopsided pyramids with flat sections cut out near ground level. The outer walls were removed, and the charcoal-colored ground was made "finite" in appearance, only extending a small distance outside the map boundary. Outside, a cylindrical wall of spinning, rising flames was added. This made the entire map appear to be spinning and falling through fire, as if into Hell; many players and a few of the MoFo admin team complained that the decoration made them feel disoriented when they tried to play. The added ricochet in the corner areas, removal of GM camping areas above the corners, and lack of outer walls also altered the map's usual gameplay.

=== The Inversion ===

Made by Spazzy McGee, this is the normal map, but instead of blocks, everything is inverted as holes in the ground.

=== MoFo Garage ===

A map by Sir_Pants that has a large car-park like structure below it.

=== Two Storey MoFo ===

Recently re-vamped, this map by Sir_Pants is similar to MoFo garage, but is much more playable. Among the added features were the second story beneath the main play area, and jump pads to go from the lower to top level. It is designed to be a 2-team CTF map, and Sir_Pants recommends the removal of the SW flag when playing this map.

=== Mammoth ===

This is a huge map with five cakes. It's basically four standard passion maps plugged together. It only really works with lots of players, but can be quite an interesting battle, since there are so many places to hide.

=== Epileptic Fit ===

A-Delusion's [[TextureMatrix]] 101.

=== Halloween Edition ===

For halloween 2007, the Planet MoFo team devised several draw-info animations objects, such as bats, dancing skeletons, and spiders. The map was also given a full texture makeover, with rotten wood and stone textures replacing the standard bricks. The map was received well, and is one of the few examples of where drawinfo code has been utilized in a successful map.

== Controversy ==

There has been some controversy surrounding Planet MoFo's use of this map. Originally, the map was designed for use on more conservative servers, however the map was hosted on a server network known for its liberalism. This was thought by some to be inappropriate, but the hosts and the author have since come to an agreement over its use and modification.

[[Category:Maps]]
[[Category:CTF Maps]]
[[Category:2 Team Maps]]

Passion

2012-02-01T05:49:55Z

L4m3r: /* Passion of the Polygon */

The 'Passion' map (previously known as 'christ.map'), was a popular map hosted by the group [[PlanetMoFo]] and other servers for some time. It is so called because when displayed on the list server, MoFo will title it as "Planet MoFo: The Passion Of The <game mode>". It has undergone constant modification and change since its introduction, though every incarnation of the map has been of the same general format:
* A three tiered central "cake" with crosses on the top, and tunnels running through the middle.
* Outer [[box|boxes]] at the corners and in the middle of the sides. The corner boxes can be substituted for bases and have flat pyramids above them.
* Two smaller [[pyramid|pyramids]] in each quarter of the map.
* [[teleporter|Teleporters]] on the outer [[box|boxes]]. Which outer boxes have [[teleporter|teleporters]] depends on the game mode.

==Map History ==
=== Early map ===
[[Image:Christ.jpg|thumb|right|Christ.map]]
The map was originally known as "christ.map" designed by Ducatiwannabe. This looks somewhat different from the current map, though the basic features are still recognizable.

=== "Classic" Passion ===
[[Image:classicmofo.jpg|thumb|right|Classic Passion map]]
This bears more resemblance to the map played on the sever now. The characteristic "MoFo in the sky" was added, as well as flat pyramids over the bases, more outer boxes and more pyramids.

The flat corner pyramids have developed into a well-known camping spot for guided missiles.

=== Current Map ===
[[Image:Moforabbit.jpg|thumb|right|Current Passion map in rabbit hunt mode.]]
The current map has been re-made using 2.0 objects, and is now almost completely [[mesh]]. The center cake has been changed to look more '2.0', with the slight change in its shape, as well as the Planet MoFo FFA logo on the side and an Oscillation Overthruster camping spot. There were also further minor changes to the map in general. It is currently in its second revision.

==== Billboards ====
In early 2007, billboards were introduced to display informative and amusing messages and pictures. They have been a great success since their launch, and Planet MoFo currently offer slots on the billboard rotation for those that have donated to the server. An archive of all the billboard images can be found at http://cbg.bzflag.org/images/billboards/

== Variations==

The map has been edited to cater for all the major game styles, as well as some of the less popular ones, such as [[HTF]]. Other than these, there have been several other maps based around the original.

=== L4m3r's Re-work ===

This was one of the first attempts at 2.0izing the original map, and was popular for some time. The crosses on the central cake were modified to be slanted, and the middle section of the cake was drivethrough. The 'MoFo in the sky' was modified to be a mesh and flashed red and black.

=== Passion of the Polygon ===

L4m3r adapted the Passion layout into a hexagonal map to create the Passion of the Polygon. Somewhat larger than the square Passion, the hexagonal version has 6 corners and uses 6-sided boxes and pyramids. Like the other geometric variations that followed, Passion of the Polygon was only used on the main server briefly as a novelty. However, L4m3r also used the hexagon for the "Steal the Bacon" game mode due to its symmetry for 3-team CTF.

A rhombus-shaped Passion was also developed for two-team CTF, with bases at opposing corners.

=== Passion of the 3-way ===

Two triangular passion maps were made, one by Spazzy McGee, the other by L4m3r. They both triangulated most objects, though in l4m3r's version, meshed skins were applied to the bases to make them triangular. In Spazzy McGee's they remained square.

=== April Fools ===

Some amusing Passion variants have been designed for April Fools' Day.

One year, L4m3r constructed a "Tiny-Huge Passion", inspired by "Tiny-Huge Island" from ''Super Mario 64''. It was actually two copies of the standard Passion, one at 150% scale, and the other at 75%. The two Passions were connected only by their teleporters and set far apart in the game world, making it difficult to see one section from the other. The result was that players would travel through a teleporter to unknowingly arrive in the corresponding location of the other map, creating the illusion that the map had suddenly become much smaller or larger.

On April 1st, 2007, The MoFo team revealed a Hell-themed map which featured several changes. The usual "MoFo in the sky" was replaced with a giant pentagram, and the pyramids were made to spin. In place of the corner boxes were large, lopsided pyramids with flat sections cut out near ground level. The outer walls were removed, and the charcoal-colored ground was made "finite" in appearance, only extending a small distance outside the map boundary. Outside, a cylindrical wall of spinning, rising flames was added. This made the entire map appear to be spinning and falling through fire, as if into Hell; many players and a few of the MoFo admin team complained that the decoration made them feel disoriented when they tried to play. The added ricochet in the corner areas, removal of GM camping areas above the corners, and lack of outer walls also altered the map's usual gameplay.

=== The Inversion ===

Made by Spazzy McGee, this is the normal map, but instead of blocks, everything is inverted as holes in the ground.

=== MoFo Garage ===

A map by Sir_Pants that has a large car-park like structure below it.

=== Two Storey MoFo ===

Recently re-vamped, this map by Sir_Pants is similar to MoFo garage, but is much more playable. Among the added features were the second story beneath the main play area, and jump pads to go from the lower to top level. It is designed to be a 2-team CTF map, and Sir_Pants recommends the removal of the SW flag when playing this map.

=== Mammoth ===

This is a huge map with five cakes. It's basically four standard passion maps plugged together. It only really works with lots of players, but can be quite an interesting battle, since there are so many places to hide.

=== Epileptic Fit ===

A-Delusion's [[TextureMatrix]] 101.

=== Halloween Edition ===

For halloween 2007, the Planet MoFo team devised several draw-info animations objects, such as bats, dancing skeletons, and spiders. The map was also given a full texture makeover, with rotten wood and stone textures replacing the standard bricks. The map was received well, and is one of the few examples of where drawinfo code has been utilized in a successful map.

== Controversy ==

There has been some controversy surrounding Planet MoFo's use of this map. Originally, the map was designed for use on more conservative servers, however the map was hosted on a server network known for its liberalism. This was thought by some to be inappropriate, but the hosts and the author have since come to an agreement over its use and modification.

[[Category:Maps]]
[[Category:CTF Maps]]
[[Category:2 Team Maps]]

Passion

2012-02-01T05:26:36Z

L4m3r: /* April Fools */

The 'Passion' map (previously known as 'christ.map'), was a popular map hosted by the group [[PlanetMoFo]] and other servers for some time. It is so called because when displayed on the list server, MoFo will title it as "Planet MoFo: The Passion Of The <game mode>". It has undergone constant modification and change since its introduction, though every incarnation of the map has been of the same general format:
* A three tiered central "cake" with crosses on the top, and tunnels running through the middle.
* Outer [[box|boxes]] at the corners and in the middle of the sides. The corner boxes can be substituted for bases and have flat pyramids above them.
* Two smaller [[pyramid|pyramids]] in each quarter of the map.
* [[teleporter|Teleporters]] on the outer [[box|boxes]]. Which outer boxes have [[teleporter|teleporters]] depends on the game mode.

==Map History ==
=== Early map ===
[[Image:Christ.jpg|thumb|right|Christ.map]]
The map was originally known as "christ.map" designed by Ducatiwannabe. This looks somewhat different from the current map, though the basic features are still recognizable.

=== "Classic" Passion ===
[[Image:classicmofo.jpg|thumb|right|Classic Passion map]]
This bears more resemblance to the map played on the sever now. The characteristic "MoFo in the sky" was added, as well as flat pyramids over the bases, more outer boxes and more pyramids.

The flat corner pyramids have developed into a well-known camping spot for guided missiles.

=== Current Map ===
[[Image:Moforabbit.jpg|thumb|right|Current Passion map in rabbit hunt mode.]]
The current map has been re-made using 2.0 objects, and is now almost completely [[mesh]]. The center cake has been changed to look more '2.0', with the slight change in its shape, as well as the Planet MoFo FFA logo on the side and an Oscillation Overthruster camping spot. There were also further minor changes to the map in general. It is currently in its second revision.

==== Billboards ====
In early 2007, billboards were introduced to display informative and amusing messages and pictures. They have been a great success since their launch, and Planet MoFo currently offer slots on the billboard rotation for those that have donated to the server. An archive of all the billboard images can be found at http://cbg.bzflag.org/images/billboards/

== Variations==

The map has been edited to cater for all the major game styles, as well as some of the less popular ones, such as [[HTF]]. Other than these, there have been several other maps based around the original.

=== L4m3r's Re-work ===

This was one of the first attempts at 2.0izing the original map, and was popular for some time. The crosses on the central cake were modified to be slanted, and the middle section of the cake was drivethrough. The 'MoFo in the sky' was modified to be a mesh and flashed red and black.

=== Passion of the Polygon ===

Another map made by L4m3r. This map is entirely hexagonal, and everything in the map is similarly hexagonal.

=== Passion of the 3-way ===

Two triangular passion maps were made, one by Spazzy McGee, the other by L4m3r. They both triangulated most objects, though in l4m3r's version, meshed skins were applied to the bases to make them triangular. In Spazzy McGee's they remained square.

=== April Fools ===

Some amusing Passion variants have been designed for April Fools' Day.

One year, L4m3r constructed a "Tiny-Huge Passion", inspired by "Tiny-Huge Island" from ''Super Mario 64''. It was actually two copies of the standard Passion, one at 150% scale, and the other at 75%. The two Passions were connected only by their teleporters and set far apart in the game world, making it difficult to see one section from the other. The result was that players would travel through a teleporter to unknowingly arrive in the corresponding location of the other map, creating the illusion that the map had suddenly become much smaller or larger.

On April 1st, 2007, The MoFo team revealed a Hell-themed map which featured several changes. The usual "MoFo in the sky" was replaced with a giant pentagram, and the pyramids were made to spin. In place of the corner boxes were large, lopsided pyramids with flat sections cut out near ground level. The outer walls were removed, and the charcoal-colored ground was made "finite" in appearance, only extending a small distance outside the map boundary. Outside, a cylindrical wall of spinning, rising flames was added. This made the entire map appear to be spinning and falling through fire, as if into Hell; many players and a few of the MoFo admin team complained that the decoration made them feel disoriented when they tried to play. The added ricochet in the corner areas, removal of GM camping areas above the corners, and lack of outer walls also altered the map's usual gameplay.

=== The Inversion ===

Made by Spazzy McGee, this is the normal map, but instead of blocks, everything is inverted as holes in the ground.

=== MoFo Garage ===

A map by Sir_Pants that has a large car-park like structure below it.

=== Two Storey MoFo ===

Recently re-vamped, this map by Sir_Pants is similar to MoFo garage, but is much more playable. Among the added features were the second story beneath the main play area, and jump pads to go from the lower to top level. It is designed to be a 2-team CTF map, and Sir_Pants recommends the removal of the SW flag when playing this map.

=== Mammoth ===

This is a huge map with five cakes. It's basically four standard passion maps plugged together. It only really works with lots of players, but can be quite an interesting battle, since there are so many places to hide.

=== Epileptic Fit ===

A-Delusion's [[TextureMatrix]] 101.

=== Halloween Edition ===

For halloween 2007, the Planet MoFo team devised several draw-info animations objects, such as bats, dancing skeletons, and spiders. The map was also given a full texture makeover, with rotten wood and stone textures replacing the standard bricks. The map was received well, and is one of the few examples of where drawinfo code has been utilized in a successful map.

== Controversy ==

There has been some controversy surrounding Planet MoFo's use of this map. Originally, the map was designed for use on more conservative servers, however the map was hosted on a server network known for its liberalism. This was thought by some to be inappropriate, but the hosts and the author have since come to an agreement over its use and modification.

[[Category:Maps]]
[[Category:CTF Maps]]
[[Category:2 Team Maps]]

Passion

2012-02-01T05:23:42Z

L4m3r: /* April Fools */

The 'Passion' map (previously known as 'christ.map'), was a popular map hosted by the group [[PlanetMoFo]] and other servers for some time. It is so called because when displayed on the list server, MoFo will title it as "Planet MoFo: The Passion Of The <game mode>". It has undergone constant modification and change since its introduction, though every incarnation of the map has been of the same general format:
* A three tiered central "cake" with crosses on the top, and tunnels running through the middle.
* Outer [[box|boxes]] at the corners and in the middle of the sides. The corner boxes can be substituted for bases and have flat pyramids above them.
* Two smaller [[pyramid|pyramids]] in each quarter of the map.
* [[teleporter|Teleporters]] on the outer [[box|boxes]]. Which outer boxes have [[teleporter|teleporters]] depends on the game mode.

==Map History ==
=== Early map ===
[[Image:Christ.jpg|thumb|right|Christ.map]]
The map was originally known as "christ.map" designed by Ducatiwannabe. This looks somewhat different from the current map, though the basic features are still recognizable.

=== "Classic" Passion ===
[[Image:classicmofo.jpg|thumb|right|Classic Passion map]]
This bears more resemblance to the map played on the sever now. The characteristic "MoFo in the sky" was added, as well as flat pyramids over the bases, more outer boxes and more pyramids.

The flat corner pyramids have developed into a well-known camping spot for guided missiles.

=== Current Map ===
[[Image:Moforabbit.jpg|thumb|right|Current Passion map in rabbit hunt mode.]]
The current map has been re-made using 2.0 objects, and is now almost completely [[mesh]]. The center cake has been changed to look more '2.0', with the slight change in its shape, as well as the Planet MoFo FFA logo on the side and an Oscillation Overthruster camping spot. There were also further minor changes to the map in general. It is currently in its second revision.

==== Billboards ====
In early 2007, billboards were introduced to display informative and amusing messages and pictures. They have been a great success since their launch, and Planet MoFo currently offer slots on the billboard rotation for those that have donated to the server. An archive of all the billboard images can be found at http://cbg.bzflag.org/images/billboards/

== Variations==

The map has been edited to cater for all the major game styles, as well as some of the less popular ones, such as [[HTF]]. Other than these, there have been several other maps based around the original.

=== L4m3r's Re-work ===

This was one of the first attempts at 2.0izing the original map, and was popular for some time. The crosses on the central cake were modified to be slanted, and the middle section of the cake was drivethrough. The 'MoFo in the sky' was modified to be a mesh and flashed red and black.

=== Passion of the Polygon ===

Another map made by L4m3r. This map is entirely hexagonal, and everything in the map is similarly hexagonal.

=== Passion of the 3-way ===

Two triangular passion maps were made, one by Spazzy McGee, the other by L4m3r. They both triangulated most objects, though in l4m3r's version, meshed skins were applied to the bases to make them triangular. In Spazzy McGee's they remained square.

=== April Fools ===

Amusing Passion variants are sometimes designed for April Fools' Day.

One year, L4m3r constructed a "Tiny-Huge Passion", inspired by "Tiny-Huge Island" from ''Super Mario 64''. It was actually two copies of the standard Passion, one at 150% scale, and the other at 75%. The two Passions were connected only by their teleporters and set far apart in the game world, making it difficult to see one section from the other. The result was that players would travel through a teleporter to unknowingly arrive in the corresponding location of the other map, creating the illusion that the map had suddenly become much smaller or larger.

On April 1st, 2007, The MoFo team revealed a Hell-themed map which featured several changes. The usual "MoFo in the sky" was replaced with a giant pentagram, and the pyramids were made to spin. In place of the corner boxes were large, lopsided pyramids with flat sections cut out near ground level. The outer walls were removed, and the charcoal-colored ground was made "finite" in appearance, only extending a small distance outside the map boundary. Outside, a cylindrical wall of spinning, rising flames was added. This made the entire map appear to be spinning and falling through fire, as if into Hell; many players and a few of the MoFo admin team complained that the decoration made them feel disoriented when they tried to play. The added ricochet in the corner areas, removal of GM camping areas above the corners, and lack of outer walls also altered the map's usual gameplay.

=== The Inversion ===

Made by Spazzy McGee, this is the normal map, but instead of blocks, everything is inverted as holes in the ground.

=== MoFo Garage ===

A map by Sir_Pants that has a large car-park like structure below it.

=== Two Storey MoFo ===

Recently re-vamped, this map by Sir_Pants is similar to MoFo garage, but is much more playable. Among the added features were the second story beneath the main play area, and jump pads to go from the lower to top level. It is designed to be a 2-team CTF map, and Sir_Pants recommends the removal of the SW flag when playing this map.

=== Mammoth ===

This is a huge map with five cakes. It's basically four standard passion maps plugged together. It only really works with lots of players, but can be quite an interesting battle, since there are so many places to hide.

=== Epileptic Fit ===

A-Delusion's [[TextureMatrix]] 101.

=== Halloween Edition ===

For halloween 2007, the Planet MoFo team devised several draw-info animations objects, such as bats, dancing skeletons, and spiders. The map was also given a full texture makeover, with rotten wood and stone textures replacing the standard bricks. The map was received well, and is one of the few examples of where drawinfo code has been utilized in a successful map.

== Controversy ==

There has been some controversy surrounding Planet MoFo's use of this map. Originally, the map was designed for use on more conservative servers, however the map was hosted on a server network known for its liberalism. This was thought by some to be inappropriate, but the hosts and the author have since come to an agreement over its use and modification.

[[Category:Maps]]
[[Category:CTF Maps]]
[[Category:2 Team Maps]]

Known Cheats

2008-03-07T08:34:28Z

L4m3r: /* Blatant Cheats */ Instant spawn (no spawn delay) has been fixed

Cheats performed on BZFlag are usually made by modifying your client. A great deal of power is invested in the client program, and therefore the client may cheat in every way from creating invincible tanks, to invisibility, to super killing. If you have seen any cheats, have performed them yourself, or have noticed a hole in the source, please add it here. Preventions for many of these cheats are being developed for inclusion in [[BZFlag 3.0|v3.0]].

== Warning ==
Do not use a modified client on a public server. If you are found to be using a cheat client, you will likely be banned from multiple servers and could quickly find yourself with nowhere to play. Cheating in BZflag is not the same as using a cheat code in a PlayStation game. See also the ''Notes on "CHEAT" servers'' at the bottom of the [[BZFlag_README | README]], which forbid the hosting of a "cheat" server. A copy of the README is included with the source code and is displayed when you install a pre-compiled copy of the game.

== Blatant Cheats ==
The following cheats are considered "blatant" cheats because they are usually apparent, even to new players.

NOTE: Some of these cheats may be prevented in certain versions of BZFlag.

A cheater may:

* fly without Wings.
* steal from or give flags to other players.
* give flags to observers.
* rapidly pickup and drop every flag on the map, as if a flag reset were performed.
* spawn with a flag (usually Guided Missile or Genocide, but can be anything).
* not respond to bad flags.
* grab a new flag when passing through a teleporter (when no flag exists).
* move, pickup flags, or shoot other tanks while paused.
* move through buildings without Oscillation Overthruster ("wall walking").
* move backwards through buildings with the Oscillation Overthruster.
* drive outside of the playing area.
* "drag 'n drop", moving from any location to any other at any speed.
* jump back briefly to avoid a bullet then return to where you were ("network jitter").
* double jump.
* instantaneous travel to a new location.
* jump and land at a pre-determined set of coordinates (i.e. the center of a team pad).
* shoot teammates without blowing them up.
* shoot bullets that travel at a different rate (usually faster).
* shoot bullets that travel at impossible linear paths (i.e. downwards, sideways).
* fire multiple shots simultaneously, often in spreads & separate impossible paths.
* shoot bullets which cannot be seen on radar or in the HUD.
* produce abnormally long laser blasts (in terms of length and time).
* be zoned, but yet still shoot tanks that are not zoned.
* cause the bullets of other tanks to explode prematurely.
* lock onto stealthed players while using Guided Missile.
* produce abnormally large, small, or frequent shockwave blasts.
* produce shockwaves at several locations simultaneously.
* respond differently to gravity.
* move at a different rate (usually faster).
* instantly self-destruct.
* be completely invincible ("god mode").
* be partially invincible, repelling everything but some particular flags (often SW or SR are chosen).
* instantly kill everyone else.
* be joined as an observer, but playing with a visible, invincible tank

== Subtle Cheats ==
'''Subtle cheats''' are modifications to the BZFlag client that give the user an unfair advantage. Unlike the obvious "blatant" cheats, these modifications are often difficult to detect by other players. These modifications often involve small changes to existing source code, and will make their users appear luckier, more intuitive, or more accurate shooters, giving them a slight edge.

Some of these cheats may be detected by examining long-term player statistics. For example, if a specific player picks up a certain superflag 80% of the time over an extended period, on a map where flag positions are completely randomized, then there is strong reason to suspect the player of using a flag identification cheat.

The following is a list of known subtle cheats:

[[Image:Bzfi0002.png|thumb|A screenshot taken on a typical cheat client. Various modifications and enhancements are visible.]]
[[Image:Bzfi0008.png|thumb|A second screenshot taken on the same hacked client as above (but on a different computer).]]

;FlagColoring
:Flags are given unique colors (or some other identifying feature - colors are simplest). This can be applied to some, or all flags. For example, bad flags are brown, Shock Wave is cyan, Stealth is orange, Guided Missile is pink, etc. This allows the user to avoid bad flags, spot good flags from across the map, and tell what flags other players are carrying or picking up much more easily.

;RadarPath
:The player can see bullet trajectories at an extended length, making shots easier to avoid, or aiding with targeting. The latter function is used mostly on ricochet maps.

;StealthDetect
:The player can see stealthed tanks on the radar. Often times the cheater's client will flash the stealthed tank on the cheater's radar. This allows a cheater to know that he shouldn't be able to know that tanks position and allow him to "play dumb".

;CloakDetect
:The player can see cloaked tanks on the field. Often times the cheater's client will show cloaked tanks as phased tanks (as if holding the PZ flag).

;DisableBadFlags
:Bad flags whose effects are invisible to other players are disabled from affecting the tank.

;NoGenocide
:A teammate is impervious to Genocide.

;FunnyBullet
:Various cheats that affect the manner in which bullets are fired are possible. The simplest is to increase bullet velocity. Other cheats include launching multiple bullets in different directions and giving bullets a vertical slope. Many of these cheats are less subtle, and discussed above.

;SkinnyTank
:Normally, if your aim is a little bit off, you can still kill a tank. When this cheat is in effect, other players have to aim more accurately to kill the user.

;ImprovedConsole
:The player's console provides more information than is normal. It's debatable whether this should be considered a cheat or not, but players with better consoles will have a slight advantage.

;GuidedMissileWontUnlock
:When the user is killed, his guided missiles remain locked on their targets. This is harder to detect than a Guided Missile being able to lock onto stealthed players, which is discussed above.

[[Image:Bzfi0001.png|thumb|A hacked client equipped with the ProgressiveIdentify cheat. One flag has been identified so far.]]

;BulletFreeZone
:Any player in the game can cause anyone else's bullets to explode prematurely (if their client is hacked). Here are a few possible effects:
:# A victim (or victims) will not be able to fire his weapon (bullets will explode shortly after leaving the muzzle). Others can't tell who is causing this.
:# Bullets will explode before hitting a cheater, as if the cheater has a forcefield.
:# Bullets will explode before hitting a "victim" who is not the cheater, creating the impression that the victim has a forcefield and is cheating. Or the cheater could create the impression that a whole group of tanks are cheating.
:# Bullets will not be allowed to enter a "bullet-free zone" (such as a building or platform).

;TinyCloak
:The cheater's tank is modified to be smaller and harder to hit, but only when carrying the Cloaking flag. Making a tank this hard to hit would be a blatant cheat if the tank wasn't cloaked.

;ProgressiveIdentify
:A variation of the FlagColoring cheat. The client holds the identity of each flag in memory whenever it is picked up by any player and displays the flag type on the cheater's HUD.

== Other Malicious Activities ==
The following is a list of malicious activities that cheaters might also engage in:

* stall or restart servers.
* promote themselves to server administrator and give large bans and kicks.
* change variables without polling successfully or being an admin.
* attempt to guess or "crack" the server or map's password.

[[Category:Server Security]]

Ideas

2008-01-31T20:42:47Z

L4m3r: /* Technical */

{{Old}}
NOTE: These are just possibilities. We won't be implementing everything here.<br>

Commentary may include personal comments by developers.

= Editing this page =

Feel free to make changes and updates to this page whenever possible. If you have any questions, feel free to [[Getting Help|ask for help]]. If you wish to make major changes to this page (i.e. remove large amounts of old ideas), please warn us ahead of time.

== Adding ideas ==
* Please remember to make sure your idea isn't already here or on the [[Rejected Ideas]] page.
* Flag ideas should be placed on [[Flag Ideas]], not here.
* Add a row to the appropriate category (at the bottom, please) and fill it in with your idea.
* Sign your idea in the third column with three tildes: <nowiki>~~~</nowiki>
* Put the submission date in the fourth column
* Describe in full and make sense!
* Leave the status column white and fill it with (Unknown).

== Adding commentary ==
* Precede your comment with an asterisk: <nowiki>*</nowiki>
* Sign your comment with four tildes: <nowiki>~~~~</nowiki>
* Be nice, polite, and constructive.
* Contribute something when you comment. Saying whether or not you like an idea is pointless if you don't explain yourself.

== Cleaning up ==
To help keep this page current, old ideas should be removed when they're implemented (after each stable release, hence the "SVN" status). If you spot any ideas that were implemented prior to the latest stable release of BZFlag, please remove it.

= The list =
<div align="center">
{| cellpadding="10" cellspacing="1" border="1"
|+align="bottom"|''Legend''
|-
|style="background-color:#FF00FF;"|'' ''
|Implemented as a server-side plug-in
|-
|style="background-color:#0080FF;"|'' ''
|SVN (Implemented and will be in next release)
|-
|style="background-color:#00FFFF;"|'' ''
|In progress (Implementing)
|-
|style="background-color:#00FF00;"|'' ''
|Good Idea
|-
|style="background-color:#808080;"|'' ''
|Idea
|-
|style="background-color:#FFFF00;"|'' ''
|Vague, not understood, or in need of work
|-
|style="background-color:#FF8000"|'' ''
|Rejected, but can be implemented as a server plug-in
|-
|style="background-color:#FF0000;"|'' ''
|Rejected
|-
|style="background-color:#FFFFFF"|'' ''
|Unknown (new)
|}
</div>

== General/Gameplay ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Add support for 5 (or more) button mice
|style="background-color:#00FF00;"|Great Idea
|
|(Unknown)
|(Old)
|-
|Better physics
|style="background-color:#00FFFF;"|In progress
|
*Planning, some changes in CVS.
|Unknown
|(Old)
|-
|SELF-DESTRUCT BLAST RADIUS: Self Destruct (delete key) should have a blast radius similar to Shock Wave, perhaps larger. If you get shot during the self-destruct count down, that should also trigger the same blast. If I gotta go, I want to take someone with me.
|(Unknown)
|
|BearRiver
|(Old)
|-
|3-second (or however long) 'invulnerability' for incoming tanks - but they can't shoot
|style="background-color:#808080;"|Idea
|
*I could see this backfiring... your spawn attracts opponents to come, wait, and blast you when you lose invincibility. -L4m3r
|MORPH
|(Old)
|-
|Ability to turn off ricochet for laser flag but allow ricochet for bullets... or let them bounce only n times.. OR implement mirror buildings/walls. Should go for some interesting self-kills when combined with the no-radar/bullet bounce
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Smart LockOn for GM - won't lock on to your teammates (configurable in server)
|style="background-color:#808080;"|Idea
|
*I don't like this idea, there should be at least *some* risks to using this weapon. Personally, I think there should be more (not fewer) risks to holding this weapon; I'd like to see the thing overheat and explode (killing the holder) if it's fired too often in a short period of time. -M. Jetleb

*2.99 has an option to disable friendly fire altogether. Close enough. Lock-on could still be looked into, however. [[User:L4m3r|L4m3r]] 01:38, 5 January 2008 (EST)
|MORPH
|(Old)
|-
|Small jumps
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Server option for genocide flag - if you're killed while you have it, your team dies :^)
|style="background-color:#808080;"|Idea
|
*Feasible with a plug-in, too. -L4m3r
|MORPH
|(Old)
|-
|for broadband or LAN connections - voice chat for teams
|style="background-color:#808080;"|Idea
|
*I really think that you can do this with another service; I'm not sure if being part of BZFlag would be a good idea due to size and bandwidth issues.
|MORPH
|(Old)
|-
|Tank avatars (uploadable tank images) - have to think about shapes, though - someone could make a 1x1x1 pixel tank - that would suck - or a tank that looks like a building or pyramid. Clients don't have to accept downloading of avators (just view other tanks in default mode). Or just s-e-l-e-c-t from a certain number of predefined avatars that could come with the bzflag distribution. Or client provides a URL to download their avatar (saves server bandwidth).
|style="background-color:#808080;"|Idea
|*Might not be implemented. Requires discussion; we may want to consider making the computer force a minimum size or something similar.
*How about uploadable flag graphics?
|MORPH
|(Old)
|-
|'Kamikaze' option for players - can take someone out by suicide
|style="background-color:#808080;"|Idea
|
*Server option if implemented.
*Implemented with a plugin by Theme97
|MORPH
|(Old)
|-
|Server option: everyone is radar-stealthed by default unless you get a 'radar' flag. You can still see all buildings, pyramids, teleports, and arena walls, though.
|style="background-color:#00FF00;"|Good idea
|
*Make them use their window. ;)
*Given the fairly narrow field of view out the window and the time it takes to turn a tank all the way around for a look-see, I think this could be frustrating. How about everyone starts out with minimum range radar instead and gets longer ranges with an appropriate flag? -M. Jetleb
*Ideally this could be implemented in the same manner as jumping and ricochet- radar could be enabled by default, or available as a flag. [[User:L4m3r|L4m3r]] 01:38, 5 January 2008 (EST)
|MORPH
|(Old)
|-
|Option for above: if you pick up GM or Laser, you're visible on radar to everyone whether they've got a radar flag or not
|style="background-color:#00FF00;"|Good idea
|
|MORPH
|(Old)
|-
|Selectable 'ricochet' fire - hold down shift key or something and your bullets won't ricochet
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Server option - tanks only have a certain number of times they can jump (gets reset when you get killed)
|style="background-color:#808080;"|Idea
|
*Could be made possible with a plug-in in 2.99. [[User:L4m3r|L4m3r]] 01:38, 5 January 2008 (EST)
|MORPH
|(Old)
|-
|Multiple-shields (server option for shield flags, or can be random - can get hit x number of times)
|style="background-color:#808080;"|Idea
|*This is pretty much moot now. It's been shot down by the devs at least once, and a similar effect can be achieved by setting _shieldFlight to a very small number. This effectively provides as many hits as _maxFlagGrabs. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|Configurable 'radarless' and/or 'blind' zones in the arena - can't see what's in there on radar or via visuals
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Tank collisions - why can tanks drive through each other? Weird.
|style="background-color:#00FF00;"|Good Idea
|*Lag could be a big problem here. If implemented, it must be impossible for two tanks to get stuck to each other. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|When tanks collide - great opportunity to implement tank damage concept, especially if one of them is moving especially fast, or has momentum flag, etc. Can push a tank off a building if your pushing them from their side.
|style="background-color:#808080;"|Idea
|
*Tank damage won't happen, but the kinetics could be neat, especially for mid-air collisions. It would certainly make "jump dancing" more interesting. [[User:L4m3r|L4m3r]]
|Morph
|(Old)
|-
|If a tank explodes right next to another tank, the other tank can be destroyed or get damaged
|style="background-color:#808080;"|Idea
|
*Somewhat implemented with the [[ShockwaveDeath]] plug-in. It would probably not be too hard to implement something similar (with a plugin) without shockwaves. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|Skins or views- In-tank mode, bumper mode, out-of-cab mode, chase mode.
|(Unknown)
|
|MORPH
|(Old)
|-
|Weapon extension packs.
|style="background-color:#FFFF00;"|(Unknown)
|*Huh? Explain, please. [[User:L4m3r|L4m3r]]
|iPod
|(Old)
|-
|The ability to choose tanks, but they all die at one shot. maybe the jump height, speed, turn speed, acceleration, size can be preset.
|(Unknown)
|
*Could be done with a plug-in in 2.99, maybe. [[User:L4m3r|L4m3r]] 01:38, 5 January 2008 (EST)
|iPod
|(Old)
|-
|Option to choose different kinds of tanks. Different tanks could be weighted with different strengths and weaknesses. (almost like having a default flag). Would also need some form of health/damage status measurement, not just single hits. For example, there could be a larger, heavily armored tank that has powerful weapons, but moves slowly, versus a small, light, fast tank which is difficult to hit, but very low armor to protect from hits.
|(Unknown)
|
|Cue
|(Old)
|-
|What about a radar that only covers visible areas (don't passing through buildings/pyramids) ? This would leads to more placement tactics).
|(Unknown)
|
|K<nowiki>'</nowiki>limero
|(Old)
|-
|Always random respawn. Currently in CTF games first respawn is at own base. This can be abused by leaving and rejoining to get near base. This leave/rejoing trick is considered to be a mild form of cheating by many. Always random respawn would make it useless.
|(Unknown)
|
* I believe there is a plug-in for this. [[User:L4m3r|L4m3r]] 22:38, 30 April 2007 (EDT)
|abli
|(Old)
|-
|multiple (3?) jump stengths mini, normal, max...just the thing to confuse the opponents that expect one and you're off doing the other.
|(Unknown)
|
|kitchen
|(Old)
|-
|Anti camping. The ability to add "no camping zones" to areas of a map or to the entire map. Campers would be messaged that they're in a no camping zone, better start moving and have a prescribe number of seconds to move away or die. If a player returns to the same NCZ (no camping zone) and receives x warnings then he's disconnected. NCZs could be marked by a different color shade from a "normal" spot and could be exempt to a single team (like at their flag base). It's just a rough idea.
|(Unknown)
|
*Definitely more suited to a plug-in (and probably doable, too).
|pherris
|(Old)
|-
|Shield Flag Changes: Give Shield flag a radius, and draw it like a moving less opaque blue shockwave. Any tanks inside the shield radius would be protected, until the shield got hit a certain number of times.
|(Unknown)
|
|YHARG
|(Old)
|-
|At our company, we instituted a voluntary policy of dropping flags after 1 kill. Prevents slaughters and keeps things rolling more. It'd be great to be able to have the game do this for us, plus I'd love to see it turned on at external sites.
|(Unknown)
|
|TomMatelich
|(Old)
|-
|Server option: default powers -- flag(s) that everyone in the game automatically has (this wouldn't count as holding a flag). For example, the current Jumping option would == including Jumping as a default power.
|(Unknown)
|
|NebNamwen
|(Old)
|-
|Shot Aiming. Basically the center shot aim box could be moved left and right as far as the edge of the view window. (This would be enabled by default.) If the map is a vertical one a server option could be enabled so that vertical aiming could be enabled (using the same concept as horizontal aiming.) The aiming would be automatically centered by a button or key. These options could be mapped to a second joystick access, mouse scroll wheel or keyboard buttons.
|(Unknown)
|Lateral shooting would basically be the same as a rotating turret, and this idea has been shot down many times. Vertical shooting has been poo-pooed also. [[User:L4m3r|L4m3r]] 01:45, 3 July 2007 (EDT)
|NN
|6/20/07
|-
|Make a tele porter along the game sides that would tele port into other games running on their own servers. This would enable larger more collaborative game board linked together that would distribute loads across multiple servers speeding up game play and making for interesting possibilities.
|(Unknown)
|
|Waban*
|7/31/07
|-
|Make a 'fog of war' where the a player's radar only shows a certain distance of the area around them and their teammates'.
|(Unknown)
|
*This could be done if radar and position data were separated, allowing the server to "filter" radar data for each player.
|Forrest
|8/19/07
|}
</div>

== UI ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Make option to show previous players list
|style="background-color:#808080;"|Idea
|
|(Unknown)
|(Old)
|-
|Make ALL server options available from the menus
|style="background-color:#808080;"|Idea
|
*There are a LOT of server options, and this could add quite a bit of clutter. If you need more than a basic game, you should probably learn to start BZFS from the command line anyway. -L4m3r
|MORPH
|(Old)
|-
|Separate windows for player messages & server messages
|style="background-color:#00FF00;"|Good idea.
|
|MORPH
|(Old)
|-
|Message log
|style="background-color:#00FF00;"|Good idea.
|
|MORPH
|(Old)
|-
|Send message to everyone 'but' specified player (crosses team boundaries, or not)
|style="background-color:#808080;"|Idea
|
*Hmm. Everybody BUT a specified player? [M. Jetleb -> as in: "Let's all get the GM guy" without the GM guy knowing he's facing a co-ordinated attack - I like this idea)
|MORPH
|(Old)
|-
|The ability to see what the world is like before connecting to the server.
|(Unknown)
|
|iPod
|(Old)
|-
|Multi-monitor support (i.e., radar on one screen, window on another, chat/event log on a third)
|(Unknown)
|
|bhtooefr
|(Old)
|-
|Make a part in bzflag to put up a real server. 1st screen has the flags you want, next page is to find the MAP file that you created on your hard drive, next page pick if you want jumping etc.
|(Unknown)
|
|Colin
|(Old)
|-
|-
|Add a rear view mirror
|(Unknown)
|
|Sparky1
|1/1/2008
|-
|}
</div>

== Technical ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Better network handling
|style="background-color:#00FFFF;"|In progress
|
|(Unknown)
|(Old)
|-
|Better robot AI
|style="background-color:#808080;"|Idea
|
*Don't know if players would like it or not in multiplayer game. Pluggable or scriptable robot AI , maybe? - Code must be restructured first
*Server side bots are coming! [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT)
|(Unknown)
|(Old)
|-
|Better positioning of tanks
|style="background-color:#808080;"|Idea
|
*BZFlag already does this, but the algorithm is bad. Needs work.
|MORPH
|(Old)
|-
|Serious multithreaded design - shouldn't lock up interface while looking for servers, or doing anything else. This program is way-unstable on Windows
|style="background-color:#00FFFF;"|In Progress
|
*We're working on these problems; many complaints are due to people still using old servers/clients.
|MORPH
|(Old)
|-
|Some type of BZFlag GUID* to ban players who cheat - won't accept players who disable their GUID, etc.

<nowiki>*</nowiki>Global Unique Identifier, sort of like an IP addrss, but permanent. Usually a number. Problem occurs when you lose your GUID (have to reformat your HD, etc. How do you keep someone from hacking their GUID, or setting up a modified BZFlag server for identity theft, etc.
|(Unknown)
|
*I doubt this is even possible, let alone practical. What about people who play from more than one location? And, because this is an open-source game, it would probably be cracked in minutes. Any verification can be spoofed, or at least altered. there is no foolproof way to permanently ban someone. -L4m3r
|MORPH
|(Old)
|-
|To prevent cheating - the server determines what flags & abilities each tank has (possible?)
|style="background-color:#00FFFF;"|In Progress
|
*Seriously being considered. This would also have the advantage of allowing different versions of clients and servers to work together. Yes, it's possible, but this type of change will mean a change in the network protocols.
*Being worked on for 3.0
|MORPH
|(Old)
|-
|BZFlag for mac in separate data and application files.
|(Unknown)
|
|iPod
|(Old)
|-
|J2ME client (allows one to play on a cell phone), would use radar
|(Unknown)
|
|bhtooefr
|(Old)
|-
|Special 'open source' BZFlag version (server and client) which is guaranteed to be compatible with all other BZFlag versions.
|(Unknown)
|
*BZFlag is already open-source, and making a universally-compatible client is not even remotely practical. Incompatibility is part of why the game breaks off new versions in the first place. [[User:L4m3r|L4m3r]]
|Orca
|(Old)
|-
|}
</div>

== Game Modes, Team Play, and Scoring ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Tounament mode
|style="background-color:#808080;"|Idea
|
*Great Idea?
|(Unknown)
|(Old)
|-
|When you shoot someone on your own team, instead of both of you blowing up, neither is destroyed, and their score goes up one, while your's goes down one. This would make teamkilling impossible and greatly discourage traitors as well.
|style="background-color:#808080;"|Idea
|
*But then couldn't cheaters spawn two clients and ramp up their scores by teamkilling their other login? --YHARG
|Trigger Happy Nerd
|(Old)
|-
|A new gameplay mode- Takes two to tank. One to control the (rotating) turret, the other drives. KIA switches positions. "Teamplay" but all in one tank.
|(Unknown)
|
*I see serious lag issues with this... How does Halo do it? ;) -L4m3r
*The main problem with this idea is coordination. If one person were to leave, the tank would be crippled. You COULD solve this by having the person switch to normal mode, but this could cause considerable jerking between modes on a busy server. [[User:F687s|F687s]] 22:13, 20 June 2007 (EDT)
|MORPH
|(Old)
|-
|Turret mode, If enabled by the server (Can be manditory with automatic grouping). One user drives and the other shoots, Turret mode tanks get double points (But onyl take one from the target). lost double points if killed. Have double ammo, And controllable speed (Max = _tankSpeed * 2 Min = _tankSpeed). Plus it takes 2 shots to kill a turret mode tank. Points gained and lost by turret tanks are divided evenly between the users, Unless the server is all turret mode, in h which case two users are displayed as one.
|(Unknown)
|
|Dogbert
|(Old)
|-
|Ability for a team to vote to 'banish' someone from their team
|style="background-color:#808080;"|Idea
|
*Possibly unfair to newer players. [[User:L4m3r|L4m3r]]
*Useful for getting rid of TKers and selfcappers. However you would need a way (e.g. a voting system) and you would need to be able to say to which team he or she should go if rogues are unavailable. Possible, if rogues are allowed, but not otherwise not really a good idea. --[[User:88.108.209.168|88.108.209.168]] 13:13, 24 December 2007 (EST)
|MORPH
|(Old)
|-
|There should be a game of cops and robbers. The teams can change after about 10 mins or so.
|style="background-color:#FFFF00;"|(Unknown)
|
|iPod
|(Old)
|-
|A special FFA Game mode "Team by Flags". This means, same Flag = same Team, so if there is a Tank with Rapid fire, and you pick up Rapid fire, you are automatically handled as Team member (this means, killing the other Tank with Rapid fire will be handled the same way as when killing a team member). YHARG: Funky idea: what about a game mode where teams shared flag abilities? Like, each player on a team's flag applies to the whole team. This could make for some interesting combos...
|(Unknown)
|
|Agonizer
|(Old)
|-
|Make life trickier for the Rogue Team; with a mix of Rogues and Colored Teams, the Rogues have more targets. This should also change the effect of the Masquerade flag - perhaps your tank is invisible to Rogues (like Cloaking)?
|(Unknown)
|
|NickGrim
|(Old)
|-
|A server option to make deaths not affect your score unless they were self-inflicted/team (the method used by many online games). This would encourage more aggressive play, because it's worth going out and blasting. As it is, you've got a very good chance by just phantoming/OOing out of the way and keeping you score at zero to stay in the top three places! It would also help fix the rather unfair situation of spawning just below a building on which someone is GM-camping...there's pretty much no way to escape, so you lose a point.
|(Unknown)
|
|LionsPhil
|(Old)
|-
|Don't show individual score in CTF games. This might help teamplay as it reduces the incentive to run around as if it would be FFA.
|(Unknown)
|
|abli
|(Old)
|-
|Give points to the player how captures flag in CTF. (Say, around 4 or so) After all, it is often a bigger job than killing someone.
|(Unknown)
|
*Maybe the score could be based the number of tanks in the other team, similar to shooting someone w/ geno. This can also discourage people from capturing thier own flag by scoreing the negative number of teamates. I'm not sure if the individual scores of the players of the captured team (other than the one who captures the flag) should be affected however. [[User:Sparky1|Sparky1]] 09:44, 21 May 2007 (EDT)
*Scores can be customized with plug-ins in 3.0. Unfortunately, there's a bug in 2.0.x that prevents the server from setting scores properly. [[User:L4m3r|L4m3r]] 01:46, 5 January 2008 (EST)
|abli
|(Old)
|-
|Ducati/Freestyle "Roles" mode: Make a game mode where players are presented with a list of flag choices (limitable to a few roles, if wanted) at respawn or connect time, and are forced to use this flag for the remainder of their connection/tank life. This would be really useful in the case of stealth vs. seer, where you could choose to be stealth or seer, but couldn't switch between them. Another idea would be high speed vs. quick turn. Or steamroller vs. machine gun... Team play would have the interesting effect of people banding together and people with each role on the team. Especially in stealth vs. seer, where a seer team member could warn the team about enemies! There would be no team flags/bases.
|(Unknown)
|
*Too specialized, use a plug-in (yes, it's possible). [[User:L4m3r|L4m3r]] 01:46, 5 January 2008 (EST)
|YHARG
|(Old)
|-
|New game called tag were someone is it and they shoot someone else and there it and ect.
|(Unknown)
|
|Supermatthew
|(Old)
|-
|Also a new game called "Hide and seek" were everyone is clocked(think thats it, were you don't see them on radar) except one who is it. he needs to find someone and shoot them then hese cloked and who was shot is not. Also when someone is shot there sent back to Ground zero( 0X, 0Y, 0Z ) so they can't shoot who ever just shot them.
|(Unknown)
|
|Supermatthew
|(Old)
|-
|"Cat" game: when a player dies, he/she respawns automaticaly, after 3 secs or so. When they have respawned 9 times, they can no longer spawn, and are observers. The one who lasts the longest wins. Games are timed.
|(Unknown)
|
|(Unknown)
|4/20/2007
|-
|A switch-teams function that allows you to swap teams during a game without losing score.
|(Unknown)
|
|jftsang
|10/11/2007
|-
|Rogue team - A mode in which rogues may TK and capture flag.
|(unknown)
|
*Why? [[User:L4m3r|L4m3r]] 01:46, 5 January 2008 (EST)
|jftsang
|10/11/2007
|-
|A Sport Mode: I noticed that there is a lot of recently created cool sport maps. In those maps a team flag is used as a "ball", and bases are used as "goals". I think that there is even more potential for great maps if there would be a game mode where a bullet behaves like a "ball".In that mode when a game starts, or right after a score, a bullet hovers over a specified location (like the center of the map) and no one can shoot. The first tank that touches the bullet "has the ball", in other words only that tank can shoot. If a tank that "has the ball" shoots it, shooting for that tank is disabled, likewise, if a tank is shot by a bullet that tank does not die, but instead it "has the ball", this allows for passing and interception. A tank that "has the ball" should be indcated somehow, perhaps by a unique flag. The "ball" has the color of the last tank that shot it. A new object would have to be created (perhaps called a goal zone?) that resembles a teleporter that results in a ctf if a bullet encounters it. Or instead of a specific object an area/volume on the map could be designated as a "goal zone" which would give more freedom in designing objects that behave like goals. The score would go to the team that has the same color as the bullet that encountered the "goal zone". All tanks would have the Steam Roller power. a tank that touches another tank would not be killed only if that tank is higher at the touch. If a tank that "has the ball" is killed before he can shoot the "ball" then the bullet appears at the tanks position of death and travel at the speed and in the direction the tank had at that point. Maybe a provision could be made where the number of "balls" could be set at a number greater than one to allow for more complex games.
|(Unknown)
|
|[[User:Sparky1|Sparky1]]
|1/21/2008
|-
|}
</div>

== Maps, Mapping, and BZW ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Materials that don't allow OO and PZ to go through
|style="background-color:#808080;"|Idea
|
*Would be nice for multilevel worlds made with the new ability to have objects above the ground.
*Sounds awesome! TD-Linux 17:41, 12 March 2007 (EDT)
*As a special case, there could be Zoned objects (objects that only respond to PZ and maybe OO; normal tanks behave like PZ through these objects). [[User:Sparky1|Sparky1]] 18:05, 21 May 2007 (EDT)
*Would also be nice if there were non-ricochet materials, or only ricochet some shot type materials. --[[User:88.108.209.168|88.108.209.168]] 13:09, 24 December 2007 (EST)
|(Unknown)
|(Old)
|-
|Differently-shaped teleporters (circles, triangles, etc.)
|style="background-color:#808080;"|Idea
|
*probably low priority
|MORPH
|(Old)
|-
|360 degree teleports - hit a spot on the ground or in the air from any direction and you teleport
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Configurable random teleporters - teleports to a different location every time
|style="background-color:#808080;"|Idea
|
*Idea is a bit vague... randomized teles are implemented if you use multiple links. Is this what is meant by this suggestion? -L4m3r
|MORPH
|(Old)
|-
|Triggers in levels
|style="background-color:#FFFF00;"|(Unknown)
|
*Triggers for what? unless you're talking about AI, this could most likely be handled with a server plug-in. [[User:L4m3r|L4m3r]]
|Dragonstar
|(Old)
|-
|wraparound world - radar remains centered on your current position. Internally, objects leaving the north border reappear to the south, but from the user's radar / visible perspective, you just see to the horizon. I believe this is how the original Battlezone worked. There are some implications: laser would need a range limit.
|(Unknown)
|
|nsayer
|(Old)
|-
|As a generalization to the wraparound world concept, how about the option of making a map based on geometry that’s non-Euclidean, for example spherical or hyperbolic. Jumping/flying, the shape of the tanks/objects, and bullet trajectories would also be affected by this global geometry. It would be like a world that has a high gravitational field, or a world situated near a wormhole.
|(Unknown)
|
|[[User:Sparky1|Sparky1]]
|5/21/2007
|-
|-
|Get rid of the PZ flag and replace it w/ special telporters that do the same thing (they could be called "zoners", and should probably look different from regular teleporters). This way superflags, badflags, and team flags can all be zoned (without needing an exception to the restricition against using more than one flag at a time). The above idea of other zoned objects would play a major role here. Zoned flags can only be picked up by zoned tanks. Flags can spawn zoned, or become zoned by being carried by an unzoned tank that becomes zoned by going through a zoner. Likewise, a zonedflag becomes unzoned when a zoned tank carries it through a zoner. Unzoned tanks respond to shots from zoned flags the same way zoned tanks respond to shots from unzoned flags. For example: when zoned, L, WG, geno, and GM do not kill unzoned tanks (zoned GM will still lock onto any tank, and zoned geno would still kill every tank on the same team as the zoned tank that was shot). Although, flags like SW and SB would still kill any tank regardless of thier zoning status. As an extension to this idea one team in a CTF game could start out zoned, i.e. thier base is zoned and they initially spawn zoned. In order for the unzoned team to capture the zoned team's flag, the flag must become unzoned, and vice versa for the zoned team. This way new possibilities exist, like two bases could be superimposed as long as one base is zoned and the other is not. Another possible extension is different kinds of zones (w/ corespondingly different kinds of zoners) for CTF involving more than two teams. The relationship between differently zoned tanks would be the same as the relationship between zoned and unzoned tanks.
|(Unknown)
|
|[[User:Sparky1|Sparky1]]
|5/21/2007
|-
|Change the workings of zones such that a zone may have its own server variables (I wanted to make a Death Castle against a Holy Castle).
|(Unknown)
|
|jftsang
|1/12/2007
|}
</div>

== Server Options, Administration, Plug-ins, and the Plug-in API ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Ability to configure server to turn somethings off or on depending on number of players - for instance, turn off ricochet after a certain number of players are connected, turn off GM & laser if a certain number of players aren't playing (GM & Laser with 2 players is kinda ridiculous)
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Allow custom-made weapons with a Object-Oriented scripting language (sorta like Liero AI uses: http://helios.et.put.poznan.pl/~sskowron/liero/index.html )
|(Unknown)
|
|Dragonstar
|(Old)
|-
|Preset world weapons that can be fired manually by admins from within BzFlag.
|(Unknown)
|
* Could be done by a plugin [[User:Tanner|Tanner]] 13:42, 12 August 2007 (EDT)
|Dogbert
|(Old)
|-
|}
</div>

== Graphics & Sound ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Sounds of tanks moving.
|(Unknown)
|
|iPod
|(Old)
|-
|Have different tank death scenes for the dying tank point of view. I realize there is some time needed for one to die and respawn, but the jumping effect one sees when killed irritates me to no end! I'd be happier if all faded to black or white or orange and had text across the screen saying ""respawning... please wait"" :) Also, when killed and your tank was moving toward a building, it just falls right thru it until it hits the ground.. wrong physics there! Splatter or tumble or shatter or something :)
|(Unknown)
|
|Robi
|(Old)
|-
|Custom color schemes for rogue players. The turret and body components can be chosen to be one of a predefined set of colors (e.g. red, yellow, black, white, blue, green, purple...). The game prohibits choosing a color scheme that matches a team scheme (e.g. red turret with red body) and the limited set stops someone choosing a shade which is nearly a team color (e.g. 0xFE0000 instead of 0xFF0000) (and also save texture memory, I think).
|(Unknown)
| * Clients are able to define their own colors, and removing the ability to would cause accessibility issues (Colorblind users). --[[User:AAA|AAA]] 13:30, 7 August 2007 (EDT)
|LionsPhil
|(Old)
|-
|Allow a small decal on the back of the top of the tank. (think Half-Life's customizable spraypaint). Possibly also apply it to any held flag?
|(Unknown)
|
|LionsPhil
|(Old)
|-
|I'd like to see something more interesting done with the sky... maybe there could be a little ufo (easter egg) that would fly around occasionally? Tux on a ufo! ;)
|(Unknown)
| This is up to servers. --[[User:AAA|AAA]] 13:30, 7 August 2007 (EDT)
|YHARG
|(Old)
|-
|Flag decals: Each flag would have a little icon/decal showing it's type ONLY when held by a player. It's kind of nice to be able to surprise people with an undercover shockwave, but doesn't make sense to have to right click (identify) or check the user list to see what flag someone has.
|(Unknown)
|
|YHARG
|(Old)
|-
|Background music! : (This can be done with an external media player so it shouldn't be the heighest priority, It would be nice to be able to control your music from within BzFlag)
|(Unknown)
|More usefully, you could just map key combinations to commands, rather than wasting time supporting all the various music players on every OS BZFlag supports. I don't know whether that would work so well on Windows, though. --[[User:77.97.207.100|77.97.207.100]] 10:14, 30 May 2007 (EDT)
|YHARG
|(Old)
|-
|}
</div>

== List Server and Other Global Services ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Multiple list servers, in case bzflag.org goes down (as it happened around feb. 15. 2004)
|style="background-color:#00FFFF;"|In progress
| * Of course someone would need to pay for it. --[[User:BinarySpike|BinarySpike]] 18:10, 10 May 2007 (EDT)
* We now have two servers, and some form of redundancy for the list should follow eventually. [[User:L4m3r|L4m3r]] 15:40, 31 January 2008 (EST)
|abli
|(Old)
|-
|}
</div>

[[Category:Development]]

Ideas

2008-01-31T20:40:16Z

L4m3r: /* List Server and Other Global Services */ List server redundnacy -> in progress

{{Old}}
NOTE: These are just possibilities. We won't be implementing everything here.<br>

Commentary may include personal comments by developers.

= Editing this page =

Feel free to make changes and updates to this page whenever possible. If you have any questions, feel free to [[Getting Help|ask for help]]. If you wish to make major changes to this page (i.e. remove large amounts of old ideas), please warn us ahead of time.

== Adding ideas ==
* Please remember to make sure your idea isn't already here or on the [[Rejected Ideas]] page.
* Flag ideas should be placed on [[Flag Ideas]], not here.
* Add a row to the appropriate category (at the bottom, please) and fill it in with your idea.
* Sign your idea in the third column with three tildes: <nowiki>~~~</nowiki>
* Put the submission date in the fourth column
* Describe in full and make sense!
* Leave the status column white and fill it with (Unknown).

== Adding commentary ==
* Precede your comment with an asterisk: <nowiki>*</nowiki>
* Sign your comment with four tildes: <nowiki>~~~~</nowiki>
* Be nice, polite, and constructive.
* Contribute something when you comment. Saying whether or not you like an idea is pointless if you don't explain yourself.

== Cleaning up ==
To help keep this page current, old ideas should be removed when they're implemented (after each stable release, hence the "SVN" status). If you spot any ideas that were implemented prior to the latest stable release of BZFlag, please remove it.

= The list =
<div align="center">
{| cellpadding="10" cellspacing="1" border="1"
|+align="bottom"|''Legend''
|-
|style="background-color:#FF00FF;"|'' ''
|Implemented as a server-side plug-in
|-
|style="background-color:#0080FF;"|'' ''
|SVN (Implemented and will be in next release)
|-
|style="background-color:#00FFFF;"|'' ''
|In progress (Implementing)
|-
|style="background-color:#00FF00;"|'' ''
|Good Idea
|-
|style="background-color:#808080;"|'' ''
|Idea
|-
|style="background-color:#FFFF00;"|'' ''
|Vague, not understood, or in need of work
|-
|style="background-color:#FF8000"|'' ''
|Rejected, but can be implemented as a server plug-in
|-
|style="background-color:#FF0000;"|'' ''
|Rejected
|-
|style="background-color:#FFFFFF"|'' ''
|Unknown (new)
|}
</div>

== General/Gameplay ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Add support for 5 (or more) button mice
|style="background-color:#00FF00;"|Great Idea
|
|(Unknown)
|(Old)
|-
|Better physics
|style="background-color:#00FFFF;"|In progress
|
*Planning, some changes in CVS.
|Unknown
|(Old)
|-
|SELF-DESTRUCT BLAST RADIUS: Self Destruct (delete key) should have a blast radius similar to Shock Wave, perhaps larger. If you get shot during the self-destruct count down, that should also trigger the same blast. If I gotta go, I want to take someone with me.
|(Unknown)
|
|BearRiver
|(Old)
|-
|3-second (or however long) 'invulnerability' for incoming tanks - but they can't shoot
|style="background-color:#808080;"|Idea
|
*I could see this backfiring... your spawn attracts opponents to come, wait, and blast you when you lose invincibility. -L4m3r
|MORPH
|(Old)
|-
|Ability to turn off ricochet for laser flag but allow ricochet for bullets... or let them bounce only n times.. OR implement mirror buildings/walls. Should go for some interesting self-kills when combined with the no-radar/bullet bounce
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Smart LockOn for GM - won't lock on to your teammates (configurable in server)
|style="background-color:#808080;"|Idea
|
*I don't like this idea, there should be at least *some* risks to using this weapon. Personally, I think there should be more (not fewer) risks to holding this weapon; I'd like to see the thing overheat and explode (killing the holder) if it's fired too often in a short period of time. -M. Jetleb

*2.99 has an option to disable friendly fire altogether. Close enough. Lock-on could still be looked into, however. [[User:L4m3r|L4m3r]] 01:38, 5 January 2008 (EST)
|MORPH
|(Old)
|-
|Small jumps
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Server option for genocide flag - if you're killed while you have it, your team dies :^)
|style="background-color:#808080;"|Idea
|
*Feasible with a plug-in, too. -L4m3r
|MORPH
|(Old)
|-
|for broadband or LAN connections - voice chat for teams
|style="background-color:#808080;"|Idea
|
*I really think that you can do this with another service; I'm not sure if being part of BZFlag would be a good idea due to size and bandwidth issues.
|MORPH
|(Old)
|-
|Tank avatars (uploadable tank images) - have to think about shapes, though - someone could make a 1x1x1 pixel tank - that would suck - or a tank that looks like a building or pyramid. Clients don't have to accept downloading of avators (just view other tanks in default mode). Or just s-e-l-e-c-t from a certain number of predefined avatars that could come with the bzflag distribution. Or client provides a URL to download their avatar (saves server bandwidth).
|style="background-color:#808080;"|Idea
|*Might not be implemented. Requires discussion; we may want to consider making the computer force a minimum size or something similar.
*How about uploadable flag graphics?
|MORPH
|(Old)
|-
|'Kamikaze' option for players - can take someone out by suicide
|style="background-color:#808080;"|Idea
|
*Server option if implemented.
*Implemented with a plugin by Theme97
|MORPH
|(Old)
|-
|Server option: everyone is radar-stealthed by default unless you get a 'radar' flag. You can still see all buildings, pyramids, teleports, and arena walls, though.
|style="background-color:#00FF00;"|Good idea
|
*Make them use their window. ;)
*Given the fairly narrow field of view out the window and the time it takes to turn a tank all the way around for a look-see, I think this could be frustrating. How about everyone starts out with minimum range radar instead and gets longer ranges with an appropriate flag? -M. Jetleb
*Ideally this could be implemented in the same manner as jumping and ricochet- radar could be enabled by default, or available as a flag. [[User:L4m3r|L4m3r]] 01:38, 5 January 2008 (EST)
|MORPH
|(Old)
|-
|Option for above: if you pick up GM or Laser, you're visible on radar to everyone whether they've got a radar flag or not
|style="background-color:#00FF00;"|Good idea
|
|MORPH
|(Old)
|-
|Selectable 'ricochet' fire - hold down shift key or something and your bullets won't ricochet
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Server option - tanks only have a certain number of times they can jump (gets reset when you get killed)
|style="background-color:#808080;"|Idea
|
*Could be made possible with a plug-in in 2.99. [[User:L4m3r|L4m3r]] 01:38, 5 January 2008 (EST)
|MORPH
|(Old)
|-
|Multiple-shields (server option for shield flags, or can be random - can get hit x number of times)
|style="background-color:#808080;"|Idea
|*This is pretty much moot now. It's been shot down by the devs at least once, and a similar effect can be achieved by setting _shieldFlight to a very small number. This effectively provides as many hits as _maxFlagGrabs. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|Configurable 'radarless' and/or 'blind' zones in the arena - can't see what's in there on radar or via visuals
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Tank collisions - why can tanks drive through each other? Weird.
|style="background-color:#00FF00;"|Good Idea
|*Lag could be a big problem here. If implemented, it must be impossible for two tanks to get stuck to each other. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|When tanks collide - great opportunity to implement tank damage concept, especially if one of them is moving especially fast, or has momentum flag, etc. Can push a tank off a building if your pushing them from their side.
|style="background-color:#808080;"|Idea
|
*Tank damage won't happen, but the kinetics could be neat, especially for mid-air collisions. It would certainly make "jump dancing" more interesting. [[User:L4m3r|L4m3r]]
|Morph
|(Old)
|-
|If a tank explodes right next to another tank, the other tank can be destroyed or get damaged
|style="background-color:#808080;"|Idea
|
*Somewhat implemented with the [[ShockwaveDeath]] plug-in. It would probably not be too hard to implement something similar (with a plugin) without shockwaves. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|Skins or views- In-tank mode, bumper mode, out-of-cab mode, chase mode.
|(Unknown)
|
|MORPH
|(Old)
|-
|Weapon extension packs.
|style="background-color:#FFFF00;"|(Unknown)
|*Huh? Explain, please. [[User:L4m3r|L4m3r]]
|iPod
|(Old)
|-
|The ability to choose tanks, but they all die at one shot. maybe the jump height, speed, turn speed, acceleration, size can be preset.
|(Unknown)
|
*Could be done with a plug-in in 2.99, maybe. [[User:L4m3r|L4m3r]] 01:38, 5 January 2008 (EST)
|iPod
|(Old)
|-
|Option to choose different kinds of tanks. Different tanks could be weighted with different strengths and weaknesses. (almost like having a default flag). Would also need some form of health/damage status measurement, not just single hits. For example, there could be a larger, heavily armored tank that has powerful weapons, but moves slowly, versus a small, light, fast tank which is difficult to hit, but very low armor to protect from hits.
|(Unknown)
|
|Cue
|(Old)
|-
|What about a radar that only covers visible areas (don't passing through buildings/pyramids) ? This would leads to more placement tactics).
|(Unknown)
|
|K<nowiki>'</nowiki>limero
|(Old)
|-
|Always random respawn. Currently in CTF games first respawn is at own base. This can be abused by leaving and rejoining to get near base. This leave/rejoing trick is considered to be a mild form of cheating by many. Always random respawn would make it useless.
|(Unknown)
|
* I believe there is a plug-in for this. [[User:L4m3r|L4m3r]] 22:38, 30 April 2007 (EDT)
|abli
|(Old)
|-
|multiple (3?) jump stengths mini, normal, max...just the thing to confuse the opponents that expect one and you're off doing the other.
|(Unknown)
|
|kitchen
|(Old)
|-
|Anti camping. The ability to add "no camping zones" to areas of a map or to the entire map. Campers would be messaged that they're in a no camping zone, better start moving and have a prescribe number of seconds to move away or die. If a player returns to the same NCZ (no camping zone) and receives x warnings then he's disconnected. NCZs could be marked by a different color shade from a "normal" spot and could be exempt to a single team (like at their flag base). It's just a rough idea.
|(Unknown)
|
*Definitely more suited to a plug-in (and probably doable, too).
|pherris
|(Old)
|-
|Shield Flag Changes: Give Shield flag a radius, and draw it like a moving less opaque blue shockwave. Any tanks inside the shield radius would be protected, until the shield got hit a certain number of times.
|(Unknown)
|
|YHARG
|(Old)
|-
|At our company, we instituted a voluntary policy of dropping flags after 1 kill. Prevents slaughters and keeps things rolling more. It'd be great to be able to have the game do this for us, plus I'd love to see it turned on at external sites.
|(Unknown)
|
|TomMatelich
|(Old)
|-
|Server option: default powers -- flag(s) that everyone in the game automatically has (this wouldn't count as holding a flag). For example, the current Jumping option would == including Jumping as a default power.
|(Unknown)
|
|NebNamwen
|(Old)
|-
|Shot Aiming. Basically the center shot aim box could be moved left and right as far as the edge of the view window. (This would be enabled by default.) If the map is a vertical one a server option could be enabled so that vertical aiming could be enabled (using the same concept as horizontal aiming.) The aiming would be automatically centered by a button or key. These options could be mapped to a second joystick access, mouse scroll wheel or keyboard buttons.
|(Unknown)
|Lateral shooting would basically be the same as a rotating turret, and this idea has been shot down many times. Vertical shooting has been poo-pooed also. [[User:L4m3r|L4m3r]] 01:45, 3 July 2007 (EDT)
|NN
|6/20/07
|-
|Make a tele porter along the game sides that would tele port into other games running on their own servers. This would enable larger more collaborative game board linked together that would distribute loads across multiple servers speeding up game play and making for interesting possibilities.
|(Unknown)
|
|Waban*
|7/31/07
|-
|Make a 'fog of war' where the a player's radar only shows a certain distance of the area around them and their teammates'.
|(Unknown)
|
*This could be done if radar and position data were separated, allowing the server to "filter" radar data for each player.
|Forrest
|8/19/07
|}
</div>

== UI ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Make option to show previous players list
|style="background-color:#808080;"|Idea
|
|(Unknown)
|(Old)
|-
|Make ALL server options available from the menus
|style="background-color:#808080;"|Idea
|
*There are a LOT of server options, and this could add quite a bit of clutter. If you need more than a basic game, you should probably learn to start BZFS from the command line anyway. -L4m3r
|MORPH
|(Old)
|-
|Separate windows for player messages & server messages
|style="background-color:#00FF00;"|Good idea.
|
|MORPH
|(Old)
|-
|Message log
|style="background-color:#00FF00;"|Good idea.
|
|MORPH
|(Old)
|-
|Send message to everyone 'but' specified player (crosses team boundaries, or not)
|style="background-color:#808080;"|Idea
|
*Hmm. Everybody BUT a specified player? [M. Jetleb -> as in: "Let's all get the GM guy" without the GM guy knowing he's facing a co-ordinated attack - I like this idea)
|MORPH
|(Old)
|-
|The ability to see what the world is like before connecting to the server.
|(Unknown)
|
|iPod
|(Old)
|-
|Multi-monitor support (i.e., radar on one screen, window on another, chat/event log on a third)
|(Unknown)
|
|bhtooefr
|(Old)
|-
|Make a part in bzflag to put up a real server. 1st screen has the flags you want, next page is to find the MAP file that you created on your hard drive, next page pick if you want jumping etc.
|(Unknown)
|
|Colin
|(Old)
|-
|-
|Add a rear view mirror
|(Unknown)
|
|Sparky1
|1/1/2008
|-
|}
</div>

== Technical ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Better network handling
|style="background-color:#00FFFF;"|In progress
|
|(Unknown)
|(Old)
|-
|Better robot AI
|style="background-color:#808080;"|Idea
|
*Don't know if players would like it or not in multiplayer game. Pluggable or scriptable robot AI , maybe? - Code must be restructured first
*Server side bots are coming! [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT)
|(Unknown)
|(Old)
|-
|Better positioning of tanks
|style="background-color:#808080;"|Idea
|
*BZFlag already does this, but the algorithm is bad. Needs work.
|MORPH
|(Old)
|-
|Serious multithreaded design - shouldn't lock up interface while looking for servers, or doing anything else. This program is way-unstable on Windows
|style="background-color:#00FFFF;"|In Progress
|
*We're working on these problems; many complaints are due to people still using old servers/clients.
|MORPH
|(Old)
|-
|Some type of BZFlag GUID* to ban players who cheat - won't accept players who disable their GUID, etc.

<nowiki>*</nowiki>Global Unique Identifier, sort of like an IP addrss, but permanent. Usually a number. Problem occurs when you lose your GUID (have to reformat your HD, etc. How do you keep someone from hacking their GUID, or setting up a modified BZFlag server for identity theft, etc.
|(Unknown)
|
*I doubt this is even possible, let alone practical. What about people who play from more than one location? And, because this is an open-source game, it would probably be cracked in minutes. Any verification can be spoofed, or at least altered. there is no foolproof way to permanently ban someone. -L4m3r
|MORPH
|(Old)
|-
|To prevent cheating - the server determines what flags & abilities each tank has (possible?)
|style="background-color:#00FF00;"|In Progress
|
*Seriously being considered. This would also have the advantage of allowing different versions of clients and servers to work together. Yes, it's possible, but this type of change will mean a change in the network protocols.
*Being worked on for 2.2
|MORPH
|(Old)
|-
|BZFlag for mac in separate data and application files.
|(Unknown)
|
|iPod
|(Old)
|-
|J2ME client (allows one to play on a cell phone), would use radar
|(Unknown)
|
|bhtooefr
|(Old)
|-
|Special 'open source' BZFlag version (server and client) which is guaranteed to be compatible with all other BZFlag versions.
|(Unknown)
|
*BZFlag is already open-source, and making a universally-compatible client is not even remotely practical. Incompatibility is part of why the game breaks off new versions in the first place. [[User:L4m3r|L4m3r]]
|Orca
|(Old)
|-
|}
</div>

== Game Modes, Team Play, and Scoring ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Tounament mode
|style="background-color:#808080;"|Idea
|
*Great Idea?
|(Unknown)
|(Old)
|-
|When you shoot someone on your own team, instead of both of you blowing up, neither is destroyed, and their score goes up one, while your's goes down one. This would make teamkilling impossible and greatly discourage traitors as well.
|style="background-color:#808080;"|Idea
|
*But then couldn't cheaters spawn two clients and ramp up their scores by teamkilling their other login? --YHARG
|Trigger Happy Nerd
|(Old)
|-
|A new gameplay mode- Takes two to tank. One to control the (rotating) turret, the other drives. KIA switches positions. "Teamplay" but all in one tank.
|(Unknown)
|
*I see serious lag issues with this... How does Halo do it? ;) -L4m3r
*The main problem with this idea is coordination. If one person were to leave, the tank would be crippled. You COULD solve this by having the person switch to normal mode, but this could cause considerable jerking between modes on a busy server. [[User:F687s|F687s]] 22:13, 20 June 2007 (EDT)
|MORPH
|(Old)
|-
|Turret mode, If enabled by the server (Can be manditory with automatic grouping). One user drives and the other shoots, Turret mode tanks get double points (But onyl take one from the target). lost double points if killed. Have double ammo, And controllable speed (Max = _tankSpeed * 2 Min = _tankSpeed). Plus it takes 2 shots to kill a turret mode tank. Points gained and lost by turret tanks are divided evenly between the users, Unless the server is all turret mode, in h which case two users are displayed as one.
|(Unknown)
|
|Dogbert
|(Old)
|-
|Ability for a team to vote to 'banish' someone from their team
|style="background-color:#808080;"|Idea
|
*Possibly unfair to newer players. [[User:L4m3r|L4m3r]]
*Useful for getting rid of TKers and selfcappers. However you would need a way (e.g. a voting system) and you would need to be able to say to which team he or she should go if rogues are unavailable. Possible, if rogues are allowed, but not otherwise not really a good idea. --[[User:88.108.209.168|88.108.209.168]] 13:13, 24 December 2007 (EST)
|MORPH
|(Old)
|-
|There should be a game of cops and robbers. The teams can change after about 10 mins or so.
|style="background-color:#FFFF00;"|(Unknown)
|
|iPod
|(Old)
|-
|A special FFA Game mode "Team by Flags". This means, same Flag = same Team, so if there is a Tank with Rapid fire, and you pick up Rapid fire, you are automatically handled as Team member (this means, killing the other Tank with Rapid fire will be handled the same way as when killing a team member). YHARG: Funky idea: what about a game mode where teams shared flag abilities? Like, each player on a team's flag applies to the whole team. This could make for some interesting combos...
|(Unknown)
|
|Agonizer
|(Old)
|-
|Make life trickier for the Rogue Team; with a mix of Rogues and Colored Teams, the Rogues have more targets. This should also change the effect of the Masquerade flag - perhaps your tank is invisible to Rogues (like Cloaking)?
|(Unknown)
|
|NickGrim
|(Old)
|-
|A server option to make deaths not affect your score unless they were self-inflicted/team (the method used by many online games). This would encourage more aggressive play, because it's worth going out and blasting. As it is, you've got a very good chance by just phantoming/OOing out of the way and keeping you score at zero to stay in the top three places! It would also help fix the rather unfair situation of spawning just below a building on which someone is GM-camping...there's pretty much no way to escape, so you lose a point.
|(Unknown)
|
|LionsPhil
|(Old)
|-
|Don't show individual score in CTF games. This might help teamplay as it reduces the incentive to run around as if it would be FFA.
|(Unknown)
|
|abli
|(Old)
|-
|Give points to the player how captures flag in CTF. (Say, around 4 or so) After all, it is often a bigger job than killing someone.
|(Unknown)
|
*Maybe the score could be based the number of tanks in the other team, similar to shooting someone w/ geno. This can also discourage people from capturing thier own flag by scoreing the negative number of teamates. I'm not sure if the individual scores of the players of the captured team (other than the one who captures the flag) should be affected however. [[User:Sparky1|Sparky1]] 09:44, 21 May 2007 (EDT)
*Scores can be customized with plug-ins in 3.0. Unfortunately, there's a bug in 2.0.x that prevents the server from setting scores properly. [[User:L4m3r|L4m3r]] 01:46, 5 January 2008 (EST)
|abli
|(Old)
|-
|Ducati/Freestyle "Roles" mode: Make a game mode where players are presented with a list of flag choices (limitable to a few roles, if wanted) at respawn or connect time, and are forced to use this flag for the remainder of their connection/tank life. This would be really useful in the case of stealth vs. seer, where you could choose to be stealth or seer, but couldn't switch between them. Another idea would be high speed vs. quick turn. Or steamroller vs. machine gun... Team play would have the interesting effect of people banding together and people with each role on the team. Especially in stealth vs. seer, where a seer team member could warn the team about enemies! There would be no team flags/bases.
|(Unknown)
|
*Too specialized, use a plug-in (yes, it's possible). [[User:L4m3r|L4m3r]] 01:46, 5 January 2008 (EST)
|YHARG
|(Old)
|-
|New game called tag were someone is it and they shoot someone else and there it and ect.
|(Unknown)
|
|Supermatthew
|(Old)
|-
|Also a new game called "Hide and seek" were everyone is clocked(think thats it, were you don't see them on radar) except one who is it. he needs to find someone and shoot them then hese cloked and who was shot is not. Also when someone is shot there sent back to Ground zero( 0X, 0Y, 0Z ) so they can't shoot who ever just shot them.
|(Unknown)
|
|Supermatthew
|(Old)
|-
|"Cat" game: when a player dies, he/she respawns automaticaly, after 3 secs or so. When they have respawned 9 times, they can no longer spawn, and are observers. The one who lasts the longest wins. Games are timed.
|(Unknown)
|
|(Unknown)
|4/20/2007
|-
|A switch-teams function that allows you to swap teams during a game without losing score.
|(Unknown)
|
|jftsang
|10/11/2007
|-
|Rogue team - A mode in which rogues may TK and capture flag.
|(unknown)
|
*Why? [[User:L4m3r|L4m3r]] 01:46, 5 January 2008 (EST)
|jftsang
|10/11/2007
|-
|A Sport Mode: I noticed that there is a lot of recently created cool sport maps. In those maps a team flag is used as a "ball", and bases are used as "goals". I think that there is even more potential for great maps if there would be a game mode where a bullet behaves like a "ball".In that mode when a game starts, or right after a score, a bullet hovers over a specified location (like the center of the map) and no one can shoot. The first tank that touches the bullet "has the ball", in other words only that tank can shoot. If a tank that "has the ball" shoots it, shooting for that tank is disabled, likewise, if a tank is shot by a bullet that tank does not die, but instead it "has the ball", this allows for passing and interception. A tank that "has the ball" should be indcated somehow, perhaps by a unique flag. The "ball" has the color of the last tank that shot it. A new object would have to be created (perhaps called a goal zone?) that resembles a teleporter that results in a ctf if a bullet encounters it. Or instead of a specific object an area/volume on the map could be designated as a "goal zone" which would give more freedom in designing objects that behave like goals. The score would go to the team that has the same color as the bullet that encountered the "goal zone". All tanks would have the Steam Roller power. a tank that touches another tank would not be killed only if that tank is higher at the touch. If a tank that "has the ball" is killed before he can shoot the "ball" then the bullet appears at the tanks position of death and travel at the speed and in the direction the tank had at that point. Maybe a provision could be made where the number of "balls" could be set at a number greater than one to allow for more complex games.
|(Unknown)
|
|[[User:Sparky1|Sparky1]]
|1/21/2008
|-
|}
</div>

== Maps, Mapping, and BZW ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Materials that don't allow OO and PZ to go through
|style="background-color:#808080;"|Idea
|
*Would be nice for multilevel worlds made with the new ability to have objects above the ground.
*Sounds awesome! TD-Linux 17:41, 12 March 2007 (EDT)
*As a special case, there could be Zoned objects (objects that only respond to PZ and maybe OO; normal tanks behave like PZ through these objects). [[User:Sparky1|Sparky1]] 18:05, 21 May 2007 (EDT)
*Would also be nice if there were non-ricochet materials, or only ricochet some shot type materials. --[[User:88.108.209.168|88.108.209.168]] 13:09, 24 December 2007 (EST)
|(Unknown)
|(Old)
|-
|Differently-shaped teleporters (circles, triangles, etc.)
|style="background-color:#808080;"|Idea
|
*probably low priority
|MORPH
|(Old)
|-
|360 degree teleports - hit a spot on the ground or in the air from any direction and you teleport
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Configurable random teleporters - teleports to a different location every time
|style="background-color:#808080;"|Idea
|
*Idea is a bit vague... randomized teles are implemented if you use multiple links. Is this what is meant by this suggestion? -L4m3r
|MORPH
|(Old)
|-
|Triggers in levels
|style="background-color:#FFFF00;"|(Unknown)
|
*Triggers for what? unless you're talking about AI, this could most likely be handled with a server plug-in. [[User:L4m3r|L4m3r]]
|Dragonstar
|(Old)
|-
|wraparound world - radar remains centered on your current position. Internally, objects leaving the north border reappear to the south, but from the user's radar / visible perspective, you just see to the horizon. I believe this is how the original Battlezone worked. There are some implications: laser would need a range limit.
|(Unknown)
|
|nsayer
|(Old)
|-
|As a generalization to the wraparound world concept, how about the option of making a map based on geometry that’s non-Euclidean, for example spherical or hyperbolic. Jumping/flying, the shape of the tanks/objects, and bullet trajectories would also be affected by this global geometry. It would be like a world that has a high gravitational field, or a world situated near a wormhole.
|(Unknown)
|
|[[User:Sparky1|Sparky1]]
|5/21/2007
|-
|-
|Get rid of the PZ flag and replace it w/ special telporters that do the same thing (they could be called "zoners", and should probably look different from regular teleporters). This way superflags, badflags, and team flags can all be zoned (without needing an exception to the restricition against using more than one flag at a time). The above idea of other zoned objects would play a major role here. Zoned flags can only be picked up by zoned tanks. Flags can spawn zoned, or become zoned by being carried by an unzoned tank that becomes zoned by going through a zoner. Likewise, a zonedflag becomes unzoned when a zoned tank carries it through a zoner. Unzoned tanks respond to shots from zoned flags the same way zoned tanks respond to shots from unzoned flags. For example: when zoned, L, WG, geno, and GM do not kill unzoned tanks (zoned GM will still lock onto any tank, and zoned geno would still kill every tank on the same team as the zoned tank that was shot). Although, flags like SW and SB would still kill any tank regardless of thier zoning status. As an extension to this idea one team in a CTF game could start out zoned, i.e. thier base is zoned and they initially spawn zoned. In order for the unzoned team to capture the zoned team's flag, the flag must become unzoned, and vice versa for the zoned team. This way new possibilities exist, like two bases could be superimposed as long as one base is zoned and the other is not. Another possible extension is different kinds of zones (w/ corespondingly different kinds of zoners) for CTF involving more than two teams. The relationship between differently zoned tanks would be the same as the relationship between zoned and unzoned tanks.
|(Unknown)
|
|[[User:Sparky1|Sparky1]]
|5/21/2007
|-
|Change the workings of zones such that a zone may have its own server variables (I wanted to make a Death Castle against a Holy Castle).
|(Unknown)
|
|jftsang
|1/12/2007
|}
</div>

== Server Options, Administration, Plug-ins, and the Plug-in API ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Ability to configure server to turn somethings off or on depending on number of players - for instance, turn off ricochet after a certain number of players are connected, turn off GM & laser if a certain number of players aren't playing (GM & Laser with 2 players is kinda ridiculous)
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Allow custom-made weapons with a Object-Oriented scripting language (sorta like Liero AI uses: http://helios.et.put.poznan.pl/~sskowron/liero/index.html )
|(Unknown)
|
|Dragonstar
|(Old)
|-
|Preset world weapons that can be fired manually by admins from within BzFlag.
|(Unknown)
|
* Could be done by a plugin [[User:Tanner|Tanner]] 13:42, 12 August 2007 (EDT)
|Dogbert
|(Old)
|-
|}
</div>

== Graphics & Sound ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Sounds of tanks moving.
|(Unknown)
|
|iPod
|(Old)
|-
|Have different tank death scenes for the dying tank point of view. I realize there is some time needed for one to die and respawn, but the jumping effect one sees when killed irritates me to no end! I'd be happier if all faded to black or white or orange and had text across the screen saying ""respawning... please wait"" :) Also, when killed and your tank was moving toward a building, it just falls right thru it until it hits the ground.. wrong physics there! Splatter or tumble or shatter or something :)
|(Unknown)
|
|Robi
|(Old)
|-
|Custom color schemes for rogue players. The turret and body components can be chosen to be one of a predefined set of colors (e.g. red, yellow, black, white, blue, green, purple...). The game prohibits choosing a color scheme that matches a team scheme (e.g. red turret with red body) and the limited set stops someone choosing a shade which is nearly a team color (e.g. 0xFE0000 instead of 0xFF0000) (and also save texture memory, I think).
|(Unknown)
| * Clients are able to define their own colors, and removing the ability to would cause accessibility issues (Colorblind users). --[[User:AAA|AAA]] 13:30, 7 August 2007 (EDT)
|LionsPhil
|(Old)
|-
|Allow a small decal on the back of the top of the tank. (think Half-Life's customizable spraypaint). Possibly also apply it to any held flag?
|(Unknown)
|
|LionsPhil
|(Old)
|-
|I'd like to see something more interesting done with the sky... maybe there could be a little ufo (easter egg) that would fly around occasionally? Tux on a ufo! ;)
|(Unknown)
| This is up to servers. --[[User:AAA|AAA]] 13:30, 7 August 2007 (EDT)
|YHARG
|(Old)
|-
|Flag decals: Each flag would have a little icon/decal showing it's type ONLY when held by a player. It's kind of nice to be able to surprise people with an undercover shockwave, but doesn't make sense to have to right click (identify) or check the user list to see what flag someone has.
|(Unknown)
|
|YHARG
|(Old)
|-
|Background music! : (This can be done with an external media player so it shouldn't be the heighest priority, It would be nice to be able to control your music from within BzFlag)
|(Unknown)
|More usefully, you could just map key combinations to commands, rather than wasting time supporting all the various music players on every OS BZFlag supports. I don't know whether that would work so well on Windows, though. --[[User:77.97.207.100|77.97.207.100]] 10:14, 30 May 2007 (EDT)
|YHARG
|(Old)
|-
|}
</div>

== List Server and Other Global Services ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Multiple list servers, in case bzflag.org goes down (as it happened around feb. 15. 2004)
|style="background-color:#00FFFF;"|In progress
| * Of course someone would need to pay for it. --[[User:BinarySpike|BinarySpike]] 18:10, 10 May 2007 (EDT)
* We now have two servers, and some form of redundancy for the list should follow eventually. [[User:L4m3r|L4m3r]] 15:40, 31 January 2008 (EST)
|abli
|(Old)
|-
|}
</div>

[[Category:Development]]

Ideas

2008-01-31T20:37:28Z

L4m3r: /* Maps, Mapping, and BZW */ Remove rejected idea

{{Old}}
NOTE: These are just possibilities. We won't be implementing everything here.<br>

Commentary may include personal comments by developers.

= Editing this page =

Feel free to make changes and updates to this page whenever possible. If you have any questions, feel free to [[Getting Help|ask for help]]. If you wish to make major changes to this page (i.e. remove large amounts of old ideas), please warn us ahead of time.

== Adding ideas ==
* Please remember to make sure your idea isn't already here or on the [[Rejected Ideas]] page.
* Flag ideas should be placed on [[Flag Ideas]], not here.
* Add a row to the appropriate category (at the bottom, please) and fill it in with your idea.
* Sign your idea in the third column with three tildes: <nowiki>~~~</nowiki>
* Put the submission date in the fourth column
* Describe in full and make sense!
* Leave the status column white and fill it with (Unknown).

== Adding commentary ==
* Precede your comment with an asterisk: <nowiki>*</nowiki>
* Sign your comment with four tildes: <nowiki>~~~~</nowiki>
* Be nice, polite, and constructive.
* Contribute something when you comment. Saying whether or not you like an idea is pointless if you don't explain yourself.

== Cleaning up ==
To help keep this page current, old ideas should be removed when they're implemented (after each stable release, hence the "SVN" status). If you spot any ideas that were implemented prior to the latest stable release of BZFlag, please remove it.

= The list =
<div align="center">
{| cellpadding="10" cellspacing="1" border="1"
|+align="bottom"|''Legend''
|-
|style="background-color:#FF00FF;"|'' ''
|Implemented as a server-side plug-in
|-
|style="background-color:#0080FF;"|'' ''
|SVN (Implemented and will be in next release)
|-
|style="background-color:#00FFFF;"|'' ''
|In progress (Implementing)
|-
|style="background-color:#00FF00;"|'' ''
|Good Idea
|-
|style="background-color:#808080;"|'' ''
|Idea
|-
|style="background-color:#FFFF00;"|'' ''
|Vague, not understood, or in need of work
|-
|style="background-color:#FF8000"|'' ''
|Rejected, but can be implemented as a server plug-in
|-
|style="background-color:#FF0000;"|'' ''
|Rejected
|-
|style="background-color:#FFFFFF"|'' ''
|Unknown (new)
|}
</div>

== General/Gameplay ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Add support for 5 (or more) button mice
|style="background-color:#00FF00;"|Great Idea
|
|(Unknown)
|(Old)
|-
|Better physics
|style="background-color:#00FFFF;"|In progress
|
*Planning, some changes in CVS.
|Unknown
|(Old)
|-
|SELF-DESTRUCT BLAST RADIUS: Self Destruct (delete key) should have a blast radius similar to Shock Wave, perhaps larger. If you get shot during the self-destruct count down, that should also trigger the same blast. If I gotta go, I want to take someone with me.
|(Unknown)
|
|BearRiver
|(Old)
|-
|3-second (or however long) 'invulnerability' for incoming tanks - but they can't shoot
|style="background-color:#808080;"|Idea
|
*I could see this backfiring... your spawn attracts opponents to come, wait, and blast you when you lose invincibility. -L4m3r
|MORPH
|(Old)
|-
|Ability to turn off ricochet for laser flag but allow ricochet for bullets... or let them bounce only n times.. OR implement mirror buildings/walls. Should go for some interesting self-kills when combined with the no-radar/bullet bounce
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Smart LockOn for GM - won't lock on to your teammates (configurable in server)
|style="background-color:#808080;"|Idea
|
*I don't like this idea, there should be at least *some* risks to using this weapon. Personally, I think there should be more (not fewer) risks to holding this weapon; I'd like to see the thing overheat and explode (killing the holder) if it's fired too often in a short period of time. -M. Jetleb

*2.99 has an option to disable friendly fire altogether. Close enough. Lock-on could still be looked into, however. [[User:L4m3r|L4m3r]] 01:38, 5 January 2008 (EST)
|MORPH
|(Old)
|-
|Small jumps
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Server option for genocide flag - if you're killed while you have it, your team dies :^)
|style="background-color:#808080;"|Idea
|
*Feasible with a plug-in, too. -L4m3r
|MORPH
|(Old)
|-
|for broadband or LAN connections - voice chat for teams
|style="background-color:#808080;"|Idea
|
*I really think that you can do this with another service; I'm not sure if being part of BZFlag would be a good idea due to size and bandwidth issues.
|MORPH
|(Old)
|-
|Tank avatars (uploadable tank images) - have to think about shapes, though - someone could make a 1x1x1 pixel tank - that would suck - or a tank that looks like a building or pyramid. Clients don't have to accept downloading of avators (just view other tanks in default mode). Or just s-e-l-e-c-t from a certain number of predefined avatars that could come with the bzflag distribution. Or client provides a URL to download their avatar (saves server bandwidth).
|style="background-color:#808080;"|Idea
|*Might not be implemented. Requires discussion; we may want to consider making the computer force a minimum size or something similar.
*How about uploadable flag graphics?
|MORPH
|(Old)
|-
|'Kamikaze' option for players - can take someone out by suicide
|style="background-color:#808080;"|Idea
|
*Server option if implemented.
*Implemented with a plugin by Theme97
|MORPH
|(Old)
|-
|Server option: everyone is radar-stealthed by default unless you get a 'radar' flag. You can still see all buildings, pyramids, teleports, and arena walls, though.
|style="background-color:#00FF00;"|Good idea
|
*Make them use their window. ;)
*Given the fairly narrow field of view out the window and the time it takes to turn a tank all the way around for a look-see, I think this could be frustrating. How about everyone starts out with minimum range radar instead and gets longer ranges with an appropriate flag? -M. Jetleb
*Ideally this could be implemented in the same manner as jumping and ricochet- radar could be enabled by default, or available as a flag. [[User:L4m3r|L4m3r]] 01:38, 5 January 2008 (EST)
|MORPH
|(Old)
|-
|Option for above: if you pick up GM or Laser, you're visible on radar to everyone whether they've got a radar flag or not
|style="background-color:#00FF00;"|Good idea
|
|MORPH
|(Old)
|-
|Selectable 'ricochet' fire - hold down shift key or something and your bullets won't ricochet
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Server option - tanks only have a certain number of times they can jump (gets reset when you get killed)
|style="background-color:#808080;"|Idea
|
*Could be made possible with a plug-in in 2.99. [[User:L4m3r|L4m3r]] 01:38, 5 January 2008 (EST)
|MORPH
|(Old)
|-
|Multiple-shields (server option for shield flags, or can be random - can get hit x number of times)
|style="background-color:#808080;"|Idea
|*This is pretty much moot now. It's been shot down by the devs at least once, and a similar effect can be achieved by setting _shieldFlight to a very small number. This effectively provides as many hits as _maxFlagGrabs. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|Configurable 'radarless' and/or 'blind' zones in the arena - can't see what's in there on radar or via visuals
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Tank collisions - why can tanks drive through each other? Weird.
|style="background-color:#00FF00;"|Good Idea
|*Lag could be a big problem here. If implemented, it must be impossible for two tanks to get stuck to each other. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|When tanks collide - great opportunity to implement tank damage concept, especially if one of them is moving especially fast, or has momentum flag, etc. Can push a tank off a building if your pushing them from their side.
|style="background-color:#808080;"|Idea
|
*Tank damage won't happen, but the kinetics could be neat, especially for mid-air collisions. It would certainly make "jump dancing" more interesting. [[User:L4m3r|L4m3r]]
|Morph
|(Old)
|-
|If a tank explodes right next to another tank, the other tank can be destroyed or get damaged
|style="background-color:#808080;"|Idea
|
*Somewhat implemented with the [[ShockwaveDeath]] plug-in. It would probably not be too hard to implement something similar (with a plugin) without shockwaves. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|Skins or views- In-tank mode, bumper mode, out-of-cab mode, chase mode.
|(Unknown)
|
|MORPH
|(Old)
|-
|Weapon extension packs.
|style="background-color:#FFFF00;"|(Unknown)
|*Huh? Explain, please. [[User:L4m3r|L4m3r]]
|iPod
|(Old)
|-
|The ability to choose tanks, but they all die at one shot. maybe the jump height, speed, turn speed, acceleration, size can be preset.
|(Unknown)
|
*Could be done with a plug-in in 2.99, maybe. [[User:L4m3r|L4m3r]] 01:38, 5 January 2008 (EST)
|iPod
|(Old)
|-
|Option to choose different kinds of tanks. Different tanks could be weighted with different strengths and weaknesses. (almost like having a default flag). Would also need some form of health/damage status measurement, not just single hits. For example, there could be a larger, heavily armored tank that has powerful weapons, but moves slowly, versus a small, light, fast tank which is difficult to hit, but very low armor to protect from hits.
|(Unknown)
|
|Cue
|(Old)
|-
|What about a radar that only covers visible areas (don't passing through buildings/pyramids) ? This would leads to more placement tactics).
|(Unknown)
|
|K<nowiki>'</nowiki>limero
|(Old)
|-
|Always random respawn. Currently in CTF games first respawn is at own base. This can be abused by leaving and rejoining to get near base. This leave/rejoing trick is considered to be a mild form of cheating by many. Always random respawn would make it useless.
|(Unknown)
|
* I believe there is a plug-in for this. [[User:L4m3r|L4m3r]] 22:38, 30 April 2007 (EDT)
|abli
|(Old)
|-
|multiple (3?) jump stengths mini, normal, max...just the thing to confuse the opponents that expect one and you're off doing the other.
|(Unknown)
|
|kitchen
|(Old)
|-
|Anti camping. The ability to add "no camping zones" to areas of a map or to the entire map. Campers would be messaged that they're in a no camping zone, better start moving and have a prescribe number of seconds to move away or die. If a player returns to the same NCZ (no camping zone) and receives x warnings then he's disconnected. NCZs could be marked by a different color shade from a "normal" spot and could be exempt to a single team (like at their flag base). It's just a rough idea.
|(Unknown)
|
*Definitely more suited to a plug-in (and probably doable, too).
|pherris
|(Old)
|-
|Shield Flag Changes: Give Shield flag a radius, and draw it like a moving less opaque blue shockwave. Any tanks inside the shield radius would be protected, until the shield got hit a certain number of times.
|(Unknown)
|
|YHARG
|(Old)
|-
|At our company, we instituted a voluntary policy of dropping flags after 1 kill. Prevents slaughters and keeps things rolling more. It'd be great to be able to have the game do this for us, plus I'd love to see it turned on at external sites.
|(Unknown)
|
|TomMatelich
|(Old)
|-
|Server option: default powers -- flag(s) that everyone in the game automatically has (this wouldn't count as holding a flag). For example, the current Jumping option would == including Jumping as a default power.
|(Unknown)
|
|NebNamwen
|(Old)
|-
|Shot Aiming. Basically the center shot aim box could be moved left and right as far as the edge of the view window. (This would be enabled by default.) If the map is a vertical one a server option could be enabled so that vertical aiming could be enabled (using the same concept as horizontal aiming.) The aiming would be automatically centered by a button or key. These options could be mapped to a second joystick access, mouse scroll wheel or keyboard buttons.
|(Unknown)
|Lateral shooting would basically be the same as a rotating turret, and this idea has been shot down many times. Vertical shooting has been poo-pooed also. [[User:L4m3r|L4m3r]] 01:45, 3 July 2007 (EDT)
|NN
|6/20/07
|-
|Make a tele porter along the game sides that would tele port into other games running on their own servers. This would enable larger more collaborative game board linked together that would distribute loads across multiple servers speeding up game play and making for interesting possibilities.
|(Unknown)
|
|Waban*
|7/31/07
|-
|Make a 'fog of war' where the a player's radar only shows a certain distance of the area around them and their teammates'.
|(Unknown)
|
*This could be done if radar and position data were separated, allowing the server to "filter" radar data for each player.
|Forrest
|8/19/07
|}
</div>

== UI ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Make option to show previous players list
|style="background-color:#808080;"|Idea
|
|(Unknown)
|(Old)
|-
|Make ALL server options available from the menus
|style="background-color:#808080;"|Idea
|
*There are a LOT of server options, and this could add quite a bit of clutter. If you need more than a basic game, you should probably learn to start BZFS from the command line anyway. -L4m3r
|MORPH
|(Old)
|-
|Separate windows for player messages & server messages
|style="background-color:#00FF00;"|Good idea.
|
|MORPH
|(Old)
|-
|Message log
|style="background-color:#00FF00;"|Good idea.
|
|MORPH
|(Old)
|-
|Send message to everyone 'but' specified player (crosses team boundaries, or not)
|style="background-color:#808080;"|Idea
|
*Hmm. Everybody BUT a specified player? [M. Jetleb -> as in: "Let's all get the GM guy" without the GM guy knowing he's facing a co-ordinated attack - I like this idea)
|MORPH
|(Old)
|-
|The ability to see what the world is like before connecting to the server.
|(Unknown)
|
|iPod
|(Old)
|-
|Multi-monitor support (i.e., radar on one screen, window on another, chat/event log on a third)
|(Unknown)
|
|bhtooefr
|(Old)
|-
|Make a part in bzflag to put up a real server. 1st screen has the flags you want, next page is to find the MAP file that you created on your hard drive, next page pick if you want jumping etc.
|(Unknown)
|
|Colin
|(Old)
|-
|-
|Add a rear view mirror
|(Unknown)
|
|Sparky1
|1/1/2008
|-
|}
</div>

== Technical ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Better network handling
|style="background-color:#00FFFF;"|In progress
|
|(Unknown)
|(Old)
|-
|Better robot AI
|style="background-color:#808080;"|Idea
|
*Don't know if players would like it or not in multiplayer game. Pluggable or scriptable robot AI , maybe? - Code must be restructured first
*Server side bots are coming! [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT)
|(Unknown)
|(Old)
|-
|Better positioning of tanks
|style="background-color:#808080;"|Idea
|
*BZFlag already does this, but the algorithm is bad. Needs work.
|MORPH
|(Old)
|-
|Serious multithreaded design - shouldn't lock up interface while looking for servers, or doing anything else. This program is way-unstable on Windows
|style="background-color:#00FFFF;"|In Progress
|
*We're working on these problems; many complaints are due to people still using old servers/clients.
|MORPH
|(Old)
|-
|Some type of BZFlag GUID* to ban players who cheat - won't accept players who disable their GUID, etc.

<nowiki>*</nowiki>Global Unique Identifier, sort of like an IP addrss, but permanent. Usually a number. Problem occurs when you lose your GUID (have to reformat your HD, etc. How do you keep someone from hacking their GUID, or setting up a modified BZFlag server for identity theft, etc.
|(Unknown)
|
*I doubt this is even possible, let alone practical. What about people who play from more than one location? And, because this is an open-source game, it would probably be cracked in minutes. Any verification can be spoofed, or at least altered. there is no foolproof way to permanently ban someone. -L4m3r
|MORPH
|(Old)
|-
|To prevent cheating - the server determines what flags & abilities each tank has (possible?)
|style="background-color:#00FF00;"|In Progress
|
*Seriously being considered. This would also have the advantage of allowing different versions of clients and servers to work together. Yes, it's possible, but this type of change will mean a change in the network protocols.
*Being worked on for 2.2
|MORPH
|(Old)
|-
|BZFlag for mac in separate data and application files.
|(Unknown)
|
|iPod
|(Old)
|-
|J2ME client (allows one to play on a cell phone), would use radar
|(Unknown)
|
|bhtooefr
|(Old)
|-
|Special 'open source' BZFlag version (server and client) which is guaranteed to be compatible with all other BZFlag versions.
|(Unknown)
|
*BZFlag is already open-source, and making a universally-compatible client is not even remotely practical. Incompatibility is part of why the game breaks off new versions in the first place. [[User:L4m3r|L4m3r]]
|Orca
|(Old)
|-
|}
</div>

== Game Modes, Team Play, and Scoring ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Tounament mode
|style="background-color:#808080;"|Idea
|
*Great Idea?
|(Unknown)
|(Old)
|-
|When you shoot someone on your own team, instead of both of you blowing up, neither is destroyed, and their score goes up one, while your's goes down one. This would make teamkilling impossible and greatly discourage traitors as well.
|style="background-color:#808080;"|Idea
|
*But then couldn't cheaters spawn two clients and ramp up their scores by teamkilling their other login? --YHARG
|Trigger Happy Nerd
|(Old)
|-
|A new gameplay mode- Takes two to tank. One to control the (rotating) turret, the other drives. KIA switches positions. "Teamplay" but all in one tank.
|(Unknown)
|
*I see serious lag issues with this... How does Halo do it? ;) -L4m3r
*The main problem with this idea is coordination. If one person were to leave, the tank would be crippled. You COULD solve this by having the person switch to normal mode, but this could cause considerable jerking between modes on a busy server. [[User:F687s|F687s]] 22:13, 20 June 2007 (EDT)
|MORPH
|(Old)
|-
|Turret mode, If enabled by the server (Can be manditory with automatic grouping). One user drives and the other shoots, Turret mode tanks get double points (But onyl take one from the target). lost double points if killed. Have double ammo, And controllable speed (Max = _tankSpeed * 2 Min = _tankSpeed). Plus it takes 2 shots to kill a turret mode tank. Points gained and lost by turret tanks are divided evenly between the users, Unless the server is all turret mode, in h which case two users are displayed as one.
|(Unknown)
|
|Dogbert
|(Old)
|-
|Ability for a team to vote to 'banish' someone from their team
|style="background-color:#808080;"|Idea
|
*Possibly unfair to newer players. [[User:L4m3r|L4m3r]]
*Useful for getting rid of TKers and selfcappers. However you would need a way (e.g. a voting system) and you would need to be able to say to which team he or she should go if rogues are unavailable. Possible, if rogues are allowed, but not otherwise not really a good idea. --[[User:88.108.209.168|88.108.209.168]] 13:13, 24 December 2007 (EST)
|MORPH
|(Old)
|-
|There should be a game of cops and robbers. The teams can change after about 10 mins or so.
|style="background-color:#FFFF00;"|(Unknown)
|
|iPod
|(Old)
|-
|A special FFA Game mode "Team by Flags". This means, same Flag = same Team, so if there is a Tank with Rapid fire, and you pick up Rapid fire, you are automatically handled as Team member (this means, killing the other Tank with Rapid fire will be handled the same way as when killing a team member). YHARG: Funky idea: what about a game mode where teams shared flag abilities? Like, each player on a team's flag applies to the whole team. This could make for some interesting combos...
|(Unknown)
|
|Agonizer
|(Old)
|-
|Make life trickier for the Rogue Team; with a mix of Rogues and Colored Teams, the Rogues have more targets. This should also change the effect of the Masquerade flag - perhaps your tank is invisible to Rogues (like Cloaking)?
|(Unknown)
|
|NickGrim
|(Old)
|-
|A server option to make deaths not affect your score unless they were self-inflicted/team (the method used by many online games). This would encourage more aggressive play, because it's worth going out and blasting. As it is, you've got a very good chance by just phantoming/OOing out of the way and keeping you score at zero to stay in the top three places! It would also help fix the rather unfair situation of spawning just below a building on which someone is GM-camping...there's pretty much no way to escape, so you lose a point.
|(Unknown)
|
|LionsPhil
|(Old)
|-
|Don't show individual score in CTF games. This might help teamplay as it reduces the incentive to run around as if it would be FFA.
|(Unknown)
|
|abli
|(Old)
|-
|Give points to the player how captures flag in CTF. (Say, around 4 or so) After all, it is often a bigger job than killing someone.
|(Unknown)
|
*Maybe the score could be based the number of tanks in the other team, similar to shooting someone w/ geno. This can also discourage people from capturing thier own flag by scoreing the negative number of teamates. I'm not sure if the individual scores of the players of the captured team (other than the one who captures the flag) should be affected however. [[User:Sparky1|Sparky1]] 09:44, 21 May 2007 (EDT)
*Scores can be customized with plug-ins in 3.0. Unfortunately, there's a bug in 2.0.x that prevents the server from setting scores properly. [[User:L4m3r|L4m3r]] 01:46, 5 January 2008 (EST)
|abli
|(Old)
|-
|Ducati/Freestyle "Roles" mode: Make a game mode where players are presented with a list of flag choices (limitable to a few roles, if wanted) at respawn or connect time, and are forced to use this flag for the remainder of their connection/tank life. This would be really useful in the case of stealth vs. seer, where you could choose to be stealth or seer, but couldn't switch between them. Another idea would be high speed vs. quick turn. Or steamroller vs. machine gun... Team play would have the interesting effect of people banding together and people with each role on the team. Especially in stealth vs. seer, where a seer team member could warn the team about enemies! There would be no team flags/bases.
|(Unknown)
|
*Too specialized, use a plug-in (yes, it's possible). [[User:L4m3r|L4m3r]] 01:46, 5 January 2008 (EST)
|YHARG
|(Old)
|-
|New game called tag were someone is it and they shoot someone else and there it and ect.
|(Unknown)
|
|Supermatthew
|(Old)
|-
|Also a new game called "Hide and seek" were everyone is clocked(think thats it, were you don't see them on radar) except one who is it. he needs to find someone and shoot them then hese cloked and who was shot is not. Also when someone is shot there sent back to Ground zero( 0X, 0Y, 0Z ) so they can't shoot who ever just shot them.
|(Unknown)
|
|Supermatthew
|(Old)
|-
|"Cat" game: when a player dies, he/she respawns automaticaly, after 3 secs or so. When they have respawned 9 times, they can no longer spawn, and are observers. The one who lasts the longest wins. Games are timed.
|(Unknown)
|
|(Unknown)
|4/20/2007
|-
|A switch-teams function that allows you to swap teams during a game without losing score.
|(Unknown)
|
|jftsang
|10/11/2007
|-
|Rogue team - A mode in which rogues may TK and capture flag.
|(unknown)
|
*Why? [[User:L4m3r|L4m3r]] 01:46, 5 January 2008 (EST)
|jftsang
|10/11/2007
|-
|A Sport Mode: I noticed that there is a lot of recently created cool sport maps. In those maps a team flag is used as a "ball", and bases are used as "goals". I think that there is even more potential for great maps if there would be a game mode where a bullet behaves like a "ball".In that mode when a game starts, or right after a score, a bullet hovers over a specified location (like the center of the map) and no one can shoot. The first tank that touches the bullet "has the ball", in other words only that tank can shoot. If a tank that "has the ball" shoots it, shooting for that tank is disabled, likewise, if a tank is shot by a bullet that tank does not die, but instead it "has the ball", this allows for passing and interception. A tank that "has the ball" should be indcated somehow, perhaps by a unique flag. The "ball" has the color of the last tank that shot it. A new object would have to be created (perhaps called a goal zone?) that resembles a teleporter that results in a ctf if a bullet encounters it. Or instead of a specific object an area/volume on the map could be designated as a "goal zone" which would give more freedom in designing objects that behave like goals. The score would go to the team that has the same color as the bullet that encountered the "goal zone". All tanks would have the Steam Roller power. a tank that touches another tank would not be killed only if that tank is higher at the touch. If a tank that "has the ball" is killed before he can shoot the "ball" then the bullet appears at the tanks position of death and travel at the speed and in the direction the tank had at that point. Maybe a provision could be made where the number of "balls" could be set at a number greater than one to allow for more complex games.
|(Unknown)
|
|[[User:Sparky1|Sparky1]]
|1/21/2008
|-
|}
</div>

== Maps, Mapping, and BZW ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Materials that don't allow OO and PZ to go through
|style="background-color:#808080;"|Idea
|
*Would be nice for multilevel worlds made with the new ability to have objects above the ground.
*Sounds awesome! TD-Linux 17:41, 12 March 2007 (EDT)
*As a special case, there could be Zoned objects (objects that only respond to PZ and maybe OO; normal tanks behave like PZ through these objects). [[User:Sparky1|Sparky1]] 18:05, 21 May 2007 (EDT)
*Would also be nice if there were non-ricochet materials, or only ricochet some shot type materials. --[[User:88.108.209.168|88.108.209.168]] 13:09, 24 December 2007 (EST)
|(Unknown)
|(Old)
|-
|Differently-shaped teleporters (circles, triangles, etc.)
|style="background-color:#808080;"|Idea
|
*probably low priority
|MORPH
|(Old)
|-
|360 degree teleports - hit a spot on the ground or in the air from any direction and you teleport
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Configurable random teleporters - teleports to a different location every time
|style="background-color:#808080;"|Idea
|
*Idea is a bit vague... randomized teles are implemented if you use multiple links. Is this what is meant by this suggestion? -L4m3r
|MORPH
|(Old)
|-
|Triggers in levels
|style="background-color:#FFFF00;"|(Unknown)
|
*Triggers for what? unless you're talking about AI, this could most likely be handled with a server plug-in. [[User:L4m3r|L4m3r]]
|Dragonstar
|(Old)
|-
|wraparound world - radar remains centered on your current position. Internally, objects leaving the north border reappear to the south, but from the user's radar / visible perspective, you just see to the horizon. I believe this is how the original Battlezone worked. There are some implications: laser would need a range limit.
|(Unknown)
|
|nsayer
|(Old)
|-
|As a generalization to the wraparound world concept, how about the option of making a map based on geometry that’s non-Euclidean, for example spherical or hyperbolic. Jumping/flying, the shape of the tanks/objects, and bullet trajectories would also be affected by this global geometry. It would be like a world that has a high gravitational field, or a world situated near a wormhole.
|(Unknown)
|
|[[User:Sparky1|Sparky1]]
|5/21/2007
|-
|-
|Get rid of the PZ flag and replace it w/ special telporters that do the same thing (they could be called "zoners", and should probably look different from regular teleporters). This way superflags, badflags, and team flags can all be zoned (without needing an exception to the restricition against using more than one flag at a time). The above idea of other zoned objects would play a major role here. Zoned flags can only be picked up by zoned tanks. Flags can spawn zoned, or become zoned by being carried by an unzoned tank that becomes zoned by going through a zoner. Likewise, a zonedflag becomes unzoned when a zoned tank carries it through a zoner. Unzoned tanks respond to shots from zoned flags the same way zoned tanks respond to shots from unzoned flags. For example: when zoned, L, WG, geno, and GM do not kill unzoned tanks (zoned GM will still lock onto any tank, and zoned geno would still kill every tank on the same team as the zoned tank that was shot). Although, flags like SW and SB would still kill any tank regardless of thier zoning status. As an extension to this idea one team in a CTF game could start out zoned, i.e. thier base is zoned and they initially spawn zoned. In order for the unzoned team to capture the zoned team's flag, the flag must become unzoned, and vice versa for the zoned team. This way new possibilities exist, like two bases could be superimposed as long as one base is zoned and the other is not. Another possible extension is different kinds of zones (w/ corespondingly different kinds of zoners) for CTF involving more than two teams. The relationship between differently zoned tanks would be the same as the relationship between zoned and unzoned tanks.
|(Unknown)
|
|[[User:Sparky1|Sparky1]]
|5/21/2007
|-
|Change the workings of zones such that a zone may have its own server variables (I wanted to make a Death Castle against a Holy Castle).
|(Unknown)
|
|jftsang
|1/12/2007
|}
</div>

== Server Options, Administration, Plug-ins, and the Plug-in API ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Ability to configure server to turn somethings off or on depending on number of players - for instance, turn off ricochet after a certain number of players are connected, turn off GM & laser if a certain number of players aren't playing (GM & Laser with 2 players is kinda ridiculous)
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Allow custom-made weapons with a Object-Oriented scripting language (sorta like Liero AI uses: http://helios.et.put.poznan.pl/~sskowron/liero/index.html )
|(Unknown)
|
|Dragonstar
|(Old)
|-
|Preset world weapons that can be fired manually by admins from within BzFlag.
|(Unknown)
|
* Could be done by a plugin [[User:Tanner|Tanner]] 13:42, 12 August 2007 (EDT)
|Dogbert
|(Old)
|-
|}
</div>

== Graphics & Sound ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Sounds of tanks moving.
|(Unknown)
|
|iPod
|(Old)
|-
|Have different tank death scenes for the dying tank point of view. I realize there is some time needed for one to die and respawn, but the jumping effect one sees when killed irritates me to no end! I'd be happier if all faded to black or white or orange and had text across the screen saying ""respawning... please wait"" :) Also, when killed and your tank was moving toward a building, it just falls right thru it until it hits the ground.. wrong physics there! Splatter or tumble or shatter or something :)
|(Unknown)
|
|Robi
|(Old)
|-
|Custom color schemes for rogue players. The turret and body components can be chosen to be one of a predefined set of colors (e.g. red, yellow, black, white, blue, green, purple...). The game prohibits choosing a color scheme that matches a team scheme (e.g. red turret with red body) and the limited set stops someone choosing a shade which is nearly a team color (e.g. 0xFE0000 instead of 0xFF0000) (and also save texture memory, I think).
|(Unknown)
| * Clients are able to define their own colors, and removing the ability to would cause accessibility issues (Colorblind users). --[[User:AAA|AAA]] 13:30, 7 August 2007 (EDT)
|LionsPhil
|(Old)
|-
|Allow a small decal on the back of the top of the tank. (think Half-Life's customizable spraypaint). Possibly also apply it to any held flag?
|(Unknown)
|
|LionsPhil
|(Old)
|-
|I'd like to see something more interesting done with the sky... maybe there could be a little ufo (easter egg) that would fly around occasionally? Tux on a ufo! ;)
|(Unknown)
| This is up to servers. --[[User:AAA|AAA]] 13:30, 7 August 2007 (EDT)
|YHARG
|(Old)
|-
|Flag decals: Each flag would have a little icon/decal showing it's type ONLY when held by a player. It's kind of nice to be able to surprise people with an undercover shockwave, but doesn't make sense to have to right click (identify) or check the user list to see what flag someone has.
|(Unknown)
|
|YHARG
|(Old)
|-
|Background music! : (This can be done with an external media player so it shouldn't be the heighest priority, It would be nice to be able to control your music from within BzFlag)
|(Unknown)
|More usefully, you could just map key combinations to commands, rather than wasting time supporting all the various music players on every OS BZFlag supports. I don't know whether that would work so well on Windows, though. --[[User:77.97.207.100|77.97.207.100]] 10:14, 30 May 2007 (EDT)
|YHARG
|(Old)
|-
|}
</div>

== List Server and Other Global Services ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Multiple list servers, in case bzflag.org goes down (as it happened around feb. 15. 2004)
|(Unknown)
|Of course someone would need to pay for it. --[[User:BinarySpike|BinarySpike]] 18:10, 10 May 2007 (EDT)
|abli
|(Old)
|-
|}
</div>

[[Category:Development]]

Ideas

2008-01-05T06:46:45Z

L4m3r: /* Game Modes, Team Play, and Scoring */

{{Old}}
NOTE: These are just possibilities. We won't be implementing everything here.<br>

Commentary may include personal comments by developers.

= Editing this page =

Feel free to make changes and updates to this page whenever possible. If you have any questions, feel free to [[Getting Help|ask for help]]. If you wish to make major changes to this page (i.e. remove large amounts of old ideas), please warn us ahead of time.

== Adding ideas ==
* Please remember to make sure your idea isn't already here or on the [[Rejected Ideas]] page.
* Flag ideas should be placed on [[Flag Ideas]], not here.
* Add a row to the appropriate category (at the bottom, please) and fill it in with your idea.
* Sign your idea in the third column with three tildes: <nowiki>~~~</nowiki>
* Put the submission date in the fourth column
* Describe in full and make sense!
* Leave the status column white and fill it with (Unknown).

== Adding commentary ==
* Precede your comment with an asterisk: <nowiki>*</nowiki>
* Sign your comment with four tildes: <nowiki>~~~~</nowiki>
* Be nice, polite, and constructive.
* Contribute something when you comment. Saying whether or not you like an idea is pointless if you don't explain yourself.

== Cleaning up ==
To help keep this page current, old ideas should be removed when they're implemented (after each stable release, hence the "SVN" status). If you spot any ideas that were implemented prior to the latest stable release of BZFlag, please remove it.

= The list =
<div align="center">
{| cellpadding="10" cellspacing="1" border="1"
|+align="bottom"|''Legend''
|-
|style="background-color:#FF00FF;"|'' ''
|Implemented as a server-side plug-in
|-
|style="background-color:#0080FF;"|'' ''
|SVN (Implemented and will be in next release)
|-
|style="background-color:#00FFFF;"|'' ''
|In progress (Implementing)
|-
|style="background-color:#00FF00;"|'' ''
|Good Idea
|-
|style="background-color:#808080;"|'' ''
|Idea
|-
|style="background-color:#FFFF00;"|'' ''
|Vague, not understood, or in need of work
|-
|style="background-color:#FF8000"|'' ''
|Rejected, but can be implemented as a server plug-in
|-
|style="background-color:#FF0000;"|'' ''
|Rejected
|-
|style="background-color:#FFFFFF"|'' ''
|Unknown (new)
|}
</div>

== General/Gameplay ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Add support for 5 (or more) button mice
|style="background-color:#00FF00;"|Great Idea
|
|(Unknown)
|(Old)
|-
|Better physics
|style="background-color:#00FFFF;"|In progress
|
*Planning, some changes in CVS.
|Unknown
|(Old)
|-
|SELF-DESTRUCT BLAST RADIUS: Self Destruct (delete key) should have a blast radius similar to Shock Wave, perhaps larger. If you get shot during the self-destruct count down, that should also trigger the same blast. If I gotta go, I want to take someone with me.
|(Unknown)
|
|BearRiver
|(Old)
|-
|3-second (or however long) 'invulnerability' for incoming tanks - but they can't shoot
|style="background-color:#808080;"|Idea
|
*I could see this backfiring... your spawn attracts opponents to come, wait, and blast you when you lose invincibility. -L4m3r
|MORPH
|(Old)
|-
|Ability to turn off ricochet for laser flag but allow ricochet for bullets... or let them bounce only n times.. OR implement mirror buildings/walls. Should go for some interesting self-kills when combined with the no-radar/bullet bounce
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Smart LockOn for GM - won't lock on to your teammates (configurable in server)
|style="background-color:#808080;"|Idea
|
*I don't like this idea, there should be at least *some* risks to using this weapon. Personally, I think there should be more (not fewer) risks to holding this weapon; I'd like to see the thing overheat and explode (killing the holder) if it's fired too often in a short period of time. -M. Jetleb

*2.99 has an option to disable friendly fire altogether. Close enough. Lock-on could still be looked into, however. [[User:L4m3r|L4m3r]] 01:38, 5 January 2008 (EST)
|MORPH
|(Old)
|-
|Small jumps
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Server option for genocide flag - if you're killed while you have it, your team dies :^)
|style="background-color:#808080;"|Idea
|
*Feasible with a plug-in, too. -L4m3r
|MORPH
|(Old)
|-
|for broadband or LAN connections - voice chat for teams
|style="background-color:#808080;"|Idea
|
*I really think that you can do this with another service; I'm not sure if being part of BZFlag would be a good idea due to size and bandwidth issues.
|MORPH
|(Old)
|-
|Tank avatars (uploadable tank images) - have to think about shapes, though - someone could make a 1x1x1 pixel tank - that would suck - or a tank that looks like a building or pyramid. Clients don't have to accept downloading of avators (just view other tanks in default mode). Or just s-e-l-e-c-t from a certain number of predefined avatars that could come with the bzflag distribution. Or client provides a URL to download their avatar (saves server bandwidth).
|style="background-color:#808080;"|Idea
|*Might not be implemented. Requires discussion; we may want to consider making the computer force a minimum size or something similar.
*How about uploadable flag graphics?
|MORPH
|(Old)
|-
|'Kamikaze' option for players - can take someone out by suicide
|style="background-color:#808080;"|Idea
|
*Server option if implemented.
*Implemented with a plugin by Theme97
|MORPH
|(Old)
|-
|Server option: everyone is radar-stealthed by default unless you get a 'radar' flag. You can still see all buildings, pyramids, teleports, and arena walls, though.
|style="background-color:#00FF00;"|Good idea
|
*Make them use their window. ;)
*Given the fairly narrow field of view out the window and the time it takes to turn a tank all the way around for a look-see, I think this could be frustrating. How about everyone starts out with minimum range radar instead and gets longer ranges with an appropriate flag? -M. Jetleb
*Ideally this could be implemented in the same manner as jumping and ricochet- radar could be enabled by default, or available as a flag. [[User:L4m3r|L4m3r]] 01:38, 5 January 2008 (EST)
|MORPH
|(Old)
|-
|Option for above: if you pick up GM or Laser, you're visible on radar to everyone whether they've got a radar flag or not
|style="background-color:#00FF00;"|Good idea
|
|MORPH
|(Old)
|-
|Selectable 'ricochet' fire - hold down shift key or something and your bullets won't ricochet
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Server option - tanks only have a certain number of times they can jump (gets reset when you get killed)
|style="background-color:#808080;"|Idea
|
*Could be made possible with a plug-in in 2.99. [[User:L4m3r|L4m3r]] 01:38, 5 January 2008 (EST)
|MORPH
|(Old)
|-
|Multiple-shields (server option for shield flags, or can be random - can get hit x number of times)
|style="background-color:#808080;"|Idea
|*This is pretty much moot now. It's been shot down by the devs at least once, and a similar effect can be achieved by setting _shieldFlight to a very small number. This effectively provides as many hits as _maxFlagGrabs. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|Configurable 'radarless' and/or 'blind' zones in the arena - can't see what's in there on radar or via visuals
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Tank collisions - why can tanks drive through each other? Weird.
|style="background-color:#00FF00;"|Good Idea
|*Lag could be a big problem here. If implemented, it must be impossible for two tanks to get stuck to each other. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|When tanks collide - great opportunity to implement tank damage concept, especially if one of them is moving especially fast, or has momentum flag, etc. Can push a tank off a building if your pushing them from their side.
|style="background-color:#808080;"|Idea
|
*Tank damage won't happen, but the kinetics could be neat, especially for mid-air collisions. It would certainly make "jump dancing" more interesting. [[User:L4m3r|L4m3r]]
|Morph
|(Old)
|-
|If a tank explodes right next to another tank, the other tank can be destroyed or get damaged
|style="background-color:#808080;"|Idea
|
*Somewhat implemented with the [[ShockwaveDeath]] plug-in. It would probably not be too hard to implement something similar (with a plugin) without shockwaves. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|Skins or views- In-tank mode, bumper mode, out-of-cab mode, chase mode.
|(Unknown)
|
|MORPH
|(Old)
|-
|Weapon extension packs.
|style="background-color:#FFFF00;"|(Unknown)
|*Huh? Explain, please. [[User:L4m3r|L4m3r]]
|iPod
|(Old)
|-
|The ability to choose tanks, but they all die at one shot. maybe the jump height, speed, turn speed, acceleration, size can be preset.
|(Unknown)
|
*Could be done with a plug-in in 2.99, maybe. [[User:L4m3r|L4m3r]] 01:38, 5 January 2008 (EST)
|iPod
|(Old)
|-
|Option to choose different kinds of tanks. Different tanks could be weighted with different strengths and weaknesses. (almost like having a default flag). Would also need some form of health/damage status measurement, not just single hits. For example, there could be a larger, heavily armored tank that has powerful weapons, but moves slowly, versus a small, light, fast tank which is difficult to hit, but very low armor to protect from hits.
|(Unknown)
|
|Cue
|(Old)
|-
|What about a radar that only covers visible areas (don't passing through buildings/pyramids) ? This would leads to more placement tactics).
|(Unknown)
|
|K<nowiki>'</nowiki>limero
|(Old)
|-
|Always random respawn. Currently in CTF games first respawn is at own base. This can be abused by leaving and rejoining to get near base. This leave/rejoing trick is considered to be a mild form of cheating by many. Always random respawn would make it useless.
|(Unknown)
|
* I believe there is a plug-in for this. [[User:L4m3r|L4m3r]] 22:38, 30 April 2007 (EDT)
|abli
|(Old)
|-
|multiple (3?) jump stengths mini, normal, max...just the thing to confuse the opponents that expect one and you're off doing the other.
|(Unknown)
|
|kitchen
|(Old)
|-
|Anti camping. The ability to add "no camping zones" to areas of a map or to the entire map. Campers would be messaged that they're in a no camping zone, better start moving and have a prescribe number of seconds to move away or die. If a player returns to the same NCZ (no camping zone) and receives x warnings then he's disconnected. NCZs could be marked by a different color shade from a "normal" spot and could be exempt to a single team (like at their flag base). It's just a rough idea.
|(Unknown)
|
*Definitely more suited to a plug-in (and probably doable, too).
|pherris
|(Old)
|-
|Shield Flag Changes: Give Shield flag a radius, and draw it like a moving less opaque blue shockwave. Any tanks inside the shield radius would be protected, until the shield got hit a certain number of times.
|(Unknown)
|
|YHARG
|(Old)
|-
|At our company, we instituted a voluntary policy of dropping flags after 1 kill. Prevents slaughters and keeps things rolling more. It'd be great to be able to have the game do this for us, plus I'd love to see it turned on at external sites.
|(Unknown)
|
|TomMatelich
|(Old)
|-
|Server option: default powers -- flag(s) that everyone in the game automatically has (this wouldn't count as holding a flag). For example, the current Jumping option would == including Jumping as a default power.
|(Unknown)
|
|NebNamwen
|(Old)
|-
|Shot Aiming. Basically the center shot aim box could be moved left and right as far as the edge of the view window. (This would be enabled by default.) If the map is a vertical one a server option could be enabled so that vertical aiming could be enabled (using the same concept as horizontal aiming.) The aiming would be automatically centered by a button or key. These options could be mapped to a second joystick access, mouse scroll wheel or keyboard buttons.
|(Unknown)
|Lateral shooting would basically be the same as a rotating turret, and this idea has been shot down many times. Vertical shooting has been poo-pooed also. [[User:L4m3r|L4m3r]] 01:45, 3 July 2007 (EDT)
|NN
|6/20/07
|-
|Make a tele porter along the game sides that would tele port into other games running on their own servers. This would enable larger more collaborative game board linked together that would distribute loads across multiple servers speeding up game play and making for interesting possibilities.
|(Unknown)
|
|Waban*
|7/31/07
|-
|Make a 'fog of war' where the a player's radar only shows a certain distance of the area around them and their teammates'.
|(Unknown)
|
*This could be done if radar and position data were separated, allowing the server to "filter" radar data for each player.
|Forrest
|8/19/07
|}
</div>

== UI ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Make option to show previous players list
|style="background-color:#808080;"|Idea
|
|(Unknown)
|(Old)
|-
|Make ALL server options available from the menus
|style="background-color:#808080;"|Idea
|
*There are a LOT of server options, and this could add quite a bit of clutter. If you need more than a basic game, you should probably learn to start BZFS from the command line anyway. -L4m3r
|MORPH
|(Old)
|-
|Separate windows for player messages & server messages
|style="background-color:#00FF00;"|Good idea.
|
|MORPH
|(Old)
|-
|Message log
|style="background-color:#00FF00;"|Good idea.
|
|MORPH
|(Old)
|-
|Send message to everyone 'but' specified player (crosses team boundaries, or not)
|style="background-color:#808080;"|Idea
|
*Hmm. Everybody BUT a specified player? [M. Jetleb -> as in: "Let's all get the GM guy" without the GM guy knowing he's facing a co-ordinated attack - I like this idea)
|MORPH
|(Old)
|-
|The ability to see what the world is like before connecting to the server.
|(Unknown)
|
|iPod
|(Old)
|-
|Multi-monitor support (i.e., radar on one screen, window on another, chat/event log on a third)
|(Unknown)
|
|bhtooefr
|(Old)
|-
|Make a part in bzflag to put up a real server. 1st screen has the flags you want, next page is to find the MAP file that you created on your hard drive, next page pick if you want jumping etc.
|(Unknown)
|
|Colin
|(Old)
|-
|-
|Add a rear view mirror
|(Unknown)
|
|Sparky1
|1/1/2008
|-
|}
</div>

== Technical ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Better network handling
|style="background-color:#00FFFF;"|In progress
|
|(Unknown)
|(Old)
|-
|Better robot AI
|style="background-color:#808080;"|Idea
|
*Don't know if players would like it or not in multiplayer game. Pluggable or scriptable robot AI , maybe? - Code must be restructured first
*Server side bots are coming! [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT)
|(Unknown)
|(Old)
|-
|Better positioning of tanks
|style="background-color:#808080;"|Idea
|
*BZFlag already does this, but the algorithm is bad. Needs work.
|MORPH
|(Old)
|-
|Serious multithreaded design - shouldn't lock up interface while looking for servers, or doing anything else. This program is way-unstable on Windows
|style="background-color:#00FFFF;"|In Progress
|
*We're working on these problems; many complaints are due to people still using old servers/clients.
|MORPH
|(Old)
|-
|Some type of BZFlag GUID* to ban players who cheat - won't accept players who disable their GUID, etc.

<nowiki>*</nowiki>Global Unique Identifier, sort of like an IP addrss, but permanent. Usually a number. Problem occurs when you lose your GUID (have to reformat your HD, etc. How do you keep someone from hacking their GUID, or setting up a modified BZFlag server for identity theft, etc.
|(Unknown)
|
*I doubt this is even possible, let alone practical. What about people who play from more than one location? And, because this is an open-source game, it would probably be cracked in minutes. Any verification can be spoofed, or at least altered. there is no foolproof way to permanently ban someone. -L4m3r
|MORPH
|(Old)
|-
|To prevent cheating - the server determines what flags & abilities each tank has (possible?)
|style="background-color:#00FF00;"|In Progress
|
*Seriously being considered. This would also have the advantage of allowing different versions of clients and servers to work together. Yes, it's possible, but this type of change will mean a change in the network protocols.
*Being worked on for 2.2
|MORPH
|(Old)
|-
|BZFlag for mac in separate data and application files.
|(Unknown)
|
|iPod
|(Old)
|-
|J2ME client (allows one to play on a cell phone), would use radar
|(Unknown)
|
|bhtooefr
|(Old)
|-
|Special 'open source' BZFlag version (server and client) which is guaranteed to be compatible with all other BZFlag versions.
|(Unknown)
|
*BZFlag is already open-source, and making a universally-compatible client is not even remotely practical. Incompatibility is part of why the game breaks off new versions in the first place. [[User:L4m3r|L4m3r]]
|Orca
|(Old)
|-
|}
</div>

== Game Modes, Team Play, and Scoring ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Tounament mode
|style="background-color:#808080;"|Idea
|
*Great Idea?
|(Unknown)
|(Old)
|-
|When you shoot someone on your own team, instead of both of you blowing up, neither is destroyed, and their score goes up one, while your's goes down one. This would make teamkilling impossible and greatly discourage traitors as well.
|style="background-color:#808080;"|Idea
|
*But then couldn't cheaters spawn two clients and ramp up their scores by teamkilling their other login? --YHARG
|Trigger Happy Nerd
|(Old)
|-
|A new gameplay mode- Takes two to tank. One to control the (rotating) turret, the other drives. KIA switches positions. "Teamplay" but all in one tank.
|(Unknown)
|
*I see serious lag issues with this... How does Halo do it? ;) -L4m3r
*The main problem with this idea is coordination. If one person were to leave, the tank would be crippled. You COULD solve this by having the person switch to normal mode, but this could cause considerable jerking between modes on a busy server. [[User:F687s|F687s]] 22:13, 20 June 2007 (EDT)
|MORPH
|(Old)
|-
|Turret mode, If enabled by the server (Can be manditory with automatic grouping). One user drives and the other shoots, Turret mode tanks get double points (But onyl take one from the target). lost double points if killed. Have double ammo, And controllable speed (Max = _tankSpeed * 2 Min = _tankSpeed). Plus it takes 2 shots to kill a turret mode tank. Points gained and lost by turret tanks are divided evenly between the users, Unless the server is all turret mode, in h which case two users are displayed as one.
|(Unknown)
|
|Dogbert
|(Old)
|-
|Ability for a team to vote to 'banish' someone from their team
|style="background-color:#808080;"|Idea
|
*Possibly unfair to newer players. [[User:L4m3r|L4m3r]]
*Useful for getting rid of TKers and selfcappers. However you would need a way (e.g. a voting system) and you would need to be able to say to which team he or she should go if rogues are unavailable. Possible, if rogues are allowed, but not otherwise not really a good idea. --[[User:88.108.209.168|88.108.209.168]] 13:13, 24 December 2007 (EST)
|MORPH
|(Old)
|-
|There should be a game of cops and robbers. The teams can change after about 10 mins or so.
|style="background-color:#FFFF00;"|(Unknown)
|
|iPod
|(Old)
|-
|A special FFA Game mode "Team by Flags". This means, same Flag = same Team, so if there is a Tank with Rapid fire, and you pick up Rapid fire, you are automatically handled as Team member (this means, killing the other Tank with Rapid fire will be handled the same way as when killing a team member). YHARG: Funky idea: what about a game mode where teams shared flag abilities? Like, each player on a team's flag applies to the whole team. This could make for some interesting combos...
|(Unknown)
|
|Agonizer
|(Old)
|-
|Make life trickier for the Rogue Team; with a mix of Rogues and Colored Teams, the Rogues have more targets. This should also change the effect of the Masquerade flag - perhaps your tank is invisible to Rogues (like Cloaking)?
|(Unknown)
|
|NickGrim
|(Old)
|-
|A server option to make deaths not affect your score unless they were self-inflicted/team (the method used by many online games). This would encourage more aggressive play, because it's worth going out and blasting. As it is, you've got a very good chance by just phantoming/OOing out of the way and keeping you score at zero to stay in the top three places! It would also help fix the rather unfair situation of spawning just below a building on which someone is GM-camping...there's pretty much no way to escape, so you lose a point.
|(Unknown)
|
|LionsPhil
|(Old)
|-
|Don't show individual score in CTF games. This might help teamplay as it reduces the incentive to run around as if it would be FFA.
|(Unknown)
|
|abli
|(Old)
|-
|Give points to the player how captures flag in CTF. (Say, around 4 or so) After all, it is often a bigger job than killing someone.
|(Unknown)
|
*Maybe the score could be based the number of tanks in the other team, similar to shooting someone w/ geno. This can also discourage people from capturing thier own flag by scoreing the negative number of teamates. I'm not sure if the individual scores of the players of the captured team (other than the one who captures the flag) should be affected however. [[User:Sparky1|Sparky1]] 09:44, 21 May 2007 (EDT)
*Scores can be customized with plug-ins in 3.0. Unfortunately, there's a bug in 2.0.x that prevents the server from setting scores properly. [[User:L4m3r|L4m3r]] 01:46, 5 January 2008 (EST)
|abli
|(Old)
|-
|Ducati/Freestyle "Roles" mode: Make a game mode where players are presented with a list of flag choices (limitable to a few roles, if wanted) at respawn or connect time, and are forced to use this flag for the remainder of their connection/tank life. This would be really useful in the case of stealth vs. seer, where you could choose to be stealth or seer, but couldn't switch between them. Another idea would be high speed vs. quick turn. Or steamroller vs. machine gun... Team play would have the interesting effect of people banding together and people with each role on the team. Especially in stealth vs. seer, where a seer team member could warn the team about enemies! There would be no team flags/bases.
|(Unknown)
|
*Too specialized, use a plug-in (yes, it's possible). [[User:L4m3r|L4m3r]] 01:46, 5 January 2008 (EST)
|YHARG
|(Old)
|-
|New game called tag were someone is it and they shoot someone else and there it and ect.
|(Unknown)
|
|Supermatthew
|(Old)
|-
|Also a new game called "Hide and seek" were everyone is clocked(think thats it, were you don't see them on radar) except one who is it. he needs to find someone and shoot them then hese cloked and who was shot is not. Also when someone is shot there sent back to Ground zero( 0X, 0Y, 0Z ) so they can't shoot who ever just shot them.
|(Unknown)
|
|Supermatthew
|(Old)
|-
|"Cat" game: when a player dies, he/she respawns automaticaly, after 3 secs or so. When they have respawned 9 times, they can no longer spawn, and are observers. The one who lasts the longest wins. Games are timed.
|(Unknown)
|
|(Unknown)
|4/20/2007
|-
|A switch-teams function that allows you to swap teams during a game without losing score.
|(Unknown)
|
|jftsang
|10/11/2007
|-
|Rogue team - A mode in which rogues may TK and capture flag.
|(unknown)
|
*Why? [[User:L4m3r|L4m3r]] 01:46, 5 January 2008 (EST)
|jftsang
|10/11/2007
|-
|}
</div>

== Maps, Mapping, and BZW ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Materials that don't allow OO and PZ to go through
|style="background-color:#808080;"|Idea
|
*Would be nice for multilevel worlds made with the new ability to have objects above the ground.
*Sounds awesome! TD-Linux 17:41, 12 March 2007 (EDT)
*As a special case, there could be Zoned objects (objects that only respond to PZ and maybe OO; normal tanks behave like PZ through these objects). [[User:Sparky1|Sparky1]] 18:05, 21 May 2007 (EDT)
*Would also be nice if there were non-ricochet materials, or only ricochet some shot type materials. --[[User:88.108.209.168|88.108.209.168]] 13:09, 24 December 2007 (EST)
|(Unknown)
|(Old)
|-
|Differently-shaped teleporters (circles, triangles, etc.)
|style="background-color:#808080;"|Idea
|
*probably low priority
|MORPH
|(Old)
|-
|360 degree teleports - hit a spot on the ground or in the air from any direction and you teleport
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Configurable random teleporters - teleports to a different location every time
|style="background-color:#808080;"|Idea
|
*Idea is a bit vague... randomized teles are implemented if you use multiple links. Is this what is meant by this suggestion? -L4m3r
|MORPH
|(Old)
|-
|Triggers in levels
|style="background-color:#FFFF00;"|(Unknown)
|
*Triggers for what? unless you're talking about AI, this could most likely be handled with a server plug-in. [[User:L4m3r|L4m3r]]
|Dragonstar
|(Old)
|-
|wraparound world - radar remains centered on your current position. Internally, objects leaving the north border reappear to the south, but from the user's radar / visible perspective, you just see to the horizon. I believe this is how the original Battlezone worked. There are some implications: laser would need a range limit.
|(Unknown)
|
|nsayer
|(Old)
|-
|As a generalization to the wraparound world concept, how about the option of making a map based on geometry that’s non-Euclidean, for example spherical or hyperbolic. Jumping/flying, the shape of the tanks/objects, and bullet trajectories would also be affected by this global geometry. It would be like a world that has a high gravitational field, or a world situated near a wormhole.
|(Unknown)
|
|[[User:Sparky1|Sparky1]]
|5/21/2007
|-
|-
|Get rid of the PZ flag and replace it w/ special telporters that do the same thing (they could be called "zoners", and should probably look different from regular teleporters). This way superflags, badflags, and team flags can all be zoned (without needing an exception to the restricition against using more than one flag at a time). The above idea of other zoned objects would play a major role here. Zoned flags can only be picked up by zoned tanks. Flags can spawn zoned, or become zoned by being carried by an unzoned tank that becomes zoned by going through a zoner. Likewise, a zonedflag becomes unzoned when a zoned tank carries it through a zoner. Unzoned tanks respond to shots from zoned flags the same way zoned tanks respond to shots from unzoned flags. For example: when zoned, L, WG, geno, and GM do not kill unzoned tanks (zoned GM will still lock onto any tank, and zoned geno would still kill every tank on the same team as the zoned tank that was shot). Although, flags like SW and SB would still kill any tank regardless of thier zoning status. As an extension to this idea one team in a CTF game could start out zoned, i.e. thier base is zoned and they initially spawn zoned. In order for the unzoned team to capture the zoned team's flag, the flag must become unzoned, and vice versa for the zoned team. This way new possibilities exist, like two bases could be superimposed as long as one base is zoned and the other is not. Another possible extension is different kinds of zones (w/ corespondingly different kinds of zoners) for CTF involving more than two teams. The relationship between differently zoned tanks would be the same as the relationship between zoned and unzoned tanks.
|(Unknown)
|
|[[User:Sparky1|Sparky1]]
|5/21/2007
|-
|-
|Change the workings of zones such that a zone may have its own server variables (I wanted to make a Death Castle against a Holy Castle).
|(Unknown)
|
|jftsang
|1/12/2007
|-
|-
|Allow dynamic map objects, such as a moving box that ricochets off and tanks can seek cover behind.
|(Unknown)
|
|jftsang
|1/12/2007
|}
</div>

== Server Options, Administration, Plug-ins, and the Plug-in API ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Ability to configure server to turn somethings off or on depending on number of players - for instance, turn off ricochet after a certain number of players are connected, turn off GM & laser if a certain number of players aren't playing (GM & Laser with 2 players is kinda ridiculous)
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Allow custom-made weapons with a Object-Oriented scripting language (sorta like Liero AI uses: http://helios.et.put.poznan.pl/~sskowron/liero/index.html )
|(Unknown)
|
|Dragonstar
|(Old)
|-
|Preset world weapons that can be fired manually by admins from within BzFlag.
|(Unknown)
|
* Could be done by a plugin [[User:Tanner|Tanner]] 13:42, 12 August 2007 (EDT)
|Dogbert
|(Old)
|-
|}
</div>

== Graphics & Sound ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Sounds of tanks moving.
|(Unknown)
|
|iPod
|(Old)
|-
|Have different tank death scenes for the dying tank point of view. I realize there is some time needed for one to die and respawn, but the jumping effect one sees when killed irritates me to no end! I'd be happier if all faded to black or white or orange and had text across the screen saying ""respawning... please wait"" :) Also, when killed and your tank was moving toward a building, it just falls right thru it until it hits the ground.. wrong physics there! Splatter or tumble or shatter or something :)
|(Unknown)
|
|Robi
|(Old)
|-
|Custom color schemes for rogue players. The turret and body components can be chosen to be one of a predefined set of colors (e.g. red, yellow, black, white, blue, green, purple...). The game prohibits choosing a color scheme that matches a team scheme (e.g. red turret with red body) and the limited set stops someone choosing a shade which is nearly a team color (e.g. 0xFE0000 instead of 0xFF0000) (and also save texture memory, I think).
|(Unknown)
| * Clients are able to define their own colors, and removing the ability to would cause accessibility issues (Colorblind users). --[[User:AAA|AAA]] 13:30, 7 August 2007 (EDT)
|LionsPhil
|(Old)
|-
|Allow a small decal on the back of the top of the tank. (think Half-Life's customizable spraypaint). Possibly also apply it to any held flag?
|(Unknown)
|
|LionsPhil
|(Old)
|-
|I'd like to see something more interesting done with the sky... maybe there could be a little ufo (easter egg) that would fly around occasionally? Tux on a ufo! ;)
|(Unknown)
| This is up to servers. --[[User:AAA|AAA]] 13:30, 7 August 2007 (EDT)
|YHARG
|(Old)
|-
|Flag decals: Each flag would have a little icon/decal showing it's type ONLY when held by a player. It's kind of nice to be able to surprise people with an undercover shockwave, but doesn't make sense to have to right click (identify) or check the user list to see what flag someone has.
|(Unknown)
|
|YHARG
|(Old)
|-
|Background music! : (This can be done with an external media player so it shouldn't be the heighest priority, It would be nice to be able to control your music from within BzFlag)
|(Unknown)
|More usefully, you could just map key combinations to commands, rather than wasting time supporting all the various music players on every OS BZFlag supports. I don't know whether that would work so well on Windows, though. --[[User:77.97.207.100|77.97.207.100]] 10:14, 30 May 2007 (EDT)
|YHARG
|(Old)
|-
|}
</div>

== List Server and Other Global Services ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Multiple list servers, in case bzflag.org goes down (as it happened around feb. 15. 2004)
|(Unknown)
|Of course someone would need to pay for it. --[[User:BinarySpike|BinarySpike]] 18:10, 10 May 2007 (EDT)
|abli
|(Old)
|-
|}
</div>

[[Category:Development]]

Ideas

2008-01-05T06:38:17Z

L4m3r: /* General/Gameplay */ Comments

{{Old}}
NOTE: These are just possibilities. We won't be implementing everything here.<br>

Commentary may include personal comments by developers.

= Editing this page =

Feel free to make changes and updates to this page whenever possible. If you have any questions, feel free to [[Getting Help|ask for help]]. If you wish to make major changes to this page (i.e. remove large amounts of old ideas), please warn us ahead of time.

== Adding ideas ==
* Please remember to make sure your idea isn't already here or on the [[Rejected Ideas]] page.
* Flag ideas should be placed on [[Flag Ideas]], not here.
* Add a row to the appropriate category (at the bottom, please) and fill it in with your idea.
* Sign your idea in the third column with three tildes: <nowiki>~~~</nowiki>
* Put the submission date in the fourth column
* Describe in full and make sense!
* Leave the status column white and fill it with (Unknown).

== Adding commentary ==
* Precede your comment with an asterisk: <nowiki>*</nowiki>
* Sign your comment with four tildes: <nowiki>~~~~</nowiki>
* Be nice, polite, and constructive.
* Contribute something when you comment. Saying whether or not you like an idea is pointless if you don't explain yourself.

== Cleaning up ==
To help keep this page current, old ideas should be removed when they're implemented (after each stable release, hence the "SVN" status). If you spot any ideas that were implemented prior to the latest stable release of BZFlag, please remove it.

= The list =
<div align="center">
{| cellpadding="10" cellspacing="1" border="1"
|+align="bottom"|''Legend''
|-
|style="background-color:#FF00FF;"|'' ''
|Implemented as a server-side plug-in
|-
|style="background-color:#0080FF;"|'' ''
|SVN (Implemented and will be in next release)
|-
|style="background-color:#00FFFF;"|'' ''
|In progress (Implementing)
|-
|style="background-color:#00FF00;"|'' ''
|Good Idea
|-
|style="background-color:#808080;"|'' ''
|Idea
|-
|style="background-color:#FFFF00;"|'' ''
|Vague, not understood, or in need of work
|-
|style="background-color:#FF8000"|'' ''
|Rejected, but can be implemented as a server plug-in
|-
|style="background-color:#FF0000;"|'' ''
|Rejected
|-
|style="background-color:#FFFFFF"|'' ''
|Unknown (new)
|}
</div>

== General/Gameplay ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Add support for 5 (or more) button mice
|style="background-color:#00FF00;"|Great Idea
|
|(Unknown)
|(Old)
|-
|Better physics
|style="background-color:#00FFFF;"|In progress
|
*Planning, some changes in CVS.
|Unknown
|(Old)
|-
|SELF-DESTRUCT BLAST RADIUS: Self Destruct (delete key) should have a blast radius similar to Shock Wave, perhaps larger. If you get shot during the self-destruct count down, that should also trigger the same blast. If I gotta go, I want to take someone with me.
|(Unknown)
|
|BearRiver
|(Old)
|-
|3-second (or however long) 'invulnerability' for incoming tanks - but they can't shoot
|style="background-color:#808080;"|Idea
|
*I could see this backfiring... your spawn attracts opponents to come, wait, and blast you when you lose invincibility. -L4m3r
|MORPH
|(Old)
|-
|Ability to turn off ricochet for laser flag but allow ricochet for bullets... or let them bounce only n times.. OR implement mirror buildings/walls. Should go for some interesting self-kills when combined with the no-radar/bullet bounce
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Smart LockOn for GM - won't lock on to your teammates (configurable in server)
|style="background-color:#808080;"|Idea
|
*I don't like this idea, there should be at least *some* risks to using this weapon. Personally, I think there should be more (not fewer) risks to holding this weapon; I'd like to see the thing overheat and explode (killing the holder) if it's fired too often in a short period of time. -M. Jetleb

*2.99 has an option to disable friendly fire altogether. Close enough. Lock-on could still be looked into, however. [[User:L4m3r|L4m3r]] 01:38, 5 January 2008 (EST)
|MORPH
|(Old)
|-
|Small jumps
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Server option for genocide flag - if you're killed while you have it, your team dies :^)
|style="background-color:#808080;"|Idea
|
*Feasible with a plug-in, too. -L4m3r
|MORPH
|(Old)
|-
|for broadband or LAN connections - voice chat for teams
|style="background-color:#808080;"|Idea
|
*I really think that you can do this with another service; I'm not sure if being part of BZFlag would be a good idea due to size and bandwidth issues.
|MORPH
|(Old)
|-
|Tank avatars (uploadable tank images) - have to think about shapes, though - someone could make a 1x1x1 pixel tank - that would suck - or a tank that looks like a building or pyramid. Clients don't have to accept downloading of avators (just view other tanks in default mode). Or just s-e-l-e-c-t from a certain number of predefined avatars that could come with the bzflag distribution. Or client provides a URL to download their avatar (saves server bandwidth).
|style="background-color:#808080;"|Idea
|*Might not be implemented. Requires discussion; we may want to consider making the computer force a minimum size or something similar.
*How about uploadable flag graphics?
|MORPH
|(Old)
|-
|'Kamikaze' option for players - can take someone out by suicide
|style="background-color:#808080;"|Idea
|
*Server option if implemented.
*Implemented with a plugin by Theme97
|MORPH
|(Old)
|-
|Server option: everyone is radar-stealthed by default unless you get a 'radar' flag. You can still see all buildings, pyramids, teleports, and arena walls, though.
|style="background-color:#00FF00;"|Good idea
|
*Make them use their window. ;)
*Given the fairly narrow field of view out the window and the time it takes to turn a tank all the way around for a look-see, I think this could be frustrating. How about everyone starts out with minimum range radar instead and gets longer ranges with an appropriate flag? -M. Jetleb
*Ideally this could be implemented in the same manner as jumping and ricochet- radar could be enabled by default, or available as a flag. [[User:L4m3r|L4m3r]] 01:38, 5 January 2008 (EST)
|MORPH
|(Old)
|-
|Option for above: if you pick up GM or Laser, you're visible on radar to everyone whether they've got a radar flag or not
|style="background-color:#00FF00;"|Good idea
|
|MORPH
|(Old)
|-
|Selectable 'ricochet' fire - hold down shift key or something and your bullets won't ricochet
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Server option - tanks only have a certain number of times they can jump (gets reset when you get killed)
|style="background-color:#808080;"|Idea
|
*Could be made possible with a plug-in in 2.99. [[User:L4m3r|L4m3r]] 01:38, 5 January 2008 (EST)
|MORPH
|(Old)
|-
|Multiple-shields (server option for shield flags, or can be random - can get hit x number of times)
|style="background-color:#808080;"|Idea
|*This is pretty much moot now. It's been shot down by the devs at least once, and a similar effect can be achieved by setting _shieldFlight to a very small number. This effectively provides as many hits as _maxFlagGrabs. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|Configurable 'radarless' and/or 'blind' zones in the arena - can't see what's in there on radar or via visuals
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Tank collisions - why can tanks drive through each other? Weird.
|style="background-color:#00FF00;"|Good Idea
|*Lag could be a big problem here. If implemented, it must be impossible for two tanks to get stuck to each other. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|When tanks collide - great opportunity to implement tank damage concept, especially if one of them is moving especially fast, or has momentum flag, etc. Can push a tank off a building if your pushing them from their side.
|style="background-color:#808080;"|Idea
|
*Tank damage won't happen, but the kinetics could be neat, especially for mid-air collisions. It would certainly make "jump dancing" more interesting. [[User:L4m3r|L4m3r]]
|Morph
|(Old)
|-
|If a tank explodes right next to another tank, the other tank can be destroyed or get damaged
|style="background-color:#808080;"|Idea
|
*Somewhat implemented with the [[ShockwaveDeath]] plug-in. It would probably not be too hard to implement something similar (with a plugin) without shockwaves. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|Skins or views- In-tank mode, bumper mode, out-of-cab mode, chase mode.
|(Unknown)
|
|MORPH
|(Old)
|-
|Weapon extension packs.
|style="background-color:#FFFF00;"|(Unknown)
|*Huh? Explain, please. [[User:L4m3r|L4m3r]]
|iPod
|(Old)
|-
|The ability to choose tanks, but they all die at one shot. maybe the jump height, speed, turn speed, acceleration, size can be preset.
|(Unknown)
|
*Could be done with a plug-in in 2.99, maybe. [[User:L4m3r|L4m3r]] 01:38, 5 January 2008 (EST)
|iPod
|(Old)
|-
|Option to choose different kinds of tanks. Different tanks could be weighted with different strengths and weaknesses. (almost like having a default flag). Would also need some form of health/damage status measurement, not just single hits. For example, there could be a larger, heavily armored tank that has powerful weapons, but moves slowly, versus a small, light, fast tank which is difficult to hit, but very low armor to protect from hits.
|(Unknown)
|
|Cue
|(Old)
|-
|What about a radar that only covers visible areas (don't passing through buildings/pyramids) ? This would leads to more placement tactics).
|(Unknown)
|
|K<nowiki>'</nowiki>limero
|(Old)
|-
|Always random respawn. Currently in CTF games first respawn is at own base. This can be abused by leaving and rejoining to get near base. This leave/rejoing trick is considered to be a mild form of cheating by many. Always random respawn would make it useless.
|(Unknown)
|
* I believe there is a plug-in for this. [[User:L4m3r|L4m3r]] 22:38, 30 April 2007 (EDT)
|abli
|(Old)
|-
|multiple (3?) jump stengths mini, normal, max...just the thing to confuse the opponents that expect one and you're off doing the other.
|(Unknown)
|
|kitchen
|(Old)
|-
|Anti camping. The ability to add "no camping zones" to areas of a map or to the entire map. Campers would be messaged that they're in a no camping zone, better start moving and have a prescribe number of seconds to move away or die. If a player returns to the same NCZ (no camping zone) and receives x warnings then he's disconnected. NCZs could be marked by a different color shade from a "normal" spot and could be exempt to a single team (like at their flag base). It's just a rough idea.
|(Unknown)
|
*Definitely more suited to a plug-in (and probably doable, too).
|pherris
|(Old)
|-
|Shield Flag Changes: Give Shield flag a radius, and draw it like a moving less opaque blue shockwave. Any tanks inside the shield radius would be protected, until the shield got hit a certain number of times.
|(Unknown)
|
|YHARG
|(Old)
|-
|At our company, we instituted a voluntary policy of dropping flags after 1 kill. Prevents slaughters and keeps things rolling more. It'd be great to be able to have the game do this for us, plus I'd love to see it turned on at external sites.
|(Unknown)
|
|TomMatelich
|(Old)
|-
|Server option: default powers -- flag(s) that everyone in the game automatically has (this wouldn't count as holding a flag). For example, the current Jumping option would == including Jumping as a default power.
|(Unknown)
|
|NebNamwen
|(Old)
|-
|Shot Aiming. Basically the center shot aim box could be moved left and right as far as the edge of the view window. (This would be enabled by default.) If the map is a vertical one a server option could be enabled so that vertical aiming could be enabled (using the same concept as horizontal aiming.) The aiming would be automatically centered by a button or key. These options could be mapped to a second joystick access, mouse scroll wheel or keyboard buttons.
|(Unknown)
|Lateral shooting would basically be the same as a rotating turret, and this idea has been shot down many times. Vertical shooting has been poo-pooed also. [[User:L4m3r|L4m3r]] 01:45, 3 July 2007 (EDT)
|NN
|6/20/07
|-
|Make a tele porter along the game sides that would tele port into other games running on their own servers. This would enable larger more collaborative game board linked together that would distribute loads across multiple servers speeding up game play and making for interesting possibilities.
|(Unknown)
|
|Waban*
|7/31/07
|-
|Make a 'fog of war' where the a player's radar only shows a certain distance of the area around them and their teammates'.
|(Unknown)
|
*This could be done if radar and position data were separated, allowing the server to "filter" radar data for each player.
|Forrest
|8/19/07
|}
</div>

== UI ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Make option to show previous players list
|style="background-color:#808080;"|Idea
|
|(Unknown)
|(Old)
|-
|Make ALL server options available from the menus
|style="background-color:#808080;"|Idea
|
*There are a LOT of server options, and this could add quite a bit of clutter. If you need more than a basic game, you should probably learn to start BZFS from the command line anyway. -L4m3r
|MORPH
|(Old)
|-
|Separate windows for player messages & server messages
|style="background-color:#00FF00;"|Good idea.
|
|MORPH
|(Old)
|-
|Message log
|style="background-color:#00FF00;"|Good idea.
|
|MORPH
|(Old)
|-
|Send message to everyone 'but' specified player (crosses team boundaries, or not)
|style="background-color:#808080;"|Idea
|
*Hmm. Everybody BUT a specified player? [M. Jetleb -> as in: "Let's all get the GM guy" without the GM guy knowing he's facing a co-ordinated attack - I like this idea)
|MORPH
|(Old)
|-
|The ability to see what the world is like before connecting to the server.
|(Unknown)
|
|iPod
|(Old)
|-
|Multi-monitor support (i.e., radar on one screen, window on another, chat/event log on a third)
|(Unknown)
|
|bhtooefr
|(Old)
|-
|Make a part in bzflag to put up a real server. 1st screen has the flags you want, next page is to find the MAP file that you created on your hard drive, next page pick if you want jumping etc.
|(Unknown)
|
|Colin
|(Old)
|-
|-
|Add a rear view mirror
|(Unknown)
|
|Sparky1
|1/1/2008
|-
|}
</div>

== Technical ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Better network handling
|style="background-color:#00FFFF;"|In progress
|
|(Unknown)
|(Old)
|-
|Better robot AI
|style="background-color:#808080;"|Idea
|
*Don't know if players would like it or not in multiplayer game. Pluggable or scriptable robot AI , maybe? - Code must be restructured first
*Server side bots are coming! [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT)
|(Unknown)
|(Old)
|-
|Better positioning of tanks
|style="background-color:#808080;"|Idea
|
*BZFlag already does this, but the algorithm is bad. Needs work.
|MORPH
|(Old)
|-
|Serious multithreaded design - shouldn't lock up interface while looking for servers, or doing anything else. This program is way-unstable on Windows
|style="background-color:#00FFFF;"|In Progress
|
*We're working on these problems; many complaints are due to people still using old servers/clients.
|MORPH
|(Old)
|-
|Some type of BZFlag GUID* to ban players who cheat - won't accept players who disable their GUID, etc.

<nowiki>*</nowiki>Global Unique Identifier, sort of like an IP addrss, but permanent. Usually a number. Problem occurs when you lose your GUID (have to reformat your HD, etc. How do you keep someone from hacking their GUID, or setting up a modified BZFlag server for identity theft, etc.
|(Unknown)
|
*I doubt this is even possible, let alone practical. What about people who play from more than one location? And, because this is an open-source game, it would probably be cracked in minutes. Any verification can be spoofed, or at least altered. there is no foolproof way to permanently ban someone. -L4m3r
|MORPH
|(Old)
|-
|To prevent cheating - the server determines what flags & abilities each tank has (possible?)
|style="background-color:#00FF00;"|In Progress
|
*Seriously being considered. This would also have the advantage of allowing different versions of clients and servers to work together. Yes, it's possible, but this type of change will mean a change in the network protocols.
*Being worked on for 2.2
|MORPH
|(Old)
|-
|BZFlag for mac in separate data and application files.
|(Unknown)
|
|iPod
|(Old)
|-
|J2ME client (allows one to play on a cell phone), would use radar
|(Unknown)
|
|bhtooefr
|(Old)
|-
|Special 'open source' BZFlag version (server and client) which is guaranteed to be compatible with all other BZFlag versions.
|(Unknown)
|
*BZFlag is already open-source, and making a universally-compatible client is not even remotely practical. Incompatibility is part of why the game breaks off new versions in the first place. [[User:L4m3r|L4m3r]]
|Orca
|(Old)
|-
|}
</div>

== Game Modes, Team Play, and Scoring ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Tounament mode
|style="background-color:#808080;"|Idea
|
*Great Idea?
|(Unknown)
|(Old)
|-
|When you shoot someone on your own team, instead of both of you blowing up, neither is destroyed, and their score goes up one, while your's goes down one. This would make teamkilling impossible and greatly discourage traitors as well.
|style="background-color:#808080;"|Idea
|
*But then couldn't cheaters spawn two clients and ramp up their scores by teamkilling their other login? --YHARG
|Trigger Happy Nerd
|(Old)
|-
|A new gameplay mode- Takes two to tank. One to control the (rotating) turret, the other drives. KIA switches positions. "Teamplay" but all in one tank.
|(Unknown)
|
*I see serious lag issues with this... How does Halo do it? ;) -L4m3r
*The main problem with this idea is coordination. If one person were to leave, the tank would be crippled. You COULD solve this by having the person switch to normal mode, but this could cause considerable jerking between modes on a busy server. [[User:F687s|F687s]] 22:13, 20 June 2007 (EDT)
|MORPH
|(Old)
|-
|Turret mode, If enabled by the server (Can be manditory with automatic grouping). One user drives and the other shoots, Turret mode tanks get double points (But onyl take one from the target). lost double points if killed. Have double ammo, And controllable speed (Max = _tankSpeed * 2 Min = _tankSpeed). Plus it takes 2 shots to kill a turret mode tank. Points gained and lost by turret tanks are divided evenly between the users, Unless the server is all turret mode, in h which case two users are displayed as one.
|(Unknown)
|
|Dogbert
|(Old)
|-
|Ability for a team to vote to 'banish' someone from their team
|style="background-color:#808080;"|Idea
|
*Possibly unfair to newer players. [[User:L4m3r|L4m3r]]
*Useful for getting rid of TKers and selfcappers. However you would need a way (e.g. a voting system) and you would need to be able to say to which team he or she should go if rogues are unavailable. Possible, if rogues are allowed, but not otherwise not really a good idea. --[[User:88.108.209.168|88.108.209.168]] 13:13, 24 December 2007 (EST)
|MORPH
|(Old)
|-
|There should be a game of cops and robbers. The teams can change after about 10 mins or so.
|style="background-color:#FFFF00;"|(Unknown)
|
|iPod
|(Old)
|-
|A special FFA Game mode "Team by Flags". This means, same Flag = same Team, so if there is a Tank with Rapid fire, and you pick up Rapid fire, you are automatically handled as Team member (this means, killing the other Tank with Rapid fire will be handled the same way as when killing a team member). YHARG: Funky idea: what about a game mode where teams shared flag abilities? Like, each player on a team's flag applies to the whole team. This could make for some interesting combos...
|(Unknown)
|
|Agonizer
|(Old)
|-
|Make life trickier for the Rogue Team; with a mix of Rogues and Colored Teams, the Rogues have more targets. This should also change the effect of the Masquerade flag - perhaps your tank is invisible to Rogues (like Cloaking)?
|(Unknown)
|
|NickGrim
|(Old)
|-
|A server option to make deaths not affect your score unless they were self-inflicted/team (the method used by many online games). This would encourage more aggressive play, because it's worth going out and blasting. As it is, you've got a very good chance by just phantoming/OOing out of the way and keeping you score at zero to stay in the top three places! It would also help fix the rather unfair situation of spawning just below a building on which someone is GM-camping...there's pretty much no way to escape, so you lose a point.
|(Unknown)
|
|LionsPhil
|(Old)
|-
|Don't show individual score in CTF games. This might help teamplay as it reduces the incentive to run around as if it would be FFA.
|(Unknown)
|
|abli
|(Old)
|-
|Give points to the player how captures flag in CTF. (Say, around 4 or so) After all, it is often a bigger job than killing someone.
|(Unknown)
|*Maybe the score could be based the number of tanks in the other team, similar to shooting someone w/ geno. This can also discourage people from capturing thier own flag by scoreing the negative number of teamates. I'm not sure if the individual scores of the players of the captured team (other than the one who captures the flag) should be affected however. [[User:Sparky1|Sparky1]] 09:44, 21 May 2007 (EDT)
|abli
|(Old)
|-
|Ducati/Freestyle "Roles" mode: Make a game mode where players are presented with a list of flag choices (limitable to a few roles, if wanted) at respawn or connect time, and are forced to use this flag for the remainder of their connection/tank life. This would be really useful in the case of stealth vs. seer, where you could choose to be stealth or seer, but couldn't switch between them. Another idea would be high speed vs. quick turn. Or steamroller vs. machine gun... Team play would have the interesting effect of people banding together and people with each role on the team. Especially in stealth vs. seer, where a seer team member could warn the team about enemies! There would be no team flags/bases.
|(Unknown)
|
|YHARG
|(Old)
|-
|New game called tag were someone is it and they shoot someone else and there it and ect.
|(Unknown)
|
|Supermatthew
|(Old)
|-
|Also a new game called "Hide and seek" were everyone is clocked(think thats it, were you don't see them on radar) except one who is it. he needs to find someone and shoot them then hese cloked and who was shot is not. Also when someone is shot there sent back to Ground zero( 0X, 0Y, 0Z ) so they can't shoot who ever just shot them.
|(Unknown)
|
|Supermatthew
|(Old)
|-
|"Cat" game: when a player dies, he/she respawns automaticaly, after 3 secs or so. When they have respawned 9 times, they can no longer spawn, and are observers. The one who lasts the longest wins. Games are timed.
|(Unknown)
|
|(Unknown)
|4/20/2007
|-
|A switch-teams function that allows you to swap teams during a game without losing score.
|(Unknown)
|
|jftsang
|10/11/2007
|-
|Rogue team - A mode in which rogues may TK and capture flag.
|(unknown)
|
|jftsang
|10/11/2007
|-
|}
</div>

== Maps, Mapping, and BZW ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Materials that don't allow OO and PZ to go through
|style="background-color:#808080;"|Idea
|
*Would be nice for multilevel worlds made with the new ability to have objects above the ground.
*Sounds awesome! TD-Linux 17:41, 12 March 2007 (EDT)
*As a special case, there could be Zoned objects (objects that only respond to PZ and maybe OO; normal tanks behave like PZ through these objects). [[User:Sparky1|Sparky1]] 18:05, 21 May 2007 (EDT)
*Would also be nice if there were non-ricochet materials, or only ricochet some shot type materials. --[[User:88.108.209.168|88.108.209.168]] 13:09, 24 December 2007 (EST)
|(Unknown)
|(Old)
|-
|Differently-shaped teleporters (circles, triangles, etc.)
|style="background-color:#808080;"|Idea
|
*probably low priority
|MORPH
|(Old)
|-
|360 degree teleports - hit a spot on the ground or in the air from any direction and you teleport
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Configurable random teleporters - teleports to a different location every time
|style="background-color:#808080;"|Idea
|
*Idea is a bit vague... randomized teles are implemented if you use multiple links. Is this what is meant by this suggestion? -L4m3r
|MORPH
|(Old)
|-
|Triggers in levels
|style="background-color:#FFFF00;"|(Unknown)
|
*Triggers for what? unless you're talking about AI, this could most likely be handled with a server plug-in. [[User:L4m3r|L4m3r]]
|Dragonstar
|(Old)
|-
|wraparound world - radar remains centered on your current position. Internally, objects leaving the north border reappear to the south, but from the user's radar / visible perspective, you just see to the horizon. I believe this is how the original Battlezone worked. There are some implications: laser would need a range limit.
|(Unknown)
|
|nsayer
|(Old)
|-
|As a generalization to the wraparound world concept, how about the option of making a map based on geometry that’s non-Euclidean, for example spherical or hyperbolic. Jumping/flying, the shape of the tanks/objects, and bullet trajectories would also be affected by this global geometry. It would be like a world that has a high gravitational field, or a world situated near a wormhole.
|(Unknown)
|
|[[User:Sparky1|Sparky1]]
|5/21/2007
|-
|-
|Get rid of the PZ flag and replace it w/ special telporters that do the same thing (they could be called "zoners", and should probably look different from regular teleporters). This way superflags, badflags, and team flags can all be zoned (without needing an exception to the restricition against using more than one flag at a time). The above idea of other zoned objects would play a major role here. Zoned flags can only be picked up by zoned tanks. Flags can spawn zoned, or become zoned by being carried by an unzoned tank that becomes zoned by going through a zoner. Likewise, a zonedflag becomes unzoned when a zoned tank carries it through a zoner. Unzoned tanks respond to shots from zoned flags the same way zoned tanks respond to shots from unzoned flags. For example: when zoned, L, WG, geno, and GM do not kill unzoned tanks (zoned GM will still lock onto any tank, and zoned geno would still kill every tank on the same team as the zoned tank that was shot). Although, flags like SW and SB would still kill any tank regardless of thier zoning status. As an extension to this idea one team in a CTF game could start out zoned, i.e. thier base is zoned and they initially spawn zoned. In order for the unzoned team to capture the zoned team's flag, the flag must become unzoned, and vice versa for the zoned team. This way new possibilities exist, like two bases could be superimposed as long as one base is zoned and the other is not. Another possible extension is different kinds of zones (w/ corespondingly different kinds of zoners) for CTF involving more than two teams. The relationship between differently zoned tanks would be the same as the relationship between zoned and unzoned tanks.
|(Unknown)
|
|[[User:Sparky1|Sparky1]]
|5/21/2007
|-
|-
|Change the workings of zones such that a zone may have its own server variables (I wanted to make a Death Castle against a Holy Castle).
|(Unknown)
|
|jftsang
|1/12/2007
|-
|-
|Allow dynamic map objects, such as a moving box that ricochets off and tanks can seek cover behind.
|(Unknown)
|
|jftsang
|1/12/2007
|}
</div>

== Server Options, Administration, Plug-ins, and the Plug-in API ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Ability to configure server to turn somethings off or on depending on number of players - for instance, turn off ricochet after a certain number of players are connected, turn off GM & laser if a certain number of players aren't playing (GM & Laser with 2 players is kinda ridiculous)
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Allow custom-made weapons with a Object-Oriented scripting language (sorta like Liero AI uses: http://helios.et.put.poznan.pl/~sskowron/liero/index.html )
|(Unknown)
|
|Dragonstar
|(Old)
|-
|Preset world weapons that can be fired manually by admins from within BzFlag.
|(Unknown)
|
* Could be done by a plugin [[User:Tanner|Tanner]] 13:42, 12 August 2007 (EDT)
|Dogbert
|(Old)
|-
|}
</div>

== Graphics & Sound ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Sounds of tanks moving.
|(Unknown)
|
|iPod
|(Old)
|-
|Have different tank death scenes for the dying tank point of view. I realize there is some time needed for one to die and respawn, but the jumping effect one sees when killed irritates me to no end! I'd be happier if all faded to black or white or orange and had text across the screen saying ""respawning... please wait"" :) Also, when killed and your tank was moving toward a building, it just falls right thru it until it hits the ground.. wrong physics there! Splatter or tumble or shatter or something :)
|(Unknown)
|
|Robi
|(Old)
|-
|Custom color schemes for rogue players. The turret and body components can be chosen to be one of a predefined set of colors (e.g. red, yellow, black, white, blue, green, purple...). The game prohibits choosing a color scheme that matches a team scheme (e.g. red turret with red body) and the limited set stops someone choosing a shade which is nearly a team color (e.g. 0xFE0000 instead of 0xFF0000) (and also save texture memory, I think).
|(Unknown)
| * Clients are able to define their own colors, and removing the ability to would cause accessibility issues (Colorblind users). --[[User:AAA|AAA]] 13:30, 7 August 2007 (EDT)
|LionsPhil
|(Old)
|-
|Allow a small decal on the back of the top of the tank. (think Half-Life's customizable spraypaint). Possibly also apply it to any held flag?
|(Unknown)
|
|LionsPhil
|(Old)
|-
|I'd like to see something more interesting done with the sky... maybe there could be a little ufo (easter egg) that would fly around occasionally? Tux on a ufo! ;)
|(Unknown)
| This is up to servers. --[[User:AAA|AAA]] 13:30, 7 August 2007 (EDT)
|YHARG
|(Old)
|-
|Flag decals: Each flag would have a little icon/decal showing it's type ONLY when held by a player. It's kind of nice to be able to surprise people with an undercover shockwave, but doesn't make sense to have to right click (identify) or check the user list to see what flag someone has.
|(Unknown)
|
|YHARG
|(Old)
|-
|Background music! : (This can be done with an external media player so it shouldn't be the heighest priority, It would be nice to be able to control your music from within BzFlag)
|(Unknown)
|More usefully, you could just map key combinations to commands, rather than wasting time supporting all the various music players on every OS BZFlag supports. I don't know whether that would work so well on Windows, though. --[[User:77.97.207.100|77.97.207.100]] 10:14, 30 May 2007 (EDT)
|YHARG
|(Old)
|-
|}
</div>

== List Server and Other Global Services ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Multiple list servers, in case bzflag.org goes down (as it happened around feb. 15. 2004)
|(Unknown)
|Of course someone would need to pay for it. --[[User:BinarySpike|BinarySpike]] 18:10, 10 May 2007 (EDT)
|abli
|(Old)
|-
|}
</div>

[[Category:Development]]

Flag ideas

2007-12-17T23:53:09Z

L4m3r: /* List of suggested flags: */ fix b0rked table

== Some simple guidelines ==

=== <span style="color:#cc0000">READ THIS FIRST</span> ===

* First, check that your idea isn't already here. Chances are someone else has already come up with your flag.
* Next, think carefully about your flag. Come up with a short and succinct description. Not only will a short description will make it easier for the project management team to make a decision about the flag, but it usually also indicates the quality of the idea. Chances are if a flag requires more than a short sentence or two, it's too complicated for the game.
* Make sure your flag idea isn't overpowered or stupid.
* Finally, add your flag to the section with the blank 'status' field. Use the teal background color and leave the status blank!
* Note that your flag approved to a "yes" does not mean it will happen. Everything done is what the developers want to do - if a flag requires significant changes to the codebase and isn't the most brilliant idea ever, it'll probably sit here for quite some time before being implemented, if ever.

This is NOT a list of flags that are being considered. Discussion/implementation of these is encouraged, but does not mean any of these flags are going into the game.

If you do implement a flag keep these things in mind:
* All powerful flags aren't fun.
* Flags that ensure your immediate destruction aren't fun.
* Flags that aren't useful aren't fun.
* Flags boost/modulate tactical trait of tanks

Based on these observations we have the following rules:

;Flag power must be limited
:For example, BZFlag has stealth and cloaking flags, but no stealth-and-cloak flag. Such a tank would be virtually impossible to destroy. Nobody likes to play against someone who can't lose.
The guided missile and laser flags are both exceptionally powerful flags, but neither make the owner invincible. Laser takes twice as long to reload and a guided missile can be dodged while still firing on the owner. You've gotta be good, but it can be done.

;Flag powers can counteract/balance each other.
:Some flags are handily defeated with another kind of flag. The oscillation overthruster can be destroyed by a super bullet or a shock wave (or a genocide). Cloaking is effective against laser and stealth is good against guided missile. Ricochet is useful against ricochet.
:Consider adding counterbalancing flags together. Or consider adding a flag that acts as a counterbalance to an existing flag or flags. Also consider making your new flag counterbalanced by an existing flag; superbullet is often a good choice.

;Don't add flags that (almost) instantly kill the owner.
:I considered adding a Death flag that would instantly kill the tank that grabbed it. I changed my mind because that's not fun and seriously dampens interest in picking up flags. Mines are similar. You're driving around and *boom* you're dead. Nothing you could've done to avoid it, no mistake you made. You're just dead. People don't mind losing so much if they know it was because they did something wrong.
:Even worse is a flag that disables your radar and vision. You're basically dead. You can shoot at random and hope to get lucky, but no amount of skill can save you. And what's worse than the Death flag is that you have to stagger around waiting for someone to kill you.
:A flag that seriously disables a tank is not as bad because the player can still use skill to defeat as many enemies as possible before getting shot. Thus we have flags like left turn only and obesity.

;Flags should require new skills
:Flags that require new skills keep the game interesting. If there's still more to learn about using ricochet or guided missile, or more to learn about fighting against them, then people will keep playing.
:Some flags seem pretty dull to some players. The steamroller and the phantom zone come to mind, or quick turn. These aren't the most powerful flags, but they do have their uses and some people enjoy them. However, I think I should have removed SR and PZ. Steamroller's usefulness is very limited and looks pretty weak compared to shock wave. PZ tends to encourage very defensive play, which slows the game down. But quick turn can be very effective when used well; put it in a tight furball and it'll do serious damage. You just have to learn how to take full advantage of it.

== List of suggested flags: ==

{| cellpadding="10" cellspacing="1" border="1"
|+align="bottom" style="color:#e76700;"|''Legend''
|-
|style="background-color:#5BFAFA;"|'' ''
|To be Approved
|-
|style="background-color:#a14141;"|'' ''
|Approved as a not bad idea, but needs research
|-
|style="background-color:#ffff00;"|'' ''
|Rejected
|-
|style="background-color:#41a141;"|'' ''
|Claimed (Implementing)
|-
|style="background-color:#4141a1;"|'' ''
|SVN
|-
|style="background-color:transparent;"|'' ''
|Maybe but there are issues
|}

{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!Name
!+/-
!Status
!Use
|-
|SPinner (SP)
| -
|style="background-color:#5BFAFA;"|'' ''
|If you turn when you have this flag you can't stop turning. Optional: If you leave the tank turning it slowly gets faster and faster, but probably only to a set speed otherwise it would get too fast.
|-
|DoNuts (DN)
| -
|style="background-color:#5BFAFA;"|'' ''
|When you pick up this flag it has the affect of picking up SPinner and Don't Stop, which means the tank doesn't stop spinning and doesn't stop driving. The tank is now driving around in circles like it is doing donuts. Mmmm... Donuts!!
|-
|Looking Around (LA)
| -
|style="background-color:#5BFAFA;"|'' ''
|This makes the camera view spin around but not the tank. It's like you are sitting on the turret and the turret is spinning around, but of course the tank is still facing forward, but this flag WON'T make the turret spin, only the camera you still have to fire forward. This could make the radar spin to the same way you are viewing, or leave the radar facing the same way.
|-
|Artillery (AY)
| +
|style="background-color:#5BFAFA;"|''may need further research, T.A.S. is willing to make it more concise''
|The distance the warhead travels is in direct relation to how long fire button is held down. Projectile flies in an arc exiting from tank at 45 degrees (no vertical aim required). Range indicated above HUD as RANGE:### (counter advances as fire button is held down).
possible advantages:
-Very long range (though still finite unlike laser)
-shots may be fired over obstacles
-relatively large warhead, radius at 5%, 8%, or 10%, of normal bullet range though much less absolute than sw-perhaps the shot would be a cluster of 5 traditional bullets that travel together in an arc upon firing
-can function akin to anti aircraft guns against wg as well

Possible disadvantages:
-Tank becomes almost stationary except pivoting/rotation (maybe have some forward/backward motion, but at something like 5 or 3 units per second), or no jumping regardless of server (like with burrow)
-Shot travels slowly, has close minimum range, shot lands where machine gun terminates at minimum release (as such player can't immediately hurt self, which actually aids the learning process)
-very long reload time (does 15% sound reasonable?)
-rarity of flag, like geno?
-binocular view and radar only when used?
|-
|Combine Momentum and Steamroller flags into one, keep momentum flag name
| +/-
|style="background-color:#5BFAFA;"|'' ''
|Better trade-off between advantage/disadvantage, simplifies flag and weakness. Is still logical to the player. Can increase speed when player is really going, and hinder maneuverability, etc. Basically, it gives players an appropriate way to express the terms "ramming speed" or "Full Steam Ahead!".
|-
|ECM (EM)
| +
|style="background-color:#ffff00;"|''Perhaps, if there is some indication of who does it. This was edited/expanded without original creator's knowledge by The Artichoke Singularity. If the below description is against the original creator's wishes, T.A.S. will rescind the added information.''
|Other tanks' radars get jammed within a certain range. Combine this flag with Missle Jammer. ECM can be visually represented in window as a large ring that surrounds the tank. Use right mouse button to release. User and all others in vicinity of ECM influence are unable to use radar when ECM is in effect. In window, all can see it as a circle or ring (someone else needs to decide the color of it) that spreads from epicenter of emission to maximum range around tank. However, viewed on non-afflicted radar, it is a black circle that clouds everything within the range of the ECM on radar much like an SW with more lasting power. Each ECM burst can last for a limited amount of time (5 seconds?) or can take the place of a shot?
|-
|Blink (BK)
| +
|style="background-color:#5BFAFA;"|'' ''
|Player alternates from stealth to cloak. Radar signature alternates from stealth to cloak. Player with flag is always visible either in window or radar. If a bad flag, player alternates from blindness and jamming for limited time.
|-
|Blink (BK)
| -
|style="background-color:#5BFAFA;"|'' ''
|If a bad flag, player alternates from blindness and jamming for limited time. Primary preference is to use blink as super flag described above.
|-
|Tankochet
|
|style="background-color:#5BFAFA;"|'' ''
|bullets ricochet off your tank for a limited time
|-
|False Enemy (FE)
|
|style="background-color:#5BFAFA;"|'' ''
|The opposite of MQ; when you pick up this flag, your teammates see you as from another team.
|-
|Campers Bullet (CP)
| +
|style="background-color:#5BFAFA;"|'' ''
|Shots go through teleporters, without actually teleporting. Useful for hiding behind a teleporter and shooting through it, while being shielded by the teleporter.
|-
|Black Hole (BH)
| +
|style="background-color:#5BFAFA;"|'' ''
|Your shots move slowly, shots within half a shockwave radius of yours aim towards yours, (double maximum turn/frame of guided missile,) your shots absorb any shots that hit them to increase their range. Black holes either can't absorb each other or if they collide, they instantly kill all tanks, including the shooter(s).
|-
|GalaGa (GG)
| +
|style="background-color:#5BFAFA;"|'' ''
|When this flag is held, your tank becomes 1.5 (to 2) times wider. However, you are able to shoot two bullets at the cost of one (like a dual fighter in Galaga).
|-
|Dome of Protection (DP)
| +
|style="background-color:#5BFAFA;"|'' ''
|Similar to SW, but instead the "shell" is a protective dome. All shots are simply absorbed or, if there is richochet, bounce off it. It can only be penetrated by SB and SW. Note: when the flag is held the player cannot fire normal shots. They can still fight by making the shots bounce back at them.
|-
|No Ricochet (NR)
| -
|style="background-color:#5BFAFA;"|'' ''
|Shots don't ricochet.
|-
|Ricochet Guided missile (RG)
| +
|style="background-color:transparent;"|''Maybe if it's a simple ricochet and has a more narrow lock-on angle.''
|Instead of exploding, the RG bounces off of surfaces and continues to track the target. Option 1: It loses velocity with each bounce. Option 2: When the RG bounces, it travels in a straight line for a certain distance before regaining lock. EDIT: Perhaps we keep it as a simple ricochet, without any lock loss. The GM keeps lock, it' just takes longer to get there.
|-
|NearSight (NS)
| -
|style="background-color:transparent;"|''Maybe, not too game breaking, but not really that exciting.''
|All tanks farther than (variable defined) world units are completely invisible on HUD. The closer they are to the player, the more visible they become. Similar to an invisible fog, does NOT effect buildings. Gives enemies a long-range advantage.
|-
|Long Shot (LS)
| +
|style="background-color:transparent;"|''Maybe, not a bad idea.''
|Bullets go twice as far but at a slower speed. Possibly N/2 extra bullets.\
|-
|Low Gravity(LG)
| +
|style="background-color:#4141a1;"|''Yes, done in 2.1.x.''
|Gravity is reduced to a large degree allowing the tank to jump very high in the air.
|-
|Long Reload (LR)
| -
|style="background-color:#a14141;"|''Yes.''
|Reloading weapon takes twice as long.
|-
|Don't Stop (DS)
| -
|style="background-color:#a14141;"|''Yes.''
|Tank always moves forward or backwards, it cannot stop.
|-
|BackFire (BF)
| +/-
|style="background-color:#a14141;"|''Yes.''
|Shots fire to rear of tank instead of front.
|-
|FrienDly fire (FD)
| +
|style="background-color:#a14141;"|''Yes.''
|Your shots don't kill friendly tanks (Your own ricochets are harmless!).
[Additional suggestions: immune to friendly shots? This can also be a server-side setting, like ricochet.]
|-
|Sensor Echo (SE)
| -
|style="background-color:#a14141;"|''Maybe, not a bad idea.''
|All tanks show up twice (or more) on radar. Echoes behave like the tank they mirror, down to the flag.
|-
|Delayed Shot (DS)
| -
|style="background-color:#a14141;"|''Yes.''
|Shots wait some prescribed amount of time (2 seconds?) between clicking and actually firing.
|-
|Extra Shot (ES)
| +
|style="background-color:#a14141;"|''Yes.''
|Player gets an extra shot.
|-
|SlowMotion (SM)
| -
|style="background-color:#a14141;"|''Yes.''
|Tank moves and turns with half speed.
|-
|INcoming (IN)
| +
|style="background-color:#ffff00;"|''No, it's very very close to a cheat.''
|Bullets that will hit the tank are highlighted on radar/main view in some fashion as a warning system.
|-
|Flip Out (FO)
| -
|style="background-color:#ffff00;"|''No not really different from reverse controls.''
|Out of window view is upside-down.
|-
|EarthQuake (EQ)
| +
|style="background-color:#ffff00;"|''No, same as using a shockwave on landing.''
|When landing after a jump, a shockwave will destroy tanks on the ground in the immediate vicinity of the landing tank.
|-
|DeFender (DF)
| +
|style="background-color:#ffff00;"|''No, too confusing for players.''
|Fires a short-range shot that projects a miniature shockwave to destroy enemy shots.
|-
|Retro (RE)
| -
|style="background-color:#ffff00;"|''No, doesn't do ANYTHING''
|View becomes green wireframe and otherwise looks like the [http://en.wikipedia.org/wiki/Battlezone original Battlezone].
|-
|Velocity Shooting (VS)
| -
|style="background-color:#ffff00;"|''No, is a server option, not to be mixed for some players and not others.''
|Shots keep Vertical-Velocity (as its set on some Servers for all players). If you jump; shots go up and when you fall; shots aim downward.
|-
|SQuishable (SQ)
| -
|style="background-color:#ffff00;"|''No, too confusing for players.''
|The opposite of Steamroller. When you touch other tanks (including teammates), you die.
|-
|Judas (JD)
| -
|style="background-color:#ffff00;"|''No, too confusing for players.''
|When you pick up the flag, you immediately become a player on a different (random) team (or rogue). You must play on that team for as long as you have the flag. If you kill one of your new teammates, you die. BUT you can kill your old teammates for as long as you hold the flag. When you drop the flag or are killed, you revert to your old color.
|-
|ANtagonize(AN)
| -
|style="background-color:#ffff00;"|''No, can not be localized easily, and may anger people.''
|This bad flag causes your tank to automatically send out mild insults and taunts to opposing players. Especially the good ones by name.
|-
|CoW launcher (CW)
| -
|style="background-color:#ffff00;"|''No, would require vertical aiming to work properly.''
|(Goofy) Launches a cow along a parabolic trajectory.
|-
|ConFusion (CF)
| -
|style="background-color:#ffff00;"|''No, too similar to CB.''
|Tank colors and names are shuffled around. Like colorblindness, but worse.
|-
|ShowOff(SO)
| +
|style="background-color:#ffff00;"|''No, basically useless in gameplay.''
|(Goofy) Tank is capable of doing tricks, back flips when jumping, riding on one tread, etc.
|-
|Leash(LE)
| -
|style="background-color:#ffff00;"|''No, too confusing for players.''
|Tank is confined to a small radius for a set time period but can still jump.
|-
|BUckler (BU)
| +
|style="background-color:#ffff00;"|''No, shield is enough.''
|Give the player a 45 degree shield that reflects all shots. It should be located in the arc between 270-315 degrees. The shielded area should be visible but transparent.
|-
|PSychic (PS)
| +
|style="background-color:#ffff00;"|''No, too powerful and makes ID pointless.''
|Callsigns and flag names of all (visible?) tanks appear above the tank.
|-
|Full Reverse(FR)
| +
|style="background-color:#ffff00;"|''No, too similar to HS and too limited in scope.''
|Your tank can move full speed in reverse. A middle ground between high speed and normal.
|-
|All Terrain (AT)
| +
|style="background-color:#ffff00;"|''No slopes, never. No.''
|Can drive over slopes and pyramids, (unless steeper than 45?) and perhaps up walls too.
|-
|Tac Nuke (TN)
| +
|style="background-color:#ffff00;"|''No too powerful.''
|On impact with any surface or tank, causes TN to detonate like a half-size SW. Option 1: TN has long reload time or is a single shot flag. Option 2: TN has an "arming" range where it cannot detonate until it passes out of that range. This range can be equal to 1/2 the blast radius or some arbitrary number. Option 3: If the TN hits a tank with a Shield flag, it is neutralized.
|-
|Glue Trail (GT)
| +
|style="background-color:#ffff00;"|''No, too confusing for players.''
|Leaves a trail that slows down other tanks behind it. fades after server-set number of seconds?
|-
|Oil Slick (OS)
| +
|style="background-color:#ffff00;"|''No, too confusing for players.''
|Leaves a trail that makes tanks behind skid/spin. Fades after server-set number of seconds?
|-
|Petrificus Totalus (PT)
| -
|style="background-color:#ffff00;"|''No, too confusing for players, and rather lame.''
|Paralyzes tank. Cannot move, turn or shoot for set number of seconds.
|-
|Toy Gun (TG)
| -
|style="background-color:#ffff00;"|''No, pointless in game play, just use the Useless flag.''
|When you shoot,the bullet that comes out is a fake bullet attached to a string which is attached to your tank.
|-
|Icy Treads (IT)
| -
|style="background-color:#ffff00;"|''No, just like momentum.''
|Tank loses traction on the ground and on all objects, as if the friction setting was lowered for that particular tank.
|-
|ParaChute (PC)
| +
|style="background-color:#ffff00;"|''No, just like Wings.''
|You can control your tank ONLY when falling down and you fall down slower.
|-
|ToRnado (TR)
| -
|style="background-color:#ffff00;"|''No, too confusing for players.''
|You jump and spin uncontrollably.
|-
|GhostS (GS)/SPawn (SP)
| +
|style="background-color:#ffff00;"|''No, FAR too complex.''
|2 or 3 mini bot tanks come out of your tanks and help you by providing cover ect. They die by being shot or after a certain period of time (45 secs?).
|-
|Death Ball (DB)
| +
|style="background-color:#ffff00;"|''No, FAR too complex.''
|Tank morphs into a Death Ball and kills anyone who touches it. Faster than a normal tanks. Can be killed by being shot 5 times. You can't jump.
|-
|DiG (DG)
| +/-
|style="background-color:#ffff00;"|''No, too similar to burrow.''
|Your tank goes completely underground upon picking up the flag, and you may then shoot up at tanks above you. Anybody may lock on you (as with GM) if they hold GM, SB, or even no flag. You are also in range of SW. Bullets will follow you underground.
|-
|RaM (RM)
| +
|style="background-color:#ffff00;"|''No, too poweful and complex.''
|Tank travels at normal speed unless you fire. Firing causes your tank to accelerate forward quickly and only for a certain range. When you touch another tank, it has Steamroller effect, causing them to explode.
|-
|Auto Teleport (AT)
| +
|style="background-color:#ffff00;"|''No, too complex, too powerful, and looks too much like a cheat.''
|With this flag a player can teleport to any place visible place on the radar by clicking the desired area on the radar. Only one teleport can be done per flag, otherwise you would be impossible to kill. Another way to make it harder is to put a reload time on it, so there would be at least some pause between teleports. If you teleport to an area occupied by a building, you go to the highest place on the specified area of the building.
|-
|Ice Laser (IL)
| +
|style="background-color:#ffff00;"|''No, too confusing for players, just kill them.''
|This laser does not kill players. Instead, it freezes them. They can't move, jump, or shoot, for 10 seconds. Players who are shot by normal bullets while they are frozen become unfrozen. When a tank is frozen, the tank becomes white, preventing other players from knowing which team the frozen tank is on.
|-
|Kamakazi Attack (KA)
| +/-
|style="background-color:#ffff00;"|''No, too confusing for players.''
|This can be a good and a bad flag. When picked up, starts a self-destruct timer, that, when runs out, will blow you up. But if the right button is pressed before the time is up, then you blow up on the click. This can be use to kill multiple tanks, and can also be used in mid-air. Moderate blast-radius?
|-
|Swallow Tanks (SW)
| +
|style="background-color:#ffff00;"|''No, far too confusing.''
|(GOOFY) If you touch another tank it disappears and becomes an observer to your tank. The more tanks you swallow the more obese you become. You can only swallow a limit of 3 tanks at a time, if you swallow more you pop. If you are killed all of the tanks you are carrying are set free. The tanks jump as they are set free to avoid multiple shots that may have been fired at the original tank. Swallow your own teammates and carry them deep into enemy territory!
|-
|Electricity Bolt (EB)
| +
|style="background-color:#ffff00;"|''No, far too powerful and confusing.''
|Looks like thief shot when fired (Short range weapon) only when it hits a structure it kills everyone on it or touching it (or in it, players with OO). This would be handy for killing tanks sitting in hard to get to places!
|-
|Invisible Objects (IO)
| -
|style="background-color:#ffff00;"|''Maybe.''
|All surface objects (pyramids, boxes, etc.) become invisible.
|-
|Meatloaf Launcher(ML)
| -
|style="background-color:#ffff00;"|''Just move forward while jumping, unrelated name.''
|Jumping propels your tank not only upwards but forwards as well.
|-
|Bent Turret (BT)
| -/+
|style="background-color:#ffff00;"|''Maybe.''
|All shots go out 30 degrees to the left/right (than a normal shot). Some people might call this a super flag because it helps dodging.
|-
|Tiny Bullet (TB)
| -
|style="background-color:#ffff00;"|''Perhaps.''
|This bad flag causes your the bullets to shrink, making them hard for you to hit your opponent.
|-
|Missle Jammer (MJ)
| +
|style="background-color:#ffff00;"|''Maybe.''
|Prevents a GM lock on your tank. You can still be killed by normal shots, or unlocked shots.
|-
|Score Flags (SF)
| +
|style="background-color:#ffff00;"|''Maybe, a multi-player isn't a bad idea.''
|Gives you more than one point for each kill. Maybe randomize between 2 and 5 points. (This could also be used as a handicap for beginners)
|-
|NearSight (NS)
| -
|style="background-color:#ffff00;"|''Maybe, not too game breaking, but not relay that exciting.''
|All tanks farther than (variable defined) world units are completely invisible on HUD. The closer they are to the player, the more visible they become. Similar to an invisible fog, does NOT effect buildings. Gives enemies a long-range advantage.
|-
|Black Death (BD)
| +/-
|style="background-color:#ffff00;"|''No, far too powerful and confusing''.
|This flag is similar to a team flag only when it is captured it kills all other opposing teams (instead of just one specific team). This would make it so that multiple teams would be competing for one flag. (The color of the flag is black)
|-
|Colored Flag (CF)
| +
|style="background-color:#ffff00;"|''No, would destroy CTF.''
|CTF only flag. Other people see the CF as their own team flag (except own team?)
|-
|Punch (PU)
| +
|style="background-color:#ffff00;"|''No, just kill with steamroller.''
|Hitting a tank at full speed throws it some appreciable distance away
|-
|Remote Mines (RM)
| +
|style="background-color:#ffff00;"|''No, no mines. They will seem to kill players for no reason.''
|Firing places a mine, up to some predefined number. The next shot detonates all of them
|-
|Firewall (FW)
| +
|style="background-color:#ffff00;"|''No, too hard to sync, and somewhat confusing.''
|Firing creates a temporary wall of flame that tanks cannot pass
|-
|Glue Bomb (GB)
| +
|style="background-color:#ffff00;"|''No, too confusing for players.''
|Shot would detonate in a big pile of glue, slowing down people in the blast radius
|-
|Corbomite Device (CD)
| +
|style="background-color:#ffff00;"|''No, too confusing, and hard to sync.''
|When the tank is shot, it generates a reciprocating shot to what killed it - these shots can be dodged normally, in most cases (SW, GM being impossible/difficult)
|-
|Clone (CN)
| +
|style="background-color:#ffff00;"|''No, too confusing and too much like cheats.''
|Tank emits a hologram clone at some offset from itself as a diversion.
|-
|Smoke Screen (SC)
| +
|style="background-color:#ffff00;"|''No, doesn't add much for gameplay.''
|The tank emits a cloud of smoke behind it. This provides a visual wall, and perhaps cancels out GM locks as well.
|-
|Time Lapse (TL)
| -
|style="background-color:#ffff00;"|''No, too similar to blind and jamming combined.''
|Holding this flag will cause the HUD & radar to refresh only every second or so.
|-
|Big Bullet (BB)
| +
|style="background-color:#ffff00;"|''No, too powerful, shots are computed as point hits.''
|Bullets are twice (or more) as large. Tank feels a kick-back when firing
|-
|Gravity Well (GW)
| +
|style="background-color:#ffff00;"|''No, FAR too complex.''
|One-shot fire, creates a gravity well at some distance away from the firing tank. This well pulls in all tanks around it - driving away from the well will slow the descent. Possible avoidance/negation flags include BU, OO, PZ, HS.
|-
|Mirror (MI)
| +
|style="background-color:#ffff00;"|''No, just make CL deflect laser.''
|Holding this flag will reflect a hit by laser. Flag is not dropped after a hit. The appearance of a tank holding this flag changes so that it reflects the surroundings. Or maybe appears pseudo-transparent, rather like the inside of structures viewed with Oscillation Overthruster, or of objects when in the PZ.
|-
|Plasma Ball (PB)
| +
|style="background-color:#ffff00;"|''No, too limited, and just kinda weird.''
|Shoots a large (8 unit) sphere that behaves exactly like a super bullet -- except it travels very, very slowly. It would travel as fast as a burrowed tank going in reverse, thus being easy to outrun in open areas, but hard to avoid on "indoor" maps. Because of the size, it would kill burrowed tanks when fired on the ground.
|-
|Fake Bullets(FB)
| +
|style="background-color:#ffff00;"|''No, too complex, and pointless.''
|1) your bullets look, bounce, show up on radar, and seem real, but they pass right through tanks, causing no damage, and can't harm anyone. This can seem like a bad flag, but would be great to get the other team jumping and running while having zero chance of hitting your own team (and this is how I'd like to use it). 2) Could be made a bad flag that requires you to hold it for a certain amount of time before dropping it. (Would be nice if there were a way to keep a bad flag if you choose.) 3) optional: fire rate is doubled, or unlimited
|-
|BulletInertia(BI)
| +
|style="background-color:#ffff00;"|''No, it's a server setting.''
|When a shot is fired it has the same motion as the tank when it was fired. So if the tank is falling the shots move downward towards the ground, and shots are accelerated or decelerated if the tank is going forward of backward.
|-
|Warp Engine (WE)
| +
|style="background-color:#ffff00;"|''No, FAR too complex.''
|Tank can hit newly-defined "Warp" key (perhaps jump key?) and, with a two-second delay, instantaneously be transported an amount in the direction of facing equal to the current warp power, which starts at a minimum value. Pushing the key during the delay period increases the power; increasing it past a certain amount causes the warp engine to overload and blow up. Warping into buildings or outside the world boundary causes a collision and blows up the tank. (A random chance of being dropped when used, depending on how much power is applied? Use a gradual teleporter fog during the about-to-warp delay? Signal about-to-warpness to the other players by turning the tank gradually bright glowing white? Use a new sound for when the warp occurs?)
|-
|Identify Friend/Foe (FF)
| +
|style="background-color:#ffff00;"|''No, just apply the setting to Masquerade.''
|Masquerade for the radar. Tank shows up for everyone as their team on the radar.
|-
|Rotating Turret (RT)
| +
|style="background-color:#ffff00;"|''No, no turning turrets, ever.''
|Turret can turn. Like GM, you can lock on people, and the turret always fires in their direction (horizontally, not vertically). May need some graphics changes (tank becomes bottom part - tank orientation + top part - turret orientation)
|-
|Boat (BO)
| +
|style="background-color:#ffff00;"|''No, too dependent on map features.''
|Tank floats on water. Moats don't kill you. You move a bit slower on water though. You can still jump on water, but not as high.
|-
|MortarBomb (MB)
| +
|style="background-color:#ffff00;"|''No, requires vertical aim to be any use.''
|Shot has same trajectory as a jump. Vertical velocity alters trajectory. Should be very useful once mastered. Many applications e.g. stop-shoot-go to drop a shot on a pursuer. - FiringSquad
|-
|CriticalMass (CM)
| +/-
|style="background-color:#ffff00;"|''No, this is a server side plugin, not a flag.''
|When killed you explode in a ShockWave (perhaps larger). Tanks with this flag should pulse on your radar. Suicide to kill at close range and dangerous to have near you. Points scored from explosion should accrue to the holder not the killer, otherwise not worth holding onto flag. - FiringSquad
|-
|ShortHop (SH)
| +/-
|style="background-color:#ffff00;"|''No, too similar to jump.''
|Jump is half the normal height and takes half the time. (+) Good for jumping over bullets and regaining control quickly to return fire. (-) Unable to reach everywhere. - FiringSquad
|-
|1000 Tons Weight (TW)
| +/-
|style="background-color:#ffff00;"|''No, just stupid''
|Timer starts as soon as flag as picked up(30 sec timer? Server set?), and user cant drop it. When timer runs out, a 1000 ton weight falls out of the sky killing the owner. When you shoot someone the flag gets transfered over. Player 1 gets TW, 25 seconds go by, he shoots Player 2, then, 5 seconds time, BOOM. Make a nice CLLANNG sound, and tank stops, and other tanks see the weight fall on him. (Punkus)
|-
|Red Eye (RE)
| +/-
|style="background-color:#ffff00;"|''No, too complex and somewhat pointless.''
|First shot causes target tank out-of-window screen to become all white (like a red-eye flash). Out-of-window view stays white for a certain number of seconds (2? 3?). Within that time initial tanks shots are normal, other shooting tank causes white screen again. Radar works as normal, only out-of-window view is affected
|-
|SUbtle (SU)
| +
|style="background-color:#ffff00;"|''No, just use CL''
|Tank appears normal to friendlies - only outline visible to enemies.
|-
|Klingon Cloak (KC)
| +
|style="background-color:#ffff00;"|''No, to powerful.''
|A super cloak, combining stealth and cloak to render you totally invisible to others (though not untouchable). You're not invincible though because, just like with the cloaks used by the Klingons, your tank cannot fire while you have this flag and there is a couple second delay between dropping cloak and being able to fire. Not much for fighting, but great for sneaking up on campers.
|-
|Team Invulnerable(TI)
| +
|style="background-color:#ffff00;"|''No, just use Friendly Fire.''
|Can't be killed by a teammate, except maybe superbullet, genocide.
|-
|TagYourit (TY)
| -
|style="background-color:#ffff00;"|''No, should be a game mode, not a flag.''
|Your tank can't fire and the only way to drop the flag is to get within a certain radius of another tank. The flag is automatically transferred to the other tank.
|-
|SwiM (SM)
| +
|style="background-color:#ffff00;"|''No, too complex.''
|In short: Can get into building. while in building can:
* raise slowly while the jump-key is pressed. fall slowly otherwise.
* get to the almost top of the building. from the top can shoot and be shot - while holding the jump key(otherwise he'll fall-in)
* and can die if the countdown reaches zero. a countdown will be started when he gets to a building, and stopped when he gets out.
|-
|Proximity Drop (PD)
| +
|style="background-color:#ffff00;"|''No, too confusing for the other players.''
|When driving close to opposing tanks (say 3 tank lengths) you cause them to lose their flags.
|-
|Lightning Bolt (LB)
| +
|style="background-color:#ffff00;"|''No, lame munchkin flag. Too limited in use.''
|A lightning bolt descends from the sky and hits the highest object above the tank (possibly passing through everything on it's way down?), destroying people above you. Harmless to your own tank. Effective against tanks with GM sniping from high places. Completely useless against almost everything else.
|-
|ThrUster (TU)
| +
|style="background-color:#ffff00;"|''No, We have Wings.''
|Clicking causes thrusters to fire up underneath your tank. Holding the left mouse button keeps the rockets on (for a time, until they burn out and you plummet to the ground). Landing on other tanks destroys, unless the thrusters used up. Rockets must recharge (especially after being burnt out) like any offensive weapon. A bit like the tank in StarFox64 - yes, I know, sinful console game.
|-
|Ostrich (OS)
| -
|style="background-color:#ffff00;"|''No, we have burrow.''
|(Goofy) Your tank becomes an ostrich. Clicking causes you to bury your head (and the rest of your body) underground, making it impervious to attack for a very short period, but completely unable to move. Any tanks in the way of it diving underground are destroyed. Weak against lasers, because there would be no time to duck.
|-
|LaZarus(LZ)
| +
|style="background-color:#ffff00;"|''No, just use shield.''
|When killed holding this flag, after being exploded your tank magically combines, and you are not dead.
|-
|WaveFront (WF)
| +
|style="background-color:#ffff00;"|''No, just use shockwave.''
|Like shockwave, but only, say, 30 degrees high and wide, but has longer range
|-
|Dud Shot (DS)
| -
|style="background-color:#ffff00;"|''No, it's kinda mean. And you could not shake it on servers with shake kills.''
|Not all of your bullets work
|-
|Death Blossom (DB)
| +
|style="background-color:#ffff00;"|''No, Just use shockwave.''
|Shoots all bullets available in a circular pattern from the tank.
|-
|COlumn(CO)
| +
|style="background-color:#ffff00;"|''No, very limited in use.''
|All of your (currently loaded) shots are fired at once, on top of each other, making a vertical column.
|-
|Sniper Rifle (SR)
| +
|style="background-color:#ffff00;"|''No, just use laser.''
|Your Tank's shots have infinite range, think of the good, and the bad.
|-
|Flash Bang (FB)
| +
|style="background-color:#ffff00;"|''No, redefines too many existing behaviors, and far too complex.
|A few possible implementations. 1) Right-click fires non-lethal shots which travel until a second right-click upon which they explode (similar to SW radius, perhaps bigger) and blind tanks within blast. 2) Could be semi-bad flag where normal shots don't kill but temporarily blind tanks that are hit to allow escape (or kill by teammate). 3) Right click flashes all opponents within line-of-sight of tank w/flag. If tanks are turned such that they can see tank w/flag, they are temporarily blinded.
|-
|Freeze Wave (FW)
| +
|style="background-color:#ffff00;"|''No, just kill them.''
|Similar to Shock Wave, except that instead of destroying other tanks within the shock radius, it freezes other tanks within the freeze radius for a certain time, so they cannot move or fire (even in mid-air). When the other tanks re-awaken, they are immune to freezing for a certain time. Dropping the flag forces a reload time (like Thief). This flag encourages team play. An alternate implementation would freeze yourself if any team tanks get frozen.
|-
|ARchitect(AR)
| +
|style="background-color:#ffff00;"|''No.. Just... No.''
|Your tank can move buildings by driving into them.
|-
|Gravity Bullet (GB)
| +
|style="background-color:#ffff00;"|''No, requires vertical aim to work well.''
|Your bullets are affected by gravity. This obviously reduces the range when fired on the ground, but a tank sitting on a building or jumping has the ability to hit people below them... if they time their shots right.
|-
|RubberTank (RT)
| +
|style="background-color:#ffff00;"|''No, use shield.''
|I'm rubber and you're glue, whatever you shoot bounces off me and kills you! Regular shots ricochet off your tank back in the direction they came, if shooter is still there or close then he gets hit by his own shot. GMs explode without killing or cause rubber damage (flag drop). Super bullet and shock wave kill. Steam roller bounces off you, maybe causing his death or both your flags to drop.
|-
|MagNet (MN)
| -
|style="background-color:#ffff00;"|''No, it's just mean.''
|Bullets are attracted to player's tank.
|-
|Force Field (FF)
| +
|style="background-color:#ffff00;"|''No, Just use Shield.''
|Pushes bullets away. Well aimed shots do not get pushed away
|-
|Boomerang Bullet (BB)
| -
|style="background-color:#ffff00;"|''No, too limiting.''
|Shots move in a curved path that includes the point of firing
|-
|ZigZag (ZZ)
| -
|style="background-color:#ffff00;"|''No, too limiting. ''
|Shots don't fly straight. Instead they fly in a sine wave or a zigzag pattern. Probably no reasonable expectation of hitting what you want.
|-
|FReeze (FR)
| -
|style="background-color:#ffff00;"|''No Too limiting.''
|Tank can't move, only jump and fire.
|-
|Shock Ring (??)
| +
|style="background-color:#ffff00;"|''No, just use shockwave.''
|Shockwave in a horizontal ring pattern
|-
|RemoteControl (RC)
| +
|style="background-color:#ffff00;"|''No.. Just... No.''
|Player can take control of another player's tank, steer and/or fire it, causing the other player to become vulnerable and/or kill himself or others. Offensive and defensive uses, especially if gm or laser campers are around. Automatically dropped after use.
|-
|TransLocate (TL)
| +
|style="background-color:#ffff00;"|''No.. Just... No.''
|Identify a player, then switch places (perhaps N times use)
|-
|Clone (CN)
| +
|style="background-color:#ffff00;"|''No.. Just... No.''
|Takes on the properties of the nearest player's flag
|-
|Lemur mode (LM)
| -
|style="background-color:#ffff00;"|''No.. Just... No.''
|Walk on walls. (maybe parallel to ground only, from however high you touched it, and then jump to get off?)
|-
|Cattle Prod (CP)
| +
|style="background-color:#ffff00;"|''No, Steamroller!?!?!''
|(Goofy) A cattle prod sticks out some fixed distance in front of the bearer's tank. Anyone who touches the prod dies. Clicking while the flag is in effect does nothing.
|-
|MiRage (MR)
| -
|style="background-color:#ffff00;"|''No.. Just... No.''
|Player sees tanks and shots where they shouldn't be.
|-
|Wormhole Bullet(WB)
| -
|style="background-color:#ffff00;"|''No.. Just... No.''
|Bullets that hit other tanks send them to a random link/teleporter instead of killing them. (If there are no teleporters, don't create flags?).
|-
|INflate(IN)
| -
|style="background-color:#ffff00;"|''No.. Just... No.''
|Your bullets cause tiny tanks to become normal sized, normal tanks to become obese, and obese tanks to explode.
|-
|Proximity Fuse (PF)
| +
|style="background-color:#ffff00;"|''No.. Just... No.''
|Shells explode with a small shock wave when they pass within range of a tank (even a friendly one).
|-
|Laser Cloud(LC)
| +
|style="background-color:#ffff00;"|''No.. Just... No.''
|Firing this causes a x amount (x = amount of shots available) of short laser beams to project from the tank, killing all GM, bullets, and tanks they meet. It can aim up and down, and has the range of a Shockwave. Can be over driven by a greater amount of shots than the tank has lasers for. Right clicking causes one single laser beam twice as long as usual, it uses all the shots available, and takes twice as long to recover (optional)
|-
|French Fries (FF)
| -
|style="background-color:#ffff00;"|''No, too complex, kinda lame.''
|(Goofy) Other tanks are attracted to the french fry and will turn to it if they are facing it within 90 degrees.It automatically moves toward it. Other tanks can still turn around (slowly) until it gets out of the magical 90 degrees.
|-
|Time Displacement(TD)
| +
|style="background-color:#ffff00;"|''No.''
|Employing this causes the whole world to freeze for a short period of time. Except you, and perhaps PZ. You loose your flag after this. You can't shoot while the world is frozen.
|-
|Ugly
| +
|style="background-color:#ffff00;"|''No.''
|When opposing tanks have you in there lock angle, their tanks automatically turn away from you. This can be compensated for by turning against it.
|-
|Fly by Wire (FW)
| +
|style="background-color:#ffff00;"|''No, though adding this to GM might be nice.''
|Missile flies with built-in camera; player's tank stands still until missile flight is over.
|-
|KamikaZe (KZ)
| -
|style="background-color:#ffff00;"|''No.''
|Tank drives fast, explodes with a large radius when it collides with another tank or obstacle
|-
|Random Teleport (RT)
| -
|style="background-color:#ffff00;"|''No.''
|Can't control when or where it teleports you
|-
|Air Burst (AB)
| +
|style="background-color:#ffff00;"|''Never.''
|Flag explodes when it reaches its apex when dropped. Apex is especially high. Explosion is large (bigger than shock wave). Being in or behind a building should protect you. Being behind (or through!) a teleporter should not.
|-
|Heat Seeker (HS)
| +
|style="background-color:#ffff00;"|''Never, same as GM.''
|Missile is fire-and-forget; heads toward nearest "heat source"
|-
|HoloGram (HG)
| +
|style="background-color:#ffff00;"|''Never.''
|Player's tank appears off to one side from where it really is.
|-
|Grappling Beam (GB)
| +
|style="background-color:#ffff00;"|''No.''
|Clicking fires a laser-like beam that travels at the same speed as bullets, and does the same thing to enemy tanks if they are hit. If the beam hits a pyramid or a box, however, the tank gets pulled rapidly to the object that was hit (like a grappling hook).
|-
|ILlusion (IL)
| +
|style="background-color:#ffff00;"|''No.''
|Opposing players see 2(?) fake copies of your tank at constant random offsets from your real position (if they are shot, either nothing happens or the fakes disappear?).
|-
|SNake (SN)
| +
|style="background-color:#ffff00;"|''No.''
|(Goofy) Becomes like a game of Nibbles for the bearer of the flag; a laser-looking barrier comes out behind the tank, and stays there (possibly for only a fixed length). Any player that touches the barrier dies.
|-
|Kill or be Killed (KK)
| -
|style="background-color:#ffff00;"|''Never.''
|Player has to make kills within a certain time, or risk blowing him/herself up. {abbrev should be changed for obvious reasons}
|-
|ShotGun (SG)
| +
|style="background-color:#ffff00;"|''Never.''
|Shots split and go off in different directions.
|-
|Interdimensional Teleport (IT)
| +
|style="background-color:#ffff00;"|''Never, no "on drop" actions.''
|Teleports to a random location when dropped
|-
|Rear Shot (RS)
| +
|style="background-color:#ffff00;"|''Never.''
|Shoots both in front and behind (if available shots)
|-
|LLama (LL)
| -
|style="background-color:#ffff00;"|''No.''
|(Goofy) Involuntarily charges all visible tanks, starting with the closest, including teammates. Has the same effect as SR on impact. Other tanks see an amusing llama. graphic.
|-
|SuperDrop(SD)
| +
|style="background-color:#ffff00;"|''Never.''
|When killed holding this flag, all tanks loose their flags, and they are sucked into the ether.
|-
|George Bush (GB)
| -
|style="background-color:#ffff00;"|''No.''
|(Goofy) All game and player messages are sent through a filter translating them into George W. Bush speak. Because he knows how difficult it is to put code on your project.
|-
|Turbo Boost (TB)
| +
|style="background-color:#ffff00;"|''Never.''
|Right click makes you faster than high speed briefly. Flag can be used multiple times, maybe with a recharge time.
|-
|ReFlect (RF)
| +
|style="background-color:#ffff00;"|''Never.''
|When you get hit, you die as usual, but shot isn't stopped, it is reflected back in the direction it came from.
|-
|MirroR (MR)
| +
|style="background-color:#ffff00;"|''Never.''
|See reflections of other tanks on the walls for aiming ricochet bullets
|-
|SubterFuge (SF)
| +
|style="background-color:#ffff00;"|''Never.''
|Similar to Antagonize. Players near you or those you id are sent deceptive messages purportedly from other players or teammates. These would be stock messages such as: watch out, [callsign] is behind you... let's go after [callsign]... boo... where callsign is a player on a team other than theirs or a rogue.
|-
|MagShield(MS)
| +
|style="background-color:#ffff00;"|''No, need to shoot.''
|A defense only flag. Fire and you envelope yourself with a brief magnetic shield that looks like or similar to shock wave, only this shield acts like a wall stopping or causing shots to rico as appropriate. Put up your shield soon enough and you're safe, but wait too long and a shot's ricocheting around inside with you. Tanks can drive thru the shield, both to fire at you or to be protected by you as you approach a target (camper). To fire yourself you have to drop the flag.
|-
|Tether Ball(TB)
| +
|style="background-color:#ffff00;"|''No. too many changes.''
|A ball appears behind the tank attached by a tether and can be swung along the ground by sharp turns. If a tank (even your own) hits either the tether or the ball it is destroyed.
|-
|Dumbfire Missile (DM)
| +
|style="background-color:#ffff00;"|''No.''
|A missile that can not be locked on, but has an actual blast area (miniature shock-wave, but without affecting PZ players). Possible alternative: Full size SW, but flag is 'used' (dropped for a long time, like the shield flag) when fired.
|-
|MultiFlag (MF)
| +
|style="background-color:#ffff00;"|''Never.''
|Tank can hold two other flags at the same time.
|-
|OIl (OI)
| +
|style="background-color:#ffff00;"|''No. large engine change.''
|Tank leaves an oil trail behind which steers people off course.
|-
|Flag Launcher(FL)
| +
|style="background-color:#ffff00;"|''No. No multiple flags.''
|Gives tank the same attributes as TH but can pick up a second flag without being affected, and fire it at another tank. If it misses you keep the flag but if it hits the tank is forced to give up any currently held flags and pick up the launched flag. Good with LE.
|-
|Radar Scout (RS)
| +
|style="background-color:#ffff00;"|''No, confusing.''
|Your tank becomes a radar-equipped scout (you can still shoot). In a certain radius around you, all tanks (except you) look obese (due to increased radar) and can be shot like obese tank (hitting is easier); they still fit through teleporters. In addition, cloaked and stealthed tanks and shots also become visible. Every tank on the play field can see and shoot the obese and cloaked tanks, so you have the advantages that

Tanks are more likely to shoot at each other, since you are normal in size, the others are obese
Others will think twice before destroying you since you provide them with a targeting aid
|-
|TurreT (TT)
| +
|style="background-color:#ffff00;"|''No.''
|Turns your tank into a turret. Same as Burrow + Machine Gun + Angular Velocity, but your tank can't move at all.
|-
|AnnoYance (AY)
| +
|style="background-color:#ffff00;"|''No, too easy to camp by a flag.''
|Tank is very large and fast, can't shoot, and invincible. Can distract enemies while friendlies go in for the kill.
|-
|AntiMatter (AM)
| +
|style="background-color:#ffff00;"|''No, needs more thought for vertical worlds.''
|Tank cannot be hit except for SB/SW. 50% increased reload time, can be steamrolled by any tank, colliding with buildings results in death too
|-
|Targeting Computer (TC)
| +
|style="background-color:#ffff00;"|''No, a lag nightmare.''
|HUD shows where to aim for lead-ahead based on dead reckoning
|-
|StraFe (SF)
| +
|style="background-color:#ffff00;"|''No, will not be a flag feature if ever implemented.''
|Modifier key makes turning strafe
|-
|ECCM (um...)
| +
|style="background-color:#ffff00;"|''No.''
|When firing from ECCM equipped tank, other tanks in front of it, 20/30 degrees, have for a while both not working radar and communication (excluding admins).
|-
|HeadAche (HA)
| -
|style="background-color:#ffff00;"|''No.''
|All colors (not just tank colors) are inverted. Causes confusion for player, should have time limit. Submitted by ThatGuySpencer
|-
|Double Shot (DS)
| +
|style="background-color:#ffff00;"|''No, see backfire.''
|Shots come out of both ends of your tank, shoting backwards and fowards (maybe your bullets run out twice as fast) - Terminator
|-
|X-ray Vision(XV)
| +
|style="background-color:#ffff00;"|''No, difficult to portray with complex worlds.''
|Can see through buildings, but not drive through them. Either they are completely invisible (making out-the window driving fun) or they show up like with OO. Makes it possible to surprise others who are behind objects, and who are depending only on radar to know where you are.
|-
|SNiper (SN)
| +
|style="background-color:#ffff00;"|''No, to much like laser.''
|Tank has one, invisible, shot that lasts until it hits something/someone. Never ricochets. Blam!
|-
|PariaH (PH)
| -
|style="background-color:#ffff00;"|''No.''
|Tank is identified in all ways as each other player's nemesis.
|-
|NeMesis (NM)
| +
|style="background-color:#ffff00;"|''No, not a good flag feature.''
|HUD indicates direction (but not distance) to last person to kill you, even if under stealth.
|-
|Rear Window (RW)
| +
|style="background-color:#ffff00;"|''No.''
|View is split horizontally, bottom half is view out the back.
|-
|Collector (CO)
| -
|style="background-color:#ffff00;"|''No holding multiple flags, unproductive''
|Or cleaner (CR). Everything is normal except this tank can collect all the flags, without being able to use them. The moment he presses spacebar or dies all flags he holds return to the world.
|-
|Bomber (BM)
| +
|style="background-color:#ffff00;"|''No we don't do splash damage''
|Like WG, but all shots go downwards. Speed is determined by _gravity. Useful for flying servers. When flying with BM the speed is slower than that of WG, but bombs shot will have a larger radius (can kill more things around them).
|-
|Pole-aXed (PX)
| -
|style="background-color:#ffff00;"|''No may as well just kill him, and we don't kill for a bad flag''
|Tank cannot move forwards or backwards, can steer and jump (even on no jump servers,to be more fair). It's like being stuck on a pole.
|-
|Splash-Damage (SD)
| +
|style="background-color:#ffff00;"|''No we don't do splash damage''
|When one of your bullets hits an enemy, he explodes in a shockwave.
|-
|PHase shift (PH)
| -
|style="background-color:#ffff00;"|''Combines OO, SB and more -- too powerful.''
|Oscillation Overthruster, but can backup, jump and shoot in walls. Shoots Super Bullets, and can be killed by Phantom Zone.}
|-
|ASsassin (AS)
| +
|style="background-color:#ffff00;"|''No, too complex, too powerfull''
|As small, fast and short-ranged as thief. Fatal and can't steal flags. Stealth and Cloaking in effect when someone is not in range, and cloaking in effect when you can't see them. (partial cloaking in effect when you can see part of them, that is, they're on the side of your view.) Can be steamrolled by anyone. Longer reload time than Thief. Can only kill once (but maybe you still keep the flag?).
|-
|BoMb (BM)
| -
|style="background-color:#ffff00;"|''No, rather pointless''
|Can be transferred to someone by shooting them, also transfers the timer. When the bad flag timer (or another timer) is up, the holder dies and creates a shockwave.
|-
|Terrain Immunity (TI)
| +
|style="background-color:#ffff00;"|''No, too map specific''
|User is invulnerable to, and can walk through, terrain hazards such as stuff that would normally be fatal to touch and conveyor belts.
|-
|Cloaked Bullet (CB)
| +
|style="background-color:#ffff00;"|''No, getting killed by a shot you can't see is bad''
|Your bullets are invisible out-the-window.
|-
|Charge Beam (CB)
| +
|style="background-color:#ffff00;"|''No, just use multiple shots from a regular laser''
|Hold mouse button to charge. Releasing shoots a laser that keeps firing for as long as you charged the beam for. (Maybe a limit on charge time, so there's a limit on how long you fire a laser for?)
|-
|Gravitational Field (GF)
| +
|style="background-color:#ffff00;"|''BZFlag is not a physics engine. Possible lag and sync nightmare.''
|Attracts nearby tanks and bullets towards you. You are also afected by Newton's third law, with a resulting force pushing you in the opposite direction of the sum of all the force vectors of all the tanks and bullets you attract. It can be good and bad. With skill you can use this flag to alter bullet paths and tank motion to your/your teammate's advantage, or to your enemy's disadvantage. An example of the effect might be if a tank w/ WG is nearby you could be pulled aloung in flight,although flight would be more difficult for the tank w/ WG. There is a higher risk of being hit and higher difficulty in moving.
|-
|Destroy Buildings (DB)
| +
|style="background-color:#ffff00;"|''No, significantly difficult to implement, and allows for to much abbuse''
|When your shot hits an object (such as a building) it causes that object to disappear temporarily. Still ricochets off.
|-
|PLane (PL)
| +
|style="background-color:#ffff00;"|''No multiple flags, no vertical shots, no weird [http://en.wikipedia.org/wiki/Royal_Flying_Corps flying] stuff. This probably won't be implemented.''
|Turns your tank into a plane. Planes have two guns, one on each wing. You can accelerate or decelerate by using scroll wheel up to accelerate, down to decelerate. Point the mouse in the direction you want to turn. If you are shot or touch a wall you turn back into a tank. ENEMY tanks get vertical lock-on on you, meaning if they shoot while you are within their view, then their shot is at an angle upward or downward so that it might hit you. You can get some flags as a plane. Shock wave drops a bomb straight down with the velocity of a shot, plus your velocity; Laser shoots a laser from your nose-cone; Rapid Fire, Super Bullet, Machine Gun, GM are the same as normal (but you still have wing guns); Cloaking, Stealth, and Masquerade are the same; Thief shoots from nose-cone; Black Hole shoots from nose-cone; OO lets you fly through walls (except floor and the surrounding wall, of course); PZ is same as normal; Galaga makes you wider, but you can shoot more shots; Charge Beam from nose-cone; Sensor Package is same as normal; No Ricochet prevents ricochet; etc.. If you drop a flag as a plane, it drops first the grabbed flag, then once you have no grabbed flag, turns you back into a tank. I realize this probably won't be implemented.
|-
|Sensor Package (SP)
| +
|style="background-color:#ffff00;"|''No, too powerful''
|In-game description: "Tank has upgraded sensors and can send locks to guided missiles and allies." Description here: You can see what flag an enemy has, you get those arrow things for enemy team flags as well as your own (and also vertical ones), all walls show up as green wireframe on black background; you get those "enemy in range, enemy to left/right" from Battle Zone when an enemy is in your range; you can lock on to enemies (but not allies) (as you do, all ENEMY missiles within the radius of a SW lock onto them, all ALLIES with GM lock onto them, but not their fired missiles), you also get notifications when you are within an enemy's line of sight and range, especially when you are within the blast radius of someone with shockwave, you can see what flag somebody has on the radar and HUD (letters over their head).
|-
|Flak (FK)
| +
|style="background-color:#ffff00;"|''No, too complex''
|Your tank shoots debris (or oval shaped sheilds or whatever they may look like) that collide and disintegrate regular type bullets instantly when the two come in contact.
|-
|Improved Masquerade (IM)
| +
|style="background-color:#ffff00;"|''No, no on shot changes, and too complex''
|Your tank appears on the Radar and through the view finder as a friendly tank to the enemy, but not to right-clicks and identification through targeting. However, this lasts until your fire. When you fire, you immediately lose the flag. This is good for infiltrating another side, but as soon as someone right-clicks you in his targeting reticule, your identity is displayed.
|-
|Kick back (KB)
| +
|style="background-color:#ffff00;"|''No, no advantage to the flag, just make it a server option for all shots''
|When shot your tanks goes backwards a certain distance. This lasts for a server set # of seconds
[Note: How is this a positive flag? This is also too similar to Big Bullet.]
|-
|Oldschool (OS)
| +
|style="background-color:#ffff00;"|''No, is not general enough, depends on other map setup''
|Immune to super bullets, missiles, laser beams, shock waves, and steamrolls. Tanks with other flags can still hit you, and theives can steal your flag; in other words, business as usual. Make others drop their precious flags.
|-
|New Age (NA)
| +
|style="background-color:#ffff00;"|''No, is not general enough, depends on other map setup''
|Immune to regular bullets; can only be killed by lasers, missiles, super bullets, steamrolls, and shock waves. Opposite of Oldschool. Probably disabled on maps without easily accessible superweapon flags.
|-
|Entanglement (QE)
| +
|style="background-color:#ffff00;"|''No''
|Whoever kills you gets destroyed by the server.
|-
|Laser Tripwire (LT)
| +
|style="background-color:#ffff00;"|''No, too complex''
|Shot travels until it strikes a wall, then generates a (non-ricocheting) laser beam along the direction of the surface normal until it reaches another surface. Beam remains until touched by a tank, which is destroyed. If player fires another tripwire, the existing tripwire is deleted. Player may drop the flag to leave the most recent tripwire in place. Shockwave will delete any tripwire it touches (if not too difficult to code).
|-
|Shotgun (SG) (Different to other one)
| +/-
|style="background-color:#ffff00;"|''No, too much like MG, same as the other ShotGun suggestion''
|All available shots are fired at once (set # by server), 1 straight, the next a set # of degrees left of the first, then the next # of degress right of the first and so on creating dispersed shots. Fast bullets but reduced range, no ricochet and very slow reload time. Good against multiple enemies in range and provides strategic usage of walls for cover while reloading. Useless against laser and guided missle and good players can jump/avoid and shoot you while reloading which is why shots travel faster. Good for short range but useless in long range.
|-
|Air Safe (AS)
| +
|style="background-color:#ffff00;"|''No, GM already has a counter flag: ST''
|Countermeasure for guided missle. Guided missles that come within sw radius of the player are destroyed but all other shots unaffected. Dampens power of guided missle.
|-
|SHort tank (SH)
| +
|style="background-color:#ffff00;"|''No, simply make a server option to make burrow jump''
|Makes tank short. Exactly like burrow except that it allows you to be on buildings and jump.
|-
|Communications Disruption (CD)
| -
|style="background-color:#ffff00;"|''No, too specific to a play style''
|You cannot send team messages. You can still send PMs, Admin messages and public messages.
|-
|Double Shot (DS)
| +
|style="background-color:#ffff00;"|''No, too complex, with not enough added benefit. Shots would have to bounce in non physical ways to seperate.''
|Every time a player with this flag fires and the shots bounce off a wall (or other object) it splits the shot into 2 shots. Can only happen once (split shots cannot split again).
|-
|Super Shield (SS)
| +
|style="background-color:#ffff00;"|''No, too complex''
|You have to be shot a set amount of times to die. A bit like shield BUT different types of shots damage the tank more. (Say a tanks picks up the SS flag and he/she has to be hit 5 times to die, but SW takes off 4 hits so he only has to be hit 2 times with SW to die). This could also work with Double Shot (DS) where when the shot splits it only makes half the damage of a normal shot. (He/she would now have to be hit 10 times with split bullets to die). Maybe put a health bar over the players tank that shows how many times YOU have to hit the tank with your bullets. (P1 gets SS flag and has to be hit 4 times to die, P2 gets GM (which takes off 2 hits) and he looks at P1 and it has the health bar and a number saying 2 (P2 has to hit P1 with the GM that he has 2 times) then P3 gets a SW flag and the health bar says 1 (because SW takes off 4 points and P1 only has 4 health points). If the health bar is too hard then i think that you could just have the SS without a health bar.
[[Category:Gameplay]]

Template:CommunityAdministrationNetwork

2007-12-10T00:31:15Z

L4m3r: Grammar. ;)

{|style="width:100%;margin-top:+.7em;background-color:#99ccff;border:2px solid #4040ff;"
|[[Image:CAN_logo.png]]
||This page contains information about an idea called the Community Administration Network Project. It does not represent any rules, opinions, or regulations for the BZFlag project. The C.A.N. was an idea whose author has lost interest. The information is left here for others to use if they wish to take up similar projects.
'''THE CAN IS NO LONGER AN ACTIVE IDEA'''
|}<br>
<includeonly>[[Category:CommunityAdministrationNetwork]]</includeonly>
<noinclude>Adding this template to a page will automatically add the page to the [[:Category:CommunityAdministrationNetwork|Category:Community Administration Network]] page. To use this template add '''<nowiki>{{CommunityAdministrationNetwork}}</nowiki>''' to at the top of the page you are creating/editing.</noinclude>

Versions

2007-11-21T07:09:06Z

L4m3r: fixed accidental repetition

BZFlag has undergone several different numbering schemes over the years (decades) that can be roughly categorized as follows: the 1.7 alphabet soup series, the 1.10 through 2.0 series, and the "new" triplet system currently in place. The information in follwoing regarding BZFlag's versioning scheme pertains to the "new" triplet system currently in use.

Ever since the unreleased 1.9 development revision, BZFlag has been using a '''MAJOR.MINOR.PATCH''' version numbering scheme that is familiar to many open source software projects. In this triplet version numbering scheme, the '''MAJOR''' number implies predominant backwards software compatibility; the '''MINOR''' number represents feature additions and enhancements; and the '''PATCH''' number is iterated releases of that given '''MAJOR.MINOR''' version. Each number in that triplet is independent and is not necessarily just a single digit for each either (e.g., 2.10 is ''not'' the same as 2.1.0 nor 2.0.10). For brevity, releases since 2.0 can generally be referred to only using the '''MAJOR.MINOR''' revision, leaving the '''PATCH''' version number off.

In order to "encourage" upgrades and facilitate making enhancements and bug fixes to the game, BZFlag's developers (intentionally) break the game protocol from time to time where new clients are released that will not work with previous releases. Starting with BZFlag version 2.0, the '''MAJOR''' number in BZFlag's versioning triplet '''''represents backwards-compatibility'''''. That is to say that all clients with a version number starting with a 2 will (only) work with others of that 2 series.

''Development of a new '''MAJOR''' version of BZFlag occurs as the previous '''MAJOR''' version number's '''99th''' '''MINOR''' revision. (e.g., 2.99 becomes 3.0, 3.99 becomes 4.0)'' The '''99th''' development revision is necessarily treated special and generally not compatible with anything but itself.

As compatible releases and enhancements are made to the game, they are released with an ''even-numbered'' '''MINOR''' version number (e.g. 3.'''0''' or 2.'''2''' or 3.'''2'''.6 etc). Versions of the game with an ''odd-numbered'' '''MINOR''' version number represents development-only versions that should not be used by non-developers under any circumstances ''(i.e., you're on your own, no support or guarantees are offered)''. Again, revisions with an '''''odd''''' second number represent '''''developer revisions''''' and those with an '''''even''''' second number are the '''''public revisions'''''.

The '''PATCH''' number in the version triplet counts publicly posted revisions for a given '''MAJOR.MINOR''' version. Since the BZFlag developers do intentionally provide (pre-release, alpha, beta) versions the game before a ''final'' post is made, those releases merely have the '''PATCH''' number incremented. Basically, the '''PATCH''' number can be looked at as how many times files have been publicly posted for a given '''MAJOR.MINOR''' version.

Labels and comments that a given release is an ''RC'' (Release Candidate) version or that it's a ''beta'' or an ''alpha'' release are merely inteded to describe the stability of a given version but are '''not''' part of the version itself. Lower patch numbers on a developer revision (where the '''MINOR''' number is an ''odd-number'') tend to imply less stability whereas higher patch numbers tend to imply greater stability. On non-developer releases, the number is generally only incremented and reposted if there was something deficient with the version already posted.

== Revision number examples ==

2.99.0 is a developer revision that will become the next 3.0 major release. Only developers should be using this revision.

2.99.27 is the 28th developer revision of 2.99, perhaps approaching some sort of beta or release-candidate status for the 3.0 release. Only developers and testers should be using this revision.

3.0.0 is a new release of a BZFlag client that is incompatible with all previous versions. This revision is for everyone.

3.0.9 is the 10th release of the 3.0 client, only providing minor bug and build fixes. This revision is for everyone.

3.1.0 is a developer revision of the 3 series, compatible with other version 3 clients and a pre-release candidate for the 3.2 release. Only developers should be using this revision.

3.12.4 is the 5th patch update of the 3.12 public release intended for everyone. There were six compatible versions released prior to this version: 3.0, 3.2, 3.4, 3.6, 3.8, and 3.10

3.2.5 is the 6th publicly posted release of version 3.2, serving enhanced functionality over the previous 3.0 clients while remaining compatible with other 3 series clients. This revision is for everyone.

3.99.0 is a developer revision that will become the next 4.0 major release. Only developers should be using this revision

== Released versions of BZFlag ==
There are currently 34 open source versions of BZFlag. Versions earlier then 1.7c-X were closed source.

The versions in chronological order are;

* [[BZFlag 1.7c-1]]
* [[BZFlag 1.7c-2]]
* [[BZFlag 1.7c-2-1]]
* [[BZFlag 1.7c-2-2]]
* [[BZFlag 1.7c-2-3]]
* [[BZFlag 1.7d-1]]
* [[BZFlag 1.7d-2]]
* [[BZFlag 1.7d-3]]
* [[BZFlag 1.7d-4]]
* [[BZFlag 1.7d-5]]
* [[BZFlag 1.7d-6]]
* [[BZFlag 1.7d-7]]
* [[BZFlag 1.7d-8]]
* [[BZFlag 1.7d-9]]
* [[BZFlag 1.7e]]
* [[BZFlag 1.7e1]]
* [[BZFlag 1.7e2]]
* [[BZFlag 1.7e4]]
* [[BZFlag 1.7e6]]
* [[BZFlag 1.7g0]]
* [[BZFlag 1.7g2]]
* [[BZFlag 1.10.0]]
* [[BZFlag 1.10.2]]
* [[BZFlag 1.10.4]]
* [[BZFlag 1.10.6]]
* [[BZFlag 1.10.8]]
* [[BZFlag 2.0.0]]
* [[BZFlag 2.0.2]]
* [[BZFlag 2.0.4]]
* [[BZFlag 2.0.6]]
* [[BZFlag 2.0.8]]
* [[BZFlag 2.0.9]]
* [[BZFlag 2.0.10]]
* [[BZFlag 2.2]]
* [[BZFlag SVN]]

[[Category:History]]

Bz eFlagDroppedEvent

2007-11-16T22:14:45Z

L4m3r: /* Overview */ drooped -> dropped ;)

{{BZFS_API_Doc}}
{{BZFS_API_Events}}

==Overview==
The '''bz_eFlagDroppedEvent''' is an API event that is called each time a flag is dropped by a player.

==Data==
'''bz_eFlagDroppedEvent''' returns the '''bz_FlagDroppedEventData_V1''' data class.

{| border="1" cellpadding="20" cellspacing="0"
!name
!type
!value desription
|-
|eventType
|[[Event(API)|bz_eEventType]]
|bz_eFlagDroppedEvent
|-
|playerID
|int
|The player that dropped the flag
|-
|flagID
|int
|The flag ID that was dropped
|-
|pos
|float[3]
|the position the flag was dropped at
|}

==Uses==
This event is a notification only event, none of the data returned can be changed. If the plug-in wishes to change the spawning position of a flag it should use the [[bz_eFlagResetEvent]]

==History==
In Version 2.0.x of BZFlag the data class for this event was named '''bz_FlagDroppedEvenData''' and contains the same data.

[[Category:BZFS_API_Docs]]
[[Category:BZFS_API_Events]]

Ideas

2007-07-03T05:49:37Z

L4m3r: /* Maps, Mapping, and BZW */ more movage

{{Old}}
NOTE: These are just possibilities. We won't be implementing everything here.<br>

Commentary may include personal comments by developers.

= Editing this page =

Feel free to make changes and updates to this page whenever possible. If you have any questions, feel free to [[Getting Help|ask for help]]. If you wish to make major changes to this page (i.e. remove large amounts of old ideas), please warn us ahead of time.

== Adding ideas ==
* Please remember to make sure your idea isn't already here or on the [[Rejected Ideas]] page.
* Flag ideas should be placed on [[Flag Ideas]], not here.
* Add a row to the appropriate category (at the bottom, please) and fill it in with your idea.
* Sign your idea in the third column with three tildes: <nowiki>~~~</nowiki>
* Put the submission date in the fourth column
* Describe in full and make sense!
* Leave the status column white and fill it with (Unknown).

== Adding commentary ==
* Precede your comment with an asterisk: <nowiki>*</nowiki>
* Sign your comment with four tildes: <nowiki>~~~~</nowiki>
* Be nice, polite, and constructive.
* Contribute something when you comment. Saying whether or not you like an idea is pointless if you don't explain yourself.

== Cleaning up ==
To help keep this page current, old ideas should be removed when they're implemented (after each stable release, hence the "SVN" status). If you spot any ideas that were implemented prior to the latest stable release of BZFlag, please remove it.

= The list =
<div align="center">
{| cellpadding="10" cellspacing="1" border="1"
|+align="bottom"|''Legend''
|-
|style="background-color:#FF00FF;"|'' ''
|Implemented as a server-side plug-in
|-
|style="background-color:#0080FF;"|'' ''
|SVN (Implemented and will be in next release)
|-
|style="background-color:#00FFFF;"|'' ''
|In progress (Implementing)
|-
|style="background-color:#00FF00;"|'' ''
|Good Idea
|-
|style="background-color:#808080;"|'' ''
|Idea
|-
|style="background-color:#FFFF00;"|'' ''
|Vague, not understood, or in need of work
|-
|style="background-color:#FF8000"|'' ''
|Rejected, but can be implemented as a server plug-in
|-
|style="background-color:#FF0000;"|'' ''
|Rejected
|-
|style="background-color:#FFFFFF"|'' ''
|Unknown (new)
|}
</div>

== General/Gameplay ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Add support for 5 (or more) button mice
|style="background-color:#00FF00;"|Great Idea
|
|(Unknown)
|(Old)
|-
|Better physics
|style="background-color:#00FFFF;"|In progress
|
*Planning, some changes in CVS.
|Unknown
|(Old)
|-
|SELF-DESTRUCT BLAST RADIUS: Self Destruct (delete key) should have a blast radius similar to Shock Wave, perhaps larger. If you get shot during the self-destruct count down, that should also trigger the same blast. If I gotta go, I want to take someone with me.
|(Unknown)
|
|BearRiver
|(Old)
|-
|3-second (or however long) 'invulnerability' for incoming tanks - but they can't shoot
|style="background-color:#808080;"|Idea
|
*I could see this backfiring... your spawn attracts opponents to come, wait, and blast you when you lose invincibility. -L4m3r
|MORPH
|(Old)
|-
|Ability to turn off ricochet for laser flag but allow ricochet for bullets... or let them bounce only n times.. OR implement mirror buildings/walls. Should go for some interesting self-kills when combined with the no-radar/bullet bounce
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Smart LockOn for GM - won't lock on to your teammates (configurable in server)
|style="background-color:#808080;"|Idea
|
*I don't like this idea, there should be at least *some* risks to using this weapon. Personally, I think there should be more (not fewer) risks to holding this weapon; I'd like to see the thing overheat and explode (killing the holder) if it's fired too often in a short period of time. -M. Jetleb
|MORPH
|(Old)
|-
|Small jumps
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Server option for genocide flag - if you're killed while you have it, your team dies :^)
|style="background-color:#808080;"|Idea
|
*Feasible with a plug-in, too. -L4m3r
|MORPH
|(Old)
|-
|for broadband or LAN connections - voice chat for teams
|style="background-color:#808080;"|Idea
|
*I really think that you can do this with another service; I'm not sure if being part of BZFlag would be a good idea due to size and bandwidth issues.
|MORPH
|(Old)
|-
|Tank avatars (uploadable tank images) - have to think about shapes, though - someone could make a 1x1x1 pixel tank - that would suck - or a tank that looks like a building or pyramid. Clients don't have to accept downloading of avators (just view other tanks in default mode). Or just s-e-l-e-c-t from a certain number of predefined avatars that could come with the bzflag distribution. Or client provides a URL to download their avatar (saves server bandwidth).
|style="background-color:#808080;"|Idea
|
*Might not be implemented. Requires discussion; we may want to consider making the computer force a minimum size or something similar.
*How about uploadable flag graphics?
|MORPH
|(Old)
|-
|'Kamikaze' option for players - can take someone out by suicide
|style="background-color:#808080;"|Idea
|
*Server option if implemented.
*Implemented with a plugin by Theme97
|MORPH
|(Old)
|-
|Server option: everyone is radar-stealthed by default unless you get a 'radar' flag. You can still see all buildings, pyramids, teleports, and arena walls, though.
|style="background-color:#00FF00;"|Good idea
|
*Make them use their window. ;)
*Given the fairly narrow field of view out the window and the time it takes to turn a tank all the way around for a look-see, I think this could be frustrating. How about everyone starts out with minimum range radar instead and gets longer ranges with an appropriate flag? -M. Jetleb
|MORPH
|(Old)
|-
|Option for above: if you pick up GM or Laser, you're visible on radar to everyone whether they've got a radar flag or not
|style="background-color:#00FF00;"|Good idea
|
|MORPH
|(Old)
|-
|Selectable 'ricochet' fire - hold down shift key or something and your bullets won't ricochet
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Server option - tanks only have a certain number of times they can jump (gets reset when you get killed)
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Multiple-shields (server option for shield flags, or can be random - can get hit x number of times)
|style="background-color:#808080;"|Idea
|
*This is pretty much moot now. It's been shot down by the devs at least once, and a similar effect can be achieved by setting _shieldFlight to a very small number. This effectively provides as many hits as _maxFlagGrabs. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|Configurable 'radarless' and/or 'blind' zones in the arena - can't see what's in there on radar or via visuals
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Tank collisions - why can tanks drive through each other? Weird.
|style="background-color:#00FF00;"|Good Idea
|
*Lag could be a big problem here. If implemented, it must be impossible for two tanks to get stuck to each other. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|When tanks collide - great opportunity to implement tank damage concept, especially if one of them is moving especially fast, or has momentum flag, etc. Can push a tank off a building if your pushing them from their side.
|style="background-color:#808080;"|Idea
|
*Tank damage won't happen, but the kinetics could be neat, especially for mid-air collisions. It would certainly make "jump dancing" more interesting. [[User:L4m3r|L4m3r]]
|Morph
|(Old)
|-
|If a tank explodes right next to another tank, the other tank can be destroyed or get damaged
|style="background-color:#808080;"|Idea
|
*Somewhat implemented with the [[ShockwaveDeath]] plug-in. It would probably not be too hard to implement something similar (with a plugin) without shockwaves. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|Skins or views- In-tank mode, bumper mode, out-of-cab mode, chase mode.
|(Unknown)
|
|MORPH
|(Old)
|-
|Weapon extension packs.
|style="background-color:#FFFF00;"|(Unknown)
|
*Huh? Explain, please. [[User:L4m3r|L4m3r]]
|iPod
|(Old)
|-
|The ability to choose tanks, but they all die at one shot. maybe the jump height, speed, turn speed, acceleration, size can be preset.
|(Unknown)
|
|iPod
|(Old)
|-
|Option to choose different kinds of tanks. Different tanks could be weighted with different strengths and weaknesses. (almost like having a default flag). Would also need some form of health/damage status measurement, not just single hits. For example, there could be a larger, heavily armored tank that has powerful weapons, but moves slowly, versus a small, light, fast tank which is difficult to hit, but very low armor to protect from hits.
|(Unknown)
|
|Cue
|(Old)
|-
|What about a radar that only covers visible areas (don't passing through buildings/pyramids) ? This would leads to more placement tactics).
|(Unknown)
|
|K<nowiki>'</nowiki>limero
|(Old)
|-
|Always random respawn. Currently in CTF games first respawn is at own base. This can be abused by leaving and rejoining to get near base. This leave/rejoing trick is considered to be a mild form of cheating by many. Always random respawn would make it useless.
|(Unknown)
|
* I believe there is a plug-in for this. [[User:L4m3r|L4m3r]] 22:38, 30 April 2007 (EDT)
|abli
|(Old)
|-
|multiple (3?) jump stengths mini, normal, max...just the thing to confuse the opponents that expect one and you're off doing the other.
|(Unknown)
|
|kitchen
|(Old)
|-
|Anti camping. The ability to add "no camping zones" to areas of a map or to the entire map. Campers would be messaged that they're in a no camping zone, better start moving and have a prescribe number of seconds to move away or die. If a player returns to the same NCZ (no camping zone) and receives x warnings then he's disconnected. NCZs could be marked by a different color shade from a "normal" spot and could be exempt to a single team (like at their flag base). It's just a rough idea.
|(Unknown)
|
|pherris
|(Old)
|-
|Shield Flag Changes: Give Shield flag a radius, and draw it like a moving less opaque blue shockwave. Any tanks inside the shield radius would be protected, until the shield got hit a certain number of times.
|(Unknown)
|
|YHARG
|(Old)
|-
|At our company, we instituted a voluntary policy of dropping flags after 1 kill. Prevents slaughters and keeps things rolling more. It'd be great to be able to have the game do this for us, plus I'd love to see it turned on at external sites.
|(Unknown)
|
|TomMatelich
|(Old)
|-
|Server option: default powers -- flag(s) that everyone in the game automatically has (this wouldn't count as holding a flag). For example, the current Jumping option would == including Jumping as a default power.
|(Unknown)
|
|NebNamwen
|(Old)
|-
|Shot Aiming. Basically the center shot aim box could be moved left and right as far as the edge of the view window. (This would be enabled by default.) If the map is a vertical one a server option could be enabled so that vertical aiming could be enabled (using the same concept as horizontal aiming.) The aiming would be automatically centered by a button or key. These options could be mapped to a second joystick access, mouse scroll wheel or keyboard buttons.
|(Unknown)
|
* Lateral shooting would basically be the same as a rotating turret, and this idea has been shot down many times. Vertical shooting has been poo-pooed also. [[User:L4m3r|L4m3r]] 01:45, 3 July 2007 (EDT)
|NN
|6/20/07
|}
</div>

== UI ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Make option to show previous players list
|style="background-color:#808080;"|Idea
|
|(Unknown)
|(Old)
|-
|Make ALL server options available from the menus
|style="background-color:#808080;"|Idea
|
*There are a LOT of server options, and this could add quite a bit of clutter. If you need more than a basic game, you should probably learn to start BZFS from the command line anyway. -L4m3r
|MORPH
|(Old)
|-
|Separate windows for player messages & server messages
|style="background-color:#00FF00;"|Good idea.
|
|MORPH
|(Old)
|-
|Message log
|style="background-color:#00FF00;"|Good idea.
|
|MORPH
|(Old)
|-
|Send message to everyone 'but' specified player (crosses team boundaries, or not)
|style="background-color:#808080;"|Idea
|
*Hmm. Everybody BUT a specified player? [M. Jetleb -> as in: "Let's all get the GM guy" without the GM guy knowing he's facing a co-ordinated attack - I like this idea)
|MORPH
|(Old)
|-
|The ability to see what the world is like before connecting to the server.
|(Unknown)
|
|iPod
|(Old)
|-
|Multi-monitor support (i.e., radar on one screen, window on another, chat/event log on a third)
|(Unknown)
|
|bhtooefr
|(Old)
|-
|Make a part in bzflag to put up a real server. 1st screen has the flags you want, next page is to find the MAP file that you created on your hard drive, next page pick if you want jumping etc.
|(Unknown)
|
|Colin
|(Old)
|-
|}
</div>

== Technical ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Better network handling
|style="background-color:#00FFFF;"|In progress
|
|(Unknown)
|(Old)
|-
|Better robot AI
|style="background-color:#808080;"|Idea
|
*Don't know if players would like it or not in multiplayer game. Pluggable or scriptable robot AI , maybe? - Code must be restructured first
*Server side bots are coming! [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT)
|(Unknown)
|(Old)
|-
|Better positioning of tanks
|style="background-color:#808080;"|Idea
|
*BZFlag already does this, but the algorithm is bad. Needs work.
|MORPH
|(Old)
|-
|Serious multithreaded design - shouldn't lock up interface while looking for servers, or doing anything else. This program is way-unstable on Windows
|style="background-color:#00FFFF;"|In Progress
|
*We're working on these problems; many complaints are due to people still using old servers/clients.
|MORPH
|(Old)
|-
|Some type of BZFlag GUID* to ban players who cheat - won't accept players who disable their GUID, etc.

<nowiki>*</nowiki>Global Unique Identifier, sort of like an IP addrss, but permanent. Usually a number. Problem occurs when you lose your GUID (have to reformat your HD, etc. How do you keep someone from hacking their GUID, or setting up a modified BZFlag server for identity theft, etc.
|(Unknown)
|
*I doubt this is even possible, let alone practical. What about people who play from more than one location? And, because this is an open-source game, it would probably be cracked in minutes. Any verification can be spoofed, or at least altered. there is no foolproof way to permanently ban someone. -L4m3r
|MORPH
|(Old)
|-
|To prevent cheating - the server determines what flags & abilities each tank has (possible?)
|style="background-color:#00FF00;"|In Progress
|
*Seriously being considered. This would also have the advantage of allowing different versions of clients and servers to work together. Yes, it's possible, but this type of change will mean a change in the network protocols.
*Being worked on for 2.2
|MORPH
|(Old)
|-
|BZFlag for mac in separate data and application files.
|(Unknown)
|
|iPod
|(Old)
|-
|J2ME client (allows one to play on a cell phone), would use radar
|(Unknown)
|
|bhtooefr
|(Old)
|-
|Special 'open source' BZFlag version (server and client) which is guaranteed to be compatible with all other BZFlag versions.
|(Unknown)
|
*BZFlag is already open-source, and making a universally-compatible client is not even remotely practical. Incompatibility is part of why the game breaks off new versions in the first place. [[User:L4m3r|L4m3r]]
|Orca
|(Old)
|-
|}
</div>

== Game Modes, Team Play, and Scoring ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Tounament mode
|style="background-color:#808080;"|Idea
|
*Great Idea?
|(Unknown)
|(Old)
|-
|When you shoot someone on your own team, instead of both of you blowing up, neither is destroyed, and their score goes up one, while your's goes down one. This would make teamkilling impossible and greatly discourage traitors as well.
|style="background-color:#808080;"|Idea
|
*But then couldn't cheaters spawn two clients and ramp up their scores by teamkilling their other login? --YHARG
|Trigger Happy Nerd
|(Old)
|-
|A new gameplay mode- Takes two to tank. One to control the (rotating) turret, the other drives. KIA switches positions. "Teamplay" but all in one tank.
|(Unknown)
|
*I see serious lag issues with this... How does Halo do it? ;) -L4m3r
*The main problem with this idea is coordination. If one person were to leave, the tank would be crippled. You COULD solve this by having the person switch to normal mode, but this could cause considerable jerking between modes on a busy server. [[User:F687s|F687s]] 22:13, 20 June 2007 (EDT)
|MORPH
|(Old)
|-
|Turret mode, If enabled by the server (Can be manditory with automatic grouping). One user drives and the other shoots, Turret mode tanks get double points (But onyl take one from the target). lost double points if killed. Have double ammo, And controllable speed (Max = _tankSpeed * 2 Min = _tankSpeed). Plus it takes 2 shots to kill a turret mode tank. Points gained and lost by turret tanks are divided evenly between the users, Unless the server is all turret mode, in h which case two users are displayed as one.
|(Unknown)
|
|Dogbert
|(Old)
|-
|Ability for a team to vote to 'banish' someone from their team
|style="background-color:#808080;"|Idea
|
*Possibly unfair to newer players. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|There should be a game of cops and robbers. The teams can change after about 10 mins or so.
|style="background-color:#FFFF00;"|(Unknown)
|
|iPod
|(Old)
|-
|A special FFA Game mode "Team by Flags". This means, same Flag = same Team, so if there is a Tank with Rapid fire, and you pick up Rapid fire, you are automatically handled as Team member (this means, killing the other Tank with Rapid fire will be handled the same way as when killing a team member). YHARG: Funky idea: what about a game mode where teams shared flag abilities? Like, each player on a team's flag applies to the whole team. This could make for some interesting combos...
|(Unknown)
|
|Agonizer
|(Old)
|-
|Make life trickier for the Rogue Team; with a mix of Rogues and Colored Teams, the Rogues have more targets. This should also change the effect of the Masquerade flag - perhaps your tank is invisible to Rogues (like Cloaking)?
|(Unknown)
|
|NickGrim
|(Old)
|-
|A server option to make deaths not affect your score unless they were self-inflicted/team (the method used by many online games). This would encourage more aggressive play, because it's worth going out and blasting. As it is, you've got a very good chance by just phantoming/OOing out of the way and keeping you score at zero to stay in the top three places! It would also help fix the rather unfair situation of spawning just below a building on which someone is GM-camping...there's pretty much no way to escape, so you lose a point.
|(Unknown)
|
|LionsPhil
|(Old)
|-
|Don't show individual score in CTF games. This might help teamplay as it reduces the incentive to run around as if it would be FFA.
|(Unknown)
|
|abli
|(Old)
|-
|Give points to the player how captures flag in CTF. (Say, around 4 or so) After all, it is often a bigger job than killing someone.
|(Unknown)
|*Maybe the score could be based the number of tanks in the other team, similar to shooting someone w/ geno. This can also discourage people from capturing thier own flag by scoreing the negative number of teamates. I'm not sure if the individual scores of the players of the captured team (other than the one who captures the flag) should be affected however. [[User:Sparky1|Sparky1]] 09:44, 21 May 2007 (EDT)
|abli
|(Old)
|-
|Ducati/Freestyle "Roles" mode: Make a game mode where players are presented with a list of flag choices (limitable to a few roles, if wanted) at respawn or connect time, and are forced to use this flag for the remainder of their connection/tank life. This would be really useful in the case of stealth vs. seer, where you could choose to be stealth or seer, but couldn't switch between them. Another idea would be high speed vs. quick turn. Or steamroller vs. machine gun... Team play would have the interesting effect of people banding together and people with each role on the team. Especially in stealth vs. seer, where a seer team member could warn the team about enemies! There would be no team flags/bases.
|(Unknown)
|
|YHARG
|(Old)
|-
|New game called tag were someone is it and they shoot someone else and there it and ect.
|(Unknown)
|
|Supermatthew
|(Old)
|-
|Also a new game called "Hide and seek" were everyone is clocked(think thats it, were you don't see them on radar) except one who is it. he needs to find someone and shoot them then hese cloked and who was shot is not. Also when someone is shot there sent back to Ground zero( 0X, 0Y, 0Z ) so they can't shoot who ever just shot them.
|(Unknown)
|
|Supermatthew
|(Old)
|-
|"Cat" game: when a player dies, he/she respawns automaticaly, after 3 secs or so. When they have respawned 9 times, they can no longer spawn, and are observers. The one who lasts the longest wins. Games are timed.
|(Unknown)
|
|(Unknown)
|4/20/2007
|-
|}
</div>

== Maps, Mapping, and BZW ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Materials that don't allow OO and PZ to go through
|style="background-color:#808080;"|Idea
|
*Would be nice for multilevel worlds made with the new ability to have objects above the ground.
*Sounds awesome! TD-Linux 17:41, 12 March 2007 (EDT)
*As a special case, there could be Zoned objects (objects that only respond to PZ and maybe OO; normal tanks behave like PZ through these objects). [[User:Sparky1|Sparky1]] 18:05, 21 May 2007 (EDT)
|(Unknown)
|(Old)
|-
|Differently-shaped teleporters (circles, triangles, etc.)
|style="background-color:#808080;"|Idea
|
*probably low priority
|MORPH
|(Old)
|-
|360 degree teleports - hit a spot on the ground or in the air from any direction and you teleport
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Configurable random teleporters - teleports to a different location every time
|style="background-color:#808080;"|Idea
|
*Idea is a bit vague... randomized teles are implemented if you use multiple links. Is this what is meant by this suggestion? -L4m3r
|MORPH
|(Old)
|-
|Triggers in levels
|style="background-color:#FFFF00;"|(Unknown)
|
*Triggers for what? unless you're talking about AI, this could most likely be handled with a server plug-in. [[User:L4m3r|L4m3r]]
|Dragonstar
|(Old)
|-
|wraparound world - radar remains centered on your current position. Internally, objects leaving the north border reappear to the south, but from the user's radar / visible perspective, you just see to the horizon. I believe this is how the original Battlezone worked. There are some implications: laser would need a range limit.
|(Unknown)
|
|nsayer
|(Old)
|-
|As a generalization to the wraparound world concept, how about the option of making a map based on geometry that’s non-Euclidean, for example spherical or hyperbolic. Jumping/flying, the shape of the tanks/objects, and bullet trajectories would also be affected by this global geometry. It would be like a world that has a high gravitational field, or a world situated near a wormhole.
|(Unknown)
|
|[[User:Sparky1|Sparky1]]
|5/21/2007
|-
|-
|Get rid of the PZ flag and replace it w/ special telporters that do the same thing (they could be called "zoners", and should probably look different from regular teleporters). This way superflags, badflags, and team flags can all be zoned (without needing an exception to the restricition against using more than one flag at a time). The above idea of other zoned objects would play a major role here. Zoned flags can only be picked up by zoned tanks. Flags can spawn zoned, or become zoned by being carried by an unzoned tank that becomes zoned by going through a zoner. Likewise, a zonedflag becomes unzoned when a zoned tank carries it through a zoner. Unzoned tanks respond to shots from zoned flags the same way zoned tanks respond to shots from unzoned flags. For example: when zoned, L, WG, geno, and GM do not kill unzoned tanks (zoned GM will still lock onto any tank, and zoned geno would still kill every tank on the same team as the zoned tank that was shot). Although, flags like SW and SB would still kill any tank regardless of thier zoning status. As an extension to this idea one team in a CTF game could start out zoned, i.e. thier base is zoned and they initially spawn zoned. In order for the unzoned team to capture the zoned team's flag, the flag must become unzoned, and vice versa for the zoned team. This way new possibilities exist, like two bases could be superimposed as long as one base is zoned and the other is not. Another possible extension is different kinds of zones (w/ corespondingly different kinds of zoners) for CTF involving more than two teams. The relationship between differently zoned tanks would be the same as the relationship between zoned and unzoned tanks.
|(Unknown)
|
|[[User:Sparky1|Sparky1]]
|5/21/2007
|}
</div>

== Server Options, Administration, Plug-ins, and the Plug-in API ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Ability to configure server to turn somethings off or on depending on number of players - for instance, turn off ricochet after a certain number of players are connected, turn off GM & laser if a certain number of players aren't playing (GM & Laser with 2 players is kinda ridiculous)
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Allow custom-made weapons with a Object-Oriented scripting language (sorta like Liero AI uses: http://helios.et.put.poznan.pl/~sskowron/liero/index.html )
|(Unknown)
|
|Dragonstar
|(Old)
|-
|Preset world weapons that can be fired manually by admins from within BzFlag.
|(Unknown)
|
|Dogbert
|(Old)
|-
|}
</div>

== Graphics & Sound ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Sounds of tanks moving.
|(Unknown)
|
|iPod
|(Old)
|-
|Have different tank death scenes for the dying tank point of view. I realize there is some time needed for one to die and respawn, but the jumping effect one sees when killed irritates me to no end! I'd be happier if all faded to black or white or orange and had text across the screen saying ""respawning... please wait"" :) Also, when killed and your tank was moving toward a building, it just falls right thru it until it hits the ground.. wrong physics there! Splatter or tumble or shatter or something :)
|(Unknown)
|
|Robi
|(Old)
|-
|Custom color schemes for rogue players. The turret and body components can be chosen to be one of a predefined set of colors (e.g. red, yellow, black, white, blue, green, purple...). The game prohibits choosing a color scheme that matches a team scheme (e.g. red turret with red body) and the limited set stops someone choosing a shade which is nearly a team color (e.g. 0xFE0000 instead of 0xFF0000) (and also save texture memory, I think).
|(Unknown)
|
|LionsPhil
|(Old)
|-
|Allow a small decal on the back of the top of the tank. (think Half-Life's customizable spraypaint). Possibly also apply it to any held flag?
|(Unknown)
|
|LionsPhil
|(Old)
|-
|wireframe mode! man, this would make the game ten times cooler for nostalgia
|(Unknown)
|Already implemented, debug must be on --[[User:BinarySpike|BinarySpike]] 18:10, 10 May 2007 (EDT)
|rjbs
|(Old)
|-
|I'd like to see something more interesting done with the sky... maybe there could be a little ufo (easter egg) that would fly around occasionally? Tux on a ufo! ;)
|(Unknown)
|
|YHARG
|(Old)
|-
|Flag decals: Each flag would have a little icon/decal showing it's type ONLY when held by a player. It's kind of nice to be able to surprise people with an undercover shockwave, but doesn't make sense to have to right click (identify) or check the user list to see what flag someone has.
|(Unknown)
|
|YHARG
|(Old)
|-
|Background music! : (This can be done with an external media player so it shouldn't be the heighest priority, It would be nice to be able to control your music from within BzFlag)
|(Unknown)
|More usefully, you could just map key combinations to commands, rather than wasting time supporting all the various music players on every OS BZFlag supports. I don't know whether that would work so well on Windows, though. --[[User:77.97.207.100|77.97.207.100]] 10:14, 30 May 2007 (EDT)
|YHARG
|(Old)
|-
|}
</div>

== List Server and Other Global Services ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Multiple list servers, in case bzflag.org goes down (as it happened around feb. 15. 2004)
|(Unknown)
|Of course someone would need to pay for it. --[[User:BinarySpike|BinarySpike]] 18:10, 10 May 2007 (EDT)
|abli
|(Old)
|-
|}
</div>

[[Category:Development]]

Ideas

2007-07-03T05:46:04Z

L4m3r: /* General/Gameplay */ fix

{{Old}}
NOTE: These are just possibilities. We won't be implementing everything here.<br>

Commentary may include personal comments by developers.

= Editing this page =

Feel free to make changes and updates to this page whenever possible. If you have any questions, feel free to [[Getting Help|ask for help]]. If you wish to make major changes to this page (i.e. remove large amounts of old ideas), please warn us ahead of time.

== Adding ideas ==
* Please remember to make sure your idea isn't already here or on the [[Rejected Ideas]] page.
* Flag ideas should be placed on [[Flag Ideas]], not here.
* Add a row to the appropriate category (at the bottom, please) and fill it in with your idea.
* Sign your idea in the third column with three tildes: <nowiki>~~~</nowiki>
* Put the submission date in the fourth column
* Describe in full and make sense!
* Leave the status column white and fill it with (Unknown).

== Adding commentary ==
* Precede your comment with an asterisk: <nowiki>*</nowiki>
* Sign your comment with four tildes: <nowiki>~~~~</nowiki>
* Be nice, polite, and constructive.
* Contribute something when you comment. Saying whether or not you like an idea is pointless if you don't explain yourself.

== Cleaning up ==
To help keep this page current, old ideas should be removed when they're implemented (after each stable release, hence the "SVN" status). If you spot any ideas that were implemented prior to the latest stable release of BZFlag, please remove it.

= The list =
<div align="center">
{| cellpadding="10" cellspacing="1" border="1"
|+align="bottom"|''Legend''
|-
|style="background-color:#FF00FF;"|'' ''
|Implemented as a server-side plug-in
|-
|style="background-color:#0080FF;"|'' ''
|SVN (Implemented and will be in next release)
|-
|style="background-color:#00FFFF;"|'' ''
|In progress (Implementing)
|-
|style="background-color:#00FF00;"|'' ''
|Good Idea
|-
|style="background-color:#808080;"|'' ''
|Idea
|-
|style="background-color:#FFFF00;"|'' ''
|Vague, not understood, or in need of work
|-
|style="background-color:#FF8000"|'' ''
|Rejected, but can be implemented as a server plug-in
|-
|style="background-color:#FF0000;"|'' ''
|Rejected
|-
|style="background-color:#FFFFFF"|'' ''
|Unknown (new)
|}
</div>

== General/Gameplay ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Add support for 5 (or more) button mice
|style="background-color:#00FF00;"|Great Idea
|
|(Unknown)
|(Old)
|-
|Better physics
|style="background-color:#00FFFF;"|In progress
|
*Planning, some changes in CVS.
|Unknown
|(Old)
|-
|SELF-DESTRUCT BLAST RADIUS: Self Destruct (delete key) should have a blast radius similar to Shock Wave, perhaps larger. If you get shot during the self-destruct count down, that should also trigger the same blast. If I gotta go, I want to take someone with me.
|(Unknown)
|
|BearRiver
|(Old)
|-
|3-second (or however long) 'invulnerability' for incoming tanks - but they can't shoot
|style="background-color:#808080;"|Idea
|
*I could see this backfiring... your spawn attracts opponents to come, wait, and blast you when you lose invincibility. -L4m3r
|MORPH
|(Old)
|-
|Ability to turn off ricochet for laser flag but allow ricochet for bullets... or let them bounce only n times.. OR implement mirror buildings/walls. Should go for some interesting self-kills when combined with the no-radar/bullet bounce
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Smart LockOn for GM - won't lock on to your teammates (configurable in server)
|style="background-color:#808080;"|Idea
|
*I don't like this idea, there should be at least *some* risks to using this weapon. Personally, I think there should be more (not fewer) risks to holding this weapon; I'd like to see the thing overheat and explode (killing the holder) if it's fired too often in a short period of time. -M. Jetleb
|MORPH
|(Old)
|-
|Small jumps
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Server option for genocide flag - if you're killed while you have it, your team dies :^)
|style="background-color:#808080;"|Idea
|
*Feasible with a plug-in, too. -L4m3r
|MORPH
|(Old)
|-
|for broadband or LAN connections - voice chat for teams
|style="background-color:#808080;"|Idea
|
*I really think that you can do this with another service; I'm not sure if being part of BZFlag would be a good idea due to size and bandwidth issues.
|MORPH
|(Old)
|-
|Tank avatars (uploadable tank images) - have to think about shapes, though - someone could make a 1x1x1 pixel tank - that would suck - or a tank that looks like a building or pyramid. Clients don't have to accept downloading of avators (just view other tanks in default mode). Or just s-e-l-e-c-t from a certain number of predefined avatars that could come with the bzflag distribution. Or client provides a URL to download their avatar (saves server bandwidth).
|style="background-color:#808080;"|Idea
|
*Might not be implemented. Requires discussion; we may want to consider making the computer force a minimum size or something similar.
*How about uploadable flag graphics?
|MORPH
|(Old)
|-
|'Kamikaze' option for players - can take someone out by suicide
|style="background-color:#808080;"|Idea
|
*Server option if implemented.
*Implemented with a plugin by Theme97
|MORPH
|(Old)
|-
|Server option: everyone is radar-stealthed by default unless you get a 'radar' flag. You can still see all buildings, pyramids, teleports, and arena walls, though.
|style="background-color:#00FF00;"|Good idea
|
*Make them use their window. ;)
*Given the fairly narrow field of view out the window and the time it takes to turn a tank all the way around for a look-see, I think this could be frustrating. How about everyone starts out with minimum range radar instead and gets longer ranges with an appropriate flag? -M. Jetleb
|MORPH
|(Old)
|-
|Option for above: if you pick up GM or Laser, you're visible on radar to everyone whether they've got a radar flag or not
|style="background-color:#00FF00;"|Good idea
|
|MORPH
|(Old)
|-
|Selectable 'ricochet' fire - hold down shift key or something and your bullets won't ricochet
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Server option - tanks only have a certain number of times they can jump (gets reset when you get killed)
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Multiple-shields (server option for shield flags, or can be random - can get hit x number of times)
|style="background-color:#808080;"|Idea
|
*This is pretty much moot now. It's been shot down by the devs at least once, and a similar effect can be achieved by setting _shieldFlight to a very small number. This effectively provides as many hits as _maxFlagGrabs. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|Configurable 'radarless' and/or 'blind' zones in the arena - can't see what's in there on radar or via visuals
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Tank collisions - why can tanks drive through each other? Weird.
|style="background-color:#00FF00;"|Good Idea
|
*Lag could be a big problem here. If implemented, it must be impossible for two tanks to get stuck to each other. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|When tanks collide - great opportunity to implement tank damage concept, especially if one of them is moving especially fast, or has momentum flag, etc. Can push a tank off a building if your pushing them from their side.
|style="background-color:#808080;"|Idea
|
*Tank damage won't happen, but the kinetics could be neat, especially for mid-air collisions. It would certainly make "jump dancing" more interesting. [[User:L4m3r|L4m3r]]
|Morph
|(Old)
|-
|If a tank explodes right next to another tank, the other tank can be destroyed or get damaged
|style="background-color:#808080;"|Idea
|
*Somewhat implemented with the [[ShockwaveDeath]] plug-in. It would probably not be too hard to implement something similar (with a plugin) without shockwaves. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|Skins or views- In-tank mode, bumper mode, out-of-cab mode, chase mode.
|(Unknown)
|
|MORPH
|(Old)
|-
|Weapon extension packs.
|style="background-color:#FFFF00;"|(Unknown)
|
*Huh? Explain, please. [[User:L4m3r|L4m3r]]
|iPod
|(Old)
|-
|The ability to choose tanks, but they all die at one shot. maybe the jump height, speed, turn speed, acceleration, size can be preset.
|(Unknown)
|
|iPod
|(Old)
|-
|Option to choose different kinds of tanks. Different tanks could be weighted with different strengths and weaknesses. (almost like having a default flag). Would also need some form of health/damage status measurement, not just single hits. For example, there could be a larger, heavily armored tank that has powerful weapons, but moves slowly, versus a small, light, fast tank which is difficult to hit, but very low armor to protect from hits.
|(Unknown)
|
|Cue
|(Old)
|-
|What about a radar that only covers visible areas (don't passing through buildings/pyramids) ? This would leads to more placement tactics).
|(Unknown)
|
|K<nowiki>'</nowiki>limero
|(Old)
|-
|Always random respawn. Currently in CTF games first respawn is at own base. This can be abused by leaving and rejoining to get near base. This leave/rejoing trick is considered to be a mild form of cheating by many. Always random respawn would make it useless.
|(Unknown)
|
* I believe there is a plug-in for this. [[User:L4m3r|L4m3r]] 22:38, 30 April 2007 (EDT)
|abli
|(Old)
|-
|multiple (3?) jump stengths mini, normal, max...just the thing to confuse the opponents that expect one and you're off doing the other.
|(Unknown)
|
|kitchen
|(Old)
|-
|Anti camping. The ability to add "no camping zones" to areas of a map or to the entire map. Campers would be messaged that they're in a no camping zone, better start moving and have a prescribe number of seconds to move away or die. If a player returns to the same NCZ (no camping zone) and receives x warnings then he's disconnected. NCZs could be marked by a different color shade from a "normal" spot and could be exempt to a single team (like at their flag base). It's just a rough idea.
|(Unknown)
|
|pherris
|(Old)
|-
|Shield Flag Changes: Give Shield flag a radius, and draw it like a moving less opaque blue shockwave. Any tanks inside the shield radius would be protected, until the shield got hit a certain number of times.
|(Unknown)
|
|YHARG
|(Old)
|-
|At our company, we instituted a voluntary policy of dropping flags after 1 kill. Prevents slaughters and keeps things rolling more. It'd be great to be able to have the game do this for us, plus I'd love to see it turned on at external sites.
|(Unknown)
|
|TomMatelich
|(Old)
|-
|Server option: default powers -- flag(s) that everyone in the game automatically has (this wouldn't count as holding a flag). For example, the current Jumping option would == including Jumping as a default power.
|(Unknown)
|
|NebNamwen
|(Old)
|-
|Shot Aiming. Basically the center shot aim box could be moved left and right as far as the edge of the view window. (This would be enabled by default.) If the map is a vertical one a server option could be enabled so that vertical aiming could be enabled (using the same concept as horizontal aiming.) The aiming would be automatically centered by a button or key. These options could be mapped to a second joystick access, mouse scroll wheel or keyboard buttons.
|(Unknown)
|
* Lateral shooting would basically be the same as a rotating turret, and this idea has been shot down many times. Vertical shooting has been poo-pooed also. [[User:L4m3r|L4m3r]] 01:45, 3 July 2007 (EDT)
|NN
|6/20/07
|}
</div>

== UI ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Make option to show previous players list
|style="background-color:#808080;"|Idea
|
|(Unknown)
|(Old)
|-
|Make ALL server options available from the menus
|style="background-color:#808080;"|Idea
|
*There are a LOT of server options, and this could add quite a bit of clutter. If you need more than a basic game, you should probably learn to start BZFS from the command line anyway. -L4m3r
|MORPH
|(Old)
|-
|Separate windows for player messages & server messages
|style="background-color:#00FF00;"|Good idea.
|
|MORPH
|(Old)
|-
|Message log
|style="background-color:#00FF00;"|Good idea.
|
|MORPH
|(Old)
|-
|Send message to everyone 'but' specified player (crosses team boundaries, or not)
|style="background-color:#808080;"|Idea
|
*Hmm. Everybody BUT a specified player? [M. Jetleb -> as in: "Let's all get the GM guy" without the GM guy knowing he's facing a co-ordinated attack - I like this idea)
|MORPH
|(Old)
|-
|The ability to see what the world is like before connecting to the server.
|(Unknown)
|
|iPod
|(Old)
|-
|Multi-monitor support (i.e., radar on one screen, window on another, chat/event log on a third)
|(Unknown)
|
|bhtooefr
|(Old)
|-
|Make a part in bzflag to put up a real server. 1st screen has the flags you want, next page is to find the MAP file that you created on your hard drive, next page pick if you want jumping etc.
|(Unknown)
|
|Colin
|(Old)
|-
|}
</div>

== Technical ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Better network handling
|style="background-color:#00FFFF;"|In progress
|
|(Unknown)
|(Old)
|-
|Better robot AI
|style="background-color:#808080;"|Idea
|
*Don't know if players would like it or not in multiplayer game. Pluggable or scriptable robot AI , maybe? - Code must be restructured first
*Server side bots are coming! [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT)
|(Unknown)
|(Old)
|-
|Better positioning of tanks
|style="background-color:#808080;"|Idea
|
*BZFlag already does this, but the algorithm is bad. Needs work.
|MORPH
|(Old)
|-
|Serious multithreaded design - shouldn't lock up interface while looking for servers, or doing anything else. This program is way-unstable on Windows
|style="background-color:#00FFFF;"|In Progress
|
*We're working on these problems; many complaints are due to people still using old servers/clients.
|MORPH
|(Old)
|-
|Some type of BZFlag GUID* to ban players who cheat - won't accept players who disable their GUID, etc.

<nowiki>*</nowiki>Global Unique Identifier, sort of like an IP addrss, but permanent. Usually a number. Problem occurs when you lose your GUID (have to reformat your HD, etc. How do you keep someone from hacking their GUID, or setting up a modified BZFlag server for identity theft, etc.
|(Unknown)
|
*I doubt this is even possible, let alone practical. What about people who play from more than one location? And, because this is an open-source game, it would probably be cracked in minutes. Any verification can be spoofed, or at least altered. there is no foolproof way to permanently ban someone. -L4m3r
|MORPH
|(Old)
|-
|To prevent cheating - the server determines what flags & abilities each tank has (possible?)
|style="background-color:#00FF00;"|In Progress
|
*Seriously being considered. This would also have the advantage of allowing different versions of clients and servers to work together. Yes, it's possible, but this type of change will mean a change in the network protocols.
*Being worked on for 2.2
|MORPH
|(Old)
|-
|BZFlag for mac in separate data and application files.
|(Unknown)
|
|iPod
|(Old)
|-
|J2ME client (allows one to play on a cell phone), would use radar
|(Unknown)
|
|bhtooefr
|(Old)
|-
|Special 'open source' BZFlag version (server and client) which is guaranteed to be compatible with all other BZFlag versions.
|(Unknown)
|
*BZFlag is already open-source, and making a universally-compatible client is not even remotely practical. Incompatibility is part of why the game breaks off new versions in the first place. [[User:L4m3r|L4m3r]]
|Orca
|(Old)
|-
|}
</div>

== Game Modes, Team Play, and Scoring ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Tounament mode
|style="background-color:#808080;"|Idea
|
*Great Idea?
|(Unknown)
|(Old)
|-
|When you shoot someone on your own team, instead of both of you blowing up, neither is destroyed, and their score goes up one, while your's goes down one. This would make teamkilling impossible and greatly discourage traitors as well.
|style="background-color:#808080;"|Idea
|
*But then couldn't cheaters spawn two clients and ramp up their scores by teamkilling their other login? --YHARG
|Trigger Happy Nerd
|(Old)
|-
|A new gameplay mode- Takes two to tank. One to control the (rotating) turret, the other drives. KIA switches positions. "Teamplay" but all in one tank.
|(Unknown)
|
*I see serious lag issues with this... How does Halo do it? ;) -L4m3r
*The main problem with this idea is coordination. If one person were to leave, the tank would be crippled. You COULD solve this by having the person switch to normal mode, but this could cause considerable jerking between modes on a busy server. [[User:F687s|F687s]] 22:13, 20 June 2007 (EDT)
|MORPH
|(Old)
|-
|Turret mode, If enabled by the server (Can be manditory with automatic grouping). One user drives and the other shoots, Turret mode tanks get double points (But onyl take one from the target). lost double points if killed. Have double ammo, And controllable speed (Max = _tankSpeed * 2 Min = _tankSpeed). Plus it takes 2 shots to kill a turret mode tank. Points gained and lost by turret tanks are divided evenly between the users, Unless the server is all turret mode, in h which case two users are displayed as one.
|(Unknown)
|
|Dogbert
|(Old)
|-
|Ability for a team to vote to 'banish' someone from their team
|style="background-color:#808080;"|Idea
|
*Possibly unfair to newer players. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|There should be a game of cops and robbers. The teams can change after about 10 mins or so.
|style="background-color:#FFFF00;"|(Unknown)
|
|iPod
|(Old)
|-
|A special FFA Game mode "Team by Flags". This means, same Flag = same Team, so if there is a Tank with Rapid fire, and you pick up Rapid fire, you are automatically handled as Team member (this means, killing the other Tank with Rapid fire will be handled the same way as when killing a team member). YHARG: Funky idea: what about a game mode where teams shared flag abilities? Like, each player on a team's flag applies to the whole team. This could make for some interesting combos...
|(Unknown)
|
|Agonizer
|(Old)
|-
|Make life trickier for the Rogue Team; with a mix of Rogues and Colored Teams, the Rogues have more targets. This should also change the effect of the Masquerade flag - perhaps your tank is invisible to Rogues (like Cloaking)?
|(Unknown)
|
|NickGrim
|(Old)
|-
|A server option to make deaths not affect your score unless they were self-inflicted/team (the method used by many online games). This would encourage more aggressive play, because it's worth going out and blasting. As it is, you've got a very good chance by just phantoming/OOing out of the way and keeping you score at zero to stay in the top three places! It would also help fix the rather unfair situation of spawning just below a building on which someone is GM-camping...there's pretty much no way to escape, so you lose a point.
|(Unknown)
|
|LionsPhil
|(Old)
|-
|Don't show individual score in CTF games. This might help teamplay as it reduces the incentive to run around as if it would be FFA.
|(Unknown)
|
|abli
|(Old)
|-
|Give points to the player how captures flag in CTF. (Say, around 4 or so) After all, it is often a bigger job than killing someone.
|(Unknown)
|*Maybe the score could be based the number of tanks in the other team, similar to shooting someone w/ geno. This can also discourage people from capturing thier own flag by scoreing the negative number of teamates. I'm not sure if the individual scores of the players of the captured team (other than the one who captures the flag) should be affected however. [[User:Sparky1|Sparky1]] 09:44, 21 May 2007 (EDT)
|abli
|(Old)
|-
|Ducati/Freestyle "Roles" mode: Make a game mode where players are presented with a list of flag choices (limitable to a few roles, if wanted) at respawn or connect time, and are forced to use this flag for the remainder of their connection/tank life. This would be really useful in the case of stealth vs. seer, where you could choose to be stealth or seer, but couldn't switch between them. Another idea would be high speed vs. quick turn. Or steamroller vs. machine gun... Team play would have the interesting effect of people banding together and people with each role on the team. Especially in stealth vs. seer, where a seer team member could warn the team about enemies! There would be no team flags/bases.
|(Unknown)
|
|YHARG
|(Old)
|-
|New game called tag were someone is it and they shoot someone else and there it and ect.
|(Unknown)
|
|Supermatthew
|(Old)
|-
|Also a new game called "Hide and seek" were everyone is clocked(think thats it, were you don't see them on radar) except one who is it. he needs to find someone and shoot them then hese cloked and who was shot is not. Also when someone is shot there sent back to Ground zero( 0X, 0Y, 0Z ) so they can't shoot who ever just shot them.
|(Unknown)
|
|Supermatthew
|(Old)
|-
|"Cat" game: when a player dies, he/she respawns automaticaly, after 3 secs or so. When they have respawned 9 times, they can no longer spawn, and are observers. The one who lasts the longest wins. Games are timed.
|(Unknown)
|
|(Unknown)
|4/20/2007
|-
|}
</div>

== Maps, Mapping, and BZW ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Materials that don't allow OO and PZ to go through
|style="background-color:#808080;"|Idea
|(Unknown)
*Would be nice for multilevel worlds made with the new ability to have objects above the ground.
*Sounds awesome! TD-Linux 17:41, 12 March 2007 (EDT)
*As a special case, there could be Zoned objects (objects that only respond to PZ and maybe OO; normal tanks behave like PZ through these objects). [[User:Sparky1|Sparky1]] 18:05, 21 May 2007 (EDT)
|
|(Old)
|-
|Get rid of the PZ flag and replace it w/ special telporters that do the same thing (they could be called "zoners", and should probably look different from regular teleporters). This way superflags, badflags, and team flags can all be zoned (without needing an exception to the restricition against using more than one flag at a time). The above idea of other zoned objects would play a major role here. Zoned flags can only be picked up by zoned tanks. Flags can spawn zoned, or become zoned by being carried by an unzoned tank that becomes zoned by going through a zoner. Likewise, a zonedflag becomes unzoned when a zoned tank carries it through a zoner. Unzoned tanks respond to shots from zoned flags the same way zoned tanks respond to shots from unzoned flags. For example: when zoned, L, WG, geno, and GM do not kill unzoned tanks (zoned GM will still lock onto any tank, and zoned geno would still kill every tank on the same team as the zoned tank that was shot). Although, flags like SW and SB would still kill any tank regardless of thier zoning status. As an extension to this idea one team in a CTF game could start out zoned, i.e. thier base is zoned and they initially spawn zoned. In order for the unzoned team to capture the zoned team's flag, the flag must become unzoned, and vice versa for the zoned team. This way new possibilities exist, like two bases could be superimposed as long as one base is zoned and the other is not. Another possible extension is different kinds of zones (w/ corespondingly different kinds of zoners) for CTF involving more than two teams. The relationship between differently zoned tanks would be the same as the relationship between zoned and unzoned tanks.
|(Unknow
|
|[[User:Sparky1|Sparky1]]
|5/21/2007
|-
|Differently-shaped teleporters (circles, triangles, etc.)
|style="background-color:#808080;"|Idea
|
*probably low priority
|MORPH
|(Old)
|-
|360 degree teleports - hit a spot on the ground or in the air from any direction and you teleport
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Configurable random teleporters - teleports to a different location every time
|style="background-color:#808080;"|Idea
|
*Idea is a bit vague... randomized teles are implemented if you use multiple links. Is this what is meant by this suggestion? -L4m3r
|MORPH
|(Old)
|-
|Triggers in levels
|style="background-color:#FFFF00;"|(Unknown)
|
*Triggers for what? unless you're talking about AI, this could most likely be handled with a server plug-in. [[User:L4m3r|L4m3r]]
|Dragonstar
|(Old)
|-
|wraparound world - radar remains centered on your current position. Internally, objects leaving the north border reappear to the south, but from the user's radar / visible perspective, you just see to the horizon. I believe this is how the original Battlezone worked. There are some implications: laser would need a range limit.
|(Unknown)
|
|nsayer
|(Old)
|-
|As a generalization to the wraparound world concept, how about the option of making a map based on geometry that’s non-Euclidean, for example spherical or hyperbolic. Jumping/flying, the shape of the tanks/objects, and bullet trajectories would also be affected by this global geometry. It would be like a world that has a high gravitational field, or a world situated near a wormhole.
|(Unknown)
|
|[[User:Sparky1|Sparky1]]
|5/21/2007
|-
|}
</div>

== Server Options, Administration, Plug-ins, and the Plug-in API ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Ability to configure server to turn somethings off or on depending on number of players - for instance, turn off ricochet after a certain number of players are connected, turn off GM & laser if a certain number of players aren't playing (GM & Laser with 2 players is kinda ridiculous)
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Allow custom-made weapons with a Object-Oriented scripting language (sorta like Liero AI uses: http://helios.et.put.poznan.pl/~sskowron/liero/index.html )
|(Unknown)
|
|Dragonstar
|(Old)
|-
|Preset world weapons that can be fired manually by admins from within BzFlag.
|(Unknown)
|
|Dogbert
|(Old)
|-
|}
</div>

== Graphics & Sound ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Sounds of tanks moving.
|(Unknown)
|
|iPod
|(Old)
|-
|Have different tank death scenes for the dying tank point of view. I realize there is some time needed for one to die and respawn, but the jumping effect one sees when killed irritates me to no end! I'd be happier if all faded to black or white or orange and had text across the screen saying ""respawning... please wait"" :) Also, when killed and your tank was moving toward a building, it just falls right thru it until it hits the ground.. wrong physics there! Splatter or tumble or shatter or something :)
|(Unknown)
|
|Robi
|(Old)
|-
|Custom color schemes for rogue players. The turret and body components can be chosen to be one of a predefined set of colors (e.g. red, yellow, black, white, blue, green, purple...). The game prohibits choosing a color scheme that matches a team scheme (e.g. red turret with red body) and the limited set stops someone choosing a shade which is nearly a team color (e.g. 0xFE0000 instead of 0xFF0000) (and also save texture memory, I think).
|(Unknown)
|
|LionsPhil
|(Old)
|-
|Allow a small decal on the back of the top of the tank. (think Half-Life's customizable spraypaint). Possibly also apply it to any held flag?
|(Unknown)
|
|LionsPhil
|(Old)
|-
|wireframe mode! man, this would make the game ten times cooler for nostalgia
|(Unknown)
|Already implemented, debug must be on --[[User:BinarySpike|BinarySpike]] 18:10, 10 May 2007 (EDT)
|rjbs
|(Old)
|-
|I'd like to see something more interesting done with the sky... maybe there could be a little ufo (easter egg) that would fly around occasionally? Tux on a ufo! ;)
|(Unknown)
|
|YHARG
|(Old)
|-
|Flag decals: Each flag would have a little icon/decal showing it's type ONLY when held by a player. It's kind of nice to be able to surprise people with an undercover shockwave, but doesn't make sense to have to right click (identify) or check the user list to see what flag someone has.
|(Unknown)
|
|YHARG
|(Old)
|-
|Background music! : (This can be done with an external media player so it shouldn't be the heighest priority, It would be nice to be able to control your music from within BzFlag)
|(Unknown)
|More usefully, you could just map key combinations to commands, rather than wasting time supporting all the various music players on every OS BZFlag supports. I don't know whether that would work so well on Windows, though. --[[User:77.97.207.100|77.97.207.100]] 10:14, 30 May 2007 (EDT)
|YHARG
|(Old)
|-
|}
</div>

== List Server and Other Global Services ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Multiple list servers, in case bzflag.org goes down (as it happened around feb. 15. 2004)
|(Unknown)
|Of course someone would need to pay for it. --[[User:BinarySpike|BinarySpike]] 18:10, 10 May 2007 (EDT)
|abli
|(Old)
|-
|}
</div>

[[Category:Development]]

Ideas

2007-07-03T05:45:20Z

L4m3r: /* General/Gameplay */ Commentary and (Unknown) status, whoops

{{Old}}
NOTE: These are just possibilities. We won't be implementing everything here.<br>

Commentary may include personal comments by developers.

= Editing this page =

Feel free to make changes and updates to this page whenever possible. If you have any questions, feel free to [[Getting Help|ask for help]]. If you wish to make major changes to this page (i.e. remove large amounts of old ideas), please warn us ahead of time.

== Adding ideas ==
* Please remember to make sure your idea isn't already here or on the [[Rejected Ideas]] page.
* Flag ideas should be placed on [[Flag Ideas]], not here.
* Add a row to the appropriate category (at the bottom, please) and fill it in with your idea.
* Sign your idea in the third column with three tildes: <nowiki>~~~</nowiki>
* Put the submission date in the fourth column
* Describe in full and make sense!
* Leave the status column white and fill it with (Unknown).

== Adding commentary ==
* Precede your comment with an asterisk: <nowiki>*</nowiki>
* Sign your comment with four tildes: <nowiki>~~~~</nowiki>
* Be nice, polite, and constructive.
* Contribute something when you comment. Saying whether or not you like an idea is pointless if you don't explain yourself.

== Cleaning up ==
To help keep this page current, old ideas should be removed when they're implemented (after each stable release, hence the "SVN" status). If you spot any ideas that were implemented prior to the latest stable release of BZFlag, please remove it.

= The list =
<div align="center">
{| cellpadding="10" cellspacing="1" border="1"
|+align="bottom"|''Legend''
|-
|style="background-color:#FF00FF;"|'' ''
|Implemented as a server-side plug-in
|-
|style="background-color:#0080FF;"|'' ''
|SVN (Implemented and will be in next release)
|-
|style="background-color:#00FFFF;"|'' ''
|In progress (Implementing)
|-
|style="background-color:#00FF00;"|'' ''
|Good Idea
|-
|style="background-color:#808080;"|'' ''
|Idea
|-
|style="background-color:#FFFF00;"|'' ''
|Vague, not understood, or in need of work
|-
|style="background-color:#FF8000"|'' ''
|Rejected, but can be implemented as a server plug-in
|-
|style="background-color:#FF0000;"|'' ''
|Rejected
|-
|style="background-color:#FFFFFF"|'' ''
|Unknown (new)
|}
</div>

== General/Gameplay ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Add support for 5 (or more) button mice
|style="background-color:#00FF00;"|Great Idea
|
|(Unknown)
|(Old)
|-
|Better physics
|style="background-color:#00FFFF;"|In progress
|
*Planning, some changes in CVS.
|Unknown
|(Old)
|-
|SELF-DESTRUCT BLAST RADIUS: Self Destruct (delete key) should have a blast radius similar to Shock Wave, perhaps larger. If you get shot during the self-destruct count down, that should also trigger the same blast. If I gotta go, I want to take someone with me.
|(Unknown)
|
|BearRiver
|(Old)
|-
|3-second (or however long) 'invulnerability' for incoming tanks - but they can't shoot
|style="background-color:#808080;"|Idea
|
*I could see this backfiring... your spawn attracts opponents to come, wait, and blast you when you lose invincibility. -L4m3r
|MORPH
|(Old)
|-
|Ability to turn off ricochet for laser flag but allow ricochet for bullets... or let them bounce only n times.. OR implement mirror buildings/walls. Should go for some interesting self-kills when combined with the no-radar/bullet bounce
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Smart LockOn for GM - won't lock on to your teammates (configurable in server)
|style="background-color:#808080;"|Idea
|
*I don't like this idea, there should be at least *some* risks to using this weapon. Personally, I think there should be more (not fewer) risks to holding this weapon; I'd like to see the thing overheat and explode (killing the holder) if it's fired too often in a short period of time. -M. Jetleb
|MORPH
|(Old)
|-
|Small jumps
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Server option for genocide flag - if you're killed while you have it, your team dies :^)
|style="background-color:#808080;"|Idea
|
*Feasible with a plug-in, too. -L4m3r
|MORPH
|(Old)
|-
|for broadband or LAN connections - voice chat for teams
|style="background-color:#808080;"|Idea
|
*I really think that you can do this with another service; I'm not sure if being part of BZFlag would be a good idea due to size and bandwidth issues.
|MORPH
|(Old)
|-
|Tank avatars (uploadable tank images) - have to think about shapes, though - someone could make a 1x1x1 pixel tank - that would suck - or a tank that looks like a building or pyramid. Clients don't have to accept downloading of avators (just view other tanks in default mode). Or just s-e-l-e-c-t from a certain number of predefined avatars that could come with the bzflag distribution. Or client provides a URL to download their avatar (saves server bandwidth).
|style="background-color:#808080;"|Idea
|
*Might not be implemented. Requires discussion; we may want to consider making the computer force a minimum size or something similar.
*How about uploadable flag graphics?
|MORPH
|(Old)
|-
|'Kamikaze' option for players - can take someone out by suicide
|style="background-color:#808080;"|Idea
|
*Server option if implemented.
*Implemented with a plugin by Theme97
|MORPH
|(Old)
|-
|Server option: everyone is radar-stealthed by default unless you get a 'radar' flag. You can still see all buildings, pyramids, teleports, and arena walls, though.
|style="background-color:#00FF00;"|Good idea
|
*Make them use their window. ;)
*Given the fairly narrow field of view out the window and the time it takes to turn a tank all the way around for a look-see, I think this could be frustrating. How about everyone starts out with minimum range radar instead and gets longer ranges with an appropriate flag? -M. Jetleb
|MORPH
|(Old)
|-
|Option for above: if you pick up GM or Laser, you're visible on radar to everyone whether they've got a radar flag or not
|style="background-color:#00FF00;"|Good idea
|
|MORPH
|(Old)
|-
|Selectable 'ricochet' fire - hold down shift key or something and your bullets won't ricochet
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Server option - tanks only have a certain number of times they can jump (gets reset when you get killed)
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Multiple-shields (server option for shield flags, or can be random - can get hit x number of times)
|style="background-color:#808080;"|Idea
|
*This is pretty much moot now. It's been shot down by the devs at least once, and a similar effect can be achieved by setting _shieldFlight to a very small number. This effectively provides as many hits as _maxFlagGrabs. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|Configurable 'radarless' and/or 'blind' zones in the arena - can't see what's in there on radar or via visuals
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Tank collisions - why can tanks drive through each other? Weird.
|style="background-color:#00FF00;"|Good Idea
|
*Lag could be a big problem here. If implemented, it must be impossible for two tanks to get stuck to each other. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|When tanks collide - great opportunity to implement tank damage concept, especially if one of them is moving especially fast, or has momentum flag, etc. Can push a tank off a building if your pushing them from their side.
|style="background-color:#808080;"|Idea
|
*Tank damage won't happen, but the kinetics could be neat, especially for mid-air collisions. It would certainly make "jump dancing" more interesting. [[User:L4m3r|L4m3r]]
|Morph
|(Old)
|-
|If a tank explodes right next to another tank, the other tank can be destroyed or get damaged
|style="background-color:#808080;"|Idea
|
*Somewhat implemented with the [[ShockwaveDeath]] plug-in. It would probably not be too hard to implement something similar (with a plugin) without shockwaves. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|Skins or views- In-tank mode, bumper mode, out-of-cab mode, chase mode.
|(Unknown)
|
|MORPH
|(Old)
|-
|Weapon extension packs.
|style="background-color:#FFFF00;"|(Unknown)
|
*Huh? Explain, please. [[User:L4m3r|L4m3r]]
|iPod
|(Old)
|-
|The ability to choose tanks, but they all die at one shot. maybe the jump height, speed, turn speed, acceleration, size can be preset.
|(Unknown)
|
|iPod
|(Old)
|-
|Option to choose different kinds of tanks. Different tanks could be weighted with different strengths and weaknesses. (almost like having a default flag). Would also need some form of health/damage status measurement, not just single hits. For example, there could be a larger, heavily armored tank that has powerful weapons, but moves slowly, versus a small, light, fast tank which is difficult to hit, but very low armor to protect from hits.
|(Unknown)
|
|Cue
|(Old)
|-
|What about a radar that only covers visible areas (don't passing through buildings/pyramids) ? This would leads to more placement tactics).
|(Unknown)
|
|K<nowiki>'</nowiki>limero
|(Old)
|-
|Always random respawn. Currently in CTF games first respawn is at own base. This can be abused by leaving and rejoining to get near base. This leave/rejoing trick is considered to be a mild form of cheating by many. Always random respawn would make it useless.
|(Unknown)
|
* I believe there is a plug-in for this. [[User:L4m3r|L4m3r]] 22:38, 30 April 2007 (EDT)
|abli
|(Old)
|-
|multiple (3?) jump stengths mini, normal, max...just the thing to confuse the opponents that expect one and you're off doing the other.
|(Unknown)
|
|kitchen
|(Old)
|-
|Anti camping. The ability to add "no camping zones" to areas of a map or to the entire map. Campers would be messaged that they're in a no camping zone, better start moving and have a prescribe number of seconds to move away or die. If a player returns to the same NCZ (no camping zone) and receives x warnings then he's disconnected. NCZs could be marked by a different color shade from a "normal" spot and could be exempt to a single team (like at their flag base). It's just a rough idea.
|(Unknown)
|
|pherris
|(Old)
|-
|Shield Flag Changes: Give Shield flag a radius, and draw it like a moving less opaque blue shockwave. Any tanks inside the shield radius would be protected, until the shield got hit a certain number of times.
|(Unknown)
|
|YHARG
|(Old)
|-
|At our company, we instituted a voluntary policy of dropping flags after 1 kill. Prevents slaughters and keeps things rolling more. It'd be great to be able to have the game do this for us, plus I'd love to see it turned on at external sites.
|(Unknown)
|
|TomMatelich
|(Old)
|-
|Server option: default powers -- flag(s) that everyone in the game automatically has (this wouldn't count as holding a flag). For example, the current Jumping option would == including Jumping as a default power.
|(Unknown)
|
|NebNamwen
|(Old)
|-
|Shot Aiming. Basically the center shot aim box could be moved left and right as far as the edge of the view window. (This would be enabled by default.) If the map is a vertical one a server option could be enabled so that vertical aiming could be enabled (using the same concept as horizontal aiming.) The aiming would be automatically centered by a button or key. These options could be mapped to a second joystick access, mouse scroll wheel or keyboard buttons.
|(Unknown)
| *Lateral shooting would basically be the same as a rotating turret, and this idea has been shot down many times. Vertical shooting has been poo-pooed also. [[User:L4m3r|L4m3r]] 01:45, 3 July 2007 (EDT)
|NN
|6/20/07
|}
</div>

== UI ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Make option to show previous players list
|style="background-color:#808080;"|Idea
|
|(Unknown)
|(Old)
|-
|Make ALL server options available from the menus
|style="background-color:#808080;"|Idea
|
*There are a LOT of server options, and this could add quite a bit of clutter. If you need more than a basic game, you should probably learn to start BZFS from the command line anyway. -L4m3r
|MORPH
|(Old)
|-
|Separate windows for player messages & server messages
|style="background-color:#00FF00;"|Good idea.
|
|MORPH
|(Old)
|-
|Message log
|style="background-color:#00FF00;"|Good idea.
|
|MORPH
|(Old)
|-
|Send message to everyone 'but' specified player (crosses team boundaries, or not)
|style="background-color:#808080;"|Idea
|
*Hmm. Everybody BUT a specified player? [M. Jetleb -> as in: "Let's all get the GM guy" without the GM guy knowing he's facing a co-ordinated attack - I like this idea)
|MORPH
|(Old)
|-
|The ability to see what the world is like before connecting to the server.
|(Unknown)
|
|iPod
|(Old)
|-
|Multi-monitor support (i.e., radar on one screen, window on another, chat/event log on a third)
|(Unknown)
|
|bhtooefr
|(Old)
|-
|Make a part in bzflag to put up a real server. 1st screen has the flags you want, next page is to find the MAP file that you created on your hard drive, next page pick if you want jumping etc.
|(Unknown)
|
|Colin
|(Old)
|-
|}
</div>

== Technical ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Better network handling
|style="background-color:#00FFFF;"|In progress
|
|(Unknown)
|(Old)
|-
|Better robot AI
|style="background-color:#808080;"|Idea
|
*Don't know if players would like it or not in multiplayer game. Pluggable or scriptable robot AI , maybe? - Code must be restructured first
*Server side bots are coming! [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT)
|(Unknown)
|(Old)
|-
|Better positioning of tanks
|style="background-color:#808080;"|Idea
|
*BZFlag already does this, but the algorithm is bad. Needs work.
|MORPH
|(Old)
|-
|Serious multithreaded design - shouldn't lock up interface while looking for servers, or doing anything else. This program is way-unstable on Windows
|style="background-color:#00FFFF;"|In Progress
|
*We're working on these problems; many complaints are due to people still using old servers/clients.
|MORPH
|(Old)
|-
|Some type of BZFlag GUID* to ban players who cheat - won't accept players who disable their GUID, etc.

<nowiki>*</nowiki>Global Unique Identifier, sort of like an IP addrss, but permanent. Usually a number. Problem occurs when you lose your GUID (have to reformat your HD, etc. How do you keep someone from hacking their GUID, or setting up a modified BZFlag server for identity theft, etc.
|(Unknown)
|
*I doubt this is even possible, let alone practical. What about people who play from more than one location? And, because this is an open-source game, it would probably be cracked in minutes. Any verification can be spoofed, or at least altered. there is no foolproof way to permanently ban someone. -L4m3r
|MORPH
|(Old)
|-
|To prevent cheating - the server determines what flags & abilities each tank has (possible?)
|style="background-color:#00FF00;"|In Progress
|
*Seriously being considered. This would also have the advantage of allowing different versions of clients and servers to work together. Yes, it's possible, but this type of change will mean a change in the network protocols.
*Being worked on for 2.2
|MORPH
|(Old)
|-
|BZFlag for mac in separate data and application files.
|(Unknown)
|
|iPod
|(Old)
|-
|J2ME client (allows one to play on a cell phone), would use radar
|(Unknown)
|
|bhtooefr
|(Old)
|-
|Special 'open source' BZFlag version (server and client) which is guaranteed to be compatible with all other BZFlag versions.
|(Unknown)
|
*BZFlag is already open-source, and making a universally-compatible client is not even remotely practical. Incompatibility is part of why the game breaks off new versions in the first place. [[User:L4m3r|L4m3r]]
|Orca
|(Old)
|-
|}
</div>

== Game Modes, Team Play, and Scoring ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Tounament mode
|style="background-color:#808080;"|Idea
|
*Great Idea?
|(Unknown)
|(Old)
|-
|When you shoot someone on your own team, instead of both of you blowing up, neither is destroyed, and their score goes up one, while your's goes down one. This would make teamkilling impossible and greatly discourage traitors as well.
|style="background-color:#808080;"|Idea
|
*But then couldn't cheaters spawn two clients and ramp up their scores by teamkilling their other login? --YHARG
|Trigger Happy Nerd
|(Old)
|-
|A new gameplay mode- Takes two to tank. One to control the (rotating) turret, the other drives. KIA switches positions. "Teamplay" but all in one tank.
|(Unknown)
|
*I see serious lag issues with this... How does Halo do it? ;) -L4m3r
*The main problem with this idea is coordination. If one person were to leave, the tank would be crippled. You COULD solve this by having the person switch to normal mode, but this could cause considerable jerking between modes on a busy server. [[User:F687s|F687s]] 22:13, 20 June 2007 (EDT)
|MORPH
|(Old)
|-
|Turret mode, If enabled by the server (Can be manditory with automatic grouping). One user drives and the other shoots, Turret mode tanks get double points (But onyl take one from the target). lost double points if killed. Have double ammo, And controllable speed (Max = _tankSpeed * 2 Min = _tankSpeed). Plus it takes 2 shots to kill a turret mode tank. Points gained and lost by turret tanks are divided evenly between the users, Unless the server is all turret mode, in h which case two users are displayed as one.
|(Unknown)
|
|Dogbert
|(Old)
|-
|Ability for a team to vote to 'banish' someone from their team
|style="background-color:#808080;"|Idea
|
*Possibly unfair to newer players. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|There should be a game of cops and robbers. The teams can change after about 10 mins or so.
|style="background-color:#FFFF00;"|(Unknown)
|
|iPod
|(Old)
|-
|A special FFA Game mode "Team by Flags". This means, same Flag = same Team, so if there is a Tank with Rapid fire, and you pick up Rapid fire, you are automatically handled as Team member (this means, killing the other Tank with Rapid fire will be handled the same way as when killing a team member). YHARG: Funky idea: what about a game mode where teams shared flag abilities? Like, each player on a team's flag applies to the whole team. This could make for some interesting combos...
|(Unknown)
|
|Agonizer
|(Old)
|-
|Make life trickier for the Rogue Team; with a mix of Rogues and Colored Teams, the Rogues have more targets. This should also change the effect of the Masquerade flag - perhaps your tank is invisible to Rogues (like Cloaking)?
|(Unknown)
|
|NickGrim
|(Old)
|-
|A server option to make deaths not affect your score unless they were self-inflicted/team (the method used by many online games). This would encourage more aggressive play, because it's worth going out and blasting. As it is, you've got a very good chance by just phantoming/OOing out of the way and keeping you score at zero to stay in the top three places! It would also help fix the rather unfair situation of spawning just below a building on which someone is GM-camping...there's pretty much no way to escape, so you lose a point.
|(Unknown)
|
|LionsPhil
|(Old)
|-
|Don't show individual score in CTF games. This might help teamplay as it reduces the incentive to run around as if it would be FFA.
|(Unknown)
|
|abli
|(Old)
|-
|Give points to the player how captures flag in CTF. (Say, around 4 or so) After all, it is often a bigger job than killing someone.
|(Unknown)
|*Maybe the score could be based the number of tanks in the other team, similar to shooting someone w/ geno. This can also discourage people from capturing thier own flag by scoreing the negative number of teamates. I'm not sure if the individual scores of the players of the captured team (other than the one who captures the flag) should be affected however. [[User:Sparky1|Sparky1]] 09:44, 21 May 2007 (EDT)
|abli
|(Old)
|-
|Ducati/Freestyle "Roles" mode: Make a game mode where players are presented with a list of flag choices (limitable to a few roles, if wanted) at respawn or connect time, and are forced to use this flag for the remainder of their connection/tank life. This would be really useful in the case of stealth vs. seer, where you could choose to be stealth or seer, but couldn't switch between them. Another idea would be high speed vs. quick turn. Or steamroller vs. machine gun... Team play would have the interesting effect of people banding together and people with each role on the team. Especially in stealth vs. seer, where a seer team member could warn the team about enemies! There would be no team flags/bases.
|(Unknown)
|
|YHARG
|(Old)
|-
|New game called tag were someone is it and they shoot someone else and there it and ect.
|(Unknown)
|
|Supermatthew
|(Old)
|-
|Also a new game called "Hide and seek" were everyone is clocked(think thats it, were you don't see them on radar) except one who is it. he needs to find someone and shoot them then hese cloked and who was shot is not. Also when someone is shot there sent back to Ground zero( 0X, 0Y, 0Z ) so they can't shoot who ever just shot them.
|(Unknown)
|
|Supermatthew
|(Old)
|-
|"Cat" game: when a player dies, he/she respawns automaticaly, after 3 secs or so. When they have respawned 9 times, they can no longer spawn, and are observers. The one who lasts the longest wins. Games are timed.
|(Unknown)
|
|(Unknown)
|4/20/2007
|-
|}
</div>

== Maps, Mapping, and BZW ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Materials that don't allow OO and PZ to go through
|style="background-color:#808080;"|Idea
|(Unknown)
*Would be nice for multilevel worlds made with the new ability to have objects above the ground.
*Sounds awesome! TD-Linux 17:41, 12 March 2007 (EDT)
*As a special case, there could be Zoned objects (objects that only respond to PZ and maybe OO; normal tanks behave like PZ through these objects). [[User:Sparky1|Sparky1]] 18:05, 21 May 2007 (EDT)
|
|(Old)
|-
|Get rid of the PZ flag and replace it w/ special telporters that do the same thing (they could be called "zoners", and should probably look different from regular teleporters). This way superflags, badflags, and team flags can all be zoned (without needing an exception to the restricition against using more than one flag at a time). The above idea of other zoned objects would play a major role here. Zoned flags can only be picked up by zoned tanks. Flags can spawn zoned, or become zoned by being carried by an unzoned tank that becomes zoned by going through a zoner. Likewise, a zonedflag becomes unzoned when a zoned tank carries it through a zoner. Unzoned tanks respond to shots from zoned flags the same way zoned tanks respond to shots from unzoned flags. For example: when zoned, L, WG, geno, and GM do not kill unzoned tanks (zoned GM will still lock onto any tank, and zoned geno would still kill every tank on the same team as the zoned tank that was shot). Although, flags like SW and SB would still kill any tank regardless of thier zoning status. As an extension to this idea one team in a CTF game could start out zoned, i.e. thier base is zoned and they initially spawn zoned. In order for the unzoned team to capture the zoned team's flag, the flag must become unzoned, and vice versa for the zoned team. This way new possibilities exist, like two bases could be superimposed as long as one base is zoned and the other is not. Another possible extension is different kinds of zones (w/ corespondingly different kinds of zoners) for CTF involving more than two teams. The relationship between differently zoned tanks would be the same as the relationship between zoned and unzoned tanks.
|(Unknow
|
|[[User:Sparky1|Sparky1]]
|5/21/2007
|-
|Differently-shaped teleporters (circles, triangles, etc.)
|style="background-color:#808080;"|Idea
|
*probably low priority
|MORPH
|(Old)
|-
|360 degree teleports - hit a spot on the ground or in the air from any direction and you teleport
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Configurable random teleporters - teleports to a different location every time
|style="background-color:#808080;"|Idea
|
*Idea is a bit vague... randomized teles are implemented if you use multiple links. Is this what is meant by this suggestion? -L4m3r
|MORPH
|(Old)
|-
|Triggers in levels
|style="background-color:#FFFF00;"|(Unknown)
|
*Triggers for what? unless you're talking about AI, this could most likely be handled with a server plug-in. [[User:L4m3r|L4m3r]]
|Dragonstar
|(Old)
|-
|wraparound world - radar remains centered on your current position. Internally, objects leaving the north border reappear to the south, but from the user's radar / visible perspective, you just see to the horizon. I believe this is how the original Battlezone worked. There are some implications: laser would need a range limit.
|(Unknown)
|
|nsayer
|(Old)
|-
|As a generalization to the wraparound world concept, how about the option of making a map based on geometry that’s non-Euclidean, for example spherical or hyperbolic. Jumping/flying, the shape of the tanks/objects, and bullet trajectories would also be affected by this global geometry. It would be like a world that has a high gravitational field, or a world situated near a wormhole.
|(Unknown)
|
|[[User:Sparky1|Sparky1]]
|5/21/2007
|-
|}
</div>

== Server Options, Administration, Plug-ins, and the Plug-in API ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Ability to configure server to turn somethings off or on depending on number of players - for instance, turn off ricochet after a certain number of players are connected, turn off GM & laser if a certain number of players aren't playing (GM & Laser with 2 players is kinda ridiculous)
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Allow custom-made weapons with a Object-Oriented scripting language (sorta like Liero AI uses: http://helios.et.put.poznan.pl/~sskowron/liero/index.html )
|(Unknown)
|
|Dragonstar
|(Old)
|-
|Preset world weapons that can be fired manually by admins from within BzFlag.
|(Unknown)
|
|Dogbert
|(Old)
|-
|}
</div>

== Graphics & Sound ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Sounds of tanks moving.
|(Unknown)
|
|iPod
|(Old)
|-
|Have different tank death scenes for the dying tank point of view. I realize there is some time needed for one to die and respawn, but the jumping effect one sees when killed irritates me to no end! I'd be happier if all faded to black or white or orange and had text across the screen saying ""respawning... please wait"" :) Also, when killed and your tank was moving toward a building, it just falls right thru it until it hits the ground.. wrong physics there! Splatter or tumble or shatter or something :)
|(Unknown)
|
|Robi
|(Old)
|-
|Custom color schemes for rogue players. The turret and body components can be chosen to be one of a predefined set of colors (e.g. red, yellow, black, white, blue, green, purple...). The game prohibits choosing a color scheme that matches a team scheme (e.g. red turret with red body) and the limited set stops someone choosing a shade which is nearly a team color (e.g. 0xFE0000 instead of 0xFF0000) (and also save texture memory, I think).
|(Unknown)
|
|LionsPhil
|(Old)
|-
|Allow a small decal on the back of the top of the tank. (think Half-Life's customizable spraypaint). Possibly also apply it to any held flag?
|(Unknown)
|
|LionsPhil
|(Old)
|-
|wireframe mode! man, this would make the game ten times cooler for nostalgia
|(Unknown)
|Already implemented, debug must be on --[[User:BinarySpike|BinarySpike]] 18:10, 10 May 2007 (EDT)
|rjbs
|(Old)
|-
|I'd like to see something more interesting done with the sky... maybe there could be a little ufo (easter egg) that would fly around occasionally? Tux on a ufo! ;)
|(Unknown)
|
|YHARG
|(Old)
|-
|Flag decals: Each flag would have a little icon/decal showing it's type ONLY when held by a player. It's kind of nice to be able to surprise people with an undercover shockwave, but doesn't make sense to have to right click (identify) or check the user list to see what flag someone has.
|(Unknown)
|
|YHARG
|(Old)
|-
|Background music! : (This can be done with an external media player so it shouldn't be the heighest priority, It would be nice to be able to control your music from within BzFlag)
|(Unknown)
|More usefully, you could just map key combinations to commands, rather than wasting time supporting all the various music players on every OS BZFlag supports. I don't know whether that would work so well on Windows, though. --[[User:77.97.207.100|77.97.207.100]] 10:14, 30 May 2007 (EDT)
|YHARG
|(Old)
|-
|}
</div>

== List Server and Other Global Services ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Multiple list servers, in case bzflag.org goes down (as it happened around feb. 15. 2004)
|(Unknown)
|Of course someone would need to pay for it. --[[User:BinarySpike|BinarySpike]] 18:10, 10 May 2007 (EDT)
|abli
|(Old)
|-
|}
</div>

[[Category:Development]]

Ideas

2007-07-03T05:40:11Z

L4m3r: /* General/Gameplay */ Moved NN's idea to the proper spot and dated it

{{Old}}
NOTE: These are just possibilities. We won't be implementing everything here.<br>

Commentary may include personal comments by developers.

= Editing this page =

Feel free to make changes and updates to this page whenever possible. If you have any questions, feel free to [[Getting Help|ask for help]]. If you wish to make major changes to this page (i.e. remove large amounts of old ideas), please warn us ahead of time.

== Adding ideas ==
* Please remember to make sure your idea isn't already here or on the [[Rejected Ideas]] page.
* Flag ideas should be placed on [[Flag Ideas]], not here.
* Add a row to the appropriate category (at the bottom, please) and fill it in with your idea.
* Sign your idea in the third column with three tildes: <nowiki>~~~</nowiki>
* Put the submission date in the fourth column
* Describe in full and make sense!
* Leave the status column white and fill it with (Unknown).

== Adding commentary ==
* Precede your comment with an asterisk: <nowiki>*</nowiki>
* Sign your comment with four tildes: <nowiki>~~~~</nowiki>
* Be nice, polite, and constructive.
* Contribute something when you comment. Saying whether or not you like an idea is pointless if you don't explain yourself.

== Cleaning up ==
To help keep this page current, old ideas should be removed when they're implemented (after each stable release, hence the "SVN" status). If you spot any ideas that were implemented prior to the latest stable release of BZFlag, please remove it.

= The list =
<div align="center">
{| cellpadding="10" cellspacing="1" border="1"
|+align="bottom"|''Legend''
|-
|style="background-color:#FF00FF;"|'' ''
|Implemented as a server-side plug-in
|-
|style="background-color:#0080FF;"|'' ''
|SVN (Implemented and will be in next release)
|-
|style="background-color:#00FFFF;"|'' ''
|In progress (Implementing)
|-
|style="background-color:#00FF00;"|'' ''
|Good Idea
|-
|style="background-color:#808080;"|'' ''
|Idea
|-
|style="background-color:#FFFF00;"|'' ''
|Vague, not understood, or in need of work
|-
|style="background-color:#FF8000"|'' ''
|Rejected, but can be implemented as a server plug-in
|-
|style="background-color:#FF0000;"|'' ''
|Rejected
|-
|style="background-color:#FFFFFF"|'' ''
|Unknown (new)
|}
</div>

== General/Gameplay ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Add support for 5 (or more) button mice
|style="background-color:#00FF00;"|Great Idea
|
|(Unknown)
|(Old)
|-
|Better physics
|style="background-color:#00FFFF;"|In progress
|
*Planning, some changes in CVS.
|Unknown
|(Old)
|-
|SELF-DESTRUCT BLAST RADIUS: Self Destruct (delete key) should have a blast radius similar to Shock Wave, perhaps larger. If you get shot during the self-destruct count down, that should also trigger the same blast. If I gotta go, I want to take someone with me.
|(Unknown)
|
|BearRiver
|(Old)
|-
|3-second (or however long) 'invulnerability' for incoming tanks - but they can't shoot
|style="background-color:#808080;"|Idea
|
*I could see this backfiring... your spawn attracts opponents to come, wait, and blast you when you lose invincibility. -L4m3r
|MORPH
|(Old)
|-
|Ability to turn off ricochet for laser flag but allow ricochet for bullets... or let them bounce only n times.. OR implement mirror buildings/walls. Should go for some interesting self-kills when combined with the no-radar/bullet bounce
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Smart LockOn for GM - won't lock on to your teammates (configurable in server)
|style="background-color:#808080;"|Idea
|
*I don't like this idea, there should be at least *some* risks to using this weapon. Personally, I think there should be more (not fewer) risks to holding this weapon; I'd like to see the thing overheat and explode (killing the holder) if it's fired too often in a short period of time. -M. Jetleb
|MORPH
|(Old)
|-
|Small jumps
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Server option for genocide flag - if you're killed while you have it, your team dies :^)
|style="background-color:#808080;"|Idea
|
*Feasible with a plug-in, too. -L4m3r
|MORPH
|(Old)
|-
|for broadband or LAN connections - voice chat for teams
|style="background-color:#808080;"|Idea
|
*I really think that you can do this with another service; I'm not sure if being part of BZFlag would be a good idea due to size and bandwidth issues.
|MORPH
|(Old)
|-
|Tank avatars (uploadable tank images) - have to think about shapes, though - someone could make a 1x1x1 pixel tank - that would suck - or a tank that looks like a building or pyramid. Clients don't have to accept downloading of avators (just view other tanks in default mode). Or just s-e-l-e-c-t from a certain number of predefined avatars that could come with the bzflag distribution. Or client provides a URL to download their avatar (saves server bandwidth).
|style="background-color:#808080;"|Idea
|
*Might not be implemented. Requires discussion; we may want to consider making the computer force a minimum size or something similar.
*How about uploadable flag graphics?
|MORPH
|(Old)
|-
|'Kamikaze' option for players - can take someone out by suicide
|style="background-color:#808080;"|Idea
|
*Server option if implemented.
*Implemented with a plugin by Theme97
|MORPH
|(Old)
|-
|Server option: everyone is radar-stealthed by default unless you get a 'radar' flag. You can still see all buildings, pyramids, teleports, and arena walls, though.
|style="background-color:#00FF00;"|Good idea
|
*Make them use their window. ;)
*Given the fairly narrow field of view out the window and the time it takes to turn a tank all the way around for a look-see, I think this could be frustrating. How about everyone starts out with minimum range radar instead and gets longer ranges with an appropriate flag? -M. Jetleb
|MORPH
|(Old)
|-
|Option for above: if you pick up GM or Laser, you're visible on radar to everyone whether they've got a radar flag or not
|style="background-color:#00FF00;"|Good idea
|
|MORPH
|(Old)
|-
|Selectable 'ricochet' fire - hold down shift key or something and your bullets won't ricochet
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Server option - tanks only have a certain number of times they can jump (gets reset when you get killed)
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Multiple-shields (server option for shield flags, or can be random - can get hit x number of times)
|style="background-color:#808080;"|Idea
|
*This is pretty much moot now. It's been shot down by the devs at least once, and a similar effect can be achieved by setting _shieldFlight to a very small number. This effectively provides as many hits as _maxFlagGrabs. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|Configurable 'radarless' and/or 'blind' zones in the arena - can't see what's in there on radar or via visuals
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Tank collisions - why can tanks drive through each other? Weird.
|style="background-color:#00FF00;"|Good Idea
|
*Lag could be a big problem here. If implemented, it must be impossible for two tanks to get stuck to each other. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|When tanks collide - great opportunity to implement tank damage concept, especially if one of them is moving especially fast, or has momentum flag, etc. Can push a tank off a building if your pushing them from their side.
|style="background-color:#808080;"|Idea
|
*Tank damage won't happen, but the kinetics could be neat, especially for mid-air collisions. It would certainly make "jump dancing" more interesting. [[User:L4m3r|L4m3r]]
|Morph
|(Old)
|-
|If a tank explodes right next to another tank, the other tank can be destroyed or get damaged
|style="background-color:#808080;"|Idea
|
*Somewhat implemented with the [[ShockwaveDeath]] plug-in. It would probably not be too hard to implement something similar (with a plugin) without shockwaves. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|Skins or views- In-tank mode, bumper mode, out-of-cab mode, chase mode.
|(Unknown)
|
|MORPH
|(Old)
|-
|Weapon extension packs.
|style="background-color:#FFFF00;"|(Unknown)
|
*Huh? Explain, please. [[User:L4m3r|L4m3r]]
|iPod
|(Old)
|-
|The ability to choose tanks, but they all die at one shot. maybe the jump height, speed, turn speed, acceleration, size can be preset.
|(Unknown)
|
|iPod
|(Old)
|-
|Option to choose different kinds of tanks. Different tanks could be weighted with different strengths and weaknesses. (almost like having a default flag). Would also need some form of health/damage status measurement, not just single hits. For example, there could be a larger, heavily armored tank that has powerful weapons, but moves slowly, versus a small, light, fast tank which is difficult to hit, but very low armor to protect from hits.
|(Unknown)
|
|Cue
|(Old)
|-
|What about a radar that only covers visible areas (don't passing through buildings/pyramids) ? This would leads to more placement tactics).
|(Unknown)
|
|K<nowiki>'</nowiki>limero
|(Old)
|-
|Always random respawn. Currently in CTF games first respawn is at own base. This can be abused by leaving and rejoining to get near base. This leave/rejoing trick is considered to be a mild form of cheating by many. Always random respawn would make it useless.
|(Unknown)
|
* I believe there is a plug-in for this. [[User:L4m3r|L4m3r]] 22:38, 30 April 2007 (EDT)
|abli
|(Old)
|-
|multiple (3?) jump stengths mini, normal, max...just the thing to confuse the opponents that expect one and you're off doing the other.
|(Unknown)
|
|kitchen
|(Old)
|-
|Anti camping. The ability to add "no camping zones" to areas of a map or to the entire map. Campers would be messaged that they're in a no camping zone, better start moving and have a prescribe number of seconds to move away or die. If a player returns to the same NCZ (no camping zone) and receives x warnings then he's disconnected. NCZs could be marked by a different color shade from a "normal" spot and could be exempt to a single team (like at their flag base). It's just a rough idea.
|(Unknown)
|
|pherris
|(Old)
|-
|Shield Flag Changes: Give Shield flag a radius, and draw it like a moving less opaque blue shockwave. Any tanks inside the shield radius would be protected, until the shield got hit a certain number of times.
|(Unknown)
|
|YHARG
|(Old)
|-
|At our company, we instituted a voluntary policy of dropping flags after 1 kill. Prevents slaughters and keeps things rolling more. It'd be great to be able to have the game do this for us, plus I'd love to see it turned on at external sites.
|(Unknown)
|
|TomMatelich
|(Old)
|-
|Server option: default powers -- flag(s) that everyone in the game automatically has (this wouldn't count as holding a flag). For example, the current Jumping option would == including Jumping as a default power.
|(Unknown)
|
|NebNamwen
|(Old)
|-
|Shot Aiming. Basically the center shot aim box could be moved left and right as far as the edge of the view window. (This would be enabled by default.) If the map is a vertical one a server option could be enabled so that vertical aiming could be enabled (using the same concept as horizontal aiming.) The aiming would be automatically centered by a button or key. These options could be mapped to a second joystick access, mouse scroll wheel or keyboard buttons. This would improve game play a ton! Please implement this!
|
|
|NN
|6/20/07
|}
</div>

== UI ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Make option to show previous players list
|style="background-color:#808080;"|Idea
|
|(Unknown)
|(Old)
|-
|Make ALL server options available from the menus
|style="background-color:#808080;"|Idea
|
*There are a LOT of server options, and this could add quite a bit of clutter. If you need more than a basic game, you should probably learn to start BZFS from the command line anyway. -L4m3r
|MORPH
|(Old)
|-
|Separate windows for player messages & server messages
|style="background-color:#00FF00;"|Good idea.
|
|MORPH
|(Old)
|-
|Message log
|style="background-color:#00FF00;"|Good idea.
|
|MORPH
|(Old)
|-
|Send message to everyone 'but' specified player (crosses team boundaries, or not)
|style="background-color:#808080;"|Idea
|
*Hmm. Everybody BUT a specified player? [M. Jetleb -> as in: "Let's all get the GM guy" without the GM guy knowing he's facing a co-ordinated attack - I like this idea)
|MORPH
|(Old)
|-
|The ability to see what the world is like before connecting to the server.
|(Unknown)
|
|iPod
|(Old)
|-
|Multi-monitor support (i.e., radar on one screen, window on another, chat/event log on a third)
|(Unknown)
|
|bhtooefr
|(Old)
|-
|Make a part in bzflag to put up a real server. 1st screen has the flags you want, next page is to find the MAP file that you created on your hard drive, next page pick if you want jumping etc.
|(Unknown)
|
|Colin
|(Old)
|-
|}
</div>

== Technical ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Better network handling
|style="background-color:#00FFFF;"|In progress
|
|(Unknown)
|(Old)
|-
|Better robot AI
|style="background-color:#808080;"|Idea
|
*Don't know if players would like it or not in multiplayer game. Pluggable or scriptable robot AI , maybe? - Code must be restructured first
*Server side bots are coming! [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT)
|(Unknown)
|(Old)
|-
|Better positioning of tanks
|style="background-color:#808080;"|Idea
|
*BZFlag already does this, but the algorithm is bad. Needs work.
|MORPH
|(Old)
|-
|Serious multithreaded design - shouldn't lock up interface while looking for servers, or doing anything else. This program is way-unstable on Windows
|style="background-color:#00FFFF;"|In Progress
|
*We're working on these problems; many complaints are due to people still using old servers/clients.
|MORPH
|(Old)
|-
|Some type of BZFlag GUID* to ban players who cheat - won't accept players who disable their GUID, etc.

<nowiki>*</nowiki>Global Unique Identifier, sort of like an IP addrss, but permanent. Usually a number. Problem occurs when you lose your GUID (have to reformat your HD, etc. How do you keep someone from hacking their GUID, or setting up a modified BZFlag server for identity theft, etc.
|(Unknown)
|
*I doubt this is even possible, let alone practical. What about people who play from more than one location? And, because this is an open-source game, it would probably be cracked in minutes. Any verification can be spoofed, or at least altered. there is no foolproof way to permanently ban someone. -L4m3r
|MORPH
|(Old)
|-
|To prevent cheating - the server determines what flags & abilities each tank has (possible?)
|style="background-color:#00FF00;"|In Progress
|
*Seriously being considered. This would also have the advantage of allowing different versions of clients and servers to work together. Yes, it's possible, but this type of change will mean a change in the network protocols.
*Being worked on for 2.2
|MORPH
|(Old)
|-
|BZFlag for mac in separate data and application files.
|(Unknown)
|
|iPod
|(Old)
|-
|J2ME client (allows one to play on a cell phone), would use radar
|(Unknown)
|
|bhtooefr
|(Old)
|-
|Special 'open source' BZFlag version (server and client) which is guaranteed to be compatible with all other BZFlag versions.
|(Unknown)
|
*BZFlag is already open-source, and making a universally-compatible client is not even remotely practical. Incompatibility is part of why the game breaks off new versions in the first place. [[User:L4m3r|L4m3r]]
|Orca
|(Old)
|-
|}
</div>

== Game Modes, Team Play, and Scoring ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Tounament mode
|style="background-color:#808080;"|Idea
|
*Great Idea?
|(Unknown)
|(Old)
|-
|When you shoot someone on your own team, instead of both of you blowing up, neither is destroyed, and their score goes up one, while your's goes down one. This would make teamkilling impossible and greatly discourage traitors as well.
|style="background-color:#808080;"|Idea
|
*But then couldn't cheaters spawn two clients and ramp up their scores by teamkilling their other login? --YHARG
|Trigger Happy Nerd
|(Old)
|-
|A new gameplay mode- Takes two to tank. One to control the (rotating) turret, the other drives. KIA switches positions. "Teamplay" but all in one tank.
|(Unknown)
|
*I see serious lag issues with this... How does Halo do it? ;) -L4m3r
*The main problem with this idea is coordination. If one person were to leave, the tank would be crippled. You COULD solve this by having the person switch to normal mode, but this could cause considerable jerking between modes on a busy server. [[User:F687s|F687s]] 22:13, 20 June 2007 (EDT)
|MORPH
|(Old)
|-
|Turret mode, If enabled by the server (Can be manditory with automatic grouping). One user drives and the other shoots, Turret mode tanks get double points (But onyl take one from the target). lost double points if killed. Have double ammo, And controllable speed (Max = _tankSpeed * 2 Min = _tankSpeed). Plus it takes 2 shots to kill a turret mode tank. Points gained and lost by turret tanks are divided evenly between the users, Unless the server is all turret mode, in h which case two users are displayed as one.
|(Unknown)
|
|Dogbert
|(Old)
|-
|Ability for a team to vote to 'banish' someone from their team
|style="background-color:#808080;"|Idea
|
*Possibly unfair to newer players. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|There should be a game of cops and robbers. The teams can change after about 10 mins or so.
|style="background-color:#FFFF00;"|(Unknown)
|
|iPod
|(Old)
|-
|A special FFA Game mode "Team by Flags". This means, same Flag = same Team, so if there is a Tank with Rapid fire, and you pick up Rapid fire, you are automatically handled as Team member (this means, killing the other Tank with Rapid fire will be handled the same way as when killing a team member). YHARG: Funky idea: what about a game mode where teams shared flag abilities? Like, each player on a team's flag applies to the whole team. This could make for some interesting combos...
|(Unknown)
|
|Agonizer
|(Old)
|-
|Make life trickier for the Rogue Team; with a mix of Rogues and Colored Teams, the Rogues have more targets. This should also change the effect of the Masquerade flag - perhaps your tank is invisible to Rogues (like Cloaking)?
|(Unknown)
|
|NickGrim
|(Old)
|-
|A server option to make deaths not affect your score unless they were self-inflicted/team (the method used by many online games). This would encourage more aggressive play, because it's worth going out and blasting. As it is, you've got a very good chance by just phantoming/OOing out of the way and keeping you score at zero to stay in the top three places! It would also help fix the rather unfair situation of spawning just below a building on which someone is GM-camping...there's pretty much no way to escape, so you lose a point.
|(Unknown)
|
|LionsPhil
|(Old)
|-
|Don't show individual score in CTF games. This might help teamplay as it reduces the incentive to run around as if it would be FFA.
|(Unknown)
|
|abli
|(Old)
|-
|Give points to the player how captures flag in CTF. (Say, around 4 or so) After all, it is often a bigger job than killing someone.
|(Unknown)
|*Maybe the score could be based the number of tanks in the other team, similar to shooting someone w/ geno. This can also discourage people from capturing thier own flag by scoreing the negative number of teamates. I'm not sure if the individual scores of the players of the captured team (other than the one who captures the flag) should be affected however. [[User:Sparky1|Sparky1]] 09:44, 21 May 2007 (EDT)
|abli
|(Old)
|-
|Ducati/Freestyle "Roles" mode: Make a game mode where players are presented with a list of flag choices (limitable to a few roles, if wanted) at respawn or connect time, and are forced to use this flag for the remainder of their connection/tank life. This would be really useful in the case of stealth vs. seer, where you could choose to be stealth or seer, but couldn't switch between them. Another idea would be high speed vs. quick turn. Or steamroller vs. machine gun... Team play would have the interesting effect of people banding together and people with each role on the team. Especially in stealth vs. seer, where a seer team member could warn the team about enemies! There would be no team flags/bases.
|(Unknown)
|
|YHARG
|(Old)
|-
|New game called tag were someone is it and they shoot someone else and there it and ect.
|(Unknown)
|
|Supermatthew
|(Old)
|-
|Also a new game called "Hide and seek" were everyone is clocked(think thats it, were you don't see them on radar) except one who is it. he needs to find someone and shoot them then hese cloked and who was shot is not. Also when someone is shot there sent back to Ground zero( 0X, 0Y, 0Z ) so they can't shoot who ever just shot them.
|(Unknown)
|
|Supermatthew
|(Old)
|-
|"Cat" game: when a player dies, he/she respawns automaticaly, after 3 secs or so. When they have respawned 9 times, they can no longer spawn, and are observers. The one who lasts the longest wins. Games are timed.
|(Unknown)
|
|(Unknown)
|4/20/2007
|-
|}
</div>

== Maps, Mapping, and BZW ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Materials that don't allow OO and PZ to go through
|style="background-color:#808080;"|Idea
|(Unknown)
*Would be nice for multilevel worlds made with the new ability to have objects above the ground.
*Sounds awesome! TD-Linux 17:41, 12 March 2007 (EDT)
*As a special case, there could be Zoned objects (objects that only respond to PZ and maybe OO; normal tanks behave like PZ through these objects). [[User:Sparky1|Sparky1]] 18:05, 21 May 2007 (EDT)
|
|(Old)
|-
|Get rid of the PZ flag and replace it w/ special telporters that do the same thing (they could be called "zoners", and should probably look different from regular teleporters). This way superflags, badflags, and team flags can all be zoned (without needing an exception to the restricition against using more than one flag at a time). The above idea of other zoned objects would play a major role here. Zoned flags can only be picked up by zoned tanks. Flags can spawn zoned, or become zoned by being carried by an unzoned tank that becomes zoned by going through a zoner. Likewise, a zonedflag becomes unzoned when a zoned tank carries it through a zoner. Unzoned tanks respond to shots from zoned flags the same way zoned tanks respond to shots from unzoned flags. For example: when zoned, L, WG, geno, and GM do not kill unzoned tanks (zoned GM will still lock onto any tank, and zoned geno would still kill every tank on the same team as the zoned tank that was shot). Although, flags like SW and SB would still kill any tank regardless of thier zoning status. As an extension to this idea one team in a CTF game could start out zoned, i.e. thier base is zoned and they initially spawn zoned. In order for the unzoned team to capture the zoned team's flag, the flag must become unzoned, and vice versa for the zoned team. This way new possibilities exist, like two bases could be superimposed as long as one base is zoned and the other is not. Another possible extension is different kinds of zones (w/ corespondingly different kinds of zoners) for CTF involving more than two teams. The relationship between differently zoned tanks would be the same as the relationship between zoned and unzoned tanks.
|(Unknow
|
|[[User:Sparky1|Sparky1]]
|5/21/2007
|-
|Differently-shaped teleporters (circles, triangles, etc.)
|style="background-color:#808080;"|Idea
|
*probably low priority
|MORPH
|(Old)
|-
|360 degree teleports - hit a spot on the ground or in the air from any direction and you teleport
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Configurable random teleporters - teleports to a different location every time
|style="background-color:#808080;"|Idea
|
*Idea is a bit vague... randomized teles are implemented if you use multiple links. Is this what is meant by this suggestion? -L4m3r
|MORPH
|(Old)
|-
|Triggers in levels
|style="background-color:#FFFF00;"|(Unknown)
|
*Triggers for what? unless you're talking about AI, this could most likely be handled with a server plug-in. [[User:L4m3r|L4m3r]]
|Dragonstar
|(Old)
|-
|wraparound world - radar remains centered on your current position. Internally, objects leaving the north border reappear to the south, but from the user's radar / visible perspective, you just see to the horizon. I believe this is how the original Battlezone worked. There are some implications: laser would need a range limit.
|(Unknown)
|
|nsayer
|(Old)
|-
|As a generalization to the wraparound world concept, how about the option of making a map based on geometry that’s non-Euclidean, for example spherical or hyperbolic. Jumping/flying, the shape of the tanks/objects, and bullet trajectories would also be affected by this global geometry. It would be like a world that has a high gravitational field, or a world situated near a wormhole.
|(Unknown)
|
|[[User:Sparky1|Sparky1]]
|5/21/2007
|-
|}
</div>

== Server Options, Administration, Plug-ins, and the Plug-in API ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Ability to configure server to turn somethings off or on depending on number of players - for instance, turn off ricochet after a certain number of players are connected, turn off GM & laser if a certain number of players aren't playing (GM & Laser with 2 players is kinda ridiculous)
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Allow custom-made weapons with a Object-Oriented scripting language (sorta like Liero AI uses: http://helios.et.put.poznan.pl/~sskowron/liero/index.html )
|(Unknown)
|
|Dragonstar
|(Old)
|-
|Preset world weapons that can be fired manually by admins from within BzFlag.
|(Unknown)
|
|Dogbert
|(Old)
|-
|}
</div>

== Graphics & Sound ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Sounds of tanks moving.
|(Unknown)
|
|iPod
|(Old)
|-
|Have different tank death scenes for the dying tank point of view. I realize there is some time needed for one to die and respawn, but the jumping effect one sees when killed irritates me to no end! I'd be happier if all faded to black or white or orange and had text across the screen saying ""respawning... please wait"" :) Also, when killed and your tank was moving toward a building, it just falls right thru it until it hits the ground.. wrong physics there! Splatter or tumble or shatter or something :)
|(Unknown)
|
|Robi
|(Old)
|-
|Custom color schemes for rogue players. The turret and body components can be chosen to be one of a predefined set of colors (e.g. red, yellow, black, white, blue, green, purple...). The game prohibits choosing a color scheme that matches a team scheme (e.g. red turret with red body) and the limited set stops someone choosing a shade which is nearly a team color (e.g. 0xFE0000 instead of 0xFF0000) (and also save texture memory, I think).
|(Unknown)
|
|LionsPhil
|(Old)
|-
|Allow a small decal on the back of the top of the tank. (think Half-Life's customizable spraypaint). Possibly also apply it to any held flag?
|(Unknown)
|
|LionsPhil
|(Old)
|-
|wireframe mode! man, this would make the game ten times cooler for nostalgia
|(Unknown)
|Already implemented, debug must be on --[[User:BinarySpike|BinarySpike]] 18:10, 10 May 2007 (EDT)
|rjbs
|(Old)
|-
|I'd like to see something more interesting done with the sky... maybe there could be a little ufo (easter egg) that would fly around occasionally? Tux on a ufo! ;)
|(Unknown)
|
|YHARG
|(Old)
|-
|Flag decals: Each flag would have a little icon/decal showing it's type ONLY when held by a player. It's kind of nice to be able to surprise people with an undercover shockwave, but doesn't make sense to have to right click (identify) or check the user list to see what flag someone has.
|(Unknown)
|
|YHARG
|(Old)
|-
|Background music! : (This can be done with an external media player so it shouldn't be the heighest priority, It would be nice to be able to control your music from within BzFlag)
|(Unknown)
|More usefully, you could just map key combinations to commands, rather than wasting time supporting all the various music players on every OS BZFlag supports. I don't know whether that would work so well on Windows, though. --[[User:77.97.207.100|77.97.207.100]] 10:14, 30 May 2007 (EDT)
|YHARG
|(Old)
|-
|}
</div>

== List Server and Other Global Services ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Multiple list servers, in case bzflag.org goes down (as it happened around feb. 15. 2004)
|(Unknown)
|Of course someone would need to pay for it. --[[User:BinarySpike|BinarySpike]] 18:10, 10 May 2007 (EDT)
|abli
|(Old)
|-
|}
</div>

[[Category:Development]]

Ideas

2007-05-01T02:38:46Z

L4m3r: Status coloring, editing section, general cleanup. Finished!

{{Old}}
NOTE: These are just possibilities. We won't be implementing everything here.<br>

Commentary may include personal comments by developers.

= Editing this page =

Feel free to make changes and updates to this page whenever possible. If you have any questions, feel free to [[Getting Help|ask for help]]. If you wish to make major changes to this page (i.e. remove large amounts of old ideas), please warn us ahead of time.

== Adding ideas ==
* Please remember to make sure your idea isn't already here or on the [[Rejected Ideas]] page.
* Flag ideas should be placed on [[Flag Ideas]], not here.
* Add a row to the appropriate category (at the bottom, please) and fill it in with your idea.
* Sign your idea in the third column with three tildes: <nowiki>~~~</nowiki>
* Put the submission date in the fourth column
* Describe in full and make sense!
* Leave the status column white and fill it with (Unknown).

== Adding commentary ==
* Precede your comment with an asterisk: <nowiki>*</nowiki>
* Sign your comment with four tildes: <nowiki>~~~~</nowiki>
* Be nice, polite, and constructive.
* Contribute something when you comment. Saying whether or not you like an idea is pointless if you don't explain yourself.

== Cleaning up ==
To help keep this page current, old ideas should be removed when they're implemented (after each stable release, hence the "SVN" status). If you spot any ideas that were implemented prior to the latest stable release of BZFlag, please remove it.

= The list =
<div align="center">
{| cellpadding="10" cellspacing="1" border="1"
|+align="bottom"|''Legend''
|-
|style="background-color:#FF00FF;"|'' ''
|Implemented as a server-side plug-in
|-
|style="background-color:#0080FF;"|'' ''
|SVN (Implemented and will be in next release)
|-
|style="background-color:#00FFFF;"|'' ''
|In progress (Implementing)
|-
|style="background-color:#00FF00;"|'' ''
|Good Idea
|-
|style="background-color:#808080;"|'' ''
|Idea
|-
|style="background-color:#FFFF00;"|'' ''
|Vague, not understood, or in need of work
|-
|style="background-color:#FF8000"|'' ''
|Rejected, but can be implemented as a server plug-in
|-
|style="background-color:#FF0000;"|'' ''
|Rejected
|-
|style="background-color:#FFFFFF"|'' ''
|Unknown (new)
|}
</div>

== General/Gameplay ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Add support for 5 (or more) button mice
|style="background-color:#00FF00;"|Great Idea
|
|(Unknown)
|(Old)
|-
|Better physics
|style="background-color:#00FFFF;"|In progress
|
*Planning, some changes in CVS.
|Unknown
|(Old)
|-
|SELF-DESTRUCT BLAST RADIUS: Self Destruct (delete key) should have a blast radius similar to Shock Wave, perhaps larger. If you get shot during the self-destruct count down, that should also trigger the same blast. If I gotta go, I want to take someone with me.
|(Unknown)
|
|BearRiver
|(Old)
|-
|3-second (or however long) 'invulnerability' for incoming tanks - but they can't shoot
|style="background-color:#808080;"|Idea
|
*I could see this backfiring... your spawn attracts opponents to come, wait, and blast you when you lose invincibility. -L4m3r
|MORPH
|(Old)
|-
|Ability to turn off ricochet for laser flag but allow ricochet for bullets... or let them bounce only n times.. OR implement mirror buildings/walls. Should go for some interesting self-kills when combined with the no-radar/bullet bounce
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Smart LockOn for GM - won't lock on to your teammates (configurable in server)
|style="background-color:#808080;"|Idea
|
*I don't like this idea, there should be at least *some* risks to using this weapon. Personally, I think there should be more (not fewer) risks to holding this weapon; I'd like to see the thing overheat and explode (killing the holder) if it's fired too often in a short period of time. -M. Jetleb
|MORPH
|(Old)
|-
|Small jumps
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Server option for genocide flag - if you're killed while you have it, your team dies :^)
|style="background-color:#808080;"|Idea
|
*Feasible with a plug-in, too. -L4m3r
|MORPH
|(Old)
|-
|for broadband or LAN connections - voice chat for teams
|style="background-color:#808080;"|Idea
|
*I really think that you can do this with another service; I'm not sure if being part of BZFlag would be a good idea due to size and bandwidth issues.
|MORPH
|(Old)
|-
|Tank avatars (uploadable tank images) - have to think about shapes, though - someone could make a 1x1x1 pixel tank - that would suck - or a tank that looks like a building or pyramid. Clients don't have to accept downloading of avators (just view other tanks in default mode). Or just s-e-l-e-c-t from a certain number of predefined avatars that could come with the bzflag distribution. Or client provides a URL to download their avatar (saves server bandwidth).
|style="background-color:#808080;"|Idea
|
*Might not be implemented. Requires discussion; we may want to consider making the computer force a minimum size or something similar.
*How about uploadable flag graphics?
|MORPH
|(Old)
|-
|'Kamikaze' option for players - can take someone out by suicide
|style="background-color:#808080;"|Idea
|
*Server option if implemented.
*Implemented with a plugin by Theme97
|MORPH
|(Old)
|-
|Server option: everyone is radar-stealthed by default unless you get a 'radar' flag. You can still see all buildings, pyramids, teleports, and arena walls, though.
|style="background-color:#00FF00;"|Good idea
|
*Make them use their window. ;)
*Given the fairly narrow field of view out the window and the time it takes to turn a tank all the way around for a look-see, I think this could be frustrating. How about everyone starts out with minimum range radar instead and gets longer ranges with an appropriate flag? -M. Jetleb
|MORPH
|(Old)
|-
|Option for above: if you pick up GM or Laser, you're visible on radar to everyone whether they've got a radar flag or not
|style="background-color:#00FF00;"|Good idea
|
|MORPH
|(Old)
|-
|Selectable 'ricochet' fire - hold down shift key or something and your bullets won't ricochet
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Server option - tanks only have a certain number of times they can jump (gets reset when you get killed)
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Multiple-shields (server option for shield flags, or can be random - can get hit x number of times)
|style="background-color:#808080;"|Idea
|
*This is pretty much moot now. It's been shot down by the devs at least once, and a similar effect can be achieved by setting _shieldFlight to a very small number. This effectively provides as many hits as _maxFlagGrabs. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|Configurable 'radarless' and/or 'blind' zones in the arena - can't see what's in there on radar or via visuals
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Tank collisions - why can tanks drive through each other? Weird.
|style="background-color:#00FF00;"|Good Idea
|
*Lag could be a big problem here. If implemented, it must be impossible for two tanks to get stuck to each other. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|When tanks collide - great opportunity to implement tank damage concept, especially if one of them is moving especially fast, or has momentum flag, etc. Can push a tank off a building if your pushing them from their side.
|style="background-color:#808080;"|Idea
|
*Tank damage won't happen, but the kinetics could be neat, especially for mid-air collisions. It would certainly make "jump dancing" more interesting. [[User:L4m3r|L4m3r]]
|Morph
|(Old)
|-
|If a tank explodes right next to another tank, the other tank can be destroyed or get damaged
|style="background-color:#808080;"|Idea
|
*Somewhat implemented with the [[ShockwaveDeath]] plug-in. It would probably not be too hard to implement something similar (with a plugin) without shockwaves. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|Skins or views- In-tank mode, bumper mode, out-of-cab mode, chase mode.
|(Unknown)
|
|MORPH
|(Old)
|-
|Weapon extension packs.
|style="background-color:#FFFF00;"|(Unknown)
|
*Huh? Explain, please. [[User:L4m3r|L4m3r]]
|iPod
|(Old)
|-
|The ability to choose tanks, but they all die at one shot. maybe the jump height, speed, turn speed, acceleration, size can be preset.
|(Unknown)
|
|iPod
|(Old)
|-
|Option to choose different kinds of tanks. Different tanks could be weighted with different strengths and weaknesses. (almost like having a default flag). Would also need some form of health/damage status measurement, not just single hits. For example, there could be a larger, heavily armored tank that has powerful weapons, but moves slowly, versus a small, light, fast tank which is difficult to hit, but very low armor to protect from hits.
|(Unknown)
|
|Cue
|(Old)
|-
|What about a radar that only covers visible areas (don't passing through buildings/pyramids) ? This would leads to more placement tactics).
|(Unknown)
|
|K<nowiki>'</nowiki>limero
|(Old)
|-
|Always random respawn. Currently in CTF games first respawn is at own base. This can be abused by leaving and rejoining to get near base. This leave/rejoing trick is considered to be a mild form of cheating by many. Always random respawn would make it useless.
|(Unknown)
|
* I believe there is a plug-in for this. [[User:L4m3r|L4m3r]] 22:38, 30 April 2007 (EDT)
|abli
|(Old)
|-
|multiple (3?) jump stengths mini, normal, max...just the thing to confuse the opponents that expect one and you're off doing the other.
|(Unknown)
|
|kitchen
|(Old)
|-
|Anti camping. The ability to add "no camping zones" to areas of a map or to the entire map. Campers would be messaged that they're in a no camping zone, better start moving and have a prescribe number of seconds to move away or die. If a player returns to the same NCZ (no camping zone) and receives x warnings then he's disconnected. NCZs could be marked by a different color shade from a "normal" spot and could be exempt to a single team (like at their flag base). It's just a rough idea.
|(Unknown)
|
|pherris
|(Old)
|-
|Shield Flag Changes: Give Shield flag a radius, and draw it like a moving less opaque blue shockwave. Any tanks inside the shield radius would be protected, until the shield got hit a certain number of times.
|(Unknown)
|
|YHARG
|(Old)
|-
|At our company, we instituted a voluntary policy of dropping flags after 1 kill. Prevents slaughters and keeps things rolling more. It'd be great to be able to have the game do this for us, plus I'd love to see it turned on at external sites.
|(Unknown)
|
|TomMatelich
|(Old)
|-
|Server option: default powers -- flag(s) that everyone in the game automatically has (this wouldn't count as holding a flag). For example, the current Jumping option would == including Jumping as a default power.
|(Unknown)
|
|NebNamwen
|(Old)
|}
</div>

== UI ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Make option to show previous players list
|style="background-color:#808080;"|Idea
|
|(Unknown)
|(Old)
|-
|Make ALL server options available from the menus
|style="background-color:#808080;"|Idea
|
*There are a LOT of server options, and this could add quite a bit of clutter. If you need more than a basic game, you should probably learn to start BZFS from the command line anyway. -L4m3r
|MORPH
|(Old)
|-
|Separate windows for player messages & server messages
|style="background-color:#00FF00;"|Good idea.
|
|MORPH
|(Old)
|-
|Message log
|style="background-color:#00FF00;"|Good idea.
|
|MORPH
|(Old)
|-
|Send message to everyone 'but' specified player (crosses team boundaries, or not)
|style="background-color:#808080;"|Idea
|
*Hmm. Everybody BUT a specified player? [M. Jetleb -> as in: "Let's all get the GM guy" without the GM guy knowing he's facing a co-ordinated attack - I like this idea)
|MORPH
|(Old)
|-
|The ability to see what the world is like before connecting to the server.
|(Unknown)
|
|iPod
|(Old)
|-
|Multi-monitor support (i.e., radar on one screen, window on another, chat/event log on a third)
|(Unknown)
|
|bhtooefr
|(Old)
|-
|Make a part in bzflag to put up a real server. 1st screen has the flags you want, next page is to find the MAP file that you created on your hard drive, next page pick if you want jumping etc.
|(Unknown)
|
|Colin
|(Old)
|-
|}
</div>

== Technical ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Better network handling
|style="background-color:#00FFFF;"|In progress
|
|(Unknown)
|(Old)
|-
|Better robot AI
|style="background-color:#808080;"|Idea
|
*Don't know if players would like it or not in multiplayer game. Pluggable or scriptable robot AI , maybe? - Code must be restructured first
*Server side bots are coming! [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT)
|(Unknown)
|(Old)
|-
|Better positioning of tanks
|style="background-color:#808080;"|Idea
|
*BZFlag already does this, but the algorithm is bad. Needs work.
|MORPH
|(Old)
|-
|Serious multithreaded design - shouldn't lock up interface while looking for servers, or doing anything else. This program is way-unstable on Windows
|style="background-color:#00FFFF;"|In Progress
|
*We're working on these problems; many complaints are due to people still using old servers/clients.
|MORPH
|(Old)
|-
|Some type of BZFlag GUID* to ban players who cheat - won't accept players who disable their GUID, etc.

<nowiki>*</nowiki>Global Unique Identifier, sort of like an IP addrss, but permanent. Usually a number. Problem occurs when you lose your GUID (have to reformat your HD, etc. How do you keep someone from hacking their GUID, or setting up a modified BZFlag server for identity theft, etc.
|(Unknown)
|
*I doubt this is even possible, let alone practical. What about people who play from more than one location? And, because this is an open-source game, it would probably be cracked in minutes. Any verification can be spoofed, or at least altered. there is no foolproof way to permanently ban someone. -L4m3r
|MORPH
|(Old)
|-
|To prevent cheating - the server determines what flags & abilities each tank has (possible?)
|style="background-color:#00FF00;"|In Progress
|
*Seriously being considered. This would also have the advantage of allowing different versions of clients and servers to work together. Yes, it's possible, but this type of change will mean a change in the network protocols.
*Being worked on for 2.2
|MORPH
|(Old)
|-
|BZFlag for mac in separate data and application files.
|(Unknown)
|
|iPod
|(Old)
|-
|J2ME client (allows one to play on a cell phone), would use radar
|(Unknown)
|
|bhtooefr
|(Old)
|-
|Special 'open source' BZFlag version (server and client) which is guaranteed to be compatible with all other BZFlag versions.
|(Unknown)
|
*BZFlag is already open-source, and making a universally-compatible client is not even remotely practical. Incompatibility is part of why the game breaks off new versions in the first place. [[User:L4m3r|L4m3r]]
|Orca
|(Old)
|-
|}
</div>

== Game Modes, Team Play, and Scoring ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Tounament mode
|style="background-color:#808080;"|Idea
|
*Great Idea?
|(Unknown)
|(Old)
|-
|When you shoot someone on your own team, instead of both of you blowing up, neither is destroyed, and their score goes up one, while your's goes down one. This would make teamkilling impossible and greatly discourage traitors as well.
|style="background-color:#808080;"|Idea
|
*But then couldn't cheaters spawn two clients and ramp up their scores by teamkilling their other login? --YHARG
|Trigger Happy Nerd
|(Old)
|-
|A new gameplay mode- Takes two to tank. One to control the (rotating) turret, the other drives. KIA switches positions. "Teamplay" but all in one tank.
|(Unknown)
|
*I see serious lag issues with this... How does Halo do it? ;) -L4m3r
|MORPH
|(Old)
|-
|Turret mode, If enabled by the server (Can be manditory with automatic grouping). One user drives and the other shoots, Turret mode tanks get double points (But onyl take one from the target). lost double points if killed. Have double ammo, And controllable speed (Max = _tankSpeed * 2 Min = _tankSpeed). Plus it takes 2 shots to kill a turret mode tank. Points gained and lost by turret tanks are divided evenly between the users, Unless the server is all turret mode, in h which case two users are displayed as one.
|(Unknown)
|
|Dogbert
|(Old)
|-
|Ability for a team to vote to 'banish' someone from their team
|style="background-color:#808080;"|Idea
|
*Possibly unfair to newer players. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|There should be a game of cops and robbers. The teams can change after about 10 mins or so.
|style="background-color:#FFFF00;"|(Unknown)
|
|iPod
|(Old)
|-
|A special FFA Game mode "Team by Flags". This means, same Flag = same Team, so if there is a Tank with Rapid fire, and you pick up Rapid fire, you are automatically handled as Team member (this means, killing the other Tank with Rapid fire will be handled the same way as when killing a team member). YHARG: Funky idea: what about a game mode where teams shared flag abilities? Like, each player on a team's flag applies to the whole team. This could make for some interesting combos...
|(Unknown)
|
|Agonizer
|(Old)
|-
|Make life trickier for the Rogue Team; with a mix of Rogues and Colored Teams, the Rogues have more targets. This should also change the effect of the Masquerade flag - perhaps your tank is invisible to Rogues (like Cloaking)?
|(Unknown)
|
|NickGrim
|(Old)
|-
|A server option to make deaths not affect your score unless they were self-inflicted/team (the method used by many online games). This would encourage more aggressive play, because it's worth going out and blasting. As it is, you've got a very good chance by just phantoming/OOing out of the way and keeping you score at zero to stay in the top three places! It would also help fix the rather unfair situation of spawning just below a building on which someone is GM-camping...there's pretty much no way to escape, so you lose a point.
|(Unknown)
|
|LionsPhil
|(Old)
|-
|Don't show individual score in CTF games. This might help teamplay as it reduces the incentive to run around as if it would be FFA.
|(Unknown)
|
|abli
|(Old)
|-
|Give points to the player how captures flag in CTF. (Say, around 4 or so) After all, it is often a bigger job than killing someone.
|(Unknown)
|
|abli
|(Old)
|-
|Ducati/Freestyle "Roles" mode: Make a game mode where players are presented with a list of flag choices (limitable to a few roles, if wanted) at respawn or connect time, and are forced to use this flag for the remainder of their connection/tank life. This would be really useful in the case of stealth vs. seer, where you could choose to be stealth or seer, but couldn't switch between them. Another idea would be high speed vs. quick turn. Or steamroller vs. machine gun... Team play would have the interesting effect of people banding together and people with each role on the team. Especially in stealth vs. seer, where a seer team member could warn the team about enemies! There would be no team flags/bases.
|(Unknown)
|
|YHARG
|(Old)
|-
|New game called tag were someone is it and they shoot someone else and there it and ect.
|(Unknown)
|
|Supermatthew
|(Old)
|-
|Also a new game called "Hide and seek" were everyone is clocked(think thats it, were you don't see them on radar) except one who is it. he needs to find someone and shoot them then hese cloked and who was shot is not. Also when someone is shot there sent back to Ground zero( 0X, 0Y, 0Z ) so they can't shoot who ever just shot them.
|(Unknown)
|
|Supermatthew
|(Old)
|-
|"Cat" game: when a player dies, he/she respawns automaticaly, after 3 secs or so. When they have respawned 9 times, they can no longer spawn, and are observers. The one who lasts the longest wins. Games are timed.
|(Unknown)
|
|(Unknown)
|4/20/2007
|-
|}
</div>

== Maps, Mapping, and BZW ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Materials that don't allow OO and PZ to go through
|style="background-color:#808080;"|Idea
|(Unknown)
|
*Would be nice for multilevel worlds made with the new ability to have objects above the ground.
*Sounds awesome! TD-Linux 17:41, 12 March 2007 (EDT)
|(Old)
|-
|Differently-shaped teleporters (circles, triangles, etc.)
|style="background-color:#808080;"|Idea
|
*probably low priority
|MORPH
|(Old)
|-
|360 degree teleports - hit a spot on the ground or in the air from any direction and you teleport
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Configurable random teleporters - teleports to a different location every time
|style="background-color:#808080;"|Idea
|
*Idea is a bit vague... randomized teles are implemented if you use multiple links. Is this what is meant by this suggestion? -L4m3r
|MORPH
|(Old)
|-
|Triggers in levels
|style="background-color:#FFFF00;"|(Unknown)
|
*Triggers for what? unless you're talking about AI, this could most likely be handled with a server plug-in. [[User:L4m3r|L4m3r]]
|Dragonstar
|(Old)
|-
|wraparound world - radar remains centered on your current position. Internally, objects leaving the north border reappear to the south, but from the user's radar / visible perspective, you just see to the horizon. I believe this is how the original Battlezone worked. There are some implications: laser would need a range limit.
|(Unknown)
|
|nsayer
|(Old)
|-
|}
</div>

== Server Options, Administration, Plug-ins, and the Plug-in API ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Ability to configure server to turn somethings off or on depending on number of players - for instance, turn off ricochet after a certain number of players are connected, turn off GM & laser if a certain number of players aren't playing (GM & Laser with 2 players is kinda ridiculous)
|style="background-color:#808080;"|Idea
|
|MORPH
|(Old)
|-
|Allow custom-made weapons with a Object-Oriented scripting language (sorta like Liero AI uses: http://helios.et.put.poznan.pl/~sskowron/liero/index.html )
|(Unknown)
|
|Dragonstar
|(Old)
|-
|Preset world weapons that can be fired manually by admins from within BzFlag.
|(Unknown)
|
|Dogbert
|(Old)
|-
|}
</div>

== Graphics & Sound ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Sounds of tanks moving.
|(Unknown)
|
|iPod
|(Old)
|-
|Have different tank death scenes for the dying tank point of view. I realize there is some time needed for one to die and respawn, but the jumping effect one sees when killed irritates me to no end! I'd be happier if all faded to black or white or orange and had text across the screen saying ""respawning... please wait"" :) Also, when killed and your tank was moving toward a building, it just falls right thru it until it hits the ground.. wrong physics there! Splatter or tumble or shatter or something :)
|(Unknown)
|
|Robi
|(Old)
|-
|Custom color schemes for rogue players. The turret and body components can be chosen to be one of a predefined set of colors (e.g. red, yellow, black, white, blue, green, purple...). The game prohibits choosing a color scheme that matches a team scheme (e.g. red turret with red body) and the limited set stops someone choosing a shade which is nearly a team color (e.g. 0xFE0000 instead of 0xFF0000) (and also save texture memory, I think).
|(Unknown)
|
|LionsPhil
|(Old)
|-
|Allow a small decal on the back of the top of the tank. (think Half-Life's customizable spraypaint). Possibly also apply it to any held flag?
|(Unknown)
|
|LionsPhil
|(Old)
|-
|wireframe mode! man, this would make the game ten times cooler for nostalgia
|(Unknown)
|
|rjbs
|(Old)
|-
|I'd like to see something more interesting done with the sky... maybe there could be a little ufo (easter egg) that would fly around occasionally? Tux on a ufo! ;)
|(Unknown)
|
|YHARG
|(Old)
|-
|Flag decals: Each flag would have a little icon/decal showing it's type ONLY when held by a player. It's kind of nice to be able to surprise people with an undercover shockwave, but doesn't make sense to have to right click (identify) or check the user list to see what flag someone has.
|(Unknown)
|
|YHARG
|(Old)
|-
|Background music! : (This can be done with an external media player so it shouldn't be the heighest priority, It would be nice to be able to control your music from within BzFlag)
|(Unknown)
|
|YHARG
|(Old)
|-
|}
</div>

== List Server and Other Global Services ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Multiple list servers, in case bzflag.org goes down (as it happened around feb. 15. 2004)
|(Unknown)
|
|abli
|(Old)
|-
|}
</div>

[[Category:Development]]

BZFlagWiki:Content Policy

2007-04-12T19:27:11Z

L4m3r: Grammar! there vs their :P

This page describes the acceptable content policy for articles in this wiki.

== Overview ==
The BZFlag wiki is provided as shared informational resource for the player community. Its intended content is factual information regarding the BZFlag game and its community. To do this it must maintain a level of impartiality when dealing with that content. Below is a set of guidelines for users posting articles here.

== Subjects ==
All articles on the BZFlag Wiki MUST have a direct bearing on the game itself. Articles that are not directly related to the game will be removed from the wiki.

=== Acceptable Subjects ===
The following are acceptable subjects for BZFlag Wiki Articles.
* Documentation of BZFlag Software.
* Documentation of BZFlag terms and concepts.
* Documentation of tasks specific to the direct use of the BZFlag source code, or software.
* Collaborative development projects directly related to BZFlag.
* Factual historical references to BZFlag, software, source code, and developers.
* General Information about specific maps, and links to their location.
* General Information about specific servers, and links to their administration and websites.
* General Information about server networks, and links to their administration and websites.

=== Unacceptable Subjects ===
The following subjects should not be addressed in wiki articles.
* Server specific rules and policies.
* Advertisements for specific servers, users, or maps.

== Article Contents ==
The contents of articles must be presented in an impartial and factual manner. Wiki articles should be considered descriptive of their subjects, and at all times informational. If a statement can not be backed up with facts, it does not belong in the article. If the fact has no bearing on the subject matter in a descriptive way, it does not belong in the article. Some articles will have more or less factual content following these rules. The further away a subject is from the core game, the less information is applicable to the wiki. The page describing the command line options of the BZFS server will have significantly more applicable information then an article on a network of servers will.

If the article does not deal directly with the BZFlag software or development process, and needs to reference information that is available on other websites, then the article should simply link to them. This includes items such as server rules, and other information that is elsewhere.

Articles should not be written to promote or hinder any one specific server, network, group, or person. No statements should be based on opinion unless the article is designed specifically for promoting a collaborative workflow. In all cases statements should be presented with civility.

Articles do not "belong" to any one author. The nature of a wiki is for community created and edited content. Recognize that articles can be changed by anyone and no individual controls any specific article; therefore, any writing you contribute can be mercilessly edited and redistributed at will by the community. If the author of an articles wishes to post information that is not to be changed by other users (such as server rules), it should not be part of the wiki article. This information should be linked to via an external web-link.

== Writing Style ==
As previously stated articles should be written to be descriptive. Personal words like "you", "me", "your", etc.. should not be used, as the wiki is not a conversation. If part of the article is a description of steps of action, then they should simply be described as the action taken, not the actions of the specific user. The various talk namespaces are of course exempted from this rule.

== Content Disputes ==
As the wiki is user edited, conflicts and edits in the contents or articles can and will occur. When an article is changed, the previous author should read the changes and attempt to understand them before taking any action. Users changing articles should leave descriptive comments with the change indicating why they changed the article. Be civil. If a previous author disputes the changes, they should attempt to work out an amicable solution on the talk page of the article. Stay cool when the editing gets hot; find consensus. The revert function should not be used in haste; it is primarily intended to assist with article vandalism, or when a change blatantly disregards this policy. Users that are unable to work out acceptable content for an article should contact the Project Administrators and be prepared to explain the issue and how the desired content will follow this policy.

==Page History==
Please [[BZFlagWiki:Be_bold|'''Be Bold''']] when editing, moving and creating articles. This is how a wiki grows and do not worry about messing up. All prior versions of articles are kept, so there is no way that you can accidentally damage the BZFlag Wiki or irretrievably destroy content. But remember — whatever you write here will be preserved for posterity.

[[Category:BZFlagWiki Policy]]

Ideas

2007-04-04T18:40:37Z

L4m3r:

{{Old}}
Feel free to make changes and updates to this page whenever possible. If you have any questions, feel free to [[Getting Help|ask for help]]. If you wish to make major changes to this page (i.e. remove large amounts of old ideas), please warn us ahead of time.

<b>NOTE: Work is in progress on this page. I'm converting to to a tabular format, and will then clean up and sort the ideas into categories. Please stand by. -L4m3r</b>

NOTE: These are just possiblilities. We won't be implementing everything here.<br>
NOTE: Flag ideas should be placed on [[Flag Ideas]]. Any other ideas can be placed here.

Status may include personal comments by developers.

== Adding ideas ==
* All ideas should be categorized and should be prefixed with a *.
* Sign your idea with four tildes: <nowiki>~~~~</nowiki>
* Describe in full and make sense!

== General/Gameplay ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Add support for 5 (or more) button mice
|Great Idea
|
|(Unknown)
|(Old)
|-
|Better physics
|In progress
|Planning, some changes in CVS.
|Unknown
|(Old)
|-
|SELF-DESTRUCT BLAST RADIUS: Self Destruct (delete key) should have a blast radius similar to Shock Wave, perhaps larger. If you get shot during the self-destruct count down, that should also trigger the same blast. If I gotta go, I want to take someone with me.
|(Unknown)
|
|BearRiver
|(Old)
|-
|3-second (or however long) 'invulnerability' for incoming tanks - but they can't shoot
|Idea
|I could see this backfiring... your spawn attracts opponents to come, wait, and blast you when you lose invincibility. -L4m3r
|MORPH
|(Old)
|-
|Ability to turn off ricochet for laser flag but allow ricochet for bullets... or let them bounce only n times.. OR implement mirror buildings/walls. Should go for some interesting self-kills when combined with the no-radar/bullet bounce
|Idea
|
|MORPH
|(Old)
|-
|Smart LockOn for GM - won't lock on to your teammates (configurable in server)
|Idea
|(M. Jetleb -> I don't like this idea, there should be at least *some* risks to using this weapon. Personally, I think there should be more (not fewer) risks to holding this weapon; I'd like to see the thing overheat and explode (killing the holder) if it's fired too often in a short period of time)
|MORPH
|(Old)
|-
|Small jumps
|Idea
|
|MORPH
|(Old)
|-
|Server option for genocide flag - if you're killed while you have it, your team dies :^)
|Idea
|Feasible with a plug-in, too. -L4m3r
|MORPH
|(Old)
|-
|for broadband or LAN connections - voice chat for teams
|Idea
|I really think that you can do this with another service; I'm not sure if being part of BZFlag would be a good idea due to size and bandwidth issues.
|MORPH
|(Old)
|-
|Tank avatars (uploadable tank images) - have to think about shapes, though - someone could make a 1x1x1 pixel tank - that would suck - or a tank that looks like a building or pyramid. Clients don't have to accept downloading of avators (just view other tanks in default mode). Or just s-e-l-e-c-t from a certain number of predefined avatars that could come with the bzflag distribution. Or client provides a URL to download their avatar (saves server bandwidth).
|Idea
|Might not be implemented. Requires discussion; we may want to consider making the computer force a minimum size or something similar. *How about uploadable flag graphics?
|MORPH
|(Old)
|-
|'Kamikaze' option for players - can take someone out by suicide
|Idea
|Server option if implemented. Implemented with a plugin by Theme97
|MORPH
|(Old)
|-
|Server option: everyone is radar-stealthed by default unless you get a 'radar' flag. You can still see all buildings, pyramids, teleports, and arena walls, though.
|Good idea
|Make them use their window. ;)(M. Jetleb -> Given the fairly narrow field of view out the window and the time it takes to turn a tank all the way around for a look-see, I think this could be frustrating. How about everyone starts out with minimum range radar instead and gets longer ranges with an appropriate flag?)
|MORPH
|(Old)
|-
|Option for above: if you pick up GM or Laser, you're visible on radar to everyone whether they've got a radar flag or not
|Good idea
|
|MORPH
|(Old)
|-
|Selectable 'ricochet' fire - hold down shift key or something and your bullets won't ricochet
|Idea
|
|MORPH
|(Old)
|-
|Server option - tanks only have a certain number of times they can jump (gets reset when you get killed)
|Idea
|
|MORPH
|(Old)
|-
|Multiple-shields (server option for shield flags, or can be random - can get hit x number of times)
|Idea
|This is pretty much moot now. It's been shot down by the devs at least once, and a similar effect can be achieved by setting _shieldFlight to a very small number. This effectively provides as many hits as _maxFlagGrabs. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|Configurable 'radarless' and/or 'blind' zones in the arena - can't see what's in there on radar or via visuals
|Idea
|
|MORPH
|(Old)
|-
|Tank collisions - why can tanks drive through each other? Weird.
|Good Idea
|Lag could be a big problem here. If implemented, it must be impossible for two tanks to get stuck to each other. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|When tanks collide - great opportunity to implement tank damage concept, especially if one of them is moving especially fast, or has momentum flag, etc. Can push a tank off a building if your pushing them from their side.
|Idea
|Tank damage won't happen, but the kinetics could be neat, especially for mid-air collisions. It would certainly make "jump dancing" more interesting. [[User:L4m3r|L4m3r]]
|Morph
|(Old)
|-
|If a tank explodes right next to another tank, the other tank can be destroyed or get damaged
|Idea
|Somewhat implemented with the [[ShockwaveDeath]] plug-in. It would probably not be too hard to implement something similar without shockwaves. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|Skins or views- In-tank mode, bumper mode, out-of-cab mode, chase mode.
|(Unknown)
|
|MORPH
|(Old)
|-
|Weapon extension packs.
|(Unknown)
|Huh? Explain, please. [[User:L4m3r|L4m3r]]
|iPod
|(Old)
|-
|The ability to choose tanks, but they all die at one shot. maybe the jump height, speed, turn speed, acceleration, size can be preset.
|(Unknown)
|
|iPod
|(Old)
|-
|Option to choose different kinds of tanks. Different tanks could be weighted with different strengths and weaknesses. (almost like having a default flag). Would also need some form of health/damage status measurement, not just single hits. For example, there could be a larger, heavily armored tank that has powerful weapons, but moves slowly, versus a small, light, fast tank which is difficult to hit, but very low armor to protect from hits.
|(Unknown)
|
|Cue
|(Old)
|-
|What about a radar that only covers visible areas (don't passing through buildings/pyramids) ? This would leads to more placement tactics).
|(Unknown)
|
|K<nowiki>'</nowiki>limero
|(Old)
|-
|Always random respawn. Currently in CTF games first respawn is at own base. This can be abused by leaving and rejoining to get near base. This leave/rejoing trick is considered to be a mild form of cheating by many. Always random respawn would make it useless.
|(Unknown)
|
|abli
|(Old)
|-
|multiple (3?) jump stengths mini, normal, max...just the thing to confuse the opponents that expect one and you're off doing the other.
|(Unknown)
|
|kitchen
|(Old)
|-
|Anti camping. The ability to add "no camping zones" to areas of a map or to the entire map. Campers would be messaged that they're in a no camping zone, better start moving and have a prescribe number of seconds to move away or die. If a player returns to the same NCZ (no camping zone) and receives x warnings then he's disconnected. NCZs could be marked by a different color shade from a "normal" spot and could be exempt to a single team (like at their flag base). It's just a rough idea.
|(Unknown)
|
|pherris
|(Old)
|-
|Shield Flag Changes: Give Shield flag a radius, and draw it like a moving less opaque blue shockwave. Any tanks inside the shield radius would be protected, until the shield got hit a certain number of times.
|(Unknown)
|
|YHARG
|(Old)
|-
|At our company, we instituted a voluntary policy of dropping flags after 1 kill. Prevents slaughters and keeps things rolling more. It'd be great to be able to have the game do this for us, plus I'd love to see it turned on at external sites.
|(Unknown)
|
|TomMatelich
|(Old)
|-
|Server option: default powers -- flag(s) that everyone in the game automatically has (this wouldn't count as holding a flag). For example, the current Jumping option would == including Jumping as a default power.
|(Unknown)
|
|NebNamwen
|(Old)
|}
</div>

== UI ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Make option to show previous players list
|Idea
|
|(Unknown)
|(Old)
|-
|Make ALL server options available from the menus
|Idea
|There are a LOT of server options, and this could add quite a bit of clutter. If you need more than a basic game, you should probably learn to start BZFS from the command line anyway. -L4m3r
|MORPH
|(Old)
|-
|Separate windows for player messages & server messages
|Good idea.
|
|MORPH
|(Old)
|-
|Message log
|Good idea.
|
|MORPH
|(Old)
|-
|Send message to everyone 'but' specified player (crosses team boundaries, or not)
|Idea
|Hmm. Everybody BUT a specified player? [M. Jetleb -> as in: "Let's all get the GM guy" without the GM guy knowing he's facing a co-ordinated attack - I like this idea)
|MORPH
|(Old)
|-
|The ability to see what the world is like before connecting to the server.
|(Unknown)
|
|iPod
|(Old)
|-
|Multi-monitor support (i.e., radar on one screen, window on another, chat/event log on a third)
|(Unknown)
|
|bhtooefr
|(Old)
|-
|Make a part in bzflag to put up a real server. 1st screen has the flags you want, next page is to find the MAP file that you created on your hard drive, next page pick if you want jumping etc.
|(Unknown)
|
|Colin
|(Old)
|-
|}
</div>

== Technical ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Better network handling
|In progress
|
|(Unknown)
|(Old)
|-
|Better robot AI
|Idea
|Don't know if players would like it or not in multiplayer game. Pluggable or scriptable robot AI , maybe? - Code must be restructured first (Server side bots are coming! [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT))
|(Unknown)
|(Old)
|-
|Better positioning of tanks
|Idea
|BZFlag already does this, but the algorithm is bad. Needs work.
|MORPH
|(Old)
|-
|Serious multithreaded design - shouldn't lock up interface while looking for servers, or doing anything else. This program is way-unstable on Windows
|In Progress
|We're working on these problems; many complaints are due to people still using old servers/clients.
|MORPH
|(Old)
|-
|Some type of BZFlag GUID* to ban players who cheat - won't accept players who disable their GUID, etc.

<nowiki>*</nowiki>Global Unique Identifier, sort of like an IP addrss, but permanent. Usually a number. Problem occurs when you lose your GUID (have to reformat your HD, etc. How do you keep someone from hacking their GUID, or setting up a modified BZFlag server for identity theft, etc.
|(Unknown)
|I doubt this is even possible, let alone practical. What about people who play from more than one location? And, because this is an open-source game, it would probably be cracked in minutes. Any verification can be spoofed, or at least altered. there is no foolproof way to permanently ban someone. -L4m3r
|MORPH
|(Old)
|-
|To prevent cheating - the server determines what flags & abilities each tank has (possible?)
|Idea
|Seriously being considered. This would also have the advantage of allowing different versions of clients and servers to work together. Yes, it's possible, but this type of change will mean a change in the network protocols. Being worked on for 2.2
|MORPH
|(Old)
|-
|BZFlag for mac in seperate data and application files.
|(Unknown)
|
|iPod
|(Old)
|-
|J2ME client (allows one to play on a cell phone), would use radar
|(Unknown)
|
|bhtooefr
|(Old)
|-
|Special 'open source' BZFlag version (server and client) which is guaranteed to be compatible with all other BZFlag versions.
|(Unknown)
|BZFlag is already open-source, and making a universally-compatible client is not even remotely practical. Incompatibility is part of why the game breaks off new versions in the first place. [[User:L4m3r|L4m3r]]
|Orca
|(Old)
|-
|}
</div>

== Game Modes, Team Play, and Scoring ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Tounament mode
|Idea
|Great Idea?
|(Unknown)
|(Old)
|-
|When you shoot someone on your own team, instead of both of you blowing up, neither is destroyed, and their score goes up one, while your's goes down one. This would make teamkilling impossible and greatly discourage traitors as well.
|Idea
|But then couldn't cheaters spawn two clients and ramp up their scores by teamkilling their other login? --YHARG
|Trigger Happy Nerd
|(Old)
|-
|A new gameplay mode- Takes two to tank. One to control the (rotating) turret, the other drives. KIA switches positions. "Teamplay" but all in one tank.
|(Unknown)
|I see serious lag issues with this... How does Halo do it? ;) -L4m3r
|MORPH
|(Old)
|-
|Turret mode, If enabled by the server (Can be manditory with automatic grouping). One user drives and the other shoots, Turret mode tanks get double points (But onyl take one from the target). lost double points if killed. Have double ammo, And controllable speed (Max = _tankSpeed * 2 Min = _tankSpeed). Plus it takes 2 shots to kill a turret mode tank. Points gained and lost by turret tanks are divided evenly between the users, Unless the server is all turret mode, in h which case two users are displayed as one.
|(Unknown)
|
|Dogbert
|(Old)
|-
|Ability for a team to vote to 'banish' someone from their team
|Idea
|Possibly unfair to newer players. [[User:L4m3r|L4m3r]]
|MORPH
|(Old)
|-
|There should be a game of cops and robbers. The teams can change after about 10 mins or so.
|(Unknown)
|
|iPod
|(Old)
|-
|A special FFA Game mode "Team by Flags". This means, same Flag = same Team, so if there is a Tank with Rapid fire, and you pick up Rapid fire, you are automatically handled as Team member (this means, killing the other Tank with Rapid fire will be handled the same way as when killing a team member). YHARG: Funky idea: what about a game mode where teams shared flag abilities? Like, each player on a team's flag applies to the whole team. This could make for some interesting combos...
|(Unknown)
|
|Agonizer
|(Old)
|-
|Make life trickier for the Rogue Team; with a mix of Rogues and Colored Teams, the Rogues have more targets. This should also change the effect of the Masquerade flag - perhaps your tank is invisible to Rogues (like Cloaking)?
|(Unknown)
|
|NickGrim
|(Old)
|-
|A server option to make deaths not affect your score unless they were self-inflicted/team (the method used by many online games). This would encourage more aggressive play, because it's worth going out and blasting. As it is, you've got a very good chance by just phantoming/OOing out of the way and keeping you score at zero to stay in the top three places! It would also help fix the rather unfair situation of spawning just below a building on which someone is GM-camping...there's pretty much no way to escape, so you lose a point.
|(Unknown)
|
|LionsPhil
|(Old)
|-
|Don't show invidual score in CTF games. This might help teamplay as it reduces the incentive to run around as if it would be FFA.
|(Unknown)
|
|abli
|(Old)
|-
|Give points to the player how captures flag in CTF. (Say, around 4 or so) After all, it is often a bigger job than killing someone.
|(Unknown)
|
|abli
|(Old)
|-
|Ducati/Freestyle "Roles" mode: Make a game mode where players are presented with a list of flag choices (limitable to a few roles, if wanted) at respawn or connect time, and are forced to use this flag for the remainder of their connection/tank life. This would be really useful in the case of stealth vs. seer, where you could choose to be stealth or seer, but couldn't switch between them. Another idea would be high speed vs. quick turn. Or steamroller vs. machine gun... Team play would have the interesting effect of people banding together and people with each role on the team. Especially in stealth vs. seer, where a seer team member could warn the team about enemies! There would be no team flags/bases.
|(Unknown)
|
|YHARG
|(Old)
|-
|New game called tag were someone is it and they shoot someone else and there it and ect.
|(Unknown)
|
|Supermatthew
|(Old)
|-
|Also a new game called "Hide and seek" were everyone is clocked(think thats it, were you don't see them on radar) except one who is it. he needs to find someone and shoot them then hese cloked and who was shot is not. Also when someone is shot there sent back to Ground zero( 0X, 0Y, 0Z ) so they can't shoot who ever just shot them.
|(Unknown)
|
|Supermatthew
|(Old)
|-
|}
</div>

== Maps, Mapping, and BZW ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Materials that don't allow OO and PZ to go through
|Idea
|Would be nice for multilevel worlds made with the new ability to have objects above the ground. (Sounds awesome! TD-Linux 17:41, 12 March 2007 (EDT))
|(Unknown)
|(Old)
|-
|Differently-shaped teleporters (circles, triangles, etc.)
|Idea
|probably low priority
|MORPH
|(Old)
|-
|360 degree teleports - hit a spot on the ground or in the air from any direction and you teleport
|
|Idea
|MORPH
|(Old)
|-
|Configurable random teleporters - teleports to a different location every time
|Idea
|Idea is a bit vague... randomized teles are implemented if you use multiple links. Is this what is meant by this suggestion? -L4m3r
|MORPH
|(Old)
|-
|Triggers in levels
|(Unknown)
|Triggers for what? unless you're talking about AI, this could most likely be handled with a server plug-in. [[User:L4m3r|L4m3r]]
|Dragonstar
|(Old)
|-
|wraparound world - radar remains centered on your current position. Internally, objects leaving the north border reappear to the south, but from the user's radar / visible perspective, you just see to the horizon. I believe this is how the original Battlezone worked. There are some implications: laser would need a range limit.
|(Unknown)
|
|nsayer
|(Old)
|-
|}
</div>

== Server Options, Administration, Plug-ins, and the Plug-in API ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Ability to configure server to turn somethings off or on depending on number of players - for instance, turn off ricochet after a certain number of players are connected, turn off GM & laser if a certain number of players aren't playing (GM & Laser with 2 players is kinda ridiculous)
|Idea
|
|MORPH
|(Old)
|-
|Allow custom-made weapons with a Object-Oriented scripting language (sorta like Liero AI uses: http://helios.et.put.poznan.pl/~sskowron/liero/index.html )
|(Unknown)
|
|Dragonstar
|(Old)
|-
|Preset world weapons that can be fired manually by admins from within BzFlag.
|(Unknown)
|
|Dogbert
|(Old)
|-
|}
</div>

== Graphics & Sound ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Sounds of tanks moving.
|(Unknown)
|
|iPod
|(Old)
|-
|Have different tank death scenes for the dying tank point of view. I realize there is some time needed for one to die and respawn, but the jumping effect one sees when killed irritates me to no end! I'd be happier if all faded to black or white or orange and had text across the screen saying ""respawning... please wait"" :) Also, when killed and your tank was moving toward a building, it just falls right thru it until it hits the ground.. wrong physics there! Splatter or tumble or shatter or something :)
|(Unknown)
|
|Robi
|(Old)
|-
|Custom color schemes for rogue players. The turret and body components can be chosen to be one of a predefined set of colors (e.g. red, yellow, black, white, blue, green, purple...). The game prohibits choosing a color scheme that matches a team scheme (e.g. red turret with red body) and the limited set stops someone choosing a shade which is nearly a team color (e.g. 0xFE0000 instead of 0xFF0000) (and also save texture memory, I think).
|(Unknown)
|
|LionsPhil
|(Old)
|-
|Allow a small decal on the back of the top of the tank. (think Half-Life's customizable spraypaint). Possibly also apply it to any held flag?
|(Unknown)
|
|LionsPhil
|(Old)
|-
|wireframe mode! man, this would make the game ten times cooler for nostalgia
|(Unknown)
|
|rjbs
|(Old)
|-
|I'd like to see something more interesting done with the sky... maybe there could be a little ufo (easter egg) that would fly around occasionally? Tux on a ufo! ;)
|(Unknown)
|
|YHARG
|(Old)
|-
|Flag decals: Each flag would have a little icon/decal showing it's type ONLY when held by a player. It's kind of nice to be able to surprise people with an undercover shockwave, but doesn't make sense to have to right click (identify) or check the user list to see what flag someone has.
|(Unknown)
|
|YHARG
|(Old)
|-
|Background music! : (This can be done with an external media player so it shouldn't be the heighest priority, It would be nice to be able to control your music from within BzFlag)
|(Unknown)
|
|YHARG
|(Old)
|-
|}
</div>

== List Server and Other Global Services ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="7%"|Status
!width="40%"|Commentary
!width="7%"|Submitter
!width="6%"|Date
|-
|Multiple list servers, in case bzflag.org goes down (as it happened around feb. 15. 2004)
|(Unknown)
|
|abli
|(Old)
|-
|}
</div>

[[Category:Development]]

Ideas

2007-03-25T22:03:50Z

L4m3r: /* General/Gameplay */

{{Old}}
Feel free to make changes and updates to this page whenever possible. If you have any questions, feel free to [[Getting Help|ask for help]]. If you wish to make major changes to this page (i.e. remove large amounts of old ideas), please warn us ahead of time.

<b>NOTE: Work is in progress on this page. I'm converting to to a tabular format, and will then clean up and sort the ideas into categories. Please stand by. -L4m3r</b>

NOTE: These are just possiblilities. We won't be implementing everything here.<br>
NOTE: Flag ideas should be placed on [[Flag Ideas]]. Any other ideas can be placed here.

Status may include personal comments by developers.

== Adding ideas ==
* All ideas should be categorized and should be prefixed with a *.
* Sign your idea with four tildes: <nowiki>~~~~</nowiki>
* Describe in full and make sense!

== General/Gameplay ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="10%"|Status
!width="40%"|Commentary
!width="10%"|Submitter
|-
|Add support for 5 (or more) button mice
|Great Idea
|Old?
|(Unknown)
|-
|Better physics
|In progress
|Planning, some changes in CVS. (Old?)
|Unknown
|-
|SELF-DESTRUCT BLAST RADIUS: Self Destruct (delete key) should have a blast radius similar to Shock Wave, perhaps larger. If you get shot during the self-destruct count down, that should also trigger the same blast. If I gotta go, I want to take someone with me.
|(Unknown)
|
|BearRiver
|-
|3-second (or however long) 'invulnerability' for incoming tanks - but they can't shoot
|Idea
|I could see this backfiring... your spawn attracts opponents to come, wait, and blast you when you lose invincibility. -L4m3r
|MORPH
|-
|Ability to turn off ricochet for laser flag but allow ricochet for bullets... or let them bounce only n times.. OR implement mirror buildings/walls. Should go for some interesting self-kills when combined with the no-radar/bullet bounce
|Idea
|
|MORPH
|-
|Smart LockOn for GM - won't lock on to your teammates (configurable in server)
|Idea
|(M. Jetleb -> I don't like this idea, there should be at least *some* risks to using this weapon. Personally, I think there should be more (not fewer) risks to holding this weapon; I'd like to see the thing overheat and explode (killing the holder) if it's fired too often in a short period of time)
|MORPH
|-
|Small jumps
|Idea
|
|MORPH
|-
|Server option for genocide flag - if you're killed while you have it, your team dies :^)
|Idea
|Feasible with a plug-in, too. -L4m3r
|MORPH
|-
|for broadband or LAN connections - voice chat for teams
|Idea
|I really think that you can do this with another service; I'm not sure if being part of BZFlag would be a good idea due to size and bandwidth issues.
|MORPH
|-
|Tank avatars (uploadable tank images) - have to think about shapes, though - someone could make a 1x1x1 pixel tank - that would suck - or a tank that looks like a building or pyramid. Clients don't have to accept downloading of avators (just view other tanks in default mode). Or just s-e-l-e-c-t from a certain number of predefined avatars that could come with the bzflag distribution. Or client provides a URL to download their avatar (saves server bandwidth).
|Idea
|Might not be implemented. Requires discussion; we may want to consider making the computer force a minimum size or something similar. *How about uploadable flag graphics?
|MORPH
|-
|'Kamikaze' option for players - can take someone out by suicide
|Idea
|Server option if implemented. Implemented with a plugin by Theme97
|MORPH
|-
|Server option: everyone is radar-stealthed by default unless you get a 'radar' flag. You can still see all buildings, pyramids, teleports, and arena walls, though.
|Good idea
|Make them use their window. ;)(M. Jetleb -> Given the fairly narrow field of view out the window and the time it takes to turn a tank all the way around for a look-see, I think this could be frustrating. How about everyone starts out with minimum range radar instead and gets longer ranges with an appropriate flag?)
|MORPH
|-
|Option for above: if you pick up GM or Laser, you're visible on radar to everyone whether they've got a radar flag or not
|Good idea
|
|MORPH
|-
|Selectable 'ricochet' fire - hold down shift key or something and your bullets won't ricochet
|Idea
|
|MORPH
|-
|Server option - tanks only have a certain number of times they can jump (gets reset when you get killed)
|Idea
|
|MORPH
|-
|Multiple-shields (server option for shield flags, or can be random - can get hit x number of times)
|Idea
|This is pretty much moot now. It's been shot down by the devs at least once, and a similar effect can be achieved by setting _shieldFlight to a very small number. This effectively provides as many hits as _maxFlagGrabs. [[User:L4m3r|L4m3r]]
|MORPH
|-
|Configurable 'radarless' and/or 'blind' zones in the arena - can't see what's in there on radar or via visuals
|Idea
|
|MORPH
|-
|Tank collisions - why can tanks drive through each other? Weird.
|Good Idea
|Lag could be a big problem here. If implemented, it must be impossible for two tanks to get stuck to each other. [[User:L4m3r|L4m3r]]
|MORPH
|-
|When tanks collide - great opportunity to implement tank damage concept, especially if one of them is moving especially fast, or has momentum flag, etc. Can push a tank off a building if your pushing them from their side.
|Idea
|Tank damage won't happen, but the kinetics could be neat, especially for mid-air collisions. It would certainly make "jump dancing" more interesting. [[User:L4m3r|L4m3r]]
|Morph
|-
|If a tank explodes right next to another tank, the other tank can be destroyed or get damaged
|Idea
|Somewhat implemented with the [[ShockwaveDeath]] plug-in. It would probably not be too hard to implement something similar without shockwaves. [[User:L4m3r|L4m3r]]
|MORPH
|-
|Skins or views- In-tank mode, bumper mode, out-of-cab mode, chase mode.
|(Unknown)
|
|MORPH
|-
|Weapon extension packs.
|(Unknown)
|Huh? Explain, please. [[User:L4m3r|L4m3r]]
|iPod
|-
|The ability to choose tanks, but they all die at one shot. maybe the jump height, speed, turn speed, acceleration, size can be preset.
|(Unknown)
|
|iPod
|-
|Option to choose different kinds of tanks. Different tanks could be weighted with different strengths and weaknesses. (almost like having a default flag). Would also need some form of health/damage status measurement, not just single hits. For example, there could be a larger, heavily armored tank that has powerful weapons, but moves slowly, versus a small, light, fast tank which is difficult to hit, but very low armor to protect from hits.
|(Unknown)
|
|Cue
|-
|What about a radar that only covers visible areas (don't passing through buildings/pyramids) ? This would leads to more placement tactics).
|(Unknown)
|
|K<nowiki>'</nowiki>limero
|-
|Always random respawn. Currently in CTF games first respawn is at own base. This can be abused by leaving and rejoining to get near base. This leave/rejoing trick is considered to be a mild form of cheating by many. Always random respawn would make it useless.
|(Unknown)
|
|abli
|-
|multiple (3?) jump stengths mini, normal, max...just the thing to confuse the opponents that expect one and you're off doing the other.
|(Unknown)
|
|kitchen
|-
|Anti camping. The ability to add "no camping zones" to areas of a map or to the entire map. Campers would be messaged that they're in a no camping zone, better start moving and have a prescribe number of seconds to move away or die. If a player returns to the same NCZ (no camping zone) and receives x warnings then he's disconnected. NCZs could be marked by a different color shade from a "normal" spot and could be exempt to a single team (like at their flag base). It's just a rough idea.
|(Unknown)
|
|pherris
|-
|Shield Flag Changes: Give Shield flag a radius, and draw it like a moving less opaque blue shockwave. Any tanks inside the shield radius would be protected, until the shield got hit a certain number of times.
|(Unknown)
|
|YHARG
|-
|At our company, we instituted a voluntary policy of dropping flags after 1 kill. Prevents slaughters and keeps things rolling more. It'd be great to be able to have the game do this for us, plus I'd love to see it turned on at external sites.
|(Unknown)
|
|TomMatelich
|-
|Server option: default powers -- flag(s) that everyone in the game automatically has (this wouldn't count as holding a flag). For example, the current Jumping option would == including Jumping as a default power.
|(Unknown)
|
|NebNamwen
|}
</div>

== UI ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="10%"|Status
!width="40%"|Commentary
!width="10%"|Submitter
|-
|Make option to show previous players list
|Idea
|
|(Unknown)
|-
|Make ALL server options available from the menus
|Idea
|There are a LOT of server options, and this could add quite a bit of clutter. If you need more than a basic game, you should probably learn to start BZFS from the command line anyway. -L4m3r
|MORPH
|-
|Separate windows for player messages & server messages
|Good idea.
|
|MORPH
|-
|Message log
|Good idea.
|
|MORPH
|-
|Send message to everyone 'but' specified player (crosses team boundaries, or not)
|Idea
|Hmm. Everybody BUT a specified player? [M. Jetleb -> as in: "Let's all get the GM guy" without the GM guy knowing he's facing a co-ordinated attack - I like this idea)
|MORPH
|-
|The ability to see what the world is like before connecting to the server.
|(Unknown)
|
|iPod
|-
|Multi-monitor support (i.e., radar on one screen, window on another, chat/event log on a third)
|(Unknown)
|
|bhtooefr
|-
|Make a part in bzflag to put up a real server. 1st screen has the flags you want, next page is to find the MAP file that you created on your hard drive, next page pick if you want jumping etc.
|(Unknown)
|
|Colin
|-
|}
</div>

== Technical ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="10%"|Status
!width="40%"|Commentary
!width="10%"|Submitter
|-
|Better network handling
|In progress
|Old?
|(Unknown)
|-
|Better robot AI
|Idea
|Don't know if players would like it or not in multiplayer game. Pluggable or scriptable robot AI , maybe? - Code must be restructured first (Server side bots are coming! [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT))
|(Unknown)
|-
|Better positioning of tanks
|Idea
|BZFlag already does this, but the algorithm is bad. Needs work.
|MORPH
|-
|Serious multithreaded design - shouldn't lock up interface while looking for servers, or doing anything else. This program is way-unstable on Windows
|In Progress
|We're working on these problems; many complaints are due to people still using old servers/clients.
|MORPH
|-
|Some type of BZFlag GUID* to ban players who cheat - won't accept players who disable their GUID, etc.

<nowiki>*</nowiki>Global Unique Identifier, sort of like an IP addrss, but permanent. Usually a number. Problem occurs when you lose your GUID (have to reformat your HD, etc. How do you keep someone from hacking their GUID, or setting up a modified BZFlag server for identity theft, etc.
|(Unknown)
|I doubt this is even possible, let alone practical. What about people who play from more than one location? And, because this is an open-source game, it would probably be cracked in minutes. Any verification can be spoofed, or at least altered. there is no foolproof way to permanently ban someone. -L4m3r
|MORPH
|-
|To prevent cheating - the server determines what flags & abilities each tank has (possible?)
|Idea
|Seriously being considered. This would also have the advantage of allowing different versions of clients and servers to work together. Yes, it's possible, but this type of change will mean a change in the network protocols. Being worked on for 2.2
|MORPH
|-
|BZFlag for mac in seperate data and application files.
|(Unknown)
|
|iPod
|-
|J2ME client (allows one to play on a cell phone), would use radar
|(Unknown)
|
|bhtooefr
|-
|Special 'open source' BZFlag version (server and client) which is guaranteed to be compatible with all other BZFlag versions.
|(Unknown)
|BZFlag is already open-source, and making a universally-compatible client is not even remotely practical. Incompatibility is part of why the game breaks off new versions in the first place. [[User:L4m3r|L4m3r]]
|Orca
|-
|}
</div>

== Game Modes, Team Play, and Scoring ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="10%"|Status
!width="40%"|Commentary
!width="40%"|Submitter
|-
|Tounament mode
|Idea
|Great Idea?
|(Unknown)
|-
|When you shoot someone on your own team, instead of both of you blowing up, neither is destroyed, and their score goes up one, while your's goes down one. This would make teamkilling impossible and greatly discourage traitors as well.
|Idea
|But then couldn't cheaters spawn two clients and ramp up their scores by teamkilling their other login? --YHARG
|Trigger Happy Nerd
|-
|A new gameplay mode- Takes two to tank. One to control the (rotating) turret, the other drives. KIA switches positions. "Teamplay" but all in one tank.
|(Unknown)
|I see serious lag issues with this... How does Halo do it? ;) -L4m3r
|MORPH
|-
|Turret mode, If enabled by the server (Can be manditory with automatic grouping). One user drives and the other shoots, Turret mode tanks get double points (But onyl take one from the target). lost double points if killed. Have double ammo, And controllable speed (Max = _tankSpeed * 2 Min = _tankSpeed). Plus it takes 2 shots to kill a turret mode tank. Points gained and lost by turret tanks are divided evenly between the users, Unless the server is all turret mode, in h which case two users are displayed as one.
|(Unknown)
|
|Dogbert
|-
|Ability for a team to vote to 'banish' someone from their team
|Idea
|Possibly unfair to newer players. [[User:L4m3r|L4m3r]]
|MORPH
|-
|There should be a game of cops and robbers. The teams can change after about 10 mins or so.
|(Unknown)
|
|iPod
|-
|A special FFA Game mode "Team by Flags". This means, same Flag = same Team, so if there is a Tank with Rapid fire, and you pick up Rapid fire, you are automatically handled as Team member (this means, killing the other Tank with Rapid fire will be handled the same way as when killing a team member). YHARG: Funky idea: what about a game mode where teams shared flag abilities? Like, each player on a team's flag applies to the whole team. This could make for some interesting combos...
|(Unknown)
|
|Agonizer
|-
|Make life trickier for the Rogue Team; with a mix of Rogues and Colored Teams, the Rogues have more targets. This should also change the effect of the Masquerade flag - perhaps your tank is invisible to Rogues (like Cloaking)?
|(Unknown)
|
|NickGrim
|-
|A server option to make deaths not affect your score unless they were self-inflicted/team (the method used by many online games). This would encourage more aggressive play, because it's worth going out and blasting. As it is, you've got a very good chance by just phantoming/OOing out of the way and keeping you score at zero to stay in the top three places! It would also help fix the rather unfair situation of spawning just below a building on which someone is GM-camping...there's pretty much no way to escape, so you lose a point.
|(Unknown)
|
|LionsPhil
|-
|Don't show invidual score in CTF games. This might help teamplay as it reduces the incentive to run around as if it would be FFA.
|(Unknown)
|
|abli
|-
|Give points to the player how captures flag in CTF. (Say, around 4 or so) After all, it is often a bigger job than killing someone.
|(Unknown)
|
|abli
|-
|Ducati/Freestyle "Roles" mode: Make a game mode where players are presented with a list of flag choices (limitable to a few roles, if wanted) at respawn or connect time, and are forced to use this flag for the remainder of their connection/tank life. This would be really useful in the case of stealth vs. seer, where you could choose to be stealth or seer, but couldn't switch between them. Another idea would be high speed vs. quick turn. Or steamroller vs. machine gun... Team play would have the interesting effect of people banding together and people with each role on the team. Especially in stealth vs. seer, where a seer team member could warn the team about enemies! There would be no team flags/bases.
|(Unknown)
|
|YHARG
|-
|New game called tag were someone is it and they shoot someone else and there it and ect.
|(Unknown)
|
|Supermatthew
|-
|Also a new game called "Hide and seek" were everyone is clocked(think thats it, were you don't see them on radar) except one who is it. he needs to find someone and shoot them then hese cloked and who was shot is not. Also when someone is shot there sent back to Ground zero( 0X, 0Y, 0Z ) so they can't shoot who ever just shot them.
|(Unknown)
|
|Supermatthew
|-
|}
</div>

== Maps, Mapping, and BZW ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="10%"|Status
!width="40%"|Commentary
!width="10%"|Submitter
|-
|Materials that don't allow OO and PZ to go through
|Idea
|Would be nice for multilevel worlds made with the new ability to have objects above the ground. (Sounds awesome! TD-Linux 17:41, 12 March 2007 (EDT))
|(Unknown)
|-
|Differently-shaped teleporters (circles, triangles, etc.)
|Idea
|probably low priority
|MORPH
|-
|360 degree teleports - hit a spot on the ground or in the air from any direction and you teleport
|
|Idea
|MORPH
|-
|Configurable random teleporters - teleports to a different location every time
|Idea
|Idea is a bit vague... randomized teles are implemented if you use multiple links. Is this what is meant by this suggestion? -L4m3r
|MORPH
|-
|Triggers in levels
|(Unknown)
|Triggers for what? unless you're talking about AI, this could most likely be handled with a server plug-in. [[User:L4m3r|L4m3r]]
|Dragonstar
|-
|wraparound world - radar remains centered on your current position. Internally, objects leaving the north border reappear to the south, but from the user's radar / visible perspective, you just see to the horizon. I believe this is how the original Battlezone worked. There are some implications: laser would need a range limit.
|(Unknown)
|
|nsayer
|-
|}
</div>

== Server Options, Administration, Plug-ins, and the Plug-in API ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="10%"|Status
!width="40%"|Commentary
!width="10%"|Submitter
|-
|Ability to configure server to turn somethings off or on depending on number of players - for instance, turn off ricochet after a certain number of players are connected, turn off GM & laser if a certain number of players aren't playing (GM & Laser with 2 players is kinda ridiculous)
|Idea
|
|MORPH
|-
|Allow custom-made weapons with a Object-Oriented scripting language (sorta like Liero AI uses: http://helios.et.put.poznan.pl/~sskowron/liero/index.html )
|(Unknown)
|
|Dragonstar
|-
|Preset world weapons that can be fired manually by admins from within BzFlag.
|(Unknown)
|
|Dogbert
|-
|}
</div>

== Graphics & Sound ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="10%"|Status
!width="40%"|Commentary
!width="10%"|Submitter
|-
|Sounds of tanks moving.
|(Unknown)
|
|iPod
|-
|Have different tank death scenes for the dying tank point of view. I realize there is some time needed for one to die and respawn, but the jumping effect one sees when killed irritates me to no end! I'd be happier if all faded to black or white or orange and had text across the screen saying ""respawning... please wait"" :) Also, when killed and your tank was moving toward a building, it just falls right thru it until it hits the ground.. wrong physics there! Splatter or tumble or shatter or something :)
|(Unknown)
|
|Robi
|-
|Custom color schemes for rogue players. The turret and body components can be chosen to be one of a predefined set of colors (e.g. red, yellow, black, white, blue, green, purple...). The game prohibits choosing a color scheme that matches a team scheme (e.g. red turret with red body) and the limited set stops someone choosing a shade which is nearly a team color (e.g. 0xFE0000 instead of 0xFF0000) (and also save texture memory, I think).
|(Unknown)
|
|LionsPhil
|-
|Allow a small decal on the back of the top of the tank. (think Half-Life's customizable spraypaint). Possibly also apply it to any held flag?
|(Unknown)
|
|LionsPhil
|-
|wireframe mode! man, this would make the game ten times cooler for nostalgia
|(Unknown)
|
|rjbs
|-
|I'd like to see something more interesting done with the sky... maybe there could be a little ufo (easter egg) that would fly around occasionally? Tux on a ufo! ;)
|(Unknown)
|
|YHARG
|-
|Flag decals: Each flag would have a little icon/decal showing it's type ONLY when held by a player. It's kind of nice to be able to surprise people with an undercover shockwave, but doesn't make sense to have to right click (identify) or check the user list to see what flag someone has.
|(Unknown)
|
|YHARG
|-
|Background music! : (This can be done with an external media player so it shouldn't be the heighest priority, It would be nice to be able to control your music from within BzFlag)
|(Unknown)
|
|YHARG
|-
|}
</div>

== List Server and Other Global Services ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="10%"|Status
!width="40%"|Commentary
!width="10%"|Submitter
|-
|Multiple list servers, in case bzflag.org goes down (as it happened around feb. 15. 2004)
|(Unknown)
|
|abli
|-
|}
</div>

[[Category:Development]]

Ideas

2007-03-25T22:02:00Z

L4m3r:

{{Old}}
Feel free to make changes and updates to this page whenever possible. If you have any questions, feel free to [[Getting Help|ask for help]]. If you wish to make major changes to this page (i.e. remove large amounts of old ideas), please warn us ahead of time.

<b>NOTE: Work is in progress on this page. I'm converting to to a tabular format, and will then clean up and sort the ideas into categories. Please stand by. -L4m3r</b>

NOTE: These are just possiblilities. We won't be implementing everything here.<br>
NOTE: Flag ideas should be placed on [[Flag Ideas]]. Any other ideas can be placed here.

Status may include personal comments by developers.

== Adding ideas ==
* All ideas should be categorized and should be prefixed with a *.
* Sign your idea with four tildes: <nowiki>~~~~</nowiki>
* Describe in full and make sense!

== General/Gameplay ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="10%"|Status
!width="40%"|Commentary
!width="10%"|Submitter
|-
|Add support for 5 (or more) button mice
|Great Idea
|Old?
|(Unknown)
|-
|Better physics
|In progress
|Planning, some changes in CVS. (Old?)
|Unknown
|-
|SELF-DESTRUCT BLAST RADIUS: Self Destruct (delete key) should have a blast radius similar to Shock Wave, perhaps larger. If you get shot during the self-destruct count down, that should also trigger the same blast. If I gotta go, I want to take someone with me.
|(Unknown)
|
|BearRiver
|-
|3-second (or however long) 'invulnerability' for incoming tanks - but they can't shoot
|Idea
|I could see this backfiring... your spawn attracts opponents to come, wait, and blast you when you lose invincibility. -L4m3r
|MORPH
|-
|Ability to turn off ricochet for laser flag but allow ricochet for bullets... or let them bounce only n times.. OR implement mirror buildings/walls. Should go for some interesting self-kills when combined with the no-radar/bullet bounce
|Idea
|
|MORPH
|-
|Smart LockOn for GM - won't lock on to your teammates (configurable in server)
|Idea
|(M. Jetleb -> I don't like this idea, there should be at least *some* risks to using this weapon. Personally, I think there should be more (not fewer) risks to holding this weapon; I'd like to see the thing overheat and explode (killing the holder) if it's fired too often in a short period of time)
|MORPH
|-
|Small jumps
|Idea
|
|MORPH
|-
|Server option for genocide flag - if you're killed while you have it, your team dies :^)
|Idea
|Feasible with a plug-in, too. -L4m3r
|MORPH
|-
|for broadband or LAN connections - voice chat for teams
|Idea
|I really think that you can do this with another service; I'm not sure if being part of BZFlag would be a good idea due to size and bandwidth issues.
|MORPH
|-
|Tank avatars (uploadable tank images) - have to think about shapes, though - someone could make a 1x1x1 pixel tank - that would suck - or a tank that looks like a building or pyramid. Clients don't have to accept downloading of avators (just view other tanks in default mode). Or just s-e-l-e-c-t from a certain number of predefined avatars that could come with the bzflag distribution. Or client provides a URL to download their avatar (saves server bandwidth).
|Idea
|Might not be implemented. Requires discussion; we may want to consider making the computer force a minimum size or something similar. *How about uploadable flag graphics?
|MORPH
|-
|'Kamikaze' option for players - can take someone out by suicide
|Idea
|Server option if implemented. Implemented with a plugin by Theme97
|MORPH
|-
|Server option: everyone is radar-stealthed by default unless you get a 'radar' flag. You can still see all buildings, pyramids, teleports, and arena walls, though.
|Good idea
|Make them use their window. ;)(M. Jetleb -> Given the fairly narrow field of view out the window and the time it takes to turn a tank all the way around for a look-see, I think this could be frustrating. How about everyone starts out with minimum range radar instead and gets longer ranges with an appropriate flag?)
|MORPH
|-
|Option for above: if you pick up GM or Laser, you're visible on radar to everyone whether they've got a radar flag or not
|Good idea
|
|MORPH
|-
|Selectable 'ricochet' fire - hold down shift key or something and your bullets won't ricochet
|Idea
|
|MORPH
|-
|Server option - tanks only have a certain number of times they can jump (gets reset when you get killed)
|Idea
|
|MORPH
|-
|Multiple-shields (server option for shield flags, or can be random - can get hit x number of times)
|Idea
|This is pretty much moot now. It's been shot down by the devs at least once, and a similar effect can be achieved by setting _shieldFlight to a very small number. This effectively provides as many hits as _maxFlagGrabs. [[User:L4m3r|L4m3r]]
|MORPH
|-
|Configurable 'radarless' and/or 'blind' zones in the arena - can't see what's in there on radar or via visuals
|Idea
|
|MORPH
|-
|Tank collisions - why can tanks drive through each other? Weird.
|Good Idea
|Lag could be a big problem here. If implemented, it must be impossible for two tanks to get stuck to each other. [[User:L4m3r|L4m3r]]
|MORPH
|-
|When tanks collide - great opportunity to implement tank damage concept, especially if one of them is moving especially fast, or has momentum flag, etc. Can push a tank off a building if your pushing them from their side.
|Idea
|Tank damage won't happen, but the kinetics could be neat, especially for mid-air collisions. It would certainly make "jump dancing" more interesting. [[User:L4m3r|L4m3r]]
|Morph
|-
|If a tank explodes right next to another tank, the other tank can be destroyed or get damaged
|Idea
|Somewhat implemented with the [[ShockWaveDeath]] plug-in. It would probably not be too hard to implement something similar without shockwaves. [[User:L4m3r|L4m3r]]
|MORPH
|-
|Skins or views- In-tank mode, bumper mode, out-of-cab mode, chase mode.
|(Unknown)
|
|MORPH
|-
|Weapon extension packs.
|(Unknown)
|Huh? Explain, please. [[User:L4m3r|L4m3r]]
|iPod
|-
|The ability to choose tanks, but they all die at one shot. maybe the jump height, speed, turn speed, acceleration, size can be preset.
|(Unknown)
|
|iPod
|-
|Option to choose different kinds of tanks. Different tanks could be weighted with different strengths and weaknesses. (almost like having a default flag). Would also need some form of health/damage status measurement, not just single hits. For example, there could be a larger, heavily armored tank that has powerful weapons, but moves slowly, versus a small, light, fast tank which is difficult to hit, but very low armor to protect from hits.
|(Unknown)
|
|Cue
|-
|What about a radar that only covers visible areas (don't passing through buildings/pyramids) ? This would leads to more placement tactics).
|(Unknown)
|
|K<nowiki>'</nowiki>limero
|-
|Always random respawn. Currently in CTF games first respawn is at own base. This can be abused by leaving and rejoining to get near base. This leave/rejoing trick is considered to be a mild form of cheating by many. Always random respawn would make it useless.
|(Unknown)
|
|abli
|-
|multiple (3?) jump stengths mini, normal, max...just the thing to confuse the opponents that expect one and you're off doing the other.
|(Unknown)
|
|kitchen
|-
|Anti camping. The ability to add "no camping zones" to areas of a map or to the entire map. Campers would be messaged that they're in a no camping zone, better start moving and have a prescribe number of seconds to move away or die. If a player returns to the same NCZ (no camping zone) and receives x warnings then he's disconnected. NCZs could be marked by a different color shade from a "normal" spot and could be exempt to a single team (like at their flag base). It's just a rough idea.
|(Unknown)
|
|pherris
|-
|Shield Flag Changes: Give Shield flag a radius, and draw it like a moving less opaque blue shockwave. Any tanks inside the shield radius would be protected, until the shield got hit a certain number of times.
|(Unknown)
|
|YHARG
|-
|At our company, we instituted a voluntary policy of dropping flags after 1 kill. Prevents slaughters and keeps things rolling more. It'd be great to be able to have the game do this for us, plus I'd love to see it turned on at external sites.
|(Unknown)
|
|TomMatelich
|-
|Server option: default powers -- flag(s) that everyone in the game automatically has (this wouldn't count as holding a flag). For example, the current Jumping option would == including Jumping as a default power.
|(Unknown)
|
|NebNamwen
|}
</div>

== UI ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="10%"|Status
!width="40%"|Commentary
!width="10%"|Submitter
|-
|Make option to show previous players list
|Idea
|
|(Unknown)
|-
|Make ALL server options available from the menus
|Idea
|There are a LOT of server options, and this could add quite a bit of clutter. If you need more than a basic game, you should probably learn to start BZFS from the command line anyway. -L4m3r
|MORPH
|-
|Separate windows for player messages & server messages
|Good idea.
|
|MORPH
|-
|Message log
|Good idea.
|
|MORPH
|-
|Send message to everyone 'but' specified player (crosses team boundaries, or not)
|Idea
|Hmm. Everybody BUT a specified player? [M. Jetleb -> as in: "Let's all get the GM guy" without the GM guy knowing he's facing a co-ordinated attack - I like this idea)
|MORPH
|-
|The ability to see what the world is like before connecting to the server.
|(Unknown)
|
|iPod
|-
|Multi-monitor support (i.e., radar on one screen, window on another, chat/event log on a third)
|(Unknown)
|
|bhtooefr
|-
|Make a part in bzflag to put up a real server. 1st screen has the flags you want, next page is to find the MAP file that you created on your hard drive, next page pick if you want jumping etc.
|(Unknown)
|
|Colin
|-
|}
</div>

== Technical ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="10%"|Status
!width="40%"|Commentary
!width="10%"|Submitter
|-
|Better network handling
|In progress
|Old?
|(Unknown)
|-
|Better robot AI
|Idea
|Don't know if players would like it or not in multiplayer game. Pluggable or scriptable robot AI , maybe? - Code must be restructured first (Server side bots are coming! [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT))
|(Unknown)
|-
|Better positioning of tanks
|Idea
|BZFlag already does this, but the algorithm is bad. Needs work.
|MORPH
|-
|Serious multithreaded design - shouldn't lock up interface while looking for servers, or doing anything else. This program is way-unstable on Windows
|In Progress
|We're working on these problems; many complaints are due to people still using old servers/clients.
|MORPH
|-
|Some type of BZFlag GUID* to ban players who cheat - won't accept players who disable their GUID, etc.

<nowiki>*</nowiki>Global Unique Identifier, sort of like an IP addrss, but permanent. Usually a number. Problem occurs when you lose your GUID (have to reformat your HD, etc. How do you keep someone from hacking their GUID, or setting up a modified BZFlag server for identity theft, etc.
|(Unknown)
|I doubt this is even possible, let alone practical. What about people who play from more than one location? And, because this is an open-source game, it would probably be cracked in minutes. Any verification can be spoofed, or at least altered. there is no foolproof way to permanently ban someone. -L4m3r
|MORPH
|-
|To prevent cheating - the server determines what flags & abilities each tank has (possible?)
|Idea
|Seriously being considered. This would also have the advantage of allowing different versions of clients and servers to work together. Yes, it's possible, but this type of change will mean a change in the network protocols. Being worked on for 2.2
|MORPH
|-
|BZFlag for mac in seperate data and application files.
|(Unknown)
|
|iPod
|-
|J2ME client (allows one to play on a cell phone), would use radar
|(Unknown)
|
|bhtooefr
|-
|Special 'open source' BZFlag version (server and client) which is guaranteed to be compatible with all other BZFlag versions.
|(Unknown)
|BZFlag is already open-source, and making a universally-compatible client is not even remotely practical. Incompatibility is part of why the game breaks off new versions in the first place. [[User:L4m3r|L4m3r]]
|Orca
|-
|}
</div>

== Game Modes, Team Play, and Scoring ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="10%"|Status
!width="40%"|Commentary
!width="40%"|Submitter
|-
|Tounament mode
|Idea
|Great Idea?
|(Unknown)
|-
|When you shoot someone on your own team, instead of both of you blowing up, neither is destroyed, and their score goes up one, while your's goes down one. This would make teamkilling impossible and greatly discourage traitors as well.
|Idea
|But then couldn't cheaters spawn two clients and ramp up their scores by teamkilling their other login? --YHARG
|Trigger Happy Nerd
|-
|A new gameplay mode- Takes two to tank. One to control the (rotating) turret, the other drives. KIA switches positions. "Teamplay" but all in one tank.
|(Unknown)
|I see serious lag issues with this... How does Halo do it? ;) -L4m3r
|MORPH
|-
|Turret mode, If enabled by the server (Can be manditory with automatic grouping). One user drives and the other shoots, Turret mode tanks get double points (But onyl take one from the target). lost double points if killed. Have double ammo, And controllable speed (Max = _tankSpeed * 2 Min = _tankSpeed). Plus it takes 2 shots to kill a turret mode tank. Points gained and lost by turret tanks are divided evenly between the users, Unless the server is all turret mode, in h which case two users are displayed as one.
|(Unknown)
|
|Dogbert
|-
|Ability for a team to vote to 'banish' someone from their team
|Idea
|Possibly unfair to newer players. [[User:L4m3r|L4m3r]]
|MORPH
|-
|There should be a game of cops and robbers. The teams can change after about 10 mins or so.
|(Unknown)
|
|iPod
|-
|A special FFA Game mode "Team by Flags". This means, same Flag = same Team, so if there is a Tank with Rapid fire, and you pick up Rapid fire, you are automatically handled as Team member (this means, killing the other Tank with Rapid fire will be handled the same way as when killing a team member). YHARG: Funky idea: what about a game mode where teams shared flag abilities? Like, each player on a team's flag applies to the whole team. This could make for some interesting combos...
|(Unknown)
|
|Agonizer
|-
|Make life trickier for the Rogue Team; with a mix of Rogues and Colored Teams, the Rogues have more targets. This should also change the effect of the Masquerade flag - perhaps your tank is invisible to Rogues (like Cloaking)?
|(Unknown)
|
|NickGrim
|-
|A server option to make deaths not affect your score unless they were self-inflicted/team (the method used by many online games). This would encourage more aggressive play, because it's worth going out and blasting. As it is, you've got a very good chance by just phantoming/OOing out of the way and keeping you score at zero to stay in the top three places! It would also help fix the rather unfair situation of spawning just below a building on which someone is GM-camping...there's pretty much no way to escape, so you lose a point.
|(Unknown)
|
|LionsPhil
|-
|Don't show invidual score in CTF games. This might help teamplay as it reduces the incentive to run around as if it would be FFA.
|(Unknown)
|
|abli
|-
|Give points to the player how captures flag in CTF. (Say, around 4 or so) After all, it is often a bigger job than killing someone.
|(Unknown)
|
|abli
|-
|Ducati/Freestyle "Roles" mode: Make a game mode where players are presented with a list of flag choices (limitable to a few roles, if wanted) at respawn or connect time, and are forced to use this flag for the remainder of their connection/tank life. This would be really useful in the case of stealth vs. seer, where you could choose to be stealth or seer, but couldn't switch between them. Another idea would be high speed vs. quick turn. Or steamroller vs. machine gun... Team play would have the interesting effect of people banding together and people with each role on the team. Especially in stealth vs. seer, where a seer team member could warn the team about enemies! There would be no team flags/bases.
|(Unknown)
|
|YHARG
|-
|New game called tag were someone is it and they shoot someone else and there it and ect.
|(Unknown)
|
|Supermatthew
|-
|Also a new game called "Hide and seek" were everyone is clocked(think thats it, were you don't see them on radar) except one who is it. he needs to find someone and shoot them then hese cloked and who was shot is not. Also when someone is shot there sent back to Ground zero( 0X, 0Y, 0Z ) so they can't shoot who ever just shot them.
|(Unknown)
|
|Supermatthew
|-
|}
</div>

== Maps, Mapping, and BZW ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="10%"|Status
!width="40%"|Commentary
!width="10%"|Submitter
|-
|Materials that don't allow OO and PZ to go through
|Idea
|Would be nice for multilevel worlds made with the new ability to have objects above the ground. (Sounds awesome! TD-Linux 17:41, 12 March 2007 (EDT))
|(Unknown)
|-
|Differently-shaped teleporters (circles, triangles, etc.)
|Idea
|probably low priority
|MORPH
|-
|360 degree teleports - hit a spot on the ground or in the air from any direction and you teleport
|
|Idea
|MORPH
|-
|Configurable random teleporters - teleports to a different location every time
|Idea
|Idea is a bit vague... randomized teles are implemented if you use multiple links. Is this what is meant by this suggestion? -L4m3r
|MORPH
|-
|Triggers in levels
|(Unknown)
|Triggers for what? unless you're talking about AI, this could most likely be handled with a server plug-in. [[User:L4m3r|L4m3r]]
|Dragonstar
|-
|wraparound world - radar remains centered on your current position. Internally, objects leaving the north border reappear to the south, but from the user's radar / visible perspective, you just see to the horizon. I believe this is how the original Battlezone worked. There are some implications: laser would need a range limit.
|(Unknown)
|
|nsayer
|-
|}
</div>

== Server Options, Administration, Plug-ins, and the Plug-in API ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="10%"|Status
!width="40%"|Commentary
!width="10%"|Submitter
|-
|Ability to configure server to turn somethings off or on depending on number of players - for instance, turn off ricochet after a certain number of players are connected, turn off GM & laser if a certain number of players aren't playing (GM & Laser with 2 players is kinda ridiculous)
|Idea
|
|MORPH
|-
|Allow custom-made weapons with a Object-Oriented scripting language (sorta like Liero AI uses: http://helios.et.put.poznan.pl/~sskowron/liero/index.html )
|(Unknown)
|
|Dragonstar
|-
|Preset world weapons that can be fired manually by admins from within BzFlag.
|(Unknown)
|
|Dogbert
|-
|}
</div>

== Graphics & Sound ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="10%"|Status
!width="40%"|Commentary
!width="10%"|Submitter
|-
|Sounds of tanks moving.
|(Unknown)
|
|iPod
|-
|Have different tank death scenes for the dying tank point of view. I realize there is some time needed for one to die and respawn, but the jumping effect one sees when killed irritates me to no end! I'd be happier if all faded to black or white or orange and had text across the screen saying ""respawning... please wait"" :) Also, when killed and your tank was moving toward a building, it just falls right thru it until it hits the ground.. wrong physics there! Splatter or tumble or shatter or something :)
|(Unknown)
|
|Robi
|-
|Custom color schemes for rogue players. The turret and body components can be chosen to be one of a predefined set of colors (e.g. red, yellow, black, white, blue, green, purple...). The game prohibits choosing a color scheme that matches a team scheme (e.g. red turret with red body) and the limited set stops someone choosing a shade which is nearly a team color (e.g. 0xFE0000 instead of 0xFF0000) (and also save texture memory, I think).
|(Unknown)
|
|LionsPhil
|-
|Allow a small decal on the back of the top of the tank. (think Half-Life's customizable spraypaint). Possibly also apply it to any held flag?
|(Unknown)
|
|LionsPhil
|-
|wireframe mode! man, this would make the game ten times cooler for nostalgia
|(Unknown)
|
|rjbs
|-
|I'd like to see something more interesting done with the sky... maybe there could be a little ufo (easter egg) that would fly around occasionally? Tux on a ufo! ;)
|(Unknown)
|
|YHARG
|-
|Flag decals: Each flag would have a little icon/decal showing it's type ONLY when held by a player. It's kind of nice to be able to surprise people with an undercover shockwave, but doesn't make sense to have to right click (identify) or check the user list to see what flag someone has.
|(Unknown)
|
|YHARG
|-
|Background music! : (This can be done with an external media player so it shouldn't be the heighest priority, It would be nice to be able to control your music from within BzFlag)
|(Unknown)
|
|YHARG
|-
|}
</div>

== List Server and Other Global Services ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!width="40%"|Idea
!width="10%"|Status
!width="40%"|Commentary
!width="10%"|Submitter
|-
|Multiple list servers, in case bzflag.org goes down (as it happened around feb. 15. 2004)
|(Unknown)
|
|abli
|-
|}
</div>

[[Category:Development]]

Rejected Ideas

2007-03-25T22:01:22Z

L4m3r:

While suggestions and ideas are always welcome, there are a few things that the BZFlag developers have decided not to include in the game. The reasons vary, but most often it's simply a design decision.

{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!Rejected Idea
!Reasoning
|-
|Ability to carry multiple flags at once
|This sort of concept would have extreme balance issues. What happens if someone grabbed ST and CL at the same time? they'd be undetectable. Furthermore, some flags simply can't work together- for instance, L and GM.
|-
|Rotating tank turrets
|Controlling a rotating turret would be a nightmare, and would add too much complexity to the game. However, this is only true for single-player control. The concept of two-player tanks (one driver and one gunner) has not been rejected.
|-
|Driving up slopes/pyramids, tilting turrets
|The game developers have decided that tanks should remain level (relative to the ground plane). In other words, it's a design decision.
|-
|Land Mines
|There are two equally-undesirable approaches to land mines:
*Mines that are visible: This would be a useless addition to the game because players could easily drive around the mines.
*Mines that are not visible: Too frustrating. Dying at random without being shot is no fun.
|-
|Tank damage, multiple-hit kills, tank health
|BZFlag is a simple game, and one-hit kills are part of that simplicity. Having tanks that require more than one hit to die would damage this, and ruin the fast-paced nature of the game.
|-
|Moving world objects, elevators, opening/closing doors, destroyable world objects
|The developers have decided that the game world in BZFlag should remain static. Moving objects complicate the game, and they introduce major lag and synchronization issues.

Note that there is currently code in the game to make objects move or rotate in a circular path. However, these objects are passable- shots and tanks go through them. In other words, they're decorative and do not affect gameplay.

[[Physics|Physics drivers]] can also be used to make workable conveyors and elevators without moving objects.
|}

Rejected Ideas

2007-03-25T19:40:47Z

L4m3r: Added non-static world items

Rejected Ideas

2007-03-25T06:47:23Z

L4m3r:

Rejected Ideas

2007-03-25T06:46:19Z

L4m3r: added tank damage item

Talk:Ideas

2007-03-22T08:57:57Z

L4m3r:

Should ideas that have already be implemented be deleted? This list is getting kinda long. [[User:TD-Linux|TD-Linux]] 21:29, 18 March 2007 (EDT) (date wrong, sorry)
:Yes, if they have actually been implemented, they should be removed. We might also think about archiving this page occasionally. Also, [[BZFlagWiki:Sign your posts on talk pages|please sign your comments on talk pages]]. [[User:DTRemenak|DTRemenak]] 18:17, 13 March 2007 (EDT)

:My other concern is how do we manage these ideas? If they get archived, should some stay here (good ones) and if so what would be the criteria? This page makes me kind of uncomfortable from a management position? I'm not sure a wiki is the best place to gather information like this. [[User:DonnyBaker|DonnyBaker]] 05:44, 14 March 2007 (EDT)

:At least an unprotected one. If it was protected and had "real" approved ideas, it would be different. [[User:DonnyBaker|DonnyBaker]] 13:05, 14 March 2007 (EDT)

::There's no point in having a protected ideas page, we have the SF.net trackers, the enhancements forum on bzbb, and so on for that. I'm not quite sure what the expected usage of this page was when it was created on the old wiki, and the only real use I see for it now is that it allows unstructured collaborative editing (which apparently isn't used, since everyone seems to sign their ideas...). [[User:DTRemenak|DTRemenak]] 13:12, 14 March 2007 (EDT)

I'm working on conversion to a table, and afterward I will remove old ideas and sort them into categories. Perhaps a page dedicated to "rejected ideas" would be a good idea. -L4m3r
:The table is great! Mabye we should also port over the color-coding system from [[Flag Ideas]]. [[User:TD-Linux|TD-Linux]] 21:29, 18 March 2007 (EDT)
::Yes, I will most likely do that. I'm going to add a date column too (and I might do that to the flag ideas page also). -L4m3r

Ideas

2007-03-20T08:20:33Z

L4m3r: more work, man this page is long

{{Old}}
Feel free to make changes and updates to this page whenever possible. If you have any questions, feel free to [[Getting Help|ask for help]]. If you wish to make major changes to this page (i.e. remove large amounts of old ideas), please warn us ahead of time.

<b>NOTE: Work is in progress on this page. I'm converting to to a tabular format, and will then clean up and sort the ideas into categories. Please stand by. -L4m3r</b>

NOTE: These are just possiblilities. We won't be implementing everything here.<br>
NOTE: Flag ideas should be placed on [[Flag Ideas]]. Any other ideas can be placed here.

Status may include personal comments by developers.

== Adding ideas ==
* All ideas should be categorized and should be prefixed with a *.
* Sign your idea with four tildes: <nowiki>~~~~</nowiki>
* Make sense!

== General/Gameplay ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!Idea
!Status
!Commentary
!Submitter
|-
|Add support for 5 (or more) button mice
|Great Idea
|Old?
|(Unknown)
|-
|Better physics
|In progress
|Planning, some changes in CVS. (Old?)
|Unknown
|-
|SELF-DESTRUCT BLAST RADIUS: Self Destruct (delete key) should have a blast radius similar to Shock Wave, perhaps larger. If you get shot during the self-destruct count down, that should also trigger the same blast. If I gotta go, I want to take someone with me.
|(Unknown)
|
|BearRiver
|-
|3-second (or however long) 'invulnerability' for incoming tanks - but they can't shoot
|Idea
|I could see this backfiring... your spawn attracts opponents to come, wait, and blast you when you lose invincibility. -L4m3r
|MORPH
|-
|Ability to turn off ricochet for laser flag but allow ricochet for bullets... or let them bounce only n times.. OR implement mirror buildings/walls. Should go for some interesting self-kills when combined with the no-radar/bullet bounce
|Idea
|
|MORPH
|-
|Smart LockOn for GM - won't lock on to your teammates (configurable in server)
|Idea
|(M. Jetleb -> I don't like this idea, there should be at least *some* risks to using this weapon. Personally, I think there should be more (not fewer) risks to holding this weapon; I'd like to see the thing overheat and explode (killing the holder) if it's fired too often in a short period of time)
|MORPH
|-
|Small jumps
|Idea
|
|MORPH
|-
|Server option for genocide flag - if you're killed while you have it, your team dies :^)
|Idea
|Feasible with a plug-in, too. -L4m3r
|MORPH
|-
|for broadband or LAN connections - voice chat for teams
|Idea
|I really think that you can do this with another service; I'm not sure if being part of BZFlag would be a good idea due to size and bandwidth issues.
|MORPH
|-
|Tank avatars (uploadable tank images) - have to think about shapes, though - someone could make a 1x1x1 pixel tank - that would suck - or a tank that looks like a building or pyramid. Clients don't have to accept downloading of avators (just view other tanks in default mode). Or just s-e-l-e-c-t from a certain number of predefined avatars that could come with the bzflag distribution. Or client provides a URL to download their avatar (saves server bandwidth).
|Idea
|Might not be implemented. Requires discussion; we may want to consider making the computer force a minimum size or something similar. *How about uploadable flag graphics?
|MORPH
|-
|}
</div>

== UI ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!Idea
!Status
!Commentary
!Submitter
|-
|Make option to show previous players list
|Idea
|
|(Unknown)
|-
|Make ALL server options available from the menus
|Idea
|There are a LOT of server options, and this could add quite a bit of clutter. If you need more than a basic game, you should probably learn to start BZFS from the command line anyway. -L4m3r
|MORPH
|-
|Separate windows for player messages & server messages
|Good idea.
|
|MORPH
|-
|Message log
|Good idea.
|
|MORPH
|-
|}
</div>

== Technical ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!Idea
!Status
!Commentary
!Submitter
|-
|Better network handling
|In progress
|Old?
|(Unknown)
|-
|Better robot AI
|Idea
|Don't know if players would like it or not in multiplayer game. Pluggable or scriptable robot AI , maybe? - Code must be restructured first (Server side bots are coming! [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT))
|(Unknown)
|-
|Better positioning of tanks
|Idea
|BZFlag already does this, but the algorithm is bad. Needs work.
|MORPH
|-
|Serious multithreaded design - shouldn't lock up interface while looking for servers, or doing anything else. This program is way-unstable on Windows
|In Progress
|We're working on these problems; many complaints are due to people still using old servers/clients.
|MORPH
|-
|Some type of BZFlag GUID* to ban players who cheat - won't accept players who disable their GUID, etc.

<nowiki>*</nowiki>Global Unique Identifier, sort of like an IP addrss, but permanent. Usually a number. Problem occurs when you lose your GUID (have to reformat your HD, etc. How do you keep someone from hacking their GUID, or setting up a modified BZFlag server for identity theft, etc.
|(Unknown)
|I doubt this is even possible, let alone practical. What about people who play from more than one location? And, because this is an open-source game, it would probably be cracked in minutes. Any verification can be spoofed, or at least altered. there is no foolproof way to permanently ban someone. -L4m3r
|MORPH
|-
|To prevent cheating - the server determines what flags & abilities each tank has (possible?)
|Idea
|Seriously being considered. This would also have the advantage of allowing different versions of clients and servers to work together. Yes, it's possible, but this type of change will mean a change in the network protocols. Being worked on for 2.2
|MORPH
|-
|}
</div>

== Game Modes, Team Play, and Scoring ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!Idea
!Status
!Commentary
!Submitter
|-
|Tounament mode
|Idea
|Great Idea?
|(Unknown)
|-
|When you shoot someone on your own team, instead of both of you blowing up, neither is destroyed, and their score goes up one, while your's goes down one. This would make teamkilling impossible and greatly discourage traitors as well.
|Trigger Happy Nerd
|But then couldn't cheaters spawn two clients and ramp up their scores by teamkilling their other login? --YHARG
|-
|A new gameplay mode- Takes two to tank. One to control the (rotating) turret, the other drives. KIA switches positions. "Teamplay" but all in one tank.
|(Unknown)
|I see serious lag issues with this... How does Halo do it? ;) -L4m3r
|MORPH
|-
|}
</div>

== Maps, Mapping, and BZW ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!Idea
!Status
!Commentary
!Submitter
|-
|Materials that don't allow OO and PZ to go through
|Idea
|Would be nice for multilevel worlds made with the new ability to have objects above the ground. (Sounds awesome! TD-Linux 17:41, 12 March 2007 (EDT))
|(Unknown)
|-
|Differently-shaped teleporters (circles, triangles, etc.)
|Idea
|probably low priority
|MORPH
|-
|360 degree teleports - hit a spot on the ground or in the air from any direction and you teleport
|
|Idea
|MORPH
|-
|Configurable random teleporters - teleports to a different location every time
|Idea
|Idea is a bit vague... randomized teles are implemented if you use multiple links. Is this what is meant by this suggestion? -L4m3r
|MORPH
|-
|}
</div>

== Server Options, Administration, Plug-ins, and the Plug-in API ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!Idea
!Status
!Commentary
!Submitter
|-
|Ability to configure server to turn somethings off or on depending on number of players - for instance, turn off ricochet after a certain number of players are connected, turn off GM & laser if a certain number of players aren't playing (GM & Laser with 2 players is kinda ridiculous)
|Idea
|
|MORPH
|-
|}
</div>

== Ideas include: ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!Idea
!Submitter
!Status/approval
|-
|Concept of a tank that can take damage without being destroyed immediately - slows down, takes a hit in a tread and turns slowly in whatever direction, etc.
|MORPH
|Good idea, but must be optional (server option). Might be rejected, since BZFlag is, by nature, a fast paced game. *Loses ability to shoot, runs and grabs a restore flag?
|-
|'Kamikaze' option for players - can take someone out by suicide
|MORPH
|Idea. Server option if implemented. Implemented with a plugin by Theme97
|-
|Server option: everyone is radar-stealthed by default unless you get a 'radar' flag. You can still see all buildings, pyramids, teleports, and arena walls, though.
|MORPH
|Good idea. Make them use their window. ;)(M. Jetleb -> Given the fairly narrow field of view out the window and the time it takes to turn a tank all the way around for a look-see, I think this could be frustrating. How about everyone starts out with minimum range radar instead and gets longer ranges with an appropriate flag?)
|-
|Option for above: if you pick up GM or Laser, you're visible on radar to everyone whether they've got a radar flag or not
|MORPH
|Good idea
|-
|Selectable 'ricochet' fire - hold down shift key or something and your bullets won't ricochet
|MORPH
|Idea.
|-
|Server option - tanks only have a certain number of times they can jump (gets reset when you get killed)
|MORPH
|Idea.
|-
|Multiple-shields (server option for shield flags, or can be random - can get hit x number of times)
|MORPH
|Idea
|-
|Ability to damage or destroy buildings/pyramids/teleporters
|MORPH
|Idea (M. Jetleb - probably a good idea for timed games, where the building can be reset after a reasonable amount of time, but can you imagine what the field would look like for a perpetual game that's been running for days? There has to be some way to reset this. Also what happens if someone shoots the bottom out of a building? Does the building collapse or just remain suspended? This could get complicated.)
|-
|Server config to make bullets NOT go through teleporters
|MORPH
|Idea
|-
|SandTraps - tank gets stuck there
|MORPH
|Idea (aren't there enough incredibly annoying ways for tanks to get stuck on pyramids etc. already? --pediddle)
|-
|Configurable 'radarless' and/or 'blind' zones in the arena - can't see what's in there on radar or via visuals
|MORPH
|Idea
|-
|'Fog' area in arena - impairs use of laser
|MORPH
|Idea
|-
|Ability for a team to vote to 'banish' someone from their team
|MORPH
|Idea
|-
|Send message to everyone 'but' specified player (crosses team boundaries, or not)
|MORPH
|Idea. Hmm. Everybody BUT a specified player? [M. Jetleb -> as in: "Let's all get the GM guy" without the GM guy knowing he's facing a co-ordinated attack - I like this idea)
|-
|Non-solid buildings - ability to make tunnels through buildings, etc.
|MORPH
|Idea.
|-
|Tank collisions - why can tanks drive through each other? Weird.
|MORPH
|Good Idea, but severely hindered by lag issues.
|-
|When tanks collide - great opportunity to implement tank damage concept, especially if one of them is moving especially fast, or has momentum flag, etc. Can push a tank off a building if your pushing them from their side.
|Morph
|Idea
|-
|If a tank explodes right next to another tank, the other tank can be destroyed or get damaged
|MORPH
|Idea
|-
|Randomly changing arena - buildings grow, shrink, move
|MORPH
|(Unknown)
|-
|Server option: Make all good flags (except for ID flag) permanent (i.e. you cannot drop a flag unless you are killed). This discourages flag hunting (for GM flag or whatever) and forces players to play (build skill with?) the first flag they pick up until they die
|MORPH
|(Unknown)
|-
|Damage status- getting hit three (3) times kills you.
|MORPH
|(Unknown)
|-
|Skins or views- In-tank mode, bumper mode, out-of-cab mode, chase mode.
|MORPH
|(Unknown)
|-
|customizable sounds and/or models.
|MORPH
|(Unknown)
|-
|A usable world editor for mac and windows so that more servers are available.
|iPod
|Done
|-
|There should be a game of cops and robbers. The teams can change after about 10 mins or so.
|iPod
|(Unknown)
|-
|BZFlag for mac in seperate data and application files.
|iPod
|(Unknown)
|-
|Weapon extention packs.
|iPod
|Huh?
|-
|The ability to choose tanks, but they all die at one shot. maybe the jump height, speed, turn speed, acceleration, size can be preset.
|iPod
|(Unknown)
|-
|The ability to see what the world is like before connecting to the server.
|iPod
|(Unknown)
|-
|Sounds of tanks moving.
|iPod
|(Unknown)
|-
|Handicap. Allow for bad players yo have better properties than the best players (like velocity), so it's a more interesting play for everybody. It'll be server optional and the handicap players are marked in player lists|
|JavierMM
|(Unknown)
|-
|Additional Idea to Handicap:
* Autobalance option. If activated it adds an additional scale factor to the tank wich depends on the score. If the score rises the tank gets bigger and if the score is negative the tank gets smaller then the normal one (The hight of the tank will not be scaled). The strength of the effect should be defined by the server. The tank of an extreme good player will at one point no longer fit trough the teleporters and this will give an additional handicap until his score comes down again.
|Amoc
|(Unknown)
|-
|Have different tank death scenes for the dying tank point of view. I realize there is some time needed for one to die and respawn, but the jumping effect one sees when killed irritates me to no end! I'd be happier if all faded to black or white or orange and had text across the screen saying ""respawning... please wait"" :) Also, when killed and your tank was moving toward a building, it just falls right thru it until it hits the ground.. wrong physics there! Splatter or tumble or shatter or something :)
|Robi
|(Unknown)
|-
|A special FFA Game mode "Team by Flags". This means, same Flag = same Team, so if there is a Tank with Rapid fire, and you pick up Rapid fire, you are automatically handled as Team member (this means, killing the other Tank with Rapid fire will be handled the same way as when killing a team member). YHARG: Funky idea: what about a game mode where teams shared flag abilities? Like, each player on a team's flag applies to the whole team. This could make for some interesting combos...
|Agonizer
|(Unknown)
|-
|Make life trickier for the Rogue Team; with a mix of Rogues and Colored Teams, the Rogues have more targets. This should also change the effect of the Masquerade flag - perhaps your tank is invisible to Rogues (like Cloaking)?
|NickGrim
|(Unknown)
|-
|A server option to make deaths not affect your score unless they were self-inflicted/team (the method used by many online games). This would encourage more aggressive play, because it's worth going out and blasting. As it is, you've got a very good chance by just phantoming/OOing out of the way and keeping you score at zero to stay in the top three places! It would also help fix the rather unfair situation of spawning just below a building on which someone is GM-camping...there's pretty much no way to escape, so you lose a point.
|LionsPhil
|(Unknown)
|-
|Custom color schemes for rogue players. The turret and body components can be chosen to be one of a predefined set of colors (e.g. red, yellow, black, white, blue, green, purple...). The game prohibits choosing a color scheme that matches a team scheme (e.g. red turret with red body) and the limited set stops someone choosing a shade which is nearly a team color (e.g. 0xFE0000 instead of 0xFF0000) (and also save texture memory, I think).
|LionsPhil
|(Unknown)
|-
|Allow a small decal on the back of the top of the tank. (think Half-Life's customizable spraypaint). Possibly also apply it to any held flag?
|LionsPhil
|(Unknown)
|-
|What about a radar that only covers visible areas (don't passing through buildings/pyramids) ? This would leads to more placement tactics).
|K<nowiki>'</nowiki>limero
|(Unknown)
|-
|Spread Fire (SF) Flag which fires three shots at the same time. One on the centerline, the other two angled at a quarter degree along either side of the centerline.
|Yohan
|(Unknown)
|-
|World configuration of server options. Sometimes a map is designed for use with specific flags, or perhaps certain flags could be too powerful and you would want to turn them off.
|Yohan
|(Unknown)
|-
|Extending an idea from above regarding teleporters: Make teleporters configurable so that the map designer decides whether bullets or tanks or both can pass through the teleporter. Also, an option which changes the angle at which a bullet or tank will pass through a teleporter. Currently, if a teleporter links back to itself, the shot always returns back at the tank which fired it rather than reflecting.
|Yohan
|(Unknown)
|-
|HUD radar. (We are using this with our local games and love it).
|Yohan
|(Unknown)
|-
|* Add ice as a terrain feature
|morfie
|(Unknown)
|-
|Allow custom-made weapons with a Object-Oriented scripting language (sorta like Liero AI uses:
http://helios.et.put.poznan.pl/~sskowron/liero/index.html)
|Dragonstar
|(Unknown)
|-
|Custom-made graphics/objects for weapons and levels
|Dragonstar
|(Unknown)
|-
|Triggers in levels
|Dragonstar
|(Unknown)
|-
|Water Terrain
|Dragonstar
|(Unknown)
|-
|Custom Terrains (select a image to tile, slipperyness, etc.)
|Dragonstar
|(Unknown)
|-
|Option to choose different kinds of tanks. Different tanks could be weighted with different strengths and weaknesses. (almost like having a default flag). Would also need some form of health/damage status measurement, not just single hits. For example, there could be a larger, heavily armored tank that has powerful weapons, but moves slowly, versus a small, light, fast tank which is difficult to hit, but very low armor to protect from hits.
|Cue
|(Unknown)
|-
|Multiple list servers, in case bzflag.org goes down (as it happened around feb. 15. 2004)
|abli
|(Unknown)
|-
|Always random respawn. Currently in CTF games first respawn is at own base. This can be abused by leaving and rejoining to get near base. This leave/rejoing trick is considered to be a mild form of cheating by many. Always random respawn would make it useless.
|abli
|(Unknown)
|-
|Don't show invidual score in CTF games. This might help teamplay as it reduces the incentive to run around as if it would be FFA.
|abli
|(Unknown)
|-
|Give points to the player how captures flag in CTF. (Say, around 4 or so) After all, it is often a bigger job than killing someone.
|abli
|(Unknown)
|-
|volcano (growing red pyramid) that's death to touch and grows during the course of a round and occasionally gives off 'pyroclast flows' aka super bullets. perhaps red-orange color.
|kitchen
|(Unknown)
|-
|multiple (3?) jump stengths mini, normal, max...just the thing to confuse the opponents that expect one and you're off doing the other.
|kitchen
|(Unknown)
|-
|J2ME client (allows one to play on a cell phone), would use radar
|bhtooefr
|(Unknown)
|-
|Multi-monitor support (i.e., radar on one screen, window on another, chat/event log on a third)
|bhtooefr
|(Unknown)
|-
|wraparound world - radar remains centered on your current position. Internally, objects leaving the north border reappear to the south, but from the user's radar / visible perspective, you just see to the horizon. I believe this is how the original Battlezone worked. There are some implications: laser would need a range limit.
|nsayer
|(Unknown)
|-
|wireframe mode! man, this would make the game ten times cooler for nostalgia
|rjbs
|(Unknown)
|-
|Make a part in bzflag to put up a real server. 1st screen has the flags you want, next page is to find the MAP file that you created on your hard drive, next page pick if you want jumping etc.
|Colin
|(Unknown)
|-
|Health, like in a fps. If you get shot from a closer range, you take more damage. When you run out of health, you die. Health pickups in places - not a flag. Although there might be a health generator flag.
|Dan
|(Unknown)
|-
|For above: a "Doctor" flag - shooting someone (similar to thief) either fixes them or, like the above health generator flag, except faster, heals them. Don't shoot the other team!
|Dan
|(Unknown)
|-
|Anti camping. The ability to add "no camping zones" to areas of a map or to the entire map. Campers would be messaged that they're in a no camping zone, better start moving and have a prescribe number of seconds to move away or die. If a player returns to the same NCZ (no camping zone) and receives x warnings then he's disconnected. NCZs could be marked by a different color shade from a "normal" spot and could be exempt to a single team (like at their flag base). It's just a rough idea.
|pherris
|(Unknown)
|-
|Special 'open source' BZFlag version (server and client) which is guaranteed to be compatible with all other BZFlag versions.
|Orca
|(Unknown)
|-
|Trajectory flag and option on servers (Causes bullets to fall (But very slowly)). Bullets will go no lower than standard level, so trajectory is only active if you are jumping, or on a block.
|Dogbert
|(Unknown)
|-
|Moving blocks, so when people put things like the USS Enterprise at the top of their map, it can move around.
|Dogbert
|(Unknown)
|-
|Turret mode, If enabled by the server (Can be manditory with automatic grouping). One user drives and the other shoots, Turret mode tanks get double points (But onyl take one from the target). lost double points if killed. Have double ammo, And controllable speed (Max = _tankSpeed * 2 Min = _tankSpeed). Plus it takes 2 shots to kill a turret mode tank. Points gained and lost by turret tanks are divided evenly between the users, Unless the server is all turret mode, in h which case two users are displayed as one.
|Dogbert
|(Unknown)
|-
|I'd like to see something more interesting done with the sky... maybe there could be a little ufo (easter egg) that would fly around occasionally? Tux on a ufo! ;)
|YHARG
|(Unknown)
|-
|"Super smash bros" style jumping: a server-side option to let tanks jump a second or third time while in the air... changing direction would be possible by jumping with the pointer moved to what direction you'd like to doublejump. The direction change would probably be much less than the maximum tank speed, but maybe that could be a variable too. This would be great for platform maps. and add a way to mix up the classic jump killing that goes on in regular games.
|YHARG
|(Unknown)
|-
|Flag decals: Each flag would have a little icon/decal showing it's type ONLY when held by a player. It's kind of nice to be able to surprise people with an undercover shockwave, but doesn't make sense to have to right click (identify) or check the user list to see what flag someone has.
|YHARG
|(Unknown)
|-
|Ducati/Freestyle "Roles" mode: Make a game mode where players are presented with a list of flag choices (limitable to a few roles, if wanted) at respawn or connect time, and are forced to use this flag for the remainder of their connection/tank life. This would be really useful in the case of stealth vs. seer, where you could choose to be stealth or seer, but couldn't switch between them. Another idea would be high speed vs. quick turn. Or steamroller vs. machine gun... Team play would have the interesting effect of people banding together and people with each role on the team. Especially in stealth vs. seer, where a seer team member could warn the team about enemies! There would be no team flags/bases.
|YHARG
|(Unknown)
|-
|Background music! : (This can be done with an external media player so it shouldn't be the heighest priority, It would be nice to be able to control your music from within BzFlag)
|YHARG
|(Unknown)
|-
|Teleporter flag: Dropped twice, and makes a temporary teleporte on the map (for a set amount of time)
|YHARG
|(Unknown)
|-
|BeamMeUp flag: Tab makes the tank teleport to the highest object directly above it. This would be very useful with high maps, but could encourage camping, and cheating.
|YHARG
|(Unknown)
|-
|Tall tank flag: Like obesity, only makes the tank too tall to maneuver under low objects.
|YHARG
|(Unknown)
|-
|Triplicate/Duplicate/MagicHat flag: Tank gets one or two bot duplicates whose shots do no damage, spawned where it is. They could possibly be respawned when killed. They would tend to stay near the tank.
|YHARG
|(Unknown)
|-
|Sleepwalker Bad Flag: Your tank becomes controlled by a bot. Does not drop until tank is killed. Player's score is changed by bot's performance.
|YHARG
|(Unknown)
|-
|Shield Flag Changes: Give Shield flag a radius, and draw it like a moving less opaque blue shockwave. Any tanks inside the shield radius would be protected, until the shield got hit a certain number of times.
|YHARG
|(Unknown)
|-
|7 words: user freindly bult-in map editor and viewer.
|Efitu
|(Unknown)
|-
|More documentation on scripting world weapons.
|Dogbert
|(Unknown)
|-
|Preset world weapons that can be fired manually by admins from within BzFlag.
|Dogbert
|(Unknown)
|-
|Regicide flag, kills both the tanks you hit and the tank with the highest score on the same team of the tank you hit (Thus giving double points)
|Dogbert
|(Unknown)
|-
|Like Efitu's idea, user freindly built-in map editor and viewer, the current map editor isn't so good, expesaly when you delete stuff it does weard things.
|Supermatthew
|(Unknown)
|-
|Moving objects like a wall that could spin on its X Y or Z axis and chose the point were it spins like 5X, 3Y, 0Z away from its center
|Supermatthew
|(Unknown)
|-
|New game called tag were someone is it and they shoot someone else and there it and ect.
|Supermatthew
|(Unknown)
|-
|Also a new game called "Hide and seek" were everyone is clocked(think thats it, were you don't see them on radar) except one who is it. he needs to find someone and shoot them then hese cloked and who was shot is not. Also when someone is shot there sent back to Ground zero( 0X, 0Y, 0Z ) so they can't shoot who ever just shot them.
|Supermatthew
|(Unknown)
|-
|Editable ground hight like hills or something
|Supermatthew
|(Unknown)
|-
|another game called dodge ball were one person can shoot and when someone is hit then they become an observer till the next game and when theres only one person(other than the one whose it) they become it.
|Supermatthew
|(Unknown)
|-
|At our company, we instituted a voluntary policy of dropping flags after 1 kill. Prevents slaughters and keeps things rolling more. It'd be great to be able to have the game do this for us, plus I'd love to see it turned on at external sites.
|TomMatelich
|(Unknown)
|-
|Server option: default powers -- flag(s) that everyone in the game automatically has (this wouldn't count as holding a flag). For example, the current Jumping option would == including Jumping as a default power.
|NebNamwen
|(Unknown)
|}
</div>

[[Category:Development]]

Ideas

2007-03-19T08:25:58Z

L4m3r: Categorizing (still in progress)

{{Old}}
Feel free to make changes and updates to this page whenever possible. If you have any questions, feel free to [[Getting Help|ask for help]]. If you wish to make major changes to this page (i.e. remove large amounts of old ideas), please warn us ahead of time.

<b>NOTE: Work is in progress on this page. I'm converting to to a tabular format, and will then clean up and sort the ideas into categories. Please stand by. -L4m3r</b>

NOTE: These are just possiblilities. We won't be implementing everything here.<br>
NOTE: Flag ideas should be placed on [[Flag Ideas]]. Any other ideas can be placed here.

Status may include personal comments by developers.

== Adding ideas ==
* All ideas should be categorized and should be prefixed with a *.
* Sign your idea with four tildes: <nowiki>~~~~</nowiki>
* Make sense!

== General/Gameplay ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!Idea
!Status
!Commentary
!Submitter
|-
|Add support for 5 (or more) button mice
|Great Idea
|Old?
|(Unknown)
|-
|Better physics
|In progress
|Planning, some changes in CVS. (Old?)
|Unknown
|-
|SELF-DESTRUCT BLAST RADIUS: Self Destruct (delete key) should have a blast radius similar to Shock Wave, perhaps larger. If you get shot during the self-destruct count down, that should also trigger the same blast. If I gotta go, I want to take someone with me.
|(Unknown)
|
|BearRiver
|-
|3-second (or however long) 'invulnerability' for incoming tanks - but they can't shoot
|Idea
|I could see this backfiring... your spawn attracts opponents to come, wait, and blast you when you lose invincibility. -L4m3r
|MORPH
|-
|Ability to turn off ricochet for laser flag but allow ricochet for bullets... or let them bounce only n times.. OR implement mirror buildings/walls. Should go for some interesting self-kills when combined with the no-radar/bullet bounce
|Idea
|
|MORPH
|-
|Smart LockOn for GM - won't lock on to your teammates (configurable in server)
|Idea
|(M. Jetleb -> I don't like this idea, there should be at least *some* risks to using this weapon. Personally, I think there should be more (not fewer) risks to holding this weapon; I'd like to see the thing overheat and explode (killing the holder) if it's fired too often in a short period of time)
|MORPH
|-
|Small jumps
|Idea
|
|MORPH
|-
|Server option for genocide flag - if you're killed while you have it, your team dies :^)
|Idea
|Feasible with a plug-in, too. -L4m3r
|MORPH
|-
|for broadband or LAN connections - voice chat for teams
|Idea
|I really think that you can do this with another service; I'm not sure if being part of BZFlag would be a good idea due to size and bandwidth issues.
|MORPH
|-
|}
</div>

== UI ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!Idea
!Status
!Commentary
!Submitter
|-
|Make option to show previous players list
|Idea
|
|(Unknown)
|-
|Make ALL server options available from the menus
|Idea
|There are a LOT of server options, and this could add quite a bit of clutter. If you need more than a basic game, you should probably learn to start BZFS from the command line anyway. -L4m3r
|MORPH
|-
|Separate windows for player messages & server messages
|Good idea.
|
|MORPH
|-
|Message log
|Good idea.
|
|MORPH
|-
|}
</div>

== Technical ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!Idea
!Status
!Commentary
!Submitter
|-
|Better network handling
|In progress
|Old?
|(Unknown)
|-
|Better robot AI
|Idea
|Don't know if players would like it or not in multiplayer game. Pluggable or scriptable robot AI , maybe? - Code must be restructured first (Server side bots are coming! [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT))
|(Unknown)
|-
|Better positioning of tanks
|Idea
|BZFlag already does this, but the algorithm is bad. Needs work.
|MORPH
|-
|Serious multithreaded design - shouldn't lock up interface while looking for servers, or doing anything else. This program is way-unstable on Windows
|In Progress
|We're working on these problems; many complaints are due to people still using old servers/clients.
|MORPH
|-
|Some type of BZFlag GUID* to ban players who cheat - won't accept players who disable their GUID, etc.

<nowiki>*</nowiki>Global Unique Identifier, sort of like an IP addrss, but permanent. Usually a number. Problem occurs when you lose your GUID (have to reformat your HD, etc. How do you keep someone from hacking their GUID, or setting up a modified BZFlag server for identity theft, etc.
|(Unknown)
|I doubt this is even possible, let alone practical. What about people who play from more than one location? And, because this is an open-source game, it would probably be cracked in minutes. Any verification can be spoofed, or at least altered. there is no foolproof way to permanently ban someone. -L4m3r
|MORPH
|-
|}
</div>

== Game Modes, Team Play, and Scoring ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!Idea
!Status
!Commentary
!Submitter
|-
|Tounament mode
|Idea
|Great Idea?
|(Unknown)
|-
|When you shoot someone on your own team, instead of both of you blowing up, neither is destroyed, and their score goes up one, while your's goes down one. This would make teamkilling impossible and greatly discourage traitors as well.
|Trigger Happy Nerd
|But then couldn't cheaters spawn two clients and ramp up their scores by teamkilling their other login? --YHARG
|-
|}
</div>

== Maps, Mapping, and BZW ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!Idea
!Status
!Commentary
!Submitter
|-
|Materials that don't allow OO and PZ to go through
|Idea
|Would be nice for multilevel worlds made with the new ability to have objects above the ground. (Sounds awesome! TD-Linux 17:41, 12 March 2007 (EDT))
|(Unknown)
|-
|Differently-shaped teleporters (circles, triangles, etc.)
|Idea
|probably low priority
|MORPH
|-
|360 degree teleports - hit a spot on the ground or in the air from any direction and you teleport
|
|Idea
|MORPH
|-
|Configurable random teleporters - teleports to a different location every time
|Idea
|Idea is a bit vague... randomized teles are implemented if you use multiple links. Is this what is meant by this suggestion? -L4m3r
|MORPH
|-
|}
</div>

== Server Options, Administration, Plug-ins, and the Plug-in API ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!Idea
!Status
!Commentary
!Submitter
|-
|Ability to configure server to turn somethings off or on depending on number of players - for instance, turn off ricochet after a certain number of players are connected, turn off GM & laser if a certain number of players aren't playing (GM & Laser with 2 players is kinda ridiculous)
|Idea
|
|MORPH
|-
|}
</div>

== Ideas include: ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!Idea
!Submitter
!Status/approval
|-
|Tank avatars (uploadable tank images) - have to think about shapes, though - someone could make a 1x1x1 pixel tank - that would suck - or a tank that looks like a building or pyramid. Clients don't have to accept downloading of avators (just view other tanks in default mode). Or just s-e-l-e-c-t from a certain number of predefined avatars that could come with the bzflag distribution. Or client provides a URL to download their avatar (saves server bandwidth).
|MORPH
|Idea, but might not be implemented. Requires discussion; we may want to consider making the computer force a minimum size or something similar. *How about uploadable flag graphics?
|-
|To prevent cheating - the server determines what flags & abilities each tank has (possible?)
|MORPH
|Idea, but seriously being considered. This would also have the advantage of allowing different versions of clients and servers to work together. Yes, it's possible, but this type of change will mean a change in the network protocols. Being worked on for 2.2
|-
|Ability to change elevation of tank barrel & direction of turret (without jumping up or turning tank) (complex interface issues - super-low priority)
|MORPH
|Idea. Turret rotation rejected: The game is too fast for this to be useful, and would probably kill the game. *How about a new gameplay mode? Takes two to tank. One to ride turret, the other drives. KIA switches positions. "Teamplay" but all in one tank.
|-
|Concept of a tank that can take damage without being destroyed immediately - slows down, takes a hit in a tread and turns slowly in whatever direction, etc.
|MORPH
|Good idea, but must be optional (server option). Might be rejected, since BZFlag is, by nature, a fast paced game. *Loses ability to shoot, runs and grabs a restore flag?
|-
|'Kamikaze' option for players - can take someone out by suicide
|MORPH
|Idea. Server option if implemented. Implemented with a plugin by Theme97
|-
|Server option: everyone is radar-stealthed by default unless you get a 'radar' flag. You can still see all buildings, pyramids, teleports, and arena walls, though.
|MORPH
|Good idea. Make them use their window. ;)(M. Jetleb -> Given the fairly narrow field of view out the window and the time it takes to turn a tank all the way around for a look-see, I think this could be frustrating. How about everyone starts out with minimum range radar instead and gets longer ranges with an appropriate flag?)
|-
|Option for above: if you pick up GM or Laser, you're visible on radar to everyone whether they've got a radar flag or not
|MORPH
|Good idea
|-
|Selectable 'ricochet' fire - hold down shift key or something and your bullets won't ricochet
|MORPH
|Idea.
|-
|Server option - tanks only have a certain number of times they can jump (gets reset when you get killed)
|MORPH
|Idea.
|-
|Multiple-shields (server option for shield flags, or can be random - can get hit x number of times)
|MORPH
|Idea
|-
|Ability to damage or destroy buildings/pyramids/teleporters
|MORPH
|Idea (M. Jetleb - probably a good idea for timed games, where the building can be reset after a reasonable amount of time, but can you imagine what the field would look like for a perpetual game that's been running for days? There has to be some way to reset this. Also what happens if someone shoots the bottom out of a building? Does the building collapse or just remain suspended? This could get complicated.)
|-
|Server config to make bullets NOT go through teleporters
|MORPH
|Idea
|-
|SandTraps - tank gets stuck there
|MORPH
|Idea (aren't there enough incredibly annoying ways for tanks to get stuck on pyramids etc. already? --pediddle)
|-
|Configurable 'radarless' and/or 'blind' zones in the arena - can't see what's in there on radar or via visuals
|MORPH
|Idea
|-
|'Fog' area in arena - impairs use of laser
|MORPH
|Idea
|-
|Ability for a team to vote to 'banish' someone from their team
|MORPH
|Idea
|-
|Send message to everyone 'but' specified player (crosses team boundaries, or not)
|MORPH
|Idea. Hmm. Everybody BUT a specified player? [M. Jetleb -> as in: "Let's all get the GM guy" without the GM guy knowing he's facing a co-ordinated attack - I like this idea)
|-
|Non-solid buildings - ability to make tunnels through buildings, etc.
|MORPH
|Idea.
|-
|Tank collisions - why can tanks drive through each other? Weird.
|MORPH
|Good Idea, but severely hindered by lag issues.
|-
|When tanks collide - great opportunity to implement tank damage concept, especially if one of them is moving especially fast, or has momentum flag, etc. Can push a tank off a building if your pushing them from their side.
|Morph
|Idea
|-
|If a tank explodes right next to another tank, the other tank can be destroyed or get damaged
|MORPH
|Idea
|-
|Randomly changing arena - buildings grow, shrink, move
|MORPH
|(Unknown)
|-
|Server option: Make all good flags (except for ID flag) permanent (i.e. you cannot drop a flag unless you are killed). This discourages flag hunting (for GM flag or whatever) and forces players to play (build skill with?) the first flag they pick up until they die
|MORPH
|(Unknown)
|-
|Damage status- getting hit three (3) times kills you.
|MORPH
|(Unknown)
|-
|Skins or views- In-tank mode, bumper mode, out-of-cab mode, chase mode.
|MORPH
|(Unknown)
|-
|customizable sounds and/or models.
|MORPH
|(Unknown)
|-
|A usable world editor for mac and windows so that more servers are available.
|iPod
|Done
|-
|There should be a game of cops and robbers. The teams can change after about 10 mins or so.
|iPod
|(Unknown)
|-
|BZFlag for mac in seperate data and application files.
|iPod
|(Unknown)
|-
|Weapon extention packs.
|iPod
|Huh?
|-
|The ability to choose tanks, but they all die at one shot. maybe the jump height, speed, turn speed, acceleration, size can be preset.
|iPod
|(Unknown)
|-
|The ability to see what the world is like before connecting to the server.
|iPod
|(Unknown)
|-
|Sounds of tanks moving.
|iPod
|(Unknown)
|-
|Handicap. Allow for bad players yo have better properties than the best players (like velocity), so it's a more interesting play for everybody. It'll be server optional and the handicap players are marked in player lists|
|JavierMM
|(Unknown)
|-
|Additional Idea to Handicap:
* Autobalance option. If activated it adds an additional scale factor to the tank wich depends on the score. If the score rises the tank gets bigger and if the score is negative the tank gets smaller then the normal one (The hight of the tank will not be scaled). The strength of the effect should be defined by the server. The tank of an extreme good player will at one point no longer fit trough the teleporters and this will give an additional handicap until his score comes down again.
|Amoc
|(Unknown)
|-
|Have different tank death scenes for the dying tank point of view. I realize there is some time needed for one to die and respawn, but the jumping effect one sees when killed irritates me to no end! I'd be happier if all faded to black or white or orange and had text across the screen saying ""respawning... please wait"" :) Also, when killed and your tank was moving toward a building, it just falls right thru it until it hits the ground.. wrong physics there! Splatter or tumble or shatter or something :)
|Robi
|(Unknown)
|-
|A special FFA Game mode "Team by Flags". This means, same Flag = same Team, so if there is a Tank with Rapid fire, and you pick up Rapid fire, you are automatically handled as Team member (this means, killing the other Tank with Rapid fire will be handled the same way as when killing a team member). YHARG: Funky idea: what about a game mode where teams shared flag abilities? Like, each player on a team's flag applies to the whole team. This could make for some interesting combos...
|Agonizer
|(Unknown)
|-
|Make life trickier for the Rogue Team; with a mix of Rogues and Colored Teams, the Rogues have more targets. This should also change the effect of the Masquerade flag - perhaps your tank is invisible to Rogues (like Cloaking)?
|NickGrim
|(Unknown)
|-
|A server option to make deaths not affect your score unless they were self-inflicted/team (the method used by many online games). This would encourage more aggressive play, because it's worth going out and blasting. As it is, you've got a very good chance by just phantoming/OOing out of the way and keeping you score at zero to stay in the top three places! It would also help fix the rather unfair situation of spawning just below a building on which someone is GM-camping...there's pretty much no way to escape, so you lose a point.
|LionsPhil
|(Unknown)
|-
|Custom color schemes for rogue players. The turret and body components can be chosen to be one of a predefined set of colors (e.g. red, yellow, black, white, blue, green, purple...). The game prohibits choosing a color scheme that matches a team scheme (e.g. red turret with red body) and the limited set stops someone choosing a shade which is nearly a team color (e.g. 0xFE0000 instead of 0xFF0000) (and also save texture memory, I think).
|LionsPhil
|(Unknown)
|-
|Allow a small decal on the back of the top of the tank. (think Half-Life's customizable spraypaint). Possibly also apply it to any held flag?
|LionsPhil
|(Unknown)
|-
|What about a radar that only covers visible areas (don't passing through buildings/pyramids) ? This would leads to more placement tactics).
|K<nowiki>'</nowiki>limero
|(Unknown)
|-
|Spread Fire (SF) Flag which fires three shots at the same time. One on the centerline, the other two angled at a quarter degree along either side of the centerline.
|Yohan
|(Unknown)
|-
|World configuration of server options. Sometimes a map is designed for use with specific flags, or perhaps certain flags could be too powerful and you would want to turn them off.
|Yohan
|(Unknown)
|-
|Extending an idea from above regarding teleporters: Make teleporters configurable so that the map designer decides whether bullets or tanks or both can pass through the teleporter. Also, an option which changes the angle at which a bullet or tank will pass through a teleporter. Currently, if a teleporter links back to itself, the shot always returns back at the tank which fired it rather than reflecting.
|Yohan
|(Unknown)
|-
|HUD radar. (We are using this with our local games and love it).
|Yohan
|(Unknown)
|-
|* Add ice as a terrain feature
|morfie
|(Unknown)
|-
|Allow custom-made weapons with a Object-Oriented scripting language (sorta like Liero AI uses:
http://helios.et.put.poznan.pl/~sskowron/liero/index.html)
|Dragonstar
|(Unknown)
|-
|Custom-made graphics/objects for weapons and levels
|Dragonstar
|(Unknown)
|-
|Triggers in levels
|Dragonstar
|(Unknown)
|-
|Water Terrain
|Dragonstar
|(Unknown)
|-
|Custom Terrains (select a image to tile, slipperyness, etc.)
|Dragonstar
|(Unknown)
|-
|Option to choose different kinds of tanks. Different tanks could be weighted with different strengths and weaknesses. (almost like having a default flag). Would also need some form of health/damage status measurement, not just single hits. For example, there could be a larger, heavily armored tank that has powerful weapons, but moves slowly, versus a small, light, fast tank which is difficult to hit, but very low armor to protect from hits.
|Cue
|(Unknown)
|-
|Multiple list servers, in case bzflag.org goes down (as it happened around feb. 15. 2004)
|abli
|(Unknown)
|-
|Always random respawn. Currently in CTF games first respawn is at own base. This can be abused by leaving and rejoining to get near base. This leave/rejoing trick is considered to be a mild form of cheating by many. Always random respawn would make it useless.
|abli
|(Unknown)
|-
|Don't show invidual score in CTF games. This might help teamplay as it reduces the incentive to run around as if it would be FFA.
|abli
|(Unknown)
|-
|Give points to the player how captures flag in CTF. (Say, around 4 or so) After all, it is often a bigger job than killing someone.
|abli
|(Unknown)
|-
|volcano (growing red pyramid) that's death to touch and grows during the course of a round and occasionally gives off 'pyroclast flows' aka super bullets. perhaps red-orange color.
|kitchen
|(Unknown)
|-
|multiple (3?) jump stengths mini, normal, max...just the thing to confuse the opponents that expect one and you're off doing the other.
|kitchen
|(Unknown)
|-
|J2ME client (allows one to play on a cell phone), would use radar
|bhtooefr
|(Unknown)
|-
|Multi-monitor support (i.e., radar on one screen, window on another, chat/event log on a third)
|bhtooefr
|(Unknown)
|-
|wraparound world - radar remains centered on your current position. Internally, objects leaving the north border reappear to the south, but from the user's radar / visible perspective, you just see to the horizon. I believe this is how the original Battlezone worked. There are some implications: laser would need a range limit.
|nsayer
|(Unknown)
|-
|wireframe mode! man, this would make the game ten times cooler for nostalgia
|rjbs
|(Unknown)
|-
|Make a part in bzflag to put up a real server. 1st screen has the flags you want, next page is to find the MAP file that you created on your hard drive, next page pick if you want jumping etc.
|Colin
|(Unknown)
|-
|Health, like in a fps. If you get shot from a closer range, you take more damage. When you run out of health, you die. Health pickups in places - not a flag. Although there might be a health generator flag.
|Dan
|(Unknown)
|-
|For above: a "Doctor" flag - shooting someone (similar to thief) either fixes them or, like the above health generator flag, except faster, heals them. Don't shoot the other team!
|Dan
|(Unknown)
|-
|Anti camping. The ability to add "no camping zones" to areas of a map or to the entire map. Campers would be messaged that they're in a no camping zone, better start moving and have a prescribe number of seconds to move away or die. If a player returns to the same NCZ (no camping zone) and receives x warnings then he's disconnected. NCZs could be marked by a different color shade from a "normal" spot and could be exempt to a single team (like at their flag base). It's just a rough idea.
|pherris
|(Unknown)
|-
|Special 'open source' BZFlag version (server and client) which is guaranteed to be compatible with all other BZFlag versions.
|Orca
|(Unknown)
|-
|Trajectory flag and option on servers (Causes bullets to fall (But very slowly)). Bullets will go no lower than standard level, so trajectory is only active if you are jumping, or on a block.
|Dogbert
|(Unknown)
|-
|Moving blocks, so when people put things like the USS Enterprise at the top of their map, it can move around.
|Dogbert
|(Unknown)
|-
|Turret mode, If enabled by the server (Can be manditory with automatic grouping). One user drives and the other shoots, Turret mode tanks get double points (But onyl take one from the target). lost double points if killed. Have double ammo, And controllable speed (Max = _tankSpeed * 2 Min = _tankSpeed). Plus it takes 2 shots to kill a turret mode tank. Points gained and lost by turret tanks are divided evenly between the users, Unless the server is all turret mode, in h which case two users are displayed as one.
|Dogbert
|(Unknown)
|-
|I'd like to see something more interesting done with the sky... maybe there could be a little ufo (easter egg) that would fly around occasionally? Tux on a ufo! ;)
|YHARG
|(Unknown)
|-
|"Super smash bros" style jumping: a server-side option to let tanks jump a second or third time while in the air... changing direction would be possible by jumping with the pointer moved to what direction you'd like to doublejump. The direction change would probably be much less than the maximum tank speed, but maybe that could be a variable too. This would be great for platform maps. and add a way to mix up the classic jump killing that goes on in regular games.
|YHARG
|(Unknown)
|-
|Flag decals: Each flag would have a little icon/decal showing it's type ONLY when held by a player. It's kind of nice to be able to surprise people with an undercover shockwave, but doesn't make sense to have to right click (identify) or check the user list to see what flag someone has.
|YHARG
|(Unknown)
|-
|Ducati/Freestyle "Roles" mode: Make a game mode where players are presented with a list of flag choices (limitable to a few roles, if wanted) at respawn or connect time, and are forced to use this flag for the remainder of their connection/tank life. This would be really useful in the case of stealth vs. seer, where you could choose to be stealth or seer, but couldn't switch between them. Another idea would be high speed vs. quick turn. Or steamroller vs. machine gun... Team play would have the interesting effect of people banding together and people with each role on the team. Especially in stealth vs. seer, where a seer team member could warn the team about enemies! There would be no team flags/bases.
|YHARG
|(Unknown)
|-
|Background music! : (This can be done with an external media player so it shouldn't be the heighest priority, It would be nice to be able to control your music from within BzFlag)
|YHARG
|(Unknown)
|-
|Teleporter flag: Dropped twice, and makes a temporary teleporte on the map (for a set amount of time)
|YHARG
|(Unknown)
|-
|BeamMeUp flag: Tab makes the tank teleport to the highest object directly above it. This would be very useful with high maps, but could encourage camping, and cheating.
|YHARG
|(Unknown)
|-
|Tall tank flag: Like obesity, only makes the tank too tall to maneuver under low objects.
|YHARG
|(Unknown)
|-
|Triplicate/Duplicate/MagicHat flag: Tank gets one or two bot duplicates whose shots do no damage, spawned where it is. They could possibly be respawned when killed. They would tend to stay near the tank.
|YHARG
|(Unknown)
|-
|Sleepwalker Bad Flag: Your tank becomes controlled by a bot. Does not drop until tank is killed. Player's score is changed by bot's performance.
|YHARG
|(Unknown)
|-
|Shield Flag Changes: Give Shield flag a radius, and draw it like a moving less opaque blue shockwave. Any tanks inside the shield radius would be protected, until the shield got hit a certain number of times.
|YHARG
|(Unknown)
|-
|7 words: user freindly bult-in map editor and viewer.
|Efitu
|(Unknown)
|-
|More documentation on scripting world weapons.
|Dogbert
|(Unknown)
|-
|Preset world weapons that can be fired manually by admins from within BzFlag.
|Dogbert
|(Unknown)
|-
|Regicide flag, kills both the tanks you hit and the tank with the highest score on the same team of the tank you hit (Thus giving double points)
|Dogbert
|(Unknown)
|-
|Like Efitu's idea, user freindly built-in map editor and viewer, the current map editor isn't so good, expesaly when you delete stuff it does weard things.
|Supermatthew
|(Unknown)
|-
|Moving objects like a wall that could spin on its X Y or Z axis and chose the point were it spins like 5X, 3Y, 0Z away from its center
|Supermatthew
|(Unknown)
|-
|New game called tag were someone is it and they shoot someone else and there it and ect.
|Supermatthew
|(Unknown)
|-
|Also a new game called "Hide and seek" were everyone is clocked(think thats it, were you don't see them on radar) except one who is it. he needs to find someone and shoot them then hese cloked and who was shot is not. Also when someone is shot there sent back to Ground zero( 0X, 0Y, 0Z ) so they can't shoot who ever just shot them.
|Supermatthew
|(Unknown)
|-
|Editable ground hight like hills or something
|Supermatthew
|(Unknown)
|-
|another game called dodge ball were one person can shoot and when someone is hit then they become an observer till the next game and when theres only one person(other than the one whose it) they become it.
|Supermatthew
|(Unknown)
|-
|At our company, we instituted a voluntary policy of dropping flags after 1 kill. Prevents slaughters and keeps things rolling more. It'd be great to be able to have the game do this for us, plus I'd love to see it turned on at external sites.
|TomMatelich
|(Unknown)
|-
|Server option: default powers -- flag(s) that everyone in the game automatically has (this wouldn't count as holding a flag). For example, the current Jumping option would == including Jumping as a default power.
|NebNamwen
|(Unknown)
|}
</div>

[[Category:Development]]

Ideas

2007-03-19T00:22:40Z

L4m3r: Removed stuff that has long since been implemented, cleaned out some duplicates

{{Old}}
Feel free to make changes and updates to this page whenever possible. If you have any questions, feel free to [[Getting Help|ask for help]]. If you wish to make major changes to this page (i.e. remove large amounts of old ideas), please warn us ahead of time.

<b>NOTE: Work is in progress on this page. I'm converting to to a tabular format, and will then clean up and sort the ideas into categories. Please stand by. -L4m3r</b>

NOTE: These are just possiblilities. We won't be implementing everything here.<br>
NOTE: Flag ideas should be placed on [[Flag Ideas]]. Any other ideas can be placed here.

Status may include personal comments by developers.

== Adding ideas ==
* All ideas should be categorized and should be prefixed with a *.
* Sign your idea with four tildes: <nowiki>~~~~</nowiki>
* Make sense!

== Ideas include: ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!Idea
!Submitter
!Status/approval
|-
|Add support for 5 (or more) button mice
|(Unknown)
|Great Idea
|-
|Make option to show previous players list
|(Unknown)
|Idea
|-
|Better network handling
|(Unknown)
|Work in progress.
|-
|Better physics
|(Unknown)
|Planning, some changes in CVS.
|-
|Map editor
|(Unknown)
|Windows, Linux and Java2 editors are working, Linux editor in CVS, I want one using BZFlag's own engine.
|-
|Tounament mode
|(Unknown)
|Idea (Great Idea?)
|-
|Ability to define flags allowed / not allowed in world file
|(Unknown)
|Implemented with zones and the +f -f commands in the "options" world object.
|-
|Materials that don't allow OO and PZ to go through
|(Unknown)
|Would be nice for multilevel worlds made with the new ability to have objects above the ground. (Sounds awesome! [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT))
|-
|Better robot AI
|(Unknown)
|Idea, don't know if players would like it or not in multiplayer game. Pluggable or scriptable robot AI , maybe? - Code must be restructured first (Server side bots are coming! [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT))
|-
|When you shoot someone on your own team, instead of both of you blowing up, neither is destroyed, and their score goes up one, while your's goes down one. This would make teamkilling impossible and greatly discourage traitors as well.
|Trigger Happy Nerd
|But then couldn't cheaters spawn two clients and ramp up their scores by teamkilling their other login? --YHARG
|-
|SELF-DESTRUCT BLAST RADIUS: Self Destruct (delete key) should have a blast radius similar to Shock Wave, perhaps larger. If you get shot during the self-destruct count down, that should also trigger the same blast. If I gotta go, I want to take someone with me.
|BearRiver
|(Unknown)
|-
|Make ALL server options available from the menus
|MORPH
|Idea
|-
|Better positioning of tanks
|MORPH
|BZFlag already does this, but the algorithm is bad. Needs work.
|-
|3-second (or however long) 'invulnerability' for incoming tanks - but they can't shoot
|MORPH
|Idea.
|-
|Ability to turn off ricochet for laser flag but allow ricochet for bullets... or let them bounce only n times.. OR implement mirror buildings/walls. Should go for some interesting self-kills when combined with the no-radar/bullet bounce
|MORPH
|Idea
|-
|Smart LockOn for GM - won't lock on to your teammates (configurable in server)
|MORPH
|Idea. (M. Jetleb -> I don't like this idea, there should be at least *some* risks to using this weapon. Personally, I think there should be more (not fewer) risks to holding this weapon; I'd like to see the thing overheat and explode (killing the holder) if it's fired too often in a short period of time)
|-
|Small jumps
|MORPH
|Idea
|-
|Differently-shaped teleporters (circles, triangles, etc.)
|MORPH
|Idea, probably low priority
|-
|360 degree teleports - hit a spot on the ground or in the air from any direction and you teleport
|MORPH
|Idea
|-
|Configurable random teleporters - teleports to a different location every time
|MORPH
|Idea
|-
|Server option for genocide flag - if you're killed while you have it, your team dies :^)
|MORPH
|Idea
|-
|for broadband or LAN connections - voice chat for teams
|MORPH
|Idea, but I really think that you can do this with another service; I'm not sure if being part of BZFlag would be a good idea due to size and bandwidth issues.
|-
|Separate windows for player messages & server messages
|MORPH
|Good idea.
|-
|Message log
|MORPH
|Good idea.
|-
|Serious multithreaded design - shouldn't lock up interface while looking for servers, or doing anything else. This program is way-unstable on Windows
|MORPH
|We're working on these problems; many complaints are due to people still using old servers/clients.
|-
|Ability to configure server to turn somethings off or on depending on number of players - for instance, turn off ricochet after a certain number of players are connected, turn off GM & laser if a certain number of players aren't playing (GM & Laser with 2 players is kinda ridiculous)
|MORPH
|Idea
|-
|'Fox & Hound' scenario - highest player automatically becomes own team, all other plays on another team - kill the 'fox' (play with highest score).
|MORPH
|Good Idea, I'd like to see more ways to play BZFlag. There is an option in rabbit hunt that makes the player with the highest score rabbit until he dies.
|-
|Higher score(s) players lose abilities (bigger tanks, can't pick up flags, momentum, whatever)
|MORPH
|Idea
|-
|Some type of BZFlag GUID* to ban players who cheat - won't accept players who disable their GUID, etc.

<nowiki>*</nowiki>Global Unique Identifier, sort of like an IP addrss, but permanent. Usually a number. Problem occurs when you lose your GUID (have to reformat your HD, etc. How do you keep someone from hacking their GUID, or setting up a modified BZFlag server for identity theft, etc.
|MORPH
|What is a GUID??
|-
|Single/multiple-use flags (or they instantly change type after being used) (configurable on a flag-by-flag basis: e.g. laser & GM one-use only before they drop/disappear)
|MORPH
|Good idea, especially with the more powerful flags.
|-
|Tank avatars (uploadable tank images) - have to think about shapes, though - someone could make a 1x1x1 pixel tank - that would suck - or a tank that looks like a building or pyramid. Clients don't have to accept downloading of avators (just view other tanks in default mode). Or just s-e-l-e-c-t from a certain number of predefined avatars that could come with the bzflag distribution. Or client provides a URL to download their avatar (saves server bandwidth).
|MORPH
|Idea, but might not be implemented. Requires discussion; we may want to consider making the computer force a minimum size or something similar. *How about uploadable flag graphics?
|-
|To prevent cheating - the server determines what flags & abilities each tank has (possible?)
|MORPH
|Idea, but seriously being considered. This would also have the advantage of allowing different versions of clients and servers to work together. Yes, it's possible, but this type of change will mean a change in the network protocols. Being worked on for 2.2
|-
|Ability to change elevation of tank barrel & direction of turret (without jumping up or turning tank) (complex interface issues - super-low priority)
|MORPH
|Idea. Turret rotation rejected: The game is too fast for this to be useful, and would probably kill the game. *How about a new gameplay mode? Takes two to tank. One to ride turret, the other drives. KIA switches positions. "Teamplay" but all in one tank.
|-
|Concept of a tank that can take damage without being destroyed immediately - slows down, takes a hit in a tread and turns slowly in whatever direction, etc.
|MORPH
|Good idea, but must be optional (server option). Might be rejected, since BZFlag is, by nature, a fast paced game. *Loses ability to shoot, runs and grabs a restore flag?
|-
|'Kamikaze' option for players - can take someone out by suicide
|MORPH
|Idea. Server option if implemented. Implemented with a plugin by Theme97
|-
|Server option: everyone is radar-stealthed by default unless you get a 'radar' flag. You can still see all buildings, pyramids, teleports, and arena walls, though.
|MORPH
|Good idea. Make them use their window. ;)(M. Jetleb -> Given the fairly narrow field of view out the window and the time it takes to turn a tank all the way around for a look-see, I think this could be frustrating. How about everyone starts out with minimum range radar instead and gets longer ranges with an appropriate flag?)
|-
|Option for above: if you pick up GM or Laser, you're visible on radar to everyone whether they've got a radar flag or not
|MORPH
|Good idea
|-
|Selectable 'ricochet' fire - hold down shift key or something and your bullets won't ricochet
|MORPH
|Idea.
|-
|Server option - tanks only have a certain number of times they can jump (gets reset when you get killed)
|MORPH
|Idea.
|-
|Multiple-shields (server option for shield flags, or can be random - can get hit x number of times)
|MORPH
|Idea
|-
|Ability to damage or destroy buildings/pyramids/teleporters
|MORPH
|Idea (M. Jetleb - probably a good idea for timed games, where the building can be reset after a reasonable amount of time, but can you imagine what the field would look like for a perpetual game that's been running for days? There has to be some way to reset this. Also what happens if someone shoots the bottom out of a building? Does the building collapse or just remain suspended? This could get complicated.)
|-
|Server config to make bullets NOT go through teleporters
|MORPH
|Idea
|-
|SandTraps - tank gets stuck there
|MORPH
|Idea (aren't there enough incredibly annoying ways for tanks to get stuck on pyramids etc. already? --pediddle)
|-
|Configurable 'radarless' and/or 'blind' zones in the arena - can't see what's in there on radar or via visuals
|MORPH
|Idea
|-
|'Fog' area in arena - impairs use of laser
|MORPH
|Idea
|-
|Ability for a team to vote to 'banish' someone from their team
|MORPH
|Idea
|-
|Send message to everyone 'but' specified player (crosses team boundaries, or not)
|MORPH
|Idea. Hmm. Everybody BUT a specified player? [M. Jetleb -> as in: "Let's all get the GM guy" without the GM guy knowing he's facing a co-ordinated attack - I like this idea)
|-
|Non-solid buildings - ability to make tunnels through buildings, etc.
|MORPH
|Idea.
|-
|Tank collisions - why can tanks drive through each other? Weird.
|MORPH
|Good Idea, but severely hindered by lag issues.
|-
|When tanks collide - great opportunity to implement tank damage concept, especially if one of them is moving especially fast, or has momentum flag, etc. Can push a tank off a building if your pushing them from their side.
|Morph
|Idea
|-
|If a tank explodes right next to another tank, the other tank can be destroyed or get damaged
|MORPH
|Idea
|-
|Randomly changing arena - buildings grow, shrink, move
|MORPH
|(Unknown)
|-
|Server option: Make all good flags (except for ID flag) permanent (i.e. you cannot drop a flag unless you are killed). This discourages flag hunting (for GM flag or whatever) and forces players to play (build skill with?) the first flag they pick up until they die
|MORPH
|(Unknown)
|-
|Damage status- getting hit three (3) times kills you.
|MORPH
|(Unknown)
|-
|Skins or views- In-tank mode, bumper mode, out-of-cab mode, chase mode.
|MORPH
|(Unknown)
|-
|customizable sounds and/or models.
|MORPH
|(Unknown)
|-
|A usable world editor for mac and windows so that more servers are available.
|iPod
|Done
|-
|There should be a game of cops and robbers. The teams can change after about 10 mins or so.
|iPod
|(Unknown)
|-
|BZFlag for mac in seperate data and application files.
|iPod
|(Unknown)
|-
|Weapon extention packs.
|iPod
|Huh?
|-
|The ability to choose tanks, but they all die at one shot. maybe the jump height, speed, turn speed, acceleration, size can be preset.
|iPod
|(Unknown)
|-
|The ability to see what the world is like before connecting to the server.
|iPod
|(Unknown)
|-
|Sounds of tanks moving.
|iPod
|(Unknown)
|-
|Handicap. Allow for bad players yo have better properties than the best players (like velocity), so it's a more interesting play for everybody. It'll be server optional and the handicap players are marked in player lists|
|JavierMM
|(Unknown)
|-
|Additional Idea to Handicap:
* Autobalance option. If activated it adds an additional scale factor to the tank wich depends on the score. If the score rises the tank gets bigger and if the score is negative the tank gets smaller then the normal one (The hight of the tank will not be scaled). The strength of the effect should be defined by the server. The tank of an extreme good player will at one point no longer fit trough the teleporters and this will give an additional handicap until his score comes down again.
|Amoc
|(Unknown)
|-
|Have different tank death scenes for the dying tank point of view. I realize there is some time needed for one to die and respawn, but the jumping effect one sees when killed irritates me to no end! I'd be happier if all faded to black or white or orange and had text across the screen saying ""respawning... please wait"" :) Also, when killed and your tank was moving toward a building, it just falls right thru it until it hits the ground.. wrong physics there! Splatter or tumble or shatter or something :)
|Robi
|(Unknown)
|-
|A special FFA Game mode "Team by Flags". This means, same Flag = same Team, so if there is a Tank with Rapid fire, and you pick up Rapid fire, you are automatically handled as Team member (this means, killing the other Tank with Rapid fire will be handled the same way as when killing a team member). YHARG: Funky idea: what about a game mode where teams shared flag abilities? Like, each player on a team's flag applies to the whole team. This could make for some interesting combos...
|Agonizer
|(Unknown)
|-
|Make life trickier for the Rogue Team; with a mix of Rogues and Colored Teams, the Rogues have more targets. This should also change the effect of the Masquerade flag - perhaps your tank is invisible to Rogues (like Cloaking)?
|NickGrim
|(Unknown)
|-
|A server option to make deaths not affect your score unless they were self-inflicted/team (the method used by many online games). This would encourage more aggressive play, because it's worth going out and blasting. As it is, you've got a very good chance by just phantoming/OOing out of the way and keeping you score at zero to stay in the top three places! It would also help fix the rather unfair situation of spawning just below a building on which someone is GM-camping...there's pretty much no way to escape, so you lose a point.
|LionsPhil
|(Unknown)
|-
|Custom color schemes for rogue players. The turret and body components can be chosen to be one of a predefined set of colors (e.g. red, yellow, black, white, blue, green, purple...). The game prohibits choosing a color scheme that matches a team scheme (e.g. red turret with red body) and the limited set stops someone choosing a shade which is nearly a team color (e.g. 0xFE0000 instead of 0xFF0000) (and also save texture memory, I think).
|LionsPhil
|(Unknown)
|-
|Allow a small decal on the back of the top of the tank. (think Half-Life's customizable spraypaint). Possibly also apply it to any held flag?
|LionsPhil
|(Unknown)
|-
|What about a radar that only covers visible areas (don't passing through buildings/pyramids) ? This would leads to more placement tactics).
|K<nowiki>'</nowiki>limero
|(Unknown)
|-
|Spread Fire (SF) Flag which fires three shots at the same time. One on the centerline, the other two angled at a quarter degree along either side of the centerline.
|Yohan
|(Unknown)
|-
|World configuration of server options. Sometimes a map is designed for use with specific flags, or perhaps certain flags could be too powerful and you would want to turn them off.
|Yohan
|(Unknown)
|-
|Extending an idea from above regarding teleporters: Make teleporters configurable so that the map designer decides whether bullets or tanks or both can pass through the teleporter. Also, an option which changes the angle at which a bullet or tank will pass through a teleporter. Currently, if a teleporter links back to itself, the shot always returns back at the tank which fired it rather than reflecting.
|Yohan
|(Unknown)
|-
|HUD radar. (We are using this with our local games and love it).
|Yohan
|(Unknown)
|-
|* Add ice as a terrain feature
|morfie
|(Unknown)
|-
|Allow custom-made weapons with a Object-Oriented scripting language (sorta like Liero AI uses:
http://helios.et.put.poznan.pl/~sskowron/liero/index.html)
|Dragonstar
|(Unknown)
|-
|Custom-made graphics/objects for weapons and levels
|Dragonstar
|(Unknown)
|-
|Triggers in levels
|Dragonstar
|(Unknown)
|-
|Water Terrain
|Dragonstar
|(Unknown)
|-
|Custom Terrains (select a image to tile, slipperyness, etc.)
|Dragonstar
|(Unknown)
|-
|Option to choose different kinds of tanks. Different tanks could be weighted with different strengths and weaknesses. (almost like having a default flag). Would also need some form of health/damage status measurement, not just single hits. For example, there could be a larger, heavily armored tank that has powerful weapons, but moves slowly, versus a small, light, fast tank which is difficult to hit, but very low armor to protect from hits.
|Cue
|(Unknown)
|-
|Multiple list servers, in case bzflag.org goes down (as it happened around feb. 15. 2004)
|abli
|(Unknown)
|-
|Always random respawn. Currently in CTF games first respawn is at own base. This can be abused by leaving and rejoining to get near base. This leave/rejoing trick is considered to be a mild form of cheating by many. Always random respawn would make it useless.
|abli
|(Unknown)
|-
|Don't show invidual score in CTF games. This might help teamplay as it reduces the incentive to run around as if it would be FFA.
|abli
|(Unknown)
|-
|Give points to the player how captures flag in CTF. (Say, around 4 or so) After all, it is often a bigger job than killing someone.
|abli
|(Unknown)
|-
|volcano (growing red pyramid) that's death to touch and grows during the course of a round and occasionally gives off 'pyroclast flows' aka super bullets. perhaps red-orange color.
|kitchen
|(Unknown)
|-
|multiple (3?) jump stengths mini, normal, max...just the thing to confuse the opponents that expect one and you're off doing the other.
|kitchen
|(Unknown)
|-
|J2ME client (allows one to play on a cell phone), would use radar
|bhtooefr
|(Unknown)
|-
|Multi-monitor support (i.e., radar on one screen, window on another, chat/event log on a third)
|bhtooefr
|(Unknown)
|-
|wraparound world - radar remains centered on your current position. Internally, objects leaving the north border reappear to the south, but from the user's radar / visible perspective, you just see to the horizon. I believe this is how the original Battlezone worked. There are some implications: laser would need a range limit.
|nsayer
|(Unknown)
|-
|wireframe mode! man, this would make the game ten times cooler for nostalgia
|rjbs
|(Unknown)
|-
|Make a part in bzflag to put up a real server. 1st screen has the flags you want, next page is to find the MAP file that you created on your hard drive, next page pick if you want jumping etc.
|Colin
|(Unknown)
|-
|Health, like in a fps. If you get shot from a closer range, you take more damage. When you run out of health, you die. Health pickups in places - not a flag. Although there might be a health generator flag.
|Dan
|(Unknown)
|-
|For above: a "Doctor" flag - shooting someone (similar to thief) either fixes them or, like the above health generator flag, except faster, heals them. Don't shoot the other team!
|Dan
|(Unknown)
|-
|Anti camping. The ability to add "no camping zones" to areas of a map or to the entire map. Campers would be messaged that they're in a no camping zone, better start moving and have a prescribe number of seconds to move away or die. If a player returns to the same NCZ (no camping zone) and receives x warnings then he's disconnected. NCZs could be marked by a different color shade from a "normal" spot and could be exempt to a single team (like at their flag base). It's just a rough idea.
|pherris
|(Unknown)
|-
|Special 'open source' BZFlag version (server and client) which is guaranteed to be compatible with all other BZFlag versions.
|Orca
|(Unknown)
|-
|Trajectory flag and option on servers (Causes bullets to fall (But very slowly)). Bullets will go no lower than standard level, so trajectory is only active if you are jumping, or on a block.
|Dogbert
|(Unknown)
|-
|Moving blocks, so when people put things like the USS Enterprise at the top of their map, it can move around.
|Dogbert
|(Unknown)
|-
|Turret mode, If enabled by the server (Can be manditory with automatic grouping). One user drives and the other shoots, Turret mode tanks get double points (But onyl take one from the target). lost double points if killed. Have double ammo, And controllable speed (Max = _tankSpeed * 2 Min = _tankSpeed). Plus it takes 2 shots to kill a turret mode tank. Points gained and lost by turret tanks are divided evenly between the users, Unless the server is all turret mode, in h which case two users are displayed as one.
|Dogbert
|(Unknown)
|-
|I'd like to see something more interesting done with the sky... maybe there could be a little ufo (easter egg) that would fly around occasionally? Tux on a ufo! ;)
|YHARG
|(Unknown)
|-
|"Super smash bros" style jumping: a server-side option to let tanks jump a second or third time while in the air... changing direction would be possible by jumping with the pointer moved to what direction you'd like to doublejump. The direction change would probably be much less than the maximum tank speed, but maybe that could be a variable too. This would be great for platform maps. and add a way to mix up the classic jump killing that goes on in regular games.
|YHARG
|(Unknown)
|-
|Flag decals: Each flag would have a little icon/decal showing it's type ONLY when held by a player. It's kind of nice to be able to surprise people with an undercover shockwave, but doesn't make sense to have to right click (identify) or check the user list to see what flag someone has.
|YHARG
|(Unknown)
|-
|Ducati/Freestyle "Roles" mode: Make a game mode where players are presented with a list of flag choices (limitable to a few roles, if wanted) at respawn or connect time, and are forced to use this flag for the remainder of their connection/tank life. This would be really useful in the case of stealth vs. seer, where you could choose to be stealth or seer, but couldn't switch between them. Another idea would be high speed vs. quick turn. Or steamroller vs. machine gun... Team play would have the interesting effect of people banding together and people with each role on the team. Especially in stealth vs. seer, where a seer team member could warn the team about enemies! There would be no team flags/bases.
|YHARG
|(Unknown)
|-
|Background music! : (This can be done with an external media player so it shouldn't be the heighest priority, It would be nice to be able to control your music from within BzFlag)
|YHARG
|(Unknown)
|-
|Teleporter flag: Dropped twice, and makes a temporary teleporte on the map (for a set amount of time)
|YHARG
|(Unknown)
|-
|BeamMeUp flag: Tab makes the tank teleport to the highest object directly above it. This would be very useful with high maps, but could encourage camping, and cheating.
|YHARG
|(Unknown)
|-
|Tall tank flag: Like obesity, only makes the tank too tall to maneuver under low objects.
|YHARG
|(Unknown)
|-
|Triplicate/Duplicate/MagicHat flag: Tank gets one or two bot duplicates whose shots do no damage, spawned where it is. They could possibly be respawned when killed. They would tend to stay near the tank.
|YHARG
|(Unknown)
|-
|Sleepwalker Bad Flag: Your tank becomes controlled by a bot. Does not drop until tank is killed. Player's score is changed by bot's performance.
|YHARG
|(Unknown)
|-
|Shield Flag Changes: Give Shield flag a radius, and draw it like a moving less opaque blue shockwave. Any tanks inside the shield radius would be protected, until the shield got hit a certain number of times.
|YHARG
|(Unknown)
|-
|7 words: user freindly bult-in map editor and viewer.
|Efitu
|(Unknown)
|-
|More documentation on scripting world weapons.
|Dogbert
|(Unknown)
|-
|Preset world weapons that can be fired manually by admins from within BzFlag.
|Dogbert
|(Unknown)
|-
|Regicide flag, kills both the tanks you hit and the tank with the highest score on the same team of the tank you hit (Thus giving double points)
|Dogbert
|(Unknown)
|-
|Like Efitu's idea, user freindly built-in map editor and viewer, the current map editor isn't so good, expesaly when you delete stuff it does weard things.
|Supermatthew
|(Unknown)
|-
|Moving objects like a wall that could spin on its X Y or Z axis and chose the point were it spins like 5X, 3Y, 0Z away from its center
|Supermatthew
|(Unknown)
|-
|New game called tag were someone is it and they shoot someone else and there it and ect.
|Supermatthew
|(Unknown)
|-
|Also a new game called "Hide and seek" were everyone is clocked(think thats it, were you don't see them on radar) except one who is it. he needs to find someone and shoot them then hese cloked and who was shot is not. Also when someone is shot there sent back to Ground zero( 0X, 0Y, 0Z ) so they can't shoot who ever just shot them.
|Supermatthew
|(Unknown)
|-
|Editable ground hight like hills or something
|Supermatthew
|(Unknown)
|-
|another game called dodge ball were one person can shoot and when someone is hit then they become an observer till the next game and when theres only one person(other than the one whose it) they become it.
|Supermatthew
|(Unknown)
|-
|At our company, we instituted a voluntary policy of dropping flags after 1 kill. Prevents slaughters and keeps things rolling more. It'd be great to be able to have the game do this for us, plus I'd love to see it turned on at external sites.
|TomMatelich
|(Unknown)
|-
|Server option: default powers -- flag(s) that everyone in the game automatically has (this wouldn't count as holding a flag). For example, the current Jumping option would == including Jumping as a default power.
|NebNamwen
|(Unknown)
|}
</div>

[[Category:Development]]

Ideas

2007-03-18T22:55:01Z

L4m3r: /* Ideas include: */ fix table wonkiness (oops)

{{Old}}
Feel free to make changes and updates to this page whenever possible. If you have any questions, feel free to [[Getting Help|ask for help]]. If you wish to make major changes to this page (i.e. remove large amounts of old ideas), please warn us ahead of time.

<b>NOTE: Work is in progress on this page. I'm converting to to a tabular format, and will then clean up and sort the ideas into categories. Please stand by. -L4m3r</b>

NOTE: These are just possiblilities. We won't be implementing everything here.<br>
NOTE: Flag ideas should be placed on [[Flag Ideas]]. Any other ideas can be placed here.

Status may include personal comments by developers.

== Adding ideas ==
* All ideas should be categorized and should be prefixed with a *.
* Sign your idea with four tildes: <nowiki>~~~~</nowiki>
* Make sense!

== Ideas include: ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!Idea
!Submitter
!Status/approval
|-
|Add support for 5 (or more) button mice
|(Unknown)
|Great Idea
|-
|Sort player list by team
|(Unknown)
|Implemented (how?)
|-
|Make option to show previous players list
|(Unknown)
|Idea
|-
|Anti-cheating measures detecting cheating clients/servers, kicking them out automatically or by vote, etc. I will push to have this implemented in version 1.8.
|(Unknown)
|Some anti-cheating measures are in 1.7G2, more work to follow. Great Idea (delete this idea, it's ancient?)
|-
|Better network handling
|(Unknown)
|Work in progress.
|-
|Better physics
|(Unknown)
|Planning, some changes in CVS.
|-
|Map editor
|(Unknown)
|Windows, Linux and Java2 editors are working, Linux editor in CVS, I want one using BZFlag's own engine.
|-
|server-side respawn position
|(Unknown)
|Implemented in [[BZFlag 2.0.0]]
|-
|2 or 3 teams as well as the current 4
|(Unknown)
|Man, this gotta be old. BZFlag used to only work with 4 teams??
|-
|Tounament mode
|(Unknown)
|Idea (Great Idea?)
|-
|Ability to define flags allowed / not allowed in world file
|(Unknown)
|Idea
|-
|Materials that don't allow OO and PZ to go through
|(Unknown)
|Would be nice for multilevel worlds made with the new ability to have objects above the ground. (Sounds awesome! [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT))
|-
|Better robot AI
|(Unknown)
|Idea, don't know if players would like it or not in multiplayer game. Pluggable or scriptable robot AI , maybe? - Code must be restructured first (Server side bots are coming! [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT))
|-
|Option to search for servers in list. It gets really annoying if you want to find a server and you have to go through all the pages, as there are over 10 now.
|Spazzy McGee
|Implemented in [[BZFlag 2.0.4]]
|-
|When you shoot someone on your own team, instead of both of you blowing up, neither is destroyed, and their score goes up one, while your's goes down one. This would make teamkilling impossible and greatly discourage traitors as well.
|Trigger Happy Nerd
|But then couldn't cheaters spawn two clients and ramp up their scores by teamkilling their other login? --YHARG
|-
|SELF-DESTRUCT BLAST RADIUS: Self Destruct (delete key) should have a blast radius similar to Shock Wave, perhaps larger. If you get shot during the self-destruct count down, that should also trigger the same blast. If I gotta go, I want to take someone with me.
|BearRiver
|(Unknown)
|-
|Make ALL server options available from the menus
|MORPH
|Idea
|-
|Ability to toggle display of player emails (some are so long they mess up the score display)
|MORPH
|Idea
|-
|Word wrap long messages - they get cut off for those with low-resolution displays
|MORPH
|Done??
|-
|Improvements to radar: Color-coded bullets, brighter bullets (may have to be larger if already using brightest color), better distinction between blue players and pyramids
|MORPH
|Done
|-
|Better positioning of tanks
|MORPH
|BZFlag already does this, but the algorithm is bad. Needs work.
|-
|3-second (or however long) 'invulnerability' for incoming tanks - but they can't shoot
|MORPH
|Idea.
|-
|Ability to turn off ricochet for laser flag but allow ricochet for bullets... or let them bounce only n times.. OR implement mirror buildings/walls. Should go for some interesting self-kills when combined with the no-radar/bullet bounce
|MORPH
|Idea
|-
|Smart LockOn for GM - won't lock on to your teammates (configurable in server)
|MORPH
|Idea. (M. Jetleb -> I don't like this idea, there should be at least *some* risks to using this weapon. Personally, I think there should be more (not fewer) risks to holding this weapon; I'd like to see the thing overheat and explode (killing the holder) if it's fired too often in a short period of time)
|-
|Small jumps
|MORPH
|Idea
|-
|Differently-shaped teleporters (circles, triangles, etc.)
|MORPH
|Idea, probably low priority
|-
|360 degree teleports - hit a spot on the ground or in the air from any direction and you teleport
|MORPH
|Idea
|-
|Configurable random teleporters - teleports to a different location every time
|MORPH
|Idea
|-
|Allow different physical properties on top of buildings (momentum, etc.)
|MORPH
|Idea, goes with my ""materials"" idea.
|-
|Allow higher wall-height around arena (ricochet at higher heights) - or no walls defining the boundaries - just a line. (ricochet only off buildings & pyramids)
|MORPH
|Idea
|-
|Server option for genocide flag - if you're killed while you have it, your team dies :^)
|MORPH
|Idea
|-
|for broadband or LAN connections - voice chat for teams
|MORPH
|Idea, but I really think that you can do this with another service; I'm not sure if being part of BZFlag would be a good idea due to size and bandwidth issues.
|-
|Separate windows for player messages & server messages
|MORPH
|Good idea.
|-
|Message log
|MORPH
|Good idea.
|-
|Serious multithreaded design - shouldn't lock up interface while looking for servers, or doing anything else. This program is way-unstable on Windows
|MORPH
|We're working on these problems; many complaints are due to people still using old servers/clients.
|-
|Ability to configure server to turn somethings off or on depending on number of players - for instance, turn off ricochet after a certain number of players are connected, turn off GM & laser if a certain number of players aren't playing (GM & Laser with 2 players is kinda ridiculous)
|MORPH
|Idea
|-
|'Fox & Hound' scenario - highest player automatically becomes own team, all other plays on another team - kill the 'fox' (play with highest score).
|MORPH
|Good Idea, I'd like to see more ways to play BZFlag. (bhtooefr: Rabbit is very similar to this)
|-
|Higher score(s) players lose abilities (bigger tanks, can't pick up flags, momentum, whatever)
|MORPH
|Idea
|-
|Some type of BZFlag GUID* to ban players who cheat - won't accept players who disable their GUID, etc.

<nowiki>*</nowiki>Global Unique Identifier, sort of like an IP addrss, but permanent. Usually a number. Problem occurs when you lose your GUID (have to reformat your HD, etc. How do you keep someone from hacking their GUID, or setting up a modified BZFlag server for identity theft, etc.
|MORPH
|What is a GUID??
|-
|Single/multiple-use flags (or they instantly change type after being used) (configurable on a flag-by-flag basis: e.g. laser & GM one-use only before they drop/disappear)
|MORPH
|Good idea, especially with the more powerful flags.
|-
|Change graphic format to PNG so new 'skins' can be created. Optional use of server-defined skin. Client can use it or not (wouldn't really matter)
|MORPH
|In CVS for 1.8.
|-
|Tank avatars (uploadable tank images) - have to think about shapes, though - someone could make a 1x1x1 pixel tank - that would suck - or a tank that looks like a building or pyramid. Clients don't have to accept downloading of avators (just view other tanks in default mode). Or just s-e-l-e-c-t from a certain number of predefined avatars that could come with the bzflag distribution. Or client provides a URL to download their avatar (saves server bandwidth).
|MORPH
|Idea, but might not be implemented. Requires discussion; we may want to consider making the computer force a minimum size or something similar. *How about uploadable flag graphics?
|-
|To prevent cheating - the server determines what flags & abilities each tank has (possible?)
|MORPH
|Idea, but seriously being considered. This would also have the advantage of allowing different versions of clients and servers to work together. Yes, it's possible, but this type of change will mean a change in the network protocols.
|-
|Send message to an individual, even if they're not on your team
|MORPH
|done
|-
|Ability to change elevation of tank barrel & direction of turret (without jumping up or turning tank) (complex interface issues - super-low priority)
|MORPH
|Idea. Turret rotation rejected: The game is too fast for this to be useful, and would probably kill the game. *How about a new gameplay mode? Takes two to tank. One to ride turret, the other drives. KIA switches positions. "Teamplay" but all in one tank.
|-
|Much better arena design capabilities - bridges over ditches, etc.
|MORPH
|Good idea. This along with some new physics (which I hope to propose soon -Jeremiah), and BZFlag will be much more interesting.
|-
|Concept of a tank that can take damage without being destroyed immediately - slows down, takes a hit in a tread and turns slowly in whatever direction, etc.
|MORPH
|Good idea, but must be optional (server option). Might be rejected, since BZFlag is, by nature, a fast paced game. *Loses ability to shoot, runs and grabs a restore flag?
|-
|'Kamikaze' option for players - can take someone out by suicide
|MORPH
|Idea. Server option if implemented.
|-
|Server option: everyone is radar-stealthed by default unless you get a 'radar' flag. You can still see all buildings, pyramids, teleports, and arena walls, though.
|MORPH
|Good idea. Make them use their window. ;)(M. Jetleb -> Given the fairly narrow field of view out the window and the time it takes to turn a tank all the way around for a look-see, I think this could be frustrating. How about everyone starts out with minimum range radar instead and gets longer ranges with an appropriate flag?)
|-
|Option for above: if you pick up GM or Laser, you're visible on radar to everyone whether they've got a radar flag or not
|MORPH
|Good idea
|-
|Selectable 'ricochet' fire - hold down shift key or something and your bullets won't ricochet
|MORPH
|Idea.
|-
|Server option - tanks only have a certain number of times they can jump (gets reset when you get killed)
|MORPH
|Idea.
|-
|Multiple-shields (server option for shield flags, or can be random - can get hit x number of times)
|MORPH
|Idea
|-
|Ability to damage or destroy buildings/pyramids/teleporters
|MORPH
|Idea (M. Jetleb - probably a good idea for timed games, where the building can be reset after a reasonable amount of time, but can you imagine what the field would look like for a perpetual game that's been running for days? There has to be some way to reset this. Also what happens if someone shoots the bottom out of a building? Does the building collapse or just remain suspended? This could get complicated.)
|-
|Server config to make bullets NOT go through teleporters
|MORPH
|Idea
|-
|Holographic buildings - can't see what's behind them, but can shoot through them (great for the radarless-option above)[M. Jetleb -> how does not being able to see through a building help when you're radarless?]. Can't tell the difference on radar between them and regular buildings
|MORPH
|Idea, could be a materials property.
|-
|SandTraps - tank gets stuck there
|MORPH
|Idea (aren't there enough incredibly annoying ways for tanks to get stuck on pyramids etc. already? --pediddle)
|-
|Configurable 'radarless' and/or 'blind' zones in the arena - can't see what's in there on radar or via visuals
|MORPH
|Idea
|-
|'Fog' area in arena - impairs use of laser
|MORPH
|Idea
|-
|Connection-quality restrictions - restriction players based on connection quality - if they're having connection problems, server can drop them (after informing them what's going on)
|MORPH
|Implemented - also, throttling is implemented; people with high framerates were sending a lot of messages, clogging things up for people with slower connections.
|-
|Ability for a team to vote to 'banish' someone from their team
|MORPH
|Idea
|-
|Send message to everyone 'but' specified player (crosses team boundaries, or not)
|MORPH
|Idea. Hmm. Everybody BUT a specified player? [M. Jetleb -> as in: "Let's all get the GM guy" without the GM guy knowing he's facing a co-ordinated attack - I like this idea)
|-
|Non-solid buildings - ability to make tunnels through buildings, etc.
|MORPH
|Idea.
|-
|Tank collisions - why can tanks drive through each other? Weird.
|MORPH
|Good Idea, but severely hindered by lag issues.
|-
|When tanks collide - great opportunity to implement tank damage concept, especially if one of them is moving especially fast, or has momentum flag, etc. Can push a tank off a building if your pushing them from their side.
|Morph
|Idea
|-
|If a tank explodes right next to another tank, the other tank can be destroyed or get damaged
|MORPH
|Idea
|-
|Randomly changing arena - buildings grow, shrink, move
|MORPH
|(Unknown)
|-
|Server option: Cause a player to die if they shoot a teammate (accidentally or otherwise). This would discourage team killers and affect strategy (players are more cautious when shooting near teammates). (how about if you die after you kill teammates n times, and n is reset whenever you die. this will protect people who just do it accidently)
|MORPH
|Implemented (for a LONG time)
|-
|Server option: Make all good flags (except for ID flag) permanent (i.e. you cannot drop a flag unless you are killed). This discourages flag hunting (for GM flag or whatever) and forces players to play (build skill with?) the first flag they pick up until they die
|MORPH
|(Unknown)
|-
|Server option: Have finite ammo for the GM and Laser.
|MORPH
|Implemented (generically- shot limits)
|-
|Damage status- getting hit three (3) times kills you.
|MORPH
|(Unknown)
|-
|Skins or views- In-tank mode, bumper mode, out-of-cab mode, chase mode.
|MORPH
|(Unknown)
|-
|customizable sounds and/or models.
|MORPH
|(Unknown)
|-
|A usable world editor for mac and windows so that more servers are available.
|iPod
|Done
|-
|Better Textures on the buildings and pyramids and more variety of structures.
|iPod
|Done (meshes)
|-
|Ramps and slopes which tanks can drive up.
|iPod
|(Unknown)
|-
|There should be a game of cops and robbers. The teams can change after about 10 mins or so.
|iPod
|(Unknown)
|-
|BZFlag for mac in seperate data and application files.
|iPod
|(Unknown)
|-
|Weapon extention packs.
|iPod
|Huh?
|-
|The ability to choose tanks, but they all die at one shot. maybe the jump height, speed, turn speed, acceleration, size can be preset.
|iPod
|(Unknown)
|-
|The ability to see what the world is like before connecting to the server.
|iPod
|(Unknown)
|-
|Sounds of tanks moving.
|iPod
|(Unknown)
|-
|Handicap. Allow for bad players yo have better properties than the best players (like velocity), so it's a more interesting play for everybody. It'll be server optional and the handicap players are marked in player lists|
|JavierMM
|(Unknown)
|-
|Additional Idea to Handicap:
* Autobalance option. If activated it adds an additional scale factor to the tank wich depends on the score. If the score rises the tank gets bigger and if the score is negative the tank gets smaller then the normal one (The hight of the tank will not be scaled). The strength of the effect should be defined by the server. The tank of an extreme good player will at one point no longer fit trough the teleporters and this will give an additional handicap until his score comes down again.
|Amoc
|(Unknown)
|-
|Have different tank death scenes for the dying tank point of view. I realize there is some time needed for one to die and respawn, but the jumping effect one sees when killed irritates me to no end! I'd be happier if all faded to black or white or orange and had text across the screen saying ""respawning... please wait"" :) Also, when killed and your tank was moving toward a building, it just falls right thru it until it hits the ground.. wrong physics there! Splatter or tumble or shatter or something :)
|Robi
|(Unknown)
|-
|A special FFA Game mode "Team by Flags". This means, same Flag = same Team, so if there is a Tank with Rapid fire, and you pick up Rapid fire, you are automatically handled as Team member (this means, killing the other Tank with Rapid fire will be handled the same way as when killing a team member). YHARG: Funky idea: what about a game mode where teams shared flag abilities? Like, each player on a team's flag applies to the whole team. This could make for some interesting combos...
|Agonizer
|(Unknown)
|-
|Make life trickier for the Rogue Team; with a mix of Rogues and Colored Teams, the Rogues have more targets. This should also change the effect of the Masquerade flag - perhaps your tank is invisible to Rogues (like Cloaking)?
|NickGrim
|(Unknown)
|-
|A server option to make deaths not affect your score unless they were self-inflicted/team (the method used by many online games). This would encourage more aggressive play, because it's worth going out and blasting. As it is, you've got a very good chance by just phantoming/OOing out of the way and keeping you score at zero to stay in the top three places! It would also help fix the rather unfair situation of spawning just below a building on which someone is GM-camping...there's pretty much no way to escape, so you lose a point.
|LionsPhil
|(Unknown)
|-
|Custom color schemes for rogue players. The turret and body components can be chosen to be one of a predefined set of colors (e.g. red, yellow, black, white, blue, green, purple...). The game prohibits choosing a color scheme that matches a team scheme (e.g. red turret with red body) and the limited set stops someone choosing a shade which is nearly a team color (e.g. 0xFE0000 instead of 0xFF0000) (and also save texture memory, I think).
|LionsPhil
|(Unknown)
|-
|Allow a small decal on the back of the top of the tank. (think Half-Life's customizable spraypaint). Possibly also apply it to any held flag?
|LionsPhil
|(Unknown)
|-
|Allow ramps in level designs, so tanks can move to certain other platforms without having to jump. This would require adjusting the engine to allow tanks to angle on the ramps. Reduced speed depending on gradient?
|LionsPhil
|(Unknown)
|-
|What about a radar that only covers visible areas (don't passing through buildings/pyramids) ? This would leads to more placement tactics).
|K<nowiki>'</nowiki>limero
|(Unknown)
|-
|Spread Fire (SF) Flag which fires three shots at the same time. One on the centerline, the other two angled at a quarter degree along either side of the centerline.
|Yohan
|(Unknown)
|-
|World configuration of server options. Sometimes a map is designed for use with specific flags, or perhaps certain flags could be too powerful and you would want to turn them off.
|Yohan
|(Unknown)
|-
|Extending an idea from above regarding teleporters: Make teleporters configurable so that the map designer decides whether bullets or tanks or both can pass through the teleporter. Also, an option which changes the angle at which a bullet or tank will pass through a teleporter. Currently, if a teleporter links back to itself, the shot always returns back at the tank which fired it rather than reflecting.
|Yohan
|(Unknown)
|-
|HUD radar. (We are using this with our local games and love it).
|Yohan
|(Unknown)
|-
|Allow ramps and ability of tanks to drive up ramps. I guess this is a duplicate, but I still like it. (Dragonstar agrees with this too) Please do this!
|Yohan
|(Unknown)
|-
|* Add ice as a terrain feature
|morfie
|(Unknown)
|-
|Server creation option: # of flags holdable at a time
|Dragonstar
|(Unknown)
|-
|Allow custom-made weapons with a Object-Oriented scripting language (sorta like Liero AI uses:
http://helios.et.put.poznan.pl/~sskowron/liero/index.html)!!!
|Dragonstar
|(Unknown)
|-
|Custom-made graphics/objects for weapons and levels
|Dragonstar
|(Unknown)
|-
|Triggers in levels!!!
|Dragonstar
|(Unknown)
|-
|Water Terrain
|Dragonstar
|(Unknown)
|-
|Custom Terrains (select a image to tile, slipperyness, etc.)
|Dragonstar
|(Unknown)
|-
|Option to choose different kinds of tanks. Different tanks could be weighted with different strengths and weaknesses. (almost like having a default flag). Would also need some form of health/damage status measurement, not just single hits. For example, there could be a larger, heavily armored tank that has powerful weapons, but moves slowly, versus a small, light, fast tank which is difficult to hit, but very low armor to protect from hits.
|Cue
|(Unknown)
|-
|Multiple list servers, in case bzflag.org goes down (as it happened around feb. 15. 2004)
|abli
|(Unknown)
|-
|Always random respawn. Currently in CTF games first respawn is at own base. This can be abused by leaving and rejoining to get near base. This leave/rejoing trick is considered to be a mild form of cheating by many. Always random respawn would make it useless.
|abli
|(Unknown)
|-
|Don't show invidual score in CTF games. This might help teamplay as it reduces the incentive to run around as if it would be FFA.
|abli
|(Unknown)
|-
|Give points to the player how captures flag in CTF. (Say, around 4 or so) After all, it is often a bigger job than killing someone.
|abli
|(Unknown)
|-
|volcano (growing red pyramid) that's death to touch and grows during the course of a round and occasionally gives off 'pyroclast flows' aka super bullets. perhaps red-orange color.
|kitchen
|(Unknown)
|-
|multiple (3?) jump stengths mini, normal, max...just the thing to confuse the opponents that expect one and you're off doing the other.
|kitchen
|(Unknown)
|-
|J2ME client (allows one to play on a cell phone), would use radar
|bhtooefr
|(Unknown)
|-
|Multi-monitor support (i.e., radar on one screen, window on another, chat/event log on a third)
|bhtooefr
|(Unknown)
|-
|wraparound world - radar remains centered on your current position. Internally, objects leaving the north border reappear to the south, but from the user's radar / visible perspective, you just see to the horizon. I believe this is how the original Battlezone worked. There are some implications: laser would need a range limit.
|nsayer
|(Unknown)
|-
|wireframe mode! man, this would make the game ten times cooler for nostalgia
|rjbs
|(Unknown)
|-
|Make a part in bzflag to put up a real server. 1st screen has the flags you want, next page is to find the MAP file that you created on your hard drive, next page pick if you want jumping etc.
|Colin
|(Unknown)
|-
|Have part in BZflag so that you can have bots.
|Colin
|(Unknown)
|-
|Toggle radar and message bar on and off with a key on your keyboard.
|Colin
|(Unknown)
|-
|Health, like in a fps. If you get shot from a closer range, you take more damage. When you run out of health, you die. Health pickups in places - not a flag. Although there might be a health generator flag.
|Dan
|(Unknown)
|-
|For above: a "Doctor" flag - shooting someone (similar to thief) either fixes them or, like the above health generator flag, except faster, heals them. Don't shoot the other team!
|Dan
|(Unknown)
|-
|Anti camping. The ability to add "no camping zones" to areas of a map or to the entire map. Campers would be messaged that they're in a no camping zone, better start moving and have a prescribe number of seconds to move away or die. If a player returns to the same NCZ (no camping zone) and receives x warnings then he's disconnected. NCZs could be marked by a different color shade from a "normal" spot and could be exempt to a single team (like at their flag base). It's just a rough idea.
|pherris
|(Unknown)
|-
|Special 'open source' BZFlag version (server and client) which is guaranteed to be compatible with all other BZFlag versions.
|Orca
|(Unknown)
|-
|Trajectory flag and option on servers (Causes bullets to fall (But very slowly)). Bullets will go no lower than standard level, so trajectory is only active if you are jumping, or on a block.
|Dogbert
|(Unknown)
|-
|Moving blocks, so when people put things like the USS Enterprise at the top of their map, it can move around.
|Dogbert
|(Unknown)
|-
|Turret mode, If enabled by the server (Can be manditory with automatic grouping). One user drives and the other shoots, Turret mode tanks get double points (But onyl take one from the target). lost double points if killed. Have double ammo, And controllable speed (Max = _tankSpeed * 2 Min = _tankSpeed). Plus it takes 2 shots to kill a turret mode tank. Points gained and lost by turret tanks are divided evenly between the users, Unless the server is all turret mode, in h which case two users are displayed as one.
|Dogbert
|(Unknown)
|-
|I'd like to see something more interesting done with the sky... maybe there could be a little ufo (easter egg) that would fly around occasionally? Tux on a ufo! ;)
|YHARG
|(Unknown)
|-
|"Super smash bros" style jumping: a server-side option to let tanks jump a second or third time while in the air... changing direction would be possible by jumping with the pointer moved to what direction you'd like to doublejump. The direction change would probably be much less than the maximum tank speed, but maybe that could be a variable too. This would be great for platform maps. and add a way to mix up the classic jump killing that goes on in regular games.
|YHARG
|(Unknown)
|-
|Flag decals: Each flag would have a little icon/decal showing it's type ONLY when held by a player. It's kind of nice to be able to surprise people with an undercover shockwave, but doesn't make sense to have to right click (identify) or check the user list to see what flag someone has.
|YHARG
|(Unknown)
|-
|Ducati/Freestyle "Roles" mode: Make a game mode where players are presented with a list of flag choices (limitable to a few roles, if wanted) at respawn or connect time, and are forced to use this flag for the remainder of their connection/tank life. This would be really useful in the case of stealth vs. seer, where you could choose to be stealth or seer, but couldn't switch between them. Another idea would be high speed vs. quick turn. Or steamroller vs. machine gun... Team play would have the interesting effect of people banding together and people with each role on the team. Especially in stealth vs. seer, where a seer team member could warn the team about enemies! There would be no team flags/bases.
|YHARG
|(Unknown)
|-
|Background music! : (This can be done with an external media player so it shouldn't be the heighest priority, It would be nice to be able to control your music from within BzFlag)
|YHARG
|(Unknown)
|-
|Teleporter flag: Dropped twice, and makes a temporary teleporte on the map (for a set amount of time)
|YHARG
|(Unknown)
|-
|BeamMeUp flag: Tab makes the tank teleport to the highest object directly above it. This would be very useful with high maps, but could encourage camping, and cheating.
|YHARG
|(Unknown)
|-
|Tall tank flag: Like obesity, only makes the tank too tall to maneuver under low objects.
|YHARG
|(Unknown)
|-
|Triplicate/Duplicate/MagicHat flag: Tank gets one or two bot duplicates whose shots do no damage, spawned where it is. They could possibly be respawned when killed. They would tend to stay near the tank.
|YHARG
|(Unknown)
|-
|Sleepwalker Bad Flag: Your tank becomes controlled by a bot. Does not drop until tank is killed. Player's score is changed by bot's performance.
|YHARG
|(Unknown)
|-
|Shield Flag Changes: Give Shield flag a radius, and draw it like a moving less opaque blue shockwave. Any tanks inside the shield radius would be protected, until the shield got hit a certain number of times.
|YHARG
|(Unknown)
|-
|7 words: user freindly bult-in map editor and viewer.
|Efitu
|(Unknown)
|-
|More documentation on scripting world weapons.
|Dogbert
|(Unknown)
|-
|Preset world weapons that can be fired manually by admins from within BzFlag.
|Dogbert
|(Unknown)
|-
|Regicide flag, kills both the tanks you hit and the tank with the highest score on the same team of the tank you hit (Thus giving double points)
|Dogbert
|(Unknown)
|-
|Tank Turret Rotation sideways and up and down(controlable with a "Point of View" on a joystick and keyboard for those who don't have joystick with it)
|Supermatthew
|(Unknown)
|-
|Like Efitu's idea, user freindly built-in map editor and viewer, the current map editor isn't so good, expesaly when you delete stuff it does weard things.
|Supermatthew
|(Unknown)
|-
|The ability to add texture to blocks like if tou wanted to add a street texture and make a road or a weard wall or whatever.
|Supermatthew
|(Unknown)
|-
|more objects ot build with like a ball and cone and cylender and incline planes (/ or \) that tanks can drive up.
|Supermatthew
|(Unknown)
|-
|Moving objects like a wall that could spin on its X Y or Z axis and chose the point were it spins like 5X, 3Y, 0Z away from its center
|Supermatthew
|(Unknown)
|-
|New game called tag were someone is it and they shoot someone else and there it and ect.
|Supermatthew
|(Unknown)
|-
|Also a new game called "Hide and seek" were everyone is clocked(think thats it, were you don't see them on radar) except one who is it. he needs to find someone and shoot them then hese cloked and who was shot is not. Also when someone is shot there sent back to Ground zero( 0X, 0Y, 0Z ) so they can't shoot who ever just shot them.
|Supermatthew
|(Unknown)
|-
|Editable ground hight like hills or something
|Supermatthew
|(Unknown)
|-
|another game called dodge ball were one person can shoot and when someone is hit then they become an observer till the next game and when theres only one person(other than the one whose it) they become it.
|Supermatthew
|(Unknown)
|-
|At our company, we instituted a voluntary policy of dropping flags after 1 kill. Prevents slaughters and keeps things rolling more. It'd be great to be able to have the game do this for us, plus I'd love to see it turned on at external sites.
|TomMatelich
|(Unknown)
|-
|Server option: default powers -- flag(s) that everyone in the game automatically has (this wouldn't count as holding a flag). For example, the current Jumping option would == including Jumping as a default power.
|NebNamwen
|(Unknown)
|}
</div>

[[Category:Development]]

Rejected Ideas

2007-03-17T23:29:07Z

L4m3r:

Rejected Ideas

2007-03-17T23:28:46Z

L4m3r: New page: While suggestions and ideas are always welcome, there are a few things that the BZFlag developers have decided not to include in the game. The reasons very, but most often it's simply a de...

While suggestions and ideas are always welcome, there are a few things that the BZFlag developers have decided not to include in the game. The reasons very, but most often it's simply a design decision.

{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!Rejected Idea
!Reasoning
|-
|Ability to carry multiple flags at once
|This sort of concept would have extreme balance issues. What happens if someone grabbed ST and CL at the same time? they'd be undetectable. Furthermore, some flags simply can't work together- for instance, L and GM.
|-
|Rotating tank turrets
|Controlling a rotating turret would be a nightmare, and would add too much complexity to the game.
|-
|Driving up slopes/pyramids, tilting turrets
|The game developers have decided that tanks should remain level (relative to the ground plane). In other words, it's a design decision.
|-
|Land Mines
|There are two equally-undesirable approaches to land mines:
*Mines that are visible: This would be a useless addition to the game because players could easily drive around the mines.
*Mines that are not visible: Too frustrating. Dying at random without being shot is no fun.
|}

Talk:Ideas

2007-03-16T23:11:25Z

L4m3r:

Should ideas that have already be implemented be deleted? This list is getting kinda long.
:Yes, if they have actually been implemented, they should be removed. We might also think about archiving this page occasionally. Also, [[BZFlagWiki:Sign your posts on talk pages|please sign your comments on talk pages]]. [[User:DTRemenak|DTRemenak]] 18:17, 13 March 2007 (EDT)

:My other concern is how do we manage these ideas? If they get archived, should some stay here (good ones) and if so what would be the criteria? This page makes me kind of uncomfortable from a management position? I'm not sure a wiki is the best place to gather information like this. [[User:DonnyBaker|DonnyBaker]] 05:44, 14 March 2007 (EDT)

:At least an unprotected one. If it was protected and had "real" approved ideas, it would be different. [[User:DonnyBaker|DonnyBaker]] 13:05, 14 March 2007 (EDT)

::There's no point in having a protected ideas page, we have the SF.net trackers, the enhancements forum on bzbb, and so on for that. I'm not quite sure what the expected usage of this page was when it was created on the old wiki, and the only real use I see for it now is that it allows unstructured collaborative editing (which apparently isn't used, since everyone seems to sign their ideas...). [[User:DTRemenak|DTRemenak]] 13:12, 14 March 2007 (EDT)

I'm working on conversion to a table, and afterward I will remove old ideas and sort them into categories. Perhaps a page dedicated to "rejected ideas" would be a good idea. -L4m3r

Ideas

2007-03-16T23:06:58Z

L4m3r:

{{Old}}
Feel free to make changes and updates to this page whenever possible. If you have any questions, feel free to [[Getting Help|ask for help]]. If you wish to make major changes to this page (i.e. remove large amounts of old ideas), please warn us ahead of time.

<b>NOTE: Work is in progress on this page. I'm converting to to a tabular format, and will then clean up and sort the ideas into categories. Please stand by. -L4m3r</b>

NOTE: These are just possiblilities. We won't be implementing everything here.<br>
NOTE: Flag ideas should be placed on [[Flag Ideas]]. Any other ideas can be placed here.

Status may include personal comments by developers.

== Adding ideas ==
* All ideas should be categorized and should be prefixed with a *.
* Sign your idea with four tildes: <nowiki>~~~~</nowiki>
* Make sense!

== Ideas include: ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!Idea
!Submitter
!Status/approval
|-
|Add support for 5 (or more) button mice
|(Unknown)
|Great Idea
|-
|Sort player list by team
|(Unknown)
|Implemented (how?)
|-
|Make option to show previous players list
|(Unknown)
|Idea
|-
|Anti-cheating measures detecting cheating clients/servers, kicking them out automatically or by vote, etc. I will push to have this implemented in version 1.8.
|(Unknown)
|Some anti-cheating measures are in 1.7G2, more work to follow. Great Idea (delete this idea, it's ancient?)
|-
|Better network handling
|(Unknown)
|Work in progress.
|-
|Better physics
|(Unknown)
|Planning, some changes in CVS.
|-
|Map editor
|(Unknown)
|Windows, Linux and Java2 editors are working, Linux editor in CVS, I want one using BZFlag's own engine.
|-
|server-side respawn position
|(Unknown)
|Implemented in [[BZFlag 2.0.0]]
|-
|2 or 3 teams as well as the current 4
|(Unknown)
|Man, this gotta be old. BZFlag used to only work with 4 teams??
|-
|Tounament mode
|(Unknown)
|Idea (Great Idea?)
|-
|Ability to define flags allowed / not allowed in world file
|(Unknown)
|Idea
|-
|Materials that don't allow OO and PZ to go through
|(Unknown)
|Would be nice for multilevel worlds made with the new ability to have objects above the ground. (Sounds awesome! [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT))
|-
|Better robot AI
|(Unknown)
|Idea, don't know if players would like it or not in multiplayer game. Pluggable or scriptable robot AI , maybe? - Code must be restructured first (Server side bots are coming! [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT))
|-
|Option to search for servers in list. It gets really annoying if you want to find a server and you have to go through all the pages, as there are over 10 now.
|Spazzy McGee
|Implemented in [[BZFlag 2.0.4]]
|-
|When you shoot someone on your own team, instead of both of you blowing up, neither is destroyed, and their score goes up one, while your's goes down one. This would make teamkilling impossible and greatly discourage traitors as well.
|Trigger Happy Nerd
|But then couldn't cheaters spawn two clients and ramp up their scores by teamkilling their other login? --YHARG
|-
|SELF-DESTRUCT BLAST RADIUS: Self Destruct (delete key) should have a blast radius similar to Shock Wave, perhaps larger. If you get shot during the self-destruct count down, that should also trigger the same blast. If I gotta go, I want to take someone with me.
|BearRiver
|(Unknown)
|-
|Make ALL server options available from the menus
|MORPH
|Idea
|-
|Ability to toggle display of player emails (some are so long they mess up the score display)
|MORPH
|Idea
|-
|Word wrap long messages - they get cut off for those with low-resolution displays
|MORPH
|Done??
|-
|Improvements to radar: Color-coded bullets, brighter bullets (may have to be larger if already using brightest color), better distinction between blue players and pyramids
|MORPH
|Done
|-
|Better positioning of tanks
|MORPH
|BZFlag already does this, but the algorithm is bad. Needs work.
|-
|3-second (or however long) 'invulnerability' for incoming tanks - but they can't shoot
|MORPH
|Idea.
|-
|Ability to turn off ricochet for laser flag but allow ricochet for bullets... or let them bounce only n times.. OR implement mirror buildings/walls. Should go for some interesting self-kills when combined with the no-radar/bullet bounce
|MORPH
|Idea
|-
|Smart LockOn for GM - won't lock on to your teammates (configurable in server)
|MORPH
|Idea. (M. Jetleb -> I don't like this idea, there should be at least *some* risks to using this weapon. Personally, I think there should be more (not fewer) risks to holding this weapon; I'd like to see the thing overheat and explode (killing the holder) if it's fired too often in a short period of time)
|-
|Small jumps
|MORPH
|Idea
|-
|Differently-shaped teleporters (circles, triangles, etc.)
|MORPH
|Idea, probably low priority
|-
|360 degree teleports - hit a spot on the ground or in the air from any direction and you teleport
|MORPH
|Idea
|-
|Configurable random teleporters - teleports to a different location every time
|MORPH
|Idea
|-
|Allow different physical properties on top of buildings (momentum, etc.)
|MORPH
|Idea, goes with my ""materials"" idea.
|-
|Allow higher wall-height around arena (ricochet at higher heights) - or no walls defining the boundaries - just a line. (ricochet only off buildings & pyramids)
|MORPH
|Idea
|-
|Server option for genocide flag - if you're killed while you have it, your team dies :^)
|MORPH
|Idea
|-
|for broadband or LAN connections - voice chat for teams
|MORPH
|Idea, but I really think that you can do this with another service; I'm not sure if being part of BZFlag would be a good idea due to size and bandwidth issues.
|-
|Separate windows for player messages & server messages
|MORPH
|Good idea.
|-
|Message log
|MORPH
|Good idea.
|-
|Serious multithreaded design - shouldn't lock up interface while looking for servers, or doing anything else. This program is way-unstable on Windows
|MORPH
|We're working on these problems; many complaints are due to people still using old servers/clients.
|-
|Ability to configure server to turn somethings off or on depending on number of players - for instance, turn off ricochet after a certain number of players are connected, turn off GM & laser if a certain number of players aren't playing (GM & Laser with 2 players is kinda ridiculous)
|MORPH
|Idea
|-
|'Fox & Hound' scenario - highest player automatically becomes own team, all other plays on another team - kill the 'fox' (play with highest score).
|MORPH
|Good Idea, I'd like to see more ways to play BZFlag. (bhtooefr: Rabbit is very similar to this)
|-
|Higher score(s) players lose abilities (bigger tanks, can't pick up flags, momentum, whatever)
|MORPH
|Idea
|-
|Some type of BZFlag GUID* to ban players who cheat - won't accept players who disable their GUID, etc.

<nowiki>*</nowiki>Global Unique Identifier, sort of like an IP addrss, but permanent. Usually a number. Problem occurs when you lose your GUID (have to reformat your HD, etc. How do you keep someone from hacking their GUID, or setting up a modified BZFlag server for identity theft, etc.
|MORPH
|What is a GUID??
|-
|Single/multiple-use flags (or they instantly change type after being used) (configurable on a flag-by-flag basis: e.g. laser & GM one-use only before they drop/disappear)
|MORPH
|Good idea, especially with the more powerful flags.
|-
|Change graphic format to PNG so new 'skins' can be created. Optional use of server-defined skin. Client can use it or not (wouldn't really matter)
|MORPH
|In CVS for 1.8.
|-
|Tank avatars (uploadable tank images) - have to think about shapes, though - someone could make a 1x1x1 pixel tank - that would suck - or a tank that looks like a building or pyramid. Clients don't have to accept downloading of avators (just view other tanks in default mode). Or just s-e-l-e-c-t from a certain number of predefined avatars that could come with the bzflag distribution. Or client provides a URL to download their avatar (saves server bandwidth).
|MORPH
|Idea, but might not be implemented. Requires discussion; we may want to consider making the computer force a minimum size or something similar. *How about uploadable flag graphics?
|-
|To prevent cheating - the server determines what flags & abilities each tank has (possible?)
|MORPH
|Idea, but seriously being considered. This would also have the advantage of allowing different versions of clients and servers to work together. Yes, it's possible, but this type of change will mean a change in the network protocols.
|-
|Send message to an individual, even if they're not on your team
|MORPH
|done
|-
|Ability to change elevation of tank barrel & direction of turret (without jumping up or turning tank) (complex interface issues - super-low priority)
|MORPH
|Idea. Turret rotation rejected: The game is too fast for this to be useful, and would probably kill the game. *How about a new gameplay mode? Takes two to tank. One to ride turret, the other drives. KIA switches positions. "Teamplay" but all in one tank.
|-
|Much better arena design capabilities - bridges over ditches, etc.
|MORPH
|Good idea. This along with some new physics (which I hope to propose soon -Jeremiah), and BZFlag will be much more interesting.
|-
|Concept of a tank that can take damage without being destroyed immediately - slows down, takes a hit in a tread and turns slowly in whatever direction, etc.
|MORPH
|Good idea, but must be optional (server option). Might be rejected, since BZFlag is, by nature, a fast paced game. *Loses ability to shoot, runs and grabs a restore flag?
|-
|'Kamikaze' option for players - can take someone out by suicide
|MORPH
|Idea. Server option if implemented.
|-
|Server option: everyone is radar-stealthed by default unless you get a 'radar' flag. You can still see all buildings, pyramids, teleports, and arena walls, though.
|MORPH
|Good idea. Make them use their window. ;)(M. Jetleb -> Given the fairly narrow field of view out the window and the time it takes to turn a tank all the way around for a look-see, I think this could be frustrating. How about everyone starts out with minimum range radar instead and gets longer ranges with an appropriate flag?)
|-
|Option for above: if you pick up GM or Laser, you're visible on radar to everyone whether they've got a radar flag or not
|MORPH
|Good idea
|-
|Selectable 'ricochet' fire - hold down shift key or something and your bullets won't ricochet
|MORPH
|Idea.
|-
|Server option - tanks only have a certain number of times they can jump (gets reset when you get killed)
|MORPH
|Idea.
|-
|Multiple-shields (server option for shield flags, or can be random - can get hit x number of times)
|MORPH
|Idea
|-
|Ability to damage or destroy buildings/pyramids/teleporters
|MORPH
|Idea (M. Jetleb - probably a good idea for timed games, where the building can be reset after a reasonable amount of time, but can you imagine what the field would look like for a perpetual game that's been running for days? There has to be some way to reset this. Also what happens if someone shoots the bottom out of a building? Does the building collapse or just remain suspended? This could get complicated.)
|-
|Server config to make bullets NOT go through teleporters
|MORPH
|Idea
|-
|Holographic buildings - can't see what's behind them, but can shoot through them (great for the radarless-option above)[M. Jetleb -> how does not being able to see through a building help when you're radarless?]. Can't tell the difference on radar between them and regular buildings
|MORPH
|Idea, could be a materials property.
|-
|SandTraps - tank gets stuck there
|MORPH
|Idea (aren't there enough incredibly annoying ways for tanks to get stuck on pyramids etc. already? --pediddle)
|-
|Configurable 'radarless' and/or 'blind' zones in the arena - can't see what's in there on radar or via visuals
|MORPH
|Idea
|-
|'Fog' area in arena - impairs use of laser
|MORPH
|Idea
|-
|Connection-quality restrictions - restriction players based on connection quality - if they're having connection problems, server can drop them (after informing them what's going on)
|MORPH
|Implemented - also, throttling is implemented; people with high framerates were sending a lot of messages, clogging things up for people with slower connections.
|-
|Ability for a team to vote to 'banish' someone from their team
|MORPH
|Idea
|-
|Send message to everyone 'but' specified player (crosses team boundaries, or not)
|MORPH
|Idea. Hmm. Everybody BUT a specified player? [M. Jetleb -> as in: "Let's all get the GM guy" without the GM guy knowing he's facing a co-ordinated attack - I like this idea)
|-
|Non-solid buildings - ability to make tunnels through buildings, etc.
|MORPH
|Idea.
|-
|Tank collisions - why can tanks drive through each other? Weird.
|MORPH
|Good Idea, but severely hindered by lag issues.
|-
|When tanks collide - great opportunity to implement tank damage concept, especially if one of them is moving especially fast, or has momentum flag, etc. Can push a tank off a building if your pushing them from their side.
|Morph
|Idea
|-
|If a tank explodes right next to another tank, the other tank can be destroyed or get damaged
|MORPH
|Idea
|-
|Randomly changing arena - buildings grow, shrink, move
|MORPH
|(Unknown)
|-
|Server option: Cause a player to die if they shoot a teammate (accidentally or otherwise). This would discourage team killers and affect strategy (players are more cautious when shooting near teammates). (how about if you die after you kill teammates n times, and n is reset whenever you die. this will protect people who just do it accidently)
|MORPH
|Implemented (for a LONG time)
|-
|Server option: Make all good flags (except for ID flag) permanent (i.e. you cannot drop a flag unless you are killed). This discourages flag hunting (for GM flag or whatever) and forces players to play (build skill with?) the first flag they pick up until they die
|MORPH
|(Unknown)
|-
|Server option: Have finite ammo for the GM and Laser.
|MORPH
|Implemented (generically- shot limits)
|-
|Damage status- getting hit three (3) times kills you.
|MORPH
|(Unknown)
|-
|Skins or views- In-tank mode, bumper mode, out-of-cab mode, chase mode.
|MORPH
|(Unknown)
|-
|customizable sounds and/or models.
|MORPH
|(Unknown)
|-
|A usable world editor for mac and windows so that more servers are available.
|iPod
|Done
|-
|Better Textures on the buildings and pyramids and more variety of structures.
|iPod
|Done (meshes)
|-
|Ramps and slopes which tanks can drive up.
|iPod
|(Unknown)
|-
|There should be a game of cops and robbers. The teams can change after about 10 mins or so.
|iPod
|(Unknown)
|-
|BZFlag for mac in seperate data and application files.
|iPod
|(Unknown)
|-
|Weapon extention packs.
|iPod
|Huh?
|-
|The ability to choose tanks, but they all die at one shot. maybe the jump height, speed, turn speed, acceleration, size can be preset.
|iPod
|(Unknown)
|-
|The ability to see what the world is like before connecting to the server.
|iPod
|(Unknown)
|-
|Sounds of tanks moving.
|iPod
|(Unknown)
|-
|Handicap. Allow for bad players yo have better properties than the best players (like velocity), so it's a more interesting play for everybody. It'll be server optional and the handicap players are marked in player lists|
|JavierMM
|(Unknown)
|-
|Additional Idea to Handicap:
* Autobalance option. If activated it adds an additional scale factor to the tank wich depends on the score. If the score rises the tank gets bigger and if the score is negative the tank gets smaller then the normal one (The hight of the tank will not be scaled). The strength of the effect should be defined by the server. The tank of an extreme good player will at one point no longer fit trough the teleporters and this will give an additional handicap until his score comes down again.
|Amoc
|(Unknown)
|-
|Have different tank death scenes for the dying tank point of view. I realize there is some time needed for one to die and respawn, but the jumping effect one sees when killed irritates me to no end! I'd be happier if all faded to black or white or orange and had text across the screen saying ""respawning... please wait"" :) Also, when killed and your tank was moving toward a building, it just falls right thru it until it hits the ground.. wrong physics there! Splatter or tumble or shatter or something :)
|Robi
|(Unknown)
|-
|A special FFA Game mode "Team by Flags". This means, same Flag = same Team, so if there is a Tank with Rapid fire, and you pick up Rapid fire, you are automatically handled as Team member (this means, killing the other Tank with Rapid fire will be handled the same way as when killing a team member). YHARG: Funky idea: what about a game mode where teams shared flag abilities? Like, each player on a team's flag applies to the whole team. This could make for some interesting combos...
|Agonizer
|(Unknown)
|-
|Make life trickier for the Rogue Team; with a mix of Rogues and Colored Teams, the Rogues have more targets. This should also change the effect of the Masquerade flag - perhaps your tank is invisible to Rogues (like Cloaking)?
|NickGrim
|(Unknown)
|-
|A server option to make deaths not affect your score unless they were self-inflicted/team (the method used by many online games). This would encourage more aggressive play, because it's worth going out and blasting. As it is, you've got a very good chance by just phantoming/OOing out of the way and keeping you score at zero to stay in the top three places! It would also help fix the rather unfair situation of spawning just below a building on which someone is GM-camping...there's pretty much no way to escape, so you lose a point.
|LionsPhil
|(Unknown)
|-
|Custom color schemes for rogue players. The turret and body components can be chosen to be one of a predefined set of colors (e.g. red, yellow, black, white, blue, green, purple...). The game prohibits choosing a color scheme that matches a team scheme (e.g. red turret with red body) and the limited set stops someone choosing a shade which is nearly a team color (e.g. 0xFE0000 instead of 0xFF0000) (and also save texture memory, I think).
|LionsPhil
|(Unknown)
|-
|Allow a small decal on the back of the top of the tank. (think Half-Life's customizable spraypaint). Possibly also apply it to any held flag?
|LionsPhil
|(Unknown)
|-
|Allow ramps in level designs, so tanks can move to certain other platforms without having to jump. This would require adjusting the engine to allow tanks to angle on the ramps. Reduced speed depending on gradient?
|LionsPhil
|(Unknown)
|-
|What about a radar that only covers visible areas (don't passing through buildings/pyramids) ? This would leads to more placement tactics).
|K<nowiki>'</nowiki>limero
|(Unknown)
|-
|Spread Fire (SF) Flag which fires three shots at the same time. One on the centerline, the other two angled at a quarter degree along either side of the centerline.
|Yohan
|(Unknown)
|-
|World configuration of server options. Sometimes a map is designed for use with specific flags, or perhaps certain flags could be too powerful and you would want to turn them off.
|Yohan
|(Unknown)
|-
|Extending an idea from above regarding teleporters: Make teleporters configurable so that the map designer decides whether bullets or tanks or both can pass through the teleporter. Also, an option which changes the angle at which a bullet or tank will pass through a teleporter. Currently, if a teleporter links back to itself, the shot always returns back at the tank which fired it rather than reflecting.
|Yohan
|(Unknown)
|-
|HUD radar. (We are using this with our local games and love it).
|Yohan
|(Unknown)
|-
|Allow ramps and ability of tanks to drive up ramps. I guess this is a duplicate, but I still like it. (Dragonstar agrees with this too) Please do this!
|Yohan
|(Unknown)
|-
|* Add ice as a terrain feature
|morfie
|(Unknown)
|}
</div>

Idea(s) From Dragonstar. Items marked with a !!! are what I want most
* Server creation option: # of flags holdable at a time
* Allow custom-made weapons with a Object-Oriented scripting language (sorta like Liero AI uses: http://helios.et.put.poznan.pl/~sskowron/liero/index.html)!!!
* Custom-made graphics/objects for weapons and levels
* Triggers in levels!!!
* Water Terrain
* Custom Terrains (select a image to tile, slipperyness, etc.)
More coming later :-)

Ideas From Cue:
* Option to choose different kinds of tanks. Different tanks could be weighted with different strengths and weaknesses. (almost like having a default flag). Would also need some form of health/damage status measurement, not just single hits. For example, there could be a larger, heavily armored tank that has powerful weapons, but moves slowly, versus a small, light, fast tank which is difficult to hit, but very low armor to protect from hits.
* Land mine flag?

Ideas from abli:
* Multiple list servers, in case bzflag.org goes down (as it happened around feb. 15. 2004)
* Always random respawn. Currently in CTF games first respawn is at own base. This can be abused by leaving and rejoining to get near base. This leave/rejoing trick is considered to be a mild form of cheating by many. Always random respawn would make it useless.
* Don't show invidual score in CTF games. This might help teamplay as it reduces the incentive to run around as if it would be FFA.
* Give points to the player how captures flag in CTF. (Say, around 4 or so) After all, it is often a bigger job than killing someone.

Idea from kitchen:
* volcano (growing red pyramid) that's death to touch and grows during the course of a round and occasionally gives off 'pyroclast flows' aka super bullets. perhaps red-orange color.
* multiple (3?) jump stengths mini, normal, max...just the thing to confuse the opponents that expect one and you're off doing the other.

Idea from bhtooefr:
* J2ME client (allows one to play on a cell phone), would use radar
* Multi-monitor support (i.e., radar on one screen, window on another, chat/event log on a third)

Idea from nsayer:
* wraparound world - radar remains centered on your current position. Internally, objects leaving the north border reappear to the south, but from the user's radar / visible perspective, you just see to the horizon. I believe this is how the original Battlezone worked. There are some implications: laser would need a range limit.

Idea from rjbs:
* wireframe mode! man, this would make the game ten times cooler for nostalgia

Idea from Colin:
* Make a part in bzflag to put up a real server. 1st screen has the flags you want, next page is to find the MAP file that you created on your hard drive, next page pick if you want jumping etc.
* Have part in BZflag so that you can have bots.
* Toggle radar and message bar on and off with a key on your keyboard.

Idea from Dan:
* Health, like in a fps. If you get shot from a closer range, you take more damage. When you run out of health, you die. Health pickups in places - not a flag. Although there might be a health generator flag.
* For above: a "Doctor" flag - shooting someone (similar to thief) either fixes them or, like the above health generator flag, except faster, heals them. Don't shoot the other team!

Idea from pherris:
* Anti camping. The ability to add "no camping zones" to areas of a map or to the entire map. Campers would be messaged that they're in a no camping zone, better start moving and have a prescribe number of seconds to move away or die. If a player returns to the same NCZ (no camping zone) and receives x warnings then he's disconnected. NCZs could be marked by a different color shade from a "normal" spot and could be exempt to a single team (like at their flag base). It's just a rough idea.

Idea from Orca
* Special 'open source' BZFlag version (server and client) which is guaranteed to be compatible with all other BZFlag versions.

Idea from Dogbert
* Trajectory flag and option on servers (Causes bullets to fall (But very slowly)). Bullets will go no lower than standard level, so trajectory is only active if you are jumping, or on a block.
* Moving blocks, so when people put things like the USS Enterprise at the top of their map, it can move around.
* Turret mode, If enabled by the server (Can be manditory with automatic grouping). One user drives and the other shoots, Turret mode tanks get double points (But onyl take one from the target). lost double points if killed. Have double ammo, And controllable speed (Max = _tankSpeed * 2 Min = _tankSpeed). Plus it takes 2 shots to kill a turret mode tank. Points gained and lost by turret tanks are divided evenly between the users, Unless the server is all turret mode, in h which case two users are displayed as one.

Ideas from YHARG:
* I'd like to see something more interesting done with the sky... maybe there could be a little ufo (easter egg) that would fly around occasionally? Tux on a ufo! ;)
* "Super smash bros" style jumping: a server-side option to let tanks jump a second or third time while in the air... changing direction would be possible by jumping with the pointer moved to what direction you'd like to doublejump. The direction change would probably be much less than the maximum tank speed, but maybe that could be a variable too. This would be great for platform maps. and add a way to mix up the classic jump killing that goes on in regular games.
* Flag decals: Each flag would have a little icon/decal showing it's type ONLY when held by a player. It's kind of nice to be able to surprise people with an undercover shockwave, but doesn't make sense to have to right click (identify) or check the user list to see what flag someone has.
* Ducati/Freestyle "Roles" mode: Make a game mode where players are presented with a list of flag choices (limitable to a few roles, if wanted) at respawn or connect time, and are forced to use this flag for the remainder of their connection/tank life. This would be really useful in the case of stealth vs. seer, where you could choose to be stealth or seer, but couldn't switch between them. Another idea would be high speed vs. quick turn. Or steamroller vs. machine gun... Team play would have the interesting effect of people banding together and people with each role on the team. Especially in stealth vs. seer, where a seer team member could warn the team about enemies! There would be no team flags/bases.
* Background music! : (This can be done with an external media player so it shouldn't be the heighest priority, It would be nice to be able to control your music from within BzFlag)
* Teleporter flag: Dropped twice, and makes a temporary teleporte on the map (for a set amount of time)
* BeamMeUp flag: Tab makes the tank teleport to the highest object directly above it. This would be very useful with high maps, but could encourage camping, and cheating.
* Tall tank flag: Like obesity, only makes the tank too tall to maneuver under low objects.
* Triplicate/Duplicate/MagicHat flag: Tank gets one or two bot duplicates whose shots do no damage, spawned where it is. They could possibly be respawned when killed. They would tend to stay near the tank.
* Sleepwalker Bad Flag: Your tank becomes controlled by a bot. Does not drop until tank is killed. Player's score is changed by bot's performance.
* Shield Flag Changes: Give Shield flag a radius, and draw it like a moving less opaque blue shockwave. Any tanks inside the shield radius would be protected, until the shield got hit a certain number of times.

Idea from Efitu:
* 7 words: user freindly bult-in map editor and viewer.

Ideas from Dogbert.
* More documentation on scripting world weapons.
* Preset world weapons that can be fired manually by admins from within BzFlag.
* Regicide flag, kills both the tanks you hit and the tank with the highest score on the same team of the tank you hit (Thus giving double points)

Idea from Supermatthew:
* Tank Turret Rotation sideways and up and down(controlable with a "Point of View" on a joystick and keyboard for those who don't have joystick with it)
* Like Efitu's idea, user freindly built-in map editor and viewer, the current map editor isn't so good, expesaly when you delete stuff it does weard things.
* The ability to add texture to blocks like if tou wanted to add a street texture and make a road or a weard wall or whatever.
* more objects ot build with like a ball and cone and cylender and incline planes (/ or \) that tanks can drive up.
* Moving objects like a wall that could spin on its X Y or Z axis and chose the point were it spins like 5X, 3Y, 0Z away from its center
* New game called tag were someone is it and they shoot someone else and there it and ect.
* Also a new game called "Hide and seek" were everyone is clocked(think thats it, were you don't see them on radar) except one who is it. he needs to find someone and shoot them then hese cloked and who was shot is not. Also when someone is shot there sent back to Ground zero( 0X, 0Y, 0Z ) so they can't shoot who ever just shot them.
* Editable ground hight like hills or something
* another game called dodge ball were one person can shoot and when someone is hit then they become an observer till the next game and when theres only one person(other than the one whose it) they become it.

Idea from TomMatelich:
* At our company, we instituted a voluntary policy of dropping flags after 1 kill. Prevents slaughters and keeps things rolling more. It'd be great to be able to have the game do this for us, plus I'd love to see it turned on at external sites.

Ideas from NebNamwen:
* Server option: default powers -- flag(s) that everyone in the game automatically has (this wouldn't count as holding a flag). For example, the current Jumping option would == including Jumping as a default power.

[[Category:Development]]

Ideas

2007-03-16T23:05:12Z

L4m3r: /* Ideas include: */

{{Old}}
Feel free to make changes and updates to this page whenever possible. If you have any questions, feel free to [[Getting Help|ask for help]]. If you wish to make major changes to this page (i.e. remove large amounts of old ideas), please warn us ahead of time.

NOTE: These are just possiblilities. We won't be implementing everything here.<br>
NOTE: Flag ideas should be placed on [[Flag Ideas]]. Any other ideas can be placed here.

Status may include personal comments by developers.

== Adding ideas ==
* All ideas should be categorized and should be prefixed with a *.
* Sign your idea with four tildes: <nowiki>~~~~</nowiki>
* Make sense!

== Ideas include: ==
<div align="center">
{| cellpadding="2" cellspacing="1" border="1" width="100%"
|- style="background-color:#ffff88;"
!Idea
!Submitter
!Status/approval
|-
|Add support for 5 (or more) button mice
|(Unknown)
|Great Idea
|-
|Sort player list by team
|(Unknown)
|Implemented (how?)
|-
|Make option to show previous players list
|(Unknown)
|Idea
|-
|Anti-cheating measures detecting cheating clients/servers, kicking them out automatically or by vote, etc. I will push to have this implemented in version 1.8.
|(Unknown)
|Some anti-cheating measures are in 1.7G2, more work to follow. Great Idea (delete this idea, it's ancient?)
|-
|Better network handling
|(Unknown)
|Work in progress.
|-
|Better physics
|(Unknown)
|Planning, some changes in CVS.
|-
|Map editor
|(Unknown)
|Windows, Linux and Java2 editors are working, Linux editor in CVS, I want one using BZFlag's own engine.
|-
|server-side respawn position
|(Unknown)
|Implemented in [[BZFlag 2.0.0]]
|-
|2 or 3 teams as well as the current 4
|(Unknown)
|Man, this gotta be old. BZFlag used to only work with 4 teams??
|-
|Tounament mode
|(Unknown)
|Idea (Great Idea?)
|-
|Ability to define flags allowed / not allowed in world file
|(Unknown)
|Idea
|-
|Materials that don't allow OO and PZ to go through
|(Unknown)
|Would be nice for multilevel worlds made with the new ability to have objects above the ground. (Sounds awesome! [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT))
|-
|Better robot AI
|(Unknown)
|Idea, don't know if players would like it or not in multiplayer game. Pluggable or scriptable robot AI , maybe? - Code must be restructured first (Server side bots are coming! [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT))
|-
|Option to search for servers in list. It gets really annoying if you want to find a server and you have to go through all the pages, as there are over 10 now.
|Spazzy McGee
|Implemented in [[BZFlag 2.0.4]]
|-
|When you shoot someone on your own team, instead of both of you blowing up, neither is destroyed, and their score goes up one, while your's goes down one. This would make teamkilling impossible and greatly discourage traitors as well.
|Trigger Happy Nerd
|But then couldn't cheaters spawn two clients and ramp up their scores by teamkilling their other login? --YHARG
|-
|SELF-DESTRUCT BLAST RADIUS: Self Destruct (delete key) should have a blast radius similar to Shock Wave, perhaps larger. If you get shot during the self-destruct count down, that should also trigger the same blast. If I gotta go, I want to take someone with me.
|BearRiver
|(Unknown)
|-
|Make ALL server options available from the menus
|MORPH
|Idea
|-
|Ability to toggle display of player emails (some are so long they mess up the score display)
|MORPH
|Idea
|-
|Word wrap long messages - they get cut off for those with low-resolution displays
|MORPH
|Done??
|-
|Improvements to radar: Color-coded bullets, brighter bullets (may have to be larger if already using brightest color), better distinction between blue players and pyramids
|MORPH
|Done
|-
|Better positioning of tanks
|MORPH
|BZFlag already does this, but the algorithm is bad. Needs work.
|-
|3-second (or however long) 'invulnerability' for incoming tanks - but they can't shoot
|MORPH
|Idea.
|-
|Ability to turn off ricochet for laser flag but allow ricochet for bullets... or let them bounce only n times.. OR implement mirror buildings/walls. Should go for some interesting self-kills when combined with the no-radar/bullet bounce
|MORPH
|Idea
|-
|Smart LockOn for GM - won't lock on to your teammates (configurable in server)
|MORPH
|Idea. (M. Jetleb -> I don't like this idea, there should be at least *some* risks to using this weapon. Personally, I think there should be more (not fewer) risks to holding this weapon; I'd like to see the thing overheat and explode (killing the holder) if it's fired too often in a short period of time)
|-
|Small jumps
|MORPH
|Idea
|-
|Differently-shaped teleporters (circles, triangles, etc.)
|MORPH
|Idea, probably low priority
|-
|360 degree teleports - hit a spot on the ground or in the air from any direction and you teleport
|MORPH
|Idea
|-
|Configurable random teleporters - teleports to a different location every time
|MORPH
|Idea
|-
|Allow different physical properties on top of buildings (momentum, etc.)
|MORPH
|Idea, goes with my ""materials"" idea.
|-
|Allow higher wall-height around arena (ricochet at higher heights) - or no walls defining the boundaries - just a line. (ricochet only off buildings & pyramids)
|MORPH
|Idea
|-
|Server option for genocide flag - if you're killed while you have it, your team dies :^)
|MORPH
|Idea
|-
|for broadband or LAN connections - voice chat for teams
|MORPH
|Idea, but I really think that you can do this with another service; I'm not sure if being part of BZFlag would be a good idea due to size and bandwidth issues.
|-
|Separate windows for player messages & server messages
|MORPH
|Good idea.
|-
|Message log
|MORPH
|Good idea.
|-
|Serious multithreaded design - shouldn't lock up interface while looking for servers, or doing anything else. This program is way-unstable on Windows
|MORPH
|We're working on these problems; many complaints are due to people still using old servers/clients.
|-
|Ability to configure server to turn somethings off or on depending on number of players - for instance, turn off ricochet after a certain number of players are connected, turn off GM & laser if a certain number of players aren't playing (GM & Laser with 2 players is kinda ridiculous)
|MORPH
|Idea
|-
|'Fox & Hound' scenario - highest player automatically becomes own team, all other plays on another team - kill the 'fox' (play with highest score).
|MORPH
|Good Idea, I'd like to see more ways to play BZFlag. (bhtooefr: Rabbit is very similar to this)
|-
|Higher score(s) players lose abilities (bigger tanks, can't pick up flags, momentum, whatever)
|MORPH
|Idea
|-
|Some type of BZFlag GUID* to ban players who cheat - won't accept players who disable their GUID, etc.

<nowiki>*</nowiki>Global Unique Identifier, sort of like an IP addrss, but permanent. Usually a number. Problem occurs when you lose your GUID (have to reformat your HD, etc. How do you keep someone from hacking their GUID, or setting up a modified BZFlag server for identity theft, etc.
|MORPH
|What is a GUID??
|-
|Single/multiple-use flags (or they instantly change type after being used) (configurable on a flag-by-flag basis: e.g. laser & GM one-use only before they drop/disappear)
|MORPH
|Good idea, especially with the more powerful flags.
|-
|Change graphic format to PNG so new 'skins' can be created. Optional use of server-defined skin. Client can use it or not (wouldn't really matter)
|MORPH
|In CVS for 1.8.
|-
|Tank avatars (uploadable tank images) - have to think about shapes, though - someone could make a 1x1x1 pixel tank - that would suck - or a tank that looks like a building or pyramid. Clients don't have to accept downloading of avators (just view other tanks in default mode). Or just s-e-l-e-c-t from a certain number of predefined avatars that could come with the bzflag distribution. Or client provides a URL to download their avatar (saves server bandwidth).
|MORPH
|Idea, but might not be implemented. Requires discussion; we may want to consider making the computer force a minimum size or something similar. *How about uploadable flag graphics?
|-
|To prevent cheating - the server determines what flags & abilities each tank has (possible?)
|MORPH
|Idea, but seriously being considered. This would also have the advantage of allowing different versions of clients and servers to work together. Yes, it's possible, but this type of change will mean a change in the network protocols.
|-
|Send message to an individual, even if they're not on your team
|MORPH
|done
|-
|Ability to change elevation of tank barrel & direction of turret (without jumping up or turning tank) (complex interface issues - super-low priority)
|MORPH
|Idea. Turret rotation rejected: The game is too fast for this to be useful, and would probably kill the game. *How about a new gameplay mode? Takes two to tank. One to ride turret, the other drives. KIA switches positions. "Teamplay" but all in one tank.
|-
|Much better arena design capabilities - bridges over ditches, etc.
|MORPH
|Good idea. This along with some new physics (which I hope to propose soon -Jeremiah), and BZFlag will be much more interesting.
|-
|Concept of a tank that can take damage without being destroyed immediately - slows down, takes a hit in a tread and turns slowly in whatever direction, etc.
|MORPH
|Good idea, but must be optional (server option). Might be rejected, since BZFlag is, by nature, a fast paced game. *Loses ability to shoot, runs and grabs a restore flag?
|-
|'Kamikaze' option for players - can take someone out by suicide
|MORPH
|Idea. Server option if implemented.
|-
|Server option: everyone is radar-stealthed by default unless you get a 'radar' flag. You can still see all buildings, pyramids, teleports, and arena walls, though.
|MORPH
|Good idea. Make them use their window. ;)(M. Jetleb -> Given the fairly narrow field of view out the window and the time it takes to turn a tank all the way around for a look-see, I think this could be frustrating. How about everyone starts out with minimum range radar instead and gets longer ranges with an appropriate flag?)
|-
|Option for above: if you pick up GM or Laser, you're visible on radar to everyone whether they've got a radar flag or not
|MORPH
|Good idea
|-
|Selectable 'ricochet' fire - hold down shift key or something and your bullets won't ricochet
|MORPH
|Idea.
|-
|Server option - tanks only have a certain number of times they can jump (gets reset when you get killed)
|MORPH
|Idea.
|-
|Multiple-shields (server option for shield flags, or can be random - can get hit x number of times)
|MORPH
|Idea
|-
|Ability to damage or destroy buildings/pyramids/teleporters
|MORPH
|Idea (M. Jetleb - probably a good idea for timed games, where the building can be reset after a reasonable amount of time, but can you imagine what the field would look like for a perpetual game that's been running for days? There has to be some way to reset this. Also what happens if someone shoots the bottom out of a building? Does the building collapse or just remain suspended? This could get complicated.)
|-
|Server config to make bullets NOT go through teleporters
|MORPH
|Idea
|-
|Holographic buildings - can't see what's behind them, but can shoot through them (great for the radarless-option above)[M. Jetleb -> how does not being able to see through a building help when you're radarless?]. Can't tell the difference on radar between them and regular buildings
|MORPH
|Idea, could be a materials property.
|-
|SandTraps - tank gets stuck there
|MORPH
|Idea (aren't there enough incredibly annoying ways for tanks to get stuck on pyramids etc. already? --pediddle)
|-
|Configurable 'radarless' and/or 'blind' zones in the arena - can't see what's in there on radar or via visuals
|MORPH
|Idea
|-
|'Fog' area in arena - impairs use of laser
|MORPH
|Idea
|-
|Connection-quality restrictions - restriction players based on connection quality - if they're having connection problems, server can drop them (after informing them what's going on)
|MORPH
|Implemented - also, throttling is implemented; people with high framerates were sending a lot of messages, clogging things up for people with slower connections.
|-
|Ability for a team to vote to 'banish' someone from their team
|MORPH
|Idea
|-
|Send message to everyone 'but' specified player (crosses team boundaries, or not)
|MORPH
|Idea. Hmm. Everybody BUT a specified player? [M. Jetleb -> as in: "Let's all get the GM guy" without the GM guy knowing he's facing a co-ordinated attack - I like this idea)
|-
|Non-solid buildings - ability to make tunnels through buildings, etc.
|MORPH
|Idea.
|-
|Tank collisions - why can tanks drive through each other? Weird.
|MORPH
|Good Idea, but severely hindered by lag issues.
|-
|When tanks collide - great opportunity to implement tank damage concept, especially if one of them is moving especially fast, or has momentum flag, etc. Can push a tank off a building if your pushing them from their side.
|Morph
|Idea
|-
|If a tank explodes right next to another tank, the other tank can be destroyed or get damaged
|MORPH
|Idea
|-
|Randomly changing arena - buildings grow, shrink, move
|MORPH
|(Unknown)
|-
|Server option: Cause a player to die if they shoot a teammate (accidentally or otherwise). This would discourage team killers and affect strategy (players are more cautious when shooting near teammates). (how about if you die after you kill teammates n times, and n is reset whenever you die. this will protect people who just do it accidently)
|MORPH
|Implemented (for a LONG time)
|-
|Server option: Make all good flags (except for ID flag) permanent (i.e. you cannot drop a flag unless you are killed). This discourages flag hunting (for GM flag or whatever) and forces players to play (build skill with?) the first flag they pick up until they die
|MORPH
|(Unknown)
|-
|Server option: Have finite ammo for the GM and Laser.
|MORPH
|Implemented (generically- shot limits)
|-
|Damage status- getting hit three (3) times kills you.
|MORPH
|(Unknown)
|-
|Skins or views- In-tank mode, bumper mode, out-of-cab mode, chase mode.
|MORPH
|(Unknown)
|-
|customizable sounds and/or models.
|MORPH
|(Unknown)
|-
|A usable world editor for mac and windows so that more servers are available.
|iPod
|Done
|-
|Better Textures on the buildings and pyramids and more variety of structures.
|iPod
|Done (meshes)
|-
|Ramps and slopes which tanks can drive up.
|iPod
|(Unknown)
|-
|There should be a game of cops and robbers. The teams can change after about 10 mins or so.
|iPod
|(Unknown)
|-
|BZFlag for mac in seperate data and application files.
|iPod
|(Unknown)
|-
|Weapon extention packs.
|iPod
|Huh?
|-
|The ability to choose tanks, but they all die at one shot. maybe the jump height, speed, turn speed, acceleration, size can be preset.
|iPod
|(Unknown)
|-
|The ability to see what the world is like before connecting to the server.
|iPod
|(Unknown)
|-
|Sounds of tanks moving.
|iPod
|(Unknown)
|-
|Handicap. Allow for bad players yo have better properties than the best players (like velocity), so it's a more interesting play for everybody. It'll be server optional and the handicap players are marked in player lists|
|JavierMM
|(Unknown)
|-
|Additional Idea to Handicap:
* Autobalance option. If activated it adds an additional scale factor to the tank wich depends on the score. If the score rises the tank gets bigger and if the score is negative the tank gets smaller then the normal one (The hight of the tank will not be scaled). The strength of the effect should be defined by the server. The tank of an extreme good player will at one point no longer fit trough the teleporters and this will give an additional handicap until his score comes down again.
|Amoc
|(Unknown)
|-
|Have different tank death scenes for the dying tank point of view. I realize there is some time needed for one to die and respawn, but the jumping effect one sees when killed irritates me to no end! I'd be happier if all faded to black or white or orange and had text across the screen saying ""respawning... please wait"" :) Also, when killed and your tank was moving toward a building, it just falls right thru it until it hits the ground.. wrong physics there! Splatter or tumble or shatter or something :)
|Robi
|(Unknown)
|-
|A special FFA Game mode "Team by Flags". This means, same Flag = same Team, so if there is a Tank with Rapid fire, and you pick up Rapid fire, you are automatically handled as Team member (this means, killing the other Tank with Rapid fire will be handled the same way as when killing a team member). YHARG: Funky idea: what about a game mode where teams shared flag abilities? Like, each player on a team's flag applies to the whole team. This could make for some interesting combos...
|Agonizer
|(Unknown)
|-
|Make life trickier for the Rogue Team; with a mix of Rogues and Colored Teams, the Rogues have more targets. This should also change the effect of the Masquerade flag - perhaps your tank is invisible to Rogues (like Cloaking)?
|NickGrim
|(Unknown)
|-
|A server option to make deaths not affect your score unless they were self-inflicted/team (the method used by many online games). This would encourage more aggressive play, because it's worth going out and blasting. As it is, you've got a very good chance by just phantoming/OOing out of the way and keeping you score at zero to stay in the top three places! It would also help fix the rather unfair situation of spawning just below a building on which someone is GM-camping...there's pretty much no way to escape, so you lose a point.
|LionsPhil
|(Unknown)
|-
|Custom color schemes for rogue players. The turret and body components can be chosen to be one of a predefined set of colors (e.g. red, yellow, black, white, blue, green, purple...). The game prohibits choosing a color scheme that matches a team scheme (e.g. red turret with red body) and the limited set stops someone choosing a shade which is nearly a team color (e.g. 0xFE0000 instead of 0xFF0000) (and also save texture memory, I think).
|LionsPhil
|(Unknown)
|-
|Allow a small decal on the back of the top of the tank. (think Half-Life's customizable spraypaint). Possibly also apply it to any held flag?
|LionsPhil
|(Unknown)
|-
|Allow ramps in level designs, so tanks can move to certain other platforms without having to jump. This would require adjusting the engine to allow tanks to angle on the ramps. Reduced speed depending on gradient?
|LionsPhil
|(Unknown)
|-
|What about a radar that only covers visible areas (don't passing through buildings/pyramids) ? This would leads to more placement tactics).
|K<nowiki>'</nowiki>limero
|(Unknown)
|-
|Spread Fire (SF) Flag which fires three shots at the same time. One on the centerline, the other two angled at a quarter degree along either side of the centerline.
|Yohan
|(Unknown)
|-
|World configuration of server options. Sometimes a map is designed for use with specific flags, or perhaps certain flags could be too powerful and you would want to turn them off.
|Yohan
|(Unknown)
|-
|Extending an idea from above regarding teleporters: Make teleporters configurable so that the map designer decides whether bullets or tanks or both can pass through the teleporter. Also, an option which changes the angle at which a bullet or tank will pass through a teleporter. Currently, if a teleporter links back to itself, the shot always returns back at the tank which fired it rather than reflecting.
|Yohan
|(Unknown)
|-
|HUD radar. (We are using this with our local games and love it).
|Yohan
|(Unknown)
|-
|Allow ramps and ability of tanks to drive up ramps. I guess this is a duplicate, but I still like it. (Dragonstar agrees with this too) Please do this!
|Yohan
|(Unknown)
|-
|* Add ice as a terrain feature
|morfie
|(Unknown)
|}
</div>

Idea(s) From Dragonstar. Items marked with a !!! are what I want most
* Server creation option: # of flags holdable at a time
* Allow custom-made weapons with a Object-Oriented scripting language (sorta like Liero AI uses: http://helios.et.put.poznan.pl/~sskowron/liero/index.html)!!!
* Custom-made graphics/objects for weapons and levels
* Triggers in levels!!!
* Water Terrain
* Custom Terrains (select a image to tile, slipperyness, etc.)
More coming later :-)

Ideas From Cue:
* Option to choose different kinds of tanks. Different tanks could be weighted with different strengths and weaknesses. (almost like having a default flag). Would also need some form of health/damage status measurement, not just single hits. For example, there could be a larger, heavily armored tank that has powerful weapons, but moves slowly, versus a small, light, fast tank which is difficult to hit, but very low armor to protect from hits.
* Land mine flag?

Ideas from abli:
* Multiple list servers, in case bzflag.org goes down (as it happened around feb. 15. 2004)
* Always random respawn. Currently in CTF games first respawn is at own base. This can be abused by leaving and rejoining to get near base. This leave/rejoing trick is considered to be a mild form of cheating by many. Always random respawn would make it useless.
* Don't show invidual score in CTF games. This might help teamplay as it reduces the incentive to run around as if it would be FFA.
* Give points to the player how captures flag in CTF. (Say, around 4 or so) After all, it is often a bigger job than killing someone.

Idea from kitchen:
* volcano (growing red pyramid) that's death to touch and grows during the course of a round and occasionally gives off 'pyroclast flows' aka super bullets. perhaps red-orange color.
* multiple (3?) jump stengths mini, normal, max...just the thing to confuse the opponents that expect one and you're off doing the other.

Idea from bhtooefr:
* J2ME client (allows one to play on a cell phone), would use radar
* Multi-monitor support (i.e., radar on one screen, window on another, chat/event log on a third)

Idea from nsayer:
* wraparound world - radar remains centered on your current position. Internally, objects leaving the north border reappear to the south, but from the user's radar / visible perspective, you just see to the horizon. I believe this is how the original Battlezone worked. There are some implications: laser would need a range limit.

Idea from rjbs:
* wireframe mode! man, this would make the game ten times cooler for nostalgia

Idea from Colin:
* Make a part in bzflag to put up a real server. 1st screen has the flags you want, next page is to find the MAP file that you created on your hard drive, next page pick if you want jumping etc.
* Have part in BZflag so that you can have bots.
* Toggle radar and message bar on and off with a key on your keyboard.

Idea from Dan:
* Health, like in a fps. If you get shot from a closer range, you take more damage. When you run out of health, you die. Health pickups in places - not a flag. Although there might be a health generator flag.
* For above: a "Doctor" flag - shooting someone (similar to thief) either fixes them or, like the above health generator flag, except faster, heals them. Don't shoot the other team!

Idea from pherris:
* Anti camping. The ability to add "no camping zones" to areas of a map or to the entire map. Campers would be messaged that they're in a no camping zone, better start moving and have a prescribe number of seconds to move away or die. If a player returns to the same NCZ (no camping zone) and receives x warnings then he's disconnected. NCZs could be marked by a different color shade from a "normal" spot and could be exempt to a single team (like at their flag base). It's just a rough idea.

Idea from Orca
* Special 'open source' BZFlag version (server and client) which is guaranteed to be compatible with all other BZFlag versions.

Idea from Dogbert
* Trajectory flag and option on servers (Causes bullets to fall (But very slowly)). Bullets will go no lower than standard level, so trajectory is only active if you are jumping, or on a block.
* Moving blocks, so when people put things like the USS Enterprise at the top of their map, it can move around.
* Turret mode, If enabled by the server (Can be manditory with automatic grouping). One user drives and the other shoots, Turret mode tanks get double points (But onyl take one from the target). lost double points if killed. Have double ammo, And controllable speed (Max = _tankSpeed * 2 Min = _tankSpeed). Plus it takes 2 shots to kill a turret mode tank. Points gained and lost by turret tanks are divided evenly between the users, Unless the server is all turret mode, in h which case two users are displayed as one.

Ideas from YHARG:
* I'd like to see something more interesting done with the sky... maybe there could be a little ufo (easter egg) that would fly around occasionally? Tux on a ufo! ;)
* "Super smash bros" style jumping: a server-side option to let tanks jump a second or third time while in the air... changing direction would be possible by jumping with the pointer moved to what direction you'd like to doublejump. The direction change would probably be much less than the maximum tank speed, but maybe that could be a variable too. This would be great for platform maps. and add a way to mix up the classic jump killing that goes on in regular games.
* Flag decals: Each flag would have a little icon/decal showing it's type ONLY when held by a player. It's kind of nice to be able to surprise people with an undercover shockwave, but doesn't make sense to have to right click (identify) or check the user list to see what flag someone has.
* Ducati/Freestyle "Roles" mode: Make a game mode where players are presented with a list of flag choices (limitable to a few roles, if wanted) at respawn or connect time, and are forced to use this flag for the remainder of their connection/tank life. This would be really useful in the case of stealth vs. seer, where you could choose to be stealth or seer, but couldn't switch between them. Another idea would be high speed vs. quick turn. Or steamroller vs. machine gun... Team play would have the interesting effect of people banding together and people with each role on the team. Especially in stealth vs. seer, where a seer team member could warn the team about enemies! There would be no team flags/bases.
* Background music! : (This can be done with an external media player so it shouldn't be the heighest priority, It would be nice to be able to control your music from within BzFlag)
* Teleporter flag: Dropped twice, and makes a temporary teleporte on the map (for a set amount of time)
* BeamMeUp flag: Tab makes the tank teleport to the highest object directly above it. This would be very useful with high maps, but could encourage camping, and cheating.
* Tall tank flag: Like obesity, only makes the tank too tall to maneuver under low objects.
* Triplicate/Duplicate/MagicHat flag: Tank gets one or two bot duplicates whose shots do no damage, spawned where it is. They could possibly be respawned when killed. They would tend to stay near the tank.
* Sleepwalker Bad Flag: Your tank becomes controlled by a bot. Does not drop until tank is killed. Player's score is changed by bot's performance.
* Shield Flag Changes: Give Shield flag a radius, and draw it like a moving less opaque blue shockwave. Any tanks inside the shield radius would be protected, until the shield got hit a certain number of times.

Idea from Efitu:
* 7 words: user freindly bult-in map editor and viewer.

Ideas from Dogbert.
* More documentation on scripting world weapons.
* Preset world weapons that can be fired manually by admins from within BzFlag.
* Regicide flag, kills both the tanks you hit and the tank with the highest score on the same team of the tank you hit (Thus giving double points)

Idea from Supermatthew:
* Tank Turret Rotation sideways and up and down(controlable with a "Point of View" on a joystick and keyboard for those who don't have joystick with it)
* Like Efitu's idea, user freindly built-in map editor and viewer, the current map editor isn't so good, expesaly when you delete stuff it does weard things.
* The ability to add texture to blocks like if tou wanted to add a street texture and make a road or a weard wall or whatever.
* more objects ot build with like a ball and cone and cylender and incline planes (/ or \) that tanks can drive up.
* Moving objects like a wall that could spin on its X Y or Z axis and chose the point were it spins like 5X, 3Y, 0Z away from its center
* New game called tag were someone is it and they shoot someone else and there it and ect.
* Also a new game called "Hide and seek" were everyone is clocked(think thats it, were you don't see them on radar) except one who is it. he needs to find someone and shoot them then hese cloked and who was shot is not. Also when someone is shot there sent back to Ground zero( 0X, 0Y, 0Z ) so they can't shoot who ever just shot them.
* Editable ground hight like hills or something
* another game called dodge ball were one person can shoot and when someone is hit then they become an observer till the next game and when theres only one person(other than the one whose it) they become it.

Idea from TomMatelich:
* At our company, we instituted a voluntary policy of dropping flags after 1 kill. Prevents slaughters and keeps things rolling more. It'd be great to be able to have the game do this for us, plus I'd love to see it turned on at external sites.

Ideas from NebNamwen:
* Server option: default powers -- flag(s) that everyone in the game automatically has (this wouldn't count as holding a flag). For example, the current Jumping option would == including Jumping as a default power.

[[Category:Development]]

Ideas

2007-03-16T20:15:29Z

L4m3r:

{{Old}}
Feel free to make changes and updates to this page whenever possible. If you have any questions, feel free to [[Getting Help|ask for help]]. If you wish to make major changes to this page (i.e. remove large amounts of old ideas), please warn us ahead of time.

NOTE: These are just possiblilities. We won't be implementing everything here.<br>
NOTE: Flag ideas should be placed on [[Flag Ideas]]. Any other ideas can be placed here.

Status may include personal comments by developers.

== Adding ideas ==
* All ideas should be categorized and should be prefixed with a *.
* Sign your idea with four tildes: <nowiki>~~~~</nowiki>
* Make sense!

== Ideas include: ==
* Add support for 5 (or more) button mice Status: Great Idea
* Sort player list by team Status: Implemented (how?)
* Make option to show previous players list Status: Idea
* Anti-cheating measures detecting cheating clients/servers, kicking them out automatically or by vote, etc. I will push to have this implemented in version 1.8. Status: Some anti-cheating measures are in 1.7G2, more work to follow. Great Idea (delete this idea, it's ancient?)
* More flags: [[Flag Ideas]]
* Better network handling Status: Work in progress.
* Better physics Status: Planning, some changes in CVS.
* Map editor Status: Windows, Linux and Java2 editors are working, Linux editor in CVS, I want one using BZFlag's own engine.
* server-side respawn position Status: Implemented in [[BZFlag 2.0.0]]
* 2 or 3 teams as well as the current 4 Status: Man, this gotta be old. BZFlag used to only work with 4 teams??
* Tounament mode Status: Idea (Great Idea?)
* Ability to define flags allowed / not allowed in world file Status: Idea
* Materials that don't allow OO and PZ to go through Status: Would be nice for multilevel worlds made with the new ability to have objects above the ground. (Sounds awesome! [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT))
* Better robot AI Status: Idea, don't know if players would like it or not in multiplayer game. Pluggable or scriptable robot AI , maybe? - Code must be restructured first (Server side bots are coming! [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT))

Idea from Spazzy McGee:
* Option to search for servers in list. It gets really annoying if you want to find a server and you have to go through all the pages, as there are over 10 now. Status: Implemented in [[BZFlag 2.0.4]]

One Idea from Trigger Happy Nerd:
* When you shoot someone on your own team, instead of both of you blowing up, neither is destroyed, and their score goes up one, while your's goes down one. This would make teamkilling impossible and greatly discourage traitors as well. | But then couldn't cheaters spawn two clients and ramp up their scores by teamkilling their other login? --YHARG

3 Ideas from BearRiver:
* SELF-DESTRUCT BLAST RADIUS: Self Destruct (delete key) should have a blast radius similar to Shock Wave, perhaps larger. If you get shot during the self-destruct count down, that should also trigger the same blast. If I gotta go, I want to take someone with me.
* SUPERBALL FLAG: Fires a standard shot that drops with gravity instead of hovering as it goes. Allows you to target burrow tanks and bounce shots over walls if you fire while jumping.
* SUPERJUMP FLAG: Doubles the height of your jump. Requires some skill to use because your a sitting duck on the way down.

Ideas from MORPH:
* Make ALL server options available from the menus status: Idea
* Ability to toggle display of player emails (some are so long they mess up the score display) status: Idea
* Word wrap long messages - they get cut off for those with low-resolution displays status: Done??
* Improvements to radar: Color-coded bullets, brighter bullets (may have to be larger if already using brightest color), better distinction between blue players and pyramids status: Done
* Better positioning of tanks status: BZFlag already does this, but the algorithm is bad. Needs work.
* 3-second (or however long) 'invulnerability' for incoming tanks - but they can't shoot status: Idea.
* Ability to turn off ricochet for laser flag but allow ricochet for bullets status: Idea Please.. or let them bounce only n times.. OR implement mirror buildings/walls. Should go for some interesting self-kills when combined with the no-radar/bullet bounce idea's..
* Smart LockOn for GM - won't lock on to your teammates (configurable in server) status: Idea. (M. Jetleb -> I don't like this idea, there should be at least *some* risks to using this weapon. Personally, I think there should be more (not fewer) risks to holding this weapon; I'd like to see the thing overheat and explode (killing the holder) if it's fired too often in a short period of time)
* Small jumps status: Idea
* Differently-shaped teleporters (circles, triangles, etc.) status: Idea, probably low priority
* 360 degree teleports - hit a spot on the ground or in the air from any direction and you teleport status: Idea
* Configurable random teleporters - teleports to a different location every time status: Idea
* Allow different physical properties on top of buildings (momentum, etc.) status: Idea, goes with my ""materials"" idea.
* Allow higher wall-height around arena (ricochet at higher heights) - or no walls defining the boundaries - just a line. (ricochet only off buildings & pyramids) status: Idea
* Server option for genocide flag - if you're killed while you have it, your team dies :^) status: Idea
* for broadband or LAN connections - voice chat for teams status: Idea, but I really think that you can do this with another service; I'm not sure if being part of BZFlag would be a good idea due to size and bandwidth issues.
* Separate windows for player messages & server messages status: Good idea.
* Message log status: Good idea.
* Serious multithreaded design - shouldn't lock up interface while looking for servers, or doing anything else. This program is way-unstable on Windows status: We're working on these problems; many complaints are due to people still using old servers/clients.
* Ability to configure server to turn somethings off or on depending on number of players - for instance, turn off ricochet after a certain number of players are connected, turn off GM & laser if a certain number of players aren't playing (GM & Laser with 2 players is kinda ridiculous) status: Idea
* 'Fox & Hound' scenario - highest player automatically becomes own team, all other plays on another team - kill the 'fox' (play with highest score). status: Good Idea, I'd like to see more ways to play BZFlag. (bhtooefr: Rabbit is very similar to this)
* Higher score(s) players lose abilities (bigger tanks, can't pick up flags, momentum, whatever) status: Idea
* Some type of BZFlag GUID to ban players who cheat - won't accept players who disable their GUID, etc. status: What is a GUID??
---
Global Unique Identifier, sort of like an IP addrss, but permanent. Usually a number. Problem occurs when you loose your GUID (have to reformat your HD, etc. How do you keep someone from hacking their GUID, or setting up a modified BZFlag server for identity theft, etc.
---
* Single/multiple-use flags (or they instantly change type after being used) (configurable on a flag-by-flag basis: e.g. laser & GM one-use only before they drop/disappear) status: Good idea, especially with the more powerful flags.
* Change graphic format to PNG so new 'skins' can be created. Optional use of server-defined skin. Client can use it or not (wouldn't really matter). status: In CVS for 1.8.
* Tank avatars (uploadable tank images) - have to think about shapes, though - someone could make a 1x1x1 pixel tank - that would suck - or a tank that looks like a building or pyramid. Clients don't have to accept downloading of avators (just view other tanks in default mode). Or just s-e-l-e-c-t from a certain number of predefined avatars that could come with the bzflag distribution. Or client provides a URL to download their avatar (saves server bandwidth). status: Idea, but might not be implemented. Requires discussion; we may want to consider making the computer force a minimum size or something similar. *How about uploadable flag graphics?
* To prevent cheating - the server determines what flags & abilities each tank has (possible?) status: Idea, but seriously being considered. This would also have the advantage of allowing different versions of clients and servers to work together. Yes, it's possible, but this type of change will mean a change in the network protocols.
* Send message to an individual, even if they're not on your team status: done
* Ability to change elevation of tank barrel & direction of turret (without jumping up or turning tank) (complex interface issues - super-low priority) status: Idea. Turret rotation rejected: The game is too fast for this to be useful, and would probably kill the game. *How about a new gameplay mode? Takes two to tank. One to ride turret, the other drives. KIA switches positions. "Teamplay" but all in one tank.
* Much better arena design capabilities - bridges over ditches, etc. status: Good idea. This along with some new physics (which I hope to propose soon -Jeremiah), and BZFlag will be much more interesting.
* Concept of a tank that can take damage without being destroyed immediately - slows down, takes a hit in a tread and turns slowly in whatever direction, etc. status: Good idea, but must be optional (server option). Might be rejected, since BZFlag is, by nature, a fast paced game. *Loses ability to shoot, runs and grabs a restore flag?
* 'Kamikaze' option for players - can take someone out by suicide status: Idea. Server option if implemented.
* Server option: everyone is radar-stealthed by default unless you get a 'radar' flag. You can still see all buildings, pyramids, teleports, and arena walls, though. status: Good idea. Make them use their window. ;)(M. Jetleb -> Given the fairly narrow field of view out the window and the time it takes to turn a tank all the way around for a look-see, I think this could be frustrating. How about everyone starts out with minimum range radar instead and gets longer ranges with an appropriate flag?)
* Option for above: if you pick up GM or Laser, you're visible on radar to everyone whether they've got a radar flag or not status: Good idea
* Selectable 'ricochet' fire - hold down shift key or something and your bullets won't ricochet status: Idea.
* Server option - tanks only have a certain number of times they can jump (gets reset when you get killed) status: Idea.
* Multiple-shields (server option for shield flags, or can be random - can get hit x number of times) status: Idea
* Ability to damage or destroy buildings/pyramids/teleporters status: Idea (M. Jetleb - probably a good idea for timed games, where the building can be reset after a reasonable amount of time, but can you imagine what the field would look like for a perpetual game that's been running for days? There has to be some way to reset this. Also what happens if someone shoots the bottom out of a building? Does the building collapse or just remain suspended? This could get complicated.)
* Server config to make bullets NOT go through teleporters status: Idea
* Holographic buildings - can't see what's behind them, but can shoot through them (great for the radarless-option above)[M. Jetleb -> how does not being able to see through a building help when you're radarless?]. Can't tell the difference on radar between them and regular buildings status: Idea, could be a materials property.
* SandTraps - tank gets stuck there status: Idea (aren't there enough incredibly annoying ways for tanks to get stuck on pyramids etc. already? --pediddle)
* Configurable 'radarless' and/or 'blind' zones in the arena - can't see what's in there on radar or via visuals status: Idea
* 'Fog' area in arena - impairs use of laser status: Idea
* Connection-quality restrictions - restriction players based on connection quality - if they're having connection problems, server can drop them (after informing them what's going on) status: Implemented - also, throttling is implemented; people with high framerates were sending a lot of messages, clogging things up for people with slower connections.
* Ability for a team to vote to 'banish' someone from their team status: Idea
* dispossition flag. See the tank somewhere else than it realy is: Idea
* Send message to everyone 'but' specified player (crosses team boundaries, or not) (morph) status: Idea. Hmm. Everybody BUT a specified player? [M. Jetleb -> as in: "Let's all get the GM guy" without the GM guy knowing he's facing a co-ordinated attack - I like this idea)
* Non-solid buildings - ability to make tunnels through buildings, etc. status: Idea.
* Tank collisions - why can tanks drive through each other? Weird. status: Good Idea.
* When tanks collide - great opportunity to implement tank damage concept, especially if one of them is moving especially fast, or has momentum flag, etc. Can push a tank off a building if your pushing them from their side. status: Idea
* If a tank explodes right next to another tank, the other tank can be destroyed or get damaged status: Idea
* Randomly changing arena - buildings grow, shrink, move,
* Server option: Cause a player to die if they shoot a teammate (accidentally or otherwise). This would discourage team killers and affect strategy (players are more cautious when shooting near teammates). (how about if you die after you kill teammates n times, and n is reset whenever you die. this will protect people who just do it accidently)
* Server option: Make all good flags (except for ID flag) permanent (i.e. you cannot drop a flag unless you are killed). This discourages flag hunting (for GM flag or whatever) and forces players to play (build skill with?) the first flag they pick up until they die.
* Server option: Have finite ammo for the GM and Laser.
* Damage status- getting hit three (3) times kills you.
* Skins or views- In-tank mode, bumper mode, out-of-cab mode, chase mode.
* customizable sounds and/or models.

Idea from iPod: items marked with !!! are the ones i want most
*A usable world editor for mac and windows so that more servers are available.!!!
*Better Textures on the buildings and pyramids and more variety of structures.
*Ramps and slopes which tanks can drive up.
*There should be a game of cops and robbers. The teams can change after about 10 mins or so.!!!
*BZFlag for mac in seperate data and application files.
*Weapon extention packs.
*The ability to choose tanks, but they all die at one shot. maybe the jump height, speed, turn speed, acceleration, size can be preset.
*The ability to see what the world is like before connecting to the server.
*Sounds of tanks moving.

One small idea from XPenguin:
* Have more than one flag to be carried at a time, but no more than two, more than that would almost be unfair to the other players.!!!

Idea from JavierMM:
* Handicap. Allow for bad players yo have better properties than the best players (like velocity), so it's a more interesting play for everybody. It'll be server optional and the handicap players are marked in player lists

Additional Idea to Handicap from Amoc:
* Autobalance option. If activated it adds an additional scale factor to the tank wich depends on the score. If the score rises the tank gets bigger and if the score is negative the tank gets smaller then the normal one (The hight of the tank will not be scaled). The strength of the effect should be defined by the server. The tank of an extreme good player will at one point no longer fit trough the teleporters and this will give an additional handicap until his score comes down again.

Idea from Robi:
* Have different tank death scenes for the dying tank point of view. I realize there is some time needed for one to die and respawn, but the jumping effect one sees when killed irritates me to no end! I'd be happier if all faded to black or white or orange and had text across the screen saying ""respawning... please wait"" :) Also, when killed and your tank was moving toward a building, it just falls right thru it until it hits the ground.. wrong physics there! Splatter or tumble or shatter or something :)

Idea from Agonizer:
* A special FFA Game mode "Team by Flags". This means, same Flag = same Team, so if there is a Tank with Rapid fire, and you pick up Rapid fire, you are automatically handled as Team member (this means, killing the other Tank with Rapid fire will be handled the same way as when killing a team member). YHARG: Funky idea: what about a game mode where teams shared flag abilities? Like, each player on a team's flag applies to the whole team. This could make for some interesting combos...

Idea from NickGrim:
* Make life trickier for the Rogue Team; with a mix of Rogues and Colored Teams, the Rogues have more targets. This should also change the effect of the Masquerade flag - perhaps your tank is invisible to Rogues (like Cloaking)?
Ideas from LionsPhil:
* A server option to make deaths not affect your score unless they were self-inflicted/team (the method used by many online games). This would encourage more aggressive play, because it's worth going out and blasting. As it is, you've got a very good chance by just phantoming/OOing out of the way and keeping you score at zero to stay in the top three places! It would also help fix the rather unfair situation of spawning just below a building on which someone is GM-camping...there's pretty much no way to escape, so you lose a point.
* Custom color schemes for rogue players. The turret and body components can be chosen to be one of a predefined set of colors (e.g. red, yellow, black, white, blue, green, purple...). The game prohibits choosing a color scheme that matches a team scheme (e.g. red turret with red body) and the limited set stops someone choosing a shade which is nearly a team color (e.g. 0xFE0000 instead of 0xFF0000) (and also save texture memory, I think).
* Allow a small decal on the back of the top of the tank. (think Half-Life's customizable spraypaint). Possibly also apply it to any held flag?
* Allow ramps in level designs, so tanks can move to certain other platforms without having to jump. This would require adjusting the engine to allow tanks to angle on the ramps. Reduced speed depending on gradient?

Idea from K<nowiki>'</nowiki>limero:
* What about a radar that only covers visible areas (don't passing through buildings/pyramids) ? This would leads to more placement tactics).

Idea(s) from Yohan:
* Spread Fire (SF) Flag which fires three shots at the same time. One on the centerline, the other two angled at a quarter degree along either side of the centerline.
* World configuration of server options. Sometimes a map is designed for use with specific flags, or perhaps certain flags could be too powerful and you would want to turn them off.
* Extending an idea from above regarding teleporters: Make teleporters configurable so that the map designer decides whether bullets or tanks or both can pass through the teleporter. Also, an option which changes the angle at which a bullet or tank will pass through a teleporter. Currently, if a teleporter links back to itself, the shot always returns back at the tank which fired it rather than reflecting.
* HUD radar. (We are using this with our local games and love it).
* Allow ramps and ability of tanks to drive up ramps. I guess this is a duplicate, but I still like it. (Dragonstar agrees with this too) Please do this!

Idea from morfie
* Add ice as a terrain feature

Idea(s) From Dragonstar. Items marked with a !!! are what I want most
* Server creation option: # of flags holdable at a time
* Allow custom-made weapons with a Object-Oriented scripting language (sorta like Liero AI uses: http://helios.et.put.poznan.pl/~sskowron/liero/index.html)!!!
* Custom-made graphics/objects for weapons and levels
* Triggers in levels!!!
* Water Terrain
* Custom Terrains (select a image to tile, slipperyness, etc.)
More coming later :-)

Ideas From Cue:
* Option to choose different kinds of tanks. Different tanks could be weighted with different strengths and weaknesses. (almost like having a default flag). Would also need some form of health/damage status measurement, not just single hits. For example, there could be a larger, heavily armored tank that has powerful weapons, but moves slowly, versus a small, light, fast tank which is difficult to hit, but very low armor to protect from hits.
* Land mine flag?

Ideas from abli:
* Multiple list servers, in case bzflag.org goes down (as it happened around feb. 15. 2004)
* Always random respawn. Currently in CTF games first respawn is at own base. This can be abused by leaving and rejoining to get near base. This leave/rejoing trick is considered to be a mild form of cheating by many. Always random respawn would make it useless.
* Don't show invidual score in CTF games. This might help teamplay as it reduces the incentive to run around as if it would be FFA.
* Give points to the player how captures flag in CTF. (Say, around 4 or so) After all, it is often a bigger job than killing someone.

Idea from kitchen:
* volcano (growing red pyramid) that's death to touch and grows during the course of a round and occasionally gives off 'pyroclast flows' aka super bullets. perhaps red-orange color.
* multiple (3?) jump stengths mini, normal, max...just the thing to confuse the opponents that expect one and you're off doing the other.

Idea from bhtooefr:
* J2ME client (allows one to play on a cell phone), would use radar
* Multi-monitor support (i.e., radar on one screen, window on another, chat/event log on a third)

Idea from nsayer:
* wraparound world - radar remains centered on your current position. Internally, objects leaving the north border reappear to the south, but from the user's radar / visible perspective, you just see to the horizon. I believe this is how the original Battlezone worked. There are some implications: laser would need a range limit.

Idea from rjbs:
* wireframe mode! man, this would make the game ten times cooler for nostalgia

Idea from Colin:
* Make a part in bzflag to put up a real server. 1st screen has the flags you want, next page is to find the MAP file that you created on your hard drive, next page pick if you want jumping etc.
* Have part in BZflag so that you can have bots.
* Toggle radar and message bar on and off with a key on your keyboard.

Idea from Dan:
* Health, like in a fps. If you get shot from a closer range, you take more damage. When you run out of health, you die. Health pickups in places - not a flag. Although there might be a health generator flag.
* For above: a "Doctor" flag - shooting someone (similar to thief) either fixes them or, like the above health generator flag, except faster, heals them. Don't shoot the other team!

Idea from pherris:
* Anti camping. The ability to add "no camping zones" to areas of a map or to the entire map. Campers would be messaged that they're in a no camping zone, better start moving and have a prescribe number of seconds to move away or die. If a player returns to the same NCZ (no camping zone) and receives x warnings then he's disconnected. NCZs could be marked by a different color shade from a "normal" spot and could be exempt to a single team (like at their flag base). It's just a rough idea.

Idea from Orca
* Special 'open source' BZFlag version (server and client) which is guaranteed to be compatible with all other BZFlag versions.

Idea from Dogbert
* Trajectory flag and option on servers (Causes bullets to fall (But very slowly)). Bullets will go no lower than standard level, so trajectory is only active if you are jumping, or on a block.
* Moving blocks, so when people put things like the USS Enterprise at the top of their map, it can move around.
* Turret mode, If enabled by the server (Can be manditory with automatic grouping). One user drives and the other shoots, Turret mode tanks get double points (But onyl take one from the target). lost double points if killed. Have double ammo, And controllable speed (Max = _tankSpeed * 2 Min = _tankSpeed). Plus it takes 2 shots to kill a turret mode tank. Points gained and lost by turret tanks are divided evenly between the users, Unless the server is all turret mode, in h which case two users are displayed as one.

Ideas from YHARG:
* I'd like to see something more interesting done with the sky... maybe there could be a little ufo (easter egg) that would fly around occasionally? Tux on a ufo! ;)
* "Super smash bros" style jumping: a server-side option to let tanks jump a second or third time while in the air... changing direction would be possible by jumping with the pointer moved to what direction you'd like to doublejump. The direction change would probably be much less than the maximum tank speed, but maybe that could be a variable too. This would be great for platform maps. and add a way to mix up the classic jump killing that goes on in regular games.
* Flag decals: Each flag would have a little icon/decal showing it's type ONLY when held by a player. It's kind of nice to be able to surprise people with an undercover shockwave, but doesn't make sense to have to right click (identify) or check the user list to see what flag someone has.
* Ducati/Freestyle "Roles" mode: Make a game mode where players are presented with a list of flag choices (limitable to a few roles, if wanted) at respawn or connect time, and are forced to use this flag for the remainder of their connection/tank life. This would be really useful in the case of stealth vs. seer, where you could choose to be stealth or seer, but couldn't switch between them. Another idea would be high speed vs. quick turn. Or steamroller vs. machine gun... Team play would have the interesting effect of people banding together and people with each role on the team. Especially in stealth vs. seer, where a seer team member could warn the team about enemies! There would be no team flags/bases.
* Background music! : (This can be done with an external media player so it shouldn't be the heighest priority, It would be nice to be able to control your music from within BzFlag)
* Teleporter flag: Dropped twice, and makes a temporary teleporte on the map (for a set amount of time)
* BeamMeUp flag: Tab makes the tank teleport to the highest object directly above it. This would be very useful with high maps, but could encourage camping, and cheating.
* Tall tank flag: Like obesity, only makes the tank too tall to maneuver under low objects.
* Triplicate/Duplicate/MagicHat flag: Tank gets one or two bot duplicates whose shots do no damage, spawned where it is. They could possibly be respawned when killed. They would tend to stay near the tank.
* Sleepwalker Bad Flag: Your tank becomes controlled by a bot. Does not drop until tank is killed. Player's score is changed by bot's performance.
* Shield Flag Changes: Give Shield flag a radius, and draw it like a moving less opaque blue shockwave. Any tanks inside the shield radius would be protected, until the shield got hit a certain number of times.

Idea from Efitu:
* 7 words: user freindly bult-in map editor and viewer.

Ideas from Dogbert.
* More documentation on scripting world weapons.
* Preset world weapons that can be fired manually by admins from within BzFlag.
* Regicide flag, kills both the tanks you hit and the tank with the highest score on the same team of the tank you hit (Thus giving double points)

Idea from Supermatthew:
* Tank Turret Rotation sideways and up and down(controlable with a "Point of View" on a joystick and keyboard for those who don't have joystick with it)
* Like Efitu's idea, user freindly built-in map editor and viewer, the current map editor isn't so good, expesaly when you delete stuff it does weard things.
* The ability to add texture to blocks like if tou wanted to add a street texture and make a road or a weard wall or whatever.
* more objects ot build with like a ball and cone and cylender and incline planes (/ or \) that tanks can drive up.
* Moving objects like a wall that could spin on its X Y or Z axis and chose the point were it spins like 5X, 3Y, 0Z away from its center
* New game called tag were someone is it and they shoot someone else and there it and ect.
* Also a new game called "Hide and seek" were everyone is clocked(think thats it, were you don't see them on radar) except one who is it. he needs to find someone and shoot them then hese cloked and who was shot is not. Also when someone is shot there sent back to Ground zero( 0X, 0Y, 0Z ) so they can't shoot who ever just shot them.
* Editable ground hight like hills or something
* another game called dodge ball were one person can shoot and when someone is hit then they become an observer till the next game and when theres only one person(other than the one whose it) they become it.

Idea from TomMatelich:
* At our company, we instituted a voluntary policy of dropping flags after 1 kill. Prevents slaughters and keeps things rolling more. It'd be great to be able to have the game do this for us, plus I'd love to see it turned on at external sites.

Ideas from NebNamwen:
* Server option: default powers -- flag(s) that everyone in the game automatically has (this wouldn't count as holding a flag). For example, the current Jumping option would == including Jumping as a default power.

[[Category:Development]]