BZFlagWiki - User contributions [en]

Packetloss

2010-10-02T21:39:19Z

Yassen: Couple more spelling errors.

Packetloss is a term used in networking to describe an event where some of the data sent between computers does not reach the intended destination.

This loss of data can have detrimental effects on software that is expecting the data. In the case of BZFlag this data loss causes player tanks to not show correctly on remote clients and causes the game play mechanics to fail.

Many BZFlag game servers will force a user to disconnect if his/her packetloss is too high in order to ensure a playable game for the rest of the players.

=Display=
BZFlag can display a '''packet loss percentage''' in its lagstats. This represents an approximation of the current data loss for the user. The number is computed by keeping track of how many lagping packets are sent and how many are received. This ratio is the packetloss.

=Causes=
All packetloss happens in the network layer of a connection. The most common cause is a weak or intermittent network connection on a client's network. Low frame rate can cause [[Lag]] but not packetloss.

==Wireless networks==
By far the most common reason for both high packetloss and high [[Jitter]] is poor wireless networking at the client end. Wireless networks are easily interrupted by interference from other radio signals. This includes both WIFI, cellular, and satellite connections. Many of these connection technologies are not suited for high speed gaming.

===Common Solutions===
The most basic thing to try when attempting to resolve WIFI related issues is to connect client directly to the internet over an Ethernet cable. If that is not possible then changing the channel that the WIFI uses may help to reduce interference. Other issues are often are often not repairable by the end user, or just a limitation of the connection technology (i.e. satellite).

==Internet Route==
The route from the client to the server can also have packetloss, especially if the server is a long physical distance from the client, or the internet route is complex. These types of issues generally can not be resolved by the end user and are simply the nature of internet data transmissions.

BZFlag 2.99

2010-06-30T21:12:22Z

Yassen: First quarter of 2010 is past us as well.

BZFlag version 3.0 is the next planned release of BZFlag.

==Overview==
Version 3.0 is currently in development and marked as version v2.99.x. Upon release it will be marked as version v3.0. The primary goals for this version are improved server side stability and security in an effort to minimize the impact of clients that have been modified to provide their users benefit ( aka, cheating ). Additional efforts are being made to extend the server side customization of the game. v3.0 will be completely incompatible with all previous versions of the game. Users of v3.0 will only be able to play on 3.0 servers. This is similar to how v2.0 was incompatible with 1.10.

==Development==
Development began on 3.0 on October 25th 2005. After an initial rush of changes, development stalled, as a number of bugs were found in the current release build of the time ([[BZFlag 2.0.4|v2.0.4]]). These bugs ,a number of graphical changes from [[trepan]], as well as other problems necessitated the release of compatible [[BZFlag 2.0.6|v2.0.6]], [[BZFlag 2.0.8|v2.0.8]], [[BZFlag 2.0.10|v2.0.10]], [[BZFlag 2.0.12|v2.0.12]] and [[BZFlag 2.0.14|v2.0.14]] versions.

==Version Number Change==
v3.0 is the first version to use the new version numbering system. The 3.0 release initially began as the 2.1 development line, with the intent of being released as version 2.2. Part of the way through development, however, the [[Versions|versioning]] number scheme changed and the development revision changed from 2.1 to 2.99. With previous releases the minor version number in the version triplet (major.minor.revision) represented protocol and client compatibility. With 3.0 compatibility is instead reflected in the major version number. This new scheme gives more "room" to deal with minor packaging revisions and patch release updates.

==Features==
v3.0 has a number of features that make for a much improved gameplay experience.

===Fonts===
The font system has been replaced and now uses standard TrueType fonts([http://en.wikipedia.org/wiki/TrueType TTF]). This offers a number of advantages over the older bitmap based font system, including support for unicode character sets.

Users can now set the default fonts that they wish to use on a per-locale basis so they can use the best fonts for their character set. (More info on how?)

===Server Side Logic===
A number of gameplay features have been moved from the client to the server, to ensure more consistent gameplay and prevent cheating over the internet, including;
* Flag operations (pickup, capture, identify, etc)
* Pause/unpause
* Shot type

===Game state and security checks===
Many changes and enhancements have been made to the network protocol to prevent errors in the network message stream or shared game state.

===BZW Format===
*Links can now be included in groups, with relative naming.
*Mesh faces can now be used as teleportation link sources (with numerous options)
*Mesh faces can now be used as team bases (must be flat tops).
*Mesh faces can now be used as zones (must be flat tops).
*Meshes can now contain weapon objects.
*World Text objects have been added (with numerous options)
*Dynamic Colors now use a simpler format.
*Solid objects can now specify the 'ricochet' property individually.

===Graphics===
Changes have been made to the graphical quality settings. What was Experimental quality in 2.0.12 is now High quality. Medium quality is between the old High and Medium, and Low has remained mostly unchanged.

The new Experimental mode includes new shot and flag graphics.

===New Server List===
The list of servers has been enhanced to allow tabbed browsing as well as improved searching and sorting.

===HUD Markers===
If HUD markers showing flag position, GM lockon are now shown to players. THe name and team of the closest target is also shown, helping prevent teamkills. Servers can turn off this feature for all players if desired.

===BZFS API===
The [[BZFS API]] has been reviewed and re-factored for 3.0 and includes a number of new events and functions.

====Server Side Players====
The API has experimental support for server side players (bots).

====Custom Flag Names====
The API may define new custom flag names using any strings desired. The ammount of logic that can be processed for custom flags is limited.

====HTTP based plug-ins====
The networking system for BZFS now allows for the support of HTTP (and other ) connections. A number of plugins have been made to take advantage of this new feature, such as;
* [[Fastmap]]
* [[Webadmin]]
* [[Webreport]]
* [[Webstats]]

====BZFS API Versioning====
The versioning system in the BZFS API has been redone, and now event data classes are versioned for forward computability. Custom plug-ins that were written for v2.0.x must be updated to use the new classnames before they will work with v3.0.x. This should only be a one time change as the new classes are versioned and will remain the same in future releases. All standard plug-ins that ship with the bzflag source code have been updated.

===Lua BZFS API===
The lua scripting language (http://lua.org), is now built into the bzfs executable, and exposes almost all of the features from the C++ BZFS API (and a few that the C++ API does not have). It has the advantages of being easier to learn and write than comparable C++ code, and it can be embedded in world files. The main disadvantage is that it is not as fast as native c++ code.

===Server Administration===
Some changes have been made to help you server administrators.

The [[Webadmin]] plug-in allows server owners to manage many aspects of the server from a standard web browsers.

====Local Authentication====
Local authentication ( '''/identify''' ), has been removed from the game, servers can use global authentication services for all authentication needs.

===Gameplay Changes===
A number of changes have been made to the game that will subtly affect gameplay.
====Acceleration====
Tank acceleration is now always on. The "-a" server option has been removed, and the acceleration values are pulled from BZDB variables. These variables are _inertiaLinear and _inertiaAngular.

====Lag Compensation====
Clients now use a synced timestmap and attempt to compensate tank positions for lag. This can change the way the game feels for players that are used to "leading" the target based on its lag.

====Hit Volume====
The volume that defines a "hit" on a tank has been changed. It is now a box around the tank that can be adjusted by the server using BZDB variables.

====No TK Option====
A new server option (-noTeamKills) is available that will prevent players from killing their teammates.

===Build System===
Much effort has been put into making the bzflag source tree easier to compile on various OSs. The makefile build system has been updated and attempts to detect as many items as possible from the host System. The windows build system has been updated to be compatible with Visual Studio 2008 Express Edition that is freely available. When possible, copies of third party libraries are included with the source code.

===Bug Fixes===
A student is being paid as part of the Google Summer of Code program to evaluate and fix the backlog of reported bugs in the software. This will have the overall effect of increasing the stability of the game.

===ChangeLog===
A full list of changes can be found in the [http://bzflag.svn.sourceforge.net/viewvc/*checkout*/bzflag/trunk/bzflag/NEWS NEWS] file in the [[BZFlag Source]] code in [[BZFlag SVN|SVN]].

==Known Issues==
A lot of stuff needs testing, and probably doesn't work.

==Release Date==
As is always the case for major updates to BZFlag, '''''3.0 will be released when it is done'''''. It is possible that the release will occur in the fourth quarter of 2010, the first quarter of 2011, or the third quarter of 2020.

==Misconceptions about V3.0==
There have been a few misconceptions in the community regarding what this new version will and will not do. Most of this is simply due to the exceptionally long development time, or comments being taken out of context.

'''V3 will do everything Server Side, including shots'''

This is untrue. While more things have been moved to the server, shoots and hits are still handled by the client. Shots and hits will not be moved to the server until the code can be shown to maintain the level of response time that players have come to expect.

'''V3 will use more bandwith and be laggy'''

V3 does a better job of handling network traffic to and from players. Many messages have been reduced in size. Server side handling of some events, (like flag grabs) have actually removed some messages from the network stream. Network performance should be similar to V2.x. In some cases, lag compensation may even improve apparent performance.

==See also==
[[Versions]]

[[V3RCChecklist]]

[[Category:Versions]]

Master Ban

2010-06-24T21:20:33Z

Yassen: Undo revision 7081 by 98.234.111.141 (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]]

Compiling

2010-03-28T19:36:58Z

Yassen: /* 2.99.x */ Update DirectX SDK Version

==Overview==
Compiling BZFlag is the act of taking the raw source codes for the game and using tools to build an executable application(s) for a target system.

==Source Code==
In order to compile a user must have his or her own copy of the [[BZFlag_Source|Source Code]]. The code can be obtained from a source archive from the [[Download]] page, or from the BZFlag [[BZFlag_SVN|Subversion]] server.

==Readme Files==
Users should always read the README files for the appropriate operating system. These files are located in the root directory of the source code tree.

==Compilers==
BZFlag is capable of being built on a number of compilers. The compiler used will depend in some way on the operating system of the computer doing the build.

* Linux and BSD computers use the GCC compiler.
* Macintosh computers use the XCode compiler (or gcc, see notes).
* Windows computers can use the Visual C++ compiler, or the MinGW compiler (based on GCC)

===GCC===
The GCC build as a number of requirements;
* Automake X.XX
* Autoconf X.XX
* Autotools X.XX
* SDL Development libraries 1.2.10 or greater (on Mac OS X you need 2.99 from svn and SDL 1.3 which is also only in SVN, to build BZFlag x86_64 binaries; i386 binaries should build fine using Mac OS X version 10.6 after setting the correct environment variables to avoid building x86_64 instead)
* OpenGL Development libraries 1.1 or greater

If the required dependencies are installed, the user must then run the following commands from at root level of the source tree

./autogen.sh
./configure
make
make install

Please note that depending on permissions levels the '''make install''' command may need to be run as an administrator or root.
On Mac you can either run make to find any problems, or xcodebuild (after ./configure) to make an .app that is useable.

===XCode===
Launch XCode and open the '''bzflag/BZFlag.xcodeproj''' project. Note that XCode should have '''BZFlag''' selected as the active target and '''Development''' as the active build configuration. Click on '''Targets''' then click the '''Build''' icon. When this process completes, your application will be in '''bzflag/build/Development'''. You can then move it wherever you like.

====Building on Snow Leopard====
Snow Leopard defaults to 64-bit binaries, which isn't compatible with MacDisplay.cxx due to Carbon.framework not implementing a lot of functionality in 64-bit mode. To compile on Snow Leopard, you must build 32-bit.

===Visual C++===

==== 2.0.x ====

'''Compiler''' 
In order to compile, you need to have Visual C++ 2003 or higher (Express version works just fine). 
To get the latest Express version of Visual C++, visit [http://www.microsoft.com/express/vc/ http://www.microsoft.com/express/vc/] 

'''Dependencies'''

In order to compile you need '''ALL''' of the following: 
[http://www.microsoft.com/downloads/details.aspx?FamilyID=86cf7fa2-e953-475c-abde-f016e4f7b61a&DisplayLang=en Microsoft DirectX SDK April 2007] (Only the Headers and Libraries) 
[http://www.microsoft.com/downloads/details.aspx?familyid=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&displaylang=en Windows Platform SDK] (This is not required for Visual C++ 2008) 
[http://curl.haxx.se/download/libcurl-7.18.0-win32-msvc.zip LibCURL] 
[http://sourceforge.net/project/downloading.php?group_id=67586&use_mirror=superb-east&filename=glew-1.5.1-win32.zip&1970168 GLEW] 
[http://sourceforge.net/project/downloading.php?group_id=30480&use_mirror=superb-west&filename=pdc34dll.zip&38017788 PDCurses] 

You then need to add them to your VC++ Directories, both include and lib folders.

==== 2.99.x ====

'''Compiler''' 
In order to compile, you need to have Visual C++ 2008 or higher (Express version works just fine). 
To get the latest Express version of Visual C++, visit [http://www.microsoft.com/express/vc/ http://www.microsoft.com/express/vc/] 

'''Dependencies''' 

[http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=2c7da5fb-ffbb-4af6-8c66-651cbd28ca15 Microsoft DirectX SDK Febuary 2010] 
[http://sourceforge.net/project/downloading.php?group_id=30480&use_mirror=superb-west&filename=pdc34dll.zip&38017788 PDCurses] 

You then need to add them to your VC++ Directories, both include and lib folders.

===Other build systems===
Other build systems may be supported in the various readme files (minGW, IRIX, SOLARIS,etc..)

===Solaris 10 (Oct, 2009)===

This is what I had to do to get bzflag-2.0.12 to compile and run on Solaris 10

Install Sparc packages (in /opt) from [http://sunfreeware.com Sunfreeware]

'''You don't necessarily have to install in /opt'''. If not, skip all the "opt" stuff or substitute the correct location instead. Most of these packages will install in /usr/local. /usr/local was not available to me.

<pre>
curl-7.19.6-sol10-sparc-local.gz
libidn-1.14-sol10-sparc-local.gz
libssh2-1.2-sol10-sparc-local.gz
openssl-0.9.8k-sol10-sparc-local.gz
libintl-3.4.0-sol10-sparc-local.gz
libiconv-1.11-sol10-sparc-local.gz
</pre>
If you get an error saying that a library has moved, you might have to go into the library's .la file and update its location.

You will also have to update the *.la files if you get errors like this:

libtool: link: cannot find the library `/usr/local/lib/libidn.la' or unhandled argument `/usr/local/lib/libidn.la'

You will have to update these lines in SMCliconv/lib/libiconv.la, etc:

dependency_libs=' -R/usr/local/lib -R/usr/lib -R/usr/openwin/lib -R/opt/SMCossl/ssl/lib -R/usr/local/BerkeleyDB.4.7/lib -R/usr/local/BerkeleyDB.4.2/lib -R/usr/X11R6/lib
-L/usr/local/lib -L/usr/lib -L/usr/openwin/lib -L/opt/SMCossl/ssl/lib -L/usr/local/BerkeleyDB.4.2/lib /opt/SMClibidn/lib/libidn.la -L/usr/local/pgsql/lib
-L/usr/X11R6/lib /opt/SMClintl/lib/libintl.la -lsec -lc /opt/SMClssh2/lib/libssh2.la /opt/SMCliconv/lib/libiconv.la -lssl -lcrypto -lsocket -lnsl -lz'

Fix missing links

ln -s /usr/sfw/bin/gmake /usr/sfw/bin/make

ln -s /usr/xpg4/bin/ar /usr/bin/ar

Modify environment variables
<pre>

export CPPFLAGS="-I/opt/SMClintl/include -I/opt/SMCossl/ssl/include -I/opt/SMCcurl/include -I/opt/SMClssh2/include"
export CPPFLAGS="$CPPFLAGS -I/opt/SMClibidn/include -L/opt/SMClintl/lib -L/opt/SMCossl/ssl/lib -L/opt/SMCcurl/lib "
export CPPFLAGS="$CPPFLAGS -L/opt/SMClssh2/lib -L/opt/SMClibidn/lib -L/opt/c-ares/lib -L/pt/SMCossl/ssl/lib -I/usr/openwin/include/GL"

export LDFLAGS="-L/usr/lib -L/opt/SMClintl/lib -L/opt/SMClibidn/lib -L/opt/SMClssh2/lib"

export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/opt/SMCcurl/lib:/opt/SMClibidn/lib:/opt/SMClintl/lib:/opt/SMClssh2/lib:/opt/SMCliconv/lib:/opt/SMCossl/lib:/opt/SMCossl/ssl/lib"
</pre>
Run configure
<pre>
./configure --with-libcurl=/opt/SMCcurl --prefix=/opt/bzflag --build=sun4
</pre>
Edit sources
<pre>
In include/SceneNode.h, change "glColor" to myColor":
(Solves the "Expected ')' before '->' token" error)

#define myColor3f(r, g, b) SceneNode::myColor3f(r, g, b)
#define myColor4f(r, g, b, a) SceneNode::myColor4f(r, g, b, a)
#define myColor3fv(rgb) SceneNode::myColor3fv(rgb)
#define myColor4fv(rgba) SceneNode::myColor4fv(rgba)

static void myColor3f(GLfloat r, GLfloat g, GLfloat b)
#ifdef __MINGW32__
{if (!colorOverride) ::myColor3f(r, g, b); };
#else
{ (*color3f)(r, g, b); }
#endif

static void myColor4f(GLfloat r, GLfloat g, GLfloat b, GLfloat a)
#ifdef __MINGW32__
{if (!colorOverride) ::myColor4f(r, g, b, a); };
#else
{ (*color4f)(r, g, b, a); }
#endif

static void myColor3fv(const GLfloat* rgb)
#ifdef __MINGW32__
{if (!colorOverride) ::myColor3fv(rgb); };
#else
{ (*color3fv)(rgb); }
#endif

static void myColor4fv(const GLfloat* rgba)
#ifdef __MINGW32__
{if (!colorOverride) ::myColor4fv(rgba); };
#else
</pre>
Fix Makefiles
<pre>
Add -lresolv to LIBS in src/bzfs/Makefile, src/bzflag/Makefile, src/bzadmin/Makefile
(Solves the inet_aton unresolved symbol error)

LIBS = -lsocket -lm -lresolv

In src/platform edit the Makefile and uncomment the Solaris stuff:

am_libPlatform_la_OBJECTS = PlatformFactory.lo \
BzfDisplay.lo \
BzfJoystick.lo \
BzfVisual.lo \
BzfWindow.lo \
BzfMedia.lo \
wave.lo \
SolarisPlatformFactory.lo \
SolarisMedia.lo \
XDisplay.lo \
XVisual.lo \
XWindow.lo

(Makes sure platform.a gets built - this can probably be done with a configure switch, but I couldn't find it)
</pre>
Make and test!

make; src/bzflag/bzflag

[[Category:Development]]
[[Category:Compiling]]
[[Category:Tutorials]]

Bz fireWorldWep

2009-05-17T19:16:46Z

Yassen: Add some more information

{{apicall
| name = bz_fireWorldWep
| description = Fires a world weapon.
| param1 = flagType
| param1type = const char*
| param1desc = Flag type the world weapon will fire with.
| param2 = lifetime
| param2type = float
| param2desc = How long the world weapon will "live".
| param3 = *pos
| param3type = float
| param3desc = Position the world weapon will fire from.
| param4 = tilt
| param4type = float
| param4desc = The tilt of the weapon in radians.
| param5 = direction
| param5type = float
| param5desc = The direction of which to fire the world weapon in radians. (rotation)
| param6 = shotID
| param6type = int
| param6desc = Shot ID of the world weapon. Each shot is given a unique shot ID for shot tracking.
| param7 = dt
| param7type = float
| param7desc = Delay time. How many seconds the weapon waits before firing.
}}

User talk:Me1/Style Merges

2009-05-15T04:56:59Z

Yassen:

*Talking about [[Free For All]], [[Capture the Flag]] and [[Rabbit Hunt]]

These pages/stubs don't really need to be separate. It'd be better if they were in one article, instead of three.
Anyone disagree? --[[User:Me1|Me1]] 18:19, 9 April 2009 (EDT)

I would tend to agree with you on this, Me1. I suggest they be merged into one 'Game Modes' article.

I (Ratfink) definitely agree that they should be merged, me1.

Same here, Game Modes should be fine. (Yassen)

Jargon

2009-05-13T20:48:35Z

Yassen: Fix the link

This page hopes to clarify some common jargon, acronyms and slang used by many players in game. They can be useful to know, especially in team situations, as other players will assume that you know what they are talking about.

Many players use map "landmarks," like "mid tower" or "@ R jump," to signify places on the map, so it's a good idea to learn your maps as well as the jargon.

= Acronyms =

<properties>
CTF=[[Capture the Flag]]
FFA=[[Free For All]]
RH=[[Rabbit Hunt]]
KOTH=King of the Hill
R=(Team's) Right
L=(Team's) Left
RF=Red flag
GF=Green flag
BF=Blue flag
PF=Purple flag
HF=Have fun
GJ=Good Job. Often said to the team when a teammate has just captured the opposing team's flag
GL=Good Luck
GS=Good shot. Generally used when a particularly difficult shot kills you
GG=Good game
G1=Good One (shot)
NP=No Problem - mostly used as a response if you're teamkilled
NS=Nice Shot
N1=Nice One (shot)
SRY=Sorry
THX=Thank You
TK=Team Kill, to kill one's own team.
TY=Thank You
WTF?=Something's not quite right..... (Vulgar)
WTH?=Similar to WTF - cleaner version
</properties>

= Jargon =

<properties>
Bots=Non-human-player tanks.
Capping=Capturing the other teams flag, verb ''to cap''.
Ours=Protect your team flag, or used to signify your team's base.
Theirs=Attack the other team's flag, or used to signify the other team's base.
Geno=Genocide Flag, usually when seen it chat by itself it means an opposing team player has the flag so be careful
Pass=Send the flag to the middle, or to a safe zone. See [[Jumping#Dropping_Flags|this article]].
Pyr=Pyramid
Tele=Teleporter
Base=Usually referring to your own base. (ex: st base!)
In=Inside the base (if applicable)
Out=Directly outside the base (if applicable)
Mid=Middle of the map
Jump/Jumper/Launcher=Either a world object that launches a tank in the air, or a tank that has used said world object.
Spamming=Filling the chat box with meaningless text.
Laser Spamming=Uselessly, blindly, rapidly shooting with the laser flag, often resulting in team kills.
Camping=Staying in one place with the same flag for a long time. If you do this you are ''a camper''.
Flag Running=Working against your own team, and taking your flag towards the other team's base. If you do this you are a ''flag runner''.
Flag Shopping=Rapidly picking up and dropping flags, in order to find a particularly powerful or useful one. Also known as ''flag farming''.
Lang=Language, Watch your language. (Please don't respond with the language you speak.)
Watch!=Watch out! or Guard! (ex: Watch ours!)
</properties>

= See Also =
* [[Flag List|Flag Abbreviations]]
* [http://en.wiktionary.org/wiki/Appendix:Internet_slang Common Internet Slang]

[[Category:Gameplay]]

Jargon

2009-05-13T20:46:56Z

Yassen: If we aren't going to allow slang or flag abbreviations, at least have links to where you can find them

Bz zapPlayer

2009-05-05T23:40:54Z

Yassen: /* Returns */ Oops, this isn't BBCode

{{BZFS_API_Doc}}{{BZFS_API_Funcs}}
==Prototype==
BZF_API bool bz_zapPlayer(int player );

==Parameters==
; int player : Player index to force a respawn.

==Returns==
False if the player does not exist, or is alive. 
True if the operation completed.

==Description==
This function is used to force a player to respawn. Her or his client will simply respawn and continue playing. Any flags will be dropped. Plug-ins that wish to move the player to a specific location must provide that position on the [[bz_eGetPlayerSpawnPosEvent]] event.

==Version==
Requires BZFS 2.99.5 (20080809, r18308) or later

Bz zapPlayer

2009-05-05T23:39:47Z

Yassen: /* Returns */ Shouldn't work if the player is alive, not the other way around

{{BZFS_API_Doc}}{{BZFS_API_Funcs}}
==Prototype==
BZF_API bool bz_zapPlayer(int player );

==Parameters==
; int player : Player index to force a respawn.

==Returns==
False if the player does not exist, or is alive.[br]
True if the operation completed.

==Description==
This function is used to force a player to respawn. Her or his client will simply respawn and continue playing. Any flags will be dropped. Plug-ins that wish to move the player to a specific location must provide that position on the [[bz_eGetPlayerSpawnPosEvent]] event.

==Version==
Requires BZFS 2.99.5 (20080809, r18308) or later

Compiling

2009-02-12T03:13:53Z

Yassen: /* Visual C++ */ More detail and list of deps

Plugin functions

2009-02-12T02:32:09Z

Yassen: Redirect to Functions(API)

#REDIRECT [[Functions(API)]]

BZFlag API

2009-02-12T02:30:44Z

Yassen: Pointer to BZFS API

'''Did you mean [[BZFS API]]?'''

BZFlag API Functions

2009-02-12T02:28:10Z

Yassen: Redirect to Functions(API)

#REDIRECT [[Functions(API)]]

API Functions

2009-02-12T02:27:39Z

Yassen: Redirect to Functions(API)

#REDIRECT [[Functions(API)]]

Bz kickUser

2009-02-12T01:36:08Z

Yassen: Added bz_kickUser

{{apicall
| name = bz_kickUser
| description = Kicks an user from the server (same as the /kick command)
| param1 = playerIndex
| param1type = int
| param1desc = Player to kick.
| param2 = reason
| param2type = const char*
| param2desc = Reason for the kick.
| param3 = notify
| param3type = bool
| param3desc = Whether to notify the admin channel and user kicked.
| returntype = bool
| returns = Whether the player exists.
| version = 2.0.x or later
}}

Bz resetBZDBVar

2009-02-12T01:27:20Z

Yassen: You can reset all variables using this function.

{{apicall
| name = bz_resetBZDBVar
| description = Resets the value of a variable. (Putting "" as the variable will reset them all)
| param1 = variable
| param1type = const char*
| param1desc = The variable to reset.
| returntype = void
}}

Bz getBZDBVarList

2009-02-12T01:25:25Z

Yassen: Added bz_getBZDBVarList

{{apicall
| name = bz_getBZDBVarList
| description = Gets a list of all the BZDB variables.
| param1 = *varList
| param1type = bz_APIStringList
| param1desc = The variable list.
| returntype = int
| returns = The amount of variables.
| version = 2.99.x or later
}}

Bz resetALLBZDBVars

2009-02-12T01:22:13Z

Yassen: Added bz_resetALLBZDBVars

{{apicall
| name = bz_resetALLBZDBVars
| description = Resets all the BZDB (/set) variables.
| param1type = void
| returntype = void
| version = 2.0.x or later
}}

Bz setMaxWaitTime

2009-02-12T01:20:23Z

Yassen: Added bz_setMaxWaitTime

{{apicall
| name = bz_setMaxWaitTime
| description = Sets the maximum wait (or idle) time.
| param1 = maxTime
| param1type = float
| param1desc = Maximum idle time.
| returntype = void
| version = 2.0.x or later
}}

Bz getMaxWaitTime

2009-02-12T01:19:33Z

Yassen: Added bz_getMaxWaitTime

{{apicall
| name = bz_getMaxWaitTime
| description = Returns the maximum wait (or idle) time for the server.
| param1type = void
| returntype = float
| returns = The maximum wait time.
| version = 2.0.x or later
}}

Bz getCurrentTime

2009-02-12T01:18:29Z

Yassen: Added bz_getCurrentTime

{{apicall
| name = bz_getCurrentTime
| description = Gets the current server time.
| param1type = void
| returntype = double
| returns = The server time (in seconds)
| version = 2.0.x or later
}}

Bz removeRabbit

2009-02-12T01:16:10Z

Yassen: Added bz_removeRabbit

{{apicall
| name = bz_removeRabbit
| description = Changes the player provided to a hunter.
| param1 = player
| param1type = int
| param1desc = Player to change to hunter.
| returntype = void
| version = 2.99.x or later
}}

Bz newRabbit

2009-02-12T01:14:57Z

Yassen: Added bz_newRabbit

{{apicall
| name = bz_newRabbit
| description = Sets a new rabbit in the rabbit chase game mode.
| param1 = player
| param1type = int
| param1desc = Player to make rabbit.
| param2 = swap
| param2type = bool
| param2desc = Whether to swap the old rabbit for the new rabbit, or make two rabbits.
| returntype = void
| version = 2.99.x or later
}}

Bz reloadGroups

2009-02-12T01:10:50Z

Yassen: Added bz_reloadGroups

{{apicall
| name = bz_reloadGroups
| description = Reloads the group file for the server.
| returntype = void
| version = 2.0.x or later
}}

Bz reloadHelp

2009-02-12T01:10:28Z

Yassen: Added bz_reloadHelp

{{apicall
| name = bz_reloadHelp
| description = Reloads the help files for the server.
| returntype = void
| version = 2.0.x or later
}}

Bz reloadUsers

2009-02-12T01:10:09Z

Yassen: bz_reloadUsers

{{apicall
| name = bz_reloadUsers
| description = Reloads the user database for the server
| returntype = void
| version = 2.0.x or later
}}

Bz reloadMasterBans

2009-02-12T01:09:53Z

Yassen: Added bz_reloadMasterBans

{{apicall
| name = bz_reloadMasterBans
| description = Reloads the master ban list.
| returntype = void
| version = 2.0.x or later
}}

Bz reloadLocalBans

2009-02-12T01:09:34Z

Yassen: Added bz_reloadLocalBans

{{apicall
| name = bz_reloadLocalBans
| description = Reloads the local ban list.
| returntype = void
| version = 2.0.x or later
}}

Bz anyPlayers

2009-02-12T01:08:13Z

Yassen: Added bz_anyPlayer

{{apicall
| name = bz_anyPlayers
| description = Returns true if there is any players on the server.
| param1type = void
| returntype = bool
| returns = True if there is any players connected, false otherwise.
| version = 2.99.x or later
}}

Bz getPlayerCount

2009-02-12T01:06:57Z

Yassen: Added bz_getPlayerCount

{{apicall
| name = bz_getPlayerCount
| description = Returns the number of users on the server.
| param1type = void
| returntype = int
| returns = Number of users on the server.
| version = 2.99.x or later
}}

Bz superkill

2009-02-12T01:05:12Z

Yassen: Added bz_superkill

{{apicall
| name = bz_superkill
| description = Kicks all users from the server.
| returntype = void
| version = 2.0.x or later
}}

Bz shutdown

2009-02-12T00:58:14Z

Yassen: Added bz_shutdown

{{apicall
| name = bz_shutdown
| description = Shutsdown the server.
| returntype = void
| version = 2.0.x or later
}}

Bz groupAllowPerm

2009-02-12T00:56:44Z

Yassen: Doesn't return a bz_APIStringList, but rather a bool. (typo)

{{apicall
| name = bz_groupAllowPerm
| description = Grants the group a certain permission.
| param1 = group
| param1type = const char*
| param1desc = Group to look up.
| param2 = perm
| param2type = const char*
| param2desc = Permission to grant.
| returntype = bool
| returns = Whether the group provided exists.
| version = 2.0.x or later
}}

Bz groupAllowPerm

2009-02-12T00:55:53Z

Yassen: Added bz_groupAllowPerm

{{apicall
| name = bz_groupAllowPerm
| description = Grants the group a certain permission.
| param1 = group
| param1type = const char*
| param1desc = Group to look up.
| param2 = perm
| param2type = const char*
| param2desc = Permission to grant.
| returntype = bz_APIStringList*
| returns = Whether the group provided exists.
| version = 2.0.x or later
}}

Bz getGroupPerms

2009-02-12T00:52:46Z

Yassen: Added bz_getGroupPerms

{{apicall
| name = bz_getGroupPerms
| description = Returns the list of permissions for the group provided.
| param1 = group
| param1type = const char*
| param1desc = Group to look up.
| returntype = bz_APIStringList*
| returns = Permissions for the group provided.
| version = 2.0.x or later
}}

Bz getGroupList

2009-02-12T00:50:19Z

Yassen: Added bz_getGroupList

{{apicall
| name = bz_getGroupList
| description = Returns the groups on the server.
| param1type = void
| returntype = bz_APIStringList*
| returns = List of groups on the server.
| version = 2.0.x or later
}}

Bz getPlayerPacketloss

2009-02-12T00:48:35Z

Yassen: Added bz_getPlayerPacketloss

{{apicall
| name = bz_getPlayerPacketloss
| description = Returns the amount of packetloss the player has.
| param1 = playerId
| param1type = int
| param1desc = Player to lookup.
| returntype = float
| returns = Amount of packetloss the player has.
| version = 2.0.x or later
}}

Bz getPlayerJitter

2009-02-12T00:47:31Z

Yassen: Added bz_getPlayerJitter

{{apicall
| name = bz_getPlayerJitter
| description = Returns the amount of jitter the player has.
| param1 = playerId
| param1type = int
| param1desc = Player to lookup.
| returntype = int
| returns = Amount of jitter the player has.
| version = 2.0.x or later
}}

Bz getPlayerLag

2009-02-12T00:47:05Z

Yassen: Added bz_getPlayerLag

{{apicall
| name = bz_getPlayerLag
| description = Returns the amount of lag the player has.
| param1 = playerId
| param1type = int
| param1desc = Player to lookup.
| returntype = int
| returns = Amount of lag the player has.
| version = 2.0.x or later
}}

Bz getPlayerRank

2009-02-12T00:45:15Z

Yassen: Added bz_getPlayerRank

{{apicall
| name = bz_getPlayerRank
| description = Returns the rank of the player given.
| param1 = playerId
| param1type = int
| param1desc = Player to lookup.
| returntype = float
| returns = Rank of the player.
| version = 2.99.x or later
}}

Bz getPlayerTKs

2009-02-12T00:44:05Z

Yassen: Added bz_getPlayerTKs

{{apicall
| name = bz_getPlayerTKs
| description = Returns the amount of TKs for the player given.
| param1 = playerId
| param1type = int
| param1desc = Player to lookup.
| returntype = int
| returns = Amount of TKs the player has.
| version = 2.99.x or later
}}

Bz getPlayerLosses

2009-02-12T00:42:59Z

Yassen: Added bz_getPlayerLosses

{{apicall
| name = bz_getPlayerLosses
| description = Returns the amount of losses for the player given.
| param1 = playerId
| param1type = int
| param1desc = Player to lookup.
| returntype = int
| returns = Amount of losses of the player.
| version = 2.99.x or later
}}

Bz getPlayerWins

2009-02-12T00:42:26Z

Yassen: Added bz_getPlayerWins

{{apicall
| name = bz_getPlayerWins
| description = Returns the amount of wins for the player given.
| param1 = playerId
| param1type = int
| param1desc = Player to lookup.
| returntype = int
| returns = Amount of wins of the player.
| version = 2.99.x or later
}}

Bz deleteIntList

2009-02-12T00:39:31Z

Yassen: typo

{{apicall
| name = bz_deleteIntList
| description = Deletes the bz_APIIntList given freeing up memory.
| param1 = *l
| param1type = bz_APIIntList
| param1desc = Int list to delete.
| returntype = void
| version = 2.0.x or later
}}

Bz deleteIntList

2009-02-12T00:38:48Z

Yassen: Added bz_deleteIntList

{{apicall
| name = bz_getPlayerByCallsign
| description = Deletes the bz_APIIntList given freeing up memory.
| param1 = *l
| param1type = bz_APIIntList
| param1desc = Int list to delete.
| returntype = void
| version = 2.0.x or later
}}

Bz newIntList

2009-02-12T00:37:38Z

Yassen: Added bz_newIntList

{{apicall
| name = bz_newIntList
| description = Creates a new bz_APIIntList. (example: bz_APIIntList playerlist = bz_newIntList(); )
| param1type = void
| returntype = bz_APIIntList
| version = 2.0.x or later
}}

Bz getPlayerByBZID

2009-02-12T00:33:42Z

Yassen: bz_getPlayerByBZID

{{apicall
| name = bz_getPlayerByBZID
| description = Gets a bz_PlayerRecord for a player based on the BZID (must be a registered user) given.
| param1 = BZID
| param1type = int
| param1desc = BZID to look up.
| returntype = bz_PlayerRecord
| returns = Player record of the player of which the BZID belongs to.
| version = 2.99.x or later
}}

Bz getPlayerByCallsign

2009-02-12T00:30:13Z

Yassen: Added bz_getPlayerByCallsign

{{apicall
| name = bz_getPlayerByCallsign
| description = Gets a bz_PlayerRecord for a player based on the callsign given.
| param1 = name
| param1type = const char*
| param1desc = Player to lookup.
| returntype = bz_PlayerRecord
| returns = Player record of the player of which the callsign belongs to.
| version = 2.99.x or later
}}

Bz getPlayerAngVel

2009-02-12T00:21:39Z

Yassen: Added bz_getPlayerAngVel

{{apicall
| name = bz_getPlayerAngVel
| description = Fills the float "angvel" with the current angular velocity of the player.
| param1 = playerID
| param1type = int
| param1desc = Player to lookup.
| param2 = *angvel
| param2type = float
| param2desc = Angular Velocity
| returntype = bool
| returns = Whether the player exists.
| version = 2.99.x or later
}}