BZFlagWiki - User contributions [en]

BZFS Command Line Options

2007-07-14T20:21:30Z

TD-Linux: /* The Options */ Link to Auto Team

BZFS supports a number of command line options that let you set the various modes and parameters for the game.

==Use==
Any command line option can be passed to BZFS in the command line, or placed in a text file passed in with the -conf parameter.

==Config files==
A [[Sample conf|config file]] is simply a text file with a list of command line options, one per line. This file can be the parameter to the -conf command line option. BZFS will load all options in the config file as if they had been passed in as runtime options.

==The Options==

*'''-a''' ''linear angular''
Sets the maximum linear and angular accelerations. The units are somewhat arbitrary so you'll have to experiment to find suitable values. Positive values will set limits to the acceleration and lower they are, greater is the inertia. Zero or negative values disable acceleration limits. '''-a 50 38''' is recommended for standard-speed servers.

*'''-admsg''' ''message''
Define a message which will be broadcast to all players every 15 minutes. This option can be used multiple times to define a multi-line message.

*'''-advertise''' ''groupname,groupname,...''
Allows control of who can see this server on the server list. Use -advertise NONE to make a private server (no one will see the server, but global logins can be used). The default, if -advertise is not specified, is to allow everyone to see the server. Otherwise, your server will only be listed to members of the groups which you specify with -advertise.

*'''-autoTeam'''
Instructs the server to automatically assign joining players to the team that needs more players, overriding user preference. For specifics on operation, see [[Auto Team]].

*'''-b'''
When -c is supplied, this option randomly rotates the buildings.

*'''-ban''' ''ip{,ip}*''
Prohibits connections from the listed IP addresses. Trailing 255 bytes are treated as mask bytes.

*'''-banfile''' ''filename''
Specifies the name of a file where bzfs will store the banlist. It will load the banlist from this file when it starts (if the file exists), and write the banlist back to the file when someone gets banned or unbanned. If this option isn't given the banlist will not be saved.

*'''-banTime'''
Default number of minutes player should be banned (unspecified, the default is 300).

*'''-c'''
Enables the capture-the-flag style game. By default this allocates one team flag per team. This can be modified see '''+f''' ''team''. By default, the free-for-all style is used.

*'''-cache''' ''worldCacheURL''
Specifies the URL for the world cache file. This is a binary file that clients will attempt to download before getting the world from the bzfs server.

*'''-cacheout''' ''filename''
Save the currently specified world into a binary cache file and exit.

*'''-conf''' ''configfilename''
Specifies the name of a configuration file to be used to set all of the bzfs options, rather than setting them on the command line.

*'''-cr'''
Enables the capture-the-flag style game with random map. You can optionally specify a building density by providing a number (default is 5). One team flag per team is provided, but more can be added through '''+f''' ''team''. By default, the free-for-all style is used.

*'''-d'''
Increase debugging level. If more '''-d''' is given, more debugging info is obtained.

*'''-density''' ''num''
Specify density for buildings, i.e. the higher the integer number, the more buildings you will get. This applies to automatically generated maps only.

*'''-disableBots'''
Prevent clients from using the ROGER autopilot or from using robots.

*'''+f''' ''{good|bad|teamflag-id}[{count}]''
Forces the existence of the given flag. If specified multiple times for the same flag-id, then that many flags will appear. The good argument is equivalent to specifying '''+f''' once for each kind of good flag. Same goes for the bad argument. The teamflag-id must match one of the predefined [[FlagCode|Flag Codes]].

*'''-f''' ''{flag-id}''
Restricts a certain flag from existing.

*'''-fb'''
Allow flags on box buildings.

*'''-filterCallsigns'''
Turn on the filtering of callsigns and email addresses. Callsigns and addresses are compared against bad words provided via '''-badwords'''.

*'''-filterChat'''
Turn on the filtering of chat messages. Messages that contain words listed via a '''-badwords''' file are replaced with !@#$%^&* characters.

*'''-filterSimple'''
By default, all filtering is aggressive, matching much more than what is strictly listed in a '''-badwords''' file for convenience. Providing this option will make the '''-filterCallsigns''' and '''-filterChat''' comparisons exact match only.

*'''-g'''
Quit after serving one game.

*'''-groupdb''' ''file''
Load groups from file

*'''-h'''
Buildings are given random heights.

*'''-handicap'''
Players are given a handicap advantage based on their ability in relation to the other players. Handicapped players will have faster tanks and shots. The handicap is determined by the player's score in relation to other players.

*'''-help'''
Shows a help page and lists all the valid flag id's.

*'''-helpmsg''' ''file name''
Create a help message accessible by /help name, which prints the contents of file. Restricted to 10 lines per help message.

*'''-i''' ''interface''
Server will listen for and respond to ''pings'' (sent via broadcast) on the given interface. Clients use this to find active servers on the network. This is the TCP/UDP/IP address the server will listen on.

*'''-j'''
Allows jumping.

*'''-lagdrop''' ''warn-count''
Kicks players after warn-count lag warnings.

*'''-lagwarn''' ''time/ms''
Send warnings to players that lag more than time. A single value sets the total number of players allowed. Five comma separated values set the maximum for each team. If a count is left blank then no limit is set for that team, except for the limit on the total number of players. Both forms may be provided.

*'''-mp''' ''total | rogue,red,green,blue,purple,observer''
Sets the maximum number of players, total or per team.A single value sets the total number of players allowed. Five comma separated values set the maximum for each team. If a count is left blank then no limit is set for that team, except for the limit on the total number of players. Both forms may be provided.

*'''-mps''' ''max-score''
Sets a maximum score for individual players. The first player to reach this score is declared the winner and the game is over.

*'''-ms ''shots''
Allows up to shots simultaneous shots for each player. This is 1 by default.

*'''-mts''' ''max-score''
Sets a maximum score for teams. The first team to reach this score is declared the winner and the game is over.

*'''-noMasterBanlist'''
Server will not attempt to load the [[Master Ban]] list from the internet.

*'''-p''' ''port''
Listen for game connections on port instead of the default port.Use '''-help''' to print the default port, or use '''-d''' debug printing.

*'''-passdb''' ''file''
Load passwords from file

*'''-passwd''' ''password''
Specify a server administrator password for use in remote administration such as /kick, /ban, /mute, etc messages.

*'''-pidfile''' ''filename''
Specify a file where the server will write its process ID so it may be used for remote administration.

*'''-poll''' ''variable=value''
Configure several aspects of the in-game polling system.

*'''-public'''
Causes the server to register itself with a list server, which clients can query to get a list of bzfs servers. By default, a server will respond to broadcast queries, allowing clients to find servers running on the standard port on the local subnet.

*'''-publicaddr''' ''address[:port]''
Advertise this server with the given address and port. Only has an effect when used with '''-public'''. Normally a server advertises itself at the local address and port. Some servers are not accessible from the internet at this address (for example servers behind a firewall using Network Address Translation). Use this option to specify the address and/or port that internet users should use to access this server.

*'''-publiclist''' ''url''
Advertise this server on the list servers listed at url. Only has an effect when used with '''-public'''. A built-in url is used by default. The BZFlag clients use the same built-in url so, by default, clients will see public servers automatically. This argument may be provided multiple times to publicize a server to multiple list servers.

*'''-q'''
If specified, the server will not listen for nor respond to ``pings''. BZFlag sends out these pings to give the user a list of available servers.This effectively makes the server private, especially if the '''-p''' option is also used.

*'''+r'''
Makes most shots ricochet. Super bullets, shock waves, and guided missiles do not.

*'''-rabbit''' ''[score|killer|random]''
Enables the rabbit-hunt style game. By default, the free-for-all style is used. You must specify the algorithm used to pick a new rabbit when the old one dies. The score algorithm uses a modified wins/(wins+losses) score and picks the top scoring player to be the new rabbit. The killer algorithm specifies a reverse tag game where whomever kills the rabbit becomes the new rabbit. The random algorithm randomly picks a new rabbit without regard to score. (The score algorithm is the original behavior.)

*'''-recbuf''' ''size''
Start with the recording buffer active, with the specified size (in megabytes).

*'''-recbufonly'''
Disable recording straight to files

*'''-reportfile''' ''filename''
Enable the /report command and log all reports to ''filename''.

*'''-reportpipe''' ''command''
Enable the /report command and execute ''command'' when a report is filed. This can be used together with, or instead of the '''-reportfile''' option.

*'''-requireudp'''
Require clients to use parallel UDP. If players fire before opening a UDP channel, kick them off the server.

*'''+s''' ''num-flags''
The server will have an extra num-flags random super flags available at all times. The '''-f''' option can be used to restrict which types of flags will be added. Required flags given by the '''+f''' option are not included in the num-flags total.

*'''-s''' ''num-flags''
The server will have up to num-flags random super flags available at any time.The '''-f''' option can be used to restrict which types of flags will be added. Required flags given by the '''+f''' option are not included in the ''num-flags'' total.

*'''-sa'''
Antidote flags are provided for players with bad flags.

*'''-sb'''
Allow spawns on box buildings.

*'''-set''' ''name value''
Set BZDB variable name to value

*'''-sl''' ''id num''
Restrict flag id to num shots.

*'''-spamtime''' ''time''
Minimum ''time'' between player chat messages that are alike.

*'''-spamwarn''' ''warnLimit''
Number of warnings a player/spammer gets, who violates '''-spamtime'''.

*'''-speedtol''' ''factor''
Override the default speed auto kick factor. The factor should not be less then 1.0. The factor is a multiplier.

*'''-srvmsg''' ''message''
Define a server welcome message. This option can be used multiple times to define a multiline message.

*'''-st''' ''time''
Bad flags are automatically dropped after time seconds.

*'''-sw''' ''count''
Bad flags are automatically dropped after count wins. Capturing a team flag does not count as a win.

*'''-synctime'''
Forces all clients to use the same time of day.T he current time is determined by the server's clock. This disables the + and - keys on the clients.

*'''-t'''
Adds teleporters to the game.

*'''-timemanual'''
The countdown has to be started manually using the /countdown command. This is useful for matches.

*'''-tk'''
Changes the default behavior where a player dies when he kills a teammate. When using this option, he will just get a -1 score penalty for the kill but not be killed in game.

*'''-tkannounce'''
Announces team kills to the admin channel

*'''-tkkr''' ''percent''
Kicks players whose team killing to normal kill ratio is greater than percent [1-100]. A start up grace period is given to players.

*'''-ts''' ''[micros]''
Include timestamp information in DEBUG output useful for logging. If micros is specified, microseconds will be added to the timestamp.

*'''-userdb''' ''file''
Load group associations from file

*'''-vars''' ''file''
Loads values for game configurable variables from file. Entries are one per line in the form: set variable value. For a list of variables that are configurable, in the BZFlag client, send a message with /set as the text.

*'''-version'''
Prints the version number of the executable.

*'''-vetoTime'''
Max seconds authorized user has to abort poll(default is 20).

*'''-votePercentage'''
Percentage of players required to affirm a poll (unspecified, the default is 50.1%).

*'''-voteRepeatTime'''
Minimum seconds required before a player may repeat a vote.

*'''-world''' ''world-file''
Reads a specific BZFlag .bzw world file in [[BZW]] format as the game map.

*'''-worldsize''' ''world-size''
Changes the size for random maps

==See also==
[[BZW|BZW world format]]

[[Category:Server]]

Tetra

2007-07-14T20:18:02Z

TD-Linux: It's not complete, I know, but who cares?

The tetra is a map object that was added in BZFlag 2.0.0 to create a polygon with four vertices. It is obsolete because of the appearance of the much more flexible [[mesh]] in BZFlag 2.0.2.

Roxport

2007-07-14T20:12:50Z

TD-Linux: oops fixed template

{{Template:Server}}
[[Roxport]]'s server is located in Fort Worth, Texas, connected to a DSL network. The server is a desktop computer built in 1997 at Computer Renaissance in Newport News, Virginia. It originally ran Win95 with a PII 233Mhz, 32mb RAM, 3g HD. It was later upgraded to 96mb RAM, 10g HD, and Win98SE. Finally, in 2001, its service life as a (MS/Windows) family home computer expired. It was converted to a full-time Linux server and is now running with a PII 333Mhz, 256mb RAM, 10g HD, and Debian Linux.<br />
=Public Servers=
roxport.game-host.org:5175 <br />
roxport.game-host.org:5176 <br />
=Private Servers=
roxport.game-host.org:5155 <br />

Roxport

2007-07-14T20:11:05Z

TD-Linux: Formatting & removed hard-to-see colors

{{Server}}
[[Roxport]]'s server is located in Fort Worth, Texas, connected to a DSL network. The server is a desktop computer built in 1997 at Computer Renaissance in Newport News, Virginia. It originally ran Win95 with a PII 233Mhz, 32mb RAM, 3g HD. It was later upgraded to 96mb RAM, 10g HD, and Win98SE. Finally, in 2001, its service life as a (MS/Windows) family home computer expired. It was converted to a full-time Linux server and is now running with a PII 333Mhz, 256mb RAM, 10g HD, and Debian Linux.<br />
=Public Servers=
roxport.game-host.org:5175 <br />
roxport.game-host.org:5176 <br />
=Private Servers=
roxport.game-host.org:5155 <br />

Roxport

2007-07-14T20:08:27Z

TD-Linux: Added server disclaimer template

{{Server}}
[[Roxport]]'s server is located in Fort Worth, Texas, connected to a DSL network. The server is a desktop computer built in 1997 at Computer Renaissance in Newport News, Virginia. It originally ran Win95 with a PII 233Mhz, 32mb RAM, 3g HD. It was later upgraded to 96mb RAM, 10g HD, and Win98SE. Finally, in 2001, its service life as a (MS/Windows) family home computer expired. It was converted to a full-time Linux server and is now running with a PII 333Mhz, 256mb RAM, 10g HD, and Debian Linux.<br />
public servers: <br />
roxport.game-host.org:5175 <br />
roxport.game-host.org:5176 <br />
<span style="color:#D3D3D3;">private server: <br />
roxport.game-host.org:5155 <br /></span>

Template:Server

2007-07-14T20:07:04Z

TD-Linux: A little disclaimer :D

{|style="width:100%;margin-top:+.7em;background-color:#fcfcfc;border:1px solid #ccc;"
|
||<div class="notice metadata" id="stub">''This article is about a community member's BZFlag server. The rules and views described here may not apply to the wiki.''</div>
|}

Talk:Roxport

2007-07-14T20:02:09Z

TD-Linux: Comment on server pages

Hmm, I don't know if descriptions of servers are allowed, but I don't see why not - it seems that this would be a good resource to find an owner of a server. I'll make a tag for server pages, I think.

Transparency

2007-07-14T19:59:07Z

TD-Linux: A redirect to the transparency section on the Materials page

#REDIRECT [[Material#Transparency]]

Material

2007-07-14T19:57:00Z

TD-Linux: Section on transparency

A material is used in a BZFlag world to define a new look for otherwise regular objects, such as [[Meshbox|meshboxes]].

==Code==
To put a material in your map, first it must be defined:
{|
|
material
name example_material
texture filename
addtexture filename
notextures
notexcolor
notexalpha
texmat -1
dyncol -1
ambient 0.0 0.0 0.0 1.0
diffuse 1.0 1.0 1.0 1.0
color 1.0 1.0 1.0 1.0
specular 0.0 0.0 0.0 1.0
emission 0.0 0.0 0.0 1.0
shininess 0.0
resetmat
end
|}
Valid parameters for a Material are:
<properties>
name=name for reference
texture=set the texture (must be .png but don't include the extension)
addtexture=add a texture (again, no extension is needed)
notextures=don't use textures.
notexcolor=don't apply the [[Color(BZW)|color]] to the texture
notexalpha=don't use the texture's alpha channel
texmat=specify a texture matrix. -1 for no texture matrix.
dyncol=specify a dynamic color. -1 for no dynamic color.
ambient=ambient color
diffuse=diffuse (main)[[Color(BZW)|color]]
[[Color(BZW)|color]]=synonym for diffuse
specular=specular [[Color(BZW)|color]]
emission=emission [[Color(BZW)|color]]
shininess=shiny!
resetmat=restore default values
</properties>
To actually apply a texture, you must use some sort of reference in an object, like so:
{|
|
meshbox
position 0 0 10
rotation 0
size 10 10 5
matref example_material
end
|}

==Transparency==
The transparency effect is created by setting the alpha component of a material's [[Color(BZW)|color]] to a value less than one.
Transparent objects should be sparingly, because everything behind them must always be rendered. In addition, very large transparent objects may be sorted and drawn in the wrong order. This is caused by the fact that the Z-buffer cannot be used because it would allow another transparent object to cover the transparent object, which would not look right. Thus, the transparent elements are instead sorted by determining the distance to a point in the center, which works well as long as there are not too many large transparent objects.
The same applies to textures that have transparent sections.

==Magic Material Names==
===General===
[[GroundMaterial]]
===Skybox===
[[LeftSkyboxMaterial]]
[[RightSkyboxMaterial]]
[[FrontSkyboxMaterial]]
[[BackSkyboxMaterial]]
[[TopSkyboxMaterial]]
[[BottomSkyboxMaterial]]

==History==
Materials were added in [[BZFlag 2.0.0]].

==Editor Support==
Materials are supported in [[Blender]] with [[BZWTools]], [[pyBZEdit]], and [[Wings3D]] with the [[BZW Exporter for Wings3D]]. Materials are NOT supported in [[BZEdit]] or [[BZFed]].

[[category:Map_Objects]]
[[category:Map Making]]

BZFS Command Line Options

2007-06-30T19:22:07Z

TD-Linux: Added -mp option that was oddly missing

BZFS supports a number of command line options that let you set the various modes and parameters for the game.

==Use==
Any command line option can be passed to BZFS in the command line, or placed in a text file passed in with the -conf parameter.

==Config files==
A [[Sample conf|config file]] is simply a text file with a list of command line options, one per line. This file can be the parameter to the -conf command line option. BZFS will load all options in the config file as if they had been passed in as runtime options.

==The Options==

*'''-a''' ''linear angular''
Sets the maximum linear and angular accelerations. The units are somewhat arbitrary so you'll have to experiment to find suitable values. Positive values will set limits to the acceleration and lower they are, greater is the inertia. Zero or negative values disable acceleration limits. '''-a 50 38''' is recommended for standard-speed servers.

*'''-admsg''' ''message''
Define a message which will be broadcast to all players every 15 minutes. This option can be used multiple times to define a multi-line message.

*'''-advertise''' ''groupname,groupname,...''
Allows control of who can see this server on the server list. Use -advertise NONE to make a private server (no one will see the server, but global logins can be used). The default, if -advertise is not specified, is to allow everyone to see the server. Otherwise, your server will only be listed to members of the groups which you specify with -advertise.

*'''-autoTeam'''
Instructs the server to automatically assign joining players to the team that needs more players, overriding user preference.

*'''-b'''
When -c is supplied, this option randomly rotates the buildings.

*'''-ban''' ''ip{,ip}*''
Prohibits connections from the listed IP addresses. Trailing 255 bytes are treated as mask bytes.

*'''-banfile''' ''filename''
Specifies the name of a file where bzfs will store the banlist. It will load the banlist from this file when it starts (if the file exists), and write the banlist back to the file when someone gets banned or unbanned. If this option isn't given the banlist will not be saved.

*'''-banTime'''
Default number of minutes player should be banned (unspecified, the default is 300).

*'''-c'''
Enables the capture-the-flag style game. By default this allocates one team flag per team. This can be modified see '''+f''' ''team''. By default, the free-for-all style is used.

*'''-cache''' ''worldCacheURL''
Specifies the URL for the world cache file. This is a binary file that clients will attempt to download before getting the world from the bzfs server.

*'''-cacheout''' ''filename''
Save the currently specified world into a binary cache file and exit.

*'''-conf''' ''configfilename''
Specifies the name of a configuration file to be used to set all of the bzfs options, rather than setting them on the command line.

*'''-cr'''
Enables the capture-the-flag style game with random map. You can optionally specify a building density by providing a number (default is 5). One team flag per team is provided, but more can be added through '''+f''' ''team''. By default, the free-for-all style is used.

*'''-d'''
Increase debugging level. If more '''-d''' is given, more debugging info is obtained.

*'''-density''' ''num''
Specify density for buildings, i.e. the higher the integer number, the more buildings you will get. This applies to automatically generated maps only.

*'''-disableBots'''
Prevent clients from using the ROGER autopilot or from using robots.

*'''+f''' ''{good|bad|teamflag-id}[{count}]''
Forces the existence of the given flag. If specified multiple times for the same flag-id, then that many flags will appear. The good argument is equivalent to specifying '''+f''' once for each kind of good flag. Same goes for the bad argument. The teamflag-id must match one of the predefined [[FlagCode|Flag Codes]].

*'''-f''' ''{flag-id}''
Restricts a certain flag from existing.

*'''-fb'''
Allow flags on box buildings.

*'''-filterCallsigns'''
Turn on the filtering of callsigns and email addresses. Callsigns and addresses are compared against bad words provided via '''-badwords'''.

*'''-filterChat'''
Turn on the filtering of chat messages. Messages that contain words listed via a '''-badwords''' file are replaced with !@#$%^&* characters.

*'''-filterSimple'''
By default, all filtering is aggressive, matching much more than what is strictly listed in a '''-badwords''' file for convenience. Providing this option will make the '''-filterCallsigns''' and '''-filterChat''' comparisons exact match only.

*'''-g'''
Quit after serving one game.

*'''-groupdb''' ''file''
Load groups from file

*'''-h'''
Buildings are given random heights.

*'''-handicap'''
Players are given a handicap advantage based on their ability in relation to the other players. Handicapped players will have faster tanks and shots. The handicap is determined by the player's score in relation to other players.

*'''-help'''
Shows a help page and lists all the valid flag id's.

*'''-helpmsg''' ''file name''
Create a help message accessible by /help name, which prints the contents of file. Restricted to 10 lines per help message.

*'''-i''' ''interface''
Server will listen for and respond to ''pings'' (sent via broadcast) on the given interface. Clients use this to find active servers on the network. This is the TCP/UDP/IP address the server will listen on.

*'''-j'''
Allows jumping.

*'''-lagdrop''' ''warn-count''
Kicks players after warn-count lag warnings.

*'''-lagwarn''' ''time/ms''
Send warnings to players that lag more than time. A single value sets the total number of players allowed. Five comma separated values set the maximum for each team. If a count is left blank then no limit is set for that team, except for the limit on the total number of players. Both forms may be provided.

*'''-mp''' ''total | rogue,red,green,blue,purple,observer''
Sets the maximum number of players, total or per team.A single value sets the total number of players allowed. Five comma separated values set the maximum for each team. If a count is left blank then no limit is set for that team, except for the limit on the total number of players. Both forms may be provided.

*'''-mps''' ''max-score''
Sets a maximum score for individual players. The first player to reach this score is declared the winner and the game is over.

*'''-ms ''shots''
Allows up to shots simultaneous shots for each player. This is 1 by default.

*'''-mts''' ''max-score''
Sets a maximum score for teams. The first team to reach this score is declared the winner and the game is over.

*'''-noMasterBanlist'''
Server will not attempt to load the [[Master Ban]] list from the internet.

*'''-p''' ''port''
Listen for game connections on port instead of the default port.Use '''-help''' to print the default port, or use '''-d''' debug printing.

*'''-passdb''' ''file''
Load passwords from file

*'''-passwd''' ''password''
Specify a server administrator password for use in remote administration such as /kick, /ban, /mute, etc messages.

*'''-pidfile''' ''filename''
Specify a file where the server will write its process ID so it may be used for remote administration.

*'''-poll''' ''variable=value''
Configure several aspects of the in-game polling system.

*'''-public'''
Causes the server to register itself with a list server, which clients can query to get a list of bzfs servers. By default, a server will respond to broadcast queries, allowing clients to find servers running on the standard port on the local subnet.

*'''-publicaddr''' ''address[:port]''
Advertise this server with the given address and port. Only has an effect when used with '''-public'''. Normally a server advertises itself at the local address and port. Some servers are not accessible from the internet at this address (for example servers behind a firewall using Network Address Translation). Use this option to specify the address and/or port that internet users should use to access this server.

*'''-publiclist''' ''url''
Advertise this server on the list servers listed at url. Only has an effect when used with '''-public'''. A built-in url is used by default. The BZFlag clients use the same built-in url so, by default, clients will see public servers automatically. This argument may be provided multiple times to publicize a server to multiple list servers.

*'''-q'''
If specified, the server will not listen for nor respond to ``pings''. BZFlag sends out these pings to give the user a list of available servers.This effectively makes the server private, especially if the '''-p''' option is also used.

*'''+r'''
Makes most shots ricochet. Super bullets, shock waves, and guided missiles do not.

*'''-rabbit''' ''[score|killer|random]''
Enables the rabbit-hunt style game. By default, the free-for-all style is used. You must specify the algorithm used to pick a new rabbit when the old one dies. The score algorithm uses a modified wins/(wins+losses) score and picks the top scoring player to be the new rabbit. The killer algorithm specifies a reverse tag game where whomever kills the rabbit becomes the new rabbit. The random algorithm randomly picks a new rabbit without regard to score. (The score algorithm is the original behavior.)

*'''-recbuf''' ''size''
Start with the recording buffer active, with the specified size (in megabytes).

*'''-recbufonly'''
Disable recording straight to files

*'''-reportfile''' ''filename''
Enable the /report command and log all reports to ''filename''.

*'''-reportpipe''' ''command''
Enable the /report command and execute ''command'' when a report is filed. This can be used together with, or instead of the '''-reportfile''' option.

*'''-requireudp'''
Require clients to use parallel UDP. If players fire before opening a UDP channel, kick them off the server.

*'''+s''' ''num-flags''
The server will have an extra num-flags random super flags available at all times. The '''-f''' option can be used to restrict which types of flags will be added. Required flags given by the '''+f''' option are not included in the num-flags total.

*'''-s''' ''num-flags''
The server will have up to num-flags random super flags available at any time.The '''-f''' option can be used to restrict which types of flags will be added. Required flags given by the '''+f''' option are not included in the ''num-flags'' total.

*'''-sa'''
Antidote flags are provided for players with bad flags.

*'''-sb'''
Allow spawns on box buildings.

*'''-set''' ''name value''
Set BZDB variable name to value

*'''-sl''' ''id num''
Restrict flag id to num shots.

*'''-spamtime''' ''time''
Minimum ''time'' between player chat messages that are alike.

*'''-spamwarn''' ''warnLimit''
Number of warnings a player/spammer gets, who violates '''-spamtime'''.

*'''-speedtol''' ''factor''
Override the default speed auto kick factor. The factor should not be less then 1.0. The factor is a multiplier.

*'''-srvmsg''' ''message''
Define a server welcome message. This option can be used multiple times to define a multiline message.

*'''-st''' ''time''
Bad flags are automatically dropped after time seconds.

*'''-sw''' ''count''
Bad flags are automatically dropped after count wins. Capturing a team flag does not count as a win.

*'''-synctime'''
Forces all clients to use the same time of day.T he current time is determined by the server's clock. This disables the + and - keys on the clients.

*'''-t'''
Adds teleporters to the game.

*'''-timemanual'''
The countdown has to be started manually using the /countdown command. This is useful for matches.

*'''-tk'''
Changes the default behavior where a player dies when he kills a teammate. When using this option, he will just get a -1 score penalty for the kill but not be killed in game.

*'''-tkannounce'''
Announces team kills to the admin channel

*'''-tkkr''' ''percent''
Kicks players whose team killing to normal kill ratio is greater than percent [1-100]. A start up grace period is given to players.

*'''-ts''' ''[micros]''
Include timestamp information in DEBUG output useful for logging. If micros is specified, microseconds will be added to the timestamp.

*'''-userdb''' ''file''
Load group associations from file

*'''-vars''' ''file''
Loads values for game configurable variables from file. Entries are one per line in the form: set variable value. For a list of variables that are configurable, in the BZFlag client, send a message with /set as the text.

*'''-version'''
Prints the version number of the executable.

*'''-vetoTime'''
Max seconds authorized user has to abort poll(default is 20).

*'''-votePercentage'''
Percentage of players required to affirm a poll (unspecified, the default is 50.1%).

*'''-voteRepeatTime'''
Minimum seconds required before a player may repeat a vote.

*'''-world''' ''world-file''
Reads a specific BZFlag .bzw world file in [[BZW]] format as the game map.

*'''-worldsize''' ''world-size''
Changes the size for random maps

==See also==
[[BZW|BZW world format]]

[[Category:Server]]

Teleporter

2007-05-09T22:20:55Z

TD-Linux: point to links page

A [[Teleporter]] is a [[BZW]] map structure that defines a object which transports the user to another teleporter in a different part of the world/map.
To be used effectively, one or more teleporters must be combined with [[link|links]].

==Code==
[[Image:Teleporter.jpg|frame|right|Teleporter with the default textures]]
The code for a teleporter object is as follows
{|
|
teleporter
name example_teleporter
position 0.0 0.0 0.0
size 5 0.125 20
rotation 0.0
border 1.12
end
|}
Valid parameters for a teleporter are
<properties>
name=defines a name for the teleport (2.0+ only). although rarely used, it proves helpful to use these for linking teleports.
position=defines the center of the teleporter in X and Y and the bottom of the teleporter in Z.
rotation=defines a rotation around the Z axis for the teleporter, in degrees.
size=defines the distance from the center to the side of the teleporter in X and Y, and the total height of the teleporter in Z.
border=defines the yellow caution border around the teleporter entry point.
</properties>

Note: Teleporters are entered through Y. As such, it is recommended to keep Y fairly small (.125 works well). However, if Y is zero, it will cause BZFlag bugs. If you need to enter a teleport from X, rotating it 90 degrees is the suggested solution. Teleports are 2-sided, not 4.

==Appearance==
Teleporters appear with a yellow/black caution texture on the outer border of the object and with a pulsing texture in the middle.

==History==
The teleporters first appeared in BZFlag 1.0.0. In [[BZFlag 2.0.0]], they were redesigned, introducing the name field, making link creation easier for designers.

==Editor Support==
Supported by all known editors.

[[category:Map Making]]
[[category:Map Objects]]

Skybox

2007-04-28T20:42:14Z

TD-Linux: stub!

Skyboxes replace the normal scenery of BZFlag.

The material names needed to create a skybox are:
* LeftSkyboxMaterial
* RightSkyboxMaterial
* TopSkyboxMaterial
* BottomSkyboxMaterial
* FrontSkyboxMaterial
* BackSyboxMaterial

BottomSkyboxMaterial

2007-04-28T20:39:29Z

TD-Linux: the last redirect! YAY!

#REDIRECT [[Skybox]]

TopSkyboxMaterial

2007-04-28T20:39:06Z

TD-Linux: only one redirect to go...

#REDIRECT [[Skybox]]

BackSkyboxMaterial

2007-04-28T20:38:41Z

TD-Linux: And another...

#REDIRECT [[Skybox]]

FrontSkyboxMaterial

2007-04-28T20:38:10Z

TD-Linux: yet another redirect...

#REDIRECT [[Skybox]]

RightSkyboxMaterial

2007-04-28T20:37:46Z

TD-Linux: another redirect...

#REDIRECT [[Skybox]]

LeftSkyboxMaterial

2007-04-28T20:37:17Z

TD-Linux: a redirect...

#REDIRECT [[Skybox]]

Material

2007-04-28T20:34:06Z

TD-Linux: Added magic material psuedodocumentation, courtesy JeffM2501

Talk:Zone

2007-04-09T01:20:05Z

TD-Linux: Information flag vs zoneflag

What is the difference between '''zoneflag''' and '''flag'''? I do not understand from this description. Is there a difference? I am assuming so since there are two different options. [[User:DonnyBaker|DonnyBaker]] 21:10, 23 March 2007 (EDT)

:Umm, I assume that '''zoneflag''' guarantee that there will be x number of x flag in that zone at any time. '''Flag''' probably just says that if there are any of x flag, they may spawn in there or they might not. Sorta confusing. Might want to get that double checked. In the old wiki it says, "Zone flag - Actually generates each flag listed w/in this zone (add ,n for quantity)" and for "Flag - where flag may spawn". [[User:Tanner|Tanner]] 15:54, 24 March 2007 (EDT)

:See what I put there now. Basically, flag says what kind of flags should spawn there (they need to be specified on teh command line) while zoneflag spawns extra flags for the zone. [[User:TD-Linux|TD-Linux]] 21:20, 8 April 2007 (EDT)

Zone

2007-04-09T01:19:03Z

TD-Linux: Better separated flag and zoneflag

A Zone is a [[BZW]] map structure that is only a rectangular prism area for spawn or flag zones.

==Code==
The code for a zone is as follows:
{|
|
zone
name example_zone
position 0.0 0.0 0.0
size 1.0 1.0 1.0
rotation 0.0
zoneflag GM,2 OO
flag L SW good bad
team 0 1 2 3 4
safety 1 2 3 4
end
|}
Valid parameters for the zone are
*'''position''': Defines the position of the zone in the word (x/y/x)
*'''size''': Defines the size of the zone (rectangular prism)
*'''rotation''': Defines a rotation around the Z axis for the box, in degrees.
*'''zoneflag''': Generates the flags listed inside this zone (adding flag,n for the quantity). The flags will be generated specifically for the zone, regardless of BZFS options.
*'''flag''': Listed flags will spawn in the zone. The flags need to be specified in the map via BZFS options.
*'''team''': Team players will spawn (0 = Rogue, 1 = Red, 2 = Green, 3 = Blue, 4 = Purple).
*'''saftey''': Team flags listed here will fly to the closest safety zone when dropped (0 = Rogue, 1 = Red, 2 = Green, 3 = Blue, 4 = Purple).

==Appearance==
Zones have no appearance in a map other than what they define (ex: flags or tank spawns).

==History==

==Editor Support==
The zone object is not supported by any known editors.

[[Category:Map Making]]
[[Category:Map_Objects]]

BZFlag SVN

2007-04-09T01:16:58Z

TD-Linux: Added instructions for reverting

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.

==Geting 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 cvs code for the 2.0.x compatable 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.

==Commiting 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===
There is probably a button for it somewhere.

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

Known Cheats

2007-04-09T01:08:34Z

TD-Linux: +{{Old}}

{{Old}}
Cheats performed on BZFlag are usually made by modifying your client. A great deal of power is invested in the client program, and therefore the client may cheat in every way from creating invincible tanks, to invisibility, to super killing. If you have seen any cheats, have performed them yourself, or have noticed a hole in the source, please add it here.

== List of Known Cheats ==

NOTE: Some of these cheats have been prevented in the current version of BZFlag. This list needs to be updated.

A cheater may:

* fly without Wings.
* shoot teammates without blowing them up.
* spawn with a flag (usually Guided Missile or Genocide, but can be anything).
* get any flag on demand (people get the exact flag they need to escape from you!).
* respond differently to gravity.
* move at a different rate (usually faster).
* shoot bullets that travel at a different rate (usually faster).
* hold multiple flags (such as shockwave, cloak, and stealth).
* fire multiple shots simultaneously (i.e. firing spreads of shots at once).
* cover the field with SW blasts.
* not respond to bad flags.
* move and pickup flags while paused.
* shoot other tanks while paused.
* instantaneous travel to a new location.
* lock on to other players with flags other than Guided Missile (or no flag at all).
* grab a new flag when passing through a teleporter (when no flag exists).
* double jump.
* shoot bullets which cannot be seen on radar or in the HUD.
* cause the bullets of other tanks to explode prematurely.
* be completely invincible.
* be partially invincible, repelling everything but some particular flags (often SW is chosen).
* drive outside of the playing area.
* produce abnormally large shockwave blasts.
* "drag 'n drop", moving from any location to any other at any speed.
* be zoned, but yet still shoot tanks that are not zoned.
* instantly kill everyone else.
* move backwards through buildings with the Oscillation Overthruster.
* produce abnormally long laser blasts (in terms of length and time).
* move through buildings without Oscillation Overthruster.
* jump back briefly to avoid a bullet then return to where you were ("network jitter").
* promote themselves to server administrator and give large bans and kicks.
* be completely invisible (or faded) without cloaking.
* change variables without polling successfully or being an admin

== Subtle Cheats ==
All the cheats listed above are "blatant" cheats in that they are easy to spot. There is a whole class of "subtle cheats" which are nearly impossible to spot. Please refer to the [[Subtle Cheats]] page.

[[Category:Server Security]]

Flag List

2007-04-09T01:04:59Z

TD-Linux: New antidote flag section

{{mergefrom|FlagCode}}
<h1>What are flags?</h1>
Flags are, well, flags. [[Tank|Tanks]] pick up a flag by driving over it. In general there are good and bad superflags, which change the behavior of the tank or weapon, and team flags. They are one of the key factors how to kill the other tanks.

Only one flag at a time may be carried and can usually be dropped by pressing the spacebar or middle mouse key (MMK). Except where a map has been configured to make you hold a "bad" superflag for a certain length of time before being automatically dropped. Some maps feature "antidote flags", which appear randomly in yellow as soon as you pick up a bad flag. Driving over the antidote flag will cause the bad flag to be dropped and the antidote flags to disappear. Some maps have the feature that shooting another tank will cause a carried bad flag to be dropped.

Can't see the flags on the playing field and/or on the radar? It's possible that the map doesn't have any flags but it's more likely that you've accidentally switched them off in your excited playing of the game! The default key to toggle flags on/off on the [[radar]] is '''h''', and in the [[HUD]] is '''j'''. Try pressing the appropriate key and see what happens!

== Team Flags ==

{|{{Prettytable}}
|-
| {{Hl3}} |'''Flag'''
| {{Hl3}} |'''Abbr'''
|-
| Red Team || R*
|-
| Blue Team || B*
|-
| Green Team || G*
|-
| Purple Team || P*
|}

Team flags are supplied by the server in the [[CTF|capture-the-flag]] style game. While at least one player is on a team, that team's flag is in the game. When captured, the flag is returned to the team's [[base]]. If the flag is dropped in a bad place, it is moved to a safety position. Bad places are on top of a building or on an enemy team base. The flag can be dropped on a team base only by a player from a third team; for example, when a blue player drops the red flag on the green base.

A team flag is captured when a tank drops an enemy flag onto its own base or when a tank takes its flag onto an enemy base, even if there's no one playing on that team. You must be on the ground to capture a flag.

== Good superflags ==
{|{{Prettytable}}
|-
| {{Hl3}} |'''Flag'''
| {{Hl3}} |'''Abbr'''
| {{Hl3}} |'''Description'''
|-
| High Speed || V || Boosts top speed by 50%.
|-
| Quick Turn || QT || Boosts turn rate by 50%.
|-
| Agility || A || Improves the dodging capabilities of the tank.
|-
| Oscillation Overthruster || OO || Lets the tank go through buildings. You cannot back up in or into a building, nor can you shoot while inside.
|-
| Rapid Fire || F || Increases shot speed and decreases range and reload delay.
|-
| Machine Gun || MG || Increases shot speed and dramatically decreases range and reload delay.
|-
| Guided Missile || GM || Shots guide themselves when locked on. The missile can be retargeted at any time during its flight (with the right mouse button). This allows the player some control over the missile steering.
|-
| Laser || L || Shoots a laser, with effectively infinite speed and range. Just point and shoot. The binoculars are handy for lining up distant targets. The downside (you knew it was coming) is that the reload time is doubled.
|-
| Ricochet || R || Shots bounce off walls. It is exceptionally easy to kill yourself with this flag.
|-
| Super Bullet || SB || Shots can go through buildings (possibly destroying a tank with the oscillation overthruster flag) and can also destroy (phantom) zoned tanks.
|-
| Stealth || ST || Tank becomes invisible on radar but is still visible out-the-window.
|-
| Cloaking || CL || Tank becomes invisible out-the-window but is still visible on radar.
|-
| Invisible Bullet || IB || Shots are invisible on radar (except your own). They are visible out-the-window. Sort of stealth for shots.
|-
| Tiny || T || Tank becomes much smaller and harder to hit. You must get quite close).
|-
| Shock Wave || SW || Tank does not fire shells. Instead it sends out a shock wave in all directions. Any tank caught in the wave is destroyed (including tanks on or in buildings).
|-
| Phantom Zone || PZ || Driving through a teleporter phantom zones the tank. A zoned tank cannot shoot, but can drive through buildings and cannot be destroyed except by a Super Bullet or a Shock Wave (or if the teams flag is captured).
|-
| Genocide || G || Destroying any tank on a team destroys every player on that team.
|-
| Jumping || JP || Allows the tank to jump. You cannot steer while in the air.
|-
| Identify || ID || Displays the identity of the closest flag in the vicinity.
|-
| Masquerade || MQ || Your tank looks like a teammate when viewed out of the window. Bullets, radar and targeting reveal your true identity.
|-
| Burrow || BU || Your tank burrows into the ground up to your muzzle, making you impervious to normal shots, as they sail above you. However your tank controls become sluggish (with the default server settings), your radar view is reduced and anyone, no matter what flag they have, can crush you like a beetle.
|-
| Seer || SE || Gives you the ability to see Stealthed, Cloaked and Masqueraded tanks as normal, as well as Invisible Bullets.
|-
| Thief || TH || Tank is small and fast, when you shoot an opponent, he is not killed, but instead, you steal his flag.
|-
| Useless || US || It is useless!
|-
| Wings || WG || Tank can drive around in the air, and may be able to jump multiple times. This can be useful when jumping or falling.
|}

== Bad superflags ==
{|{{Prettytable}}
|-
| {{Hl3}} |'''Flag'''
| {{Hl3}} |'''Abbr'''
| {{Hl3}} |'''Description'''
|-
| Colorblindness || CB || Prevents tank from seeing any team information about other tanks. You have to be careful to avoid shooting teammates.
|-
| Momentum || M || Gives the tank a lot of inertia.
|-
| Blindness || B || Blanks the out-the-window view. The radar still works. It is effectively impossible to detect any tank with Stealth; shooting a Stealth with Blindness is the stuff legends are made of.
|-
| Jamming || JM || Disables the radar but you can still see.
|-
| Wide Angle || WA || Gives the tank a fish eye lens that
|-
| No Jumping || NJ || Tank is not allowed to jump.
|-
| Trigger Happy || TR || Tank cannot stop shooting. Watch out for that richochet.
|-
| Reverse Controls || RC || Tank driving controls are reversed from their usual behavior.
|}

== Antidote Flag ==
The antidote flag is not really a flag, though it appears like one. It is rarely used, and is only useful on servers with bad flags. When it is enabled and a player picks up a bad flag, their client randomly places a yellow antidote flag on the map. Upon touching the flag, the player instantly drops their bad flag.

The antidote flag is not a real flag because its location is determined by the client, it is not seen by other clients, it can be 'picked up' when carrying a flag, and instantly disspears when 'picked up'.

==Flag Ideas==
See [[Flag Ideas]] page
[[Category:Gameplay]]

Flag List

2007-04-09T00:59:35Z

TD-Linux: Added table to 'Team Flags' section

{{mergefrom|FlagCode}}
<h1>What are flags?</h1>
Flags are, well, flags. [[Tank|Tanks]] pick up a flag by driving over it. In general there are good and bad superflags, which change the behavior of the tank or weapon, and team flags. They are one of the key factors how to kill the other tanks.

Only one flag at a time may be carried and can usually be dropped by pressing the spacebar or middle mouse key (MMK). Except where a map has been configured to make you hold a "bad" superflag for a certain length of time before being automatically dropped. Some maps feature "antidote flags", which appear randomly in yellow as soon as you pick up a bad flag. Driving over the antidote flag will cause the bad flag to be dropped and the antidote flags to disappear. Some maps have the feature that shooting another tank will cause a carried bad flag to be dropped.

Can't see the flags on the playing field and/or on the radar? It's possible that the map doesn't have any flags but it's more likely that you've accidentally switched them off in your excited playing of the game! The default key to toggle flags on/off on the [[radar]] is '''h''', and in the [[HUD]] is '''j'''. Try pressing the appropriate key and see what happens!

== Team Flags ==

{|{{Prettytable}}
|-
| {{Hl3}} |'''Flag'''
| {{Hl3}} |'''Abbr'''
|-
| Red Team || R*
|-
| Blue Team || B*
|-
| Green Team || G*
|-
| Purple Team || P*
|}

Team flags are supplied by the server in the [[CTF|capture-the-flag]] style game. While at least one player is on a team, that team's flag is in the game. When captured, the flag is returned to the team's [[base]]. If the flag is dropped in a bad place, it is moved to a safety position. Bad places are on top of a building or on an enemy team base. The flag can be dropped on a team base only by a player from a third team; for example, when a blue player drops the red flag on the green base.

A team flag is captured when a tank drops an enemy flag onto its own base or when a tank takes its flag onto an enemy base, even if there's no one playing on that team. You must be on the ground to capture a flag.

== Good superflags ==
{|{{Prettytable}}
|-
| {{Hl3}} |'''Flag'''
| {{Hl3}} |'''Abbr'''
| {{Hl3}} |'''Description'''
|-
| High Speed || V || Boosts top speed by 50%.
|-
| Quick Turn || QT || Boosts turn rate by 50%.
|-
| Agility || A || Improves the dodging capabilities of the tank.
|-
| Oscillation Overthruster || OO || Lets the tank go through buildings. You cannot back up in or into a building, nor can you shoot while inside.
|-
| Rapid Fire || F || Increases shot speed and decreases range and reload delay.
|-
| Machine Gun || MG || Increases shot speed and dramatically decreases range and reload delay.
|-
| Guided Missile || GM || Shots guide themselves when locked on. The missile can be retargeted at any time during its flight (with the right mouse button). This allows the player some control over the missile steering.
|-
| Laser || L || Shoots a laser, with effectively infinite speed and range. Just point and shoot. The binoculars are handy for lining up distant targets. The downside (you knew it was coming) is that the reload time is doubled.
|-
| Ricochet || R || Shots bounce off walls. It is exceptionally easy to kill yourself with this flag.
|-
| Super Bullet || SB || Shots can go through buildings (possibly destroying a tank with the oscillation overthruster flag) and can also destroy (phantom) zoned tanks.
|-
| Stealth || ST || Tank becomes invisible on radar but is still visible out-the-window.
|-
| Cloaking || CL || Tank becomes invisible out-the-window but is still visible on radar.
|-
| Invisible Bullet || IB || Shots are invisible on radar (except your own). They are visible out-the-window. Sort of stealth for shots.
|-
| Tiny || T || Tank becomes much smaller and harder to hit. You must get quite close).
|-
| Shock Wave || SW || Tank does not fire shells. Instead it sends out a shock wave in all directions. Any tank caught in the wave is destroyed (including tanks on or in buildings).
|-
| Phantom Zone || PZ || Driving through a teleporter phantom zones the tank. A zoned tank cannot shoot, but can drive through buildings and cannot be destroyed except by a Super Bullet or a Shock Wave (or if the teams flag is captured).
|-
| Genocide || G || Destroying any tank on a team destroys every player on that team.
|-
| Jumping || JP || Allows the tank to jump. You cannot steer while in the air.
|-
| Identify || ID || Displays the identity of the closest flag in the vicinity.
|-
| Masquerade || MQ || Your tank looks like a teammate when viewed out of the window. Bullets, radar and targeting reveal your true identity.
|-
| Burrow || BU || Your tank burrows into the ground up to your muzzle, making you impervious to normal shots, as they sail above you. However your tank controls become sluggish (with the default server settings), your radar view is reduced and anyone, no matter what flag they have, can crush you like a beetle.
|-
| Seer || SE || Gives you the ability to see Stealthed, Cloaked and Masqueraded tanks as normal, as well as Invisible Bullets.
|-
| Thief || TH || Tank is small and fast, when you shoot an opponent, he is not killed, but instead, you steal his flag.
|-
| Useless || US || It is useless!
|-
| Wings || WG || Tank can drive around in the air, and may be able to jump multiple times. This can be useful when jumping or falling.
|}

== Bad superflags ==
{|{{Prettytable}}
|-
| {{Hl3}} |'''Flag'''
| {{Hl3}} |'''Abbr'''
| {{Hl3}} |'''Description'''
|-
| Colorblindness || CB || Prevents tank from seeing any team information about other tanks. You have to be careful to avoid shooting teammates.
|-
| Momentum || M || Gives the tank a lot of inertia.
|-
| Blindness || B || Blanks the out-the-window view. The radar still works. It is effectively impossible to detect any tank with Stealth; shooting a Stealth with Blindness is the stuff legends are made of.
|-
| Jamming || JM || Disables the radar but you can still see.
|-
| Wide Angle || WA || Gives the tank a fish eye lens that
|-
| No Jumping || NJ || Tank is not allowed to jump.
|-
| Trigger Happy || TR || Tank cannot stop shooting. Watch out for that richochet.
|-
| Reverse Controls || RC || Tank driving controls are reversed from their usual behavior.
|}

==Flag Ideas==
See [[Flag Ideas]] page
[[Category:Gameplay]]

Talk:Flag List

2007-04-09T00:55:48Z

TD-Linux: Forgot signature

A distinction should be made between superflags and flags that are not super. G, SW, GM, ST, L, WG, SB, BU should be considered Super, the others not. [[User:Hannibal]]

I don't think flags should be spread across different pages; not sure if that's what is being suggested? The line between super flags and bad flags isn't clear. What about CL? Probably super too (gives you an advantage). But what about PZ? It's good in that it reduces the number of ways you can be killed. But it's bad because you can't kill anyone while you hold it. And US? Is it neutral? Or bad - you wasted time picking it up! GM isn't so brilliant, you can't lock it at close range. BU usually slows you down and reduces the radar range. What about team flags? Whether a flag is labelled super or bad or whatever doesn't really matter. Just describe how it affects the tank carrying it and adjust your playing to suit. [[User:Mr Burns|Mr Burns]] 04:08, 4 April 2007 (EDT)

I think all white flags are called Super Flags. Those flags are then in 2 categories good or bad. All good flags have weaknesses, and that is by design. Useless is the real fence rider as to whether it is good or bad. I could argue it either way so, maybe, it and the Team Flags are neutral as they do nothing to/for the tank. [[User:DonnyBaker|DonnyBaker]] 09:54, 4 April 2007 (EDT)
:I agree with this, I always have thought Super Flags == White Flags. [[User:TD-Linux|TD-Linux]] 20:55, 8 April 2007 (EDT)

No, I was suggesting a seperate category, in the chart and general page info, for superflags. I was under the impression that 'flags' was the term for all the white ones. I believe on the GU non-league HiX, it advertises 'no superflags' but Tiny, V, A, etc. were on the map. Maybe I'm mistaken about this, though. A clear definition of superflag seems to be in order, but that may be hard. I tend to draw the line at wether a player with the given flag can dominate a game, if not, its just a good flag. [[Hannibal]]

Talk:Flag List

2007-04-09T00:54:33Z

TD-Linux: Super Flags

A distinction should be made between superflags and flags that are not super. G, SW, GM, ST, L, WG, SB, BU should be considered Super, the others not. [[User:Hannibal]]

I don't think flags should be spread across different pages; not sure if that's what is being suggested? The line between super flags and bad flags isn't clear. What about CL? Probably super too (gives you an advantage). But what about PZ? It's good in that it reduces the number of ways you can be killed. But it's bad because you can't kill anyone while you hold it. And US? Is it neutral? Or bad - you wasted time picking it up! GM isn't so brilliant, you can't lock it at close range. BU usually slows you down and reduces the radar range. What about team flags? Whether a flag is labelled super or bad or whatever doesn't really matter. Just describe how it affects the tank carrying it and adjust your playing to suit. [[User:Mr Burns|Mr Burns]] 04:08, 4 April 2007 (EDT)

I think all white flags are called Super Flags. Those flags are then in 2 categories good or bad. All good flags have weaknesses, and that is by design. Useless is the real fence rider as to whether it is good or bad. I could argue it either way so, maybe, it and the Team Flags are neutral as they do nothing to/for the tank. [[User:DonnyBaker|DonnyBaker]] 09:54, 4 April 2007 (EDT)
:I agree with this, I always have thought Super Flags == White Flags.

No, I was suggesting a seperate category, in the chart and general page info, for superflags. I was under the impression that 'flags' was the term for all the white ones. I believe on the GU non-league HiX, it advertises 'no superflags' but Tiny, V, A, etc. were on the map. Maybe I'm mistaken about this, though. A clear definition of superflag seems to be in order, but that may be hard. I tend to draw the line at wether a player with the given flag can dominate a game, if not, its just a good flag. [[Hannibal]]

BZFX

2007-04-09T00:13:10Z

TD-Linux: More fixing of the first section

[http://bzfx.net/ BZFX] is a BZFlag server network. It is owned and operated by [[User:A_Meteorite|A Meteorite]].

= Why another server network? =

[[User:A_Meteorite|A Meteorite]], the founder of the network, believed that he could do it better than the large server networks currently in existence. He is developing proprietary software to operate the network.

= Contact =

To contact BZFX directly, you should go to the [irc://irc.freenode.net/#bzfx #bzfx channel] on IRC Freenode.

If you have been reprimanded by a BZFX administrator, and have a problem with it, '''contact that administrator first'''. Issues can almost always be resolved, but if it can not be, BZFX's owner, A Meteorite, will be contacted. If you need to contact A Meteorite for a reason other than administration issues, see [[User:A_Meteorite|his user page]].

= History =

BZFX was started in early-2006 by [[User:A_Meteorite|A Meteorite]]. The exact date when BZFX started hosting servers is unknown, but the [http://bzfx.net/ BZFX domain] was registered May 29, 2006 which makes it the official birthday of BZFX.

= Rules =

* No cussing or swearing. This includes abbreviations. Basically if the FCC won't allow it (except for a few other words), BZFX won't allow it.
* No [[Team_Kill|teamkilling]]. This includes capturing your own team's flag. The only exception to this is if the current game style is [[HoldTheFlag|HTF]].
* No cheating. This is defined as any source modification to your BZFlag client that gives you an advantage others do not have. Features available in [[BZFlag_SVN|BZFlag's SVN]] that are not in stable binary releases do not apply.
* "Wall walking" is considered cheating. Wall walking is using artificial means to go through walls or other objects not intended to go through.
* Use common sense, don't come to BZFX just to make irritate other players or ruin the general atmosphere.

Players that do not abide by these rules will be dealt with immediately. Possible punishments include muting, [[Kick|kicking]], and [[Ban|banning]].

All chat is logged at BZFX servers.

If you have been reprimanded for breaking a rule, and would like to contact someone about it, the server owner wishes that you contact the administrator that did the reparations directly.

== Groups ==

* '''BZFX.hAdmin''' (Head Admin): The highest group of BZFX, but basically BZFX.Admin [[Server_Permissions|permissions]] wise. It is used for more of a politically correct standpoint. Contains server owners (not map owners), developers, and otherwise large-scale contributors.
* '''BZFX.Admin''': The second highest group of BZFX. Contains administrators that have been on-board with BZFX for a long time and those who have shown an extraordinary commitment to BZFX.
* '''BZFX.Cop''': The mainstream group, but certainly not the least group. Our new cops go here until they have more experience with BZFX's ways. People who are valuable, but do not admin as much, may also go here.
* '''BZFX.Hidden''': A hidden admin group. It is used to catch people who may otherwise act differently if they see an administrator logged into the server.

BZFX

2007-04-08T23:43:39Z

TD-Linux: Took out unnecessary parts, though they now need a bit of reorganization

[http://bzfx.net/ BZFX] is a BZFlag server network. It is owned and operated by [[User:A_Meteorite|A Meteorite]].

= Why another server network? =

[[User:A_Meteorite|A Meteorite]] believed that no well-created and managed unified BZFlag server network existed. He believed he could do it better, and others have believed in him and BZFX. Since BZFX has been founded and taken off, several pieces of software has been in development for the higher furthering of BZFlag servers.

= Contact =

To contact BZFX directly, you should go to the [irc://irc.freenode.net/#bzfx #bzfx channel] on IRC Freenode.

If you have been reprimanded by a BZFX administrator, and have a problem with it, '''contact that administrator first'''. Issues can almost always be resolved, but if it can not be, BZFX's owner, A Meteorite, will be contacted. If you need to contact A Meteorite for a reason other than administration issues, see [[User:A_Meteorite|his user page]].

= History =

BZFX was started in early-2006 by [[User:A_Meteorite|A Meteorite]]. The exact date when BZFX started hosting servers is unknown, but the [http://bzfx.net/ BZFX domain] was registered May 29, 2006 which makes it the official birthday of BZFX.

= Rules =

BZFX's rules are strictly enforced. They are not hard to abide by, and that's all BZFX asks of it's players.

* No cussing or swearing. This includes abbreviations. Basically if the FCC won't allow it (except for a few other words), BZFX won't allow it.
* No [[Team_Kill|teamkilling]]. This includes capturing your own team's flag. The only exception to this is if the current game style is [[HoldTheFlag|HTF]].
* No cheating. This is defined as any source modification to your BZFlag client that gives you an advantage others do not have. Features available in [[BZFlag_SVN|BZFlag's SVN]] that are not in stable binary releases do not apply.
* "Wall walking" is considered cheating. Wall walking is using artificial means to go through walls or other objects not intended to go through.
* Use common sense, don't come to BZFX just to make irritate other players or ruin the general atmosphere.

Players that do not abide by these rules will be dealt with immediately. Possible punishments include muting, [[Kick|kicking]], and [[Ban|banning]].

All chat is logged at BZFX servers.

If you have been reprimanded for breaking a rule, and would like to contact someone about it, the server owner wishes that you contact the administrator that did the reparations directly.

== Groups ==

* '''BZFX.hAdmin''' (Head Admin): The highest group of BZFX, but basically BZFX.Admin [[Server_Permissions|permissions]] wise. It is used for more of a politically correct standpoint. Contains server owners (not map owners), developers, and otherwise large-scale contributors.
* '''BZFX.Admin''': The second highest group of BZFX. Contains administrators that have been on-board with BZFX for a long time and those who have shown an extraordinary commitment to BZFX.
* '''BZFX.Cop''': The mainstream group, but certainly not the least group. Our new cops go here until they have more experience with BZFX's ways. People who are valuable, but do not admin as much, may also go here.
* '''BZFX.Hidden''': A hidden admin group. It is used to catch people who may otherwise act differently if they see an administrator logged into the server.

Main Page

2007-04-01T19:21:11Z

TD-Linux: Much improved.

__NOTOC__[[Image:Wzflag.png|center]]
{|style="width:100%;margin-top:+.7em;background-color:#fcfcfc;border:1px solid #ccc"
|style="width:56%;color:#000"|
{|style="width:280px;border:solid 0px;background:none"
|-
|style="width:280px;text-align:center;white-space:nowrap;color:#000" |
[[Image:Bzflag-48x48.png|left]]
<div style="font-size:162%;border:none;margin: 0;padding:.1em;color:#000">Welcome to the WZFlag Wiki,</div>
<div style="top:+0.2em;font-size: 95%">The source for community information on most things related to WZFlag!</div>
<div style="font-size:162%;border:none;margin: 0;padding:.1em;color:#000">The WZFlag Wiki motto: [[BZFlagWiki:Be_bold|'''Be Bold!!''']]</div>
<div id="articlecount" style="width:100%;text-align:center;font-size:85%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] articles available</div>
|}
|style="width:15%;font-size:95%"|
[[Image:Bzflag-48x48.png|right]]
*[http://my.bzflag.org/bb The Forums]
*[http://my.bzflag.org WZFlag Stats]
*[http://sourceforge.net/projects/bzflag/ WZFlag on SourceForge]

|}
Welcome to the newly launched WZFlag Wiki. The number of articles is growing, but there is much more to do. The hope of this site is to draw together all of the great information about WZFlag and WZFlag related items that is currently scattered in many different places. Bringing all of this information together will make it easier for people to understand and answer all of the questions they have about running a server (options, permissions, set-up, etc.), configuring their client, coding plug-ins, compiling the source code, and anything else they can think of. All are welcome to contribute and may edit most pages. With everyone's help we can make this site a great resource to the WZFlag community. Please remember the WZFlag Wiki's new motto, [[BZFlagWiki:Be_bold|'''Be Bold''']] (click the link for a full explanation of the motto), when editing articles.

If you are unsure of how to edit or add pages, there is always a link to the [[Help:Contents|'''Help''']] section on the links to the left no matter where you are on the site. Don't be shy; give editing the site a try and be proud of your contributions! You can edit whether or not you have an account created. The advantage of having an account is that you will be credited with the contribution on the ''History'' link/tab of the page.

==Google Summer of Code 2007==
WZFlag is a participating mentor organization in the [http://code.google.com/soc/ Google Summer of Code] this year. What this basically amounts to is that if you are a full-time student and 18+ years old, and your application is accepted, Google will pay you to write code for WZFlag. Prospective students are encouraged to submit project proposals that are in line with our '''[[Google Summer of Code|goals]]''' for this summer, though proposals for other [[Ideas]] will be considered.

==General Information==
[[Getting Help]]

==Areas of Interest==
*[[:Category:Client|Client]]
*[[:Category:Compiling|Compiling]]
*[[:Category:Concepts|Concepts]]
*[[:Category:Development|Development]]
*[[:Category:Gameplay|Gameplay]]
*[[:Category:Installing|Installing]]
*[[:Category:Map Making|Map Making]]
*[[:Category:Maps|Maps]]
*[[:Category:Plug-Ins|Plug-ins]]
*[[Releases]]
*[[:Category:Server|Server]]
*[[:Category:Support|Support]]
*[[:Category:Tactics|Tactics]]
*[[Versions]]

==Things To Do==
*[[:Category:Stubs|Stubs]]
*[[:Special:Wantedpages|Wanted pages (links, but no page,yet...)]]
*[[:Category:Items to be merged|Pages to merge]]
*[[:Category:Old|Pages with old info]]
*[[:Category:Inaccurate|Inaccurate Pages]]
*[[:Category:Pending Deletions|Pending Deletions]]

File:Wzflag.png

2007-04-01T19:17:52Z

TD-Linux: The new temporary BZFlag banner.

The new temporary BZFlag banner.

Different Mouse Settings

2007-03-21T00:29:55Z

TD-Linux: +inaccurate

{{inaccurate}}
The cursor movement controls the [[Tank]] which is controlled by the operating system the game runs on. The driver are giving different setup possibilities. This article covers some parts of those.

== Overview ==

The acceleration of your tank is controlled by moving the cursor in the little box on the [[HUD]]. This determines how fast the cursor is moving on the screen.

== Different Mousebox Sizes==

{|{{Prettytable}}
|-
| {{Hl3}} |'''Mousebox size'''
| {{Hl3}} |'''Pros'''
| {{Hl3}} |'''Cons'''
|-

|Big Mousebox
|Driver has more precise control over the tank. Good for climbing on buildings and avoiding falling from buildings.
|The cursor takes longer to travel around the whole box. This leads to the tank accelerating slower into the next direction => you can dodge bullets, but with |great difficulty and effort
|-
|Little Mousebox
| It enables you to dodge bullets with much less movement, therefore more quickly.
|It is also much easier to accidentally fall down from buildings.
|-
|Middle Mousebox Size
|A happy- medium of precision and reaction speed. Can be used to dodge bullets relatively well. Falling down from buildings is much rarer than when using a miniscule mousebox
|You end up getting neither the absolute control nor the best reaction time.
|}

== Different Cursor Settings ==
{|{{Prettytable}}
|-
| {{Hl3}} |'''Cursor movement'''
| {{Hl3}} |'''Pros'''
| {{Hl3}} |'''Cons'''
| {{Hl3}} |'''Good Mousebox in combination'''
|-
|Fast Cursor
|Very good to dodge bullets.
|Risky to drive around on buildings.
|Big or middle mousebox. Only use a small mousebox if you don't jump often.
|-
|Slow Cursor
|Good for doing complicated jumps.
|Hard to dodge incoming bullets.
|Small or middle mousebox. A big mousebox is suicide!
|-
|Middle Cursor Speed
|Can be used to dodge much incoming bullets. Driving on buildings is not dangerous.
|Occasionally you can't dodge or fall down from a building.
|Big, middle and small mouseboxes can be used.
|}

== Platform differences ==

=== Cursor Speed ===
Speed is a linear factor added to your cursor movement. The cursor is constantly faster/slower.

=== Cursor Acceleration ===
Acceleration is a multiplier to your cursor movement. High impact to cursor movement when moving the mouse fast, slow impact when moving the mouse slower.

=== I'm on Mac OS X - Others seem to have an advantage ===

The only real advantage they have is the agility flag, that is because on other platforms mouse drivers use speed instead of acceleration. The resulting change is that they Find it easier to drive a straight line and then jump with the agility flag so that they can escape easier. With mouse acceleration you gain some other advantages against the player with mouse speed, like you will always be able to react quicker than them and can move more precisely when you move your cursor slower.

Macs use mouse acceleration because it is better than mouse speed - a lot of people say it is strange simply because they are not used to it. Driving on the different platforms is really a rather big difference.

All that talk about acceleration and speed may sound strange to you - with drivers like [http://plentycom.jp/en/steermouse/ SteerMouse] and [http://www.usboverdrive.com/ USBOverdrive] you can quickly get a feeling for the difference.

A good mousepad (more important than the mouse itself!) and a nice mouse change a lot but the cost needs to be considered.

[[Category:Tactics]]
[[Category:Client]]

Talk:Different Mouse Settings

2007-03-21T00:29:13Z

TD-Linux: Mac OS X?

What is with the whole thing on Mac OS X, which claims only Mac OS X uses 'mouse acceleration'. In fact, Windoze has for a very long time, as has X11. And the terms aren't very accurate anyway, it seems - anyone know about what is being talked about here? Is this old stuff from the old wiki? [[User:TD-Linux|TD-Linux]] 20:29, 20 March 2007 (EDT)

BZFS Command Line Options

2007-03-19T21:20:48Z

TD-Linux: Random grammar, format, ws fixes

BZFS supports a number of command line options that let you set the various modes and parameters for the game.

==Use==
Any command line option can be passed to BZFS in the command line, or placed in a text file passed in with the -conf parameter.

==Config files==
A [[Sample conf|config file]] is simply a text file with a list of command line options, one per line. This file can be the parameter to the -conf command line option. BZFS will load all options in the config file as if they had been passed in as runtime options.

==The Options==

*'''-a''' ''linear angular''
Sets the maximum linear and angular accelerations. The units are somewhat arbitrary so you'll have to experiment to find suitable values. Positive values will set limits to the acceleration and lower they are, greater is the inertia. Zero or negative values disable acceleration limits.

*'''-admsg''' ''message''
Define a message which will be broadcast to all players every 15 minutes. This option can be used multiple times to define a multi-line message.

*'''-advertise''' ''groupname,groupname,...''
Allows control of who can see this server on the server list. Use -advertise NONE to make a private server (no one will see the server, but global logins can be used). The default, if-advertise is not specified, is to alloweveryone to see the server. Otherwise, your server will only be listed to members of the groups which you specify with -advertise.

*'''-ban''' ''ip{,ip}*''
Prohibits connections from the listed IP addresses. Trailing 255 bytes are treated as mask bytes.

*'''-banfile''' ''filename''
Specifies the name of a file where bzfs will store the banlist. It will load the banlist from this file when it starts (if the file exists), and write the banlist back to the file when someone gets banned or unbanned. If this option isn't given the banlist will not be saved.

*'''-c'''
Enables the capture-the-flag style game. By default this allocates one team flag per team. This can be modified see '''+f''' ''team''. By default, the free-for-all style is used.

*'''-cache''' ''worldCacheURL''
Specifies the URL for the world cache file. This is a binary file that clients will attempt to download before getting the world from the bzfs server.

*'''-cacheout''' ''filename''
Save the currently specified world into a binary cache file and exit.

*'''-conf''' ''configfilename''
Specifies the name of a configuration file to be used to set all of the bzfs options, rather than setting them on the command line.

*'''-cr'''
Enables the capture-the-flag style game with random map. You can optionally specify a building density by providing a number (default is 5). One team flag per team is provided, but more can be added thru '''+f''' ''team''.By default, the free-for-all style is used.

*'''-d'''
Increase debugging level. If more '''-d''' is given, more debugging info is obtained.

*'''-density''' ''num''
Specify density for buildings, i.e. the higher the integer number, the more buildings you will get. This applies to automatically generated maps only.

*'''-disableBots'''
Prevent clients from using the ROGER autopilot or from using robots.

*'''+f''' ''{good|bad|teamflag-id}[{count}]''
Forces the existence of the given flag. If specified multiple times for the same flag-id, then that many flags will appear. The good argument is equivalent to specifying '''+f''' once for each kind of good flag. Same goes for the bad argument. The teamflag-id must match one of the predefined [[FlagCode|Flag Codes]].

*'''-fb'''
Allow flags on box buildings.

*'''-filterCallsigns'''
Turn on the filtering of callsigns and email addresses. Callsigns and addresses are compared against bad words provided via '''-badwords'''.

*'''-filterChat'''
Turn on the filtering of chat messages. Messages that contain words listed via a '''-badwords''' file are replaced with !@#$%^&* characters.

*'''-filterSimple'''
By default, all filtering is aggressive, matching much more than what is strictly listed in a '''-badwords''' file for convenience.Providing this option will make the '''-filterCallsigns''' and '''-filterChat''' comparisons exact match only.

*'''-g'''
Quit after serving one game.

*'''-groupdb''' ''file''
Load groups from file

*'''-h'''
Buildings are given random heights.

*'''-handicap'''
Players are given a handicap advantage based on their ability in relation to the other players. Handicapped players will have faster tanks and shots. The handicap is determined by the player's score in relation to other players.

*'''-help'''
Shows a help page and lists all the valid flag id's.

*'''-helpmsg''' ''file name''
Create a help message accessible by /help name, which prints the contents of file. Restricted to 10 lines per help message.

*'''-i''' ''interface''
Server will listen for and respond to ''pings'' (sent via broadcast) on the given interface. Clients use this to find active servers on the network. This is the TCP/UDP/IP address the server will listen on.

*'''-j'''
Allows jumping.

*'''-lagdrop''' ''warn-count''
Kicks players after warn-count lag warnings.

*'''-lagwarn''' ''time/ms''
Send warnings to players that lag more than time. A single value sets the total number of players allowed. Five comma separated values set the maximum for each team. If a count is left blank then no limit is set for that team, except for the limit on the total number of players. Both forms may be provided.

*'''-mps''' ''max-score''
Sets a maximum score for individual players. The first player to reach this score is declared the winner and the game is over.

*'''-ms ''shots''
Allows up to shots simultaneous shots for each player. This is 1 by default.

*'''-mts''' ''max-score''
Sets a maximum score for teams. The first team to reach this score is declared the winner and the game is over.

*'''-noMasterBanlist'''
Server will not attempt to load the [[Master Ban]] list from the internet.

*'''-p''' ''port''
Listen for game connections on port instead of the default port.Use '''-help''' to print the default port, or use '''-d''' debug printing.

*'''-passdb''' ''file''
Load passwords from file

*'''-passwd''' ''password''
Specify a server administrator password for use in remote administration such as /kick, /ban, /mute, etc messages.

*'''-pidfile''' ''filename''
Specify a file where the server will write its process ID so it may be used for remote administration.

*'''-poll''' ''variable=value''
Configure several aspects of the in-game polling system
{|
|
'''banTime'''
default number of minutes player should be banned (unspecified, the default is 300)
'''vetoTime'''
max seconds authorized user has to abort poll(default is 20)
'''votePercentage'''
percentage of players required to affirm a poll (unspecified, the default is 50.1%)
'''voteRepeatTime'''
minimum seconds required before a player may description. By default, a server will
respond to broadcast queries, allowing clients to find servers running on the
standard port on the local subnet.The '''-public''' option causes the server to register
itself with a list server, which clients can query to get a list of bzfs servers.
|}
*'''-publicaddr''' ''address[:port]''
Advertise this server with the given address and port. Only has an effect when used with '''-public'''. Normally a server advertises itself at the local address and port. Some servers are not accessible from the internet at this address (for example servers behind a firewall using Network Address Translation). Use this option to specify the address and/or port that internet users should use to access this server.

*'''-publiclist''' ''url''
Advertise this server on the list servers listed at url. Only has an effect when used with '''-public'''. A built-in url is used by default. The BZFlag clients use the same built-in url so, by default, clients will see public servers automatically. This argument may be provided multiple times to publicize a server to multiple list servers.

*'''-q'''
If specified, the server will not listen for nor respond to ``pings''. BZFlag sends out these pings to give the user a list of available servers.This effectively makes the server private, especially if the '''-p''' option is also used.

*'''+r'''
Makes most shots ricochet. Super bullets, shock waves, and guided missiles do not.

*'''-rabbit''' ''[score|killer|random]''
Enables the rabbit-hunt style game. By default, the free-for-all style is used. You must specify the algorithm used to pick a new rabbit when the old one dies. The score algorithm uses a modified wins/(wins+losses) score and picks the top scoring player to be the new rabbit. The killer algorithm specifies a reverse tag game where whomever kills the rabbit becomes the new rabbit. The random algorithm randomly picks a new rabbit without regard to score. (The score algorithm is the original behavior.)

*'''-recbuf''' ''size''
Start with the recording buffer active, with the specified size (in megabytes).

*'''-recbufonly'''
Disable recording straight to files

*'''-reportfile'''

*'''-requireudp'''
Require clients to use parallel UDP. If players fire before opening a UDP channel, kick them off the server.

*'''+s''' ''num-flags''
The server will have an extra num-flags random super flags available at all times. The '''-f''' option can be used to restrict which types of flags will be added. Required flags given by the '''+f''' option are not included in the num-flags total.

*'''-s''' ''num-flags''
The server will have up to num-flags random super flags available at any time.The '''-f''' option can be used to restrict which types of flags will be added. Required flags given by the '''+f''' option are not included in the ''num-flags'' total.

*'''-sa'''
Antidote flags are provided for players with bad flags.

*'''-sb'''
Allow spawns on box buildings.

*'''-set''' ''name value''
Set BZDB variable name to value

*'''-sl''' ''id num''
Restrict flag id to num shots.

*'''-spamtime''' ''time''
Minimum ''time'' between player chat messages that are alike.

*'''-spamwarn''' ''warnLimit''
Number of warnings a player/spammer gets, who violates '''-spamtime'''.

*'''-speedtol''' ''factor''
Override the default speed auto kick factor. The factor should not be less then 1.0. The factor is a multiplier.

*'''-srvmsg''' ''message''
Define a server welcome message. This option can be used multiple times to define a multiline message.

*'''-st''' ''time''
Bad flags are automatically dropped after time seconds.

*'''-sw''' ''count''
Bad flags are automatically dropped after count wins. Capturing a team flag does not count as a win.

*'''-synctime'''
Forces all clients to use the same time of day.T he current time is determined by the server's clock. This disables the + and - keys on the clients.

*'''-t'''
Adds teleporters to the game.

*'''-timemanual'''
The countdown has to be started manually using the /countdown command. This is useful for matches.

*'''-tk'''
Changes the default behavior where a player dies when he kills a teammate. When using this option, he will just get a -1 score penalty for the kill but not be killed in game.

*'''-tkannounce'''
Announces team kills to the admin channel

*'''-tkkr''' ''percent''
Kicks players whose team killing to normal kill ratio is greater than percent [1-100]. A start up grace period is given to players.

*'''-ts''' ''[micros]''
Include timestamp information in DEBUG output useful for logging. If micros is specified, microseconds will be added to the timestamp.

*'''-userdb''' ''file''
Load group associations from file

*'''-vars''' ''file''
Loads values for game configurable variables from file. Entries are one per line in the form: set variable value. For a list of variables that are configurable, in the BZFlag client, send a message with /set as the text.

*'''-version'''
Prints the version number of the executable.

*'''-world''' ''world-file''
Reads a specific BZFlag .bzw world file in [[BZW]] format as the game map.

*'''-worldsize''' ''world-size''
Changes the size for random maps

==See also==
[[BZW|BZW world format]]

[[Category:Server]]

Talk:Mesh

2007-03-19T21:10:58Z

TD-Linux: drawInfo?

Does anyone have experience on using drawInfo? I would like to add information, but I can't seem to figure out how it works myself. [[User:TD-Linux|TD-Linux]] 17:10, 19 March 2007 (EDT)

Template:Inaccurate

2007-03-19T01:46:06Z

TD-Linux: Made sound a bit better

{|style="width:100%;margin-top:+.7em;background-color:#fcfcfc;border:1px solid #ccc;"
|[[Image:MessedUp.png]]
||''This page contains blatant errors, wild inaccuracies, and/or unclear text. Please discuss these errors on the [[Help:Talk page|talk page]] or fix them yourself.''

''Look out for flying tanks.''
|}
<includeonly>[[Category:Inaccurate]]</includeonly>

Logging

2007-03-19T01:45:18Z

TD-Linux: Hmm, I think we need some new templates... none seem to fit well.

{{Inaccurate}}
= INTRO =

learner is in the process of adding a logging framework that will unify logging across all of the bzflag binaries. This raises the need for some discussion and agreement on default logging message types, logging categories, default formats for those messages and categories, and how logging is to be specified in general. This file intends to serve as a RFC as well as a draft specification for what will get implemented. You are welcome to make contributions but please denote your changes with your irc name, if you would. Write in plain english (even if broken) and try to be clear.. :)

'''Quick Overview:'''

We are logging MESSAGES. Those MESSAGES are comprised of %atoms. %atoms may be comprised of other %atoms.

MESSAGES may be grouped into categories_of_messages. categories_of_messages may be comprised of other_categories_of_messages.

'''Example:'''

CHAT => "%timestamp %player: %message" example: "2004-11-05T08:15:30-05:00 chestal: guten tag"

TEAM_CHAT => "%timestamp [TEAM] %player (%team): %message" example: "2004-11-05T00:15:39+05:00 [TEAM] bzg (green): hello"

public_messages => CHAT TEAM_CHAT

chat_messages => public_messages ADMIN_CHAT PRIVATE_CHAT

'''Slightly Longer Overview:'''

Logging is comprised of messages of various types such as notification that a player fired a shot, that someone picked up a flag, that someone joined the server, that a network packet was lost, and much more. Each log message type is denoted below in uppercase (e.g. ADMIN_CHAT) and contains various identifiable components like player names, time stamps, shot IDs, and more. These identifiable components are called message 'atoms' and are designated with a % prefix optionally wrapped in curly braces (e.g. %timestamp, %{flag}, %player). Atoms themselves may be comprised of other atoms (e.g. %timestamp might be a combination of "%year %month %day %hour:%minute:%second") -- and yes, someone has already mentioned they should probably be called molecules but stick with the metaphor -- they are still succint message units from a formatting perspective. ;-) Finally and additionally, the various messages may be grouped together according to various categories like chatting, player actions, networking, and more. Message groups are designated by a underscore-separated lowercase word (e.g. chat_messages and debug_messages) and like atoms, you may have groups that are comprised of other groups (and messages that belong to multiple groups).

This specification intends to describe the types of messages, a default grouping of the various categories, and a list of all the message atoms possible. It should also suggest the user-interface for how the logging format is to be specified (user menus, command line options, etc).

----

= NEEDS =

The basic needs that are considered useful (even if already implemented in some fashion) are as follows:

1. server logging
2. client chat logging
3. debug logging for developers
4. ability to have separate logs for separate categories of messages
5. multi-server logs
6. time-stamping
7. multiple message types with specified formats
8.

= MESSAGE TYPES =

There are a variety of default logging categories that can be grouped a variety of ways. Some of the major groups of messages are separated out below. At a fundamental level, though, they are simply all just individual message types:

== Chat (chat_messages) ==

=== public chat (CHAT) ===
This is a message sent to all players from some player

=== private chat (PRIVATE_CHAT) ===
This is a message sent to a specific player from some player

=== team chat (TEAM_CHAT) ===
This is a message sent to a specific team from some player

=== admin chat (ADMIN_CHAT) ===
This is a message sent from a specific player to all players in the ADMIN group or that have the adminMessages permission.

== Player Actions (action_messages) ==

=== Firing a weapon action (firing_messages) ===

==== firing a bullet (SHOOT) ====
==== firing a guided missile (SHOT_GM) ====
==== firing a laser (SHOT_L) ====
==== firing a shock wave (SHOT_SW) ====
... lot more ...

* Why the difference in tense (shoot/shot) between normal bullets and flags? --DTRemenak

=== Picking up or dropping Flags (flag_message) ===

==== laser (L) ====
==== guided missle (GM) ====
==== shock wave (SW) ====
... lot more ...

== Developer/Debug (debug_messages) ==

=== informational (INFO) ===
Something informative that is not a trace

=== trace (TRACE) ===
A message that tells you about run-time values or where the current execution is in the code.

=== warning (WARN) ===
Caution about some event or status that has occured.

=== error (ERROR) ===
A fatal or catastrophic exception (that will generally abort the application).

* I'd like to see the ability to have "debug channels" like wine does...e.g. so I could enable just network debug logging when working on net stuff (and leave it turned off when working on other stuff), or just whatever else is relevant. --DTRemenak

= DEFAULT MESSAGE GROUPS =
== chat_messages => CHAT, PRIVATE_CHAT, TEAM_CHAT, ADMIN_CHAT ==
== debug_messages => INFO, TRACE, WARN, ERROR ==
== firing_messages => SHOOT, SHOT_GM, SHOT_L, SHOT_SW ==
== flag_messages => L, GM, SW ==
== action_messages => firing_messages, flag_messages ==

= MESSAGE ATOMS =

Message atoms are the individual components of a log that you might want to specify individually somehow. See the list for ideas of what that means. The list includes some atoms that are basically combinations of other atoms too (like ISO date/time format).

== logging goo ==
1. message type (%level)
2. ip address (%ip)
3. resolved domain name (%dn)

== time-related ==
1. 4 digit year (%year)
2. numeric month (%month)
3. month name (%Month)
4. numeric day (%day)
5. day of week name (%Day)
6. calendar date (%ymd => %year %month %day)
7. time (%hour %minute %second %subsecond %timezone %utc_offset)
8. ISO date/time (%timestamp => %year-%month-%{day}T%hour:%minute:%second.%subsecond%utc_offset)
9. UNIX timestamp (%date => %Day %Month %day %hour:%minute:%second %timezone %year)

== chat-related ==
1. sending player
2. recipient player
3. recipient group (team/all)
4. chat message
5. logging of the private/team/admin recipients with the message

== flag-related ==
1. flag type
2. flag actions (grabbed/dropped/captured/reset/removed)

== player-related ==
1. callsign
2. email address
3. player type (human/robot/observer)
4. team
5. player actions (connected/quit/kicked/banned/died/spawned)

== map-related ==
1. position
2. obstacle type
3. size/dimension

= SPECIFYING LOGS =

How server operators and players specify logging should be as simple yet potentially flexible as possible, of course. Players and server ops definately have rather different logging needs, and I (learner) suggest that both client and server have the same mechanism on the command line, yet the client should also have an in-game menu for configuring logging on a basic level.

== In-Game Menu ==

Since there will still be the command-line interface for rather complicated logging configurations, the in-game menu for logging should be as simple as possible. I (learner) would propose that there basically be a field to specify a directory (perhaps default to ~/.bzf), and then a variety of checkboxes for what to enable-disable. The menu could include the following components:

=== input field for a logging directory ===
=== option for logging in one file, separate by server/join, or separate by type ===
=== checkbox for logging to the console ===
=== checkbox for logging everything (toggling it on would enable all below) ===
==== checkbox for join/quit notifications ====
==== checkbox for flag events (captures, pickups, and drops) ====
==== checkbox for kills ====
==== checkbox for pause/nr ====
==== checkbox for logging all chat (toggling on enables all chat types) ====
===== checkbox for public chat =====
===== checkbox for private chat =====
===== checkbox for team/group (would include admin) chat =====
===== checkbox for server chat =====

== Command-line Interface ==

Maybe something like:

=== --logFormat CHAT "%timestamp %user: %message" ===
=== --logGroup chat_messages CHAT,PRIVATE_CHAT,ADMIN_CHAT,TEAM_CHAT ===
=== --log chat_messages /var/log/chat.log ===
=== --log server_messages syslog,local3.info ===
=== --log debug_messages stdout ===

[[Category:Development]]

Talk:Logging

2007-03-19T01:43:34Z

TD-Linux: ?!?

== LogDetail ==
Is this a good page for information about the logDetail plugin? -- [[User:CannonBallGuy|CannonBallGuy]] 16:27, 19 February 2007 (EST)
:How about [[LogDetail]]? ;) Well, it might be good to mention it. This page is really messed up right now and unclear, so I'm adding the Inaccurate thingy to the top. Old might also be appropriate. [[User:TD-Linux|TD-Linux]] 21:43, 18 March 2007 (EDT)

Spawning

2007-03-19T01:39:06Z

TD-Linux: General outline, not really a stub because there isn't much to see ;)

Spawning is the act of your [[Tank|tank]] reappearing. This can be caused by two events:
*Joining a server allows you to spawn immediately.
*After dying, a delay takes place, after which you may spawn.

Spawn locations are determined by the server, thus they may be modified by plugins such as [[Airspawn]].

Material

2007-03-19T01:32:19Z

TD-Linux: Fixed meshbox link

A material is used in a BZFlag world to define a new look for otherwise regular objects, such as [[Meshbox|meshboxes]].

==Code==
To put a material in your map, first it must be defined:
{|
|
material
name example_material
texture filename # set the texture (don't use PNG extension)
addtexture filename # add a texture (again, no PNG extension)
notextures # don't use textures.
notexcolor # don't apply the color to the texture
notexalpha # don't use the texture's alpha channel
texmat -1 # specify a texture matrix. -1 for no texture matrix.
dyncol -1 # specify a dynamic color. -1 for no dynamic color.
ambient 0.0 0.0 0.0 1.0 # ambient color
diffuse 1.0 1.0 1.0 1.0 # diffuse (main) color
color 1.0 1.0 1.0 1.0 # synonym for diffuse
specular 0.0 0.0 0.0 1.0 # specular color
emission 0.0 0.0 0.0 1.0 # emission color
shininess 0.0 # shiny!
resetmat # restore default values
end
|}

To actually apply a texture, you must use some sort of reference in an object, like so:
{|
|
meshbox
position 0 0 10
rotation 0
size 10 10 5
matref example_material
end
|}

==History==
Materials were added in [[BZFlag 2.0.0]].

==Editor Support==
Materials are supported in [[Blender]] with [[BZWTools]], [[pyBZEdit]], and [[Wings3D]] with the [[BZW Exporter for Wings3D]]. Materials are NOT supported in [[BZEdit]] or [[BZFed]].

[[category:Map_Objects]]
[[category:Map Making]]

Talk:Ideas

2007-03-19T01:29:48Z

TD-Linux: color-coding?

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

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

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

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

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

Template:Old

2007-03-18T18:03:43Z

TD-Linux: Changed picture to something more old

{|style="width:100%;margin-top:+.7em;background-color:#fcfcfc;border:1px solid #ccc;"
|[[Image:BZFlag-1.7d9_thumb.jpg]]
||''This page has facts that are stale, obsolete, or grossly outdated. Please update this page with newer information.''
|}
<includeonly>[[Category:Old]]</includeonly>

File:BZFlag-1.7d9 thumb.jpg

2007-03-18T18:00:19Z

TD-Linux: Really old bzflag, courtesy Lan.

Really old bzflag, courtesy Lan.

Talk:2.4 Releases

2007-03-17T22:43:04Z

TD-Linux: comments

They should not be merged, not all versions are released. Releases are just versions that have been published. CVS is not a version. They do link to the same pages, but it's just a list.
JeffM.
:Okay, so Releases really should just be a subcategory of versions. Also, remember the venerable <nowiki>~~~~</nowiki>. [[User:TD-Linux|TD-Linux]] 18:43, 17 March 2007 (EDT)

2.4 Releases

2007-03-15T21:14:16Z

TD-Linux: changed merge box

{{mergeto|Versions}}
Pages related to various releases of BZFlag.

== Articles in category "Releases" ==
There are currently 32 releases of BZFlag, starting with the earliest.

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

[[Category:History]]

Versions

2007-03-15T21:13:36Z

TD-Linux: change merge tag

{{mergefrom|Releases}}
Pages related to various versions of BZFlag.

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

The versions in chronological order are;

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

[[Category:History]]

Strong Authentication

2007-03-14T00:45:03Z

TD-Linux: removed unnecessary tables; ws

To use strong auhentication on bzflag an infrastructure based on kerberos should be put in place.

kdc: is the kerberos Key Distribution Center, part of the mit-kerberos5 distribution. It should be unique, possibly with a slave configured, and for bzflag to work it should be configured to serve the realm BZFLAG.ORG . Your system needs to know where KDC is.
So you should write a /etc/krb5.conf on Unix or krb5.ini on windows, with the following content:

[realms]
BZFLAG.ORG = {
kdc = bryjen.bzflag.org
admin_server = bryen.bzflag.org
}

This is temporary and will be changed whenever we decide on where to put it.

On the kerberos database should be created one principal (kerberos user) for any client and one principal for any server that should participate.

* Server principal name should be #port/publicaddr@BZFLAG.ORG (like 5154/bzflag0.gamesunited.de@BZFLAG.ORG)
* Client principal name should be clientName@BZFLAG.ORG (like c3po@BZFLAG.ORG)

When starting a public server it will try to authenticate using the value given in -port -publicaddr and -password

When starting a client, it will authenticate to the server if the bzdb variable: username & password are defined (in the bzfs config file). So write the following lines on your config:

set username yourName

set password yourSecret

If credentials are unmatched, you will be still logged as an untrusted user.

[[Category:Development]]

Talk:Ideas

2007-03-13T22:10:36Z

TD-Linux: ?

Should ideas that have already be implemented be deleted? This list is getting kinda long.

Main Page

2007-03-13T22:02:59Z

TD-Linux: Added 'Things To Do' for bored wikiholics

[[Image:BZflag_2_0_8_Banner.png|center]]
{|style="width:100%;margin-top:+.7em;background-color:#fcfcfc;border:1px solid #ccc"
|style="width:56%;color:#000"|
{|style="width:280px;border:solid 0px;background:none"
|-
|style="width:280px;text-align:center;white-space:nowrap;color:#000" |
[[Image:Bzflag-48x48.png|left]]
<div style="font-size:162%;border:none;margin: 0;padding:.1em;color:#000">Welcome to the BZFlag Wiki,</div>
<div style="top:+0.2em;font-size: 95%">The source for community information on most things related to BZFlag!</div>
<div id="articlecount" style="width:100%;text-align:center;font-size:85%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] articles available</div>
|}
|style="width:15%;font-size:95%"|
[[Image:Bzflag-48x48.png|right]]
*[http://my.bzflag.org/bb The Forums]
*[http://my.bzflag.org BZFlag Stats]
*[http://sourceforge.net/projects/bzflag/ BZFlag on SourceForge]

|}
Welcome to the newly launched BZFlag Wiki. Currently there are not many articles, but with everyone's help the volume should grow quickly. The hope of this site is to draw together all of the great information about BZFlag and BZFlag related items that is currently scattered in many different places. Bringing all of this information together will make it easier for people to understand and answer all of the questions they have about running a server (options, permissions, set-up, etc.), configuring their client, coding plug-ins, compiling the source code, and anything else they can think of. All are welcome to contribute and may edit most pages. With everyone's help we can make this site a great resource to the BZFlag community.

==Google Summer of Code 2007==
If accepted as a mentoring organization, BZFlag intends to participate in the [http://code.google.com/soc/ Google Summer of Code] this year. What this basically amounts to is that if you are a full-time student and 18+ years old, and your application is accepted, Google will pay you to write code for BZFlag. Prospective students are encouraged to submit project proposals that are in line with our '''[[Google Summer of Code|goals]]''' for this summer, though proposals for other [[Ideas]] will be considered.

==General Information==
[[Getting Help]]

==Areas of Interest==
*[[:Category:Client|Client]]
*[[:Category:Compiling|Compiling]]
*[[:Category:Concepts|Concepts]]
*[[:Category:Development|Development]]
*[[:Category:Gameplay|Gameplay]]
*[[:Category:Installing|Installing]]
*[[:Category:Map Making|Map Making]]
*[[:Category:Maps|Maps]]
*[[:Category:Plug-Ins|Plug-ins]]
*[[Releases]]
*[[:Category:Server|Server]]
*[[:Category:Support|Support]]
*[[:Category:Tactics|Tactics]]
*[[Versions]]

==Things To Do==
*[[:Category:Stubs]]
*[[:Category:Old]]
*[[:Category:Inaccruate]]
*[[:Category:Pending Deletions]]

Ideas

2007-03-13T21:54:46Z

TD-Linux: Old...

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

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

''Is this text below still valid?'' [[User:TD-Linux|TD-Linux]] 17:41, 12 March 2007 (EDT)<br>
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.

Status may include personal comments by developers.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Idea from morfie
* Add ice as a terrain feature

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[[Category:Development]]