BZFlagWiki - User contributions [en]

GU League

2011-11-28T07:25:17Z

A Meteorite: Undo revision 8130 by 68.180.79.149 (talk)

The GU League is currently the most successful and active BZFlag league. It launched on January 23rd 2005, and since then has recorded over [http://www.guleague.org/Matches/ 21,100 matches]. There are currently [http://www.guleague.org/Teams/ 28 teams], 20 of which are active. There are over [http://www.guleague.org/Players/ 350 players] representing 47 different countries. All matches are played on the [[Hix]] map. (Statistics as of June 2, 2010)

The GU League offers challenging competition and includes some of the top BZFlag players. New players learn fast by getting involved in fun matches and by watching other players. People from all age groups play and many are willing to help new players get started.

Make sure to visit the [http://my.bzflag.org/bb/viewforum.php?f=103 official GU League forum] and read the "sticky" threads at the top of the page. They contain a lot of important information.

[[Image:GUMatch.jpg|right|thumb|300px|A GU match in progress. ]]

=Playing in GU=

For players that are new to BZFlag, it is recommended to check out the [[Getting_Started|Getting Started]] page. A [[Getting_Started#Registering_a_callsign.28Optional.29|globally registered name]] is required for league play.

A player can then [http://www.guleague.org/Login/ register in the league] using the same name. One of the [http://www.guleague.org/Contact/ GU League Admins] must be contacted with a request to be added to the [http://my.bzflag.org/bb/memberlist.php?mode=group&g=20506 gu.league spawnlist] on the BZBB forums. This will allow the player to spawn and talk on league servers.

==Rules and Guidelines==

The league keeps very high standards of behavior and sportsmanship. So check these rules before doing anything else:

*Match disturbance, player harassment, language, cheat accusations in public (1 day -7 days ban)
*Using cheats on public servers or in other leagues (6-9 months)
*Using cheats in the GU league (1 year to life)

These are subject to change, so please always check the [http://www.guleague.org/Rules/ GU Rules page] directly.

Please also consider reading the [http://my.bzflag.org/bb/viewtopic.php?f=103&t=13245| inofficial whitelist] on the BZBB, as it's often been referred to it in an actual issue.

===Fun Matches===

A good way to get started in the league is to play fun matches (typically abbreviated as 'fm'). These types of matches are very popular. Only official matches are entered into the website, so there is less pressure during a fun match. Players do not have to be in a team, and players from specific league teams don't have to play on the same color.

Fun matches can also have additional players join during play. Make sure that the current players don't mind before joining a match. Players should '''self-kill''' by shooting while facing a wall or self-destructing with the delete key. This ensures there is not an unfair advantage due to initially spawning on the team base. The phrase "sk please" is used quite often to request that someone self-kills.

Fun matches are not to be reported.

===Teams, Matching & Reporting===

So, you've registered and want to get some action? First of all, you're going to need a team. You can join a team by visiting the [http://www.guleague.org/Teams/ teams] page and hitting the "Join" button next to the team, that is, if the team is open to anyone. Most teams however, are closed and can only be joined by invitation sent from the team leader.
Usually you will always find some teams that are interested in new and active players. If you want to contact the leader of a team or the team itself, use the "BZMail" option that can be found at the top or bottom of any Team/Player profile page.
Don't be discouraged if the first couple of requests get turned down, most teams like to get to know the players before they accept them into their team. But it's easy to establish yourself within the GU community. You can get to know players best by playing fun matches, spending time on the various public servers and talking to others in Observer during matches. It's a learning by doing system.

Once you've found and joined a team you like you can immediately start matching! There are some rules you should take into account before doing so though.

===Official Matches===

Basic commands needed during official matches:

* '''/countdown''' - Start the 30 minute match timer.
* '''/countdown pause''' - Pause the match timer. Should not be abused and should only be used when necessary. (E.g. a player has to stop for a moment, etc.)
* '''/countdown resume''' - Resume the match timer and allow the match to continue.
* '''/gameover''' - This will abruptly end the match at any given time. (Do not abuse! Ending a match with out any notice will most certainly lead to a ban.)

Guidelines:

* Do not start the match timer before all participating players are ready and make sure everyone has agreed on playing an official match.
* Make sure all players agree with opponents lag before starting the match. It is frowned upon to start a match and realize half way in that the lag is unplayable.
* Everyone participating should either able to finish the match or have a substitute available in case.
* Make sure the server is an official GU League match server.
* If a player goes [NR] (which means they are 'Not Responding', thus have lost their connection to the server somehow), pause the match and wait for a substitute or for the player to rejoin
* Make sure everyone is ready for a substitute before it happens to prevent major chaos in the match.
* If two more players want to join from the respective teams, make sure everyone is prepared and has said yes to the addition of players.
* Pick a server closest to the majority of players. If it is a half/half case, just agree on one.

If for some reason a match has to be canceled, make sure a player of both teams somehow saves score, remaining time, position of flags/players. (Easiest by taking a screenshot - hit F5)
When the match can be resumed later, adjust the timer to the remaining time the match was stopped at. Use the /timelimit <minutes go here> command to adjust the timer before a match.

===Entering/Reporting official matches===

After you've successfully played an official match, you need to either report the match to one of the [http://www.guleague.org/Contact/ referees (aka 'refs') or admins] by BZMail on the GU site, or just have a present ref/admin enter it. When reporting by BZMail, you '''must''' include: Teams, Score, Time, Date.

==Official league servers==

It is very important that you only play official matches on the official league servers.

Here is a list of the servers and their respective locations.

'''Europe:'''

* brad.guleague.org: 5158
* bzf.guleague.org: 5157 and 5158
* dub.guleague.org: 59997
* longdon.guleague.org: 5158
* destroyer.guleague.org: 5158

'''America:'''

* quol.guleague.org: 5157 and 5158 (Quebec, Canada)
* my.inexplicably.org: 5158 (Texas, USA)
* brl.arpa.net: 5158 (California, USA)

'''New Zealand:'''

* bzflag.enuffsaid.co.nz: 5158

The replay servers can be found on port 5159, except for dub.guleague.org: 59996

If a match is not played on one of these servers, than it cannot be counted as official.

===Replays===

Every match, official or fun, is automatically recorded and saved to the respective replay server. Some servers have websites where the replay file, time, date and players are posted.

* http://longdon.guleague.org/
* http://destroyer.guleague.org/
* http://bzf.guleague.org/matchlist.html
* http://quol.bzflag.bz/bzmatches/ (New design!)

You can find help on how to get a replay start and running on the servers but here's a quick summary:

#Find the replay file you want by either using the above mentioned web-sites or by using
##/replay list -n (if possible, will display a list of recent replays in chronological order)
##/replay list *10042009* (will show you all replays played on April 10th, 2009)

#Once you've found your replay file
##/replay load #index number

Use /replay skip + or - <amount of seconds> to navigate within a replay
Use /replay pause and /replay resume to pause and resume a replay

===Public Servers===

Along with the various official servers, there are quite a few public servers set up using either identical or similar settings to the league. Players usually meet up there to get warm and just shoot around before or after a match. Anyone can play there, regardless of being registered in the league or not. All of these public servers are running the HiX map, some are CTF and some are just FFA.

List of popular HiX public servers:

* bzf.bzflag.net:5154 [FFA - HiX map]
* bzf.bzflag.net:5155 [4-Team CTF HiX]
* bzf.bzflag.net:5160 [2-Team CTF HiX]
* quol.guleague.org:5156 [2-Team CTF HiX]

=Settings and Options=

A big part of the GU league, is being able to compete. But the premise for that, is having good settings that will make things like dodging, shooting and jumping a lot easier. A very large amount of the GU players use mouse and only a dozen keyboard. If you are just starting out, I would recommend you try playing with mouse first, as many things will be easier to do later on.
In this game, it's impossible to become the best dodger, jumper and shooter at the same time. These are two if not three completely different types of playing that require many different settings.

Most of the setting adjustment is done by the [[Config_File]], as you can not exercise all your possibilities in the GUI options. You can find a lot of detailed information by using the [http://my.bzflag.org/bb/search.php Search option on BZBB]. Many players have posted their personal configs and other tips there.

For mouse players, these individual playing styles, also mean individual mouse settings. Mousebox size, mouse DPI, mouse sensitivity are all crucial. Usually slower mouse settings and a big mouseboxsize, will enable you to be a better jumper and or shooter, while fast, sensitive, precise mouse settings and a small to even negative mouseboxsize will be enable you to dodge better.
Next to all the native options, some players use mouse enhancement applications, see [http://my.bzflag.org/bb/viewtopic.php?f=103&t=13245 Whitelist] for further info.

Very experienced players however, are known to be able to jump, shoot and dodge with extreme precision. So, no setting in the world is going to help, if you don't practice and play enough.

=Stats=

You might have asked yourself how you're supposed to find other players online if you want to arrange a match.
There are some very useful BZStats and Player checkers that are have been useful to the whole community for years.

#The general BZStats checker that Strayer coded shows a massive amount of information on everything BZFlag related.
##http://bzstats.strayer.de
##http://bzstats.strayer.de/leagues/gu/online/?lang=en (that shows all current GU players that are online)

#The second checker is Saturos' GU League Checker
##http://guc.saturos.de (V.1)
##http://guc.phago.de (Beta V.2, this version is still in the makes but already has many features and fixes that V.1 does not)
The GUC displays all main Public and Official GU League servers with scores, players, timer and teams. (Very useful for following matches without opening a client)

=Abbreviations you should know=

As mentioned already above, there are some abbreviations used very often in the league. If you haven't already, check out [[Jargon]] for more non-league specific abbreviations and Jargon. Below are some league specific abbreviations. Note that this is not a complete list, just the most common terms you should know in order to prevent confusion between players or in a match.

<properties>
offi=Referring to an official match. ("offi?" means somebody wants to play an official match)
fm=Referring to fun match. ("fm?" means somebody wants to play a fun match)
sk=Selfkill. (Expression often used when new players join an already running fun match. New players should kill themselves once immediately after spawning.)
tk=Teamkill. (More frequently used outside of league play too)
def=Defense. Your flag is under immediate attack or about to be taken. Watch out for yours!
att=Attack. Focus on getting your opponents flag.
gs, ns, n1, g1=Good shot, nice shot, nice one, good one. Frequently used when a player does something that the other regards as nice or skillfull.
ty, thx=Thank you. Thanks.
hf, gl=Have fun, good luck.Usually always said to the opposing team before a match starts
gg=Good game. Usually said by all participating players after a match has ended.
</properties>

[[Category:Leagues]]

User:A Meteorite

2010-10-04T02:27:51Z

A Meteorite: formatting, grammar, add other contacts

I am the owner of the [[BZFX|BZFX server network]].

= Contact =

Please do not contact me about BZFX administration issues until you have tried to resolve it with the administrator who took action against you.

* '''E-Mail''':
** bzmeteorite[at]gmail[dot]com
** meteorite[at]bzfx[dot]net

* '''Other''':
** AIM & YIM: bzmeteorite
** gTalk & MSN: bzmeteorite[at]gmail[dot]com, meteorite[at]bzfx[dot]net (gTalk only)
** ICQ: 486607573

== External Links ==

* My [http://my.bzflag.org/bb/memberlist.php?mode=viewprofile&u=2863 BZBB Profile]

Main Page

2009-09-26T08:38:54Z

A Meteorite: Undo revision 6692 by Lala0453 (Talk)

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

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

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

==Google Summer of Code ==
BZFlag has applied to once again be a mentor organization in the Google Summer of Code. For details, please see the [[Google Summer of Code/2009|2009 Summer of Code wiki page]].

==General Information==
*[[Getting Started|Quick Start]]
*[[Getting Help]]
*[[:Category:BZFlagWiki_Policy|BZFlag Wiki Policy]]

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

==Things To Do==
*[[:Category:Stubs|Stubs]] These are short pages. You can help by expanding the content and adding more detail.
*[[:Special:Wantedpages|Wanted pages]] These are pages which don't exist yet but are pointed to from other pages. You can help by creating them.
*[[:Category:Items to be merged|Pages to merge]] These are pages which are similar. It is suggested that similar pages be merged. You can help by reviewing the pairs of pages and commenting on any proposals by using the "Discussion" tab at the top of each page.
*[[:Category:Old|Pages with old info]] You can help by updating these pages.
*[[:Category:Inaccurate|Inaccurate pages]] You can help by updating these pages.
*[[:Category:Pending Deletions|Pending deletions]] These are pages which have been nominated for deletion. You can help by reviewing these pages and commenting on any proposals by using the "Discussion" tab at the top of each page.

User:A Meteorite

2009-06-07T07:39:52Z

A Meteorite: phpBB3 has different profile links

Owner of the [[BZFX|BZFX server network]].

= Contact =

Please do not contact me about BZFX administration issues until you have tried to resolve it with the administrator.

* '''E-Mail''':
** meteorite [at] bzfx [dot] net

* '''Other''':
** AIM & YIM: bzmeteorite
** gTalk & MSN: bzmeteorite@gmail.com
** ICQ: 486607573

----

* See [http://my.bzflag.org/bb/memberlist.php?mode=viewprofile&u=2863 BZBB Profile]

Category:Leagues

2009-06-07T07:31:56Z

A Meteorite: Undo revision 5858 by 208.184.6.27 (Talk)

== BZFlag Leagues ==

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

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

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

Match Length: 15, 20 or 30 minutes

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

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

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

Match Length: 30 minutes.

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

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

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

Match Length: 15, 20 or 30 minutes.

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

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

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

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

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

== Plosileague ==

'''League is dead.'''

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

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

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

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

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

IRC Channel: None.

Match Length: First to 10 kills.

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

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

IRC Channel: None.

Match Length: Depends on which map you play on.

Rules: Depends on which map you play on.

== BZSoccer League ==

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

IRC Channel: ##divi

Match length: 15 minutes

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

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

Getting Started

2009-06-07T07:31:07Z

A Meteorite: Undo revision 5859 by 208.184.6.27 (Talk)

This article covers the basics of getting started with BZFlag. It is intended for new players who have just found the game and require assistance. More detailed help can be found on our [[Getting Help]] page.

==Getting Started==
These simple steps have been designed to allow new users to begin playing the game as quickly as possible.

===Downloading and installing the game===

The main thing users need to play is the game software. Users can [[Download]] the software for a number of different [http://en.wikipedia.org/wiki/Operating_system|operating systems].

====Windows====
The most common operating system for players is Microsoft Windows. A simple installer can be found at, http://prdownloads.sourceforge.net/bzflag/bzflag-2.0.10.exe?download . Simply Double click the downloaded file to install the game.

====Mac OSX====
The next most popular system for players is Apple's MacOS X for the Macintosh family of computers. The version for macs can be found at, http://prdownloads.sourceforge.net/bzflag/BZFlag-2.0.10.dmg . Simply drag the BZFlag icon from the extracted DMG to your Applications folder to install the game.

====Linux====
The project does not distribute a premade binary package for linux, but many linux distrobutions have BZFlag in their package management systems ( APT, YUM, emerge, etc.. ). Linux users can always build the game from the source code. Please see the [[Download|downloads]] page for more information.

===Registering a callsign(Optional)===
It is not mandatory to register a callsign ( the name a player uses in-game), but it is highly recommended.

A few of the benefits of registering are:

* The callsign is reserved, and can not be used by any other player.
* Registered users post on the BZFlag forums
* Registered users can join global groups, and leagues.
* Many servers require registration to play.

Users that wish to register can simply do so on the BZFlag forums at [http://my.bzflag.org/bb/profile.php?mode=register my.bzflag.org/bb]

===Running the game===

Once the game is installed, it must be run to play.

====Windows====
Windows users that have installed the game with the provided installer will find a shortcut to the game in the start menu, under program files. Users simply have to click this shortcut to start the game.

====Mac OS X====
Macintosh users simply have to double click the BZFlag icon that they dragged to their Applications folder to start the game.

====Linux====
Linux, and other unix based platforms can start the game by typing the command '''bzflag''' in a terminal.

===Joining a game===
When the game is first started it will show the main menu screen. Users navigate the menu by using the Up and Down arrow keys to highlight a menu item, and using the enter key to select and activate the highlighted item.

{|
|-
|
====Main Menu====
The main menu includes a number of menu items that lead to sub menus. The most important menu for new players is the '''Join Game''' item.
|[[Image:MainMenu.png|right|thumb|300px|The Main Menu]]
|-
|

====Join Game Menu====
Users wishing to join an internet game in progress should choose the '''Join Game''' item from the main menu.

On the first run of the game software all the fields in the Join Menu will be empty. Players need to use the arrow keys to highlight the '''Callsign''' item and input a player name. This name will be how other players see the user. Registered users should use the same callsign that they registered when playing. Registered users should also enter in their password into the item marked '''password'''. This password is only used for to verify your identity and is NEVER sent to the game server.

The e-mail string is optional and usually left blank by many users.

Once this information has been entered, the user must choose a server to play on. Servers are games of BZFlag that are hosted on the internet. There are over 200 servers to choose from. A listing of all the servers can be found by highlighting the '''Find Server''' menu item to bring up the server list.

|[[Image:JoinGame.png|right|thumb|300px|]]
|-
|
====Server List====
The server list menu shows a listing of all publicly available internet games. The list is sorted by the number of players on each server at any time, and will dynamically change over time. The servers with the highest player counts will always be at the top of the list.

The various servers can be highlighted using the arrow keys, and additional information about the highlighted game will be shown at the top of the screen. Once the user has chosen a server to join they must hit the enter key to select the server and return to the Join Game Menu.

|[[Image:ServerList.png|right|thumb|300px|The Serverlist]]
|-
|

====Entering a Game====
When a server is choosen from the Server List, it's information will be automatically entered into the appropriate fields in the Join Game menu. The user may then choose a team color, or leave the setting on automatic if they wish the server to assign them to a team.

When all the information is entered, the user simply has to choose connect menu item, and they will join the game. If additional textures or resources are needed to join the game, they will be downloaded automatically.
|-
|

====Playing BZFlag====
Once the user has joined the game they will be able to enjoy the gameplay that has made BZFlag one of the most popular open source games in history.
|-
|

=====Controls=====
The basic controls for the game are rather simple.

By default the mouse is used for movement. Moving the mouse up and down will move the tank forwards and backwards, while moving the mouse left and right will cause the tank to turn in that direction. Returning the mouse to the center of the screen will cause the tank to stop moving.

The left mouse button is used to fire the tank's weapon.

Optionally the keyboard can be used. The arrow keys control movement in the same way as the mouse, and the space bar is used to fire the weapon.

Some servers offer a feature that allows tanks to jump. The ''tab'' key is used to start a small jump into the air. When jumping a tank normally can not change its speed or direction until it lands. Depending on the map, it may be possible for tanks to jump and land on various world objects and continue to fight.
|-
|

=====Objective=====
BZFlag is a team game, and has various objectives depending on the game type.

The default game type is '''Free For All''', commonly abbreviated as ''FFA''. This mode is similar to a team death match in other first person shooting type games. The objective is to destroy as many tanks as possible on other teams, while minimizing your own losses. Tanks are destroyed by being shot, in most cases one shot is all it takes to kill an enemy tank.

Capture the Flag is another common game type. Its objective is to pick up the flag from an opposing team and return it to your base. Tanks are destroyed the same way as in FFA games.

The least common type of game is '''Rabbit Hunt'''. In this game mode, one user is a white-colored '''rabbit''' tank, and everyone else is a orange-colored '''hunter''' tank. The '''hunter''' tank(s) must chase and kill the rabbit tank. The '''hunter''' tank which kills the '''rabbit''' tank then becomes the '''rabbit''' tank.
|-
|

=====Non-Standard Teams=====

Usually, you may not shoot members of your own team. But, there is one exception to this rule, called the '''rogue''' team. '''Rogue''' tanks are black in the view window, and yellow on the radar. They may shoot their "teammates", and gain points for it. This is because '''rogue''' tanks are each on a one-man team of their own. '''Rogue''' tanks are usually found on '''Free For All''' maps, but are occasionally found on '''CTF''' maps.
|-Rogue.
|

=====Flags=====
There are four different kinds of flags on an average server:
* Team flags are colored to correspond with the teams on the map. The idea is to grab the other team's flag and bring it back to your base.
* Superflags are "power ups" for your tank. Some examples of superflags can be '''Guided Missile''' (Allows your tank to lock onto and shoot others), '''laser''' (Allows your tank to shoot an infinitely fast and long laser beam), and '''Stealth''' (Your tank does not appear on radar).
* Bad Flags restrict the movement or actions of your tank. Some bad flags are ''''No Jumping, Obesity, Trigger Happy,''' and '''Left turn only.'''
* Antidote flags are flags that appear only when you have a bad flag. Driving over an antidote flag removes the bad flag from your tank.
|-
|

=====Customizing Controls=====
You can alter most of the controls in the menu (or, if you prefer, by editing the BZFlag config file.)
In the menu it is located at Options > Input settings > Key mapping

To assign a keystroke, mouse button or joystick button to a particular command select the command with Up or Down arrows, press Enter and press the keystroke or button you wish to associate with that command.
You can assign two different keystrokes/buttons to a given command, by repeating the assignment process.

Note: you can assign a keystroke or button already in use for a different command, but if you do remember that the old command will be unmapped..

To delete an assignment select the command with Up or Down arrows and press Delete.
If the command has two assignments, the first (leftmost) assignment is deleted, and the second (rightmost) assignment takes its place.

|-
|

=====Interface Elements=====
Most of the interface elements can be changed in the GUI settings, or by editing the config file.
|-
|

======Scoreboard======
Once a player has joined a server, they should notice a number of things, including the scoreboard.

Internet games commonly feature between 5 and 20 players. The names of these players will be listed in the scoreboard on the left hand side of the screen. The scoreboard can be hidden and shown by using the ''S'' key. The scoreboard is usually set up to show a players name, score, teamkills, email string, flag, kills/deaths, and the amount of kills/deaths you have scored against that player. For example, in this scoreboard, player "Andrey" has a score of 2, 0 teamkills, and email string of "Andrey@andreypc", has the SW (shock wave) flag, has 8 kills, 6 deaths, and has been killed by player "me1" 0 times, and has killed player "me1" once. Flags whose names are in white are powerful flags. Team flags are always the color of that team on the scoreboard. Other flags are just the same color as the player using them.

|[[Image:Scoreboard.jpg|right|thumb|300px|The Scoreboard]]
|-
|
======Team Scoreboard======
There is also a scoreboard for team scores. In FFA this shows the kills, deaths, and overall score. In CTF this shows the amount of flags that team has captured, and the amount of times their flag was captured, and the score. Also, to the right is the amount of players on that team. The rogue team is never included on the team scoreboard.
|[[Image:Teamscoreboard.jpg|right|thumb|300px|The Team Scoreboard]]
|-
|

======Radar======
The [[Radar]] (In the bottom left), shows a bird's eye, 2d view of the map. This is useful for dodging bullets, and seeing where other players are in relation to the users' tank. The user's tank is displayed in the center of the radar, in white. Two lines from the user's "blip" on the radar represent the user's FOV (Field of view). The user's bullets are also displayed in white. Other teams are shown on the radar in their respective color, red shown in red, green shown in green, etc. The rogue team is shown in yellow. Flags are shown as little x's, and team flags as colored x's. A square is also around each radar "blip." This represents height. The larger the square, the higher something is. If a "blip" has an X through it, that tank has a flag.

|[[Image:Radar.jpg|right|thumb|300px|The Radar]]
|-
|

====Sportsmanship====

When playing BZFlag, it is important to keep a few simple rules in mind:

* Players should never shoot tanks on their own team (except for the rogue players).
* Players should be civil to other players in all respects.

|[[Image:Screenshot1.jpg|right|thumb|300px|A Screenshot of a standard 2.0.9 client playing on Missile War 2]]
|}

Master Ban

2009-06-07T07:30:02Z

A Meteorite: Undo revision 5857 by 208.184.6.27 (Talk)

The Master Ban list is an administration tool used to prevent abuse of the BZFlag server network.

==Overview==
The master ban list is an opt-out system for all public game servers that downloads an additional ban file. This ban file contains the static IPs of a small number of players who have been disruptive to the gaming network as a whole.

==Usage==
A public server does not have to do anything to use the Master Ban list, it is loaded automatically at server start for any server that uses the '''-public''' command line option. Servers that do not wish to use the Master Ban list can add the '''-noMasterBanlist''' option and [[BZFS]] will not attempt to load the list.

==Players on the Master Ban List==
The players on the Master Ban list were added because they engaged in disruptive behavior across a large number of servers, or attempted to disrupt the global network services (such as the [[Global Registration]] System, [[List Server]], or [http://my.bzflag.org/bb Forums]). All members of the Master Ban list have static IP addresses. No user with a dynamic IP address will be added to the Master Ban list, as the possibility of banning an innocent user is too great. An exception to this rule for single addresses in dynamic ranges may be made temporarily during periods of severe disruption at the discretion of the developers.

===Behavior for which you can be Masterbanned (i.e. "Disruptive Behavior" above)===
* Cheating on multiple game servers
* Spamming inappropriate (including, but not exclusively, commercial advertisement, hateful, vulgar, or racist) messages on multiple game servers
* Cracking attempts, denial of service attacks, or exploitation of vulnerabilities against multiple game servers
* Cracking attempts, denial of service attacks, or exploitation of vulnerabilities against network resources (i.e. List server, Bulletin boards, IRC channel, Global authentication servers, Wiki)

===Behavior for which you cannot be Masterbanned===
* Cheating on, attacking, or exploiting a single game server.
** Rationale: fabrication of evidence is too easy (and therefore, possibility of being "framed" or "set up" is too high)
* Violating server rules other than cheating or spamming on game servers (e.g. language violations).
** Rationale: it is not the purpose of the master ban list to enforce local server rules. Bans for this behavior should be handled at the server level
* Violating rules on network resources (i.e. spamming, engaging in personal attacks, or using foul language on the bulletin boards or IRC channels)
** Rationale: if the violations you committed are not related to playing and you do not pose a hazard to the servers, you should be allowed to continue to play. Note, however, that you will still be banned from whatever resources you have abused and potentially others that we feel you are likely to abuse.

==Master Ban List Management==
Write access to the Master Ban list is limited to developers and community members with [[BZFlag SVN|SVN]] commit access. The list is stored in SVN for history tracking. All additions to the list are handled via the SVN system, so they are logged for review. The Master Ban list can be viewed at http://www.bzflag.org/master-bans.txt . All changes to the list can be viewed at http://bzflag.cvs.sourceforge.net/bzflag/admin/master-bans.txt?view=log .

===Getting Off the Master Ban List===
Users who are on the list and feel they should not be, or would like to be removed, should attempt to contact the project administrators as soon as possible. They should be willing to discuss how they got on the list and what they can do to get off the list. If they are guilty of the actions that got them on the list, they should be ready to explain why the administration staff should remove them from the list. They should also remember that playing is a privilege and not a right. The administration staff is willing to discuss Master Ban issues with anyone who is willing to discuss the matter in a civil manner.

===Getting Someone On the Master Ban List===
The list is only intended for network wide abusers with static IP addresses. In all other cases local server bans will take care of the abuser. Comments from server owners are generally the only ones considered when reporting a master ban candidate. Players that feel a user should be master banned should take the issue up with the owners of the servers on which the disruptive behavior has been observed.

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

==External links==
[http://www.bzflag.org/master-bans.txt Master Ban List]

[http://bzflag.cvs.sourceforge.net/bzflag/admin/master-bans.txt?view=log Master Ban Change Log]

[[Category:Server Security]]

Master Ban

2009-06-07T07:29:15Z

A Meteorite: Undo revision 5856 by 208.184.6.27 (Talk)

The Master Ban list is an administration tool used to prevent abuse of the BZFlag server network.

==Overview==
The master ban list is an opt-out system for all public game servers that downloads an additional ban file. This ban file contains the static IPs of a small number of players who have been disruptive to the gaming network as a whole.

==Usage==
A public server does not have to do anything to use the Master Ban list, it is loaded automatically at server start for any server that uses the '''-public''' command line option. Servers that do not wish to use the Master Ban list can add the '''-noMasterBanlist''' option and [[BZFS]] will not attempt to load the list.

==Players on the Master Ban List==
The players on the Master Ban list were added because they engaged in disruptive behavior across a large number of servers, or attempted to disrupt the global network services (such as the [[Global Registration]] System, [[List Server]], or [http://my.bzflag.org/bb Forums]). All members of the Master Ban list have static IP addresses. No user with a dynamic IP address will be added to the Master Ban list, as the possibility of banning an innocent user is too great. An exception to this rule for single addresses in dynamic ranges may be made temporarily during periods of severe disruption at the discretion of the developers.

===Behavior for which you can be Masterbanned (i.e. "Disruptive Behavior" above)===
* Cheating on multiple game servers
* Spamming inappropriate (including, but not exclusively, commercial advertisement, hateful, vulgar, or racist) messages on multiple game servers
* Cracking attempts, denial of service attacks, or exploitation of vulnerabilities against multiple game servers
* Cracking attempts, denial of service attacks, or exploitation of vulnerabilities against network resources (i.e. List server, Bulletin boards, IRC channel, Global authentication servers, Wiki)

===Behavior for which you cannot be Masterbanned===
* Cheating on, attacking, or exploiting a single game server.
** Rationale: fabrication of evidence is too easy (and therefore, possibility of being "framed" or "set up" is too high)
* Violating server rules other than cheating or spamming on game servers (e.g. language violations).
** Rationale: it is not the purpose of the master ban list to enforce local server rules. Bans for this behavior should be handled at the server level
* Violating rules on network resources (i.e. spamming, engaging in personal attacks, or using foul language on the bulletin boards or IRC channels)
** Rationale: if the violations you committed are not related to playing and you do not pose a hazard to the servers, you should be allowed to continue to play. Note, however, that you will still be banned from whatever resources you have abused and potentially others that we feel you are likely to abuse.

==Master Ban List Management==
Write access to the Master Ban list is limited to developers and community members with [[BZFlag SVN|SVN]] commit access. The list is stored in SVN for history tracking. All additions to the list are handled via the SVN system, so they are logged for review. The Master Ban list can be viewed at http://www.bzflag.org/master-bans.txt . All changes to the list can be viewed at http://bzflag.cvs.sourceforge.net/bzflag/admin/master-bans.txt?view=log .

===Getting Off on Master Ban List===
Users with a decidedly sadistic bent, who experience arousal while viewing the list and feel they cannot contain their excitement are encouraged to stimulate themselves to orgasm while viewing the list of dissenters. If users would like advice on how to perform these actions in details then they should attempt to contact the project administrators as soon as possible. They should be willing to discuss how best to achieve orgasm while attempting auto fellatio. They should also remember that the homo-centric advice dispensed by the project administrators is a privilege and not a right. The administration staff is willing to discuss Masturbation issues with anyone who is willing to discuss the matter in a civil manner.

===Getting Someone On the Master Ban List===
The list is only intended for network wide abusers with static IP addresses. In all other cases local server bans will take care of the abuser. Comments from server owners are generally the only ones considered when reporting a master ban candidate. Players that feel a user should be master banned should take the issue up with the owners of the servers on which the disruptive behavior has been observed.

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

==External links==
[http://www.bzflag.org/master-bans.txt Master Ban List]

[http://bzflag.cvs.sourceforge.net/bzflag/admin/master-bans.txt?view=log Master Ban Change Log]

[[Category:Server Security]]

Boxy War

2008-09-09T04:00:05Z

A Meteorite: /* Map History */ spelling

[[Boxy War]] is a Blue vs Red 2 team CTF map.
==Description==
The bases are two castles situated across from each other with two smaller structures containing SW flags on their left and right. Inside the base, L flags are found on the first two levels, a sniper spot on the third level, and SE, MQ, CL, and ST flags on the top level. GM flags are located in front of the bases on small boxes attached to the bases. Three cones are located in the base to prevent laser ricochets from becoming out of hand. Giant pyramids can be found between the two bases along with an X shaped stucture supporting a box containing OO and 1 G flag. This is surrounded by transparent trapezoidal shaped meshes.
==Strategy==
*Take control of the middle section. Geno is critical to this map, the team with the middle has it and as long as they keep it, the enemy will have a hard time winning.
*Have laser snipers everywhere. Have at least 1 on each side of the base aimed at the upper exit to their base and preferable also have 1 on each of the enemy's SW buildings.
Once these two keys are in place, your opponents will have a hard time even leaving their base.
==Flag Placement==
The flag should either be placed on the top section of the base on the back wall, or in one of the bottom corners of the base. Each spot has its own pros and cons.
====Top Pros====
*Hard to reach
*Time consuming for enemy
====Top Cons====
*Easy exit for enemy
*Hard to shoot enemy once at the flag
====Bottom Pros====
*Easy to shoot enemy
*Hard escape for enemy
====Bottom Cons====
*Easy for enemy to grab flag
==Map History==
The original Boxy War was created in late 2005 by BinarySpike. The base design was fundamentally different than the current incarnation of Boxy War, along with significantly different corners and the lack of the SW flag. Several months later, development of the map took on a new beginning by [[User:A Meteorite|A Meteorite]] and [[User:TD-Linux|TD-Linux]], and the previous map was totally scrapped – leaving only some of the basic principles in place.

In July of 2006, pyramids around the Geno area were replaced with a clear mesh containing the Boxy War logo along with the removal of bad flags from the middle, replacing them with OO flags. Blue beams known as plasma forks were also added to the top section, turning you tank into "A hearty soup of ions" when touched.

In the Fall of 2006, L flags and a new spawn zone was added to each side of the base due to the challenge of exiting base when on the losing team.

In late 2006 or early 2007, the map went through its biggest change. OO flags around geno were replaced with obesity flags. These flags could only be removed by leaving the middle section. MQ flags were added on the roof of each castle. Geno was given unlimited shots, but only allowed one kill. Laser was limited to 100 kills. This change to the map, along with a brand new 4 team CTF map, [[Missile War]], sealed the fate of the once popular map.

The changes were reversed after about one month, keeping the MQ flags though, but it was too late, Boxy War was dying in popularity.

==Boxy War Today==
Boxy War is currently hosted at bzfx.net:5222, once again as an official [[BZFX]] map, but only remains slightly popular with small surges of activity.

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

BZFX

2008-06-24T05:38:14Z

A Meteorite: Update

[http://bzfx.net/ BZFX] is a game server network, with a commonality being that they use the same rules and administration. BZFX also runs several development projects and offers both paid and free hosting to others.

= Contacts =
== IRC Channel==
The network maintains an IRC channel on the freenode IRC network [irc://irc.freenode.net/#bzfx #bzfx channel]. This channel is used for most discussions about the network.

== Administration ==
The network is owned and operated by [[User:A_Meteorite|A Meteorite]] and administered by a group of users.
Individual administrators should be contacted for the resolution of issues they are involved in. If a resolution can not be reached, then a user should contact the owner.

Boxy War

2008-06-24T05:36:09Z

A Meteorite: Added more history, fixed some grammar and spelling.

[[Boxy War]] is a Blue vs Red 2 team CTF map.
==Description==
The bases are two castles situated across from each other with two smaller structures containing SW flags on their left and right. Inside the base, L flags are found on the first two levels, a sniper spot on the third level, and SE, MQ, CL, and ST flags on the top level. GM flags are located in front of the bases on small boxes attached to the bases. Three cones are located in the base to prevent laser ricochets from becoming out of hand. Giant pyramids can be found between the two bases along with an X shaped stucture supporting a box containing OO and 1 G flag. This is surrounded by transparent trapezoidal shaped meshes.
==Strategy==
*Take control of the middle section. Geno is critical to this map, the team with the middle has it and as long as they keep it, the enemy will have a hard time winning.
*Have laser snipers everywhere. Have at least 1 on each side of the base aimed at the upper exit to their base and preferable also have 1 on each of the enemy's SW buildings.
Once these two keys are in place, your opponents will have a hard time even leaving their base.
==Flag Placement==
The flag should either be placed on the top section of the base on the back wall, or in one of the bottom corners of the base. Each spot has its own pros and cons.
====Top Pros====
*Hard to reach
*Time consuming for enemy
====Top Cons====
*Easy exit for enemy
*Hard to shoot enemy once at the flag
====Bottom Pros====
*Easy to shoot enemy
*Hard escape for enemy
====Bottom Cons====
*Easy for enemy to grab flag
==Map History==
The original Boxy War was created in late 2005 by BinarySpike. The base design was fundamentally different than the current incarnation of Boxy War, along with significantly different corners and the lack of the SW flag. Several months later, development of the map took on a new beginning by [[User:A Meteorite|A Meteorite]] and [[User:TD-Linux|TD-Linux]], and the previous map was totally scrapped – leaving only some of the basic principles in place.

In July of 2006, pyramids around the Geno area were replaced with a clear mesh containing the Boxy War logo along with the removal of bad flags from the middle, replacing them with OO flags. Blue beams known as plasma forks were also added to the top section, turning you tank into "A hearty soup of ions" when touched.

In the Fall of 2006, L flags and a new spawn zone was added to each side of the base due to the challenge of exiting base when on the losing team.

In late 2006 or early 2007, the map went through its biggest change. OO flags around geno were replaced with obesity flags. These flags could only be removed by leaving the middle section. MQ flags were added on the roof of each castle. Geno was given unlimited shots, but only allowed one kill. Laser was limited to 100 kills. This change to the map, along with a brand new 4 team CTF map, [[Missile War]], sealed the fate of the once popular map.

The changes were reversed after about one month, keeping the MQ flags though, but it was too late, Boxy War was dieing in popularity.

==Boxy War Today==
Boxy War is currently hosted at bzfx.net:5222, once again as an official [[BZFX]] map, but only remains slightly popular with small surges of activity.

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

CommunityAdministrationNetwork/About

2007-11-04T20:43:59Z

A Meteorite: Missed another "administration"

{{CommunityAdministrationNetwork}}

==Overview==
The Community Administration Network is an independent organization of server owners and administrators who have chosen to group together to provide the best possible play experience to BZFlag players.

'''Please note'''
The network is just in it's conceptual stages at this point. Please post any questions, comments, or concerns to the talk page. Also if you are a server owner that would be interested in being a member please also post that to the talk page, we are very interested in knowing who would like to participate.

==Organization==
The Network is made up of servers whose owners have chosen to provide the network administration staff the ability to manage and enforce a specific set of rules on their servers.

Information for users playing on member servers can be found on the [[CommunityAdministrationNetwork/Players]] page.

The network is made up of the following groups:

===Server Owners===
These are server owner/operators that have chosen to participate in the network. The owners have agreed to the rules for servers and have been accepted into the network. They run the CANAdmin plug-in as part of their server setup. Information on the requirements and expectations of server owners can be found on the [[CommunityAdministrationNetwork/Server Owners]] page.

===Field Agent===
These are users chosen from the community to do the day-to-day admin actions on network servers. They are normal players that have agreed to the terms and rules for CAN Field Agents. They use the CANAdmin plug-in on network servers to perform their administration actions. All actions by all agents are logged by the network for review. Information on the requirements and expectations of Field Agents can be found on the [[CommunityAdministrationNetwork/Field Agent]] page.

===Core Administrators===
These are a smaller group of administrators that in addition to the abilities of the field agents, is responsible for arbitrating disputes between players and field agents and for adding or removing field agents when needed. The Core administration team is also responsible for approving and reviewing the servers that make up the network.

===Network Administrator===
The network administrator in addition to being a Core Administrator, is the one person responsible for the entire network. He/she creates the rules to which all other administrators and server owners agree. The network administrator has the power of veto over any action of the other agents but must provide a reasonable explanation, or face the other administrators and agents abandoning the network (making it pointless).

==CANAdmin plug-in==
The network administrators make use of a special plugin that server administrators install to allow network administration. This allows agents to apply network wide warnings, kicks, and bans to users that violate the network rules and regulations. The network agents are only able to enforce the network-specific rules on servers and by default do not have any additional administrative permissions or abilities on any server. A server owner may choose to give network agents additional abilities, but it is not required for network membership.

==Rules==
The network has a very specific set of rules that it applies to servers. This rule set is expected to be a small subset of the rules on any one server. CAN Administrators will only enforce these specific rules by default. Every administrative action (warn, kick, and ban) will be logged with the rule number to which the violation applies, as well as any applicable logs or records needed.

===1) No Cheating===
Users must not use modified clients to gain an unfair advantage over other users. This includes any modification that changes the behavior of a player tank from the release version of the game, or any modification that provides additional information or reaction time to the game.
Examples include (but are not limited to):
* God Mode (un-killable)
* Auto-Aim
* Seeing Stealth or Cloak.
* Jump Modification
* Speed modification
* Tank hit size modification
* Shot end modification
Additional items may be added based on the observations of the administrator. If a user is experiencing network or software problems that may appear to be cheats, then it is up to them to work with the Administration staff and/or the project development to rectify the issue as soon as they are warned. The administration staff will be more then happy to work with the users to determine the cause of any software- or network-related issues. If the issues are network-related and cause the disruption of play with other users, network administrators can request that the user discontinue play on a specific server until such time as network conditions improve. The administrators are expected to speak to the players about the behavior before taking any action to determine its cause.

===2) No Exploiting===
Users must not use in-game features or flaws to gain an unfair advantage over other players. This includes using game features or bugs to create artificial lag spikes, tweaks or changes to the input system, or the operating system / drivers to create positional discrepancies or speed changes. If the administration staff asks a user to discontinue an action that is causing a problem, the user is expected to refrain from that action. This includes the use of external applications to modify the game's internal state or network data.

===3) No Griefing===
Users must not engage in behavior that is disruptive to the play of the game. This includes actions such as intentional team-killing, intentional or repeated genocide of one's own teammates, or capturing your own team's flag in a CTF game. Griefing also includes message spamming, whether private or public. The administration team does understand that isolated accidents do happen and are required to issue warnings before taking actions. Users warned of a particular offense are expected to take care to not repeat the actions, even if they were accidents in the first place.

===4) Minimum Language Rules===
Users are expected to adhere to a set of [[CommunityAdministrationNetwork/DisallowedWords|minimum language rules]] that disallows a set of very specific words when using public or team chat channels. Users are also expected to refrain from attacking or making disparaging remarks about another player's race, religion, gender, disability, ethnicity, employment circumstances, or sexual orientation. The in-game chat is primarily for discussion about the game while playing. Users who are warned for language violations are expected to discontinue use of the offensive language, and continue to play in a civil manner. It should be noted that individual servers can and may have more strict language policies in place that they administer locally. The minimum language policy applies to any content that is displayed to other players including user callsigns, in game e-mail addresses, parting messages, as well as all public and team chat text.

===5) No disruption of public services===
Users are expected to not take actions that would disrupt any of the network's or project's public services. This includes any websites or forums, IRC channels, or servers operated by the network itself, or the
BZFlag project. Actions of this nature are very serious and will not be taken lightly.

==Recommendations==

===Global Registration===
It is highly documented that all users must be globally registered and identified when they play. Unregistered users will be tracked by there IP, hostmask, and other data. Unregistered users may not dispute any administrative action on the network. Unregistered users will not be white listed to get around any IP range or host mask bans that may be in place. It is assumed that honest players will have no problem with registering for the game. Any network agent will be glad to help users get registered with the BZFlag global login system

==Common Questions and concerns==

===Questions===
====Does the network do range bans?====
Yes, the network can and will do IP range bans for dynamic IPs. When possible a BZID ban will be used, but some situations require a range ban. Registered users can be given a white list based on there BZID and be allowed to play on IPs in a banned range.

===What the Network Is===
This is a list of items that describe what the network is meant for:

====The CAN is a group of people:====
The network consists of people - people that the server owners have chosen to trust to enforce a set of rules. It is run by people for people. People are human. It is assumed that people can and will make mistakes on both sides. Mistakes can be fixed as long as both parties are willing to work at fixing the problem in a civil manner.

====The CAN is reasonable:====
Administrators are more then willing to listen to anyone who has been kicked or banned, as long as the user is willing to work with them in a reasonable manner. If a user has an issue that can not be resolved with an administrator, they should take it up to the next level of administration as indicated in the organization section above.

====The CAN keeps records, lots of them:====
The CANAdmin plug-in will track all actions done by administrators, and can provide them for review if needed. These records are kept independently of any logging or tracking that server owners choose to do, and are intended to be used by network staff only. This provides a set of checks and accountability for all actions, as well as records of the reasons behind any action.

====The CAN is a team:====
Network administrators work together. Any administrator can work on any problem, regardless of who the issue started with. Administrators are encouraged to work together, with other administrators, and players.

====The CAN works with leagues:====
Since the field agents don't have any control over gameplay commands, and the CANAdmin plug-in doesn't use any of the host server's administration functions, there is no reason why a league server can not also be a CAN member server. The network rules should be compatible as a subset for all leagues.

===What the network is not===

====The CAN is not your mom====
The network does not exist to arbitrate small disagreements in playstyle or behavior. It will not make Billy stop touching your flag. It does not exist to decide what is or isn't fair in games. The rules that the network enforces have nothing to do with gameplay or any specific game ruleset. The CAN will not and cannot do such gameplay actions as resetting flags, balancing teams, or changing server variables.

====The CAN does not take over a server.====
By default CAN administrators do not have access to a server banlist, groups, passwords, users, or any other abilities. All network actions are applied by the CANAdmin plug-in and do not affect the server settings in any way.

====The CAN is not a democracy.====
The network is a service provided by its administrator and trusted staff. Server owners can choose to allow the CAN onto their servers, or they can choose not to. The network is not designed or run by any sort of committee. It is run following the specific rules set forth in this document.

====The CAN is not the master ban list.====
While some of the network administration staff are also part of the BZFlag project, the network itself is not. Network bans are not part of the global master ban list that is applied by default to all public servers. Actions against the project itself may result in CAN administrative action, but the reverse is not always true.

== See Also==
[[CommunityAdministrationNetwork/Server Owners]]

[[CommunityAdministrationNetwork/Field Agent]]

[[CommunityAdministrationNetwork/Core Administrators]]

[[CommunityAdministrationNetwork/Players]]

[[CommunityAdministrationNetwork/CANAdmin Plug-In]]

CommunityAdministrationNetwork/Field Agent

2007-11-04T20:42:49Z

A Meteorite: Misspelled "administration"

{{CommunityAdministrationNetwork}}

==Overview==
This page describes the information needed by Field Agents for the [[CommunityAdministrationNetwork/About|Community Administration Network]].

==Requirements==
Field Agents must meet the following requirements.

===Global Registration===
Field Agents must have a valid global name and login, with valid contact info.

===Age===
Field Agents must be at least 17 years of age, or be approved by the network administrator.
Field Agents must report their correct age to the administration staff when asked.

===Record===
Field Agents must have a clean record on the master ban list, and not have any outstanding bans or issues on any CAN servers.

===Sponsorship and approval===
Field Agents must be sponsored by at least one Core Administrator. 3 Field Agents can petition a Core Administrator to sponsor a new Field Agent. All new field agents must be approved by the Core Administrators, or the Network Administrator.

==Behavior==
Field Agents are expected to follow a behavior guideline when playing on CAN member servers.

===Follow the Rules===
Field Agents are expected to follow the same rules as players when playing. Violations of these rules will lead to removal from the administration staff, as well as possible network administrative actions ( bans ).

===Be Civil===
Field Agents are expected to conduct their administration in a calm and civil manner. They should not let anger or personal feelings get in the way of their administration duties. They are expected to not hold any "grudges" against specific users. All discussions, arguments, or disagreements with players over administrative issues should happen in private in order to disrupt the play for others as little as possible. Field Agents must remember that it is their job to help all users play the game and have fun.

===Give the benefit of the doubt===
Field Agents are expected to give a user the benefit of the doubt when dealing with an initial violation. Users should always be approached with private chat text to ask them first to stop the behavior that is causing the violation. The agent should explain what the behavior is, why it is a violation, and be willing to help the user resolve the issue to the best of their ability. Field Agents are expected to remove bans on users who have spoken with them or other administration staff in a civil manner and have agreed to not repeat their offenses. Users that abuse this will not be given that courtesy a second time.

===Use the least necessary action to resolve an issue===
Field Agents are expected to resolve issues with the "lowest" possible administrative action. They should not kick when a silence should work, not ban when a kick would do the same. Bans should be the last resort as they are network wide. Field Agents are expected to warn before all actions. The CANAdmin plug-in will track and enforce the warning of people before higher level actions are allowed ( kick and ban ). Field Agents are expected to work with all users to resolve any violation issues, and never simply "blow them off". They should refer the user to the Core Administrators if a suitable resolution can not be found.

===Use CAN admin abilities only for network violations===
All admin actions on servers must be in response to a violation of one of the six network rules. No other use of the network admin functions are permitted. The CANAdmin plug-in will require the rule number that is in violation for all actions. Field Agents may be granted additional abilities by server owners, and be asked to enforce additional rules. If the Field administrator agrees to this, then he/she must use the server's local administration system to enforce those additional rules, and not the network system.

Violations of rule 5, the minimum language rules, must violate the very specific conditions set forth in the rule. Interpretations of the rule should strictly adhere to the rule as stated. Flexible interpretations based on additional language that is not mentioned in the rule, personal distaste, or beliefs, are not allowed. Violations of rule 5 must be very clear-cut before ban level action is taken. Most users who will skirt the edges of rule 5 will most likely break another rule in the process, usually rule 4. Simple violations of rule 5 can be handled with a simple net silence command after the required warnings. While annoying, violations of rule 5 have the least affect on the game, and are the simplest to resolve, even for regular users ( everyone can use the silence command ). Field Agents are expected to understand that different people have different levels of tolerance for language, and may find things more or less offensive then they personally do. Common saying that may have religious overtones, are not considered offensive. Attacks must be very directed against very specific subjects. Terms or abbreviations like "OMG", "WTF", and the like, are common enough in language that they are not meant as offensive they are simply exclamations. Any action that is simply taken as "blasphemy" in any religion is not worthy of action and should be ignored, unless the player uses the text in a violation of rule 4 (spamming).

Agents that abuse the network admin features for their own personal reasons, will be removed as network agents, and possibly banned from the network depending on the severity of the actions. All network actions are logged with the BZID of the admin who applied them. If need be the Core Administrators can remove any and all network actions caused by any Agent.

==Administrative actions==
Field Agents may take the following administrative actions on any member server. All actions are logged and recorded with the administrator that performed the action, and the server that they were applied on.

===NetWarn===
Usage
'''/NetWarn''' ''Rule'' Player ''Comment''

This action will notify the specified player that they are in violation of the specified rule. The warn action will be logged with the central network database. The user will also receive a BZBB PM with the warning and link to the network rules. Multiple warnings can be issued but must have at least 1 minute duration in between them to allow the user time to discontinue the action. The CANAdmin plug-in will not accept warnings that violate the wait duration.

===NetActivityList===
Usage
'''/NetActivityList''' Player

This action will list the history of warnings, kicks, bans, silences, and other admin actions stored for the player across all network servers. Each action will list the action, rule violated, the admin, and the comment given at the time of the action. Players have access to a simplified version of this command that will list all the actions for their call sign, but not any others. Server Admins (anyone with an @) also have access to the full version of this command for informational use.

===NetSetIdent===
Usage
'''/NetSetIdent''' ''SINGLE | CLASSB | CLASS C | HOST | HOSTRANGE '' Player
This action is only available for unregistered players. It will set the tracking mode for the IP address of the specified player.
SINGLE mode will use the full IP of the user for detection. This is the default mode.
CLASSB mode will use the the first 2 sections of an IPV4 address for detection. This is the same as a XXX.YYY.*.* range.
CLASSC mode will use the the first 3 sections of an IPV4 address for detection. This is the same as a XXX.YYY.ZZZ.* range.
HOST mode will use the reverse DNS host name for detection.
HOSTRANGE mode will use the last 3 sections reverse DNS name for detection. This is the same as a *.ISP.DOMAIN.TLD range.
Agents should use the smallest possible range when dealing with unregistered players.

===NetUserInfo===
Usage
'''/NetUserInfo''' Player
This action will return all stored user info for the current player, including there current IP, BZID, Tracking Mode, warn count, ban status/times, and there hostmask. Server Admins (anyone with an @) also have access to the full version of this command for informational use.

===NetSilence===
Usage
'''/NetSilence''' ''Rule'' Player ''Comment''
This action will block all chat for the specified user on all network services for a period of one hour. The action will also be logged the same way as a warning.

===NetKick===
Usage
'''/NetKick''' ''Rule'' Player ''Reason''
This action will force the specified user to disconnect from the server, and disallow any new connections to any network server for a period of no less then 10 minutes. The Kick is network wide, and will prevent immediate rejoins. Users will be given a countdown time each time they attempt to reconnect. This action is logged, and will not be performed by the CANAdmin plug-in unless the user has received 3 or more warnings.

===NetBan===
Usage
'''/NetBan''' ''Rule'' Player ''Reason''
This action will force the specified user to disconnect from the server and disallow any new connections to any network server for a period of 336 hours ( 14 days, aka. 2 weeks ). This is the harshest action a Field Agent can take, and should only be used as a last resort. Like the kick, the action is logged and can not be applied unless the user has received 3 warnings.

===NetBanCritical===
Usage
'''/NetBanCritical''' ''Rule'' Player ''Reason''
This action will force the specified user to disconnect from the server and disallow any new connections to any network server for a period of 336 hours ( 14 days, aka. 2 weeks ), just like a regular NetBan command. In addition this command will flag the ban action for review by the Core Administration team for a possible longer term BAN. This command should not be used lightly or frequently by the Field Agents, and should only be reserved for the worst offenders. Field Agents that abuse this command will face administrative action. Like the NetBan, the action is logged and can not be applied unless the user has received 3 warnings.

===Tracking Mode===
All commands that apply limits to users across servers will use ether the BZID of the user, or if unregistered the current tracking mode. If the tracking mode represents a range of IPs, then any user who isn't registered in that IP range will be blocked. Agents need to check and set the tracking mode using ''/NetSetIdent'' before applying any actions. The tracking mode will be stored with the user name of the player in the central database.

CommunityAdministrationNetwork/Server Owners

2007-11-04T20:41:38Z

A Meteorite: Misspelled "administration"

{{CommunityAdministrationNetwork}}

==Overview==
This page describes the information needed by server owners who are part of the [[CommunityAdministrationNetwork/About|Community Administration Network]].

==Membership Requirements==

Membership as a CAN server is rather simple, and requires the server owner to agree to a few small things, and install a single plug-in.

===Publicly List===
CAN is only for public servers. It is not available for private servers, due to its link with global authentication and web-based services.

===Endorse Global Authentication===
Running a CAN server means that the server owner agrees to use the global registration system. The CANAdmin plug-in will notify unregistered users that they should register, and provide a URL with instructions on how to register. The CANAdmin plug-in will also disallow any unregistered user, using a registered callsign to spawn, or be on the server for more then 5 min. Server owners should also have and use a global username.

===Provide a contact name and e-mail===
The CAN system needs a contact name and e-mail for each server or group of servers that it runs. This is so that the administration staff can contact the server owners if need be, and for the CAN website to send automatically generated usage/action logs every week. Servers with invalid contact information will be removed from the network.

===Provide a valid domain name and port for each server running===
The CAN system needs to know the names and ports of each server that is run in order to verify its membership in the network.

===Run a minimum version of the BZFS server===
In order for the CANAdmin plug-in to work, it will require a specific version of BZFS. Server owners that can not build their own BZFS simply need to ask, and the network staff can work with you to get a version that is compatible with the required server.

===Understand the service===
It is important that each server owner understand what services are and are not being offered by the network, as well as understanding what responsibilities do and don't come with network membership. Being a CAN member server does not automatically confer any network administration status or abilities to the server owner. While many server owners would make fine field agents or core administrators and may be asked to participate in the network in those positions, they will not be judged for those positions solely on their ownership of a server. Field Agent positions have their own set of criteria for membership and they will be chosen for those alone. Server owners do not lose any local administration ability by becoming a CAN member server.

==Actions that will result in membership termination==

There is a small number of actions that will result in the termination of the membership agreement with a server.

===Modification of the CANAdmin plug-in===
A server owner should never need to modify the plug-in, or change it in any way. Use of a modified plug-in can result in the removal of a server from the network. If a server owner requires additional features from the plug-in, they should contact the administration staff, so the features can be worked into the base plug-in code.

==Disputes with Administration actions==

The administration team is more than happy to work with server owners to resolve any issues or disputes that they may have with the actions of its agents. Accountability of agent actions is a primary goal of the network. If a server owner has any issue with an action, it is best that they talk to the administration team about it as soon as possible. Issues such as a "rogue agent" or a misplaced ban are taken very seriously by the network and the admin staff will do its best to have it resolved as soon as possible. If need be, the core administrators can "undo" all the actions of specific agents.

The administration staff asks that server owners not block access to the server for any of its agents except in the worst of circumstances, and that it not override the actions of the administration staff, as it will prevent the network from doing what has been agreed upon. If a server owner feels they must take actions such as these, the admin staff highly recommends opening a dialog as soon as possible.

Server owners are free to unload or remove the CANAdmin plug-in at any time to leave the network at their own discretion. The Core Administrators and the Network Administrator reserve the right to remove any server from the CAN network at any time, with notification.

CommunityAdministrationNetwork/Players

2007-11-04T20:40:01Z

A Meteorite: Misspelled "administration"

{{CommunityAdministrationNetwork}}

==Overview==
This page describes the information needed by players to play on servers that are part of the [[CommunityAdministrationNetwork/About|Community Administration Network]].

==Requirements==
Players on network servers must only meet 2 requirements.

===Global Registration===
Players are highly recommended to a valid global user name and login, and play using that name. Unregistered users may subject to limitations in play on many servers, and also loose the ability to dispute any actions of the network.

===Follow the Rules===
Players are expected to follow the 6 network rules as they are specified in the [[CommunityAdministrationNetwork/About#Rules|Community Administration Network]] Document. Failure to follow these rules can result in administrative actions.

==Disputes==
Players that have a dispute are expected to work with the administration staff to resolve the dispute in a calm and civil manner in private. The admin staff will gladly work with players to resolve any technical, network, or software issues that may cause violations of any of the rules. The admin staff has a good working relationship with the project developers and will ask them to assist in diagnosing any problems. Players are expected to assist the admin staff in resolving the issues so that everyone can have a fun game.

If a dispute is unable to be resolved by the Field Agents, the player can bring the issue to the attention of the Core Administrators. The Core Administrators can be contacted via the following means.

* <SOME EMAIL ADDRESS WE PICK>
* the ##CommunityAdminNetwork IRC channel on irc.freenode.net:6667
* BZBB PM to any core member ( list them somewhere ).

Issues that players may have with the Core Administration team should be addressed to the Network Administrator directly.

==Questions==

===I would like to help out and be a field agent, what do I do?===
The answer to this question is complex. It is important to understand exactly what a field agent does before a player decides they wish to apply to the network. All users should be aware of the requirements, and expected behaviors of a field agent as well as the full ruleset for the network. The [[CommunityAdministrationNetwork/Field_Agent|Field Agent]] guide lists the requirements and behaviors. Players should also have a history of good play on one or more member servers before they even think about applying as a field agent.

Once a player has read and understands all the material, he/she should contact the Administration staff and let them know that he/she is interested in donating his/her time as a field agent. The best way to do this is via the IRC channel, or e-mail. Once he/she has let the staff know, simply wait. Field agents are chosen based on a number of criteria, and need. Pushing, pestering, or bugging people to become an agent, shows that the applicant probably does not meet the behavior needs of field agent. A new field agent must be sponsored by an existing Core Administrator. 3 or more existing field agents can petition the Core Administrators to sponsor a new field agent. Agents are only added if there is a need for more. The network administrator has veto and approval power over all field agents.

When a new field agent is approved, he/she will be asked to read and agree to the field agent agreement form, and fill in valid contact info, age, and verify that he/she has read and understands the network rules and administration policy. He/she will also be trained and tested on the use of the CANAdmin plug-in. After this is completed, the user's BZID will be added to the central database as a field agent. Other field agents or the network administration staff may monitor or review any new or existing field agents actions at any time.

CommunityAdministrationNetwork/About

2007-11-04T20:38:09Z

A Meteorite: Misspelled "administration"

{{CommunityAdministrationNetwork}}

==Overview==
The Community Administration Network is an independent organization of server owners and administrators who have chosen to group together to provide the best possible play experience to BZFlag players.

'''Please note'''
The network is just in it's conceptual stages at this point. Please post any questions, comments, or concerns to the talk page. Also if you are a server owner that would be interested in being a member please also post that to the talk page, we are very interested in knowing who would like to participate.

==Organization==
The Network is made up of servers whose owners have chosen to provide the network administration staff the ability to manage and enforce a specific set of rules on their servers.

Information for users playing on member servers can be found on the [[CommunityAdministrationNetwork/Players]] page.

The network is made up of the following groups:

===Server Owners===
These are server owner/operators that have chosen to participate in the network. The owners have agreed to the rules for servers and have been accepted into the network. They run the CANAdmin plug-in as part of their server setup. Information on the requirements and expectations of server owners can be found on the [[CommunityAdministrationNetwork/Server Owners]] page.

===Field Agent===
These are users chosen from the community to do the day-to-day admin actions on network servers. They are normal players that have agreed to the terms and rules for CAN Field Agents. They use the CANAdmin plug-in on network servers to perform their administration actions. All actions by all agents are logged by the network for review. Information on the requirements and expectations of Field Agents can be found on the [[CommunityAdministrationNetwork/Field Agent]] page.

===Core Administrators===
These are a smaller group of administrators that in addition to the abilities of the field agents, is responsible for arbitrating disputes between players and field agents and for adding or removing field agents when needed. The Core administration team is also responsible for approving and reviewing the servers that make up the network.

===Network Administrator===
The network administrator in addition to being a Core Administrator, is the one person responsible for the entire network. He/she creates the rules to which all other administrators and server owners agree. The network administrator has the power of veto over any action of the other agents but must provide a reasonable explanation, or face the other administrators and agents abandoning the network (making it pointless).

==CANAdmin plug-in==
The network administrators make use of a special plugin that server administrators install to allow network administration. This allows agents to apply network wide warnings, kicks, and bans to users that violate the network rules and regulations. The network agents are only able to enforce the network-specific rules on servers and by default do not have any additional administrative permissions or abilities on any server. A server owner may choose to give network agents additional abilities, but it is not required for network membership.

==Rules==
The network has a very specific set of rules that it applies to servers. This rule set is expected to be a small subset of the rules on any one server. CAN Administrators will only enforce these specific rules by default. Every administrative action (warn, kick, and ban) will be logged with the rule number to which the violation applies, as well as any applicable logs or records needed.

===1) No Cheating===
Users must not use modified clients to gain an unfair advantage over other users. This includes any modification that changes the behavior of a player tank from the release version of the game, or any modification that provides additional information or reaction time to the game.
Examples include (but are not limited to):
* God Mode (un-killable)
* Auto-Aim
* Seeing Stealth or Cloak.
* Jump Modification
* Speed modification
* Tank hit size modification
* Shot end modification
Additional items may be added based on the observations of the administrator. If a user is experiencing network or software problems that may appear to be cheats, then it is up to them to work with the Administration staff and/or the project development to rectify the issue as soon as they are warned. The administration staff will be more then happy to work with the users to determine the cause of any software- or network-related issues. If the issues are network-related and cause the disruption of play with other users, network administrators can request that the user discontinue play on a specific server until such time as network conditions improve. The administrators are expected to speak to the players about the behavior before taking any action to determine its cause.

===2) No Exploiting===
Users must not use in-game features or flaws to gain an unfair advantage over other players. This includes using game features or bugs to create artificial lag spikes, tweaks or changes to the input system, or the operating system / drivers to create positional discrepancies or speed changes. If the administration staff asks a user to discontinue an action that is causing a problem, the user is expected to refrain from that action. This includes the use of external applications to modify the game's internal state or network data.

===3) No Griefing===
Users must not engage in behavior that is disruptive to the play of the game. This includes actions such as intentional team-killing, intentional or repeated genocide of one's own teammates, or capturing your own team's flag in a CTF game. Griefing also includes message spamming, whether private or public. The administration team does understand that isolated accidents do happen and are required to issue warnings before taking actions. Users warned of a particular offense are expected to take care to not repeat the actions, even if they were accidents in the first place.

===4) Minimum Language Rules===
Users are expected to adhere to a set of [[CommunityAdminstrationNetwork/DisallowedWords|minimum language rules]] that disallows a set of very specific words when using public or team chat channels. Users are also expected to refrain from attacking or making disparaging remarks about another player's race, religion, gender, disability, ethnicity, employment circumstances, or sexual orientation. The in-game chat is primarily for discussion about the game while playing. Users who are warned for language violations are expected to discontinue use of the offensive language, and continue to play in a civil manner. It should be noted that individual servers can and may have more strict language policies in place that they administer locally. The minimum language policy applies to any content that is displayed to other players including user callsigns, in game e-mail addresses, parting messages, as well as all public and team chat text.

===5) No disruption of public services===
Users are expected to not take actions that would disrupt any of the network's or project's public services. This includes any websites or forums, IRC channels, or servers operated by the network itself, or the
BZFlag project. Actions of this nature are very serious and will not be taken lightly.

==Recommendations==

===Global Registration===
It is highly documented that all users must be globally registered and identified when they play. Unregistered users will be tracked by there IP, hostmask, and other data. Unregistered users may not dispute any administrative action on the network. Unregistered users will not be white listed to get around any IP range or host mask bans that may be in place. It is assumed that honest players will have no problem with registering for the game. Any network agent will be glad to help users get registered with the BZFlag global login system

==Common Questions and concerns==

===Questions===
====Does the network do range bans?====
Yes, the network can and will do IP range bans for dynamic IPs. When possible a BZID ban will be used, but some situations require a range ban. Registered users can be given a white list based on there BZID and be allowed to play on IPs in a banned range.

===What the Network Is===
This is a list of items that describe what the network is meant for:

====The CAN is a group of people:====
The network consists of people - people that the server owners have chosen to trust to enforce a set of rules. It is run by people for people. People are human. It is assumed that people can and will make mistakes on both sides. Mistakes can be fixed as long as both parties are willing to work at fixing the problem in a civil manner.

====The CAN is reasonable:====
Administrators are more then willing to listen to anyone who has been kicked or banned, as long as the user is willing to work with them in a reasonable manner. If a user has an issue that can not be resolved with an administrator, they should take it up to the next level of administration as indicated in the organization section above.

====The CAN keeps records, lots of them:====
The CANAdmin plug-in will track all actions done by administrators, and can provide them for review if needed. These records are kept independently of any logging or tracking that server owners choose to do, and are intended to be used by network staff only. This provides a set of checks and accountability for all actions, as well as records of the reasons behind any action.

====The CAN is a team:====
Network administrators work together. Any administrator can work on any problem, regardless of who the issue started with. Administrators are encouraged to work together, with other administrators, and players.

====The CAN works with leagues:====
Since the field agents don't have any control over gameplay commands, and the CANAdmin plug-in doesn't use any of the host server's administration functions, there is no reason why a league server can not also be a CAN member server. The network rules should be compatible as a subset for all leagues.

===What the network is not===

====The CAN is not your mom====
The network does not exist to arbitrate small disagreements in playstyle or behavior. It will not make Billy stop touching your flag. It does not exist to decide what is or isn't fair in games. The rules that the network enforces have nothing to do with gameplay or any specific game ruleset. The CAN will not and cannot do such gameplay actions as resetting flags, balancing teams, or changing server variables.

====The CAN does not take over a server.====
By default CAN administrators do not have access to a server banlist, groups, passwords, users, or any other abilities. All network actions are applied by the CANAdmin plug-in and do not affect the server settings in any way.

====The CAN is not a democracy.====
The network is a service provided by its administrator and trusted staff. Server owners can choose to allow the CAN onto their servers, or they can choose not to. The network is not designed or run by any sort of committee. It is run following the specific rules set forth in this document.

====The CAN is not the master ban list.====
While some of the network administration staff are also part of the BZFlag project, the network itself is not. Network bans are not part of the global master ban list that is applied by default to all public servers. Actions against the project itself may result in CAN administrative action, but the reverse is not always true.

== See Also==
[[CommunityAdministrationNetwork/Server Owners]]

[[CommunityAdministrationNetwork/Field Agent]]

[[CommunityAdministrationNetwork/Core Administrators]]

[[CommunityAdministrationNetwork/Players]]

[[CommunityAdministrationNetwork/CANAdmin Plug-In]]

CommunityAdminstrationNetwork/DisallowedWords

2007-11-04T20:35:11Z

A Meteorite: CommunityAdminstrationNetwork/DisallowedWords moved to CommunityAdministrationNetwork/DisallowedWords: Misspelled "administration"

#REDIRECT [[CommunityAdministrationNetwork/DisallowedWords]]

CommunityAdministrationNetwork/DisallowedWords

2007-11-04T20:35:11Z

A Meteorite: CommunityAdminstrationNetwork/DisallowedWords moved to CommunityAdministrationNetwork/DisallowedWords: Misspelled "administration"

{{CommunityAdministrationNetwork}}

== Overview==
This page lists the disallowed words for the network. They are here as a reference. Readers that are easily offended by vulgarity should discontinue reading now.

These words are disallowed as they are most often used in a manner to offend or insult, and have no legitimate bearing on the game.

== Major Words==
Use of these words, variations containing them, or abbreviations implying them is considered a direct violation.

Fuck
Shit
Asshole
Cunt
Motherfucker
Cock

== Minor Words==
Use of these words or their variations in most contexts is considered a direct violation.

Nigger
Hitler
Anal
Bitch

CommunityAdminstrationNetwork/Field Agent

2007-11-04T20:34:41Z

A Meteorite: CommunityAdminstrationNetwork/Field Agent moved to CommunityAdministrationNetwork/Field Agent: Misspelled "administration"

#REDIRECT [[CommunityAdministrationNetwork/Field Agent]]

CommunityAdministrationNetwork/Field Agent

2007-11-04T20:34:41Z

A Meteorite: CommunityAdminstrationNetwork/Field Agent moved to CommunityAdministrationNetwork/Field Agent: Misspelled "administration"

{{CommunityAdministrationNetwork}}

==Overview==
This page describes the information needed by Field Agents for the [[CommunityAdminstrationNetwork/About|Community Administration Network]].

==Requirements==
Field Agents must meet the following requirements.

===Global Registration===
Field Agents must have a valid global name and login, with valid contact info.

===Age===
Field Agents must be at least 17 years of age, or be approved by the network administrator.
Field Agents must report their correct age to the administration staff when asked.

===Record===
Field Agents must have a clean record on the master ban list, and not have any outstanding bans or issues on any CAN servers.

===Sponsorship and approval===
Field Agents must be sponsored by at least one Core Administrator. 3 Field Agents can petition a Core Administrator to sponsor a new Field Agent. All new field agents must be approved by the Core Administrators, or the Network Administrator.

==Behavior==
Field Agents are expected to follow a behavior guideline when playing on CAN member servers.

===Follow the Rules===
Field Agents are expected to follow the same rules as players when playing. Violations of these rules will lead to removal from the administration staff, as well as possible network administrative actions ( bans ).

===Be Civil===
Field Agents are expected to conduct their administration in a calm and civil manner. They should not let anger or personal feelings get in the way of their administration duties. They are expected to not hold any "grudges" against specific users. All discussions, arguments, or disagreements with players over administrative issues should happen in private in order to disrupt the play for others as little as possible. Field Agents must remember that it is their job to help all users play the game and have fun.

===Give the benefit of the doubt===
Field Agents are expected to give a user the benefit of the doubt when dealing with an initial violation. Users should always be approached with private chat text to ask them first to stop the behavior that is causing the violation. The agent should explain what the behavior is, why it is a violation, and be willing to help the user resolve the issue to the best of their ability. Field Agents are expected to remove bans on users who have spoken with them or other administration staff in a civil manner and have agreed to not repeat their offenses. Users that abuse this will not be given that courtesy a second time.

===Use the least necessary action to resolve an issue===
Field Agents are expected to resolve issues with the "lowest" possible administrative action. They should not kick when a silence should work, not ban when a kick would do the same. Bans should be the last resort as they are network wide. Field Agents are expected to warn before all actions. The CANAdmin plug-in will track and enforce the warning of people before higher level actions are allowed ( kick and ban ). Field Agents are expected to work with all users to resolve any violation issues, and never simply "blow them off". They should refer the user to the Core Administrators if a suitable resolution can not be found.

===Use CAN admin abilities only for network violations===
All admin actions on servers must be in response to a violation of one of the six network rules. No other use of the network admin functions are permitted. The CANAdmin plug-in will require the rule number that is in violation for all actions. Field Agents may be granted additional abilities by server owners, and be asked to enforce additional rules. If the Field administrator agrees to this, then he/she must use the server's local administration system to enforce those additional rules, and not the network system.

Violations of rule 5, the minimum language rules, must violate the very specific conditions set forth in the rule. Interpretations of the rule should strictly adhere to the rule as stated. Flexible interpretations based on additional language that is not mentioned in the rule, personal distaste, or beliefs, are not allowed. Violations of rule 5 must be very clear-cut before ban level action is taken. Most users who will skirt the edges of rule 5 will most likely break another rule in the process, usually rule 4. Simple violations of rule 5 can be handled with a simple net silence command after the required warnings. While annoying, violations of rule 5 have the least affect on the game, and are the simplest to resolve, even for regular users ( everyone can use the silence command ). Field Agents are expected to understand that different people have different levels of tolerance for language, and may find things more or less offensive then they personally do. Common saying that may have religious overtones, are not considered offensive. Attacks must be very directed against very specific subjects. Terms or abbreviations like "OMG", "WTF", and the like, are common enough in language that they are not meant as offensive they are simply exclamations. Any action that is simply taken as "blasphemy" in any religion is not worthy of action and should be ignored, unless the player uses the text in a violation of rule 4 (spamming).

Agents that abuse the network admin features for their own personal reasons, will be removed as network agents, and possibly banned from the network depending on the severity of the actions. All network actions are logged with the BZID of the admin who applied them. If need be the Core Administrators can remove any and all network actions caused by any Agent.

==Administrative actions==
Field Agents may take the following administrative actions on any member server. All actions are logged and recorded with the administrator that performed the action, and the server that they were applied on.

===NetWarn===
Usage
'''/NetWarn''' ''Rule'' Player ''Comment''

This action will notify the specified player that they are in violation of the specified rule. The warn action will be logged with the central network database. The user will also receive a BZBB PM with the warning and link to the network rules. Multiple warnings can be issued but must have at least 1 minute duration in between them to allow the user time to discontinue the action. The CANAdmin plug-in will not accept warnings that violate the wait duration.

===NetActivityList===
Usage
'''/NetActivityList''' Player

This action will list the history of warnings, kicks, bans, silences, and other admin actions stored for the player across all network servers. Each action will list the action, rule violated, the admin, and the comment given at the time of the action. Players have access to a simplified version of this command that will list all the actions for their call sign, but not any others. Server Admins (anyone with an @) also have access to the full version of this command for informational use.

===NetSetIdent===
Usage
'''/NetSetIdent''' ''SINGLE | CLASSB | CLASS C | HOST | HOSTRANGE '' Player
This action is only available for unregistered players. It will set the tracking mode for the IP address of the specified player.
SINGLE mode will use the full IP of the user for detection. This is the default mode.
CLASSB mode will use the the first 2 sections of an IPV4 address for detection. This is the same as a XXX.YYY.*.* range.
CLASSC mode will use the the first 3 sections of an IPV4 address for detection. This is the same as a XXX.YYY.ZZZ.* range.
HOST mode will use the reverse DNS host name for detection.
HOSTRANGE mode will use the last 3 sections reverse DNS name for detection. This is the same as a *.ISP.DOMAIN.TLD range.
Agents should use the smallest possible range when dealing with unregistered players.

===NetUserInfo===
Usage
'''/NetUserInfo''' Player
This action will return all stored user info for the current player, including there current IP, BZID, Tracking Mode, warn count, ban status/times, and there hostmask. Server Admins (anyone with an @) also have access to the full version of this command for informational use.

===NetSilence===
Usage
'''/NetSilence''' ''Rule'' Player ''Comment''
This action will block all chat for the specified user on all network services for a period of one hour. The action will also be logged the same way as a warning.

===NetKick===
Usage
'''/NetKick''' ''Rule'' Player ''Reason''
This action will force the specified user to disconnect from the server, and disallow any new connections to any network server for a period of no less then 10 minutes. The Kick is network wide, and will prevent immediate rejoins. Users will be given a countdown time each time they attempt to reconnect. This action is logged, and will not be performed by the CANAdmin plug-in unless the user has received 3 or more warnings.

===NetBan===
Usage
'''/NetBan''' ''Rule'' Player ''Reason''
This action will force the specified user to disconnect from the server and disallow any new connections to any network server for a period of 336 hours ( 14 days, aka. 2 weeks ). This is the harshest action a Field Agent can take, and should only be used as a last resort. Like the kick, the action is logged and can not be applied unless the user has received 3 warnings.

===NetBanCritical===
Usage
'''/NetBanCritical''' ''Rule'' Player ''Reason''
This action will force the specified user to disconnect from the server and disallow any new connections to any network server for a period of 336 hours ( 14 days, aka. 2 weeks ), just like a regular NetBan command. In addition this command will flag the ban action for review by the Core Administration team for a possible longer term BAN. This command should not be used lightly or frequently by the Field Agents, and should only be reserved for the worst offenders. Field Agents that abuse this command will face administrative action. Like the NetBan, the action is logged and can not be applied unless the user has received 3 warnings.

===Tracking Mode===
All commands that apply limits to users across servers will use ether the BZID of the user, or if unregistered the current tracking mode. If the tracking mode represents a range of IPs, then any user who isn't registered in that IP range will be blocked. Agents need to check and set the tracking mode using ''/NetSetIdent'' before applying any actions. The tracking mode will be stored with the user name of the player in the central database.

CommunityAdminstrationNetwork/Server Owners

2007-11-04T20:34:07Z

A Meteorite: CommunityAdminstrationNetwork/Server Owners moved to CommunityAdministrationNetwork/Server Owners: Misspelled "administration"

#REDIRECT [[CommunityAdministrationNetwork/Server Owners]]

CommunityAdministrationNetwork/Server Owners

2007-11-04T20:34:07Z

A Meteorite: CommunityAdminstrationNetwork/Server Owners moved to CommunityAdministrationNetwork/Server Owners: Misspelled "administration"

{{CommunityAdministrationNetwork}}

==Overview==
This page describes the information needed by server owners who are part of the [[CommunityAdminstrationNetwork/About|Community Administration Network]].

==Membership Requirements==

Membership as a CAN server is rather simple, and requires the server owner to agree to a few small things, and install a single plug-in.

===Publicly List===
CAN is only for public servers. It is not available for private servers, due to its link with global authentication and web-based services.

===Endorse Global Authentication===
Running a CAN server means that the server owner agrees to use the global registration system. The CANAdmin plug-in will notify unregistered users that they should register, and provide a URL with instructions on how to register. The CANAdmin plug-in will also disallow any unregistered user, using a registered callsign to spawn, or be on the server for more then 5 min. Server owners should also have and use a global username.

===Provide a contact name and e-mail===
The CAN system needs a contact name and e-mail for each server or group of servers that it runs. This is so that the administration staff can contact the server owners if need be, and for the CAN website to send automatically generated usage/action logs every week. Servers with invalid contact information will be removed from the network.

===Provide a valid domain name and port for each server running===
The CAN system needs to know the names and ports of each server that is run in order to verify its membership in the network.

===Run a minimum version of the BZFS server===
In order for the CANAdmin plug-in to work, it will require a specific version of BZFS. Server owners that can not build their own BZFS simply need to ask, and the network staff can work with you to get a version that is compatible with the required server.

===Understand the service===
It is important that each server owner understand what services are and are not being offered by the network, as well as understanding what responsibilities do and don't come with network membership. Being a CAN member server does not automatically confer any network administration status or abilities to the server owner. While many server owners would make fine field agents or core administrators and may be asked to participate in the network in those positions, they will not be judged for those positions solely on their ownership of a server. Field Agent positions have their own set of criteria for membership and they will be chosen for those alone. Server owners do not lose any local administration ability by becoming a CAN member server.

==Actions that will result in membership termination==

There is a small number of actions that will result in the termination of the membership agreement with a server.

===Modification of the CANAdmin plug-in===
A server owner should never need to modify the plug-in, or change it in any way. Use of a modified plug-in can result in the removal of a server from the network. If a server owner requires additional features from the plug-in, they should contact the administration staff, so the features can be worked into the base plug-in code.

==Disputes with Administration actions==

The administration team is more than happy to work with server owners to resolve any issues or disputes that they may have with the actions of its agents. Accountability of agent actions is a primary goal of the network. If a server owner has any issue with an action, it is best that they talk to the administration team about it as soon as possible. Issues such as a "rogue agent" or a misplaced ban are taken very seriously by the network and the admin staff will do its best to have it resolved as soon as possible. If need be, the core administrators can "undo" all the actions of specific agents.

The administration staff asks that server owners not block access to the server for any of its agents except in the worst of circumstances, and that it not override the actions of the administration staff, as it will prevent the network from doing what has been agreed upon. If a server owner feels they must take actions such as these, the admin staff highly recommends opening a dialog as soon as possible.

Server owners are free to unload or remove the CANAdmin plug-in at any time to leave the network at their own discretion. The Core Administrators and the Network Administrator reserve the right to remove any server from the CAN network at any time, with notification.

CommunityAdminstrationNetwork/Players

2007-11-04T20:33:05Z

A Meteorite: CommunityAdminstrationNetwork/Players moved to CommunityAdministrationNetwork/Players: Misspelled "administration"

#REDIRECT [[CommunityAdministrationNetwork/Players]]

CommunityAdministrationNetwork/Players

2007-11-04T20:33:05Z

A Meteorite: CommunityAdminstrationNetwork/Players moved to CommunityAdministrationNetwork/Players: Misspelled "administration"

{{CommunityAdministrationNetwork}}

==Overview==
This page describes the information needed by players to play on servers that are part of the [[CommunityAdminstrationNetwork/About|Community Administration Network]].

==Requirements==
Players on network servers must only meet 2 requirements.

===Global Registration===
Players are highly recommended to a valid global user name and login, and play using that name. Unregistered users may subject to limitations in play on many servers, and also loose the ability to dispute any actions of the network.

===Follow the Rules===
Players are expected to follow the 6 network rules as they are specified in the [[CommunityAdminstrationNetwork/About#Rules|Community Administration Network]] Document. Failure to follow these rules can result in administrative actions.

==Disputes==
Players that have a dispute are expected to work with the administration staff to resolve the dispute in a calm and civil manner in private. The admin staff will gladly work with players to resolve any technical, network, or software issues that may cause violations of any of the rules. The admin staff has a good working relationship with the project developers and will ask them to assist in diagnosing any problems. Players are expected to assist the admin staff in resolving the issues so that everyone can have a fun game.

If a dispute is unable to be resolved by the Field Agents, the player can bring the issue to the attention of the Core Administrators. The Core Administrators can be contacted via the following means.

* <SOME EMAIL ADDRESS WE PICK>
* the ##CommunityAdminNetwork IRC channel on irc.freenode.net:6667
* BZBB PM to any core member ( list them somewhere ).

Issues that players may have with the Core Administration team should be addressed to the Network Administrator directly.

==Questions==

===I would like to help out and be a field agent, what do I do?===
The answer to this question is complex. It is important to understand exactly what a field agent does before a player decides they wish to apply to the network. All users should be aware of the requirements, and expected behaviors of a field agent as well as the full ruleset for the network. The [[CommunityAdminstrationNetwork/Field_Agent|Field Agent]] guide lists the requirements and behaviors. Players should also have a history of good play on one or more member servers before they even think about applying as a field agent.

Once a player has read and understands all the material, he/she should contact the Administration staff and let them know that he/she is interested in donating his/her time as a field agent. The best way to do this is via the IRC channel, or e-mail. Once he/she has let the staff know, simply wait. Field agents are chosen based on a number of criteria, and need. Pushing, pestering, or bugging people to become an agent, shows that the applicant probably does not meet the behavior needs of field agent. A new field agent must be sponsored by an existing Core Administrator. 3 or more existing field agents can petition the Core Administrators to sponsor a new field agent. Agents are only added if there is a need for more. The network administrator has veto and approval power over all field agents.

When a new field agent is approved, he/she will be asked to read and agree to the field agent agreement form, and fill in valid contact info, age, and verify that he/she has read and understands the network rules and administration policy. He/she will also be trained and tested on the use of the CANAdmin plug-in. After this is completed, the user's BZID will be added to the central database as a field agent. Other field agents or the network administration staff may monitor or review any new or existing field agents actions at any time.

Talk:CommunityAdminstrationNetwork/About

2007-11-04T20:32:34Z

A Meteorite: Talk:CommunityAdminstrationNetwork/About moved to Talk:CommunityAdministrationNetwork/About: Misspelled "administration"

#REDIRECT [[Talk:CommunityAdministrationNetwork/About]]

Talk:CommunityAdministrationNetwork/About

2007-11-04T20:32:34Z

A Meteorite: Talk:CommunityAdminstrationNetwork/About moved to Talk:CommunityAdministrationNetwork/About: Misspelled "administration"

Please let us know what you think.--[[User:JeffM2501|JeffM2501]] 18:14, 9 May 2007 (EDT)

CommunityAdminstrationNetwork/About

2007-11-04T20:32:33Z

A Meteorite: CommunityAdminstrationNetwork/About moved to CommunityAdministrationNetwork/About: Misspelled "administration"

#REDIRECT [[CommunityAdministrationNetwork/About]]

CommunityAdministrationNetwork/About

2007-11-04T20:32:32Z

A Meteorite: CommunityAdminstrationNetwork/About moved to CommunityAdministrationNetwork/About: Misspelled "administration"

{{CommunityAdministrationNetwork}}

==Overview==
The Community Administration Network is an independent organization of server owners and administrators who have chosen to group together to provide the best possible play experience to BZFlag players.

'''Please note'''
The network is just in it's conceptual stages at this point. Please post any questions, comments, or concerns to the talk page. Also if you are a server owner that would be interested in being a member please also post that to the talk page, we are very interested in knowing who would like to participate.

==Organization==
The Network is made up of servers whose owners have chosen to provide the network administration staff the ability to manage and enforce a specific set of rules on their servers.

Information for users playing on member servers can be found on the [[CommunityAdminstrationNetwork/Players]] page.

The network is made up of the following groups:

===Server Owners===
These are server owner/operators that have chosen to participate in the network. The owners have agreed to the rules for servers and have been accepted into the network. They run the CANAdmin plug-in as part of their server setup. Information on the requirements and expectations of server owners can be found on the [[CommunityAdminstrationNetwork/Server Owners]] page.

===Field Agent===
These are users chosen from the community to do the day-to-day admin actions on network servers. They are normal players that have agreed to the terms and rules for CAN Field Agents. They use the CANAdmin plug-in on network servers to perform their administration actions. All actions by all agents are logged by the network for review. Information on the requirements and expectations of Field Agents can be found on the [[CommunityAdminstrationNetwork/Field Agent]] page.

===Core Administrators===
These are a smaller group of administrators that in addition to the abilities of the field agents, is responsible for arbitrating disputes between players and field agents and for adding or removing field agents when needed. The Core administration team is also responsible for approving and reviewing the servers that make up the network.

===Network Administrator===
The network administrator in addition to being a Core Administrator, is the one person responsible for the entire network. He/she creates the rules to which all other administrators and server owners agree. The network administrator has the power of veto over any action of the other agents but must provide a reasonable explanation, or face the other administrators and agents abandoning the network (making it pointless).

==CANAdmin plug-in==
The network administrators make use of a special plugin that server administrators install to allow network administration. This allows agents to apply network wide warnings, kicks, and bans to users that violate the network rules and regulations. The network agents are only able to enforce the network-specific rules on servers and by default do not have any additional administrative permissions or abilities on any server. A server owner may choose to give network agents additional abilities, but it is not required for network membership.

==Rules==
The network has a very specific set of rules that it applies to servers. This rule set is expected to be a small subset of the rules on any one server. CAN Administrators will only enforce these specific rules by default. Every administrative action (warn, kick, and ban) will be logged with the rule number to which the violation applies, as well as any applicable logs or records needed.

===1) No Cheating===
Users must not use modified clients to gain an unfair advantage over other users. This includes any modification that changes the behavior of a player tank from the release version of the game, or any modification that provides additional information or reaction time to the game.
Examples include (but are not limited to):
* God Mode (un-killable)
* Auto-Aim
* Seeing Stealth or Cloak.
* Jump Modification
* Speed modification
* Tank hit size modification
* Shot end modification
Additional items may be added based on the observations of the administrator. If a user is experiencing network or software problems that may appear to be cheats, then it is up to them to work with the Administration staff and/or the project development to rectify the issue as soon as they are warned. The administration staff will be more then happy to work with the users to determine the cause of any software- or network-related issues. If the issues are network-related and cause the disruption of play with other users, network administrators can request that the user discontinue play on a specific server until such time as network conditions improve. The administrators are expected to speak to the players about the behavior before taking any action to determine its cause.

===2) No Exploiting===
Users must not use in-game features or flaws to gain an unfair advantage over other players. This includes using game features or bugs to create artificial lag spikes, tweaks or changes to the input system, or the operating system / drivers to create positional discrepancies or speed changes. If the administration staff asks a user to discontinue an action that is causing a problem, the user is expected to refrain from that action. This includes the use of external applications to modify the game's internal state or network data.

===3) No Griefing===
Users must not engage in behavior that is disruptive to the play of the game. This includes actions such as intentional team-killing, intentional or repeated genocide of one's own teammates, or capturing your own team's flag in a CTF game. Griefing also includes message spamming, whether private or public. The administration team does understand that isolated accidents do happen and are required to issue warnings before taking actions. Users warned of a particular offense are expected to take care to not repeat the actions, even if they were accidents in the first place.

===4) Minimum Language Rules===
Users are expected to adhere to a set of [[CommunityAdminstrationNetwork/DisallowedWords|minimum language rules]] that disallows a set of very specific words when using public or team chat channels. Users are also expected to refrain from attacking or making disparaging remarks about another player's race, religion, gender, disability, ethnicity, employment circumstances, or sexual orientation. The in-game chat is primarily for discussion about the game while playing. Users who are warned for language violations are expected to discontinue use of the offensive language, and continue to play in a civil manner. It should be noted that individual servers can and may have more strict language policies in place that they administer locally. The minimum language policy applies to any content that is displayed to other players including user callsigns, in game e-mail addresses, parting messages, as well as all public and team chat text.

===5) No disruption of public services===
Users are expected to not take actions that would disrupt any of the network's or project's public services. This includes any websites or forums, IRC channels, or servers operated by the network itself, or the
BZFlag project. Actions of this nature are very serious and will not be taken lightly.

==Recommendations==

===Global Registration===
It is highly documented that all users must be globally registered and identified when they play. Unregistered users will be tracked by there IP, hostmask, and other data. Unregistered users may not dispute any administrative action on the network. Unregistered users will not be white listed to get around any IP range or host mask bans that may be in place. It is assumed that honest players will have no problem with registering for the game. Any network agent will be glad to help users get registered with the BZFlag global login system

==Common Questions and concerns==

===Questions===
====Does the network do range bans?====
Yes, the network can and will do IP range bans for dynamic IPs. When possible a BZID ban will be used, but some situations require a range ban. Registered users can be given a white list based on there BZID and be allowed to play on IPs in a banned range.

===What the Network Is===
This is a list of items that describe what the network is meant for:

====The CAN is a group of people:====
The network consists of people - people that the server owners have chosen to trust to enforce a set of rules. It is run by people for people. People are human. It is assumed that people can and will make mistakes on both sides. Mistakes can be fixed as long as both parties are willing to work at fixing the problem in a civil manner.

====The CAN is reasonable:====
Administrators are more then willing to listen to anyone who has been kicked or banned, as long as the user is willing to work with them in a reasonable manner. If a user has an issue that can not be resolved with an administrator, they should take it up to the next level of administration as indicated in the organization section above.

====The CAN keeps records, lots of them:====
The CANAdmin plug-in will track all actions done by administrators, and can provide them for review if needed. These records are kept independently of any logging or tracking that server owners choose to do, and are intended to be used by network staff only. This provides a set of checks and accountability for all actions, as well as records of the reasons behind any action.

====The CAN is a team:====
Network administrators work together. Any administrator can work on any problem, regardless of who the issue started with. Administrators are encouraged to work together, with other administrators, and players.

====The CAN works with leagues:====
Since the field agents don't have any control over gameplay commands, and the CANAdmin plug-in doesn't use any of the host server's administration functions, there is no reason why a league server can not also be a CAN member server. The network rules should be compatible as a subset for all leagues.

===What the network is not===

====The CAN is not your mom====
The network does not exist to arbitrate small disagreements in playstyle or behavior. It will not make Billy stop touching your flag. It does not exist to decide what is or isn't fair in games. The rules that the network enforces have nothing to do with gameplay or any specific game ruleset. The CAN will not and cannot do such gameplay actions as resetting flags, balancing teams, or changing server variables.

====The CAN does not take over a server.====
By default CAN administrators do not have access to a server banlist, groups, passwords, users, or any other abilities. All network actions are applied by the CANAdmin plug-in and do not affect the server settings in any way.

====The CAN is not a democracy.====
The network is a service provided by its administrator and trusted staff. Server owners can choose to allow the CAN onto their servers, or they can choose not to. The network is not designed or run by any sort of committee. It is run following the specific rules set forth in this document.

====The CAN is not the master ban list.====
While some of the network administration staff are also part of the BZFlag project, the network itself is not. Network bans are not part of the global master ban list that is applied by default to all public servers. Actions against the project itself may result in CAN administrative action, but the reverse is not always true.

== See Also==
[[CommunityAdminstrationNetwork/Server Owners]]

[[CommunityAdminstrationNetwork/Field Agent]]

[[CommunityAdminstrationNetwork/Core Administrators]]

[[CommunityAdminstrationNetwork/Players]]

[[CommunityAdminstrationNetwork/CANAdmin Plug-In]]

BZFS API

2007-08-14T03:10:17Z

A Meteorite: /* bzApiString */ s/bzApiString/bz_ApiString

The BZFS API (Application Programmers Interface) is a set of C++ functions, structures, and classes that is exported by [[BZFS]] to be used by [[Plug-ins]]. The API provides access to the various states and data structures of a running BZFS game and is the primary method of communication between a plug-in and the game server.

==Overview==
The BZFS API is defined entirely in the '''bzfsAPI.h''' header file that is part of the [[BZFlag Source]] code. The header is also included with each install of the BZFlag installer for Microsoft Windows.

Plug-ins include this file in there source code so that they may access the functions it contains.

==Naming Conventions==
All BZFS API code structures will begin with the prefix '''bz_''' for clarification and to prevent conficts with names of code strcutres inside BZFS or any plug-ins.

==API Versions==
The API was added in version 2.0.4 of BZFlag. While working well for many users, it was found to be lacking in a number of features that would make make it difficult for plug-ins to run when the API itself was changed.

As of version 2.1 of BZFlag, the entire API was versioned and set up to use derived classes to that plug-ins written to use an older version of the API will work in newer versions of the software. Newer data structures would be put into further derived classes and would not be seen by the older plug-in. Due to this change a large number of API functions changed in name. This change causes all older 2.0.x plug-ins to no longer work with out a source code change. Once older plug-ins are updated to the new 2.1 API they will use the new versioning system and work fine in newer versions with out any needed changes.

==Entry Points==
There are 3 primary entry points into each plug-in. These entry points are the 3 core functions that every plug-in must implement.

BZF_PLUGIN_CALL int [[bz_Load]] ( const char* command );
BZF_PLUGIN_CALL int [[bz_Unload]] ( void );
BZF_PLUGIN_CALL int [[bz_GetVersion]] ( void );

[[bz_Load]] is called when the plug-in is first initialized. This is when the plug-in should register any [[Event(API)|event handlers]] needed and initialize any "one time" startup data.

[[bz_Unload]] is called when a plug-in is no longer needed and will be shut down. This is most commonly called when bzfs is shutting down, or when a plug-in is unloaded manualy.

[[bz_GetVersion]] is called by bzfs before any other functions are called. The function should return the version of the API that it is written for. This is to prevent bzfs from attempting to load plug-ins that use a newer incompatible API.

'''bzfsAPI.h''' defines a C MACRO to help ease the implementation of this function. All a plug-in must do is put the macro;

BZ_GET_PLUGIN_VERSION

somewhere in its sources, and then export the function. This will automatically return the API version of the current API you are using. See the sample plug-ins for examples. These will be the only 3 functions called by bzfs for non-event actions.

All entry point functions should be preceded with the BZF_PLUGIN_CALL macro. This macro will tell your compiler to export these functions so bzfs can call them after the plug-in is loaded.

==Types==

Due to how Microsoft Windows handles memory access between an application and dynamically loaded Libaries(DLLs), there are a few custom data types that are used in the API. These are used for common STL style containers, for strings and lists.

===bz_ApiString===
Any text passed back from the API or events will come in the form of a [[bz_ApiString]]. This is a class defined in the API that behaves much like a std::string. The 'c_str()' method can be used to get the text out as a normal 'const char*'. The class also supports many assignment functions for setting it's contents.

A plug-in should never need to make variables of its' own using the [[bz_ApiString]] type, but should use a standard stl std::string instead, [[bz_ApiString]] provides an appropriate assignment operator.

[[bz_ApiString]] also includes some utility functions such as replace all and tokenize that are commonly needed by plug-ins.

===bz_APILists===

A few API functions require lists of integers, strings, or floats. For these functions the plug-in will need to use one of the following list classes. These classes are similar to the std::vector in implementation. When a plug-in needs to allocate one of these lists, it must use the appropriate allocator function, so BZFS can make a new list for the plug-in to use. These will return a pointer to a new list for the plug-in to use. When the plug-in is finished with the list, it needs to tell BZFS to delete the list with a call to the appropriate delete function.
The lists types are;
{| border="1" cellpadding="20" cellspacing="0"
!List
!allocator function
!delete function
!contained type
|-
|[[bz_APIIntList]]
|[[bz_newIntList]]
|[[bz_deleteIntList]]
|int
|-
|[[bz_APIFloatList]]
|[[bz_newFloatList]]
|[[bz_deleteFloatList]]
|float
|-
|[[bz_APIStringList]]
|[[bz_newStringList]]
|[[bz_deleteStringList]]
|[[bz_ApiString]]
|}

===Enumerations===
A number of enumerations exist in the API and are used by a number of API functions and events.
[[bz_eTeamType]]
[[Event(API)|bz_eEventType]]
[[bz_eShotType]]
[[bz_eGameType]]
[[bz_ePlayerStatus]]
[[bz_eWorldObjectType]]
[[bz_eAPIColType]]
[[bz_ePlayerType]]
[[bz_eRejectCodes]]
[[bz_ePlayerDeathReason]]

==Events==
Plug-ins can register callbacks so they can be notified of various actions and state changes in the current BZFS game. These events tell a plug-in when important things happen, such as when a player has spawned, or is killed. These events are the primary form of communication from the BZFS server into the plug-in.

See the [[Event(API)|API events]] page for more detailed information on events.

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

See the [[Functions(API)|API Functions]] page for more information on functions.

==See Also==
[[BZFS]]

[[Plug-ins]]

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

BZFS API

2007-08-14T02:43:33Z

A Meteorite: /* bzAPILists */ The classes now use underscores (bz_APIIntList vs bzAPIIntList, bz_ApiString vs bzApiString, etc)

The BZFS API (Application Programmers Interface) is a set of C++ functions, structures, and classes that is exported by [[BZFS]] to be used by [[Plug-ins]]. The API provides access to the various states and data structures of a running BZFS game and is the primary method of communication between a plug-in and the game server.

==Overview==
The BZFS API is defined entirely in the '''bzfsAPI.h''' header file that is part of the [[BZFlag Source]] code. The header is also included with each install of the BZFlag installer for Microsoft Windows.

Plug-ins include this file in there source code so that they may access the functions it contains.

==Naming Conventions==
All BZFS API code structures will begin with the prefix '''bz_''' for clarification and to prevent conficts with names of code strcutres inside BZFS or any plug-ins.

==API Versions==
The API was added in version 2.0.4 of BZFlag. While working well for many users, it was found to be lacking in a number of features that would make make it difficult for plug-ins to run when the API itself was changed.

As of version 2.1 of BZFlag, the entire API was versioned and set up to use derived classes to that plug-ins written to use an older version of the API will work in newer versions of the software. Newer data structures would be put into further derived classes and would not be seen by the older plug-in. Due to this change a large number of API functions changed in name. This change causes all older 2.0.x plug-ins to no longer work with out a source code change. Once older plug-ins are updated to the new 2.1 API they will use the new versioning system and work fine in newer versions with out any needed changes.

==Entry Points==
There are 3 primary entry points into each plug-in. These entry points are the 3 core functions that every plug-in must implement.

BZF_PLUGIN_CALL int [[bz_Load]] ( const char* command );
BZF_PLUGIN_CALL int [[bz_Unload]] ( void );
BZF_PLUGIN_CALL int [[bz_GetVersion]] ( void );

[[bz_Load]] is called when the plug-in is first initialized. This is when the plug-in should register any [[Event(API)|event handlers]] needed and initialize any "one time" startup data.

[[bz_Unload]] is called when a plug-in is no longer needed and will be shut down. This is most commonly called when bzfs is shutting down, or when a plug-in is unloaded manualy.

[[bz_GetVersion]] is called by bzfs before any other functions are called. The function should return the version of the API that it is written for. This is to prevent bzfs from attempting to load plug-ins that use a newer incompatible API.

'''bzfsAPI.h''' defines a C MACRO to help ease the implementation of this function. All a plug-in must do is put the macro;

BZ_GET_PLUGIN_VERSION

somewhere in its sources, and then export the function. This will automatically return the API version of the current API you are using. See the sample plug-ins for examples. These will be the only 3 functions called by bzfs for non-event actions.

All entry point functions should be preceded with the BZF_PLUGIN_CALL macro. This macro will tell your compiler to export these functions so bzfs can call them after the plug-in is loaded.

==Types==

Due to how Microsoft Windows handles memory access between an application and dynamically loaded Libaries(DLLs), there are a few custom data types that are used in the API. These are used for common STL style containers, for strings and lists.

===bzApiString===
Any text passed back from the API or events will come in the form of a [[bzApiString]]. This is a class defined in the API that behaves much like a std::string. The 'c_str()' method can be used to get the text out as a normal 'const char*'. The class also supports many assignment functions for setting it's contents.

A plug-in should never need to make variables of its' own using the [[bzApiString]] type, but should use a standard stl std::string instead, [[bzApiString]] provides an appropriate assignment operator.

[[bzApiString]] also includes some utility functions such as replace all and tokenize that are commonly needed by plug-ins.

===bz_APILists===

A few API functions require lists of integers, strings, or floats. For these functions the plug-in will need to use one of the following list classes. These classes are similar to the std::vector in implementation. When a plug-in needs to allocate one of these lists, it must use the appropriate allocator function, so BZFS can make a new list for the plug-in to use. These will return a pointer to a new list for the plug-in to use. When the plug-in is finished with the list, it needs to tell BZFS to delete the list with a call to the appropriate delete function.
The lists types are;
{| border="1" cellpadding="20" cellspacing="0"
!List
!allocator function
!delete function
!contained type
|-
|[[bz_APIIntList]]
|[[bz_newIntList]]
|[[bz_deleteIntList]]
|int
|-
|[[bz_APIFloatList]]
|[[bz_newFloatList]]
|[[bz_deleteFloatList]]
|float
|-
|[[bz_APIStringList]]
|[[bz_newStringList]]
|[[bz_deleteStringList]]
|[[bz_ApiString]]
|}

===Enumerations===
A number of enumerations exist in the API and are used by a number of API functions and events.
[[bz_eTeamType]]
[[Event(API)|bz_eEventType]]
[[bz_eShotType]]
[[bz_eGameType]]
[[bz_ePlayerStatus]]
[[bz_eWorldObjectType]]
[[bz_eAPIColType]]
[[bz_ePlayerType]]
[[bz_eRejectCodes]]
[[bz_ePlayerDeathReason]]

==Events==
Plug-ins can register callbacks so they can be notified of various actions and state changes in the current BZFS game. These events tell a plug-in when important things happen, such as when a player has spawned, or is killed. These events are the primary form of communication from the BZFS server into the plug-in.

See the [[Event(API)|API events]] page for more detailed information on events.

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

See the [[Functions(API)|API Functions]] page for more information on functions.

==See Also==
[[BZFS]]

[[Plug-ins]]

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

Main Page

2007-08-04T01:56:16Z

A Meteorite: Undo vandalism

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

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

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

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

==General Information==
*[[Getting Help]]
*[[:Category:BZFlagWiki_Policy|BZFlag Wiki Policy]]

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

==Things To Do==
*[[:Category:Stubs|Stubs]] These are short pages. You can help by expanding the content and adding more detail.
*[[:Special:Wantedpages|Wanted pages]] These are pages which don't exist yet but are pointed to from other pages. You can help by creating them.
*[[:Category:Items to be merged|Pages to merge]] These are pages which are similar. It is suggested that similar pages be merged. You can help by reviewing the pairs of pages and commenting on any proposals by using the "Discussion" tab at the top of each page.
*[[:Category:Old|Pages with old info]] You can help by updating these pages.
*[[:Category:Inaccurate|Inaccurate pages]] You can help by updating these pages.
*[[:Category:Pending Deletions|Pending deletions]] These are pages which have been nominated for deletion. You can help by reviewing these pages and commenting on any proposals by using the "Discussion" tab at the top of each page.

Category:Compiling

2007-07-30T03:56:53Z

A Meteorite: Undo revision 2911 by 66.189.4.29 (Talk)

Pages dealing with the building and compiling of BZFlag into usable binary executables.

Talk:Main Page

2007-07-30T03:56:02Z

A Meteorite: Undo revision 2905 by 66.189.4.29 (Talk)

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)

== Areas of Interest list is too long ==

I think the list is too long; it should contain 8 or 9 items only.
Concepts - I think is a meaningless category.
Gameplay and Tactics - merge?
Releases and Versions - merge?
[[User:Mr Burns|Mr Burns]]

Category:Client

2007-07-30T03:55:33Z

A Meteorite: Undo revision 2910 by 66.189.4.29 (Talk)

Pages that are related to the BZFlag Client

Category:BZFlagWiki Policy

2007-07-30T03:54:59Z

A Meteorite: Undo revision 2908 by 66.189.4.29 (Talk)

Pages in this category are widely accepted as BZFlag Wiki policy. All editors should adhere to these policies whenever possible.

Getting Help

2007-07-30T03:54:16Z

A Meteorite: Revert

Getting help on BZFlag is rather easy. There are a number of places to get help

==IRC Chat Room==
The BZFlag communities [[BZFlag on IRC|make heavy use of IRC]] for communication and collaboration.

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

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

Please see [[BZFlag on IRC]] for more info.

==Web Forums==

BZFlag maintains a set of [[BZFlag Forums|official forums]], located at http://my.BZFlag.org/bb/

An older set of forums, now mostly unused, is located on SourceForge:
*http://sourceforge.net/forum/?group_id=3248 - main page
*http://sourceforge.net/forum/forum.php?forum_id=9554 - help forum

==Mailing Lists==

There are a number of BZFlag mailing lists. The best one for support questions is bzflag-user. Archives and subscription information can be found on the SourceForge BZFlag project mailing list page at http://sourceforge.net/mail/?group_id=3248

==Common Support Issues==
The [[Common Support Issues]] page lists a number of the common problems with the game, and their resolutions.

==Documentation==
The game is documented via a series of manual pages ( or man pages ).
On Linux and other Unix like operating systems they are installed by default and can be accessed by using the '''man''' command and one of the following pages.
*bzflag
*bzfs
*bzadmin
*bzw

On Microsoft Windows and Apple OSX the manual pages are in HTML format. They are installed in the start menu for Windows, or in the extras folder on the install DMG for OSX.

The man pages are also available online in HTML format:
NOTE: As of June 2007 there is a problem with the man page conversion to HTML and the web manuals are NOT CORRECT! Use the man pages from source, or
Corrected versions are being made, and will be posted on this wiki.

*[http://my.bzflag.org/bzfman.cgi?bzflag.6.in bzflag]
*[http://my.bzflag.org/bzfman.cgi?bzadmin.6.in bzadmin]
*[http://my.bzflag.org/bzfman.cgi?bzfs.6.in bzfs]
*[http://my.bzflag.org/bzfman.cgi?bzw.5.in bzw]

==Further Support==
If any of these methods don't provide a resolution to a problem, the project maintains a support tracking system on SourceForge. New tickets can be opened at this URL:

http://sourceforge.net/tracker/?group_id=3248&atid=203248

==See also==
[[BZFlag on IRC]]

[[BZFlag Forums]]

[[Common Support Issues]]

==External links==
[http://my.BZFlag.org/irc/irc.cgi BZFlag Web IRC gateway]

[[Category:Support]]

BZFlagWiki:Be bold

2007-07-30T03:53:04Z

A Meteorite: Undo revision 2909 by 66.189.4.29 (Talk)

''This page in a nutshell: If in doubt, fix it.''

==Be '''BOLD'''…==
The Wiki philosophy, and BZFlagWiki particularly, encourages users to '''be bold in updating articles'''.
Wikis develop faster when people fix problems, correct grammar, add facts, make sure the wording is accurate, etc. We expect everyone to be bold. How many times have you read something and thought, "Why aren't these pages copy-edited?" BZFlagWiki not only allows you to add, revise, and edit the article — it ''wants'' you to do it. It does require some amount of civility, but it works. You'll see.

Also, of course, others here will edit what ''you'' write. Don't take it personally. They, like all of us, just want to make the BZFlag Wiki as good as it can possibly be. Bring out all information that you can.

==…but don't be reckless.==

If you anticipate a disagreement with your version of the article, and you want to change or delete a large amount of the text, it's a good idea to list your objections one by one in the talk page, reasonably quoting the disputed phrases, explaining your reasoning, and providing solid references.

Then, wait for responses for at least a day: people edit the BZFlag Wiki in their spare time and may not respond immediately. If no one objects, proceed, but always list your objections to the text so that other people will understand your changes and will be able to follow the history of the page. Also be sure to leave a descriptive edit summary detailing your change and reasoning.

Additional information can be found at the [[BZFlagWiki:Content Policy|Content Policy]] page.

==Categories and templates==
Although it is generally fine to be bold in updating '''articles''', being bold in updating or creating '''categories and templates''', especially templates, can often be very bad. This is because category changes - and even more so template changes - can affect a large number of pages. In the case of templates, changing code on one template that is very widely used can potentially cause problems for BZFlagWiki's servers. It is usually worth proposing any changes to categories and/or templates on talk pages prior to making any change.

== See also ==
[[BZFlagWiki:Content Policy]]

[[Category:BZFlagWiki Policy]]

Main Page

2007-07-30T03:51:47Z

A Meteorite: Revert

User:A Meteorite

2007-04-08T23:38:37Z

A Meteorite: prevent those spam bots harvesting my e-mail

BZFX

2007-04-08T19:39:58Z

A Meteorite: official founding date, not birthday

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

= History =
BZFX was started in early-2006 by [[User:A_Meteorite|A Meteorite]]. The official founding date of BZFX is May 29, 2006, which is when the [http://bzfx.net/ BZFX domain] was registered.

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

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

Talk:Wiki/index.php

2007-04-08T08:27:56Z

A Meteorite: remove spam

BZFlag on IRC

2007-04-07T22:59:39Z

A Meteorite: /* Other channels */

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

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

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

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

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

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

* ##bar (DUCLeague team, The Barbarians)
* #bzfx (Support channel for the bzfx.net BZFlag servers)
* ##bz-inc (DUCLeague team, [http://my.bzflag.org/league/index.php?link=teaminfo&id=689/ Bz-Incorporated])
* #dub (Support channel for the dub.bzflag.org BZFlag servers)
* ##ducleague (Support channel for [http://my.bzflag.org/league/ Ducati League (DucLeague)])
* #guleague (Support channel for [http://gu.bzleague.com/ GamesUnited League (GULeague)])
* #hepcat (Support channel for borrego.hepcat.org BZFlag server)
* ##icf (Support channel for [http://gu.bzleague.com/index.php?link=teaminfo&id=112 Insane Crazy Funsters, (GULeague)])
* #forestforce ([http://gu.bzleague.com/index.php?link=teaminfo&id=10 GULeague Team])
* #inleague (Support channel for [http://in.bzleague.com InterNational League (INLeague)])
* #kas (GULeague team, KAS)
* ##norang (Support channel for [http://bzflag.norang.ca Norang.ca] BZFlag servers)
* ##openleague (Support channel for [http://openleague.org/ OpenLeague])--IRC and website appear to be defunct a this point in time [[User:DonnyBaker|DonnyBaker]] 20:43, 23 March 2007 (EDT)
* #pillbox (Support channel for [http://pillbox.bzleague.com/ Pillbox League (PBLeague)])
* ##planetmofo (Support channel for [http://www.planet-mofo.com planet-mofo.com] servers)
* #plosileague (Support channel for [http://bzfx.net/league/ Plosileague])
* #silvercat (Support channel for [http://silvercat.bzflag.org/ Silvercat BZFlag servers])
* ##t42 ([http://gu.bzleague.com/index.php?link=teaminfo&id=39 GULeague team])
* ##untamed ([http://my.bzflag.org/league/index.php?link=teaminfo&id=909 DUCLeague team])

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

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

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

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

http://irchelp.org/

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

Passion

2007-04-07T22:57:22Z

A Meteorite: no "chest pounding" on groups or people, according to donny_baker it is not allowed. so removed the planet mofo only relevant stuff.

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

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

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

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

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

== Variations==

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

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

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

=== Passion of the Polygon ===

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

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

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

=== April Fools ===

This was three maps in one - the regular map, a map scaled down and a map scaled up. These were linked by teleporters and designed to disorientate the player.

April 1st 2007 saw the change to a "hell map" which featured several changes including flaming walls, spinning pyramids and a giant pentagram in the sky. This map is quite different and as a result gameplay is slightly different as there was no outer walls to rico off and no GM camping spots (flattened corner pyramids).

=== The Inversion ===

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

=== MoFo Garage ===

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

=== Two Story MoFo ===

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

=== Mammoth ===

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

=== Epileptic Fit ===

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

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

Talk:BZFX

2007-04-07T05:06:12Z

A Meteorite:

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

::If I so choose to have more information about BZFX, why not? Information is good. The more the merrier. If this is because BZFX's page has more info than a league page, that is really lame. The league owners - or even players - could add more info so as long as it's not opinion. --[[User:A Meteorite|A Meteorite]] 22:44, 5 April 2007 (EDT)

:[[User:A Meteorite|A Meteorite]] the information you present adds nothing to BZFlag... it is valuable to BZFX and therefore belongs on the BZFX web page. You are more than welcome to put the link to that site here (which you did). If people are interested in your rules and who your admins/cops are they can go to your website where you have full control of the content. As for the opinion comment, and I quote: "[[User:A_Meteorite|A Meteorite]] believed that no well-created and managed unified BZFlag server network existed. He believed he could do it better, and others have believed in him and BZFX. Since BZFX has been founded and taken off, several pieces of software has been in development for the higher furthering of BZFlag servers." Sounds like a bunch of chest beating to me, and that is not what the wiki is for. There are several "Networks", as you call them and they will get the same treatment if and when they post items like this. The fight is over, the page is protected and is noted on the page. --[[User:DonnyBaker|DonnyBaker]] 06:06, 6 April 2007 (EDT)

"[[User:A_Meteorite|A Meteorite]] believed that no well-created and managed unified BZFlag server network existed. He believed he could do it better, and others have believed in him and BZFX. Since BZFX has been founded and taken off, several pieces of software has been in development for the higher furthering of BZFlag servers."
::That part can be removed, if is what it takes to be able to have rules and such. --[[User:A Meteorite|A Meteorite]] 01:06, 7 April 2007 (EDT)

Talk:BZFX

2007-04-07T03:58:09Z

A Meteorite:

Talk:BZFX

2007-04-06T02:44:31Z

A Meteorite:

Talk:BZFX

2007-04-06T02:03:57Z

A Meteorite: /* DonnyBaker's page removal */

BZFX

2007-04-06T02:02:58Z

A Meteorite: Page in limbo state

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

= Why another server network? =

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

= Contact =

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

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

= History =

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

= Rules =

BZFX's rules are strictly enforced. They are not hard to abide by, and that's all BZFX asks of it's players. Playing at BZFX is a privilege, '''not''' a right. The rules are quite simple:

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

Players that do not abide by these rules will be dealt with immediately. Possible punishments include muting, [[Kick|kicking]], and [[Ban|banning]]. BZFX administrators are trained to use the appropriate reprimands for each offense and it's severity.

All chat is logged at BZFX servers. You may be reprimanded if deemed fit by server logs. BZFX's rules are to be obeyed at all times, even when an administrator is not around. Also, young kids play at BZFX. One of BZFX's major goals is to be an always family-friendly atmosphere and BZFX will do whatever necessary to enforce that.

If you have been reprimanded for breaking a rule, and would like to contact someone about it, please contact the administrator that did the reparations directly. If you can not find out how to contact them directly, use other modes of [[#Contact|contact]] to get in touch with the administrator. They are more than prepared to deal with issues directly with an offender. If, for some reason, you can not work it out with the administrator, [[User:A_Meteorite|A Meteorite]] will be contacted. Please note that contacting either the administrator that reprimanded you or A Meteorite will '''not get you a free ride'''. The only issue that will be discussed is whether or not you are guilty of breaking a BZFX rule. If you are, then there will always be a reparation for it. The reparation may be lessened, though, if BZFX deems you truly remorseful of your actions.

= Administration =

BZFX servers are administered to the highest standards possible. All BZFX admins and cops are trained in their duties and the rules.

Never ask to be added to a group. It will not happen. Players are selected based on previous experience, behavior, and general people skills. Also, people who contribute to BZFX are '''generally''' privileged to a group.

== Groups ==

There is a distinct hierarchy to BZFX's administration system. Each group holds a meaning, which is described below.

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

== Current Staff ==

Below is the current administration staff of BZFX listed in no particular order:

* '''BZFX.hAdmin''' (Head Admin):
** A Meteorite
** tadd
** daniel_jackson
** Win Xp

* '''BZFX.Admin''':
** BinarySpike
** boofhead
** Cedric.
** ducatiwannabe
** Dumbledore
** Evil Bob
** Flutterby
** High Karate Kitty
** Lady K
** Rio_Dj_Narrow
** Sky King
** SportChick
** TD-Linux

* '''BZFX.Cop''':
** BIYA
** brad2901
** dartman
** elem3nt
** G5 Serenity Again
** Genosse Dark Lord
** Matt?
** Rover Blaster
** SilverFox
** Slayer++
** Theme97
** Think_Different
** USS Enterprise

* '''BZFX.Hidden''':
** BZFX does not reveal these members

Talk:BZFX

2007-04-06T01:59:57Z

A Meteorite: /* DonnyBaker's page removal */

Talk:BZFX

2007-04-06T01:59:31Z

A Meteorite: