|This article relies too much on references to primary sources. (June 2009) (Learn how and when to remove this template message)|
A screenshot from version 2.0.14
|Original author(s)||Chris Schoeneman|
|Developer(s)||Tim Riker, David Trowbidge, Sean Morrison|
2.4.8 / October 11, 2016
BZFlag was originally written in C by Chris Schoeneman (creator of Synergy) in 1992 based on the chart-topping hit arcade game, Battlezone. At first, BZFlag was called "bz" and despite its similarity to the SGI game of the same title by Chris Fouts, both games were completely independent of each other. Originally, BZFlag was simply a shoot 'em up game with no other modes. However, after Schoeneman and his friend Rick Pasetto (who helped Schoeneman develop BZFlag from the beginning) became bored with the concept, they invented the capture-the-flag mode. This new mode added a requirement of strategy, teamwork, and skill, which was sufficient to keep interest.
In 1993, BZFlag was released to the public for the first time. This release took a new turn compared to older versions after a cheater, who edited the source code of his client to give himself powers that do not come from official releases, inspired Schoeneman and Pasetto to add "super-flags." Super flags affect a tank's performance by adding abilities or weapons to its arsenal. The first four flags were High Speed (boosted tank speed), Quick Turn (tank turned faster), Rapid Fire (shots moved faster), and Oscillation Overthruster (tank could go through objects). There was only one of each flag, and all flags had a marker on them so tanks knew what type it was. Soon after, bad and good flags were added, and the idea remains part of game play today; however, flags do not have markers and the flag type is unknown to the player until it is picked up (unless the player's tank is carrying an identify flag).
In 1997, the release of version 1.7d came with a groundbreaking new feature: an in-game public server list. Previously, players had to either set up their own servers, know of servers, or read a list published and maintained by a third-party. Now the server list is hosted on the official BZFlag website and allows anybody to play games on servers that choose to be public.
Schoeneman eventually re-wrote BZFlag in C++ for SGI's third IndiZone competition, which won in the "Reality Engine" category. Tim Riker was later given the project prior to version 1.7e to maintain and evolve.
BZFlag is written in C++ and uses OpenGL for rendering. Its audio and several other sub-systems (such as window management and file access) have been written using OS specific methods, although newer releases use SDL to perform low-level operations on all platforms. Textures for in-game objects are loaded from PNG files; audio, from WAVs. Zlib is used to decompress data files, which is written in C.
The number of contributors to the project has steadily increased over time. The project invites all sufficiently experienced developers to contribute. Though there are currently[update] 64 listed developers, a much smaller number of those are active contributors.
Developers are able to edit any of the project's files to make changes at any time. However, when a developer has made an edit of which other developers do not approve, or is inappropriate for the game, they are requested to revert to the previous version of the file; most developers monitor source edits on IRC.
The copyright holder for the game is Tim Riker but maintenance is guided by Scott Wichser and Jeff Makey as project managers. The game's original author, Chris Schoeneman, is no longer involved in development.
In a game of BZFlag, players drive around tanks, viewed from a first-person view, in a server-defined world (also known as a "map"), which can be modified. Tanks have the ability to drive through other tanks, but cannot travel through buildings or other world objects. The basic objective is to destroy opponents' tanks, which are tanks of another team's color. Since all players can see the position of all the tanks on their radar, it is a game of outmaneuvering rather than sneaking.
There are styles of game play that modify the objective. Styles are server-based, as the server operator chooses what style to host. If there is no special style indicated by the server owner, the only objective is the above (to simply kill opponent tanks); it is called a "free for all", or "FFA" for short.
There are three other objectives and corresponding styles (four in total): a style called "capture-the-flag" (or "CTF" for short) in which tanks try to pick up an opponent's flag and bring to their own home base, a style called "rabbit chase" in which the objective is to have every hunter (orange)tank try to destroy a particular white tank, called the "rabbit," and a style called "King of the Hill," in which a team attempts to stay in a certain area for 30–60 seconds without being killed. If they succeed, that team becomes "The King of the Hill."
Servers can change the game mode and have custom maps made to fit the properties of the game. Certain thresholds are used to catch malicious players and kick them off the server, as well as message filters and an entire collection of other anti-cheating features. There are around 250 servers active at any given time (although only about 10-20% have active players most of the time).
Tanks can join as one of the four team colors, as a rogue, or as an observer. Observers cannot play, but can move anywhere in the world and watch what the tank they are linked to is doing. Observers do not have a tank and are therefore not visible to players, but are shown in the scoreboard. The colored teams are Red, Green, Blue and Purple. Rogue players are teamless players: they are allowed to kill colored team players and other rogues. Rogue tanks are colored dark grey out the window, and yellow on the radar.
In rabbit-hunt games there is a white tank, known as the "rabbit", against the orange-brown "hunters", or every other player. The hunters are considered a team, so rabbits with genocide, shockwave, Guided Missile, or Laser flags are dangerous, and often team kills occur due to a group assault on the "rabbit."
Teams are necessary in capture-the-flag games, in which they have to protect their team flag from capture. Because rogues are occasionally allowed on servers, a rogue tank does not have any flag to defend, and in turn cannot capture flags. However, rogues usually tend to aid other teams of choice, or merely enjoy adding a distraction to all teams. There is a plugin to prevent this, however it is only used on servers with two large teams and one or two rogue players.
A BZFlag server can be configured to create a basic, random map for play, or users can load custom map files. BZFlag uses a customized text based map format to define the placement of objects. While writing a map is fairly simple in this format, most map-makers use a 3d modeling program Wings 3D, or blender. Graphical map editors, BZEdit or iBZEdit have also been used. Note that BZEdit is not distributed with the game, and is no longer under active development (versions of it are available at the BZFlag SourceForge.net site). However, using blender in combination with a BZFlag map plug-in is currently the most popular mapping method.
As to the simplicity of maps, there are a number of basic objects in a map: boxes, pyramids, teleporters, cones, arcs, cylinders, spheres, team bases and meshes. Teleporters are rectangular, yellow-bordered objects that teleport a tank to another teleporter. A mapmaker may choose to not have a teleporter teleport tanks by leaving out links, or simple definitions of two points for teleporters to link between. Teleporters are also capable of teleporting to themselves, reflecting bullets and tanks that enter. Team Bases are used for CTF style games. Full three dimensional meshes have been available in maps since the 2.0 release.
BZFlag has three types of flags: team flags, bad flags and super flags. Team flags are only placed in a world during a capture-the-flag game, and represent the team it is colored to. Super flags are flags that can be in both free-for-all games and capture-the-flag games, but are strongly controlled by a server operator. The number, types of super flags, as well as where they are placed can all be controlled by the operator. Super flags come in both bad and good form, and affect a tank accordingly. A bad flag may take away a certain sense of the tank: its sight, speed, or related things, while a good flag does the opposite and actually helps a tank. Good super flags are usually held until the tank is killed and explodes, or until the player driving the tank chooses to drop the flag. Bad flags are dropped after a short amount of time, after a certain amount of "wins", or until the tank dies. The rules for dropping bad flags are set by the operator. All super flags have a one or two letter code that is displayed next to a player's name on the scoreboard when that player has that flag. Once in a while, a new flag is introduced, which anyone can contribute to via developer contact or the wiki.
Servers have environments that simulate the real world. A server's environment consists of three things: The map in play, the time of day that is being simulated, and weather conditions, introducing elements of which players have no control, like rain, snow, icy and/or slippery ground, modified friction and gravity, and fog. BZFlag takes the local time from the geographical location of the server and creates a night or day-time atmosphere in the background. Servers may synchronize the local server time or allow players to change the time to any time they may desire.
BZFlag was selected in Summer 2015 as "HotPick" by Linux Format. BZFlag was selected as the SourceForge.net Project of the Month for April 2004. Both Free Software Magazine and Linux Magazine noted that BZFlag was fun to play and suitable for younger gamers.
- Chris Schoeneman (2003). "SVN revision 20629". sourceforge. Retrieved September 16, 2009.
- "bzflag/README at d85df040e26d831cfea875338ad599a29f9614a0 · BZFlag-Dev/bzflag". GitHub. Retrieved 2016-10-11.
- Diehl, Mike (2007-10-18). "Free Games for Linux". Linux Journal. Retrieved 2010-10-13.
- "stats.bzflag.org - Welcome!". Stats.bzflag.org. Archived from the original on 2008-09-08. Retrieved 2008-10-28.
- Berg, Alan. "Bzflags- Kill or be Killed". Free Software Magazine.
- Tim Riker (2006). "SVN revision 12251". sourceforge. Retrieved June 24, 2007.
- Tim Riker (2006). "SVN revision 19236". sourceforge. Retrieved April 10, 2009.
- Linux Format Summer 2015 page 56
- "April 2004 - BZFlag". Project of the Month. SourceForge, Inc. 2004. Retrieved 2007-09-03.
|Wikimedia Commons has media related to BZFlag.|