BZFlagWiki - User contributions [en]

Recordmatch

2009-05-25T04:01:27Z

TangenT: Alright, for real, I'm fixing things. This should look pretty good now.

Recordmatch is a standard [[Plug-ins|plug-in]] that is shipped with the [[BZFlag Source|source code]]. It allows for match games, such as league matches, to be recorded onto the server to be replayed later. It will automatically record when a game (match) is started, and it will record with a filename given by the current date and time. Recordmatch is included in [[BZFlag 2.0.6|v2.0.6]] and later releases.

==Usage==
When the recordmatch plugin is loaded, it waits for a match game to be started. When a game is started, it will create a new file to store the recording, named with the current date and time. When the game is ended, it will stop recording and close the file. The usage is (for Windows and Unix-based systems, respectively):

-loadplugin "X:\path\to\the\plugin\recordmatch.dll"
-loadplugin "/path/to/the/plugin/recordmatch"

or in an already running game (for Windows and Unix-based systems, respectively):

/loadplugin "X:\path\to\the\plugin\record.dll"
/loadplugin "/path/to/the/plugin/recordmatch"

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

==History==
The BZFS API was changed in the development of [[BZFlag 2.0.6|v2.0.6]] to allow for recordings to be started. Recordmatch is the first plugin to use the newly-added capability.

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

Recordmatch

2009-05-25T03:56:14Z

TangenT: Cleaning up this mess... let's use correct information and formatting, shall we?

Recordmatch is a standard [[Plug-ins|plug-in]] that is shipped with the [[BZFlag Source|source code]]. It allows for match games, such as league matches, to be recorded onto the server to be replayed later. It will automatically record when a game (match) is started, and it will record with a filename given by the current date and time. Recordmatch is included in [[BZFlag 2.0.6|v2.0.6]] and later releases.

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

-loadplugin "X:\path\to\the\plugin\recordmatch.dll"
-loadplugin "/path/to/the/plugin/recordmatch.so"

or in an already running game (for Windows and *Nix, respectively):

/loadplugin "X:\path\to\the\plugin\record.dll"
/loadplugin "/path/to/the/plugin/recordmatch.so"

Examples:

-loadplugin "C:\Program Files\BZFlag2.0.8\recordmatch.dll"
-loadplugin "/usr/local/bzflag2.0.8/plugins/recordmatch.so"

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

==History==
The BZFS API was changed in the development of 2.0.6 to allow for recordings to be started. Recordmatch is the first plugin to use the newly-added capability.

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

User:TangenT

2007-07-05T04:13:57Z

TangenT: Let's be an annoying trend follower, shall we?

Hi, I'm TangenT (aka Hyper, or eTangenT). I have been playing BZFlag since early 2006, and in that time, I have made a few maps and run a few servers.

My very first map was TangenT's Playground (bad name? of course.), which consisted of some X structures and some pyramids. It was basic, but fun for testing. I later added two small towers for launching GM, and I also made a CTF version that featured two (excessively) tall towers (with tunnels!) that led up to the team bases. Other additions include a Laser Show every couple minutes, some random Genocide bullets flying around, and the occasional World Weapon Shockwave.

This first map led to my first server group, called Null BZFlag (later shortened to NullBZ). I initially ran the Playground fulltime, but then I created a maze map with no radar (and no real name, either!), and begun a rotation on NullBZ. Later, I created another Maze map, and also, I created the Village map (there were a bunch of hut-looking things). I moved the mazes to their own rotation.

However, with no-radar maps dying in popularity, I felt it was better to remove the maze rotation, and in its place, I put up a 2-Team CTF rotation, and a 4-team CTF rotation.

Now my servers are currently down, but in the meantime, other maps have been completed, including Bridges, a battle over water, and Aquatic Dispute (Atlantis?), which is a map above AND inside water (if you can find it, and it's on the BZFlag forums, you should check it out).

Of course, being that NullBZ is now out of existance (I think), I am working with Constitution on a new project, one of the biggest things BZFlag will ever see. It's still in progress, but if you know where to look, you can find our progress.

Talk:Main Page

2007-06-12T16:41:08Z

TangenT: spam removal.

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

----

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

----

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

----

== Flag Ideas needs some responses, ==

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

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

Category:Support

2007-06-12T07:05:27Z

TangenT: Spam.

Help:Contents

2007-06-10T17:17:09Z

TangenT: Remove Spam (Why is there so much of this?)

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

[[Category:Help| ]]

AHOD

2007-06-10T17:14:24Z

TangenT: Remove Spam

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

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

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

Sphere

2007-06-05T00:24:02Z

TangenT: Create a page for the sphere object! (that's very important!)

The sphere is a [[BZW]] Object that defines a sphere in the game arena.

==Code==
The code to place a sphere in your map is as follows:
{|
|
sphere
name example_sphere
divisions 4
flatshading
position 0 0 10
size 10 10 10
radius 10
rotation 0
shift 0 0 0
scale 0 0 0
shear 0 0 0
spin angle nx ny nz
phydrv example_phydrv
smoothbounce
matref example_material
end
|}
Valid properites for a [[sphere]] are
<properties>
name=defines the name of the sphere, it is not required, and often unused
divisions=defines the number of subdivisions (pieces) of the sphere
flatshading=enables flat shading, smooth shading is the default
position=defines the center point of the sphere
size=defines the size of the sphere
radius=sets all size values to the same value
rotation=defines rotation for the sphere
shift=shifts the sphere (repeatable)
scale=scales the sphere (repeatable)
shear=shears the sphere (repeatable)
spin=spins the sphere around vector n (repeatable)
phydrv=attaches a physics driver to the sphere
smoothbounce=makes ricochets use normals
matref=defines a material for the sphere to use
</properties>

==Appearance==
By default, the sphere is a perfect sphere, with a red brick texture around the outside. You can, however, make the sphere elongated on one side (just don't use the radius option).

==History==
The sphere object has been supported since [[BZFlag 2.0.0]]. In previous versions of BZFlag, this object will not work.

==Editor Support==
Editors that support the sphere object include [[Blender]] using the [[BZWTools]], [[Wings3D]] using the [[BZW Exporter for Wings3D]], and [[pyBZEdit]]. [[BZEdit]] and [[BZFed]] do NOT support the sphere.

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

Link

2007-06-04T23:59:15Z

TangenT: Put this in a category so people can find it.

A Link is a BZW object which creates a link (route) between two [[Teleporter|teleporters]].

Links go in hand with [[Teleporter|teleporters]].
{|
|
==Code==
link
name example_link
from *
to *
end
|}
Valid parameters for a link are:

*'''from''': From what [[Teleporter|teleporters]]
*'''to''': To what [[Teleporter|teleporters]]

In either of the from/to parameters, "*" or "?" can be used to make multiple matches. To specify which side of the teleporter you are linking you can use the ":f" (forward) or ":b" (backward) after the name of the teleporter. Ex: tele:f

==History==

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

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

Zone

2007-05-16T13:23:25Z

TangenT: /* History */ - Added.

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
<properties>
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).
</properties>

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

==History==
Zones were added to BZFlag in version 2.0.0.

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

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

Slash Commands

2007-03-20T05:12:34Z

TangenT: Changed a flag command to show the correct command.

Below is a list of the commands that are available in BZFlag. Access to most of these commands is controlled through [[Server_Permissions|permissions]].

All commands are preceded by a '/' on any chat prompt.
The format for commands that take arguments are provided by the server by issuing the command with no arguments. (ie. `/ban`)

'''Some commands take no arguments''' (eg. ''/shutdownserver'', ''/superkill'') '''and therefore''' do not return the format string for the command but '''execute the command instead.'''

{|{{Prettytable}}
|-
| {{Hl3}} |'''Command'''
| {{Hl3}} |'''Description'''
|-
| ''/?'' || List commands
|-
| ''/ban'' || Ban players using the specified IPs of the player specified for certain length of time from using this server.
|-
| ''/banlist'' || List all of the IPs currently banned from this server. Items from the master ban list on my.bzflag.org/bb have an '(m)' after the IP for masterban. If an argument is specified only bans that match the argument are displayed.
|-
| ''/checkip'' || Check if a specified IP is banned or not and report the results.
|-
| ''/clientquery'' || Retrieve client version info from all users, or just CALLSIGN if given
|-
| ''/countdown'' || Starts the countdown sequence for a timed game. The countdown sequence length can optionally be specified in seconds.
|-
| ''/date'' || Responds with the current server local date and time (same as /time).
|-
| ''/deregister'' || With an argument, it deregisters another user's callsign . Without, it removes your own registration. (only affects local registration)
|-
| ''/endgame'' || Ends the current game
|-
| ''/flag reset'' || Repositions flags. If unused is specified, flags carried by tanks are not affected.
|-
| ''/flag up'' || Removes all flags from the game
|-
| ''/flag show'' || Shows all flags with information.
|-
| ''/flag give'' || Give the specified flag to the specified player. This command spawns the flag directly above the play, so if they are moving the flag will fall on the ground near them. If the flag is not available, it will take a flag from the person who has the flag specified. You cannot give flags that do not exist on the map.
|-
| ''/flag take'' || Will take the flag that the player specified is currently carrying.
|-
| ''/flaghistory'' || Lists what flags players have grabbed in the past.
|-
| ''/gameover'' || Ends a timed game.
|-
| ''/ghost'' || Kicks off an impersonating player or ghost
|-
| ''/grouplist'' || Lists the available user groups
|-
| ''/groupperms'' || Lists the permissions for each group
|-
| ''/help'' || With no argument it displays a lists the help files available. With the argument it displays the contents of the help file.
|-
| ''/hostban'' || Ban players using the specified hostnames for a certain length of time from using this server.
|-
| ''/hostbanlist'' || List all of the host patterns currently banned from this server.
|-
| ''/hostunban'' || Will remove the the specified host from the ban list so that players from that host will be able to blay again.
|-
| ''/idban'' || Ban a player by bzbb id. This will stick even if the player ip changes.
|-
| ''/idbanlist'' || List all bans made with ''/idban''
|-
| ''/identify'' || Log in to a registered callsign
|-
| ''/idlestats'' || Displays the idle time in seconds for each player. A player is idle when he is dead and has not respawned yet.
|-
| ''/idlist'' || Will list the currently banned IDs
|-
| ''/idunban'' || Will remove the ban on the ID specified so that the player may play on the server again.
|-
| ''/kick'' || Kick a named player off the server.
|-
| ''/kill'' || Kill a player (they explode)
|-
| ''/lagdrop'' || With no argument it displays current lagdrop setting, with argument it sets it to the value specified. This specifies the number of warnings a player gets due to high lag before the server kicks the players.
|-
| ''/lagstats'' || Lists network delays, jitter and number of lost (out of order packets) by player.
|-
| ''/lagwarn'' || With no argument it displays current lagwarn setting, with argument it sets it to the value specified. If a players lag is higher that the setting they will be warned, then kicked.
|-
| ''/localset'' || Set local client variables in your configuration file.
|-
| ''/masterban'' || Manipulate the master ban list.
|-
| ''/me'' || This command displays an "action" that is conveyed to another player. It allows for a little more expressivity in the game. For example: "/me is hunting wabbits" turns into a message like "Thumper is hunting wabbits" that gets displayed differently to other players.
|-
| ''/msg'' || This command allows a player to send a message to another player. Similar to using the "," and "." message keys in the game and then selecting your recipient, this will send some message to particular player.
|-
| ''/mute'' || Allows a server admin to remove the ability for a player to communicate with other players. Once muted the player may only talk to admins on the server. This command removes the TALK permission for that user.
|-
| ''/part'' || Leave the server with a goodbye message (same as /quit).
|-
| ''/password'' || Attempt to gain administrator. The passwords are random and regenerated every time the server starts making this command nearly useless on norang.ca servers.
|-
| ''/playerlist'' || List player names and IP addresses.
|-
| ''/poll'' || Start a player poll
|-
| ''/quit'' || Leave the server with a goodbye message (same as /part).
|-
| ''/record'' || List all files in the recordings directory
|-
| ''/record start'' || Starts recording
|-
| ''/record stop'' || Stops recording
|-
| ''/record size'' || Specify size of recording buffer in megabytes (MB)
|-
| ''/record rate'' || Specify recording rate in seconds
|-
| ''/record stats'' || Display statistics of recording
|-
| ''/record file'' || Specify a filename for recording instead of using memory
|-
| ''/record save'' || Save an in-memory recording buffer to a file
|-
| ''/register'' || Register your current callsign locally to the specified password. Passwords must be at least 3 characters long, and the callsign may not contain quotes or other non-alphanumeric/space characters. We use global logons and this is not needed.
|-
| ''/reload'' || Reloads the user, group, and password files (for synchronization between multiple servers on the same machine)
|-
| ''/removegroup'' || Remove a user from a group
|-
| ''/replay list'' || List recording files that can be replayed
|-
| ''/replay load'' || Load a recording file for play
|-
| ''/replay play'' || Start playback of the loaded recording
|-
| ''/replay skip'' || Skip forwards or backwards through the recording
|-
| ''/report'' || Write a message to the server administrator
|-
| ''/reset'' || Reset a server variable to it's bzfs default setting.
|-
| ''/say'' || Generate a public message sent by the server. For example "/say This is a server message", will display ''[SERVER:] This is a server message (Thumper)''
|-
| ''/sendhelp'' || Send a help file to a player
|-
| ''/serverquery'' || Report the server version number
|-
| ''/set'' || With no arguments it will list the values of all server variables. With the arguments it will set the variable that is specified to the value that is given.
|-
| ''/setgroup'' || Add a user to a group
|-
| ''/setpass'' || Changes your password (for locally registered users, not globally)
|-
| ''/showgroup'' || Lists the groups that a registered user is a member of
|-
| ''/showperms'' || Show permissions granted to yourself or another player
|-
| ''/shutdownserver'' || Stop serving BZFlag on this server.
|-
| ''/superkill'' || Kick all players off the server.
|-
| ''/time'' || Responds with the current server local date and time (same as /date).
|-
| ''/unban'' || Will remove the IP adress from the banlist, allowing someone from that address to conncet and play BZFlag.
|-
| ''/unmute'' || Allows a server admin to restore the TALK permission to a previously muted player.
|-
| ''/uptime'' || Prints server's current running time in days, hours, mins and secs.
|-
| ''/veto'' || If there is a poll active, this will cancel the poll.
|-
| ''/viewreports'' || View the server's report file.
|-
| ''/vote'' || If there is a poll active, this command will place a vote in favor or in opposition to the poll. Multiple languages are supported as a vote argument in addition to "yes" and "no". By default, you must be registered to vote on a poll.
|}

[[Category:Server]]
[[Category:Client]]

BZFS Command Line Options

2007-03-20T04:27:12Z

TangenT: /* The Options */ Edited reportfile, added reportpipe.

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

*'''-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-03-19T00:40:00Z

TangenT: Added History, added categories, put in some misc. information.

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.

==Code==
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
*'''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.

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.

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

Arc

2007-03-19T00:22:17Z

TangenT: /* Code */ Typo fix.

The arc object is a [[BZW]] object that defines an arc or cylinder in the game arena.

==Code==
To place an arc into your map file, the following template is suggested:
{|
|
arc
name example_arc
divisions 16
flatshading
angle 360
ratio 1
position 0 0 0
rotation 0
size 10 10 10
shift 0 0 0
shear 0 0 0
scale 1 1 1
spin angle nx ny nz
phydrv physics_driver_name
smoothbounce
matref material
end
|}
Valid parameters for an [[arc]] are
*'''name'''; defines the name of arc, often unused
*'''divisions'''; defines the number of subdivisions in the arc
*'''flatshading'''; defines the use of flat shading, smooth is the default
*'''angle'''; defines the sweep of the arc, 360 indicates a full circle
*'''ratio'''; defines the ratio to make a hollow arc, the parameter is (outrad - inrad) / outrad.
*'''position'''; defines the position of the arc in X-pos, Y-pos and the height of the arc in Z.
*'''rotation'''; defines a rotation around the Z axis for the arc, in degrees.
*'''size'''; defines the distance from the center to the side of the arc in X and Y, and the total height of the arc in Z.
*'''shift'''; shift the arc (repeatable)
*'''shear'''; (repeatable)
*'''scale'''; defines the scale of the arc in x,y, and z, 1 is the default, lower values make it smaller (repeatable)
*'''spin angle'''; rotate the arc around a vector by angle. ONE of nx, ny, and nz should be 1, the others should be 0. (repeatable)
*'''phydrv'''; reference to a predefined [[physics|physics driver]].
*'''smoothbounce'''; defines that shot bounces use normals
*'''matref'''; reference to a predefined [[material]].

==Appearance==
The arc, by default, has the red brick wall texture on the sides, and the grey roofs of normal boxes on the top. However, using [[matref]], one can change the appearance of the arc.

==History==
The arc object has been supported since [[BZFlag 2.0.0]]. In previous versions of BZFlag, this object will not work.

==Editor Support==
Editors that support the arc object include [[Blender]] using the [[BZWTools]], [[Wings3D]] using the [[BZW Exporter for Wings3D]], and [[pyBZEdit]]. [[BZEdit]] and [[BZFed]] do NOT support the arcs.

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

Define

2007-03-18T20:19:08Z

TangenT: /* Code */

Group Definition, or define, will group a set of objects that can be recalled and duplicated multiple times with the [[group]] object.

Define goes hand-in-hand with the [[group]] object.

== Code ==
{|
|
define my_group

# You can put the following objects in a group definition:
# box
# pyramid
# base
# mesh
# meshbox
# meshpyr
# arc
# sphere
# tetrahedron
# teleporter

enddef
|-
|
#You can then recall the group with

group my_group
shift 0 0 0
rotation 0
end
|}
A more detailed description of the group installation can be found [[group|here]].

== Editor Support ==
There are currently no supported editors: group definitions are normally most useful when editing by hand.

==History==
The group definition object was added with the [[BZFlag 2.0.0|v2.0.0]] release of BZFlag.

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

Meshbox

2007-03-18T18:24:34Z

TangenT: /* History */

The meshbox is the 2.0 update to the original [[box]] object in BZFlag 1.0. The main difference between the [[box]] and the Meshbox is that the meshbox supports new features in BZFlag 2.0, such as physics drivers and textures.

==Code==
A very basic meshbox will include:
{|
|
meshbox
position 0 0 0 # x-pos, y-pos, height
rotation 0 # rotation in degrees
size 10 10 10 # x-len, y-len, height
end
|}

As with the [[box]] object, position defines where the meshbox should be located. Rotation defines the angle it should be rotated to (about the Z-axis), and size defines how big or small the object should be. Now, if you're looking for something a little fancier, you can try code similar to this:

{|
|
meshbox
position 0 0 0
rotation 0
size 10 10 10
outside matref my_cool_wall
top matref my_cool_roof
phydrv example_physics
obstacle
end
|}

So what's the difference here? Well, this object will be treated as an obstacle. The outside walls (as opposed to inside, top, or bottom) will appear with the "my_cool_wall" [[material]], and the roof (top) will have "my_cool_roof." Of course, if you want a [[material]] on all sides of the object, you can simply omit the "top" specification at the start of the line, and simply have: "matref my_cool_material." Also, you can specify a [[physics driver]] to the object, to influence tank behavior a bit.

==Appearance==
By default, a meshbox will have red brick walls, and a grey stone roof. However, if a [[material]] is specified by the map creator, the appearance depends on the designer's choosing.

==History==
The meshbox was added in [[BZFlag 2.0.0]].

==Editor Support==
The meshbox IS supported by [[iBZEdit]], [[pyBZEdit]], [[Blender]] with the [[BZWTools]] plugin, and the [[BZW Exporter for Wings3D]]. The meshbox is NOT supported by [[BZEdit]] or [[BZFed]].

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

Arc

2007-03-18T18:23:43Z

TangenT: /* History */

The arc object is a [[BZW]] object that defines an arc or cylinder in the game arena.

==Code==
To place an arc into your map file, the following template is suggested:
{|
|
arc
name example_arc
divisions 16 # number of subdivisions in the arc
flatshading # use flat shading. smooth is default.
angle 360 # the sweep of the arc. 360 makes a full circle.
ratio 1 # use ratio to make a hollow arc. the parameter is (outrad - inrad) / outrad.
position 0 0 0 # the position of the arc (params: x-pos, y-pos, height)
size 10 10 10 # the size of the arc (params: width, length, height)
rotation 0 # the angle rotation of the arc.
shift 0 0 0 # shift the arc (repeatable)
shear 0 0 0 # (repeatable)
scale 1 1 1 # the scale of the arc to usual. 1 is default, lower values make it smaller. (repeatable)
spin angle nx ny nz # rotate the arc around a vector by angle. ONE of nx, ny, and nz should be 1, the others should be 0. (repeatable)
phydrv physics_driver_name # apply a physics driver to the arc
smoothbounce # shot bounces use normals
matref material # simple way to apply a material to the arc
end
|}

==Appearance==
The arc, by default, has the red brick wall texture on the sides, and the grey roofs of normal boxes on the top. However, using [[matref]], one can change the appearance of the arc.

==History==
The arc object has been supported since [[BZFlag 2.0.0]]. In previous versions of BZFlag, this object will not work.

==Editor Support==
Editors that support the arc object include [[Blender]] using the [[BZWTools]], [[Wings3D]] using the [[BZW Exporter for Wings3D]], and [[pyBZEdit]]. [[BZEdit]] and [[BZFed]] do NOT support the arcs.

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

Material

2007-03-18T18:21:33Z

TangenT: Initial posting of material reference.

A material is used in a BZFlag world to define a new look for otherwise regular objects, such as [[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]]

Meshbox

2007-03-18T17:39:25Z

TangenT: /* Editor Support */

The meshbox is the 2.0 update to the original [[box]] object in BZFlag 1.0. The main difference between the [[box]] and the Meshbox is that the meshbox supports new features in BZFlag 2.0, such as physics drivers and textures.

==Code==
A very basic meshbox will include:
{|
|
meshbox
position 0 0 0 # x-pos, y-pos, height
rotation 0 # rotation in degrees
size 10 10 10 # x-len, y-len, height
end
|}

As with the [[box]] object, position defines where the meshbox should be located. Rotation defines the angle it should be rotated to (about the Z-axis), and size defines how big or small the object should be. Now, if you're looking for something a little fancier, you can try code similar to this:

{|
|
meshbox
position 0 0 0
rotation 0
size 10 10 10
outside matref my_cool_wall
top matref my_cool_roof
phydrv example_physics
obstacle
end
|}

So what's the difference here? Well, this object will be treated as an obstacle. The outside walls (as opposed to inside, top, or bottom) will appear with the "my_cool_wall" [[material]], and the roof (top) will have "my_cool_roof." Of course, if you want a [[material]] on all sides of the object, you can simply omit the "top" specification at the start of the line, and simply have: "matref my_cool_material." Also, you can specify a [[physics driver]] to the object, to influence tank behavior a bit.

==Appearance==
By default, a meshbox will have red brick walls, and a grey stone roof. However, if a [[material]] is specified by the map creator, the appearance depends on the designer's choosing.

==History==
The meshbox was added to BZFlag in version 2.0.0.

==Editor Support==
The meshbox IS supported by [[iBZEdit]], [[pyBZEdit]], [[Blender]] with the [[BZWTools]] plugin, and the [[BZW Exporter for Wings3D]]. The meshbox is NOT supported by [[BZEdit]] or [[BZFed]].

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

BZW Exporter for Wings3D

2007-03-18T17:38:35Z

TangenT: Initial posting of Wings3D exporter article.

The BZW Exporter for Wings3D was written by trepan so that users of Wings3D could export their 3D models to BZFlag world files.

==Download==
You can download the plugin [http://trepan.bzflag.bz/wings3d_to_bzw_1.1.tar.gz here]. To install, save the .tar.gz to your computer and simply hit File->Install Plugin. Then, select the .tar.gz file which you saved to your local machine.

==OS Support==
The BZW export plugin will work on any operating system that supports Wings3D.

[[category:Map Making]]
[[category:Map Editors]]

Arc

2007-03-18T17:27:08Z

TangenT: /* Editor Support */

The arc object is a [[BZW]] object that defines an arc or cylinder in the game arena.

==Code==
To place an arc into your map file, the following template is suggested:
{|
|
arc
name example_arc
divisions 16 # number of subdivisions in the arc
flatshading # use flat shading. smooth is default.
angle 360 # the sweep of the arc. 360 makes a full circle.
ratio 1 # use ratio to make a hollow arc. the parameter is (outrad - inrad) / outrad.
position 0 0 0 # the position of the arc (params: x-pos, y-pos, height)
size 10 10 10 # the size of the arc (params: width, length, height)
rotation 0 # the angle rotation of the arc.
shift 0 0 0 # shift the arc (repeatable)
shear 0 0 0 # (repeatable)
scale 1 1 1 # the scale of the arc to usual. 1 is default, lower values make it smaller. (repeatable)
spin angle nx ny nz # rotate the arc around a vector by angle. ONE of nx, ny, and nz should be 1, the others should be 0. (repeatable)
phydrv physics_driver_name # apply a physics driver to the arc
smoothbounce # shot bounces use normals
matref material # simple way to apply a material to the arc
end
|}

==Appearance==
The arc, by default, has the red brick wall texture on the sides, and the grey roofs of normal boxes on the top. However, using [[matref]], one can change the appearance of the arc.

==History==
The arc object has been supported in all BZFlag versions since 2.0.0. In previous versions of BZFlag, this object will not work.

==Editor Support==
Editors that support the arc object include [[Blender]] using the [[BZWTools]], [[Wings3D]] using the [[BZW Exporter for Wings3D]], and [[pyBZEdit]]. [[BZEdit]] and [[BZFed]] do NOT support the arcs.

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

Meshbox

2007-03-18T17:26:26Z

TangenT:

The meshbox is the 2.0 update to the original [[box]] object in BZFlag 1.0. The main difference between the [[box]] and the Meshbox is that the meshbox supports new features in BZFlag 2.0, such as physics drivers and textures.

==Code==
A very basic meshbox will include:
{|
|
meshbox
position 0 0 0 # x-pos, y-pos, height
rotation 0 # rotation in degrees
size 10 10 10 # x-len, y-len, height
end
|}

As with the [[box]] object, position defines where the meshbox should be located. Rotation defines the angle it should be rotated to (about the Z-axis), and size defines how big or small the object should be. Now, if you're looking for something a little fancier, you can try code similar to this:

{|
|
meshbox
position 0 0 0
rotation 0
size 10 10 10
outside matref my_cool_wall
top matref my_cool_roof
phydrv example_physics
obstacle
end
|}

So what's the difference here? Well, this object will be treated as an obstacle. The outside walls (as opposed to inside, top, or bottom) will appear with the "my_cool_wall" [[material]], and the roof (top) will have "my_cool_roof." Of course, if you want a [[material]] on all sides of the object, you can simply omit the "top" specification at the start of the line, and simply have: "matref my_cool_material." Also, you can specify a [[physics driver]] to the object, to influence tank behavior a bit.

==Appearance==
By default, a meshbox will have red brick walls, and a grey stone roof. However, if a [[material]] is specified by the map creator, the appearance depends on the designer's choosing.

==History==
The meshbox was added to BZFlag in version 2.0.0.

==Editor Support==
The meshbox IS supported by [[iBZEdit]], [[pyBZEdit]], [[Blender]] with the [[BZWTools]] plugin, and the [[BZW Export Tool for Wings3D]]. The meshbox is NOT supported by [[BZEdit]] or [[BZFed]].

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

Weapon (object)

2007-03-18T17:24:22Z

TangenT: /* Code */

A weapon object is a [[BZW]] map structure that defines a fixed weapon effect. This is also called a '''world weapon'''.

==Code==
The code for a weapon object is as follows
{|
|
weapon
name example_weapon
position 0.0 0.0 0.0
rotation 0.0
color 0
tilt 0.0
initdelay 10.0
delay 10.0 3.0 5.0 3.0
type V
trigger flagcap
eventteam R
end
|}
Valid parameters for a weapon object are:
*'''name''' : the name of the weapon, generally unused.
*'''position ''' : the position in world units for the effect to begin at
*'''rotation ''' : the orientation in degrees for the effect to fire in.
*'''color ''' : the color the weapon should be.
*'''tilt ''' : the vertical tilt in degrees for the effect to fire in.
*'''initdelay ''' : the delay to wait after the server starts before the effect is triggered.
*'''delay ''' : a list of delays to loop through after the startup delay.
*'''type ''' : the [[FlagCode]] for the flag effect to use for the weapon.
*'''trigger ''' : if a delay is not used, when to trigger the flag, currently only flagcap is valid.
*'''eventteam ''' : the team to use when looking at flagcap weapons.

The weapon object can be used as many times as desired on a map.

==Appearance==
The weapon object will produce a weapon effect that is exactly the same as similar effects produced by players.

==History==
The weapon object was added in [[BZFlag 2.0.0|v2.0.0]].

==Editor Support==
The weapon object is only fully supported by the [[BZWTools]] blender plug-in.

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

Meshbox

2007-03-18T17:19:53Z

TangenT: Initial posting of the meshbox object

The meshbox is the 2.0 update to the original [[box]] object in BZFlag 1.0. The main difference between the [[box]] and the Meshbox is that the meshbox supports new features in BZFlag 2.0, such as physics drivers and textures.

==Code==
A very basic meshbox will include:
{|
|
meshbox
position 0 0 0 # x-pos, y-pos, height
rotation 0 # rotation in degrees
size 10 10 10 # x-len, y-len, height
end
|}

As with the [[box]] object, position defines where the meshbox should be located. Rotation defines the angle it should be rotated to (about the Z-axis), and size defines how big or small the object should be. Now, if you're looking for something a little fancier, you can try code similar to this:

{|
|
meshbox
position 0 0 0
rotation 0
size 10 10 10
outside matref my_cool_wall
top matref my_cool_roof
phydrv example_physics
obstacle
end
|}

So what's the difference here? Well, this object will be treated as an obstacle. The outside walls (as opposed to inside, top, or bottom) will appear with the "my_cool_wall" [[material]], and the roof (top) will have "my_cool_roof." Of course, if you want a [[material]] on all sides of the object, you can simply omit the "top" specification at the start of the line, and simply have: "matref my_cool_material." Also, you can specify a [[physics driver]] to the object, to influence tank behavior a bit.

==Appearance==
By default, a meshbox will have red brick walls, and a grey stone roof. However, if a [[material]] is specified by the map creator, the appearance depends on the designer's choosing.

==History==
The meshbox was added to BZFlag in version 2.0.0.

==Editor Support==
The meshbox IS supported by [[iBZEdit]], [[pyBZEdit]], [[Blender]] with the [[BZWTools]] plugin, and the [[BZW Export Tool for Wings3D]]. The meshbox is NOT supported by [[BZEdit]] or [[BZFEdit]].

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

Arc

2007-03-18T17:03:44Z

TangenT:

The arc object is a [[BZW]] object that defines an arc or cylinder in the game arena.

==Code==
To place an arc into your map file, the following template is suggested:
{|
|
arc
name example_arc
divisions 16 # number of subdivisions in the arc
flatshading # use flat shading. smooth is default.
angle 360 # the sweep of the arc. 360 makes a full circle.
ratio 1 # use ratio to make a hollow arc. the parameter is (outrad - inrad) / outrad.
position 0 0 0 # the position of the arc (params: x-pos, y-pos, height)
size 10 10 10 # the size of the arc (params: width, length, height)
rotation 0 # the angle rotation of the arc.
shift 0 0 0 # shift the arc (repeatable)
shear 0 0 0 # (repeatable)
scale 1 1 1 # the scale of the arc to usual. 1 is default, lower values make it smaller. (repeatable)
spin angle nx ny nz # rotate the arc around a vector by angle. ONE of nx, ny, and nz should be 1, the others should be 0. (repeatable)
phydrv physics_driver_name # apply a physics driver to the arc
smoothbounce # shot bounces use normals
matref material # simple way to apply a material to the arc
end
|}

==Appearance==
The arc, by default, has the red brick wall texture on the sides, and the grey roofs of normal boxes on the top. However, using [[matref]], one can change the appearance of the arc.

==History==
The arc object has been supported in all BZFlag versions since 2.0.0. In previous versions of BZFlag, this object will not work.

==Editor Support==
Editors that support the arc object include [[Blender]] using the [[BZWTools]], [[Wings3D]] using the [[BZW Exporter for Wings3D]], and [[pyBZEdit]]. [[BZEdit]] and [[BZFedit]] do NOT support the arcs.

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

Arc

2007-03-18T16:47:29Z

TangenT: Initial posting of the arc object.

The arc object is a [[BZW]] object that defines an arc or cylinder in the game arena.

==Code==
To place an arc into your map file, the following template is suggested:
{|
|
arc
name example_arc
divisions 16 # number of subdivisions in the arc
flatshading # use flat shading. smooth is default.
angle 360 # the sweep of the arc. 360 makes a full circle.
ratio 1 # use ratio to make a hollow arc. the parameter is (outrad - inrad) / outrad.
position 0 0 0 # the position of the arc (params: x-pos, y-pos, height)
size 10 10 10 # the size of the arc (params: width, length, height)
rotation 0 # the angle rotation of the arc.
shift 0 0 0 # shift the arc (repeatable)
shear 0 0 0 # this should be edited. (repeatable)
scale 1 1 1 # the scale of the arc to usual. 1 is default, lower values make it smaller. (repeatable)
spin angle nx ny nz # rotate the arc around a vector by angle. ONE of nx, ny, and nz should be 1, the others should be 0. (repeatable)
phydrv physics_driver_name # apply a physics driver to the arc
smoothbounce # shot bounces use normals
matref material # simple way to apply a material to the arc
end
|}

==Appearance==
The arc, by default, has the red brick wall texture on the sides, and the grey roofs of normal boxes on the top. However, using [[matref]], one can change the appearance of the arc.

==History==
The arc object has been supported in all BZFlag versions since 2.0.0. In previous versions of BZFlag, this object will not work.

==Editor Support==
Editors that support the arc object include [[Blender]] using the [[BZWTools]], [[Wings3D]] using the [[BZW Exporter for Wings3D]], and [[pyBZEdit]]. [[BZEdit]] and [[BZFedit]] do NOT support the arcs.

BZFlagWiki - User contributions [en]

Recordmatch

Recordmatch

User:TangenT

Talk:Main Page

Category:Support

Other Links

Help:Contents

AHOD

Sphere

Link

Zone

Slash Commands

BZFS Command Line Options

Teleporter

Arc

Define

Meshbox

Arc

Material

Meshbox

BZW Exporter for Wings3D

Arc

Meshbox

Weapon (object)

Meshbox

Arc

Arc