BZFlagWiki - User contributions [en]

Bz BasePlayerRecord

2012-10-16T00:35:57Z

Brad: /* Data */

{{BZFS_API_Doc}}
{{BZFS_API_Class}}

==Overview==
The '''bz_BasePlayerRecord''' is an API class that is provided to expose information about a connected player to the plug-in.

==Data==
Class bz_BasePlayerRecord has the following data members:

; int version : The version number of this API class ;
; int playerID : The player ID for the player.
; [[bz_ApiString]] callsign : The username/callsign for the player.
; [[bz_eTeamType]] team : The team the player is currently on.
; float lastUpdateTime : The server time of the last player update
; [[bz_PlayerUpdateState]] lastKnownState : The state record that was last sent
; [[bz_PlayerUpdateState]] currentState (not in 2.4) : The predicted state at the current time, representing where the server and all remote users show the player at.
; [[bz_ApiString]] ipAddress : The Internet Protocol v4 address of the connected client
; [[bz_ApiString]] currentFlag : The flag code of the flag to give to the player. The [[Flag_Reference_in_Plugins|flag code format]] is a string that looks like "FLag (+FL)" Where letters that make up the flag abbreviation is capitalized. So for example, Narrow is Narrow and Wings is WinGs. The content in parenthesis include a + sign if the flag is a good flag or a - sign if the flag is a bad flag followed by the symbol of the flag. If no flag is being held, this parameter is simply an empty string. The actual values outputted by this member can also be clarified on the 5th & 6th pages of the "Help" section in-game.
; [[bz_APIStringList]] flagHistory : A list of strings representing the names of all the flags the player has held, in order from newest to oldest.
; bool spawned : True if the user has spawned and is playing.
; bool verified : True if the user has authenticated with the login system. Comparable to a user having a "+" in the scoreboard.
; bool globalUser : True if the user name was authenticated using the global login system as opposed to a local one.
; [[bz_ApiString]] bzID : The globally unique ID for authenticated users.
; bool admin : Is true by default if user has the BAN permission. Sets the "@" sign.
; bool op : True if the user is identified as a server operator via /password
; bool canSpawn : True if the user has permissions to spawn (BZFlag 2.99).
; [[bz_APIStringList]] groups : The list of groups the user is a member of
; int lag : The user's current lag amount in milliseconds.
; int jitter : The user's current jitter amount in milliseconds.
; float packetloss : The user's current packet loss percentage.
; int wins : The number of kills the user has had.
; int losses : The number of deaths the user has had
; int teamKills : The number of team mates the user has killed.

==Methods==
The class provides a number of methods for various utility functions;

===update===
void update ( void );

This method will update the player record with the most current data. This is usefully if a plug-in stores the pointer to the class and wishes to use it with current data.

===hasPerm===
bool hasPerm ( const char* perm );

This method will return true if the user has the permission with the specified name.

===grantPerm===
bool grantPerm ( const char* perm );

This method will give the user the permission with the specified name, and return true if the operation was successful.

===revokePerm===
bool revokePerm ( const char* perm );

This method will remove the user the permission with the specified name, and return true if the operation was successful.

==Uses==
This class is returned by a number of API functions and events. This class is used any time player specific data is requested.

==Removed Fields==
The email field was removed with version 2.4 since it was removed from the game and changed to "motto"

Bz BasePlayerRecord

2012-10-16T00:35:35Z

Brad: /* Data */

{{BZFS_API_Doc}}
{{BZFS_API_Class}}

==Overview==
The '''bz_BasePlayerRecord''' is an API class that is provided to expose information about a connected player to the plug-in.

==Data==
Class bz_BasePlayerRecord has the following data members:

; int version : The version number of this API class ;
; int playerID : The player ID for the player.
; [[bz_ApiString]] callsign : The username/callsign for the player.
; [[bz_eTeamType]] team : The team the player is currently on.
; float lastUpdateTime : The server time of the last player update
; [[bz_PlayerUpdateState]] lastKnownState : The state record that was last sent
; [[bz_PlayerUpdateState]] currentState : The predicted state at the current time, representing where the server and all remote users show the player at.
; [[bz_ApiString]] ipAddress : The Internet Protocol v4 address of the connected client
; [[bz_ApiString]] currentFlag (not in 2.4) : The flag code of the flag to give to the player. The [[Flag_Reference_in_Plugins|flag code format]] is a string that looks like "FLag (+FL)" Where letters that make up the flag abbreviation is capitalized. So for example, Narrow is Narrow and Wings is WinGs. The content in parenthesis include a + sign if the flag is a good flag or a - sign if the flag is a bad flag followed by the symbol of the flag. If no flag is being held, this parameter is simply an empty string. The actual values outputted by this member can also be clarified on the 5th & 6th pages of the "Help" section in-game.
; [[bz_APIStringList]] flagHistory : A list of strings representing the names of all the flags the player has held, in order from newest to oldest.
; bool spawned : True if the user has spawned and is playing.
; bool verified : True if the user has authenticated with the login system. Comparable to a user having a "+" in the scoreboard.
; bool globalUser : True if the user name was authenticated using the global login system as opposed to a local one.
; [[bz_ApiString]] bzID : The globally unique ID for authenticated users.
; bool admin : Is true by default if user has the BAN permission. Sets the "@" sign.
; bool op : True if the user is identified as a server operator via /password
; bool canSpawn : True if the user has permissions to spawn (BZFlag 2.99).
; [[bz_APIStringList]] groups : The list of groups the user is a member of
; int lag : The user's current lag amount in milliseconds.
; int jitter : The user's current jitter amount in milliseconds.
; float packetloss : The user's current packet loss percentage.
; int wins : The number of kills the user has had.
; int losses : The number of deaths the user has had
; int teamKills : The number of team mates the user has killed.

==Methods==
The class provides a number of methods for various utility functions;

===update===
void update ( void );

This method will update the player record with the most current data. This is usefully if a plug-in stores the pointer to the class and wishes to use it with current data.

===hasPerm===
bool hasPerm ( const char* perm );

This method will return true if the user has the permission with the specified name.

===grantPerm===
bool grantPerm ( const char* perm );

This method will give the user the permission with the specified name, and return true if the operation was successful.

===revokePerm===
bool revokePerm ( const char* perm );

This method will remove the user the permission with the specified name, and return true if the operation was successful.

==Uses==
This class is returned by a number of API functions and events. This class is used any time player specific data is requested.

==Removed Fields==
The email field was removed with version 2.4 since it was removed from the game and changed to "motto"

Bz eAllowFlagGrab

2012-10-15T16:37:28Z

Brad:

{{BZFS_API_Doc}}
{{BZFS_API_Events}}

==Overview==
The '''bz_eAllowFlagGrab''' is an API event that is called each time a player is about to grab a flag.
==Data==
'''bz_eAllowFlagGrab''' returns the '''bz_AllowFlagGrabData_V1''' data class.

{| border="1" cellpadding="20" cellspacing="0"
!name
!type
!value description
|-
|eventType
|[[Event(API)|bz_eEventType]]
|bz_eAllowFlagGrab
|-
|playerID
|int
|The ID of the player who is grabbing the flag
|-
|pos
|float[3]
|The position of the player about to grab the flag
|-
|flagID
|int
|The ID of the flag that is going to be grabbed
|-
|flagType
|const char*
|The type of the flag about to be grabbed
|-
|allow
|bool
|Whether or not to allow the flag grab
|}

Bz eAllowFlagGrabEvent

2012-10-15T16:36:19Z

Brad: moved Bz eAllowFlagGrabEvent to Bz eAllowFlagGrab: this is the real name for the event

#REDIRECT [[Bz eAllowFlagGrab]]

Bz eAllowFlagGrab

2012-10-15T16:36:19Z

Brad: moved Bz eAllowFlagGrabEvent to Bz eAllowFlagGrab: this is the real name for the event

{{BZFS_API_Doc}}
{{BZFS_API_Events}}

==Overview==
The '''bz_eAllowFlagGrabEvent''' is an API event that is called each time a player is about to grab a flag.
==Data==
'''bz_eAllowFlagGrabEvent''' returns the '''bz_eAllowFlagGrabEvent_V1''' data class.

{| border="1" cellpadding="20" cellspacing="0"
!name
!type
!value description
|-
|eventType
|[[Event(API)|bz_eEventType]]
|bz_eAllowFlagGrabEvent
|-
|playerID
|int
|The ID of the player who is grabbing the flag
|-
|pos
|float[3]
|The position of the player about to grab the flag
|-
|flagID
|int
|The ID of the flag that is going to be grabbed
|-
|flagType
|const char*
|The type of the flag about to be grabbed
|-
|allow
|bool
|Whether or not to allow the flag grab
|}

Bz eListServerUpdateEvent

2012-10-15T16:21:49Z

Brad: /* Data */

{{BZFS_API_Doc}}
{{BZFS_API_Events}}

==Overview==
The '''bz_eListServerUpdateEvent''' is an API event called before the server adds itself to the list server.

==Data==
'''bz_eListServerUpdateEvent''' returns the '''bz_ListServerUpdateEvent_V1''' data class.

{| border="1" cellpadding="20" cellspacing="0"
!name
!type
!value description
|-
|eventType
|[[Event(API)|bz_eEventType]]
| bz_eListServerUpdateEvent
|-
|address
|[[bz_ApiString]]
|The public address of the server, as specified with the '''-publicaddr''' [[BZFS_Command_Line_Options |command-line option]].
|-
|description
|[[bz_ApiString]]
|The public description of the server, as specified with the '''-publictitle''' [[BZFS_Command_Line_Options |command-line option]].
|-
|groups
|[[bz_ApiString]]
|The groups the server will be advertised to, as specified with the '''-advertise''' [[BZFS_Command_Line_Options |command-line option]].
|-
|handled
|bool
|
|-
|eventTime
|double
|The server time the event occurred (in seconds.)
|}

==Uses==
Allows the plugin to programmatically change the information sent to the list server; all fields (except the event type) are read/write.

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

DevelopmentPlans/2.3

2011-05-23T17:16:21Z

Brad: clarification

==Overview==
BZFlag 2.3 will be a development version that will be released as 2.4.0.0. This is to get around the problem that [[BZFlag 3.0]] development has stalled and does not look like it will continue. This is a last ditch effort to get development moving again.

==Goal==
The goal is to release a new version of [[Main Page|BZFlag]] that is incompatible with 2.0.x for a good reason, and has at least one new feature that will make many players '''want''' to upgrade.

The hope is that this process will renew developer motivation and attract new developers.

==Schedule==
* Move trunk to a v2_99_branch. '''Complete'''
* Copy v2_0branch to trunk and change protocol number. '''Complete'''
* Change the version docs to make compatibility be the minor version number. '''Complete'''
* Solicit specific change proposals that can be completed within one month. Each proposal must be sponsored by an individual developer who will lead its implementation. '''In Progress'''
* When proposals are in and accepted by consensus, start the 1-month countdown clock.
* Implement accepted proposals and test.
* Document server upgrade process for the many server owners.
* After 1 month, revert any changes that have caused unfixed regressions.
* Do a release candidate before final release?
* Tag trunk 2.4.0.0 for release.

==Projects==
These are the many ideas, both new and old, for changes to BZFlag.

===Assignments and tracking===
Task tracking is managed via a google spread sheet that can be found here.

https://spreadsheets.google.com/spreadsheet/pub?hl=en&hl=en&key=0Agca59DESlNKdC1CSUtUMUhiSldrOVVPSHcwQUNzOUE&output=html

Developers with assigned tasks can request edit access to the document on IRC.

===Timeline===
Project must be completed by June 14th 2011 or they will be rolled back and excluded from the release.

===Viable Projects===
The developers believe any (but not all) of the following could be added to 2.3 within the proposed schedule.

====Backports====
These 2.99 features are suitable for porting to 2.3.

* Connection header change (HTTP-style) '''JeffM'''
* New GUI elements '''DTRemenak'''
* Server-side scoring '''DTRemenak'''
* Segmented simulation loop (to prevent wallwalking) '''JeffM'''
* Server-side flag ID and pickup '''Pimpinella'''
* [[2.3_NewShotGraphics|New shot graphics]] (geolaser/geothief) '''JeffM''' '''Discuss on IRC'''
* HUD markers '''JeffM'''
* [[2.3_QualityChanges|Removal of low graphics, promotion of experimental to high]]. '''JeffM'''
* Server list from GSoC '''DTRemenak'''
* BZFS API rework '''JeffM'''
* Remove local authentication (the /identify command) '''JeffM'''
* Windows project cleanup '''JeffM'''
* New make system '''BulletCatcher'''
* New source docs (authors etc...) '''Constitution'''
* Server-side handicap
* Guided Missile shot checks
* Stealth fixes for rabbit '''mdskpr'''
* Asynchronous screenshot compression so client won't freeze up during screenshots '''DTRemenak'''
* BZFlag update notification '''DTRemenak'''
* Wings velocity change (additive flap instead of instant upward velocity) '''blast007''' (r14997, r15162, r15832)
* Message protection (ensure network messages are valid) '''A_Meteorite'''
* Add message types so that actions (/me) are properly implemented '''blast007''' (r19833)
* New artwork '''JeffM'''
* Server option to disable teamkills '''JeffM'''
* OpenFFA '''JeffM'''
* Download URL change (to force just images.bzflag.org, not any .org or .bz) '''Constitution'''
* Remove option to turn off fog '''JeffM'''
* Require OpenGL 1.2 '''JeffM'''
* Only allow a single end shot credit for holding the shield flag '''Thumper'''
* Only players with POLL permission are eligible to take part in a vote '''Thumper'''
* Add the /serverdebug command '''Thumper'''
* bzfs: Report errors to stderr instead of stdout '''Thumper'''
* bzfs: Add -utc switch to output log messages in UTC instead of localtime '''Thumper'''
* bzfs: Fix timestamp buffer size so -ts micros output fits '''Thumper'''
* Joystick input fixes/enhancements '''DTRemenak'''
* Remove -geometry and make -window take a size '''JeffM'''
* bzfs: Allow -time to have an ending time '''blast007'''

====New Changes====
* Round Robin for services '''JeffM'''
* Fix the protocol bug that version [[BZFlag 2.0.16|2.0.16]] was a band-aid for
* Facilitate moving global services (e.g., my.bzflag.org) to new hardware, if any changes will help ''JeffM'' ''Blast007'' ''JoeVano''
* Import client customization settings from the 2.0 config.cfg file to the 2.4 version
* Implement new version numbering system into code. (/src/date/buildDate.cxx and DEVINFO at least, there might be more places where it is needed)

===To Evaluate===
These items need further evaluation to see if they can be or should be backported from 2.99. These may exist as code or patches.

====Backports====
* Map changes '''mdskpr'''
* HTTP plugins '''JeffM'''
* New API events '''JeffM'''
* Custom flag system '''DTRemenak'''
* BZFSCron '''Thumper'''
* Server Side Players '''JeffM'''
* Bug fixes not in notes '''Thumper'''
* Hunter as proper team '''mdskpr (grabbed by DTRemenak)'''
* bzfs -publickey '''trepan'''
* Lua
* push stats as default

====New Changes====
* Countdown/reload timer position fix for when showCoordinates is enabled ''mdskpr''
* SVN props cleanup '''Bullet Catcher'''
* Display BZBB rank images in game. ''JeffM''

===Exclusions===
These items should not be done or backported at this time due to stability issues or the large effort required. These are generally the blocking items preventing 3.0's current release.

* New flags
* Network buffering
* Lag compensation (needs a lot more testing)
* Acceleration changes
* Font system (still has some bugs/glitches and possible performance issues)
* New Translations (requires the new font system)
* Map geometry changes (requires flag zap zone support or breaks existing servers)
* Website changes.

==Known Issues==
===Empty Flag Types===
When you start BZFS with +f good{2} the server will generate 8 "empty" flag IDs in addition to all normal good flags (no flag type.)
This can be seen by doing '/flag show'. You can also '/flag give' the empty flag types, although all it seems to do is say "user: grabbed flag " in chat and make the flag pick-up noise - it doesn't actually give you a flag.

[[Category:Versions]]

DevelopmentPlans/2.3

2011-05-23T17:09:55Z

Brad: known issues -> empty flag types

==Overview==
BZFlag 2.3 will be a development version that will be released as 2.4.0.0. This is to get around the problem that [[BZFlag 3.0]] development has stalled and does not look like it will continue. This is a last ditch effort to get development moving again.

==Goal==
The goal is to release a new version of [[Main Page|BZFlag]] that is incompatible with 2.0.x for a good reason, and has at least one new feature that will make many players '''want''' to upgrade.

The hope is that this process will renew developer motivation and attract new developers.

==Schedule==
* Move trunk to a v2_99_branch. '''Complete'''
* Copy v2_0branch to trunk and change protocol number. '''Complete'''
* Change the version docs to make compatibility be the minor version number. '''Complete'''
* Solicit specific change proposals that can be completed within one month. Each proposal must be sponsored by an individual developer who will lead its implementation. '''In Progress'''
* When proposals are in and accepted by consensus, start the 1-month countdown clock.
* Implement accepted proposals and test.
* Document server upgrade process for the many server owners.
* After 1 month, revert any changes that have caused unfixed regressions.
* Do a release candidate before final release?
* Tag trunk 2.4.0.0 for release.

==Projects==
These are the many ideas, both new and old, for changes to BZFlag.

===Assignments and tracking===
Task tracking is managed via a google spread sheet that can be found here.

https://spreadsheets.google.com/spreadsheet/pub?hl=en&hl=en&key=0Agca59DESlNKdC1CSUtUMUhiSldrOVVPSHcwQUNzOUE&output=html

Developers with assigned tasks can request edit access to the document on IRC.

===Timeline===
Project must be completed by June 14th 2011 or they will be rolled back and excluded from the release.

===Viable Projects===
The developers believe any (but not all) of the following could be added to 2.3 within the proposed schedule.

====Backports====
These 2.99 features are suitable for porting to 2.3.

* Connection header change (HTTP-style) '''JeffM'''
* New GUI elements '''DTRemenak'''
* Server-side scoring '''DTRemenak'''
* Segmented simulation loop (to prevent wallwalking) '''JeffM'''
* Server-side flag ID and pickup '''Pimpinella'''
* [[2.3_NewShotGraphics|New shot graphics]] (geolaser/geothief) '''JeffM''' '''Discuss on IRC'''
* HUD markers '''JeffM'''
* [[2.3_QualityChanges|Removal of low graphics, promotion of experimental to high]]. '''JeffM'''
* Server list from GSoC '''DTRemenak'''
* BZFS API rework '''JeffM'''
* Remove local authentication (the /identify command) '''JeffM'''
* Windows project cleanup '''JeffM'''
* New make system '''BulletCatcher'''
* New source docs (authors etc...) '''Constitution'''
* Server-side handicap
* Guided Missile shot checks
* Stealth fixes for rabbit '''mdskpr'''
* Asynchronous screenshot compression so client won't freeze up during screenshots '''DTRemenak'''
* BZFlag update notification '''DTRemenak'''
* Wings velocity change (additive flap instead of instant upward velocity) '''blast007''' (r14997, r15162, r15832)
* Message protection (ensure network messages are valid) '''A_Meteorite'''
* Add message types so that actions (/me) are properly implemented '''blast007''' (r19833)
* New artwork '''JeffM'''
* Server option to disable teamkills '''JeffM'''
* OpenFFA '''JeffM'''
* Download URL change (to force just images.bzflag.org, not any .org or .bz) '''Constitution'''
* Remove option to turn off fog '''JeffM'''
* Require OpenGL 1.2 '''JeffM'''
* Only allow a single end shot credit for holding the shield flag '''Thumper'''
* Only players with POLL permission are eligible to take part in a vote '''Thumper'''
* Add the /serverdebug command '''Thumper'''
* bzfs: Report errors to stderr instead of stdout '''Thumper'''
* bzfs: Add -utc switch to output log messages in UTC instead of localtime '''Thumper'''
* bzfs: Fix timestamp buffer size so -ts micros output fits '''Thumper'''
* Joystick input fixes/enhancements '''DTRemenak'''
* Remove -geometry and make -window take a size '''JeffM'''
* bzfs: Allow -time to have an ending time '''blast007'''

====New Changes====
* Round Robin for services '''JeffM'''
* Fix the protocol bug that version [[BZFlag 2.0.16|2.0.16]] was a band-aid for
* Facilitate moving global services (e.g., my.bzflag.org) to new hardware, if any changes will help ''JeffM'' ''Blast007'' ''JoeVano''
* Import client customization settings from the 2.0 config.cfg file to the 2.4 version
* Implement new version numbering system into code. (/src/date/buildDate.cxx and DEVINFO at least, there might be more places where it is needed)

===To Evaluate===
These items need further evaluation to see if they can be or should be backported from 2.99. These may exist as code or patches.

====Backports====
* Map changes '''mdskpr'''
* HTTP plugins '''JeffM'''
* New API events '''JeffM'''
* Custom flag system '''DTRemenak'''
* BZFSCron '''Thumper'''
* Server Side Players '''JeffM'''
* Bug fixes not in notes '''Thumper'''
* Hunter as proper team '''mdskpr (grabbed by DTRemenak)'''
* bzfs -publickey '''trepan'''
* Lua
* push stats as default

====New Changes====
* Countdown/reload timer position fix for when showCoordinates is enabled ''mdskpr''
* SVN props cleanup '''Bullet Catcher'''
* Display BZBB rank images in game. ''JeffM''

===Exclusions===
These items should not be done or backported at this time due to stability issues or the large effort required. These are generally the blocking items preventing 3.0's current release.

* New flags
* Network buffering
* Lag compensation (needs a lot more testing)
* Acceleration changes
* Font system (still has some bugs/glitches and possible performance issues)
* New Translations (requires the new font system)
* Map geometry changes (requires flag zap zone support or breaks existing servers)
* Website changes.

==Known Issues==
===Empty Flag Types===
When you start BZFS with +f good{2} the server will generate 8 "empty" flag IDs (no flag type.)
This can be seen by doing '/flag show'. You can also '/flag give' the empty flag types, although all it seems to do is say "user: grabbed flag " in chat and make the flag pick-up noise - it doesn't actually give you a flag.

[[Category:Versions]]

Config File

2011-05-22T20:13:16Z

Brad: Add info on 2.3 config file location

BZFlag uses an ASCII configuration file to store user settings. The file is called "config.cfg."
==Location==
The location of the config file depends on your operating system.
===Windows===
'''XP''': C:\Documents and Settings\[user]\My Documents\My BZFlag Files\2.0\config.cfg 
'''Vista / 7''': C:\Users\[user]\Documents\My BZFlag Files\2.0\config.cfg

(You will need to replace [user] with whichever Windows user name you are currently logged in as.)

===Windows Development Version (2.3)===
'''XP''': C:\Documents and Settings\[user]\Local Settings\Aplication Data\BZFlag\2.4\config.cfg 
'''Vista / 7''': C:\Users\[user]\AppData\Local\BZFlag\2.4\config.cfg 
An easy way to get to the BZFlag config folder is to do '''windows key + r''' then copy/paste '''%LOCALAPPDATA%\BZFlag''' into the box and hit enter. 

(You will need to replace [user] with whichever Windows user name you are currently logged in as.)

===Mac OS X===
~/Library/Application Support/BZFlag/2.0/config.cfg
set list http://my.bzflag.org:81/db

===Linux and unix platforms===
~/.bzf/2.0/config.cfg

Note: "~" is your home directory
==Editing the Config File==
As the config file is a text file, it is possible to directly edit it via text-editor instead of through the built-in GUI. Most things can be edited through the in-game GUI, however, there are some things that you can only add via text-editor. Settings that can only be set by editing the config file directly will be discussed here. (Note: these can also be set in-game with the /localset or /bind commands).

===Localset Options===
set highlightPattern "laser"
set highlightPattern "laser|genocide"
set highlightPattern "(Team Flag|Team's Flag|Genocide)"
''highlightPattern'' highlights lines with the selected words when they appear in the console(chat box).
*When highlighting one word, just type the word in quotes, such as "laser."
*If one wants to highlight two or more words, the words must be separated with a '|', such as "laser|genocide" (highlights lines with laser OR genocide).
*If any of the words have spaces, all the words must be surrounded in parentheses, such as "(Team Flag|Team's Flag|Genocide)" (highlights lines with "Team Flag," "Team's Flag," OR "Genocide").

set linedradarshots 10
set linedradarshots 65
''linedradarshots'' sets how long shots are on the radar. While this option ''is'' set-able through the in-game GUI, you can only set this setting up to 10 via the GUI. You can hand-edit your config to give you longer shot lengths.

set latitude 45
set longitude 71
''latitude'' and ''longitude'' set the latitude and longitude for BZFlag's sky rendering system.

''Hint: To always have a black sky set latitude 90 (north pole) or -90 (south pole) for winter/summer respectively.''

===Binding Custom Keys===
One can bind custom keys outside of those given in the in-game GUI.

The standard format for binding a key is as follows:
bind <event> <press> <action>

The event is the key or button that was pressed (or a combination of keys) such as F or "Shift+Page Up". The double quotes are necessary if there are spaces. The press will be one of up, down, or both. If it is set to up, for example, if will only trigger when they key or button is released. And finally, the action is what will be triggered.

For example, the following binding sets ''displayRadarRange'', or how far the radar is zoomed, to 0.12, when the key '`' is pressed.
bind ` down "set displayRadarRange 0.12"

One can use this template to set any of the options in the config file. However, some of the options, like ''radarsize'' need an additional function call that is only called via the options menu, and as such cannot be altered with this method.

One can also use the toggle keyword instead of set to have a key toggle two options:
bind F down "toggle linedradarshots 65"
bind F down "toggle linedradarshots 65 10"
The first line toggles the length of shots on the radar between 65 and an implied 0. The second line toggles ''linedradarshots'' between 65 and 10. This is much easier than having two keys to switch between two options.

''(Don't do this.)''
bind F down "set linedradarshots 65"
bind G down "set linedradarshots 10"

You can also bind one key with two funtions:

bind E down fire
bind E up identify

This will make it so you can fire and lock-on with GM with the same button.

To un-bind a key, just place a hash(#) at the front of the line, or remove the line completely. For example, to if one is tired of unintentionally hitting F12, he or she can simply disable it.
#bind F12 down quit


[[Category:Client]]

Bz fireWorldGM

2010-04-05T02:18:10Z

Brad: dt = delay time

{{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.
}}

Category:Leagues

2009-06-02T19:12:37Z

Brad: add irc link

== BZFlag Leagues ==

To join a league click on one of the links below and register your callsign. Some leagues may require that you be added to a list by an admin before you are allowed to talk/spawn on match servers. Please use the same callsign for matching that you have register on the league site. Most of the IRC channels for each league are situated on the [http://freenode.net/ freenode] network. Please refer to [[BZFlag on IRC]] for help on using IRC.

== Ducati League ==
Website: [http://league.bzflag.org/ http://league.bzflag.org/]

IRC Channel: [irc://irc.freenode.net/##ducleague ##ducleague]

Match Length: 15, 20 or 30 minutes

Rules: 2 shots, no jumping, ricochet, CTF, randomly generated map.

== [[GU League]] ==
Website: [http://gu.bzleague.com/ http://gu.bzleague.com/]

IRC Channel: [irc://irc.freenode.net/#guleague #guleague]

Match Length: 30 minutes.

Rules: 3 shots, jumping, ricochet, CTF, [[HiX]] map.

== Pillbox League ==
Website: [http://pillbox.bzleague.com/ http://pillbox.bzleague.com/]

IRC Channel: [irc://irc.freenode.net/#pillbox #pillbox]

Match Length: 15, 20 or 30 minutes.

Rules: 3 shots, no jumping, no ricochet, CTF, pillbox map.

== [[Open League]] ==
Website: [http://openleague.net/ http://openleague.net/]

IRC Channel: [irc://irc.freenode.net/#openleague.net #openleague.net]

Match Length: 15, 20, 30, 45 or 60 minutes.

Rules: 3 shots, jumping , ricochet, CTF, [[babel]] or a map that changes every week (which can have different rules).

== Plosileague ==

'''League is dead.'''

Website: [http://bzfx.net/league/ http://bzfx.net/league/]

IRC Channel: [irc://irc.freenode.net/#plosileague #plosileague]

Match Length: 30 minutes or first to 5 caps and ahead of the other team by at least 2 caps

Rules: 3 shots, jumping, ricochet, CTF, [[overlord]] or [[babel]] map.

== 1vs1 League ==
Website: [http://1vs1.bzleague.com/ http://1vs1.bzleague.com/]

IRC Channel: None.

Match Length: First to 10 kills.

Rules: 2 shots, no jumping, ricochet, small randomly generated map.

== Fun League ==
Website: [http://fun.bzleague.com/ http://fun.bzleague.com/]

IRC Channel: None.

Match Length: Depends on which map you play on.

Rules: Depends on which map you play on.

== BZSoccer League ==

Website: [http://bzsoccer.bzleague.com/ http://bzsoccer.bzleague.com/] *Note* Website is not maintained by anyone and has many bugs.

IRC Channel: ##divi

Match length: 15 minutes

Rules: 2 shots, jumping, ricochet, soccer field map.

*Note* Please note that this league is now dead. The owner has moved on, so if anyone wants to take the league you are more than welcome too.

List Server Usage Policy

2007-11-20T22:48:23Z

Brad:

==Overview==
The list server usage policy describes the intended use of the BZFlag [[List Server]] service that is provided by the project administration. It also describes the acceptable behaviour for the users of the system.

==Policy==
The list server is provided free of charge to the BZFlag players and server owners. Use of the list server, however, is provided under stipulations of what is fair and reasonable for being non-disruptive to the game and our community.

For players the list server provides a list of compatible internet games, public service messages, and an account verification system that can tie a player to their BZFlag discussion forum account ( also known as their 'Global Login' and their BZBB account ). All interactions with the list server are potentially logged or monitored. All information sent to the list server is kept confidential and is only used by the project staff for administration and development purposes.

Players who are disruptive or fraudulent to any of BZFlag's public services including (but not limited to) project and league services, multiple servers, or large groups of individuals may be denied access to the public list servers at any time, and at the sole discretion of the BZFlag list server administrators. Players who have been known to cheat or abuse the game on multiple public servers may also be denied access. Similarly, anyone engaging in denial-of-service attacks or are otherwise detrimentally impacting the public services may have their access blocked.

For server owners, the list server provides public listing of any number of BZFlag game server (bzfs) instances, as well as token and permission group verification for global login services. No player personal information is sent from the list server to the game servers other than the player's callsign and their global login status.

Server owners who run servers that are cheat servers ( publicly advertised or not ), use disruptive server modifications, use "bot" clients to artificially inflate their list position, or have disruptive or slanderous names or descriptions may be removed from the list and/or have access to other BZFlag public services revoked.

The project itself does not have anything to do with exactly how specific servers are run or administered unless the server affects other servers or large groups of players.

It is important to understand that the list is provided for free at the project's discretion. The data contained in it, nor the service of hosting it is in any way "open source" and no user has any inherent "right" to use any of the public services. We provide those services for the betterment of the community and abuse will not be tolerated.

The project reserves the right to allow or disallow access to any public or project service to any user at any time without notice and without reason.

Airspawn

2007-09-06T07:15:48Z

Brad:

Airspawn is a standard [[Plug-ins|plug-in]] that is shipped with the [[BZFlag Source|source code]]. It allows the starting, or [[spawning]] position of a player tank to be somewhere in the air. Airspawn is included in [[BZFlag 2.0.4|v2.0.4]] and later releases.

==Usage==
When the airspawn is loaded it can take an [[Plug-ins#Parameters|optional parameter]] that represents the maximum height variance that will be applied to a spawn position. The default value is 10 [[world units]]. With the plugin loaded, the height above ground of tank spawns will be a random value between 0 and the maximum value. The usage is:

-loadplugin "X:\path\to\the\plugin\airspawn.dll,<maxHeight>"

or in an already running game:

/loadplugin "X:\path\to\the\plugin\airspawn.dll,<maxHeight>"

Examples:

-loadplugin "C:\Program Files\BZFlag2.0.8\airspawn.dll,100"
-loadplugin "/usr/local/bzflag2.0.8/plugins/airspawn.dll,100"

The "-loadplugin" syntax is used in the [[sample conf|server configuration]] file or at the command line when invoking a game [[BZFS|server]].

==History==
Airspawn was the very first plug-in made, it was a proof of concept for the API.

[[Category:Development]]
[[Category:Plug-Ins]]

BZFlag on IRC

2007-09-06T07:10:33Z

Brad:

The BZFlag communities use the [http://freenode.net/ freenode IRC network] for communication and collaboration. [http://en.wikipedia.org/wiki/IRC IRC]

The [http://freenode.net/ freenode network] is used for all IRC communications.
Common channels include:
* #bzflag
* #bzchat

A web interface is provided to these channels at http://my.BZFlag.org/irc/irc.cgi
==Channels==

===#bzflag===
The #bzflag channel is the primary development and support channel. The major developers and many long time community members are users. Discussions in the channel range from development and coding discussions to technical support and bug reports. #bzflag is a great channel to discuss new features and bugs. The channel is moderated by the project administration and development staff.

===#bzchat===
The #bzchat channel is a more informal channel designated for player community discussions.

===Other channels===
A number of players, servers, and [[leagues]] have their own channel for more focused discussion, some of these include:

* ##bar (DUCLeague team, The Barbarians)
* #BoomBZ (Team Channel for GU team [BoOm])
* #bzfx (Support channel for the bzfx.net BZFlag servers)
* #bzw (A place to discuss map making for BZFlag, including ideas and help)
* ##bz-inc (DUCLeague team, [http://my.bzflag.org/league/index.php?link=teaminfo&id=689/ Bz-Incorporated])
* #dub (Support channel for the dub.bzflag.org BZFlag servers)
* ##ducleague (Support channel for [http://my.bzflag.org/league/ Ducati League (DucLeague)])
* ##guleague (Support channel for [http://gu.bzleague.com/ GamesUnited League (GULeague)])
* #hepcat (Support channel for borrego.hepcat.org BZFlag server)
* ##icf (Support channel for [http://gu.bzleague.com/index.php?link=teaminfo&id=112 Insane Crazy Funsters, (GULeague)])
* #forestforce ([http://gu.bzleague.com/index.php?link=teaminfo&id=10 GULeague Team])
* #inleague (Support channel for [http://in.bzleague.com InterNational League (INLeague)])
* #kas (GULeague team, KAS)
* ##norang (Support channel for [http://bzflag.norang.ca Norang.ca] BZFlag servers)
* #pillbox (Support channel for [http://pillbox.bzleague.com/ Pillbox League (PBLeague)])
* ##planetmofo (Support channel for [http://www.planet-mofo.com planet-mofo.com] servers)
* #plosileague (Support channel for [http://bzfx.net/league/ Plosileague])
* #silvercat (Support channel for [http://silvercat.bzflag.org/ Silvercat BZFlag servers])
* ##t42 ([http://gu.bzleague.com/index.php?link=teaminfo&id=39 GULeague team])
* ##untamed ([http://my.bzflag.org/league/index.php?link=teaminfo&id=909 DUCLeague team])

==IRC Clients==
To access the IRC network you need to use an IRC client, there are many IRC client softwares available for most operating systems.

http://irchelp.org/ is an excellent resource for more information on general IRC.

===Web IRC Interface===
The project provides a [http://my.BZFlag.org/irc/irc.cgi web based interface] to the main IRC channels. These are intended mostly for tech support issues, and the web interface is limited in the number of channels it can access.

==External links==
http://my.BZFlag.org/irc/irc.cgi

http://irchelp.org/

[[Category:Development]]
[[Category:Support]]

BZFlag on IRC

2007-09-06T07:09:17Z

Brad: remove dead and duplicate chans

The BZFlag communities use the [http://freenode.net/ freenode IRC network] for communication and collaboration. [http://en.wikipedia.org/wiki/IRC IRC]

The [http://freenode.net/ freenode network] is used for all IRC communications.
Common channels include:
* #bzflag
* #bzchat

A web interface is provided to these channels at http://my.BZFlag.org/irc/irc.cgi
==Channels==

===#bzflag===
The #bzflag channel is the primary development and support channel. The major developers and many long time community members are users. Discussions in the channel range from development and coding discussions to technical support and bug reports. #bzflag is a great channel to discuss new features and bugs. The channel is moderated by the project administration and development staff.

===#bzchat===
The #bzchat channel is a more informal channel designated for player community discussions.

===Other channels===
A number of players, servers, and [[leagues]] have their own channel for more focused discussion, some of these include:

* ##bar (DUCLeague team, The Barbarians)
* #BoomBZ (Team Channel for GU team [BoOm])
* #bzfx (Support channel for the bzfx.net BZFlag servers)
* #bzw (A place to discuss map making for BZFlag, including ideas and help)
* ##bz-inc (DUCLeague team, [http://my.bzflag.org/league/index.php?link=teaminfo&id=689/ Bz-Incorporated])
* #dub (Support channel for the dub.bzflag.org BZFlag servers)
* ##ducleague (Support channel for [http://my.bzflag.org/league/ Ducati League (DucLeague)])
* #guleague (Support channel for [http://gu.bzleague.com/ GamesUnited League (GULeague)])
* #hepcat (Support channel for borrego.hepcat.org BZFlag server)
* ##icf (Support channel for [http://gu.bzleague.com/index.php?link=teaminfo&id=112 Insane Crazy Funsters, (GULeague)])
* #forestforce ([http://gu.bzleague.com/index.php?link=teaminfo&id=10 GULeague Team])
* #inleague (Support channel for [http://in.bzleague.com InterNational League (INLeague)])
* #kas (GULeague team, KAS)
* ##norang (Support channel for [http://bzflag.norang.ca Norang.ca] BZFlag servers)
* #pillbox (Support channel for [http://pillbox.bzleague.com/ Pillbox League (PBLeague)])
* ##planetmofo (Support channel for [http://www.planet-mofo.com planet-mofo.com] servers)
* #plosileague (Support channel for [http://bzfx.net/league/ Plosileague])
* #silvercat (Support channel for [http://silvercat.bzflag.org/ Silvercat BZFlag servers])
* ##t42 ([http://gu.bzleague.com/index.php?link=teaminfo&id=39 GULeague team])
* ##untamed ([http://my.bzflag.org/league/index.php?link=teaminfo&id=909 DUCLeague team])

==IRC Clients==
To access the IRC network you need to use an IRC client, there are many IRC client softwares available for most operating systems.

http://irchelp.org/ is an excellent resource for more information on general IRC.

===Web IRC Interface===
The project provides a [http://my.BZFlag.org/irc/irc.cgi web based interface] to the main IRC channels. These are intended mostly for tech support issues, and the web interface is limited in the number of channels it can access.

==External links==
http://my.BZFlag.org/irc/irc.cgi

http://irchelp.org/

[[Category:Development]]
[[Category:Support]]

Category:Client

2007-07-07T00:48:41Z

Brad: Undo revision 2669 by Special:Contributions/QuwUm4 (User talk:QuwUm4)

Pages that are related to the BZFlag Client

Category:Support

2007-07-07T00:48:01Z

Brad: Undo revision 2668 by Special:Contributions/203.162.27.90 (User talk:203.162.27.90)

BZFlag SVN

2007-06-27T17:14:48Z

Brad:

BZFlag SVN, is the [http://en.wikipedia.org/wiki/Subversion_(software) Subversion Revision Control System] used by the development team to maintain and store the [[BZFlag Source]] code. The SVN system is hosted by [http://www.sourceforge.net SourceForge] and is accessible by anyone with the proper software. The SVN system replaces the [[BZFlag CVS]] system that was used in the past.

==SVN clients==
To access the source code via SVN , you will need a SVN client. Most unix/linux type operating systems have the command line SVN client as an installable option. Windows users must download the Windows native [http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=91 SVN command line utility] or a third party SVN client, such as [http://tortoisesvn.tigris.org/ the Tortoise Graphical SVN Client] (highly recommended). SVN is also available to Windows users via [http://cygwin.com/ Cygwin] with SVN and other common Devel tools selected during installation.

==Getting code from SVN Access==
===Command line===
The simplest way to get the bzflag source code is to use the URL for the current ( or TRUNK ) bzflag module.

$ svn co <nowiki>https://bzflag.svn.sourceforge.net/svnroot/bzflag/trunk/bzflag</nowiki>

This will get you the current bzflag source code for the development version.

If you want the SVN code for the 2.0.x compatible version use the URL

$ svn co <nowiki>https://bzflag.svn.sourceforge.net/svnroot/bzflag/branches/v2_0branch/bzflag</nowiki>

If you wish to get all of our source code in one step, you can get the entire repository with the command.

$ svn co <nowiki>https://bzflag.svn.sourceforge.net/svnroot/bzflag</nowiki> bzflag

This will get all modules, branches, tags, and subdirs. Beware! This is a very large amount of data (make sure you have at least 2.7 GB of disk space available) and will take a while and will be rather useless, as it is the code for every version of bzflag. Most users will only need the code for one specific version.

The '''best''' way, is to only get the subdir for the module you are interested in. This is much more efficient and suitable for most users. The most common module to get is the bzlag module, as it is the actual game.

Please see the sections below for more information about the URLs to use for branches and modules.

===TortoiseSVN===

Windows users that use the Tortoise Graphical SVN Client simply enter the URL of the SVN path they wish to check out in the field marked ''URL of repository''. For the current version of all modules simply use the /trunk path. Note, if you want your code to be checked out into a new folder, be sure to enter that folder name in the ''Checkout directory'' field.

If you wish to get only a single module subdir, or a revision, simply use the URL specified in the sections below.

==Committing Code to SVN==

Project developers that need write access to the source code to make changes ( or [[commits]] ) need to provide their sourceforge username and password when doing a SVN commit. A sourceforge account is required for developer access, as well as approval from a project administrator.

===Command Line===
Using the command
svn commit
in a directory that has code changes will commit any changed code back to the repository. The svn client will prompt you for your username and password.

===TortoiseSVN===
Windows users that use the Tortoise Graphical SVN Client can simply choose the SVN commit item, and enter their username and password when prompted.

==Updating code from SVN to the current version==

===Command Line===
Using the command
svn up
in the directory that has checked out code will cause subversion to update that code to the current version for that branch.

===TortoiseSVN===
Windows users that use the Tortoise Graphical SVN Client can simply choose the SVN update item from their right click menus.

==Reverting local code to the server's version==

===Command Line===
Using the command
svn revert
svn up
in the directory that has checked out code will cause subversion to set flags on all modified local files, then update the code to match the code on the server. NOTE: This has the effect of wiping out all local changes, so use with caution!

===TortoiseSVN===
Right click on the file or directory you would like to revert and from the TortoiseSVN submenu, select '''Revert...'''. The menus is context sensitive, so there must be code that has been modified for the menu choice to be available.

==Module sub directories==

The source code in SVN is broken up into a number of modules for ease of use and management. When requesting the source code from the SVN system a sub-directory may be specified to limit the code that is accessed.

The current SVN modules are:
*bzflag : The main module that includes the game [[client]], [[BZFS|server]], [[plug-ins]], and [[BZAdmin]].
*admin : The [[Master Ban]] list
*bzedit : The linux version of the BZFlag map editor [[BZEdit]]
*bzeditw32 : The windows version of the BZFlag map editor [[BZEditWin32]]
*web : The main website at http://www.bzflag.org
*db : Files related to the website http://my.bzflag.org and the [[Global Registration]] system.
*pybzflag : an abandoned python implementation of BZFlag

to get the current version of a module, you would add
/trunk/MODULE_NAME
after the normal SVN URL.

so to get the current version of just the bzflag module, the URL would be

<nowiki>https://bzflag.svn.sourceforge.net/svnroot/bzflag/trunk/bzflag/</nowiki>

From the command line

$ svn co <nowiki>https://bzflag.svn.sourceforge.net/svnroot/bzflag/trunk/bzflag</nowiki>

==Branches==
Branches in subversion are simply subfolders.
All branches are in the /branches subdirectory that if off the root level of the SVN tree.
they can be viewed here, http://bzflag.svn.sourceforge.net/viewvc/bzflag/branches/
To get the code in a branch, you simply use the branch URL in your svn client.

To get the 2.0.x branch of the BZFlag module, you'd use the following URL.
https://bzflag.svn.sourceforge.net/svnroot/bzflag/branches/v2_0branch/bzflag/

==See also==
[[BZFlag Version Numbers]]

==External Links==
[http://sourceforge.net/svn/?group_id=3248 SourceForge SVN Access page]

[http://bzflag.svn.sourceforge.net/viewvc/bzflag/ BZFlag SVN Tree]

[[Category:Development]]
[[Category:Compiling]]
[[Category:Versions]]

Box

2007-06-11T16:30:20Z

Brad: Undo revision 2519 by Special:Contributions/75.68.151.61 (User talk:75.68.151.61)

A Box is a [[BZW]] map structure that defines a rectilinear parellepiped in the world.

==Code==
[[Image:BoxeAppearance.png|frame|right|Default boxes]]
The code for a box object is as follows
{|
|
box
position 10 20 30
rotation 45
size 1 2 3
end
|}
Valid parameters for a box are
<properties>
position=defines the center of the box in X and Y and the bottom of the box in Z.
rotation=defines a rotation around the Z axis for the box, in degrees.
size=defines the distance from the center to the side of the box in X and Y, and the total height of the box in Z.
</properties>

Boxes do not support [[Material]], [[Texture Matrix]], or [[Physics Drivers]]. The [[Meshbox]] object replaces the box object and supports these features.

==Appearance==
Box objects by default have a red brick texture on the vertical sides, and a white plaster texture on the top and bottom.

==History==
The box is one of the original objects supported by BZFlag and has been a mainstay of maps since the very beginning. Boxes are heavily used by the software when generating random maps. In [[BZFlag 2.0.0|v2.0.0]] the box was replaced with the [[meshbox]] object to support [[Material|Materials]] and [[Physics Drivers]]. The original box definition was left unchanged, in order to maintain functional compatibility for older maps.

==Editor Support==
The box object is supported by all known editors.

[[Category:Map Making]]
[[Category:Map Objects]]

Help:Contents

2007-06-11T16:29:48Z

Brad: Undo revision 2521 by Special:Contributions/FxbJb7 (User talk:FxbJb7)

To many people a wiki is a new and interesting concept. A wiki is a web site where everyone is allowed, and even encouraged, to add, edit, and/or correct any page. While this would seem to lead to mass chaos, the concept surprisingly works. As you are editing pages, others are reading them and making corrections. So with an active and vibrant community the wiki becomes a better and better place, all of the time. We encourage everyone to contribute (please read the [[BZFlagWiki:Content Policy|Content Policy]]) and remember the BZFlag Wiki motto: [[BZFlagWiki:Be_bold|'''Be Bold''']]
;Reading
:[[Help:Navigation|Navigation]]
:[[Help:Searching|Searching]]
:[[Help:Tracking changes|Tracking changes]]
;Editing
:[[Help:Editing pages|Editing pages]]
:[[Help:Starting a new page|Starting a new page]]
:[[Help:Formatting|Formatting]]
:[[Help:Links|Links]]
:[[Help:Categories|Categories]]
;Advanced Editing
:[[Help:Images|Images]]
:[[Help:Tables|Tables]]
:[[Help:Templates|Templates]]
:[[Help:Variables|Variables]]
:[[Help:Managing files|Managing files]]
;Customizing
:[[Help:Preferences|Preferences]]
:[[Help:Skins|Skins]]
;Administration
:[[Help:Interwiki linking|Interwiki linking]]
:[[Help:Namespaces|Namespaces]]

[[Category:Help| ]]

AHOD

2007-06-11T16:28:55Z

Brad: spam

[[Image:Ahod.jpg|thumb|right|All Hands On Deck]]
[[AHOD]] (All Hands On Deck) is a map and play-style originally created by [[trepan]]. It has since been updated by [[brad]] and now uses a [[plugin]] instead of a server mod. The aim is to get the enemy flag and a certain percentage of your team to the Deck to make a capture. The Deck is marked by an arrow and a flashing halo, as well as [[ShockWave|shockwaves]] on radar - you can't miss it.

You can be on either the Red or Green team, the blue team platform is the target Deck. Once someone is on the Deck with the enemy flag the plugin will announce how many more people on your team are required to make a capture. When the flag is captured both teams die and respawn at their bases.

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

Talk:Main Page

2007-06-10T19:39:04Z

Brad: spam

I said bzflag-256x256.png, not the 48x48 one! [[User:TD-Linux|TD-Linux]] 17:27, 11 February 2007 (EST)

----

Yay!!! MediaWiki!!! [[User:SilverFox|SilverFox]] 12:07, 19 February 2007 (EST)

----

The main page redirects form "BZFlag" wt? shouldn't we have a BZFlag page with a summary of it? --[[User:Me1|Me1]] 18:48, 13 March 2007 (EDT)

----

== Flag Ideas needs some responses, ==

[[Flag Ideas]] needs someone to go and respond to it. There are a lot of good ideas that haven't been responded to. They need responses. Most of them were posted by me. [[User:71.34.240.223|71.34.240.223]] 20:52, 5 June 2007 (EDT)

When a developer decides to look at them, they will. If you want to code them up and submit them as patches feel free (no guarantee that the patches will be accepted). No one is getting paid for this, they code in their spare time for fun (yeah, fun... that's it). I looked them over and from past experience most will be rejected (some of the ideas have been suggested in other places) if you really want to know. [[User:DonnyBaker|DonnyBaker]] 05:50, 6 June 2007 (EDT)

Help:Contents

2007-06-10T19:37:15Z

Brad: Undo revision 2510 by Special:Contributions/HzoWdh (User talk:HzoWdh)

Talk:BZFlag Forums

2007-06-06T08:32:03Z

Brad: New page: what is the point of this? did you not notice the link to the forums in the menu on the left? ----

what is the point of this? did you not notice the link to the forums in the menu on the left?
----

Help:Contents

2007-05-16T20:41:46Z

Brad: remove spam

Change Default Font

2007-03-01T07:36:00Z

Brad:

It is little known, except among [[BZFlag_on_IRC|#bzflag irc]] visitors, that there is a second font designed specially for console use included with [[BZFlag2.0.8|BZFlag 2.0]]. It's called ProFont and I adapted it to [[BZFlag]] after seeing an attempt by [[DTRemenak]] to do the same out of a TTF file (which didn't turn out too good); it has a 50% transparent black border for readability in the sky and other bright places. It might be a bit small for high-resolution screens at its default size (8pt), but it's far more readable than Vera Mono in my opinion. The best way to describe it is to show you what it looks like.. if you want to see some screenshots before changing your BZFlag to it, check them out here:

http://turbogfx.homelinux.org/imgfiles/bzflag-ss/profont-bz/

The first is of the normal (8pt) font, and the second one is of the "micro" (6pt) font.

So if you decide you'd like to try it out for yourself...
To change your console font to ProFont, locate your config file:

For Windows: <code>C:\Documents and Settings\<User>\<User's Documents>\My BZFlag Files\2.0\config.cfg</code>

For Mac OS X: <code>~/Library/Application\ Support/2.0/config.cfg</code>

For Linux and relatives: <code>~/.bzf/2.0/config.cfg</code>

Open the config in a text editor and add this line to it:

set consoleFont profont

Save the file, then start [[BZFlag]] and see the new font in action.

[This article was originally created by [[Legoguy]] - See [http://my.bzflag.org/bb/viewtopic.php?t=2677 here].]

[[Category:Client]]

Change Default Font

2007-03-01T07:34:32Z

Brad:

It is little known, except among [[BZFlag_On_IRC|#bzflag irc]] visitors, that there is a second font designed specially for console use included with [[BZFlag2.0.8|BZFlag 2.0]]. It's called ProFont and I adapted it to [[BZFlag]] after seeing an attempt by [[DTRemenak]] to do the same out of a TTF file (which didn't turn out too good); it has a 50% transparent black border for readability in the sky and other bright places. It might be a bit small for high-resolution screens at its default size (8pt), but it's far more readable than Vera Mono in my opinion. The best way to describe it is to show you what it looks like.. if you want to see some screenshots before changing your BZFlag to it, check them out here:

http://turbogfx.homelinux.org/imgfiles/bzflag-ss/profont-bz/

The first is of the normal (8pt) font, and the second one is of the "micro" (6pt) font.

So if you decide you'd like to try it out for yourself...
To change your console font to ProFont, locate your config file:

For Windows: <code>C:\Documents and Settings\<User>\<User's Documents>\My BZFlag Files\2.0\config.cfg</code>

For Mac OS X: <code>~/Library/Application\ Support/2.0/config.cfg</code>

For Linux and relatives: <code>~/.bzf/2.0/config.cfg</code>

Open the config in a text editor and add this line to it:

set consoleFont profont

Save the file, then start [[BZFlag]] and see the new font in action.

[This article was originally created by [[Legoguy]] - See [http://my.bzflag.org/bb/viewtopic.php?t=2677 here].]

[[Category:Client]]

Category:Plug-Ins

2007-02-28T23:24:23Z

Brad:

Plug-ins are server side extensions written in C++ that are loaded at run time by the server.

BZFlag on IRC

2007-02-27T20:00:03Z

Brad: spelling

The BZFlag communities use the [http://freenode.net/ freenode IRC network] for communication and collaboration. [http://en.wikipedia.org/wiki/IRC IRC]

The [http://freenode.net/ freenode network] is used for all IRC communications.
Common channels include:
* #bzflag
* #bzchat

A web interface is provided to these channels at http://my.BZFlag.org/irc/irc.cgi
==Channels==

===#bzflag===
The #bzflag channel is the primary development and support channel. The major developers and many long time community members are users. Discussions in the channel range from development and coding discussions to technical support and bug reports. #bzflag is a great channel to discuss new features and bugs. The channel is moderated by the project administration and development staff.

===#bzchat===
The #bzchat channel is a more informal channel designated for player community discussions.

===Other channels===
A number of players, servers, and [[leagues]] have their own channel for more focused discussion, some of these include:

* #bzfx (Support channel for the bzfx.net BZFlag servers)
* #dub (Support channel for the dub.bzflag.org BZFlag servers)
* ##ducleague (Support channel for [http://my.bzflag.org/league/ Ducati League (DucLeague)])
* #guleague (Support channel for [http://gu.bzleague.com/ GamesUnited League (GULeague)])
* #hepcat (Support channel for borrego.hepcat.org BZFlag server)
* ##icf (Support channel for [http://gu.bzleague.com/index.php?link=teaminfo&id=112 Insane Crazy Funsters, (GULeague)])
* #forestforce ([http://gu.bzleague.com/index.php?link=teaminfo&id=10 GULeague Team])
* #inleague (Support channel for [http://in.bzleague.com InterNational League (INLeague)])
* ##norang (Support channel for [http://bzflag.norang.ca|bzflag.norang.ca] BZFlag servers)
* ##openleague (Support channel for [http://openleague.org/ OpenLeague])
* #pillbox (Support channel for [http://pillbox.bzleague.com/ Pillbox League (PBLeague)])
* ##planetmofo (Support channel for [http://www.planet-mofo.com planet-mofo.com] servers)
* #plosileague (Support channel for plosileague, website currently down)
* #silvercat (Support channel for [http://silvercat.bzflag.org/ Silvercat BZFlag servers])
* ##t42 ([http://gu.bzleague.com/index.php?link=teaminfo&id=39 GULeague team])
* ##untamed ([http://my.bzflag.org/league/index.php?link=teaminfo&id=909 DUCLeague team])

==IRC Clients==
To access the IRC network you need to use an IRC client, there are many IRC client softwares available for most operating systems.

http://irchelp.org/ is an excellent resource for more information on general IRC.

===Web IRC Interface===
The project provides a [http://my.BZFlag.org/irc/irc.cgi web based interface] to the main IRC channels. These are intended mostly for tech support issues, and the web interface is limited in the number of channels it can access.

==External links==
http://my.BZFlag.org/irc/irc.cgi

http://irchelp.org/

BZFlag on IRC

2007-02-27T19:59:34Z

Brad: typo

The BZFlag communities use the [http://freenode.net/ freenode IRC network] for communication and collaboration. [http://en.wikipedia.org/wiki/IRC IRC]

The [http://freenode.net/ freenode network] is used for all IRC communications.
Common channels include:
* #bzflag
* #bzchat

A web interface is provided to these channels at http://my.BZFlag.org/irc/irc.cgi
==Channels==

===#bzflag===
The #bzflag channel is the primary development and support channel. The major developers and many long time community members are users. Discussions in the channel range from development and coding discussions to technical support and bug reports. #bzflag is a great channel to discuss new features and bugs. The channel is moderated by the project administration and development staff.

===#bzchat===
The #bzchat channel is a more informal channel designated for player community discussions.

===Other channels===
A number of players, servers, and [[leagues]] have their own channel for more focused discussion, some of these include:

* #bzfx (Support channel for the bzfx.net BZFlag servers)
* #dub (Support channel for the dub.bzflag.org BZFlag servers)
* ##ducleague (Support channel for [http://my.bzflag.org/league/ Ducati League (DucLeague)])
* #guleague (Support channel for [http://gu.bzleague.com/ GamesUnited League (GULeague)])
* #hepcat (Support channel for borrego.hepcat.org BZFlag server)
* ##icf (Support channel for [http://gu.bzleague.com/index.php?link=teaminfo&id=112 Insane Crazy Funsters, (GULeague)])
* #forestforce ([http://gu.bzleague.com/index.php?link=teaminfo&id=10 GULeague Team])
* #inleague (Support channel for [http://in.bzleague.com InterNational League (INLeague)])
* ##norang (Support channel for [http://bzflag.norang.ca|bzflag.norang.ca] BZFlag servers)
* ##openleague (Support channel for [http://openleague.org/ OpenLeague])
* #pillbox (Support channel for [http://pillbox.bzleague.com/ Pillbox League (PBLeague)])
* ##planetmofo (Support channel for [http://www.planet-mofo.com planet-mofo.com] servers)
* #plosileague (Support channel for plosileague, website currently down)
* #silvercat (Support channel for [http://silvercat.bzflag.org/ Silvercat BZFlag servers])
* ##t42 ([http://gu.bzleague.com/index.php?link=teaminfo&id=39 GULeague team])
* ##untamed ([http://my.bzflag.org/league/index.php?link=teaminfo&id=909 DUCLeague team])

==IRC Clients==
To access the IRC network you need to use an IRC client, there are many IRC client softwares available for most operating systems.

http://irchelp.org/ is an excelent resource for more information on general IRC.

===Web IRC Interface===
The project provides a [http://my.BZFlag.org/irc/irc.cgi web based interface] to the main IRC channels. These are intended mostly for tech support issues, and the web interface is limited in the number of channels it can access.

==External links==
http://my.BZFlag.org/irc/irc.cgi

http://irchelp.org/

Server Bandwidth

2007-02-26T04:37:08Z

Brad: <math> tags don't exist

'''this page is in need of an update'''

The BZFlag server bzfs uses player^2 bandwidth so limit players to limit bandwidth.

The image below shows bandwidth usage for Badgerking's server. Average of 15 players, 5 shots, +f good{3}, ricochet.

[[Image:Server-bandwidth.jpg]]

[[Category:Server]]

Sample conf

2007-02-22T20:51:54Z

Brad: add category

<nowiki>#</nowiki> This is a BZFlag Server (bzfs) configuration file. 
<nowiki>#</nowiki> It assumes that you wish to connect to the bzflag list server. 
<nowiki>#</nowiki> Please read through it carefully. Lines starting with a <nowiki>#</nowiki> are comments. 
<nowiki>#</nowiki> to enable an option, remove the <nowiki>#</nowiki> at the beginning of a line. To 
<nowiki>#</nowiki> disable that option, put the <nowiki>#</nowiki> back. There are some examples in this 
<nowiki>#</nowiki> file. Make sure you change the examples if you uncomment the line. If 
<nowiki>#</nowiki> you don't know what something does, you are okay to just leave 
<nowiki>#</nowiki> it commented out. Failure to read through this file (looking for 
<nowiki>#</nowiki> already uncommented lines) might be a little embarrassing. Have fun. 
 
 
 
<nowiki>#</nowiki> This option is for debug. You can have as many as 4 of them. 
<nowiki>#</nowiki> simple debug 
<nowiki>#</nowiki>-d 
<nowiki>#</nowiki> and more complex debugging. 
-dd 
<nowiki>#</nowiki>-ddd 
<nowiki>#</nowiki>-dddd 
 
<nowiki>#</nowiki> Sets the admin password for the server. It is necessary for server 
<nowiki>#</nowiki> administration if no groups are used. 
<nowiki>#</nowiki> CHANGE THIS! 
-password abcdef 
 
<nowiki>#</nowiki> Enables inertia and sets the maximum linear and angular accelerations. 
<nowiki>#</nowiki> The units are somewhat arbitrary so you'll have to experiment to find 
<nowiki>#</nowiki> suitable values. The values must be non-negative and higher values 
<nowiki>#</nowiki> yield greater inertia. 
<nowiki>#</nowiki> Used to control "Mouse Enhancements" 
-a 50 38 
 
 
<nowiki>#</nowiki><nowiki>#</nowiki> World <nowiki>#</nowiki><nowiki>#</nowiki> 
 
<nowiki>#</nowiki> This specifies the world filename. 
<nowiki>#</nowiki> Use this format for Windows 
<nowiki>#</nowiki>-world "c:\mymaps\louschurchyard.bzw" 
<nowiki>#</nowiki> Use this format for *nix and Mac 
<nowiki>#</nowiki>-world /users/noob/lousdesktop.bzw 
 
 
<nowiki>#</nowiki><nowiki>#</nowiki> Random World Generation <nowiki>#</nowiki><nowiki>#</nowiki> 
 
<nowiki>#</nowiki> This option allows world objects to be randomly rotated. Only applies 
<nowiki>#</nowiki> if a randomly generated world is used. 
<nowiki>#</nowiki>-b 
 
<nowiki>#</nowiki> Enables capture-the-flag style game with a balanced random map. Default is 
<nowiki>#</nowiki> free-for-all style game. 
<nowiki>#</nowiki>-cr 
 
<nowiki>#</nowiki> Adds teleporters to the game. for random maps only 
<nowiki>#</nowiki>-t 
 
<nowiki>#</nowiki> This option controls the building density on random worlds(1-10) default is 5 
<nowiki>#</nowiki>-density 7 
 
<nowiki>#</nowiki> This option changes the size of random maps. 
<nowiki>#</nowiki>-worldsize 800 
 
<nowiki>#</nowiki> This option gives buildings random heights. This is used when 
<nowiki>#</nowiki> you are using random maps. 
<nowiki>#</nowiki>-h 
 
 
<nowiki>#</nowiki><nowiki>#</nowiki> Game Styles <nowiki>#</nowiki><nowiki>#</nowiki> 
 
<nowiki>#</nowiki> This enables capture-the-flag style game. Default is free-for-all style. 
<nowiki>#</nowiki> Requires one base object for each team to be specified in the world file. 
<nowiki>#</nowiki> Can be used with random world generation. 
<nowiki>#</nowiki>-c 
 
<nowiki>#</nowiki> More than one team-flag may be specified. 
<nowiki>#</nowiki> This is generally not desirable. 
<nowiki>#</nowiki> B* - Blue Team G* - Green Team, P* - Purple Team, R* - Red Team, 
<nowiki>#</nowiki>+f B* 
<nowiki>#</nowiki>+f R* 
 
<nowiki>#</nowiki> This sets the maximum number of shots before a reload. The default 
<nowiki>#</nowiki> is 5. 
-ms 3 
 
<nowiki>#</nowiki> This makes most shots ricochet. 
+r 
 
<nowiki>#</nowiki> This option allows jumping. 
-j 
 
<nowiki>#</nowiki> These two flags can be used if they are not specified as options. 
<nowiki>#</nowiki> +f R{1} <nowiki>#</nowiki> Ricochet 
<nowiki>#</nowiki> +f J{1} <nowiki>#</nowiki> Jumping 
 
<nowiki>#</nowiki> This option allows for flags on box buildings. 
<nowiki>#</nowiki>-fb 
 
<nowiki>#</nowiki> This option allows tanks to spawn on buildings. This is especially useful 
<nowiki>#</nowiki> as tank spawn locations are now are calculated on the server without the 
<nowiki>#</nowiki> advantage of knowing where shots are. 
<nowiki>#</nowiki>-sb 
 
<nowiki>#</nowiki> By default if a player kills a teammate, he dies too, this option turns this 
<nowiki>#</nowiki> off. Used mostly for capture the flag style games. 
<nowiki>#</nowiki>-tk 
 
<nowiki>#</nowiki> Kick a player if his ratio of teammate to non-teammate kills is this 
<nowiki>#</nowiki> percentage or greater. 
-tkkr 32 
 
<nowiki>#</nowiki> This option allows you to tell the server how long a team flag remains 
<nowiki>#</nowiki> before it is reset after the last player on a team leaves. The default 
<nowiki>#</nowiki> is 30 seconds. 
<nowiki>#</nowiki>-tftimeout 60 
 
<nowiki>#</nowiki> Hunt the rabbit game is activated with this option. 
<nowiki>#</nowiki> Use only one of these options. 
<nowiki>#</nowiki> Choose rabbit based on score. 
<nowiki>#</nowiki>-rabbit score 
<nowiki>#</nowiki> Rabbit is chosen by whoever kills the rabbit. 
<nowiki>#</nowiki>-rabbit killer 
<nowiki>#</nowiki> Or you can choose the rabbit randomly. 
<nowiki>#</nowiki>-rabbit random 
 
<nowiki>#</nowiki> It is possible to restrict bots and autopilot from being used on the server. 
<nowiki>#</nowiki> This is accomplished with the following. 
<nowiki>#</nowiki>-disableBots 
 
<nowiki>#</nowiki> This option causes the server to quit after serving one game. This is 
<nowiki>#</nowiki> handy if you want to do a timed game, or script a rotating server. 
<nowiki>#</nowiki>-g 
 
<nowiki>#</nowiki> This option sets the max score for players. The game ends when a person 
<nowiki>#</nowiki> reaches this score and is declared the winner. 
<nowiki>#</nowiki>-mps 100 
 
<nowiki>#</nowiki> This sets the max team score. The first team to reach this score is 
<nowiki>#</nowiki> declared the winner and the game is ended. 
<nowiki>#</nowiki>-mts 250 
 
<nowiki>#</nowiki> This dumps the score to console when it changes. 
<nowiki>#</nowiki>-printscore 
 
<nowiki>#</nowiki> This sets time limit (in seconds) for the game. Time starts when first 
<nowiki>#</nowiki> client connects. 
<nowiki>#</nowiki>-time 3600 
 
<nowiki>#</nowiki> This option requires a timed game to be started using the /countdown 
<nowiki>#</nowiki> command to start a timed game. Default is when first player joins. 
<nowiki>#</nowiki>-timemanual 
 
 
<nowiki>#</nowiki><nowiki>#</nowiki> List server Connection <nowiki>#</nowiki><nowiki>#</nowiki> 
 
<nowiki>#</nowiki> This is the public message that the server advertises on the public 
<nowiki>#</nowiki> server list. This is required if you want to be shown on the list. 
<nowiki>#</nowiki> It often advertises the map you are using. Keep it short. 
-public "Noo BZFlag Server With Random Map" 
 
<nowiki>#</nowiki> This is also needed to be listed on the public server list. The 
<nowiki>#</nowiki> address needs to be valid in DNS. It's your IP, plus port number. 
-publicaddr 123.456.789.000:5154 
 
<nowiki>#</nowiki> The server will listen on this port. Default port is 5154. 
-p 5154 
 
<nowiki>#</nowiki> Tells server not to respond to "pings". This makes the server private. 
<nowiki>#</nowiki> You should remove -public and -publicaddr when using it. 
<nowiki>#</nowiki> If your router is open, you can still give people your IP and port, and 
<nowiki>#</nowiki> they will be able to connect, you just wont be on the list. 
<nowiki>#</nowiki>-q 
 
<nowiki>#</nowiki> You probably don't need to use this, but it is there if you do. This 
<nowiki>#</nowiki> specifies where the server advertises itself. The built-in default 
<nowiki>#</nowiki> should work just fine. You need to hunt down the proper address if 
<nowiki>#</nowiki> it doesn't work. DON'T Change It 
<nowiki>#</nowiki>-publiclist <list-server-url> 
 
<nowiki>#</nowiki> Server will listen for and respond to "pings" (sent via broadcast) on 
<nowiki>#</nowiki> the given interface. The server uses the first interface by default. 
<nowiki>#</nowiki> This is the TCP/UDP/IP address the server will listen on. 
<nowiki>#</nowiki> You don't need to use this unless your server has multiple 
<nowiki>#</nowiki> interfaces and doesn't show up on the server lists. 
<nowiki>#</nowiki>-i 123.456.789.000 
 
 
<nowiki>#</nowiki><nowiki>#</nowiki> Player Connections <nowiki>#</nowiki><nowiki>#</nowiki> 
 
<nowiki>#</nowiki> Automatically assigns players to teams when they join so that teams are 
<nowiki>#</nowiki> evenly matched in number of players. Players are placed on teams with 
<nowiki>#</nowiki> lowest number of players first, then those with the lowest scores or 
<nowiki>#</nowiki> kill ratios. 
-autoTeam 
 
<nowiki>#</nowiki> This sets the max number of players. It can be done in 2 ways. A flat 
<nowiki>#</nowiki> count of players, or by number of players on a given team. 
<nowiki>#</nowiki> This allows up to 50 players, no team limits. 
<nowiki>#</nowiki> Typical home DSL connections max out at 12 players before lag begins. 
<nowiki>#</nowiki> Lag equals players times shots. So a one-shot server could have more 
<nowiki>#</nowiki> players, and vice-versa. 
-mp 12 
 
<nowiki>#</nowiki> This allows for max player by team. 
<nowiki>#</nowiki> The order is rogue, red, green, blue, purple, observer. 
<nowiki>#</nowiki>-mp 3,3,3,3,3,3 
 
<nowiki>#</nowiki> This requires clients to use UDP (a good thing). This will generally 
<nowiki>#</nowiki> make the server behave better, and make play more smooth. 
<nowiki>#</nowiki> It will kick players who are unable to establish a UDP connection 
<nowiki>#</nowiki> when they attempt to fire. 
-requireudp 
 
<nowiki>#</nowiki> Set to not use a UDP connection for players. You typically do NOT want to 
<nowiki>#</nowiki> do this (UDP is good!) 
<nowiki>#</nowiki>-noudp 
 
<nowiki>#</nowiki> This option warns the user their lag is too high when it crosses the 
<nowiki>#</nowiki> number of milliseconds set. 
-lagwarn 350 
 
<nowiki>#</nowiki> This option kicks players after they have been warned about high lag for 
<nowiki>#</nowiki> a certain number of times. 
-lagdrop 3 
 
<nowiki>#</nowiki> This option kicks the user after they have been idle for a number of 
<nowiki>#</nowiki> seconds. Idle means paused, not-spawning or not-responding. 
-maxidle 300 
 
<nowiki>#</nowiki> This option sets up your ban list. This is ip masks separated by commas. 
<nowiki>#</nowiki> The * character is used as a wild card in range bans. 
<nowiki>#</nowiki>-ban "192.168.1.5,10.10.2.*,10.2.*.*" 
 
<nowiki>#</nowiki> This option tells the server where to store the ban list. The ban list will 
<nowiki>#</nowiki> be loaded from this file when the server starts (if the file exists) and 
<nowiki>#</nowiki> written back to the file when someone gets banned or unbanned. If this 
<nowiki>#</nowiki> option isn't used the ban list will not be saved. 
<nowiki>#</nowiki>-banfile /path/to/mybanfile.txt 
 
<nowiki>#</nowiki> Registered player files which will be loaded on startup. 
<nowiki>#</nowiki> Use all three if you are not connecting to the list server. 
<nowiki>#</nowiki> Players can use /register passwd and /identify passwd 
<nowiki>#</nowiki> to confirm their identities. 
<nowiki>#</nowiki> passdb stores local user password mappings. 
<nowiki>#</nowiki>-passdb /path/to/passes.txt 
<nowiki>#</nowiki> userdb stores user to group mappings. 
<nowiki>#</nowiki>-userdb /path/to/users.txt 
 
<nowiki>#</nowiki> If you use the BZFlag forums at http://my.bzflag.org/bb 
<nowiki>#</nowiki> and have established groups there, you only need groupdb 
<nowiki>#</nowiki> Though local registrations can also be used. 
<nowiki>#</nowiki> groupdb stores group to permission mappings. 
<nowiki>#</nowiki>-groupdb /path/to/groups.txt 
 
<nowiki>#</nowiki> If you have registered groups at the bzbb forums, only players 
<nowiki>#</nowiki> in this group will see your server in the list. 
<nowiki>#</nowiki>-advertise NOOB.COP 
 
 
<nowiki>#</nowiki><nowiki>#</nowiki> General Options <nowiki>#</nowiki><nowiki>#</nowiki> 
 
<nowiki>#</nowiki> This is the server welcome message. Please change it. 
-srvmsg " This is a Noo BZFlag Server " 
-srvmsg " Have Fun and Play Nice " 
 
<nowiki>#</nowiki> Define a message which will be broadcast to all players every 15 minutes. 
-admsg " Noo BZFlag Server " 
-admsg " BZFlag is Fun " 
 
<nowiki>#</nowiki> This sets the amount of time in seconds that is required to pass between 
<nowiki>#</nowiki> two identical messages sent. 
-spamtime 15 
 
<nowiki>#</nowiki> This sets the amount of times to warn spammers (see -spamtime) before they 
<nowiki>#</nowiki> are kicked. 
-spamwarn 3 
 
<nowiki>#</nowiki> Specify a file that contains bad words that will be used when 
<nowiki>#</nowiki> either -filterCallsigns or -filterChat is enabled. 
<nowiki>#</nowiki> A multilingual badwords file can be found in source downloads. 
<nowiki>#</nowiki>-badwords /path/to/badwords.txt 
 
<nowiki>#</nowiki> Turn on the filtering of chat messages. Messages have words provided 
<nowiki>#</nowiki> via a -badwords file are replaced with !@<nowiki>#</nowiki>$%^&* characters. 
<nowiki>#</nowiki>-filterChat 
 
<nowiki>#</nowiki> Turn on the filtering of callsigns. Callsigns are compared against 
<nowiki>#</nowiki> bad words provided via -badwords. 
<nowiki>#</nowiki>-filterCallsigns 
 
<nowiki>#</nowiki> By default, all filtering is aggressive, matching much more than what 
<nowiki>#</nowiki> is strictly listed in a -badwords file for convenience. Providing this 
<nowiki>#</nowiki> option will make the -filterCallsigns and -filterChat comparisons 
<nowiki>#</nowiki> exact match only. 
<nowiki>#</nowiki>-filterSimple 
 
<nowiki>#</nowiki> This forces all clients to use the same time of day. The time is 
<nowiki>#</nowiki> determined by the server's clock. This disables the + and - keys 
<nowiki>#</nowiki> on the clients. 
<nowiki>#</nowiki>-synctime 
 
 
 
<nowiki>#</nowiki><nowiki>#</nowiki> Player Controlled Functions <nowiki>#</nowiki><nowiki>#</nowiki> 
 
<nowiki>#</nowiki> This option specifies a help file that will be displayed when the player 
<nowiki>#</nowiki> types /help name 
<nowiki>#</nowiki> Maximum length is 50 lines and 120 characters per line 
<nowiki>#</nowiki>-helpfile shock /path/to/shockwavehelp.txt 
<nowiki>#</nowiki>-helpfile noob /path/to/noobhelp.txt 
 
<nowiki>#</nowiki> You can specify a file so that people can type /report to report problems 
<nowiki>#</nowiki> on the server. The reports are logged in this file. 
<nowiki>#</nowiki>-reportfile /path/to/reports.txt 
 
<nowiki>#</nowiki> You can also use this option to cause the /report to trigger a command 
<nowiki>#</nowiki> as well as, or instead of, logging to a file. 
<nowiki>#</nowiki>-reportpipe command 
 
<nowiki>#</nowiki> This specifies the number of seconds in which a poll can be vetoed. 
<nowiki>#</nowiki>-vetoTime 60 
 
<nowiki>#</nowiki> This specifies the percentage of people required for a successful vote. 
<nowiki>#</nowiki>-votePercentage 51 
 
<nowiki>#</nowiki> This is the number of voters required to hold a poll. 
<nowiki>#</nowiki>-votesRequired 6 
 
<nowiki>#</nowiki> This is the length of time that players have to vote. 
<nowiki>#</nowiki>-voteTime 60 
 
 
<nowiki>#</nowiki><nowiki>#</nowiki> Flags <nowiki>#</nowiki><nowiki>#</nowiki> 
 
<nowiki>#</nowiki> This option allows for antidote flags to be available for players who 
<nowiki>#</nowiki> get bad flags. 
-sa 
 
<nowiki>#</nowiki> Bad flags are automatically dropped after this many seconds. 
-st 5 
 
<nowiki>#</nowiki> Bad flags are automatically dropped after this many wins. 
-sw 1 
 
<nowiki>#</nowiki> This allows you to limit the number of shots from a particular flag. 
<nowiki>#</nowiki>-sl GM 20 
<nowiki>#</nowiki>-sl L 20 
 
<nowiki>#</nowiki> There are two sets of flags. Flags that must be in the world at all times 
<nowiki>#</nowiki> and flags that may get generated randomly. in addition. +f specifies flags that 
<nowiki>#</nowiki> must be there and -f specifies flags the should never be generated. 
 
<nowiki>#</nowiki> The server will randomly place flags from the following list. 
<nowiki>#</nowiki> To be sure there is at least a certain amount of a flag on the map 
<nowiki>#</nowiki> at any given time, you can use the +f option to guarantee a certain 
<nowiki>#</nowiki> number of a flag. 
 
<nowiki>#</nowiki> Good Flags 
+f A{2} <nowiki>#</nowiki> Agility 
+f CL{2} <nowiki>#</nowiki> Cloaking 
+f F{2} <nowiki>#</nowiki> rapid Fire 
+f G{1} <nowiki>#</nowiki> Genocide 
+f GM{2} <nowiki>#</nowiki> Guided Missile 
+f IB{2} <nowiki>#</nowiki> Invisible Bullett 
+f L{2} <nowiki>#</nowiki> Laser 
+f MG{2} <nowiki>#</nowiki> Machine Gun 
+f N{2} <nowiki>#</nowiki> Narrow 
+f OO{2} <nowiki>#</nowiki> Oscillation Overthruster 
+f PZ{2} <nowiki>#</nowiki> Phantom Zone 
+f QT{2} <nowiki>#</nowiki> QuickTurn 
+f SB{2} <nowiki>#</nowiki> Super Bullet 
+f SE{2} <nowiki>#</nowiki> SEer 
+f SH{2} <nowiki>#</nowiki> SHield 
+f SR{2} <nowiki>#</nowiki> SteamRoller 
+f ST{2} <nowiki>#</nowiki> Stealth 
+f SW{2} <nowiki>#</nowiki> ShockWave 
+f T{2} <nowiki>#</nowiki> Tiny 
+f TH{2} <nowiki>#</nowiki> THeif 
+f US{2} <nowiki>#</nowiki> USeless 
+f V{2} <nowiki>#</nowiki> Velocity (high speed) 
+f WG{2} <nowiki>#</nowiki> WinGs 
 
<nowiki>#</nowiki> BAD FLAGS 
+f B{1} <nowiki>#</nowiki> Blindness 
+f BY{1} <nowiki>#</nowiki> Bouncy 
+f CB{1} <nowiki>#</nowiki> Color Blindess 
+f FO{1} <nowiki>#</nowiki> Forward Only 
+f JM{1} <nowiki>#</nowiki> Jamming 
+f LT{1} <nowiki>#</nowiki> Left Turn only 
+f M{1} <nowiki>#</nowiki> Momentum 
+f NJ{1} <nowiki>#</nowiki> No Jumping 
+f O{1} <nowiki>#</nowiki> Obesity 
+f RC{1} <nowiki>#</nowiki> Reverse Controls 
+f RO{1} <nowiki>#</nowiki> Reverse Only 
+f RT{1} <nowiki>#</nowiki> Right Turn only 
+f TR{1} <nowiki>#</nowiki> Trigger Happy 
+f WA{1} <nowiki>#</nowiki> Wide Angle 
 
<nowiki>#</nowiki> Using "+f good" is the equivalent of doing +f for each of the good flags. 
<nowiki>#</nowiki> If you want to restrict a certain flag, you can use the -f option. 
<nowiki>#</nowiki> just like with the +f option. "-f bad" is the same as doing -f for 
<nowiki>#</nowiki> all of the bad flags. 
<nowiki>#</nowiki>-f bad <nowiki>#</nowiki>no bad flags 
<nowiki>#</nowiki>+f good <nowiki>#</nowiki>one of each good flag 
<nowiki>#</nowiki>-f G <nowiki>#</nowiki>no genocide 
 
<nowiki>#</nowiki> Use +s to have the server generate a certain number of extra flags 
<nowiki>#</nowiki> and have them available at all times. This is in addition to 
<nowiki>#</nowiki> any other flags specified. 
<nowiki>#</nowiki>+s 20 
 
<nowiki>#</nowiki> The server will have up to this many super flags at any time. 
<nowiki>#</nowiki> Use this if you don't use any other method of flag generation. 
<nowiki>#</nowiki>-s 30 
 
 
<nowiki>#</nowiki><nowiki>#</nowiki> Variables <nowiki>#</nowiki><nowiki>#</nowiki> 
 
<nowiki>#</nowiki> And there are three ways to load sets of server-specific variables. 
<nowiki>#</nowiki> They can be specified in this .conf file. 
<nowiki>#</nowiki> They can be specified in the .bzw map file in an options block. 
<nowiki>#</nowiki> Or they can be specified in a third file with this option 
<nowiki>#</nowiki>-vars /path/to/vars.txt 
 
<nowiki>#</nowiki> Server variables can also be modified in-game using 
<nowiki>#</nowiki> /set _varName value 
<nowiki>#</nowiki> View the entire variable list by using 
<nowiki>#</nowiki> /set (with nothing afterward) lists all vars 
<nowiki>#</nowiki> /diff will list most non-default settings 
<nowiki>#</nowiki> /? will list other available commands 
 
<nowiki>#</nowiki> Here are a few examples of variables. 
<nowiki>#</nowiki> Some variables are set to 0 for off, 1 for on. 
<nowiki>#</nowiki>-set _obeseFactor 12 
<nowiki>#</nowiki>-set _skyColor grey44 
<nowiki>#</nowiki>-set _wingsJumpCount 3 
<nowiki>#</nowiki>-set _tankExplosionSize 60 
<nowiki>#</nowiki>-set _jumpVelocity 20 
<nowiki>#</nowiki>-set _squishTime 7 
<nowiki>#</nowiki>-set _mirror grey22 
<nowiki>#</nowiki>-set _wallHeight 2 
<nowiki>#</nowiki>-set _shotsKeepVerticalVelocity 1 
<nowiki>#</nowiki>-set _drawGround 1 
<nowiki>#</nowiki>-set _drawSky 1 
<nowiki>#</nowiki>-set _drawClouds 0 
<nowiki>#</nowiki>-set _drawMountains 0 
<nowiki>#</nowiki>-set _fogMode exp 
<nowiki>#</nowiki>-set _fogColor black 
<nowiki>#</nowiki>-set _fogDensity .01 
-set _rainType bubble 
 
 
<nowiki>#</nowiki><nowiki>#</nowiki> Plugins <nowiki>#</nowiki><nowiki>#</nowiki> 
 
<nowiki>#</nowiki> Plugins have mostly superseded patches as a means of modifying 
<nowiki>#</nowiki> the play of BZFlag servers. Recent improvements in the bzfs2.0.9 have enabled 
<nowiki>#</nowiki> almost every server functionality to be modified with the plugin API. 
<nowiki>#</nowiki> 
<nowiki>#</nowiki> Plugins cannot be accessed unless you compile your plugins and 
<nowiki>#</nowiki> bzfs binary with the option --enable-shared 
<nowiki>#</nowiki>-loadplugin /path/to/playHistoryTracker 
 
<nowiki>#</nowiki><nowiki>#</nowiki> Replay <nowiki>#</nowiki><nowiki>#</nowiki> 
 
<nowiki>#</nowiki> You can set up a server for replay mode by entering this option 
<nowiki>#</nowiki>-replay 
 
<nowiki>#</nowiki> This option sets the recording buffer to the specified amount of megabytes. 
<nowiki>#</nowiki>-recbuf 2 
 
<nowiki>#</nowiki> This option sets the directory to look for and save recordings. 
<nowiki>#</nowiki>-recdir 
 
 
<nowiki>#</nowiki><nowiki>#</nowiki> More Comments <nowiki>#</nowiki><nowiki>#</nowiki> 
 
<nowiki>#</nowiki> This is intended to include the minimum options for a working 
<nowiki>#</nowiki> BZFlag server, that is also connected to the list server. 
<nowiki>#</nowiki> All you need to do is edit your IP numbers in -publicaddr 
<nowiki>#</nowiki> and start bzfs. 
<nowiki>#</nowiki> As it connects to the list server, your terminal will show 
<nowiki>#</nowiki> something that looks like a player has joined, then immediately left. 
<nowiki>#</nowiki> When you see that happen, you have succeeded, and are listed. 
<nowiki>#</nowiki> If you can not connect to the list server, you probably need to open 
<nowiki>#</nowiki> port 5154 through your router, for both UDP and TCP. Instructions for that 
<nowiki>#</nowiki> are not included here. 
 
<nowiki>#</nowiki> You join your server locally, by opening your BZFlag game client 
<nowiki>#</nowiki> and editing these lines in the JOIN GAME screen. 
<nowiki>#</nowiki> In the SERVER line add localhost 
<nowiki>#</nowiki> In the PORT line add 5154 
<nowiki>#</nowiki> Then JOIN your server. 
 
<nowiki>#</nowiki> Here are the short instructions. 
<nowiki>#</nowiki> Open your router firewall at port 5154 
<nowiki>#</nowiki> Change the -publicaddr line in this .file to match your IP. 
<nowiki>#</nowiki> In your terminal, cd to the location of the bzfs binary. 
<nowiki>#</nowiki> ./bzfs -conf /path/to/sample.conf 
<nowiki>#</nowiki> Don't take out any <nowiki>#</nowiki> comment markers or add options that you think look cool 
<nowiki>#</nowiki> until after you have the server working. 
<nowiki>#</nowiki> The options you need have been included in this file. 
<nowiki>#</nowiki> You don't even need to specify a map, bzfs will create a random map for you. 
<nowiki>#</nowiki> 
<nowiki>#</nowiki> You do not even need this .conf file to start a server. 
<nowiki>#</nowiki> You can use as many options you'd like just typing them into the terminal. 
<nowiki>#</nowiki> Assuming you have installed BZFlag in default locations. 
<nowiki>#</nowiki> In Macintosh terminal application these two should work 
<nowiki>#</nowiki> cd /Applications/BZFlag2.0.8/Contents/MacOS/ 
<nowiki>#</nowiki> ./bzfs -dd 
<nowiki>#</nowiki> 
<nowiki>#</nowiki> In windows command prompt, these two commands should suffice 
<nowiki>#</nowiki> cd C:\program files\bzflag2.0.2 
<nowiki>#</nowiki> bzfs.exe -dd 
<nowiki>#</nowiki> All other path examples given in this file use *nix format 
<nowiki>#</nowiki> Windows users will have to change all the path examples given in this file. 

[[Category:Server]]

Key Mapping

2007-02-21T23:29:26Z

Brad: fix category

Below is a list of the default key mappings within the [[BZFlag]] client. These can be changed in Options -> Input Settings -> Key Mapping.

{|{{Prettytable}}
|-
|Key(s) || Description
|-
|- - || time backward
|-
| 1 || set displayRadarRange 0.25
|-
| 2 || set displayRadarRange 0.5
|-
| 3 || set displayRadarRange 1.0
|-
| 4 || radarZoom in
|-
| 5 || radarZoom out
|-
| 7 || addhunt
|-
| 9 || autopilot
|-
| = || time forward
|-
| A || toggle slowKeyboard
|-
| B || viewZoom toggle
|-
| F || toggle displayFlagHelp
|-
| H || toggleFlags radar
|-
| I || restart
|-
| J || toggleFlags main
|-
| K || silence
|-
| O || servercommand
|-
| P || pause
|-
| Q || toggleRadar
|-
| S || toggle displayScore
|-
| T || toggle frames-per-second display
|-
| U || hunt
|-
| W || toggleConsole
|-
| Y || toggle milliseconds for frame-drawing [added by hand]
|-
| F1 || fullscreen
|-
| F4 || iconify
|-
| F5 || screenshot
|-
| End || scrollpanel bottom
|-
| F12 || quit
|-
| Tab || jump
|-
| Enter || fire
|-
| Pause || pause
|-
| Space || drop flag
|-
| Delete || self-destruct
|-
| Ctrl+Wheel Down || viewZoom out
|-
| Ctrl+Wheel Up || viewZoom in
|-
| Home (Pos1) || get shots statistic for players [added by hand]
|-
| Mouse Left || fire
|-
| Mouse Middle || drop
|-
| Mouse Right || restart
|-
| Page Down || scrollpanel down_page
|-
|Page Up || scrollpanel up_page
|-
| Shift+F1 || messagepanel all
|-
| Shift+F2 || messagepanel chat
|-
| Shift+F3 || messagepanel server
|-
| Shift+F4 || messagepanel misc
|-
| Shift+Wheel Down || radarZoom out
|-
| Shift+Wheel Up || radarZoom in
|-
| Wheel Down || scrollpanel down 3
|-
| Wheel Up || scrollpanel up 3
|-
| Arrow Down || Drive backwards
|-
| Arrow Up || Drive forwards
|-
| Arrow Left || Turn left
|-
| Arrow Right || Turn right
|-
| , || Send PM to nemesis
|-
| . || Send PM to recipient
|-
| M || Send a message to your team
|-
| N || Send a message to all players
|-
| Z || Send a message to admins.
|-
| ALT+(F1-F10) || Custom quick keys to all.
|-
| CTRL+(F1-F10) || Custom quick keys to team.
|-
| L || Toggle display labels in observer
|-
| F6 || roam cycle subject backward
|-
| F7 || roam cycle subject forwards
|-
| F8 || change observer mode
|-
| F9 || zoom in
|-
| F10 || zoom out
|-
| F11 || normal zoom
|-
| ALT+Arrow Keys || move up and down while roaming
|-
| CTRL+Arrow Keys || rotate left, right, up and down while roaming
|-
| SHIFT+Arrow Keys || Send a message to all players
|-
| F8 || Send a message to all players
|-

|}

[[Category:Client]]

Dead Reckoning

2007-02-21T23:25:14Z

Brad: add category

This page should give information and suggestion on what Dead Reckoning (DR) is, how it is implemented, what it should be.

DR is a method to find the current position by measuring the course and distance from a past know point.

It is used in Distributed Interactive Simulation to save the bandwidth in the communication between two different network entities, when exchanging positional information of the object. It starts from a kinematic model of the object.

Let explain that with simple cases around the entity that own the object (A), and the entity that should receive the positional update (B). Name this object tank.

A is updating is tank position continuosly, taking into account the environment, the player wished, and the physics (virtual) laws that the game impose. Continuosly just means any frame. A is the master (driver) of the tank.
B is following with A, using A provided info to update is local copy of the tank. B is a slave.

Let assume at first a 0 delay network.

First approach could be for A to communicate the tank position to B any time (frame) it is updating its internal tank representation. B uses these message to change its internal copy of the tank and uses the last arrived data, whenever tank info should be used. This is a bandwidth wasting!

To save bandwidth, A and B could share a DR model of the tank.

After having A updated is tank position, without taking into account the DR model, and just before sending, A compare the current tank position with a predicted tank position, taking now into account the DR model. If the two object representation are not so different, below a threshold, it just avoids sending data. B, when no data is arriving, uses the DR model to know the position of the tank. That is not a futured position. It is just the current position with an error maximized by the threshold. Tank position is however updated periodically, to allow for new player entering in the game. For this to work, we should add DR model parameters to the updated data.

This way we do not send tank update when the position can be accurately derived by the old data, saving bandwidth.

Let assume now a fixed delay network.

With the same behaviour described above, A send its data to B. B update is tank representation with just the same rules above. Forgetting the network delay, B has the "correct" representation of the object, and its history, but just delayed by the network. Here Dead reckoning is not going to "predict" any position, B behaves the same as if DR is not used, (i.e. A send tank updates any frames). Data futuring is not in the game.

What happens with a jittered network?

With jitter, the fastest packets arrive with a delay that is near the minimum path route, while some other packets arrives later, due to some network bottleneck.
Now the tank updates from A to B does not arrive just delayed, but sometimes there is an event time compression, sometimes a time expansion, without A knowing anything about it. If B takes into account this message without any time correction the two prediction algorithm, A & B, behave not the same. And DR is going to alter the perception of A tank in B, not just delaying his history, but changing its trajectory.

One of the most effect of this behaviour is when A cannot control its tank so the DR algorithm works saving much. Jumping!
Probably, during jumping A send just few updates, let us assume that it will send 4 updates: beginning, half of the raise, top, half of descent, landing. So take an example.

Tank start to jump, so it send an update. The next update suffers from network congestion, so it is seen delayed at B side. In the mean time, B continue to predict the tank position. When tank is seen at B at half descent, the delayed message was received, so B put back is local view of the tank at the half raise point, where the local view of tank continue is raising. After a while a new update is received putting the tank again forward to his top and half descent position.

I see lot of time this while playing.

To correct this, we should compute the network jitter, and use this to correctly position the tank in time & space as view by the DR algorithm, so it can continue to work happily. The "fixed" (unknown) network delay still apply, so our local tank representation is still delayed and, apart the network congestion event, where we blindly predict the future, truely reflect the remote one.

[[Category:Development]]

Rotation Server

2007-02-21T23:21:13Z

Brad: add category

The scripts below can be used to have a server that rotates through specified maps every time it is restarted. Only use the scripts for your OS or they will not work. More information about map rotation scripts can be found [http://my.bzflag.org/bb/viewtopic.php?t=4252 here] on the BZBB.

== Windows ==
Copy and the script below into notepad and save it as '''start-server.bat'''.

All paths should be in 8.3 notation e.g. progra~1 not program files

Don't forget to add -g and -time <secs> to your config files.

Press CTRL-C twice and "y" to answer "Terminate Batch Job (y/n)?" to exit.

You will probably need to edit the paths to the bzfs binary and your configuration files.

You should have all your config files in the same directory as you specified in the script.

To run the server, you just need to double-click on '''start-server.bat'''.

@ECHO OFF

BREAK ON

SET BZFSPATH=c:\progra~1\bzflag~1.2\bzfs.exe

IF "%1" == "" SET CONFDIR=c:\your\path\to\conf\files

IF NOT "%1" == "" SET CONFDIR=%1

:loop_top

ECHO.

FOR %%b IN (%CONFDIR%\*.conf) DO %BZFSPATH% -conf %%b

ECHO "Reached end of rotation, starting over.

GOTO loop_top

== POSIX Shell (Mac OS X, Linux, BSD, IRIX, etc) ==

Save the script below as '''rotate.sh'''

Put all your config files in the CONFIGPATH directory.

After editing the CONFIGPATH and path to bzfs, type '''chmod a+x rotate.sh''' and then '''./rotate.sh''' to run the script.

<pre>
#!/bin/sh

if [ $1 ] ; then
CONFIGPATH=$1
else
CONFIGPATH="/your/path/to/configfiles"
fi
cd $CONFIGPATH || echo "$CONFIGPATH not found"

BZFSPATH=/usr/local/bin/bzfs

abort=0
while [ $abort -eq 0 ]; do
for b in *.conf ; do
$BZFSPATH -conf $b
if [ $? -ne 0 ] ; then
abort=1
break
fi
done
echo "Reached end of rotation, starting over."
done
</pre>

[[Category:Server]]

Group Permissions

2007-02-21T23:18:59Z

Brad: add category

Below is a list of all the available group permissions. They are used by the server to determine what players can and can not do.

{|{{Prettytable}}
|-
|Permission || Commands
|-
| ACTIONMESSAGE || /me
|-
| ADMINMESSAGERECEIVE || Able to recieve messages on admin channel
|-
| ADMINMESSAGESEND || Able to send messages to admin channel
|-
| ANTIBAN || protected from being banned
|-
| ANTIDEREGISTER || Protected from being deregistered locally
|-
| ANTIKICK || Protected from being kicked
|-
| ANTIPOLL || Protected from being polled against
|-
| ANTIPOLLBAN || Protected from being poll banned
|-
| ANTIPOLLKICK || Protected from being poll kicked
|-
| BAN || /ban /hostban
|-
| BANLIST || /banlist /hostbanlist
|-
| COUNTDOWN || /countdown
|-
| DATE || /date
|-
| ENDGAME || /gameover
|-
| FLAGHISTORY || /flaghistory
|-
| FLAGMOD || /flag
|-
| HIDEADMIN || Does not show the @ symbol by admins
|-
| IDLESTATS || /idlestats
|-
| INFO || Not implemented
|-
| KICK || /kick
|-
| LAGSTATS || /lagstats
|-
| LAGWARN || /lagwarn
|-
| LISTPERMS || Not implemented
|-
| MASTERBAN || /masterban
|-
| PLAYERLIST || /playerlist
|-
| POLL || /poll
|-
| POLLBAN || /poll ban
|-
| POLLKICK || /poll kick
|-
| POLLSET || /poll set
|-
| POLLFLAGRESET || /poll flagreset
|-
| PRIVATEMESSAGE || /privateMessage
|-
| RECORD || /record
|-
| REJOIN || Protects player from the rejoin delay after disconnecting
|-
| REMOVEPERMS || /removegroup
|-
| REPLAY || /replay
|-
| REQUIREIDENTIFY || Requires that the player is identified before playing
|-
| SAY || /say
|-
| SETALL || /reload /deregister /reset /set
|-
| SETPASSWORD || /setpassword
|-
| SETPERMS || /setgroup
|-
| SETVAR || /set /reset
|-
| SHOWOTHERS || /showgroup
|-
| SHORTBAN || /shortBan
|-
| SHUTDOWNSERVER || /shutdownserver
|-
| SPAWN || Allows player to spawn
|-
| SUPERKILL || /superkill
|-
| UNBAN || /unban /hostunban
|-
| VETO || /veto
|-
| VIEWREPORTS || /viewreports
|-
| VOTE || /vote
|-
|}

[[Category:Server]]

Config File

2007-02-21T23:17:46Z

Brad: add category, formatting, remove {{{'s and }}}'s

BZFlag uses a [[Config File]] to store user settings.

= Windows =

My Documents\My BZFlag Files\2.0\config.cfg

= Mac OS X =

~/Library/Application Support/BZFlag/2.0/config.cfg

= Linux and unix platforms =

~/.bzf/2.0/config.cfg

[[Category:Client]]

Alias Your IP Address

2007-02-21T23:14:59Z

Brad: add category

Your IP address can sometimes be hard to memorize, especially if you have a dynamic IP address (one that changes every so often). This page explains how you can associate a memorable name such as bzflag.game-host.org to your IP address. Even if your IP is static, it is much easier to remember bzserver.domain.org than something like 169.19.123.234

One way to alias your IP is to get a free account at [http://www.dyndns.org/ www.dyndns.org]. Once you register and login, you will be able to attach a domain name to your IP address. There are dozens of top-level domains to choose from. Once you log in to dyndns.org, choose static or dynamic DNS depending on whether your provider assigns you a static or dynamic ip, click on "add a new host", and choose the name of your preference.

If your IP is dynamic, you'll also need to download and run a client program that will periodically tell dyndns.org what the IP of your machine is. The dyndns.org site has a page with a list of clients. It is fairly easy to set them up (basically, you only need to install them. Most of them will let you specify if you want the client to startup every time you start your computer, and also how often the client should check whether your IP has changed (say, for example, every 10 minutes).

NOTE: dyndns.org will *NOT* let you choose any top-level domain (the xxx.org part of the domain name). It will give you a list of a few dozen domains (such as game-host.org) to which you can add your own preferred name (resulting in myname.game-host.org). If you want to register and use your own domain name (something like my.domain.org), you'll have to pay them some money. Depending on the registration service you use, prices range between $8 and $20 a year. If you don't want to pay, you have less of a choice, but at least you can get a name.

[[Category:Server]]

Auto Team

2007-02-21T23:13:54Z

Brad: add category

AutoTeam is a way of assigning color/team that is already in the 1.10 release. It is selectable by the server or by the client. When selected, the team assigned to tank is decided by some automatic criteria.

Bots always join requesting AutoTeam.

The team selection is done in this way:
* If Rogues are allowed and player asks to be a rogue, assign to Rogue if there is space for it. They don't want to be in a team at first.
* If you have only one colored team (not Rogue) with players, assign the incoming player to the others.
* When you have at least 2 teams (not Rogue), before assigning other teams, put the player on the lowest numbered team with at least a tank on it.
* When you have at least 2 teams with 1 player, don't bother creating another team, add a player to one of these teams.
* When the above rules give more than one choice, follow the user requested team, and if not available, assign the tank to the weakest (in term of team point) team

I explain with example what I mean :
* We have 4 teams with this distribution 5R-2G-1B-0P on an AutoTeam server.
If a player joins he will be assigned to Blue to have 5R-2G-2B-0P. Should both the 2 Blue exit and rejoin, he will go to Green having 5R-4G-0B-0P
in case of a distribution 5R-5G-0B-0P, when Blue/Purple tanks has left, while Red/Green stay, I want to start the other team earlier, so we can have 5R-5G-0B-1P and the next 5R-5G-0B-2P

* With 20 players joining, with no leaving, team will be 5-5-5-5
if, after some leaving, we have 10-0-0-0, the next 10 players joining will give 10-10-0-0

* With 4 players joining, with no leaving, teams will go 2-2-0-0, that I think is better then 1-1-1-1

Tupone

TimRiker comments:

* If the player asks for a color, they should get that color unless there are no more slots of that color available. If there are no more slots then treating them as type "automatic" is fine.
* I don't under stand what you mean by "try to balance the bigger"
* There is no "user preference" just a "user requested team" which might be "automatic".

learner/brlcad comments:

I updated the "current 1.10 behavior" description to reflect what I effectively made it do in 1.9. Basically, the player gets what they request if it's available, otherwise the assignment is automatic to the first available and most empty team. If there are no slots available, they are joined as observer (or rejected).

Let me reiterate, the player should get what they asked for period. The only questions that come into play are when they ask for automatic team placement.

The suggested changes listed above by Tupone effectively makes only one modification to the existing behavior. Instead of simply joining a player to the least filled team, a bias is imposed to prefer filling teams up first. That is to say that if we have a map like HiX where there are four teams with, say, 10 players allowed per team -- there will be 10 vs 10 vs 0 vs 0. New players will cause the third team to be imbalanced until sufficient additional joins/leavings are achieved.

I considered that case when I first implemented the automatic joining server-side and rejected it for a couple reasons:

1. That imbalance caused can be detrimental. The team is effectively weak and potentially unplayable (from a CTF perspective) until rejoins or new joins are able to balance the teams out. This time is completely unknown giving rise to a horrible potential situation.

2. It's simply not true to say that two or three 'large' teams are better than four or five relativley 'empty' teams. That is completely personal preference. To impose a bias for larger teams even potentially goes against the server/map design. I made a map for 4 teams -- empty or not, that is what was specified and may be what I (as an operator) want to encourage. There may be justification to allow a server-side configuration to allow this autoteam-bias, but I seriously think it's a bad idea to make it the default behavior.

[[Category:Server]]

AHOD

2007-02-21T23:05:53Z

Brad:

[[Image:Ahod.jpg|thumb|right|All Hands On Deck]]
[[AHOD]] (All Hands On Deck) is a map and play-style originally created by [[trepan]]. It has since been updated by [[brad]] and now uses a plugin instead of a server mod. The aim is to get the enemy flag and a certain percentage of your team to the Deck to make a capture. The Deck is marked by an arrow and a flashing halo, as well as shockwaves on radar - you can't miss it.

You can be on either the Red or Green team, the blue team platform is the target Deck. Once someone is on the Deck with the enemy flag the plugin will announce how many more people on your team are required to make a capture. When the flags is captured both teams die and respawn at their bases.

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

Change Default Font

2007-02-21T21:51:50Z

Brad: fix external link

It is little known, except among [[BZFlag_And_IRC|#bzflag irc]] visitors, that there is a second font designed specially for console use included with [[BZFlag2.0.8|BZFlag 2.0]]. It's called ProFont and I adapted it to [[BZFlag]] after seeing an attempt by [[DTRemenak]] to do the same out of a TTF file (which didn't turn out too good); it has a 50% transparent black border for readability in the sky and other bright places. It might be a bit small for high-resolution screens at its default size (8pt), but it's far more readable than Vera Mono in my opinion. The best way to describe it is to show you what it looks like.. if you want to see some screenshots before changing your BZFlag to it, check them out here:

http://turbogfx.homelinux.org/imgfiles/bzflag-ss/profont-bz/

The first is of the normal (8pt) font, and the second one is of the "micro" (6pt) font.

So if you decide you'd like to try it out for yourself...
To change your console font to ProFont, locate your config file:

For Windows: <code>C:\Documents and Settings\<User>\<User's Documents>\My BZFlag Files\2.0\config.cfg</code>

For Mac OS X: <code>~/Library/Application\ Support/2.0/config.cfg</code>

For Linux and relatives: <code>~/.bzf/2.0/config.cfg</code>

Open the config in a text editor and add this line to it:

set consoleFont profont

Save the file, then start [[BZFlag]] and see the new font in action.

[This article was originally created by [[Legoguy]] - See [http://my.bzflag.org/bb/viewtopic.php?t=2677 here].]

[[Category:Client]]

Change Default Font

2007-02-21T21:50:24Z

Brad: formatting

Ideas

2007-02-21T19:23:13Z

Brad: fix category

= BZFlag Ideas =

== Any and all ideas for BZFlag! ==

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, please warn us ahead of time.

On this page, I'll post what people are doing, as well as what new features are planned and how they are coming.

NOTE: These are just possiblilities. We won't be implementing everything here.

NOTE: Flag ideas should be placed on [[Flag List]]. Any other ideas can be placed here.

This page has gone through a few changes; people have had troubles with editing this page, so a lot of content is missing. I will be merging this page with the backup from my webpage soon, and making a new backup. I will also be going through some E-mails I have received for ideas.

The BZFlag homepage is located at http://BZFlag.org, and the SourceForge group page is located at https://sourceforge.net/projects/bzflag/.

Status may include personal comments by developers.

Ideas include:
* Add support for 5 (or more) button mice Status: Great Idea
* Sort player list by team Status: Idea
* 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
* More flags (listed below) Status: See Table
* 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: Good Idea
* 2 or 3 teams as well as the current 4 Status: Idea
* 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.
* 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

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.

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.
Comments??
SortedIdeas

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'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]]

Change Default Font

2007-02-21T19:21:39Z

Brad: formatting

It is little known, except among [[BZFlag_And_IRC|#bzflag irc]] visitors, that there is a second font designed specially for console use included with [[BZFlag2.0.8|BZFlag 2.0]]. It's called ProFont and I adapted it to [[BZFlag]] after seeing an attempt by [[DTRemenak]] to do the same out of a TTF file (which didn't turn out too good); it has a 50% transparent black border for readability in the sky and other bright places. It might be a bit small for high-resolution screens at its default size (8pt), but it's far more readable than Vera Mono in my opinion. The best way to describe it is to show you what it looks like.. if you want to see some screenshots before changing your BZFlag to it, check them out here:

http://turbogfx.homelinux.org/imgfiles/bzflag-ss/profont-bz/

The first is of the normal (8pt) font, and the second one is of the "micro" (6pt) font.

So if you decide you'd like to try it out for yourself...
To change your console font to ProFont, locate your config file:
For Windows: <code>C:\Documents and Settings\<User>\<User's Documents>\My BZFlag Files\2.0\config.cfg</code>
For Mac OS X: <code>~/Library/Application\ Support/2.0/config.cfg</code>
For Linux and relatives: <code>~/.bzf/2.0/config.cfg</code>

Open the config in a text editor and add this line to it:

set consoleFont profont

Save the file, then start [[BZFlag]] and see the new font in action.

[This article was originally created by [[Legoguy]] - See [http://my.bzflag.org/bb/viewtopic.php?t=2677&highlight=profont here].]

[[Category:Client]]

Change Default Font

2007-02-21T19:20:46Z

Brad: remove erroneuous square brackets.

It is little known, except among [[BZFlag_And_IRC|#bzflag irc]] visitors, that there is a second font designed specially for console use included with [[BZFlag2.0.8|BZFlag 2.0]]. It's called ProFont and I adapted it to [[BZFlag]] after seeing an attempt by [[DTRemenak]] to do the same out of a TTF file (which didn't turn out too good); it has a 50% transparent black border for readability in the sky and other bright places. It might be a bit small for high-resolution screens at its default size (8pt), but it's far more readable than Vera Mono in my opinion. The best way to describe it is to show you what it looks like.. if you want to see some screenshots before changing your BZFlag to it, check them out here:

http://turbogfx.homelinux.org/imgfiles/bzflag-ss/profont-bz/

The first is of the normal (8pt) font, and the second one is of the "micro" (6pt) font.

So if you decide you'd like to try it out for yourself...
To change your console font to ProFont, locate your config file:
For Windows: <code>C:\Documents and Settings\<User>\<User's Documents>\My BZFlag Files\2.0\config.cfg</code>
For Mac OS X: <code>~/Library/Application\ Support/2.0/config.cfg</code>
For Linux and relatives: <code>~/.bzf/2.0/config.cfg</code>

Open the config in a text editor and add this line to it:

set consoleFont profont

Save the file, then start [[BZFlag]] and see the new font in action.

[This article was originally created by [[Legoguy]] - [http://my.bzflag.org/bb/viewtopic.php?t=2677&highlight=profont see here.]]

[[Category:Client]]

Change Default Font

2007-02-21T19:19:48Z

Brad: add page explaining how to change the default font in the bzflag client

It is little known, except among [[BZFlag_And_IRC|#bzflag irc]] visitors, that there is a second font designed specially for console use included with [[BZFlag2.0.8|BZFlag 2.0]]. It's called ProFont and I adapted it to [[BZFlag]] after seeing an attempt by [[DTRemenak]] to do the same out of a TTF file (which didn't turn out too good); it has a 50% transparent black border for readability in the sky and other bright places. It might be a bit small for high-resolution screens at its default size (8pt), but it's far more readable than Vera Mono in my opinion. The best way to describe it is to show you what it looks like.. if you want to see some screenshots before changing your BZFlag to it, check them out here:

http://turbogfx.homelinux.org/imgfiles/bzflag-ss/profont-bz/

The first is of the normal (8pt) font, and the second one is of the "micro" (6pt) font.

So if you decide you'd like to try it out for yourself...
To change your console font to ProFont, locate your config file:
For Windows: <code>C:\Documents and Settings\<User>\<User's Documents>\My BZFlag Files\2.0\config.cfg</code>
For Mac OS X: <code>~/Library/Application\ Support/2.0/config.cfg</code>
For Linux and relatives: <code>~/.bzf/2.0/config.cfg</code>

Open the config in a text editor and add this line to it:

set consoleFont profont

Save the file, then start [[BZFlag]] and see the new font in action.

[This article was originally created by [[Legoguy]] - [[http://my.bzflag.org/bb/viewtopic.php?t=2677&highlight=profont see here.]]]

[[Category:Client]]

Scoreboard

2007-02-21T19:10:04Z

Brad: add text explaining the font used in the images

== Individual Player Scores ==

[[Image:Playerscores.png]]

The image above shows a typical [[scoreboard]] found in [[BZFlag]] on a [[Free For All]] server. Please note that the font in the image is not the default font - look [[Change_Default_Font|here]] for ways of changing the default font. The text below will explain what each of the numbers mean, going from left to right.

'''"Score" column'''
# Score of the player (kills - deaths).
# Number of players the player has killed.
# Number of players who have killed the player.
# The number in square brackets shows the number of teammates the player has killed.

'''"Kills" column'''
# The number of times you have killed that player.
# The number of times that player has killed you.

'''"Player" column'''
# An explanation of the symbols ("+", "-" and "@") can be found [[List_Server#When_I_join_a_game.2C_I_see_-.2C_.2B.2C_and_.40_in_front_of_player_callsigns.__What_do_these_mean.3F|here]].
# The [[callsign]] of the player.
# In brackets is the [[email]] of the player which only shows if not blank. This is sometimes set to the team of the player if they are in any [[leagues]].
# If the player is carrying a flag, a flag ID will show seperated by a forward slash. The possible flag IDs can be seen [[Flag_List|here]].

What team the player is on depends on the color of the callsign. Only red and green are available on this [[server]]. The white players at the bottom are [[observers]] (could be waiting to join, or just... observing).

== Team Scores ==

[[Image:Teamscores.png]]

The text below will explain what each of the numbers mean in the '''Team Score''' section of the [[scoreboard]]. Please note that this will change depending on the type of server you are on. The image shows team scores for a [[Free For All]] server.

Going from left to right:
# The total score of the team (wins - losses).
# The number of times players on the team have killed other players.
# The number of times players on the team been killed.
# The amount of players on the team. The image shows 4 purples, 3 greens, 2 reds and 3 blues. Please note that rogues and observers do not show here.

[[Category:Client]]

Scoreboard

2007-02-21T19:08:04Z

Brad: change text in accordance with new images

== Individual Player Scores ==

[[Image:Playerscores.png]]

The image above shows a typical [[scoreboard]] found in [[BZFlag]] on a [[Free For All]] server. The text below will explain what each of the numbers mean, going from left to right.

'''"Score" column'''
# Score of the player (kills - deaths).
# Number of players the player has killed.
# Number of players who have killed the player.
# The number in square brackets shows the number of teammates the player has killed.

'''"Kills" column'''
# The number of times you have killed that player.
# The number of times that player has killed you.

'''"Player" column'''
# An explanation of the symbols ("+", "-" and "@") can be found [[List_Server#When_I_join_a_game.2C_I_see_-.2C_.2B.2C_and_.40_in_front_of_player_callsigns.__What_do_these_mean.3F|here]].
# The [[callsign]] of the player.
# In brackets is the [[email]] of the player which only shows if not blank. This is sometimes set to the team of the player if they are in any [[leagues]].
# If the player is carrying a flag, a flag ID will show seperated by a forward slash. The possible flag IDs can be seen [[Flag_List|here]].

What team the player is on depends on the color of the callsign. Only red and green are available on this [[server]]. The white players at the bottom are [[observers]] (could be waiting to join, or just... observing).

== Team Scores ==

[[Image:Teamscores.png]]

The text below will explain what each of the numbers mean in the '''Team Score''' section of the [[scoreboard]]. Please note that this will change depending on the type of server you are on. The image shows team scores for a [[Free For All]] server.

Going from left to right:
# The total score of the team (wins - losses).
# The number of times players on the team have killed other players.
# The number of times players on the team been killed.
# The amount of players on the team. The image shows 4 purples, 3 greens, 2 reds and 3 blues. Please note that rogues and observers do not show here.

[[Category:Client]]

Scoreboard

2007-02-21T18:31:50Z

Brad: fix category

== Individual Player Scores ==

[[Image:Playerscores.png]]

The image above shows a typical [[scoreboard]] found in [[BZFlag]] on a [[Capture The Flag]] server. The text below will explain what each of the numbers mean, going from left to right.

'''"Score" column'''
# Score of the player (kills - deaths).
# Number of players the player has killed.
# Number of players who have killed the player.
# The number in square brackets shows the number of teammates the player has killed.

'''"Kills" column'''
# The number of times you have killed that player.
# The number of times that player has killed you.

'''"Player" column'''
# An explanation of the symbols ("+", "-" and "@") can be found [[List_Server#When_I_join_a_game.2C_I_see_-.2C_.2B.2C_and_.40_in_front_of_player_callsigns.__What_do_these_mean.3F|here]].
# The [[callsign]] of the player.
# In brackets is the [[email]] of the player which only shows if not blank. This is sometimes set to the team of the player if they are in any [[leagues]].
# If the player is carrying a flag, a flag ID will show seperated by a forward slash. The possible flag IDs can be seen [[Flag_List|here]].

What team the player is on depends on the color of the callsign. Only red and green are available on this [[server]]. The white players at the bottom are [[observers]] (could be waiting to join, or just... observing).

== Team Scores ==

[[Image:Teamscores.png]]

The text below will explain what each of the numbers mean in the '''Team Score''' section of the [[scoreboard]]. Please note that this will change depending on the type of server you are on. The image shows team scores for a [[Capture The Flag]] server.

Going from left to right:
# The total score of the team (wins - losses).
# The total flags the team has captured.
# The total captures the team has had against them.
# The amount of players on the team. The image shows 11 reds and 11 greens.

[[Category:Client]]

BZFlagWiki - User contributions [en]

Bz BasePlayerRecord

Bz BasePlayerRecord

Bz eAllowFlagGrab

Bz eAllowFlagGrabEvent

Bz eAllowFlagGrab

Bz eListServerUpdateEvent

DevelopmentPlans/2.3

DevelopmentPlans/2.3

Config File

Bz fireWorldGM

Category:Leagues

List Server Usage Policy

Airspawn

BZFlag on IRC

BZFlag on IRC

Category:Client

Category:Support

BZFlag SVN

Box

Help:Contents

AHOD

Talk:Main Page

Help:Contents

Talk:BZFlag Forums

Other Links

Help:Contents

Change Default Font

Change Default Font

Category:Plug-Ins

BZFlag on IRC

BZFlag on IRC

Server Bandwidth

Sample conf

Key Mapping

Dead Reckoning

Rotation Server

Group Permissions

Config File

Alias Your IP Address

Auto Team

AHOD

Change Default Font

Change Default Font

Ideas

Change Default Font

Change Default Font

Change Default Font

Scoreboard

Scoreboard

Scoreboard