BZFlagWiki - User contributions [en]

Box

2007-08-27T10:07:11Z

Tanner: Undo revision 3144 by 192.72.124.12 (Talk)

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

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

'''In versions 2.0.8 and older, boxes do not support''' [[material]], custom textures, or [[Physics_Drivers|physics drivers]]. The [[meshbox]] object replaces the box object and supports all these features and capabilities.

'''However, as of June 6, 2006 (SVN revision 13013, version 2.0.9)''', bzfs will convert the box object to a mesh when necessary. This feature allows them to be textured and have physics drivers assigned to them.

{|
|
box
position 0 40 0
size 5 5 10
rotation 0
'''top matref something1'''
'''sides matref something2'''
'''y+ matref something3'''
'''y- matref something4'''
'''bottom matref something6'''
'''texsize 1 1'''
'''phydrv physics_driver_name'''
end
|}

<properties>
x+, x-, y+, y-, z+, and z-=Assigns a [[material]] to a specific side of the box
top=Assigns a [[material]] to the top (z+) of the box
bottom=Assigns a [[material]] to the bottom (z-) of the box
sides or outside=Assigns a [[material]] to the x+, x-, y+, and y- sides of the box
texsize=Texture sizes, changes how the textures scale on the object.
texoffset=Controls the offset of the texture
phydrv=Reference to a predefined [[physics|physics driver]].
</properties>

More information that needs to be merged into the wiki, as well as the BZW manfile: [http://my.bzflag.org/bb/viewtopic.php?t=8199 Smart Boxes and Pyramids]

==Appearance==
Box objects by default have a red brick texture on the vertical sides, and a white plaster texture on the top and bottom. A box of height 0 on ground level ''is'' visible.

The texsizes of boxes and boxes made of meshes (e.g. meshbox and box with one of the new properties) are different.

{|
|+
|- texsize
|- Old style boxes
|- -2.0f -2.0f -8.0f -8.0f
|}

{|{{Prettytable}}
|-
| {{Hl3}} |'''Box type'''
| {{Hl3}} |'''texsize'''
|-
|box (old style box)
| -2.0f -2.0f -8.0f -8.0f
|-
|meshbox
| -8.0f -8.0f -8.0f -8.0f
|-
|box with one meshbox property
| -8.0f -8.0f -8.0f -8.0f
|}

This will cause the textures to scale differently in X and Z axis. Same values will cause textures in Y axis (vertical axis) to scale the same way.

In [[BZFlag_2.2|BZFlag 2.2]] all 3 type of boxes will use "texsize -8.0f -8.0f -8.0f -8.0f".

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

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

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

Ideas

2007-08-12T17:43:00Z

Tanner: /* Server Options, Administration, Plug-ins, and the Plug-in API */

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

Commentary may include personal comments by developers.

= Editing this page =

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[[Category:Development]]

Talk:Map making by hand

2007-07-22T02:32:50Z

Tanner: New page: Needs some sort of clean-up/organization.

Needs some sort of clean-up/organization.

Hot keys

2007-06-09T19:28:47Z

Tanner: Redirect to key mapping.

#REDIRECT [[Key Mapping]]

Genocide

2007-05-23T01:04:14Z

Tanner: New page: Genocide is a flag which kills an entire team that the shot hits with the exception of rogues. Rogues can experience the same reaction with the help of RogueGenocide. {{stub}}

Genocide is a flag which kills an entire team that the shot hits with the exception of rogues. Rogues can experience the same reaction with the help of [[RogueGenocide]].

{{stub}}

PyBZEdit

2007-05-23T01:02:02Z

Tanner:

pyBZEdit is the name of a [[BZW]] map editor written in the [http://en.wikipedia.org/wiki/Python_%28programming_language%29 python programing language]. It is somewhat platform independent and can be made to run on most systems.

With the update of wxPython, it seems that the map viewing section of pyBZEdit is not compatible with the new version and therefore is not working.

==Overview==
While attempting to solve the cross platform compatibility issues of [[BZEdit]] and [[BZEditWin32]] by using the python language, pyBZEdit was in the end dependent on a number of external libraries that were difficult to install on the host OS, and fell out of use shortly after it was announced.

==Development==
pyBZEdit was not developed by the BZFlag developers and is maintained independently at, http://sourceforge.net/projects/pybzedit/ by David Lawler. It appears as if development is slowed or stopped at this time.

== Replacement by blender ==
The current accepted method of graphically editing [[BZW]] maps on Linux is using the [[BZWTools]] plug-ins for [http://blender.org blender], as they provide a full 2.0 compliant editing system on a large number of platforms.

[[Category:Map Making]]
[[Category:Map Editors]]

Material

2007-05-13T16:22:18Z

Tanner: /* Code */

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 (don't use PNG extension)
addtexture=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=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 (red,green,blue,alpha)
color=synonym for diffuse
specular=specular color
emission=emission 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
|}

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

Meshpyr

2007-04-16T21:19:20Z

Tanner:

[[Image:MeshpyrAppearance.jpg|right|thumb|400px|Several meshpyr, with the one in the middle having the default texture]]
A meshpyr is a [[BZW]] map object that constructs a specialized [[mesh|Mesh]] has the geometric appearance of a [[Pyramid]]. It replaces the [[pyramid]] object as of [[BZFlag 2.0.0|v2.0.0]] and is compatible with [[material|materials]] and [[physics|physics drivers]].

==Code==
The code for a meshpyr object is as follows
{|
|
meshpyr
position 10 20 30
rotation 45
size 1 2 3
matref myMaterial
phydrv myPhysics
end
|}

Valid parameters for a meshpyr are:
<properties>
position=defines the center of the box in X and Y and the bottom of the box in Z.
rotation=defines a rotation around the Z axis for the box, in degrees.
size=defines the distance from the center to the side of the box in X and Y, and the total height of the box in Z.
matref=reference to a predefined [[material]].
phydrv=reference to a predefined [[physics|physics driver]].
</properties>

==Appearance==
An meshpyr with out a material definition will use the default material used by a standard [[pyramid]] object. Geometrically a meshpyr is identical to a standard [[pyramid]] object.

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

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

BZFS Command Line Options

2007-04-12T21:21:48Z

Tanner:

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 allow everyone 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 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.

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

Ricochet

2007-04-09T20:32:41Z

Tanner:

The ricochet effect causes standard and laser shot types to rebound off of objects.

The effect can be acquired with the Ricochet(R) superflag or added to all players with the +r [[BZFS Command Line Options|BZFS Command Line Option]].

==Unaffected Flags==
Ricochet on the server does not effect Superbullet, PhantomZone, GuidedMissle, nor Shockwave superflags. See the [[Flag List|Flag List]] for a list of all flags availble in BZFlag.
{{Stub}}

Radar

2007-04-08T15:38:44Z

Tanner: New page: The radar is shown on the users screen to the left of the message box which gives them a layout of the map. ==Overview== On the radar players, map objects, bases, and flags are shown. {{...

The radar is shown on the users screen to the left of the message box which gives them a layout of the map.

==Overview==
On the radar players, map objects, bases, and flags are shown.

{{stub}}

Category:History

2007-04-08T13:47:52Z

Tanner: New page: Articles inside this category relate to or tell the story of BZFlag's history.

Articles inside this category relate to or tell the story of BZFlag's history.

Talk:BZFX

2007-04-06T02:30:00Z

Tanner:

== DonnyBaker's page removal ==

I don't see why BZFX can't have extended information. It is relevant to BZFlag and a major server network. It's also in a convenient place to find - not everyone knows about the BZFX web-site. --[[User:A Meteorite|A Meteorite]] 18:47, 5 April 2007 (EDT)

As I stated in my rollback. The information you have is suited for a BZFX website, not BZFlag. The 'majorness' of your network is pretty much an opinion, yours. I will do the same to any other "Network" that posts information that belongs on their own website. [[User:DonnyBaker|DonnyBaker]] 20:52, 5 April 2007 (EDT)

The 'majorness' of your network is pretty much an opinion, yours. I will do the same to any other "Network" that posts information that belongs on their own website. [[User:DonnyBaker|DonnyBaker]] 20:52, 5 April 2007 (EDT)

Wait, what? Opinion? Rules are not opinion. Group information is not opinion. Those are all things BZFX and BZFX rules, which are facts '''to BZFX''' (which is what the article is '''about'''). I never say BZFX is a major server network on the wiki page either, because that is opinion. The other stuff is facts to BZFX. Plus some of this is important information and might possibly only get the exposure it needs on this wiki. --[[User:A Meteorite|A Meteorite]] 21:59, 5 April 2007 (EDT)

:Any network should be treated as if it were a league - basic information only (website, irc channel...etc). On the leagues page it does not go into full explanation of what the league is; just the basics. -[[User:Tanner|Tanner]] 22:30, 5 April 2007 (EDT)

Rogue

2007-03-31T01:15:34Z

Tanner:

;Rogue
/roʊg/ noun, verb, rogued, ro·guing, adjective

:Def1: a dishonest, knavish person; scoundrel.
:Def2: a playfully mischievous person; scamp: The youngest boys are little rogues.
:Def3: no longer obedient, belonging, or accepted and hence not controllable or answerable; deviating, renegade: a rogue cop; a rogue union local.
[From http://dictionary.reference.com/browse/rogue]

In BZFlag, rogue is a team players can join (if allowed), though they have no teammates, and can kill any and all tanks, including other rogues. The bullet color is yellow, as is the tank on the radar. The tanks themselves are a dark gray/black color, in the usual tank pattern.

If a rogue team is on a [[CTF]] server, they do not have a team flag.

User:Tanner

2007-03-30T23:18:49Z

Tanner: New page: Tanner lives in Georgia, USA. Tanner is the owner of [http://labs.tssoftware.net labs.tssoftware.net] which runs BZStocks and hosts BZFlag_Info files.

Tanner lives in Georgia, USA.

Tanner is the owner of [http://labs.tssoftware.net labs.tssoftware.net] which runs BZStocks and hosts BZFlag_Info files.

Administrator

2007-03-30T10:01:07Z

Tanner:

An [[Administrator]] of a server can start/shutdown the server and edit the many options of it. Usually administrators of a server are the ones who own/run the server or are trusted friends of the owner.

==Display==
On the [[Scoreboard|scoreboard]], admins have an '''@''' sign next to their name.

==Permissions==
Administrators can run many [[Slash Commands | commands]] on the server including the following:
*/kick
*/ban
*/set
*/flag (reset,give/take)
*The list continues...

Depending on their level of admin privilege, administrators can also change in-game parameters, for example the pattern on the ground or the shot reload time.

==Becoming Admin==
Perhaps the number one rule of becoming a server admin is to '''never ask to become one'''. Most owners frown upon this and will not consider you for future promotions. You do not need to bring anything to their attention, if they need an admin, they will ask someone if they would like to become one.

Server owners usually only let trusting people become server admins. People who help others, play a lot at the server(s), or can be trusted may be asked to be admin on a server. Just play nice, be friendly and see what happens!

==Being a Good Admin==
A good admin exhibits several traits. A good admin takes care of vulgar language users, flame wars, spammers and [[Known Cheats|cheaters]]. The admin supports the server and promotes good and courteous gameplay. Some servers allow the use of strong language; this is usually announced in the server welcome message when you first join.

{{stub}}

Administrator

2007-03-30T09:57:08Z

Tanner:

An [[Administrator]] of a server can start/shutdown the server and edit the many options of it. Usually administrators of a server are the ones who own/run the server or are trusted friends of the owner.

==Display==
On the [[playerlist]], admins have an '''@''' sign next to their name.

==Permissions==
Administrators can run many [[Slash Commands | commands]] on the server including the following:
*/kick
*/ban
*/set
*/flag (reset,give/take)
*The list continues...

Depending on their level of admin privilege, administrators can also change in-game parameters, for example the pattern on the ground or the shot reload time.

==Becoming Admin==
Perhaps the number one rule of becoming a server admin is to '''never ask to become one'''. Most owners frown upon this and will not consider you for future promotions. You do not need to bring anything to their attention, if they need an admin, they will ask someone if they would like to become one.

Server owners usually only let trusting people become server admins. People who help others, play a lot at the server(s), or can be trusted may be asked to be admin on a server. Just play nice, be friendly and see what happens!

==Being a Good Admin==
A good admin exhibits several traits. A good admin takes care of vulgar language users, flame wars, spammers and [[Known Cheats|cheaters]]. The admin supports the server and promotes good and courteous gameplay. Some servers allow the use of strong language; this is usually announced in the server welcome message when you first join.

{{stub}}

BZFlag Community

2007-03-30T00:34:02Z

Tanner: Redirecting to BZFlag Forums

#REDIRECT [[BZFlag Forums]]

Global Registration

2007-03-30T00:31:45Z

Tanner: New page: Global Registration is the link between the BZFlag Forums and the game. If you are registered at the forums, you are registered on the game (although you only have one registration - t...

Global Registration is the link between the [[BZFlag Forums]] and the game. If you are registered at the forums, you are registered on the game (although you only have one registration - the forums). The game uses the forums to authenticate you as a registered user.

{{stub}}

Administrator

2007-03-30T00:18:54Z

Tanner: New page: An Administrator of a server can start/shutdown the server and edit the many options of it. Usually administrators of a server are the ones who own/run the server or trusted friends of...

An [[Administrator]] of a server can start/shutdown the server and edit the many options of it. Usually administrators of a server are the ones who own/run the server or trusted friends of the owner.

==Display==
On the playerlist, admins have a '''@''' sign next to their name.

==Permissions==
Administrators can run many commands on the server including the following:
*/kick
*/ban
*/set
*Among many others...

==Becoming Admin==
Perhaps the number one rule of becoming a server admin is to '''never ask to become one'''. Most owners frown upon this and will not consider you for future promotions. You do not need to bring anything to their attention, if they need an admin, they will ask someone if they would like to become one.

Server owners usually only let trusting people become server admins. People who help others, play a lot at the server(s), or can be trusted may be able to be admin on a server.

==Being a Good Admin==
A good admin consists of a few traits. They may or may not be apply. A good admin takes care of vulgar language users, flame wars, and cheaters. The admin supports the server and promotes good and curtious gameplay. Again, these may vary on the rules of the server.

{{stub}}

David Trowbridge

2007-03-29T23:46:05Z

Tanner: Spam.

David Trowbridge aka "purple_cow" is a developer and system administrator for the project. He has committed a great deal of code to the project, including [[BZEdit]] and [[BZDB]].

[[Category:Developer]]
[[Category:Core_Developer]]

Missile War

2007-03-28T18:35:55Z

Tanner:

Missilewar is a 4-team CTF map by Ducatiwannabe.

The bases are situated in the corners of the map. There are many superflags, such as Guided Missile, Laser, Super Bullet and Stealth. This and other map features make sniping possible, defending interesting and capturing a challenge.

[[Category:CTF Maps]]
[[Category:4 Team Maps]]

BZFS

2007-03-26T22:50:17Z

Tanner:

''This is an article specifically about the BZFS program. For general information on creating a BZFlag server, see [[Creating A Server]].''

BZFS is name of the the [[BZFlag]] server application. It is a command line application that can ether be run manually or started from within the game. The server supports a large list of [[BZFS Command Line Options|command line options]] that can be used. All BZFlag games are hosted on BZFS servers, there is no 'single player' game that is run with only a client.

==Public Vs. Private Servers==
BZFS can be run in ether a [[Public BZFS|public]] or private mode. Public servers are listed with the central [[List Server]] system and can take advantage of the [[Global Login]] system for user management. Private servers will only be visible on the LAN they are started on. The in-game server menu can only start private servers.

==Command line options and Config files==
BZFS uses a large number of [[BZFS Command Line Options|command line options]] to set the various modes and options for a game. These options can be specified from the comamnd line prompt of the host OS, or via a text file that is called the 'Config'. BZFS does not ship with a standard config file, it is assumed that the user will make there own. The full path to the config file is specified with the '''-conf''' options.

==World Files==
BZFS can read in [[BZW]] formated map files and use them to define the 3d world the game is played in.

==Plug-ins and the BZFS API==
BZFS can be extended by the use of server side [[Plug-ins]]. These [[Plug-ins]] are runtime loaded DLLs/SO files that use the [[BZFS API]] to modify and automate various game logic and settings.

==See also==
[[BZFS Command Line Options]]

[[BZFS API]]

[[Plug-ins]]

[[Sample conf|Sample Config File]]

[[Category:Server]]

Config File

2007-03-26T22:49:06Z

Tanner:

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

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

===Mac OS X===
~/Library/Application Support/BZFlag/2.0/config.cfg

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

[[Category:Client]]

Config File

2007-03-26T22:48:56Z

Tanner:

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

==Linking to The Config==

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

===Mac OS X===
~/Library/Application Support/BZFlag/2.0/config.cfg

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

[[Category:Client]]

Config File

2007-03-26T22:48:37Z

Tanner:

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

==Creating a Config==
For a starting point, look at the [[Sample conf|sample config file]] for most of the options that can be set in the config.

==Linking to The Config==

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

===Mac OS X===
~/Library/Application Support/BZFlag/2.0/config.cfg

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

[[Category:Client]]

Sample conf

2007-03-26T22:48:32Z

Tanner: The wiki already parses nothing in <pre> so why tell it not to again?

<pre>
# This is a BZFlag Server (bzfs) configuration file.
# It assumes that you wish to connect to the bzflag list server.
# Please read through it carefully. Lines starting with a # are comments.
# to enable an option, remove the # at the beginning of a line. To
# disable that option, put the # back. There are some examples in this
# file. Make sure you change the examples if you uncomment the line. If
# you don't know what something does, you are okay to just leave
# it commented out. Failure to read through this file (looking for
# already uncommented lines) might be a little embarrassing. Have fun.

# This option is for debug. You can have as many as 4 of them.
# simple debug
#-d
# and more complex debugging.
-dd
#-ddd
#-dddd

# Sets the admin password for the server. It is necessary for server
# administration if no groups are used.
# CHANGE THIS!
-password abcdef

# Enables inertia and sets the maximum linear and angular accelerations.
# The units are somewhat arbitrary so you'll have to experiment to find
# suitable values. The values must be non-negative and higher values
# yield greater inertia.
# Used to control "Mouse Enhancements"
-a 50 38

## World ##

# This specifies the world filename.
# Use this format for Windows
#-world "c:\mymaps\louschurchyard.bzw"
# Use this format for *nix and Mac
#-world /users/noob/lousdesktop.bzw

## Random World Generation ##

# This option allows world objects to be randomly rotated. Only applies
# if a randomly generated world is used.
#-b

# Enables capture-the-flag style game with a balanced random map. Default is
# free-for-all style game.
#-cr

# Adds teleporters to the game. for random maps only
#-t

# This option controls the building density on random worlds(1-10) default is 5
#-density 7

# This option changes the size of random maps.
#-worldsize 800

# This option gives buildings random heights. This is used when
# you are using random maps.
#-h

## Game Styles ##

# This enables capture-the-flag style game. Default is free-for-all style.
# Requires one base object for each team to be specified in the world file.
# Can be used with random world generation.
#-c

# More than one team-flag may be specified.
# This is generally not desirable.
# B* - Blue Team G* - Green Team, P* - Purple Team, R* - Red Team,
#+f B*
#+f R*

# This sets the maximum number of shots before a reload. The default
# is 5.
-ms 3

# This makes most shots ricochet.
+r

# This option allows jumping.
-j

# These two flags can be used if they are not specified as options.
# +f R{1} # Ricochet
# +f J{1} # Jumping

# This option allows for flags on box buildings.
#-fb

# This option allows tanks to spawn on buildings. This is especially useful
# as tank spawn locations are now are calculated on the server without the
# advantage of knowing where shots are.
#-sb

# By default if a player kills a teammate, he dies too, this option turns this
# off. Used mostly for capture the flag style games.
#-tk

# Kick a player if his ratio of teammate to non-teammate kills is this
# percentage or greater.
-tkkr 32

# This option allows you to tell the server how long a team flag remains
# before it is reset after the last player on a team leaves. The default
# is 30 seconds.
#-tftimeout 60

# Hunt the rabbit game is activated with this option.
# Use only one of these options.
# Choose rabbit based on score.
#-rabbit score
# Rabbit is chosen by whoever kills the rabbit.
#-rabbit killer
# Or you can choose the rabbit randomly.
#-rabbit random

# It is possible to restrict bots and autopilot from being used on the server.
# This is accomplished with the following.
#-disableBots

# This option causes the server to quit after serving one game. This is
# handy if you want to do a timed game, or script a rotating server.
#-g

# This option sets the max score for players. The game ends when a person
# reaches this score and is declared the winner.
#-mps 100

# This sets the max team score. The first team to reach this score is
# declared the winner and the game is ended.
#-mts 250

# This dumps the score to console when it changes.
#-printscore

# This sets time limit (in seconds) for the game. Time starts when first
# client connects.
#-time 3600

# This option requires a timed game to be started using the /countdown
# command to start a timed game. Default is when first player joins.
#-timemanual

## List server Connection ##

# This is the public message that the server advertises on the public
# server list. This is required if you want to be shown on the list.
# It often advertises the map you are using. Keep it short.
-public "Noo BZFlag Server With Random Map"

# This is also needed to be listed on the public server list. The
# address needs to be valid in DNS. It's your IP, plus port number.
-publicaddr 123.456.789.000:5154

# The server will listen on this port. Default port is 5154.
-p 5154

# Tells server not to respond to "pings". This makes the server private.
# You should remove -public and -publicaddr when using it.
# If your router is open, you can still give people your IP and port, and
# they will be able to connect, you just wont be on the list.
#-q

# You probably don't need to use this, but it is there if you do. This
# specifies where the server advertises itself. The built-in default
# should work just fine. You need to hunt down the proper address if
# it doesn't work. DON'T Change It
#-publiclist <list-server-url>

# Server will listen for and respond to "pings" (sent via broadcast) on
# the given interface. The server uses the first interface by default.
# This is the TCP/UDP/IP address the server will listen on.
# You don't need to use this unless your server has multiple
# interfaces and doesn't show up on the server lists.
#-i 123.456.789.000

## Player Connections ##

# Automatically assigns players to teams when they join so that teams are
# evenly matched in number of players. Players are placed on teams with
# lowest number of players first, then those with the lowest scores or
# kill ratios.
-autoTeam

# This sets the max number of players. It can be done in 2 ways. A flat
# count of players, or by number of players on a given team.
# This allows up to 50 players, no team limits.
# Typical home DSL connections max out at 12 players before lag begins.
# Lag equals players times shots. So a one-shot server could have more
# players, and vice-versa.
-mp 12

# This allows for max player by team.
# The order is rogue, red, green, blue, purple, observer.
#-mp 3,3,3,3,3,3

# This requires clients to use UDP (a good thing). This will generally
# make the server behave better, and make play more smooth.
# It will kick players who are unable to establish a UDP connection
# when they attempt to fire.
-requireudp

# Set to not use a UDP connection for players. You typically do NOT want to
# do this (UDP is good!)
#-noudp

# This option warns the user their lag is too high when it crosses the
# number of milliseconds set.
-lagwarn 350

# This option kicks players after they have been warned about high lag for
# a certain number of times.
-lagdrop 3

# This option kicks the user after they have been idle for a number of
# seconds. Idle means paused, not-spawning or not-responding.
-maxidle 300

# This option sets up your ban list. This is ip masks separated by commas.
# The * character is used as a wild card in range bans.
#-ban "192.168.1.5,10.10.2.*,10.2.*.*"

# This option tells the server where to store the ban list. The ban list will
# be loaded from this file when the server starts (if the file exists) and
# written back to the file when someone gets banned or unbanned. If this
# option isn't used the ban list will not be saved.
#-banfile /path/to/mybanfile.txt

# Registered player files which will be loaded on startup.
# Use all three if you are not connecting to the list server.
# Players can use /register passwd and /identify passwd
# to confirm their identities.
# passdb stores local user password mappings.
#-passdb /path/to/passes.txt
# userdb stores user to group mappings.
#-userdb /path/to/users.txt

# If you use the BZFlag forums at http://my.bzflag.org/bb
# and have established groups there, you only need groupdb
# Though local registrations can also be used.
# groupdb stores group to permission mappings.
#-groupdb /path/to/groups.txt

# If you have registered groups at the bzbb forums, only players
# in this group will see your server in the list.
#-advertise NOOB.COP

## General Options ##

# This is the server welcome message. Please change it.
-srvmsg " This is a Noo BZFlag Server "
-srvmsg " Have Fun and Play Nice "

# Define a message which will be broadcast to all players every 15 minutes.
-admsg " Noo BZFlag Server "
-admsg " BZFlag is Fun "

# This sets the amount of time in seconds that is required to pass between
# two identical messages sent.
-spamtime 15

# This sets the amount of times to warn spammers (see -spamtime) before they
# are kicked.
-spamwarn 3

# Specify a file that contains bad words that will be used when
# either -filterCallsigns or -filterChat is enabled.
# A multilingual badwords file can be found in source downloads.
#-badwords /path/to/badwords.txt

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

# Turn on the filtering of callsigns. Callsigns are compared against
# bad words provided via -badwords.
#-filterCallsigns

# 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.
#-filterSimple

# This forces all clients to use the same time of day. The time is
# determined by the server's clock. This disables the + and - keys
# on the clients.
#-synctime

## Player Controlled Functions ##

# This option specifies a help file that will be displayed when the player
# types /help name
# Maximum length is 50 lines and 120 characters per line
#-helpmsg shock /path/to/shockwavehelp.txt
#-helpmsg noob /path/to/noobhelp.txt

# You can specify a file so that people can type /report to report problems
# on the server. The reports are logged in this file.
#-reportfile /path/to/reports.txt

# You can also use this option to cause the /report to trigger a command
# as well as, or instead of, logging to a file.
#-reportpipe command

# This specifies the number of seconds in which a poll can be vetoed.
#-vetoTime 60

# This specifies the percentage of people required for a successful vote.
#-votePercentage 51

# This is the number of voters required to hold a poll.
#-votesRequired 6

# This is the length of time that players have to vote.
#-voteTime 60

## Flags ##

# This option allows for antidote flags to be available for players who
# get bad flags.
-sa

# Bad flags are automatically dropped after this many seconds.
-st 5

# Bad flags are automatically dropped after this many wins.
-sw 1

# This allows you to limit the number of shots from a particular flag.
#-sl GM 20
#-sl L 20

# There are two sets of flags. Flags that must be in the world at all times
# and flags that may get generated randomly. in addition. +f specifies flags that
# must be there and -f specifies flags the should never be generated.

# The server will randomly place flags from the following list.
# To be sure there is at least a certain amount of a flag on the map
# at any given time, you can use the +f option to guarantee a certain
# number of a flag.

# Good Flags
+f A{2} # Agility
+f CL{2} # Cloaking
+f F{2} # rapid Fire
+f G{1} # Genocide
+f GM{2} # Guided Missile
+f IB{2} # Invisible Bullett
+f L{2} # Laser
+f MG{2} # Machine Gun
+f N{2} # Narrow
+f OO{2} # Oscillation Overthruster
+f PZ{2} # Phantom Zone
+f QT{2} # QuickTurn
+f SB{2} # Super Bullet
+f SE{2} # SEer
+f SH{2} # SHield
+f SR{2} # SteamRoller
+f ST{2} # Stealth
+f SW{2} # ShockWave
+f T{2} # Tiny
+f TH{2} # THeif
+f US{2} # USeless
+f V{2} # Velocity (high speed)
+f WG{2} # WinGs

# BAD FLAGS
+f B{1} # Blindness
+f BY{1} # Bouncy
+f CB{1} # Color Blindess
+f FO{1} # Forward Only
+f JM{1} # Jamming
+f LT{1} # Left Turn only
+f M{1} # Momentum
+f NJ{1} # No Jumping
+f O{1} # Obesity
+f RC{1} # Reverse Controls
+f RO{1} # Reverse Only
+f RT{1} # Right Turn only
+f TR{1} # Trigger Happy
+f WA{1} # Wide Angle

# Using "+f good" is the equivalent of doing +f for each of the good flags.
# If you want to restrict a certain flag, you can use the -f option.
# just like with the +f option. "-f bad" is the same as doing -f for
# all of the bad flags.
#-f bad #no bad flags
#+f good #one of each good flag
#-f G #no genocide

# Use +s to have the server generate a certain number of extra flags
# and have them available at all times. This is in addition to
# any other flags specified.
#+s 20

# The server will have up to this many super flags at any time.
# Use this if you don't use any other method of flag generation.
#-s 30

## Variables ##

# There are three ways to load sets of server-specific variables.
# They can be specified in this .conf file.
# They can be specified in the .bzw map file in an options block.
# Or they can be specified in a third file with this option
#-vars /path/to/vars.txt

# Server variables can also be modified in-game using
# /set _varName value
# View the entire variable list by using
# /set (with nothing afterward) lists all vars
# /diff will list most non-default settings
# /? will list other available commands

# Here are a few examples of variables.
# Some variables are set to 0 for off, 1 for on.
#-set _obeseFactor 12
#-set _skyColor grey44
#-set _wingsJumpCount 3
#-set _tankExplosionSize 60
#-set _jumpVelocity 20
#-set _squishTime 7
#-set _mirror grey22
#-set _wallHeight 2
#-set _shotsKeepVerticalVelocity 1
#-set _drawGround 1
#-set _drawSky 1
#-set _drawClouds 0
#-set _drawMountains 0
#-set _fogMode exp
#-set _fogColor black
#-set _fogDensity .01
-set _rainType bubble

## Plugins ##

# Plugins have mostly superseded patches as a means of modifying
# the play of BZFlag servers. Recent improvements in the bzfs2.0.9 have enabled
# almost every server functionality to be modified with the plugin API.
#
# Plugins cannot be accessed unless you compile your plugins and
# bzfs binary with the option --enable-shared
#-loadplugin /path/to/playHistoryTracker

## Replay ##

# You can set up a server for replay mode by entering this option
#-replay

# This option sets the recording buffer to the specified amount of megabytes.
#-recbuf 2

# This option sets the directory to look for and save recordings.
#-recdir

## More Comments ##
# An excellent conf builder exists at this location http://groupdb.links-clan.net/bzfs_conf.php<br>

# This is intended to include the minimum options for a working
# BZFlag server, that is also connected to the list server.
# All you need to do is edit your IP numbers in -publicaddr
# and start bzfs.
# As it connects to the list server, your terminal will show
# something that looks like a player has joined, then immediately left.
# When you see that happen, you have succeeded, and are listed.
# If you can not connect to the list server, you probably need to open
# port 5154 through your router, for both UDP and TCP. Instructions for that
# are not included here.

# You join your server locally, by opening your BZFlag game client
# and editing these lines in the JOIN GAME screen.
# In the SERVER line add localhost
# In the PORT line add 5154
# Then JOIN your server.

# Here are the short instructions.
# Open your router firewall at port 5154
# Change the -publicaddr line in this .file to match your IP.
# In your terminal, cd to the location of the bzfs binary.
# ./bzfs -conf /path/to/sample.conf
# Don't take out any # comment markers or add options that you think look cool
# until after you have the server working.
# The options you need have been included in this file.
# You don't even need to specify a map, bzfs will create a random map for you.
#
# You do not even need this .conf file to start a server.
# You can use as many options you'd like just typing them into the terminal.
# Assuming you have installed BZFlag in default locations.
# In Macintosh terminal application these two should work
# cd /Applications/BZFlag2.0.8/Contents/MacOS/
# ./bzfs -dd
#
# In windows command prompt, these two commands should suffice
# cd C:\program files\bzflag2.0.2
# bzfs.exe -dd
# All other path examples given in this file use *nix format
# Windows users will have to change all the path examples given in this file.
</pre>

[[Category:Server]]

Talk:Download

2007-03-25T03:38:02Z

Tanner: New page: We need torrents? ~~~~

We need torrents? [[User:Tanner|Tanner]] 23:38, 24 March 2007 (EDT)

Rabbit Hunt

2007-03-24T19:58:47Z

Tanner: New page: Rabbit Hunt is a game mode in BZFlag. ==Playing== A player is selected to be the rabbit (can be based on their killer or totally random) and the rest of the players remain hunters. Th...

[[Rabbit Hunt]] is a game mode in BZFlag.

==Playing==
A player is selected to be the rabbit (can be based on their killer or totally random) and the rest of the players remain hunters. The rabbit tries to kill the hunters while avoiding their shots. If the rabbit gets shot (by themselves or a hunter) they are no longer rabbit and someone else becomes rabbit. Hunters can get [[Team Kill|team killed]] by other hunters.

{{stub}}

[[Category:Gameplay]]

Talk:Zone

2007-03-24T19:54:49Z

Tanner:

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)

Talk:Zone

2007-03-24T19:54:37Z

Tanner:

Talk:Zone

2007-03-24T19:51:09Z

Tanner:

Zone

2007-03-24T19:42:42Z

Tanner:

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)
*'''flag''': Listed flags will spawn in the zone.
*'''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]]

TK

2007-03-24T19:39:26Z

Tanner: TK moved to Team Kill

#REDIRECT [[Team Kill]]

Team Kill

2007-03-24T19:39:26Z

Tanner: TK moved to Team Kill

Killing a player who is on the same team as you is known as "team-killing". TKing is frowned upon amongst players and it is customary to send an apologetic [[message]] after accidentally doing so. Maps are sometimes configured to destroy you if you TK and/or [[kick]] you for repeated TKs. Deliberate TKers are a nuisance and will most likely earn themselves a [[kick]] or [[ban]] from server admins.

Players who believe they are being victimised and deliberately TKed should send a [[message]] during the game asking the offender to stop. Try to stay calm and objective - the offending player may be new to the game and not realise what they are doing. If it doesn't stop, go somewhere else or switch team, then delight in shooting them back!

Note that rogue is not a team - they can shoot players of all team colours '''including''' other rogues.

Team Kill

2007-03-24T19:39:16Z

Tanner:

Server Administration

2007-03-24T19:38:31Z

Tanner:

[[administrator | Administrators]] can ban players from their servers if they see fit. It's an extreme measure but it's their server so why put up with disruptive, abusive or cheating players? Bans can be applied to individually named players and/or their IP address and/or whole ranges of IP addresses. Bans can have whatever duration the administrator deems appropriate, ranging from minutes, through days, to permanent.

Don't worry though, play nice and you won't be banned!

Kick

2007-03-24T19:38:09Z

Tanner:

This is the process of being thrown off a map. If a server unexpectedly exits, all current players and observers will be kicked. [[administrator | Administrators]] can kick individual players as they see fit. Behaviour liable to get a player kicked includes: cheating, deliberate [[TK | teamkilling]], swearing or abusing players in [[message | messages]].

Hold the Flag

2007-03-24T01:42:13Z

Tanner: Hold the Flag moved to HoldTheFlag

#REDIRECT [[HoldTheFlag]]

HoldTheFlag

2007-03-24T01:42:13Z

Tanner: Hold the Flag moved to HoldTheFlag

HTF is a plugin that creates basically a half capture the flag game mode. The user spawns on their team's base, somewhere on the map is their team's flag. Now the goal of the game is to capture your own flag (something not thought of as nice in normal CTF). More times you capture your own flag, the more points you get. Points do not affect your score in anyway and are shown via the chat.

{{stub}}

HTF

2007-03-24T01:40:43Z

Tanner: HTF moved to Hold the Flag: Will redirect HTF to this new page.

#REDIRECT [[Hold the Flag]]

HoldTheFlag

2007-03-24T01:40:43Z

Tanner: HTF moved to Hold the Flag: Will redirect HTF to this new page.

Capture the Flag

2007-03-24T01:16:27Z

Tanner:

Capture the Flag (CTF) is a game mode in BZFlag.

==Playing==
In the game playing CTF, there can be two or up to three teams with their own bases. Each team as one or more team flag(s) (usually just one) that they must protect. To win, they must get an enemies team flag to their home base. When they do get the enemies flag to their home base, all the other enemy teams die and restart at their base. The team who capped the flag, survives and is not affected.

{{stub}}

[[Category:Gameplay]]

FFA

2007-03-24T01:15:28Z

Tanner: Redirecting to Free For All

#REDIRECT [[Free For All]]

FFA

2007-03-24T01:14:54Z

Tanner: Redirecting to Free-for-all

#REDIRECT [[Free-for-all]]

Capture the Flag

2007-03-24T01:13:21Z

Tanner: New page: Capture the Flag (CTF) is a game mode in BZFlag. ==Playing== In the game playing CTF, there can be two or up to three teams with their own bases. Each team as one or more team flag(s) (us...

CTF

2007-03-24T01:08:31Z

Tanner: Redirecting to Capture the Flag

#REDIRECT [[Capture the Flag]]

Link

2007-03-24T01:02:35Z

Tanner:

A Link is a BZW object whichs 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 teleproter are

*'''from'''; From what teleporter.
*'''to'''; To what teleporter.

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.

Link

2007-03-24T00:59:14Z

Tanner:

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

==Code==
link
name example_link
from *
to *
end

Valid parameters for a teleproter are

*'''from'''; From what teleporter.
*'''to'''; To what teleporter.

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.

BZFlagWiki - User contributions [en]

Box

Ideas

Talk:Map making by hand

Hot keys

Other Links

Genocide

PyBZEdit

Material

Meshpyr

BZFS Command Line Options

Ricochet

Radar

Category:History

Talk:BZFX

Rogue

User:Tanner

Administrator

Administrator

BZFlag Community

Global Registration

Administrator

David Trowbridge

Missile War

BZFS

Config File

Config File

Config File

Sample conf

Talk:Download

Rabbit Hunt

Talk:Zone

Talk:Zone

Talk:Zone

Zone

TK

Team Kill

Team Kill

Server Administration

Kick

Hold the Flag

HoldTheFlag

HTF

HoldTheFlag

Capture the Flag

FFA

FFA

Capture the Flag

CTF

Link

Link