BZFlagWiki - User contributions [en]

https://wiki.bzflag.org/api.php?action=feedcontributions&feedformat=atom&user=Yrogirg BZFlagWiki - User contributions [en] 2026-05-19T12:17:58Z User contributions MediaWiki 1.43.5 https://wiki.bzflag.org/index.php?title=Jargon&diff=8170 Jargon 2011-12-25T12:10:29Z

<p>Yrogirg: /* Acronyms */</p> <hr /> <div>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.<br /> <br /> 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.<br /> <br /> = Acronyms =<br /> <br /> <br /> CTF=[[Capture the Flag]]<br /> <br /> FFA=[[Free For All]]<br /> <br /> OFFA=Open Free For All (Everyone may kill each other regardless of team color)<br /> <br /> RH=[[Rabbit Hunt]]<br /> <br /> HTF=Hold the Flag<br /> <br /> KOTH=King of the Hill<br /> <br /> R=(Team's) Right<br /> <br /> L=(Team's) Left<br /> <br /> RF=Red flag<br /> <br /> GF=Green flag<br /> <br /> BF=Blue flag<br /> <br /> PF=Purple flag<br /> <br /> HF=Have fun<br /> <br /> GC=Good Cap. - Used when your team caps an opposing teams flag<br /> <br /> GJ=Good Job. Often said to the team when a teammate has just captured the opposing team's flag<br /> <br /> GL=Good Luck<br /> <br /> GS=Good shot. Generally used when a particularly difficult shot kills you<br /> <br /> GG=Good game<br /> <br /> G1=Good One (shot)<br /> <br /> NP=No Problem - mostly used as a response if you're teamkilled<br /> <br /> NR=Not Responding - as seen on the scoreboard, indicating a problem with a player's connection to the server<br /> <br /> NS=Nice Shot<br /> <br /> N1=Nice One (shot)<br /> <br /> SRY=Sorry<br /> <br /> THX=Thank You<br /> <br /> TK=Team Kill, to kill one's own team.<br /> <br /> TY=Thank You<br /> <br /> WTF?=Something's not quite right..... (Vulgar)<br /> <br /> WTH?=Similar to WTF - cleaner version<br /> <br /> PC=Pass Camp: Stand on the enemies base waiting for a teammate to capture the flag. Then, after the cap immediately grab the enemies flag and pass it to the center of the map <br /> or to its map specific save-point. Saying this could either mean, that your own team is getting "passcamped" or that there is a chance to passcamp for the own team's score.<br /> <br /> = Jargon =<br /> <br /> Base=Usually referring to your own base. (eg: ST base! "There's someone with stealth in/at/near our base")<br /> <br /> Boom=Players of a team about to be capped will all explode. Thus a "boom" is appropriate.<br /> <br /> Bots=Non-human-player tanks.<br /> <br /> Camping=Staying in one place with the same flag for a long time. If you do this you are ''a camper''.<br /> <br /> Capping=Capturing the other teams flag, verb ''to cap''.<br /> <br /> Flag Running=Working against your own team, taking your team's flag towards the other team's base. If you do this you are a ''flag runner''.<br /> <br /> Flag Shopping=Rapidly picking up and dropping flags, in order to find a particularly powerful or useful one. Also known as ''flag farming''.<br /> <br /> Geno, G, or GGG =Genocide Flag, usually when seen it chat by itself it warns that an opposing team player has the flag so be careful.<br /> <br /> In=Inside the base (if applicable)<br /> <br /> J/Jump/Jumper/Launcher=Either a world object that launches a tank in the air, or a tank that has used said world object. "st j r" means stealth jumper right.<br /> <br /> Lang=Language, Watch your language. (Please don't respond with the language you speak.)<br /> <br /> Laser Spamming=Uselessly, blindly, rapidly shooting with the laser flag, often resulting in team kills.<br /> <br /> N, S, E, W=North, South, East, West. Compass points relative to the map. (eg: "Where the rabbit?" "N inside hut" or "SE corner")<br /> <br /> Out=Directly outside the base (if applicable)<br /> <br /> Mid, or Ctr=Middle of the map<br /> <br /> Pass=Send the flag to the middle, or to a safe zone. See [[Jumping#Dropping_Flags|this article]].<br /> <br /> Pyr/Pyra=Pyramid<br /> <br /> Runner=Usually means "flag runner", above as in "we have a runner" but may also mean teammate carrying enemy flag as in "cover our runner."<br /> <br /> Spamming=Filling the chat box with meaningless text.<br /> <br /> Spawn camping=Sitting near a team's spawn site waiting to kill them when they respawn after their flag is captured.<br /> <br /> Spawn killing=Killing someone as soon as they spawn.<br /> <br /> Tele=Teleporter<br /> <br /> Theirs=Attack the other team's flag, or used to signify the other team's base.<br /> <br /> Twr=Tower, as in "ST on the right GM Twr"<br /> <br /> Ours=Protect your team flag, or used to signify your team's base.<br /> <br /> Watch!=Watch out! or Guard! (eg: Watch ours!)<br /> <br /> Win=Kill everyone on the map. At the same time.<br /> <br /> = See Also =<br /> * [[Flag List|Flag Abbreviations]]<br /> * [http://en.wiktionary.org/wiki/Appendix:Internet_slang Common Internet Slang]<br /> <br /> [[Category:Gameplay]]</div>

Yrogirg https://wiki.bzflag.org/index.php?title=BZFlag_2.99&diff=7394 BZFlag 2.99 2011-01-14T06:47:29Z

<p>Yrogirg: /* Release Date */ we are moving to the third quarter of 2020</p> <hr /> <div>BZFlag version 3.0 is the next planned release of BZFlag. <br /> <br /> ==Overview==<br /> 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.<br /> <br /> ==Development==<br /> 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.<br /> <br /> ==Version Number Change==<br /> 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.<br /> <br /> ==Features==<br /> v3.0 has a number of features that make for a much improved gameplay experience.<br /> <br /> ===Fonts===<br /> 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. <br /> <br /> 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?)<br /> <br /> ===Server Side Logic===<br /> 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;<br /> * Flag operations (pickup, capture, identify, etc)<br /> * Pause/unpause<br /> * Shot type<br /> <br /> ===Game state and security checks===<br /> Many changes and enhancements have been made to the network protocol to prevent errors in the network message stream or shared game state.<br /> <br /> ===BZW Format===<br /> *Links can now be included in groups, with relative naming.<br /> *Mesh faces can now be used as teleportation link sources (with numerous options)<br /> *Mesh faces can now be used as team bases (must be flat tops).<br /> *Mesh faces can now be used as zones (must be flat tops).<br /> *Meshes can now contain weapon objects.<br /> *World Text objects have been added (with numerous options)<br /> *Dynamic Colors now use a simpler format.<br /> *Solid objects can now specify the 'ricochet' property individually.<br /> <br /> ===Graphics===<br /> 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.<br /> <br /> The new Experimental mode includes new shot and flag graphics.<br /> <br /> ===New Server List===<br /> The list of servers has been enhanced to allow tabbed browsing as well as improved searching and sorting.<br /> <br /> ===HUD Markers===<br /> 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.<br /> <br /> ===BZFS API===<br /> The [[BZFS API]] has been reviewed and re-factored for 3.0 and includes a number of new events and functions.<br /> <br /> ====Server Side Players====<br /> The API has experimental support for server side players (bots).<br /> <br /> ====Custom Flag Names====<br /> 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.<br /> <br /> ====HTTP based plug-ins====<br /> 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;<br /> * [[Fastmap]]<br /> * [[Webadmin]]<br /> * [[Webreport]]<br /> * [[Webstats]]<br /> <br /> ====BZFS API Versioning====<br /> 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.<br /> <br /> ===Lua BZFS API===<br /> 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.<br /> <br /> ===Server Administration===<br /> Some changes have been made to help you server administrators.<br /> <br /> The [[Webadmin]] plug-in allows server owners to manage many aspects of the server from a standard web browsers.<br /> <br /> ====Local Authentication====<br /> Local authentication ( '''/identify''' ), has been removed from the game, servers can use global authentication services for all authentication needs.<br /> <br /> ===Gameplay Changes===<br /> A number of changes have been made to the game that will subtly affect gameplay.<br /> ====Acceleration====<br /> 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.<br /> <br /> ====Lag Compensation====<br /> 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.<br /> <br /> ====Hit Volume====<br /> 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.<br /> <br /> ====No TK Option====<br /> A new server option (-noTeamKills) is available that will prevent players from killing their teammates.<br /> <br /> ===Build System===<br /> 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.<br /> <br /> ===Bug Fixes===<br /> 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.<br /> <br /> ===ChangeLog===<br /> 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]].<br /> <br /> ==Known Issues==<br /> A lot of stuff needs testing, and probably doesn't work.<br /> <br /> ==Release Date==<br /> 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 first quarter of 2011, or the third quarter of 2020.<br /> <br /> ==Misconceptions about V3.0==<br /> 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.<br /> <br /> '''V3 will do everything Server Side, including shots'''<br /> <br /> 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.<br /> <br /> '''V3 will use more bandwith and be laggy'''<br /> <br /> 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.<br /> <br /> ==See also==<br /> [[Versions]]<br /> <br /> [[V3RCChecklist]]<br /> <br /> [[Category:Versions]]</div>

Yrogirg https://wiki.bzflag.org/index.php?title=World_units&diff=7393 World units 2011-01-13T08:30:48Z

<p>Yrogirg: Tank length is 6</p> <hr /> <div>A world unit is the basic unit of measure when dealing with BZFlag. World units have no real-world counterpart, as they are a purely virtual concept, but they can be though of to be equivalent to about 1 meter in length if you assume a roughly real world sized [[tank]].<br /> <br /> All coordinates in the map file are specified in World Units. Many [[Server Variables]] are specified in terms of world units or world units per second as well.<br /> <br /> ==Origin==<br /> The origin for the World coordinate system is the center of the map.<br /> <br /> ==Orientation==<br /> World Units are oriented in a normal right hand rule coordinate system with positive Z being the "UP" direction.<br /> <br /> ===North===<br /> "north" on the in game radar is the positive Y direction in map coordinates.<br /> <br /> ===Figure 1===<br /> This image shows a typical map, with the origin and axis directions clearly marked out.<br /> [[Image:MapCoordinateSystem.png]]<br /> <br /> == Some useful measures at default settings ==<br /> <div align="center"><br /> {| cellpadding="0" cellspacing="0" border="1" width="60%"<br /> |- <br /> |width="60%"|Jump height limit (next to impossible)<br /> |width="20%"|See below<br /> |width="10%"|18.42<br /> |- <br /> |Common jump height<br /> |See below<br /> |17.0<br /> |-<br /> |Tank length<br /> |_tankLength<br /> |6.0<br /> |-<br /> |Tank width<br /> |_tankWidth<br /> |2.8<br /> |-<br /> |Tank height<br /> |_tankHeight<br /> |2.05<br /> |-<br /> |Barrel height<br /> |_muzzleHeight<br /> |1.57<br /> |-<br /> |Drivable bump height<br /> |_bumpHeight<br /> |0.33<br /> |-<br /> |}<br /> </div><br /> <br /> == Calculating jump height ==<br /> Jump height is determined by the gravity and jump velocity settings on the server (see [[Server Variables]] for details). Note that the jump velocity and gravity may be altered by flags including [[Flag List|Low Gravity]] and [[Flag List|Wings]].<br /> <br /> :Max jump height = -(_jumpVelocity)<sup>2</sup> / (2 * (_gravity))<br /> <br /> A typical BZFlag player can reliably jump a bit more than 90% of the maximum jump height.<br /> <br /> [[Category:Map Making]]<br /> [[Category:Concepts]]</div>

Yrogirg https://wiki.bzflag.org/index.php?title=Server_Variables&diff=7134 Server Variables 2010-08-05T04:46:50Z

<p>Yrogirg: </p> <hr /> <div>The BZFlag Server (BZFS) allows administrators to configure a large number of gameplay and configuration settings from within the client. The /set command in-game allows users with the appropriate permissions to change these values. These may also be known as BZDB variables and "/set variables" depending on who you speak with.<br /> <br /> Unless otherwise noted, time values are measured in seconds, distances in [[world units]], and speeds in [[world units]] per second.<br /> <br /> {{InfoBox|Note|Some values, such as _worldSize, only take affect at server start since they affect the world file that is generated. It is recommended to apply these in the map file so they are loaded with the map.}}<br /> {|{{Prettytable}}<br /> |-<br /> |{{Hl3}}|'''Name'''<br /> |{{Hl3}}|'''Default'''<br /> |{{Hl3}}|'''Description'''<br /> |-<br /> | _agilityAdVel || 2.25 || Multiplies _tankSpeed for tanks holding Agility flag for a specified amount of time (_agilityTimeWindow)<br /> |-<br /> | _agilityTimeWindow || 1 || The amount of time (in seconds)that the tank will have the speed specified by _agilityAdVel<br /> |-<br /> | _agilityVelDelta || 0.3 || <br /> |-<br /> | _ambientLight || none ||<br /> |-<br /> | _angleTolerance || 0.05 || If a tank has turned more than it was expected to, plus this tolerance, a new update is sent so the other clients are aware of the change in heading<br /> |-<br /> | _angularAd || 1.5 || Multiplies _tankAngVel to determine how fast tanks can turn while holding the Quick Turn flag<br /> |-<br /> | _avenueSize || 2*_boxBase || Space to leave between objects in random maps?<br /> |-<br /> | _baseSize || 60 || Width and Depth (bases have constant height) of the square bases for CTF games<br /> |-<br /> | _boxBase || 30 || Width and Depth of boxes on a random map?<br /> |-<br /> | _boxHeight || 6*_muzzleHeight || Height of boxes on a random map?<br /> |-<br /> | _burrowDepth || -1.32 || Determines how far down tanks drop when they have the Burrow Flag. Making this much lower makes it below the floor, and impossible to kill the tank without something like a ShockWave flag!<br /> |-<br /> | _burrowSpeedAd || .8 || Multiplied by _tankSpeed to determine how fast tanks holding the Burrow Flag move.<br /> |-<br /> | _burrowAngularAd || .55 || Multiplied by _tankAngVel to determine how fast tanks can turn while holding the Burrow flag.<br /> |-<br /> | _coldetDepth || 6 ||<br /> |-<br /> | _coldetElements || 4 || <br /> |-<br /> | _countdownResumeDelay || 5 || This enforces a delay when resuming a paused countdown. If the argument is lower or equal to 0 then resuming is instantly, otherwise it is delayed according to the value (in seconds). ''Available in 2.1 and later''<br /> |-<br /> | _cullDepth || 6 ||<br /> |-<br /> | _cullDist || fog || Far plane culling distance ('fog' uses the fog parameters).<br /> |-<br /> | _cullElements || 16 || <br /> |-<br /> | _cullOccluders || 0 ||<br /> |-<br /> | _disableBots || none || A value of 1 in this variable does not allow autopilot or bots on the server, equivalent to the old -prohibitbots command line option. <br /> |-<br /> | _disableSpeedChecks || 0 || Allows disabling/enabling the speed kicks.<br /> |-<br /> | _disableHeightChecks || 0 || Allows disabling/enabling the "too high" check (or maybe the out of the world boundaries check in general).<br /> |-<br /> | _drawCelestial || 1 || Draw the stars, sun, and moon.<br /> |-<br /> | _drawClouds || 1 || Draw the clouds.<br /> |-<br /> | _drawGround || 1 || Draw the ground plane.<br /> |-<br /> | _drawGroundLights || 1 || If set to 0, lights on the ground (such as the light from bullets) will not be drawn.<br /> |-<br /> | _drawMountains || 1 || Draw the mountains.<br /> |-<br /> | _drawSky || 1 || Draw the sky pyramid.<br /> |-<br /> | _enableDistanceCheck || 0 || Distance checking tries to verify if a player moved too far between updates (as in, cheating).<br /> |-<br /> | _endShotDetection || 5 || This setting controls how many "end shot" messages can be sent without corresponding deaths (or other reasons, such as a shield drop).<br /> |-<br /> | _explodeTime || 5 || After a tank is killed, this is how long it takes to blow up, and then "respawn". Larger values translates into longer explosions and more client processor time. Note that an explosion is invisible if you are inside it, so large values may make it invisible up close, and extremely large values may make explosions entirely invisible.<br /> |-<br /> | _flagAltitude || 11 || The height that the flag flies up when dropped and the height that a flag spawns at.<br /> |-<br /> | _flagEffectTime || 0.64 || How much time it takes for the flag to go into effect.<br /> |-<br /> | _flagHeight || 10 || The height of the flag (not its pole).<br /> |-<br /> | _flagPoleWidth || 0.025 || The diameter of the flag pole.<br /> |-<br /> | _flagPoleSize || 0.8 || The height of the flag pole.<br /> |-<br /> | _flagRadius || 2.5 || Determines how close a tank must be to a flag to pick it up.<br /> |-<br /> | _fogMode || none || Valid values: linear, exp, or exp2.<br /> |-<br /> | _fogDensity || 0.001 || Used for exp and exp2 fog modes.<br /> |-<br /> | _fogNoSky || 0 || 1 will turn off fog drawing on the sky. The default is fog everywhere.<br /> |-<br /> | _fogStart || 0.5*_worldSize || Used for linear fog mode, the distance where fog begins to occlude vision.<br /> |-<br /> | _fogEnd || _worldSize || Used for linear fog mode, the distance where the fog occludes everything.<br /> |-<br /> | _fogColor || "0.25 0.25 0.25" || RGB or black, red, blue (alpha is ignored).<br /> |-<br /> | _friction || 0 || Zero is normal friction, the closer to 0 the harder it is to start and stop, and the higher the number the easier it is to start and stop.<br /> |-<br /> | _gmActivationTime || 0.5 || The amount of time (in seconds) it takes for a Guided Missile to become active after it is fired. Any contact under this time will not result in detonation (setting it too low could cause its owner to run into its own GM and be blown up!<br /> |-<br /> | _gmAdLife || 0.95 || Multiplied by _shotRange to determine the distance guided missiles will go.<br /> |-<br /> | _gmTurnAngle || 0.628319 || The angle at which a Guided Missile will turn to follow its target. (Measured in radians)<br /> |-<br /> | _gravity || -9.8 || The rate at which a tank will fall (or be kept from jumping) Measured in [[World units]]/Seconds^2. Setting this to a zero or positive value will result in tanks being unable to stay down and will float away.<br /> |-<br /> | _handicapScoreDiff || 50 || How much of a score difference (from the leader?) there must be for a player to get a handicap<br /> |-<br /> | _handicapVelAd || 2 || Player with handicap will receive this much more (_tankSpeed + _handicapVelAd) velocity than the normal _tankSpeed value.<br>''**Note: These could be factors rather than additions''<br /> |-<br /> | _handicapAngAd || 1.5 || Player with handicap will receive this much more (_angularAd + _handicapAngAd) turning ability than the normal _angularAd. <br>''**Note: These could be factors rather than additions''<br /> |-<br /> | _handicapShotAd || 1.75 || ''**Note: These could be factors rather than additions''<br /> |-<br /> | _identifyRange || 50 || If a flag is this distance or closer to a tank carrying the Identify (ID) flag, it will display the closest flag's type.<br /> |-<br /> | _inertiaAngular || 38 || Sets the maximum angular acceleration. Available in version 3.0. Replaces the "-a" option. <br /> |-<br /> | _inertiaLinear || 45 || Sets the maximum linear acceleration. Available in version 3.0. Replaces the "-a" option. <br /> |-<br /> | _jumpVelocity || 19 || The speed a tank moves vertically while jumping.<br /> |-<br /> | _laserAdVel || 1000 || The length of each laser shot. Lasers aren't exactly "infinite" as their description states, they go on for as long as this variable states.<br /> |-<br /> | _laserAdRate || 0.5 || Multiplied by _rFireAdRate to determine the firing rate for a laser.<br /> |-<br /> | _laserAdLife || 0.1 || The amount of time (in seconds) that a laser remains after being fired.<br /> |-<br /> | _latitude || 37.5 || The latitude at which the world exists. This affects the timezone.<br /> |-<br /> | _lgGravity|| 12.7 || Modifies the gravity for owners of the Low Gravity flag. Similar to the _gravity variable. ''Available starting in version 2.1''<br /> |-<br /> | _lockOnAngle || 0.15 || Angle (in radians) in relation to tanks heading (positive or negative) that will allow a Guided Missile to lock onto a target.<br /> |-<br /> | _longitude || 122 || The longitude at which the world exists. This affects the timezone.<br /> |-<br /> | _lRAdRate || 0.5 ||<br /> |-<br /> | _maxBumpHeight || 0.33 || Any difference between the surface a tank is on and the top surface of an object the tank runs into that is less than this value will allow the tank to simply move up to the object rather than being stopped by it.<br /> |-<br /> | _maxFlagGrabs || 4.0 || How many times a flag can be dropped before it respawns. At the first spawn, flags are assigned a random # between 1 and _maxFlagGrabs. Each grab reduces that number by 1, until zero is reached, then the flag spawns at a new location. Flags will always respawn no matter how many flag grabs they have left if dropped over an 'unsafe' zone.<br /> |-<br /> | _maxLOD || 32767 || The max level of detail to allow.<br /> |-<br /> | _mirror || none || Options: '''white''', '''black''', '''red''', '''blue''', '''pink''', '''purple''', '''orange''', etc... ("black 0.75" is a good setting, some invalid options such as '''mirror''' will give a mirror look)<br /> |-<br /> | _momentumLinAcc || 1 || Momentum flag's effect on going forwards and backwards.<br /> |-<br /> | _momentumAngAcc || 1 || Momentum flag's effect on turning.<br /> |-<br /> | _momentumFriction || 0 || Friction (same as _friction) when holding the Momentum flag.<br /> |-<br /> | _mGunAdVel || 1/_mGunAdRate || The speed of the machine gun's bullets.<br /> |-<br /> | _mGunAdRate || 10 || _reloadTime divided by _mGunAdRate gives how long machine gun bullets take to reload.<br /> |-<br /> | _mGunAdLife || 1.5 || Multiplied by _shotRange to determine the distance machine gun bullets go.<br /> |-<br /> | _muzzleFront || _tankRadius + 0.1 || Location of muzzle of tank (affects bullets and player camera location).<br /> |-<br /> | _muzzleHeight || 1.57 || See _muzzleFront.<br /> |-<br /> | _noClimb || 1 || Allow or disallow climbing on sloped surfaces. A value of 0 allows, 1 disallows.<br /> |-<br /> | _noShadows || 0 || Enables or disables shadows. A value of 0 allows, 1 disallows.<br /> |-<br /> | _noSmallPackets || 0 ||<br /> |-<br /> | _notRespondingTime || 5 || The amount of time (in seconds) the server should wait before reporting a tank as not responding.<br /> |-<br /> | _obeseFactor || 2.5 || Multiplier of normal size that determines how big a tank gets when carrying the Obese flag.<br /> |-<br /> | _pauseDropTime || 15 || The amount of time (in seconds) that a tank needs to be paused before its flag is dropped automatically.<br /> |-<br /> | _positionTolerance || 0.09 || <br /> |-<br /> | _pyrBase || 4 * _tankHeight || Base size of pyramids generated by the default random map generator.<br /> |-<br /> | _pyrHeight || 5 * _tankHeight || Height of pyramids generated by the default random map generator.<br /> |-<br /> | _radarLimit || _worldSize || The maximum area that the radar can see (when not rotated).<br /> |-<br /> | _rainBaseColor || none || When _rainType = rain, sets color of the bottom of raindrops.<br /> |-<br /> | _rainDensity || none || Determines how many drops of rain are in the space defined by _rainSpread.<br /> |-<br /> | _rainEndZ || none || The height above the ground where rain should stop falling.<br /> |-<br /> | _rainMaxPuddleTime || none || The amount of time (in seconds) a rain puddle should exist before disappearing.<br /> |-<br /> | _rainPuddleSpeed || none || The speed at which puddles should spread out.<br /> |-<br /> | _rainPuddleColor || none || Color of rain puddles. none means no puddle.<br /> |-<br /> | _rainPuddleTexture ||none || Texture of puddles. Best to leave default.<br /> |-<br /> | _rainRoofs || 1 || '''0''' rain falls through everything<br>'''1''' rain hits buildings, but puddles are only on the ground<br>'''2''' rain hits buildings, and creates puddles on them<br /> |-<br /> | _rainSpread || none || The radius from center of map where rain will fall.<br /> |-<br /> | _rainSpeed || none || The speed at which the rain falls.<br /> |-<br /> | _rainSpeedMod || none || Randomizes _rainSpeed by adding/subtracting up to this number from each raindrop's speed<br /> |-<br /> | _rainSpins || none || '''0''' Rain does not spin as it falls<br>'''1''' Rain spins as it falls.<br /> |-<br /> | _rainStartZ || none || The height above ground that rain should fall from.<br /> |-<br /> | _rainTexture || none || The name of the texture in data directory.<br>''Works with _rainTypes of frog, particle, bubble, snow, fatrain''<br /> |-<br /> | _rainTopColor ||none || When _rainType = rain, sets color of the top of raindrops.<br /> |-<br /> | _rainType || none || Adjusts all _rain* and _use* variables automatically<br>Valid Options : '''frog''', '''particle''', '''rain''', '''bubble''', '''snow''', '''fatrain'''<br /> |-<br /> | _rejoinTime || _explodeTime || The number of seconds before clients can rejoin a game, after they leave.<br /> |-<br /> | _rejumpTime || 0.01 || From version 3.0. Time a tank has to wait before he can jump again after landing. Any value higher than 0 will make it difficult to jump away from sloped faces like pyramids.<br /> |-<br /> | _reloadTime || _shotRange/_shotSpeed || Time between shot reloads, note that this can cut shot range short.<br /> |-<br /> | _rFireAdVel || 1.5 || Multiplied by _shotSpeed to determine the speed of the rapid fire bullets.<br /> |-<br /> | _rFireAdRate || 2 || The reload time (in seconds) for rapid fire bullets.<br /> |-<br /> | _rFireAdLife || 1/_rFireAdRate || How long the rapid fire bullets last.<br /> |-<br /> | _shieldFlight || 2.7 || The amount of time (in seconds) that a shield flag floats in the air (after you drop it) before coming down again.<br /> |-<br /> | _shockAdLife || 0.2 || The amount of time (in seconds) that a shockwave lasts.<br /> |-<br /> | _shockInRadius || _tankLength || The starting radius of the shockwave. Negative values will make the shockwave shrink and expand.<br /> |-<br /> | _shockOutRadius || 60 || The outer radius of the shockwave. If greater than _shockInRadius, the shockwave expands outward. If less than _shockInRadius, the shockwave starts big and shrinks inward.<br /> |-<br /> | _shotRadius || 0.5 || For collision detection.<br /> |-<br /> | _shotRange || 350 || Range of shots, note that they can be cut short by _reloadTime.<br /> |-<br /> | _shotSpeed || 100 || Speed of shots.<br /> |-<br /> | _shotTailLength || 4 || <br /> |-<br /> | _shotsKeepVerticalVelocity || 0 || If '''0''', shots always move straight in relation to the ground. If '''1''', shots are affected vertically by the tank's speed, and can fly up and down. Lasers are also affected. <br /> |-<br /> | _skyColor || white || Sets the sky to a specific color.<br /> |-<br /> | _spawnMaxCompTime || 0.01 || This controls the maximum amount of time to attempt finding a safe spawn location. If this time is exceeded, the tank will just get dropped in from maximum height. The time should be in seconds, so the default is to only wait for 10ms.<br /> |-<br /> | _spawnSafeRadMod || 20 || <br /> |-<br /> |_spawnSafeSRMod || 20 || prevent spawning people near steamroller.<br /> |-<br /> |_spawnSafeSWMod || 1.5 || prevent spawning people near shock wave.<br /> |-<br /> | _speedChecksLogOnly || 0 || If set to 1, someone moving too fast will not get kicked - it will just log it to the stdout.<br /> |-<br /> | _srRadiusMult || 2 || Radius of steamroller effect.<br /> |-<br /> | _squishFactor || 1 || How much tanks squish when landing.<br /> |-<br /> | _squishTime || 1 || How much squishy time you get after falling to the ground.<br /> |-<br /> | _syncTime || 1 || Whether or not to sync the players time with the servers'.<br /> |-<br /> | _syncLocation || 0 || Whether or not to sync the location time with the servers'.<br /> |-<br /> | _tankAngVel || 0.785398 || How fast the tank can turn.<br /> |-<br /> | _tankExplosionSize || 3.5 * _tankLength || How large the tank's explosion is.<br /> |-<br /> | _tankHeight || 2.05 || The height of the tank.<br /> |-<br /> | _tankLength || 6 || The length of the tank.<br /> |-<br /> | _tankRadius || 0.72 * _tankLength || The radius of the tank.<br /> |-<br /> | _tankSpeed || 25 || The speed of the tank<br /> |-<br /> | _tankWidth || 2.8 || The width of the tank.<br /> |-<br /> | _targetingAngle || 0.3|| Something to do with GM... <br /> |-<br /> | _teleportBreadth || 4.48|| Random maps?<br /> |-<br /> | _teleportHeight || 10.08 || See _teleportBreadth.<br /> |-<br /> | _teleportTime || 1 ||<br /> |-<br /> | _teleportWidth || 1.12 || See _teleportHeight.<br /> |-<br /> | _thiefAdLife || 0.05 || The amount of time (in seconds) that a thief shot lasts.<br /> |-<br /> | _thiefAdRate || 12 || The amount of time (in seconds) that the Thief "shot" reloads.<br /> |-<br /> | _thiefAdShotVel || 8 || The speed of thief.<br /> |-<br /> | _thiefTinyFactor || 0.5|| Multiplied by the normal tank size to shrink a tank carrying the thief flag.<br /> |-<br /> | _thiefVelAd || 1.67 || Multiplied by _tankSpeed to determine how fast tanks holding the thief goes.<br /> |-<br /> | _thiefDropTime || reloadTime * 0.5 ||The amount of time you must wait to fire a shot after stealing a flag.<br /> |-<br /> | _tinyFactor || 0.4 || Multiplied by the normal tank size to shrink a tank carrying the tiny flag.<br /> |-<br /> | _trackFade || 3 || The amount of time (in seconds) before track marks fade.<br /> |-<br /> | _updateThrottleRate || 30 ||<br /> |-<br /> | _useLineRain || none || '''0''' Rain is not a vertical line<br>'''1''' Rain is vertical lines, smoothly shaded from _rainTopColor to _rainBaseColor<br /> |-<br /> | _useRainPuddles || none || '''0''' Rain does not create puddles<br>'''1''' Rain creates puddles<br /> |-<br /> | _useRainBillboards || none || '''0''' Rain is lines or polygons<br>'''1''' Rain is billboards, textured and look the same from all angles<br /> |-<br /> | _velocityAd || 1.5 || Multiplies _tankSpeed to determine the speed of a tank carrying the high speed (V) flag<br /> |-<br /> | _wallHeight || 3 * _tankHeight|| The outer wall height.<br /> |-<br /> | _weapons || 1 || Used with world weapons, '''0''' world weapons will not fire<br>'''1''' world weapons will fire<br /> |-<br /> | _wideAngleAng || 1.745329 || The viewing angle when a tank has the Wide Angle bad flag.<br /> |-<br /> | _wingsGravity || _gravity || How much gravity affects tanks with the WG flag.<br /> |-<br /> | _wingsJumpCount || 1 || The number of jumps a tank with the wings flag can do before returning to the ground.<br /> |-<br /> | _wingsJumpVelocity || _jumpVelocity || The initial velocity of a jump with wings, in [[world units]]/sec.<br /> |-<br /> | _wingsSlideTime || 0 || When in the air, the tanks will slide for this long.<br /> |-<br /> | _worldSize || 400 || The size of the world. This should not be set during play, as the walls will not move for currently connected players. Setting this larger will allow tanks to go outside the map, and setting it smaller will cause tanks to be kicked for leaving the world boundaries.<br /> |}<br /> <br /> [[Category:Server]]</div>

Yrogirg https://wiki.bzflag.org/index.php?title=Server_Variables&diff=7133 Server Variables 2010-08-04T08:07:27Z

<p>Yrogirg: </p> <hr /> <div>The BZFlag Server (BZFS) allows administrators to configure a large number of gameplay and configuration settings from within the client. The /set command in-game allows users with the appropriate permissions to change these values. These may also be known as BZDB variables and "/set variables" depending on who you speak with.<br /> <br /> Unless otherwise noted, time values are measured in seconds, distances in [[world units]], and speeds in [[world units]] per second.<br /> <br /> {{InfoBox|Note|Some values, such as _worldSize, only take affect at server start since they affect the world file that is generated. It is recommended to apply these in the map file so they are loaded with the map.}}<br /> {|{{Prettytable}}<br /> |-<br /> |{{Hl3}}|'''Name'''<br /> |{{Hl3}}|'''Default'''<br /> |{{Hl3}}|'''Description'''<br /> |-<br /> | _agilityAdVel || 2.25 || Multiplies _tankSpeed for tanks holding Agility flag for a specified amount of time (_agilityTimeWindow)<br /> |-<br /> | _agilityTimeWindow || 1 || The amount of time (in seconds)that the tank will have the speed specified by _agilityAdVel<br /> |-<br /> | _agilityVelDelta || 0.3 || <br /> |-<br /> | _angleTolerance || 0.05 || If a tank has turned more than it was expected to, plus this tolerance, a new update is sent so the other clients are aware of the change in heading<br /> |-<br /> | _angularAd || 1.5 || Multiplies _tankAngVel to determine how fast tanks can turn while holding the Quick Turn flag<br /> |-<br /> | _avenueSize || 2*_boxBase || Space to leave between objects in random maps?<br /> |-<br /> | _baseSize || 60 || Width and Depth (bases have constant height) of the square bases for CTF games<br /> |-<br /> | _boxBase || 30 || Width and Depth of boxes on a random map?<br /> |-<br /> | _boxHeight || 6*_muzzleHeight || Height of boxes on a random map?<br /> |-<br /> | _burrowDepth || -1.32 || Determines how far down tanks drop when they have the Burrow Flag. Making this much lower makes it below the floor, and impossible to kill the tank without something like a ShockWave flag!<br /> |-<br /> | _burrowSpeedAd || .8 || Multiplied by _tankSpeed to determine how fast tanks holding the Burrow Flag move.<br /> |-<br /> | _burrowAngularAd || .55 || Multiplied by _tankAngVel to determine how fast tanks can turn while holding the Burrow flag.<br /> |-<br /> | _coldetDepth || 6 ||<br /> |-<br /> | _coldetElements || 4 || <br /> |-<br /> | _countdownResumeDelay || 5 || This enforces a delay when resuming a paused countdown. If the argument is lower or equal to 0 then resuming is instantly, otherwise it is delayed according to the value (in seconds). ''Available in 2.1 and later''<br /> |-<br /> | _cullDepth || 6 ||<br /> |-<br /> | _cullDist || fog || Far plane culling distance ('fog' uses the fog parameters).<br /> |-<br /> | _cullElements || 16 || <br /> |-<br /> | _cullOccluders || 0 ||<br /> |-<br /> | _disableBots || none || A value of 1 in this variable does not allow autopilot or bots on the server, equivalent to the old -prohibitbots command line option. <br /> |-<br /> | _drawCelestial || 1 || Draw the stars, sun, and moon.<br /> |-<br /> | _drawClouds || 1 || Draw the clouds.<br /> |-<br /> | _drawGround || 1 || Draw the ground plane.<br /> |-<br /> | _drawMountains || 1 || Draw the mountains.<br /> |-<br /> | _drawSky || 1 || Draw the sky pyramid.<br /> |-<br /> | _explodeTime || 5 || After a tank is killed, this is how long it takes to blow up, and then "respawn". Larger values translates into longer explosions and more client processor time. Note that an explosion is invisible if you are inside it, so large values may make it invisible up close, and extremely large values may make explosions entirely invisible.<br /> |-<br /> | _flagAltitude || 11 || The height that the flag flies up when dropped and the height that a flag spawns at.<br /> |-<br /> | _flagEffectTime || 0.64 || How much time it takes for the flag to go into effect.<br /> |-<br /> | _flagHeight || 10 || The height of the flag (not its pole).<br /> |-<br /> | _flagPoleWidth || 0.025 || The diameter of the flag pole.<br /> |-<br /> | _flagPoleSize || 0.8 || The height of the flag pole.<br /> |-<br /> | _flagRadius || 2.5 || Determines how close a tank must be to a flag to pick it up.<br /> |-<br /> | _fogMode || none || Valid values: linear, exp, or exp2.<br /> |-<br /> | _fogDensity || 0.001 || Used for exp and exp2 fog modes.<br /> |-<br /> | _fogStart || 0.5*_worldSize || Used for linear fog mode, the distance where fog begins to occlude vision.<br /> |-<br /> | _fogEnd || _worldSize || Used for linear fog mode, the distance where the fog occludes everything.<br /> |-<br /> | _fogColor || "0.25 0.25 0.25" || RGB or black, red, blue (alpha is ignored).<br /> |-<br /> | _friction || 0 || Zero is normal friction, the closer to 0 the harder it is to start and stop, and the higher the number the easier it is to start and stop.<br /> |-<br /> | _gmActivationTime || 0.5 || The amount of time (in seconds) it takes for a Guided Missile to become active after it is fired. Any contact under this time will not result in detonation (setting it too low could cause its owner to run into its own GM and be blown up!<br /> |-<br /> | _gmAdLife || 0.95 || Multiplied by _shotRange to determine the distance guided missiles will go.<br /> |-<br /> | _gmTurnAngle || 0.628319 || The angle at which a Guided Missile will turn to follow its target. (Measured in radians)<br /> |-<br /> | _gravity || -9.8 || The rate at which a tank will fall (or be kept from jumping) Measured in [[World units]]/Seconds^2. Setting this to a zero or positive value will result in tanks being unable to stay down and will float away.<br /> |-<br /> | _handicapScoreDiff || 50 || How much of a score difference (from the leader?) there must be for a player to get a handicap<br /> |-<br /> | _handicapVelAd || 2 || Player with handicap will receive this much more (_tankSpeed + _handicapVelAd) velocity than the normal _tankSpeed value.<br>''**Note: These could be factors rather than additions''<br /> |-<br /> | _handicapAngAd || 1.5 || Player with handicap will receive this much more (_angularAd + _handicapAngAd) turning ability than the normal _angularAd. <br>''**Note: These could be factors rather than additions''<br /> |-<br /> | _handicapShotAd || 1.75 || ''**Note: These could be factors rather than additions''<br /> |-<br /> | _identifyRange || 50 || If a flag is this distance or closer to a tank carrying the Identify (ID) flag, it will display the closest flag's type.<br /> |-<br /> | _inertiaAngular || 38 || Sets the maximum angular acceleration. Available in version 3.0. Replaces the "-a" option. <br /> |-<br /> | _inertiaLinear || 45 || Sets the maximum linear acceleration. Available in version 3.0. Replaces the "-a" option. <br /> |-<br /> | _jumpVelocity || 19 || The speed a tank moves vertically while jumping.<br /> |-<br /> | _laserAdVel || 1000 || The length of each laser shot. Lasers aren't exactly "infinite" as their description states, they go on for as long as this variable states.<br /> |-<br /> | _laserAdRate || 0.5 || Multiplied by _rFireAdRate to determine the firing rate for a laser.<br /> |-<br /> | _laserAdLife || 0.1 || The amount of time (in seconds) that a laser remains after being fired.<br /> |-<br /> | _latitude || 37.5 || The latitude at which the world exists. This affects the timezone.<br /> |-<br /> | _lgGravity|| 12.7 || Modifies the gravity for owners of the Low Gravity flag. Similar to the _gravity variable. ''Available starting in version 2.1''<br /> |-<br /> | _lockOnAngle || 0.15 || Angle (in radians) in relation to tanks heading (positive or negative) that will allow a Guided Missile to lock onto a target.<br /> |-<br /> | _longitude || 122 || The longitude at which the world exists. This affects the timezone.<br /> |-<br /> | _lRAdRate || 0.5 ||<br /> |-<br /> | _maxBumpHeight || 0.33 || Any difference between the surface a tank is on and the top surface of an object the tank runs into that is less than this value will allow the tank to simply move up to the object rather than being stopped by it.<br /> |-<br /> | _maxFlagGrabs || 4.0 || How many times a flag can be dropped before it respawns. At the first spawn, flags are assigned a random # between 1 and _maxFlagGrabs. Each grab reduces that number by 1, until zero is reached, then the flag spawns at a new location. Flags will always respawn no matter how many flag grabs they have left if dropped over an 'unsafe' zone.<br /> |-<br /> | _maxLOD || 32767 || The max level of detail to allow.<br /> |-<br /> | _mirror || none || Options: '''white''', '''black''', '''red''', '''blue''', '''pink''', '''purple''', '''orange''', etc... ("black 0.75" is a good setting, some invalid options such as '''mirror''' will give a mirror look)<br /> |-<br /> | _momentumLinAcc || 1 || Momentum flag's effect on going forwards and backwards.<br /> |-<br /> | _momentumAngAcc || 1 || Momentum flag's effect on turning.<br /> |-<br /> | _momentumFriction || 0 || Friction (same as _friction) when holding the Momentum flag.<br /> |-<br /> | _mGunAdVel || 1/_mGunAdRate || The speed of the machine gun's bullets.<br /> |-<br /> | _mGunAdRate || 10 || _reloadTime divided by _mGunAdRate gives how long machine gun bullets take to reload.<br /> |-<br /> | _mGunAdLife || 1.5 || Multiplied by _shotRange to determine the distance machine gun bullets go.<br /> |-<br /> | _muzzleFront || _tankRadius + 0.1 || Location of muzzle of tank (affects bullets and player camera location).<br /> |-<br /> | _muzzleHeight || 1.57 || See _muzzleFront.<br /> |-<br /> | _noClimb || 1 || Allow or disallow climbing on sloped surfaces. A value of 0 allows, 1 disallows.<br /> |-<br /> | _noShadows || 0 || Enables or disables shadows. A value of 0 allows, 1 disallows.<br /> |-<br /> | _noSmallPackets || 0 ||<br /> |-<br /> | _notRespondingTime || 5 || The amount of time (in seconds) the server should wait before reporting a tank as not responding.<br /> |-<br /> | _obeseFactor || 2.5 || Multiplier of normal size that determines how big a tank gets when carrying the Obese flag.<br /> |-<br /> | _pauseDropTime || 15 || The amount of time (in seconds) that a tank needs to be paused before its flag is dropped automatically.<br /> |-<br /> | _positionTolerance || 0.09 || <br /> |-<br /> | _pyrBase || 4 * _tankHeight || Base size of pyramids generated by the default random map generator.<br /> |-<br /> | _pyrHeight || 5 * _tankHeight || Height of pyramids generated by the default random map generator.<br /> |-<br /> | _radarLimit || _worldSize || The maximum area that the radar can see (when not rotated).<br /> |-<br /> | _rainBaseColor || none || When _rainType = rain, sets color of the bottom of raindrops.<br /> |-<br /> | _rainDensity || none || Determines how many drops of rain are in the space defined by _rainSpread.<br /> |-<br /> | _rainEndZ || none || The height above the ground where rain should stop falling.<br /> |-<br /> | _rainMaxPuddleTime || none || The amount of time (in seconds) a rain puddle should exist before disappearing.<br /> |-<br /> | _rainPuddleSpeed || none || The speed at which puddles should spread out.<br /> |-<br /> | _rainPuddleColor || none || Color of rain puddles. none means no puddle.<br /> |-<br /> | _rainPuddleTexture ||none || Texture of puddles. Best to leave default.<br /> |-<br /> | _rainRoofs || 1 || '''0''' rain falls through everything<br>'''1''' rain hits buildings, but puddles are only on the ground<br>'''2''' rain hits buildings, and creates puddles on them<br /> |-<br /> | _rainSpread || none || The radius from center of map where rain will fall.<br /> |-<br /> | _rainSpeed || none || The speed at which the rain falls.<br /> |-<br /> | _rainSpeedMod || none || Randomizes _rainSpeed by adding/subtracting up to this number from each raindrop's speed<br /> |-<br /> | _rainSpins || none || '''0''' Rain does not spin as it falls<br>'''1''' Rain spins as it falls.<br /> |-<br /> | _rainStartZ || none || The height above ground that rain should fall from.<br /> |-<br /> | _rainTexture || none || The name of the texture in data directory.<br>''Works with _rainTypes of frog, particle, bubble, snow, fatrain''<br /> |-<br /> | _rainTopColor ||none || When _rainType = rain, sets color of the top of raindrops.<br /> |-<br /> | _rainType || none || Adjusts all _rain* and _use* variables automatically<br>Valid Options : '''frog''', '''particle''', '''rain''', '''bubble''', '''snow''', '''fatrain'''<br /> |-<br /> | _rejoinTime || _explodeTime || The number of seconds before clients can rejoin a game, after they leave.<br /> |-<br /> | _rejumpTime || 0.01 || From version 3.0. Time a tank has to wait before he can jump again after landing. Any value higher than 0 will make it difficult to jump away from sloped faces like pyramids.<br /> |-<br /> | _reloadTime || _shotRange/_shotSpeed || Time between shot reloads, note that this can cut shot range short.<br /> |-<br /> | _rFireAdVel || 1.5 || Multiplied by _shotSpeed to determine the speed of the rapid fire bullets.<br /> |-<br /> | _rFireAdRate || 2 || The reload time (in seconds) for rapid fire bullets.<br /> |-<br /> | _rFireAdLife || 1/_rFireAdRate || How long the rapid fire bullets last.<br /> |-<br /> | _shieldFlight || 2.7 || The amount of time (in seconds) that a shield flag floats in the air (after you drop it) before coming down again.<br /> |-<br /> | _shockAdLife || 0.2 || The amount of time (in seconds) that a shockwave lasts.<br /> |-<br /> | _shockInRadius || _tankLength || The starting radius of the shockwave. Negative values will make the shockwave shrink and expand.<br /> |-<br /> | _shockOutRadius || 60 || The outer radius of the shockwave. If greater than _shockInRadius, the shockwave expands outward. If less than _shockInRadius, the shockwave starts big and shrinks inward.<br /> |-<br /> | _shotRadius || 0.5 || For collision detection.<br /> |-<br /> | _shotRange || 350 || Range of shots, note that they can be cut short by _reloadTime.<br /> |-<br /> | _shotSpeed || 100 || Speed of shots.<br /> |-<br /> | _shotTailLength || 4 || <br /> |-<br /> | _shotsKeepVerticalVelocity || 0 || If '''0''', shots always move straight in relation to the ground. If '''1''', shots are affected vertically by the tank's speed, and can fly up and down. Lasers are also affected. <br /> |-<br /> | _skyColor || white || Sets the sky to a specific color.<br /> |-<br /> | _srRadiusMult || 2 || Radius of steamroller effect.<br /> |-<br /> | _squishFactor || 1 || How much tanks squish when landing.<br /> |-<br /> | _squishTime || 1 || How much squishy time you get after falling to the ground.<br /> |-<br /> | _syncTime || 1 || Whether or not to sync the players time with the servers'.<br /> |-<br /> | _syncLocation || 0 || Whether or not to sync the location time with the servers'.<br /> |-<br /> | _tankAngVel || 0.785398 || How fast the tank can turn.<br /> |-<br /> | _tankExplosionSize || 3.5 * _tankLength || How large the tank's explosion is.<br /> |-<br /> | _tankHeight || 2.05 || The height of the tank.<br /> |-<br /> | _tankLength || 6 || The length of the tank.<br /> |-<br /> | _tankRadius || 0.72 * _tankLength || The radius of the tank.<br /> |-<br /> | _tankSpeed || 25 || The speed of the tank<br /> |-<br /> | _tankWidth || 2.8 || The width of the tank.<br /> |-<br /> | _targetingAngle || 0.3|| Something to do with GM... <br /> |-<br /> | _teleportBreadth || 4.48|| Random maps?<br /> |-<br /> | _teleportHeight || 10.08 || See _teleportBreadth.<br /> |-<br /> | _teleportTime || 1 ||<br /> |-<br /> | _teleportWidth || 1.12 || See _teleportHeight.<br /> |-<br /> | _thiefAdLife || 0.05 || The amount of time (in seconds) that a thief shot lasts.<br /> |-<br /> | _thiefAdRate || 12 || The amount of time (in seconds) that the Thief "shot" reloads.<br /> |-<br /> | _thiefAdShotVel || 8 || The speed of thief.<br /> |-<br /> | _thiefTinyFactor || 0.5|| Multiplied by the normal tank size to shrink a tank carrying the thief flag.<br /> |-<br /> | _thiefVelAd || 1.67 || Multiplied by _tankSpeed to determine how fast tanks holding the thief goes.<br /> |-<br /> | _thiefDropTime || reloadTime * 0.5 ||The amount of time you must wait to fire a shot after stealing a flag.<br /> |-<br /> | _tinyFactor || 0.4 || Multiplied by the normal tank size to shrink a tank carrying the tiny flag.<br /> |-<br /> | _trackFade || 3 || The amount of time (in seconds) before track marks fade.<br /> |-<br /> | _updateThrottleRate || 30 ||<br /> |-<br /> | _useLineRain || none || '''0''' Rain is not a vertical line<br>'''1''' Rain is vertical lines, smoothly shaded from _rainTopColor to _rainBaseColor<br /> |-<br /> | _useRainPuddles || none || '''0''' Rain does not create puddles<br>'''1''' Rain creates puddles<br /> |-<br /> | _useRainBillboards || none || '''0''' Rain is lines or polygons<br>'''1''' Rain is billboards, textured and look the same from all angles<br /> |-<br /> | _velocityAd || 1.5 || Multiplies _tankSpeed to determine the speed of a tank carrying the high speed (V) flag<br /> |-<br /> | _wallHeight || 3 * _tankHeight|| The outer wall height.<br /> |-<br /> | _weapons || 1 || Used with world weapons, '''0''' world weapons will not fire<br>'''1''' world weapons will fire<br /> |-<br /> | _wideAngleAng || 1.745329 || The viewing angle when a tank has the Wide Angle bad flag.<br /> |-<br /> | _wingsGravity || _gravity || How much gravity affects tanks with the WG flag.<br /> |-<br /> | _wingsJumpCount || 1 || The number of jumps a tank with the wings flag can do before returning to the ground.<br /> |-<br /> | _wingsJumpVelocity || _jumpVelocity || The initial velocity of a jump with wings, in [[world units]]/sec.<br /> |-<br /> | _wingsSlideTime || 0 || When in the air, the tanks will slide for this long.<br /> |-<br /> | _worldSize || 400 || The size of the world. This should not be set during play, as the walls will not move for currently connected players. Setting this larger will allow tanks to go outside the map, and setting it smaller will cause tanks to be kicked for leaving the world boundaries.<br /> |}<br /> <br /> [[Category:Server]]</div>

Yrogirg https://wiki.bzflag.org/index.php?title=Server_Variables&diff=7131 Server Variables 2010-07-28T05:48:12Z

<p>Yrogirg: guess that's right</p> <hr /> <div>The BZFlag Server (BZFS) allows administrators to configure a large number of gameplay and configuration settings from within the client. The /set command in-game allows users with the appropriate permissions to change these values. These may also be known as BZDB variables and "/set variables" depending on who you speak with.<br /> <br /> Unless otherwise noted, time values are measured in seconds, distances in [[world units]], and speeds in [[world units]] per second.<br /> <br /> {{InfoBox|Note|Some values, such as _worldSize, only take affect at server start since they affect the world file that is generated. It is recommended to apply these in the map file so they are loaded with the map.}}<br /> {|{{Prettytable}}<br /> |-<br /> |{{Hl3}}|'''Name'''<br /> |{{Hl3}}|'''Default'''<br /> |{{Hl3}}|'''Description'''<br /> |-<br /> | _agilityAdVel || 2.25 || Multiplies _tankSpeed for tanks holding Agility flag for a specified amount of time (_agilityTimeWindow)<br /> |-<br /> | _agilityTimeWindow || 1 || The amount of time (in seconds)that the tank will have the speed specified by _agilityAdVel<br /> |-<br /> | _agilityVelDelta || 0.3 || <br /> |-<br /> | _angleTolerance || 0.05 || If a tank has turned more than it was expected to, plus this tolerance, a new update is sent so the other clients are aware of the change in heading<br /> |-<br /> | _angularAd || 1.5 || Multiplies _tankAngVel to determine how fast tanks can turn while holding the Quick Turn flag<br /> |-<br /> | _avenueSize || 2*_boxBase || Space to leave between objects in random maps?<br /> |-<br /> | _baseSize || 60 || Width and Depth (bases have constant height) of the square bases for CTF games<br /> |-<br /> | _boxBase || 30 || Width and Depth of boxes on a random map?<br /> |-<br /> | _boxHeight || 6*_muzzleHeight || Height of boxes on a random map?<br /> |-<br /> | _burrowDepth || -1.32 || Determines how far down tanks drop when they have the Burrow Flag. Making this much lower makes it below the floor, and impossible to kill the tank without something like a ShockWave flag!<br /> |-<br /> | _burrowSpeedAd || .8 || Multiplied by _tankSpeed to determine how fast tanks holding the Burrow Flag move.<br /> |-<br /> | _burrowAngularAd || .55 || Multiplied by _tankAngVel to determine how fast tanks can turn while holding the Burrow flag.<br /> |-<br /> | _coldetDepth || 6 ||<br /> |-<br /> | _coldetElements || 4 || <br /> |-<br /> | _countdownResumeTime || 5 || This enforces a delay when resuming a paused countdown. If the argument is lower or equal to 0 then resuming is instantly, otherwise it is delayed according to the value (in seconds). ''Available in 2.1 and later''<br /> |-<br /> | _cullDepth || 6 ||<br /> |-<br /> | _cullDist || fog || Far plane culling distance ('fog' uses the fog parameters).<br /> |-<br /> | _cullElements || 16 || <br /> |-<br /> | _cullOccluders || 0 ||<br /> |-<br /> | _disableBots || none || A value of 1 in this variable does not allow autopilot or bots on the server, equivalent to the old -prohibitbots command line option. <br /> |-<br /> | _drawCelestial || 1 || Draw the stars, sun, and moon.<br /> |-<br /> | _drawClouds || 1 || Draw the clouds.<br /> |-<br /> | _drawGround || 1 || Draw the ground plane.<br /> |-<br /> | _drawMountains || 1 || Draw the mountains.<br /> |-<br /> | _drawSky || 1 || Draw the sky pyramid.<br /> |-<br /> | _explodeTime || 5 || After a tank is killed, this is how long it takes to blow up, and then "respawn". Larger values translates into longer explosions and more client processor time. Note that an explosion is invisible if you are inside it, so large values may make it invisible up close, and extremely large values may make explosions entirely invisible.<br /> |-<br /> | _flagAltitude || 11 || The height that the flag flies up when dropped and the height that a flag spawns at.<br /> |-<br /> | _flagEffectTime || 0.64 || How much time it takes for the flag to go into effect.<br /> |-<br /> | _flagHeight || 10 || The height of the flag (not its pole).<br /> |-<br /> | _flagPoleWidth || 0.025 || The diameter of the flag pole.<br /> |-<br /> | _flagPoleSize || 0.8 || The height of the flag pole.<br /> |-<br /> | _flagRadius || 2.5 || Determines how close a tank must be to a flag to pick it up.<br /> |-<br /> | _fogMode || none || Valid values: linear, exp, or exp2.<br /> |-<br /> | _fogDensity || 0.001 || Used for exp and exp2 fog modes.<br /> |-<br /> | _fogStart || 0.5*_worldSize || Used for linear fog mode, the distance where fog begins to occlude vision.<br /> |-<br /> | _fogEnd || _worldSize || Used for linear fog mode, the distance where the fog occludes everything.<br /> |-<br /> | _fogColor || "0.25 0.25 0.25" || RGB or black, red, blue (alpha is ignored).<br /> |-<br /> | _friction || 0 || Zero is normal friction, the closer to 0 the harder it is to start and stop, and the higher the number the easier it is to start and stop.<br /> |-<br /> | _gmActivationTime || 0.5 || The amount of time (in seconds) it takes for a Guided Missile to become active after it is fired. Any contact under this time will not result in detonation (setting it too low could cause its owner to run into its own GM and be blown up!<br /> |-<br /> | _gmAdLife || 0.95 || Multiplied by _shotRange to determine the distance guided missiles will go.<br /> |-<br /> | _gmTurnAngle || 0.628319 || The angle at which a Guided Missile will turn to follow its target. (Measured in radians)<br /> |-<br /> | _gravity || -9.8 || The rate at which a tank will fall (or be kept from jumping) Measured in [[World units]]/Seconds^2. Setting this to a zero or positive value will result in tanks being unable to stay down and will float away.<br /> |-<br /> | _handicapScoreDiff || 50 || How much of a score difference (from the leader?) there must be for a player to get a handicap<br /> |-<br /> | _handicapVelAd || 2 || Player with handicap will receive this much more (_tankSpeed + _handicapVelAd) velocity than the normal _tankSpeed value.<br>''**Note: These could be factors rather than additions''<br /> |-<br /> | _handicapAngAd || 1.5 || Player with handicap will receive this much more (_angularAd + _handicapAngAd) turning ability than the normal _angularAd. <br>''**Note: These could be factors rather than additions''<br /> |-<br /> | _handicapShotAd || 1.75 || ''**Note: These could be factors rather than additions''<br /> |-<br /> | _identifyRange || 50 || If a flag is this distance or closer to a tank carrying the Identify (ID) flag, it will display the closest flag's type.<br /> |-<br /> | _inertiaAngular || 38 || Sets the maximum angular acceleration. Available in version 3.0. Replaces the "-a" option. <br /> |-<br /> | _inertiaLinear || 45 || Sets the maximum linear acceleration. Available in version 3.0. Replaces the "-a" option. <br /> |-<br /> | _jumpVelocity || 19 || The speed a tank moves vertically while jumping.<br /> |-<br /> | _laserAdVel || 1000 || The length of each laser shot. Lasers aren't exactly "infinite" as their description states, they go on for as long as this variable states.<br /> |-<br /> | _laserAdRate || 0.5 || Multiplied by _rFireAdRate to determine the firing rate for a laser.<br /> |-<br /> | _laserAdLife || 0.1 || The amount of time (in seconds) that a laser remains after being fired.<br /> |-<br /> | _latitude || 37.5 || The latitude at which the world exists. This affects the timezone.<br /> |-<br /> | _lgGravity|| 12.7 || Modifies the gravity for owners of the Low Gravity flag. Similar to the _gravity variable. ''Available starting in version 2.1''<br /> |-<br /> | _lockOnAngle || 0.15 || Angle (in radians) in relation to tanks heading (positive or negative) that will allow a Guided Missile to lock onto a target.<br /> |-<br /> | _longitude || 122 || The longitude at which the world exists. This affects the timezone.<br /> |-<br /> | _lRAdRate || 0.5 ||<br /> |-<br /> | _maxBumpHeight || 0.33 || Any difference between the surface a tank is on and the top surface of an object the tank runs into that is less than this value will allow the tank to simply move up to the object rather than being stopped by it.<br /> |-<br /> | _maxFlagGrabs || 4.0 || How many times a flag can be dropped before it respawns. At the first spawn, flags are assigned a random # between 1 and _maxFlagGrabs. Each grab reduces that number by 1, until zero is reached, then the flag spawns at a new location. Flags will always respawn no matter how many flag grabs they have left if dropped over an 'unsafe' zone.<br /> |-<br /> | _maxLOD || 32767 || The max level of detail to allow.<br /> |-<br /> | _mirror || none || Options: '''white''', '''black''', '''red''', '''blue''', '''pink''', '''purple''', '''orange''', etc... ("black 0.75" is a good setting, some invalid options such as '''mirror''' will give a mirror look)<br /> |-<br /> | _momentumLinAcc || 1 || Momentum flag's effect on going forwards and backwards.<br /> |-<br /> | _momentumAngAcc || 1 || Momentum flag's effect on turning.<br /> |-<br /> | _momentumFriction || 0 || Friction (same as _friction) when holding the Momentum flag.<br /> |-<br /> | _mGunAdVel || 1/_mGunAdRate || The speed of the machine gun's bullets.<br /> |-<br /> | _mGunAdRate || 10 || _reloadTime divided by _mGunAdRate gives how long machine gun bullets take to reload.<br /> |-<br /> | _mGunAdLife || 1.5 || Multiplied by _shotRange to determine the distance machine gun bullets go.<br /> |-<br /> | _muzzleFront || _tankRadius + 0.1 || Location of muzzle of tank (affects bullets and player camera location).<br /> |-<br /> | _muzzleHeight || 1.57 || See _muzzleFront.<br /> |-<br /> | _noClimb || 1 || Allow or disallow climbing on sloped surfaces. A value of 0 allows, 1 disallows.<br /> |-<br /> | _noShadows || 0 || Enables or disables shadows. A value of 0 allows, 1 disallows.<br /> |-<br /> | _noSmallPackets || 0 ||<br /> |-<br /> | _notRespondingTime || 5 || The amount of time (in seconds) the server should wait before reporting a tank as not responding.<br /> |-<br /> | _obeseFactor || 2.5 || Multiplier of normal size that determines how big a tank gets when carrying the Obese flag.<br /> |-<br /> | _pauseDropTime || 15 || The amount of time (in seconds) that a tank needs to be paused before its flag is dropped automatically.<br /> |-<br /> | _positionTolerance || 0.09 || <br /> |-<br /> | _pyrBase || 4 * _tankHeight || Base size of pyramids generated by the default random map generator.<br /> |-<br /> | _pyrHeight || 5 * _tankHeight || Height of pyramids generated by the default random map generator.<br /> |-<br /> | _radarLimit || _worldSize || The maximum area that the radar can see (when not rotated).<br /> |-<br /> | _rainBaseColor || none || When _rainType = rain, sets color of the bottom of raindrops.<br /> |-<br /> | _rainDensity || none || Determines how many drops of rain are in the space defined by _rainSpread.<br /> |-<br /> | _rainEndZ || none || The height above the ground where rain should stop falling.<br /> |-<br /> | _rainMaxPuddleTime || none || The amount of time (in seconds) a rain puddle should exist before disappearing.<br /> |-<br /> | _rainPuddleSpeed || none || The speed at which puddles should spread out.<br /> |-<br /> | _rainPuddleColor || none || Color of rain puddles. none means no puddle.<br /> |-<br /> | _rainPuddleTexture ||none || Texture of puddles. Best to leave default.<br /> |-<br /> | _rainRoofs || 1 || '''0''' rain falls through everything<br>'''1''' rain hits buildings, but puddles are only on the ground<br>'''2''' rain hits buildings, and creates puddles on them<br /> |-<br /> | _rainSpread || none || The radius from center of map where rain will fall.<br /> |-<br /> | _rainSpeed || none || The speed at which the rain falls.<br /> |-<br /> | _rainSpeedMod || none || Randomizes _rainSpeed by adding/subtracting up to this number from each raindrop's speed<br /> |-<br /> | _rainSpins || none || '''0''' Rain does not spin as it falls<br>'''1''' Rain spins as it falls.<br /> |-<br /> | _rainStartZ || none || The height above ground that rain should fall from.<br /> |-<br /> | _rainTexture || none || The name of the texture in data directory.<br>''Works with _rainTypes of frog, particle, bubble, snow, fatrain''<br /> |-<br /> | _rainTopColor ||none || When _rainType = rain, sets color of the top of raindrops.<br /> |-<br /> | _rainType || none || Adjusts all _rain* and _use* variables automatically<br>Valid Options : '''frog''', '''particle''', '''rain''', '''bubble''', '''snow''', '''fatrain'''<br /> |-<br /> | _rejoinTime || _explodeTime || The number of seconds before clients can rejoin a game, after they leave.<br /> |-<br /> | _rejumpTime || 0.01 || From version 3.0. Time a tank has to wait before he can jump again after landing. Any value higher than 0 will make it difficult to jump away from sloped faces like pyramids.<br /> |-<br /> | _reloadTime || _shotRange/_shotSpeed || Time between shot reloads, note that this can cut shot range short.<br /> |-<br /> | _rFireAdVel || 1.5 || Multiplied by _shotSpeed to determine the speed of the rapid fire bullets.<br /> |-<br /> | _rFireAdRate || 2 || The reload time (in seconds) for rapid fire bullets.<br /> |-<br /> | _rFireAdLife || 1/_rFireAdRate || How long the rapid fire bullets last.<br /> |-<br /> | _shieldFlight || 2.7 || The amount of time (in seconds) that a shield flag floats in the air (after you drop it) before coming down again.<br /> |-<br /> | _shockAdLife || 0.2 || The amount of time (in seconds) that a shockwave lasts.<br /> |-<br /> | _shockInRadius || _tankLength || The starting radius of the shockwave. Negative values will make the shockwave shrink and expand.<br /> |-<br /> | _shockOutRadius || 60 || The outer radius of the shockwave. If greater than _shockInRadius, the shockwave expands outward. If less than _shockInRadius, the shockwave starts big and shrinks inward.<br /> |-<br /> | _shotRadius || 0.5 || For collision detection.<br /> |-<br /> | _shotRange || 350 || Range of shots, note that they can be cut short by _reloadTime.<br /> |-<br /> | _shotSpeed || 100 || Speed of shots.<br /> |-<br /> | _shotTailLength || 4 || <br /> |-<br /> | _shotsKeepVerticalVelocity || 0 || If '''0''', shots always move straight in relation to the ground. If '''1''', shots are affected vertically by the tank's speed, and can fly up and down. Lasers are also affected. <br /> |-<br /> | _skyColor || white || Sets the sky to a specific color.<br /> |-<br /> | _srRadiusMult || 2 || Radius of steamroller effect.<br /> |-<br /> | _squishFactor || 1 || How much tanks squish when landing.<br /> |-<br /> | _squishTime || 1 || How much squishy time you get after falling to the ground.<br /> |-<br /> | _syncTime || 1 || Whether or not to sync the players time with the servers'.<br /> |-<br /> | _syncLocation || 0 || Whether or not to sync the location time with the servers'.<br /> |-<br /> | _tankAngVel || 0.785398 || How fast the tank can turn.<br /> |-<br /> | _tankExplosionSize || 3.5 * _tankLength || How large the tank's explosion is.<br /> |-<br /> | _tankHeight || 2.05 || The height of the tank.<br /> |-<br /> | _tankLength || 6 || The length of the tank.<br /> |-<br /> | _tankRadius || 0.72 * _tankLength || The radius of the tank.<br /> |-<br /> | _tankSpeed || 25 || The speed of the tank<br /> |-<br /> | _tankWidth || 2.8 || The width of the tank.<br /> |-<br /> | _targetingAngle || 0.3|| Something to do with GM... <br /> |-<br /> | _teleportBreadth || 4.48|| Random maps?<br /> |-<br /> | _teleportHeight || 10.08 || See _teleportBreadth.<br /> |-<br /> | _teleportTime || 1 ||<br /> |-<br /> | _teleportWidth || 1.12 || See _teleportHeight.<br /> |-<br /> | _thiefAdLife || 0.05 || The amount of time (in seconds) that a thief shot lasts.<br /> |-<br /> | _thiefAdRate || 12 || The amount of time (in seconds) that the Thief "shot" reloads.<br /> |-<br /> | _thiefAdShotVel || 8 || The speed of thief.<br /> |-<br /> | _thiefTinyFactor || 0.5|| Multiplied by the normal tank size to shrink a tank carrying the thief flag.<br /> |-<br /> | _thiefVelAd || 1.67 || Multiplied by _tankSpeed to determine how fast tanks holding the thief goes.<br /> |-<br /> | _thiefDropTime || reloadTime * 0.5 ||The amount of time you must wait to fire a shot after stealing a flag.<br /> |-<br /> | _tinyFactor || 0.4 || Multiplied by the normal tank size to shrink a tank carrying the tiny flag.<br /> |-<br /> | _trackFade || 3 || The amount of time (in seconds) before track marks fade.<br /> |-<br /> | _updateThrottleRate || 30 ||<br /> |-<br /> | _useLineRain || none || '''0''' Rain is not a vertical line<br>'''1''' Rain is vertical lines, smoothly shaded from _rainTopColor to _rainBaseColor<br /> |-<br /> | _useRainPuddles || none || '''0''' Rain does not create puddles<br>'''1''' Rain creates puddles<br /> |-<br /> | _useRainBillboards || none || '''0''' Rain is lines or polygons<br>'''1''' Rain is billboards, textured and look the same from all angles<br /> |-<br /> | _velocityAd || 1.5 || Multiplies _tankSpeed to determine the speed of a tank carrying the high speed (V) flag<br /> |-<br /> | _wallHeight || 3 * _tankHeight|| The outer wall height.<br /> |-<br /> | _weapons || 1 || Used with world weapons, '''0''' world weapons will not fire<br>'''1''' world weapons will fire<br /> |-<br /> | _wideAngleAng || 1.745329 || The viewing angle when a tank has the Wide Angle bad flag.<br /> |-<br /> | _wingsGravity || _gravity || How much gravity affects tanks with the WG flag.<br /> |-<br /> | _wingsJumpCount || 1 || The number of jumps a tank with the wings flag can do before returning to the ground.<br /> |-<br /> | _wingsJumpVelocity || _jumpVelocity || The initial velocity of a jump with wings, in [[world units]]/sec.<br /> |-<br /> | _wingsSlideTime || 0 || When in the air, the tanks will slide for this long.<br /> |-<br /> | _worldSize || 400 || The size of the world. This should not be set during play, as the walls will not move for currently connected players. Setting this larger will allow tanks to go outside the map, and setting it smaller will cause tanks to be kicked for leaving the world boundaries.<br /> |}<br /> <br /> [[Category:Server]]</div>

Yrogirg https://wiki.bzflag.org/index.php?title=Map_making_by_hand&diff=7099 Map making by hand 2010-07-06T11:06:18Z

<p>Yrogirg: /* Text Editors */</p> <hr /> <div>{{DoDoc|Major re-organization, transform away from "chat" style. Need to reference pages elsewhere on the wiki in place of much of the content which appears to be building up here. Create them if necessary, or see the list [[Special:Allpages|here]].}}<br /> Although there are a number of GUI options for creating maps such as BZ-Edit, 3D modelers, many map-makers use a basic text-editor. There are many times when it is necessary to make small changes to a map, such as including objects that are unavailable in GUI map-maker, but there are also some who enjoy the challenge of creating a map entirely from scratch with a text-editor.<br /> <br /> ==Text Editors==<br /> Most text-editors designed for coding/programming are more than sufficient for editing bzw files. Although word-processing programs such as Microsoft Word can be used, there are many cheaper (free) and more efficient programs designed specifically for coding. If you are interested in syntax highlighting, look at the [http://my.bzflag.org/bb/viewtopic.php?f=24&t=16037&p=148953 forum topic].<br /> ===Windows===<br /> *Notepad<br /> *PSPad<br /> *NoteTab<br /> ===Mac===<br /> *TextWrangler<br /> *TextEdit<br /> ===Linux===<br /> *Command-line editors such as nano, emacs, pico, vim, or ed.<br /> *GEdit<br /> *Kate<br /> <br /> ==Editing existing maps==<br /> Beginning mapmakers should spend some time studying and making small changes in existing maps to see how things work. In the client, maps can be saved for editing by joining the desired server and choosing: Options>Save World. Maps can also be saved by issuing the /saveworld command. The map should be a simple map when getting started. One may find it easier to create a file in BZEdit and open the resulting file in the text-editor.<br /> <br /> ==Getting Started==<br /> If you have created a box in BZEdit you may see:<br /> {|<br /> |<br /> # World built with bzedit32 world class, available at<br /> # http://www.sourceforge.net/projects/bzflag<br /> world <br /> size 400 <br /> end <br /> options <br /> +r <br /> -j <br /> -set _tankSpeed 25 <br /> -ms 5 <br /> -mp 0,2,0,2,0,2 <br /> end <br /> box <br /> name box1 <br /> position 0 0 0 <br /> size 10 10 10 <br /> rotation 0 <br /> end <br /> |}<br /> <br /> ===What that means===<br /> "There are set variables that define various things such as how fast your tank is, how fast the bullets are, or if it's raining or foggy. Put those in the options setting with "-set(space) " in front of it. You can also make those changes as an admin by using /set _variable (notice there is a space between the set and the _). A full list of these settings can be found on the [[Server Variables]] page. Other options, such as how many times a flag can be grabbed before it resets or if flags can land on buildings are explained [http://my.bzflag.org/bb/files/antigrav4teamconf_114.txt in this forum post]<br /> Optionally, the variables can be placed in a separate configuration file and referenced when the server is started."<br /> '''old'''<br /> <br /> <br /> First, it says:<br /> # World built with bzedit32 world class, available at<br /> # http://www.sourceforge.net/projects/bzflag<br /> (Note: the # sign is used for comments.)<br /> <br /> This is the text added by the application initially, kind of like advertising. This will be the first thing anyone sees when they look at the map.<br /> <br /> The next thing is:<br /> <pre><br /> world <br /> size 400 # Sets the world size to 400 (800 x 800 total)<br /> end <br /> </pre><br /> This is rather self-explanatory. It's the <size> of the <world>.<br /> <br /> Next is:<br /> <pre><br /> options <br /> +r # Enable Ricochet<br /> -j # Enable Jumping<br /> -set _tankSpeed 25 # Sets the tank speed to 25 bzunits/second<br /> -ms 5 # Sets the maximum shots (per tank) to 5<br /> -mp 0,2,0,2,0,2 # Maximum of 2 Red Players, 2 Blue Players, and 2 Observers<br /> end <br /> </pre><br /> This is the <options>.<br /> The commands listed here are:<br /> Ricochet, Jumping, Tank speed, Max Shots, and Max Players.<br /> These are rather self explanatory, except for Max Players. It works like this. Rouge, Red, Green, Blue, Purple, Observer. Each number defines the max number of players per category.<br /> <br /> For more, see [[Options_(object)|Options Object]].<br /> <br /> We now come to:<br /> <pre><br /> box <br /> name box1 # Generally unused<br /> position 0 0 0 # X Y Z Position<br /> size 10 10 10 # X Y Z Size (bzunits from the position of the box)<br /> rotation 0 # Rotation (in degrees)<br /> end <br /> </pre><br /> This is a <box> with a <name> of <box1>.<br /> The <position> is 0,0,0 in R3[http://en.wikipedia.org/wiki/R3].<br /> The rest is pretty self explanatory.<br /> <br /> '''Important:''' EVERY STATEMENT MUST HAVE AN END.<br /> <br /> ===Basic Definitions===<br /> ;Objects<br /> :Objects are the basic building blocks of the bzw file. Objects begin with a line declaring the object, some fields describing that object, and a line that closes the object (usually with "end"). Each of these sections of the object is important.<br /> ;Comments<br /> :BZFS ignores anything in a line following the #; the line has been "commented out." It is highly recommended that comments be used often, both for the mapmaker and for others that may see the map.<br /> ;3D Cartesian Coordinate System<br /> :In most objects, you will see three numbers after position and size. These numbers are coordinates on a graph. The first number is the x coordinate (left and right) the middle number is the y coordinate (forward and backward) and the third number is the z coordinate (height and depth). Another way of thinking of it is: x = width, y = depth, z = height. (Those accustomed to the Y axis determining height will have to slightly adjust their thinking.) <br /> <br /> ==Sample Objects==<br /> ===The Box===<br /> Perhaps the simplest object is the box. There is actually nothing special you can do to it (but in versions of BZFlag from 2.0.8 up, you can do a lot more to it). Here is an example of a box:<br /> <br /> box<br /> name box1 # Optional, but good to include<br /> position 0 0 0<br /> size 10 10 10<br /> rotation 0<br /> end<br /> <br /> In the first line, notice the word "box". It simply says the next object is a box. The next line is the name of the object. It is defined with the syntax "<tt>name ''objectName''</tt>". It is not required, but is good to include. The third line defines the position of the center of the bottom of the object. The three arguments of <tt>position</tt> are the x, y, and z coordinates of the box, respectively. The x and y coordinates can be positive or negative, but the z coordinate should just be positive or zero. On the fourth line, the size of the box is defined. The arguments of <tt>size</tt> are the x, y, and z sizes of the object, respectively. The x and y arguments make the box that wide on both sides of it's position. However, the z argument makes the object exactly the number of units tall as defined. The next line just says how much the object is rotated. This number is the number of degrees of rotation, and can be negative or positive. The last line just tells BZFlag the object is done, and a new one can be defined. Be sure to '''always''' use this.<br /> <br /> ===The Cone===<br /> Most objects have similar parameters as the basic box. For instance, the code for a cone may look something like this:<br /> <br /> cone<br /> name cone1<br /> position 0 0 0<br /> size 10 10 20<br /> divisions 128<br /> end<br /> <br /> Divisions basically decide how smooth the cone is. The higher the divisions the more smooth the cone is. A division of 4 would look like a pyramid. Another parameter that can be added to the cone object is angle. If you say angle 180, that would make 1/2 of a cone, 90 would make 1/4 of a cone, and so on. <br /> <br /> ===The Arc===<br /> <br /> An arc is basically a cylinder. However it doesn’t have to be a perfect cylinder depending on certain options you select. For an arc the only required options are divisions, position and size. Just like the cone divisions have the same effect, position and size are all the same. Once again you can have an oval shaped cylinder type thing. Now, you WILL find more options to an arc than to a cone, for example the ratio option. The ratio options let you basically put a hole in the cylinder. So if you have the option: ratio 1 you would have a full cylinder. If you say for example ratio .3 or any number less than 1 you will get a whole in the cylinder. The bigger the number, the smaller the hole. Angle allows you to do a simi-circle. Rotation once again isn't really needed. all the options like spin and shear are the same for this object too! phydrv and matref I’ll show later. Let’s move to the sphere <br /> <br /> ===The Sphere===<br /> <br /> The only options required to make a sphere are position, size, and divisions. <br /> All these options do the same thing as they did in the objects above. You may also have an oval like sphere. You make an oval like sphere simply by making the x and y's different sizes just like in the cone and arc. The radius option is just a substitute for size. You can write size 10 10 10 or radius 10. Both do the same thing. However if you want an oval shaped sphere you have to use size. Rotation wouldn't really have an effect and the shear and spin works the same for this object.<br /> <br /> ==Getting more help==<br /> *The links at the bottom of the [[:Category:Map Making|Map Making]] page.<br /> *The original creator of this page is flight, you can email him at dirtbikerdude_91@yahoo.com and he will be happy to answer any questions that he is capable of answering.<br /> <br /> ==Special Objects==<br /> There are certain objects that are often coded by hand because it is simpler or it is impossible to do with graphical map creation tools. <br /> <br /> ===Materials ===<br /> Example:<br /> <br /> material <br /> name mat1 <br /> addtexture blue_bolt.png <br /> end <br /> meshbox <br /> position 0 0 0 <br /> size 10 10 10 <br /> rotation 0 <br /> matref mat1 <br /> end <br /> <br /> Material is letting the computer know that a material is about to be explained to it. You name it so that way you can reference it with the matref. The name can be any thing you want as long as it does not have any spaces. You type in <tt>addtexture</tt> and you state a texture name. Now, how do you know what texture names there are to use?<br /> <br /> '''On Linux''': Running <tt>ls /usr/share/bzflag/*.png</tt> in a terminal will show the list of pictures.<br /> <br /> '''On Mac''': If you control click (right click) on the bzflag icon, click show package contents, click contents, and click resources, those are the pictures you may use. <br /> <br /> '''On Windows''': The default path is <tt>C:\Program Files\BZFlag\data\*.png</tt><br /> <br /> What you will find are images that are used in every day games. The top of a base, the wall of a base. A bullet which is blue_bolt.png (as was used above). The full path to the texture needs to be used if the texture is not found in that directory. Any customized textures should be uploaded to the [http://images.bzflag.org/submitimages/ BZFlag Image Submission System] before the map is hosted publicly.<br /> <br /> Servers running bzfs 2.0.8 and earlier will require "meshbox" and "meshpyr" in order to apply textures and physics to these objects.<br /> <br /> <br /> Instead of creating a new texture, many interesting and creative things can be done with the "diffuse" parameter in the material object. You can add the diffuse command and it will look like this diffuse 1 1 1 1. The first number is the amount of red that will be in the meshobject. The second number is the amount of green, the third is the amount of blue. So you can mix those colors to make more colors. You may use a range from 0-1. For example diffuse .3 .5 .26 1. The fourth number determines the opacity or transparency (the see-throughability). 0 is invisible, .5 is half invisible, and 1 is normal. <br /> <br /> material <br /> name mat1 <br /> diffuse .5 .25 .1 .6 <br /> addtexture mesh.png <br /> end<br /> <br /> ===Physics===<br /> <br /> <br /> Physics make your tank behave in different ways. If you have ever played laser mania by Louman than you know on the outskirts of the map there is something you can jump on and you go really fast, that is a physics. Physics and materials work the same way. Physics is to material as phydrv is to matref. You must specify a physics then on a meshbox, meshpyr cone arc sphere or whatever, you can reference that physics by using the phydrv command just like you would use the matref command for materials. There are different physics commands. Linear, angular, slide and death. In the Louman map I mentioned above is a linear physics. Linear physics makes your tank move in a line. The numbers after a linear command are just like position x y z. Example:<br /> <br /> physics <br /> name phy1 <br /> linear 50 0 0 <br /> end <br /> <br /> This will make your tank move at a speed of 50 in a positive x direction you may use -50 and it will make it go the other way.<br /> <br /> physics <br /> name phy2 <br /> linear 0 50 0 <br /> end <br /> <br /> This will make your tank move at a speed of 50 in a positive y direction <br /> <br /> physics <br /> name phy3 <br /> linear 0 0 50 <br /> end <br /> <br /> This will make your tank jump at a speed of 50 <br /> <br /> physics <br /> name phy4 <br /> slide 5 0 <br /> end <br /> <br /> This will make your tank basically feel like it's on ice. Whichever way the tank is moving it will keep moving that way. <br /> <br /> physics <br /> name phy5 <br /> death haha! you died <br /> end <br /> <br /> This will make the tank die when it touches the object that refers to this and the message haha! you died will be displayed to that person. <br /> <br /> example:<br /> physics <br /> name phy1 <br /> death I like you better dead! <br /> end <br /> meshbox <br /> position 0 0 0 <br /> size 10 10 10 <br /> rotation 0 <br /> phydrv phy1 # Or what ever you named the physics.<br /> end <br /> <br /> This works just like the material <br /> <br /> The thing about physics and materials is that they have to be written before they are referenced. <br /> <br /> This '''won't''' work <br /> <br /> meshbox <br /> position 0 0 0 <br /> size 10 10 10 <br /> rotation 0 <br /> matref mat1 <br /> end <br /> material <br /> name mat1 <br /> addtexture blue_team.png <br /> end<br /> <br /> ===Groups===<br /> A group is a defined group of objects that can be called to gether as one.<br /> <br /> For example if a map editor is makeing a forest, and each tree contains 2 objects, the editor doesn't want to type up the code for each tree over and over again. What he can do is tell BZFS that these objects = tree. and then whenever he wants to make a tree he just types tree.<br /> <br /> Example-----------<br /> <br /> first define a group of obects as a tree <br /> <br /> <br /> define tree<br /> <br /> box<br /> position 0 0 0<br /> size 2 2 4<br /> end<br /> <br /> pyramid<br /> position 0 0 3<br /> size 5 5 10<br /> end<br /> <br /> enddef<br /> <br /> then to add a tree simpily type<br /> <br /> <br /> group tree<br /> position 0 0 0<br /> end<br /> <br /> ==Transformations==<br /> [[Category:Map Making]]<br /> Transformations are simple ways of modifying objects so that maps have some variety. These can get complicated so I will only give you a sample of what they can do. There are 3 transformations shift, spin, and shear. You can find a different also helpful page here [[3d Transformations]]<br /> <br /> The one is will tell you about is '''Shift'''.<br /> <br /> '''Shift''' moves an object by the amount of units that you specify from its present position.<br /> the object..<br /> box<br /> position 10 10 0<br /> end<br /> <br /> is at place 10 10 0<br /> <br /> while the object..<br /> <br /> box<br /> position 10 10 0<br /> shift 0 0 10<br /> end<br /> <br /> is at position 10 10 10.<br /> <br /> ====Spin====<br /> Spinning an object is just like rotating an object but can be on a different axis. (y and x)<br /> When you rotate it is around the center of the object.<br /> Remember: Only spin-able objects can be spun.<br /> Here is what the code looks like:<br /> meshbox<br /> position 0 0 0 <br /> rotation 0<br /> size 10 10 10<br /> spin 45 0 1 0<br /> end<br /> The meshbox will now be tilted 45 degrees on its y axis.<br /> Spin code has four numbers, the first one is how many degrees to spin.<br /> The last three are for which axis's to spin, by placing a value of more than 0.</div>

Yrogirg https://wiki.bzflag.org/index.php?title=Meshpyr&diff=7098 Meshpyr 2010-07-04T06:27:26Z

<p>Yrogirg: /* Appearance */</p> <hr /> <div>[[Image:MeshpyrAppearance.jpg|right|thumb|400px|Several meshpyr, with the one in the middle having the default texture]]<br /> A meshpyr is a [[BZW]] map object that constructs a specialized [[Mesh|mesh]] that has the geometric appearance of a [[Pyramid]]. It replaces the [[pyramid]] object as of [[BZFlag 2.0.0|v2.0.0]] and is compatible with [[material|materials]] and [[physics|physics drivers]].<br /> <br /> <br /> <br /> ==Appearance==<br /> An meshpyr without a material definition will use the default material used by a standard [[pyramid]] object. Geometrically a meshpyr is identical to a standard [[pyramid]] object.<br /> <br /> meshpyr<br /> name example 1<br /> position 0.0 0.0 0.0<br /> size 15 15 15 <br /> rotation 0.0<br /> matref Mymaterial<br /> phydrv MyPhydrv<br /> end<br /> <br /> name=name<br /> position=positon on map<br /> rotation=rotate on z axis<br /> size=size amount<br /> matref=apply a material/texture here<br /> phydrv=assign a physics driver<br /> <br /> ==Editor Support==<br /> The meshpyr object is only fully supported by the [[BZWTools]] blender plug-in.<br /> <br /> [[Category:Map Making]]<br /> [[Category:Map_Objects]]</div>

Yrogirg https://wiki.bzflag.org/index.php?title=User:Yrogirg/Test&diff=6902 User:Yrogirg/Test 2010-02-06T20:04:12Z

<p>Yrogirg: </p> <hr /> <div>STOP editing this page, it's the user subpage, I use it as a draft/test page. If you want the final result, look at [[Tricks with no skills]]. If you want to talk tome, use talk page instead. Or the talk page of the article u are interested in.<br /> <br /> Getting the most from your client can give considerable advantages without [[Known Cheats|cheating]] and any [[Essential skills|skills]].<br /> <br /> ==Tune the graphics==<br /> This only affects systems with VERY low FPS(under 60) Most systems get well over 100fps on even old hardware. Also Fog is enforced in 3.0--[[User:JeffM2501|JeffM2501]] 14:26, 6 February 2010 (EST)<br /> <br /> I know fog forced in 3.0. And thats not about performance, its all about better aiming --- without fog and rain you concentrate better. Btw, I'm still writing and its my personal draft. [[User:Yrogirg|Yrogirg]] 14:35, 6 February 2010 (EST)<br /> <br /> First of all, disable rain and fog, so you will be able to see further. This is especially handy with laser flag. But remember, some maps (e.g. Desert War) have very slight fog, that doesn't affect gameplay, but makes the map much more nicer. And note, that in [[BZFlag 3.0|3.0]] fog is enforced.<br /> <br /> Then decide about lightning and shadows. Do you really need them? These settings affect the image contrast. Lightning may distort the appearance of objects, enemy is less visible when he is in a shadow. The only use of shadow is that stealth tanks have one, so it might help you to identify them.<br /> <br /> Now lets turn to textures. You need them, except of one case. If the game is about a dark (black) labyrinth, where you can't tell wall from the ceiling, turn off textures and turn on lightning --- that will help you greatly. Experiment with the texturing display options. The setting "Linear Mipmap Linear" is fastest on almost all OS's and graphics cards. <br /> <br /> There is another setting that affects the image, but you can't set it once and for all --- time of the day. When you spawn on the server you will see the map at the server time. You have to use - and = keys to adjust time of the day and to make it actually day.<br /> <br /> ==Tune the radar==<br /> You will find soon, that the [[radar]] is actually the most important part of the screen. So make it as big as possible and transparent. Also set it into Enhanced style. However, on some maps big radar will fool you, if the map author has left some huge unimportant objects visible on a radar, but such maps usually aren't very playable and unpopular.<br /> <br /> Shots must be clearly visible on the radar, so look at the settings "Radar Shot Size" and "Radar Shot Length"<br /> <br /> ==Other settings==<br /> Set Display Threads to off to have larger visible area.<br /> <br /> Set Track Marks setting as high as possible --- that will help you to track cloacked and st tanks.<br /> <br /> ==Get the most information during the game==<br /> Use look button (the same you lock with GM) to find what flag someone carries. This button is a great help on maps without radar --- use it to figure where other tanks are, especially cloacked.<br /> <br /> Hear attentively the sounds to figure weather there is a stealth jumping. It works well if you are somewhere high, so the enemy needs to jump to you.<br /> <br /> As already mentioned, watch tanks marks to figure st's and cl's. Shadows from stealthed tanks can also help.<br /> <br /> Listen for your teammates --- they provide some valuable information, e.g. enemy's st positions. You should be familiar with [[Jargon|bzflag jargon]].<br /> <br /> Use you radar against campers. Imagine there is a laser camper higher then you. Get laser flag, hide some where he cant see you and turn to him. Then use 4 and 5 keys (or shift + wheel) to make him coincide with a special tick on the radar. So now you are aiming at him. Then jump and when you'll see camper, shoot. If you are lucky he won't be able to react fast enough and shoot you.<br /> <br /> ==Key mapping==<br /> There certainly must be a separate article. Players usually find there own input settings, however there are some styles and useful ideas.</div>

Yrogirg https://wiki.bzflag.org/index.php?title=User:Yrogirg/Test&diff=6897 User:Yrogirg/Test 2010-02-06T19:56:44Z

<p>Yrogirg: </p> <hr /> <div>Getting the most from your client can give considerable advantages without [[Known Cheats|cheating]] and any [[Essential skills|skills]].<br /> <br /> ==Tune the graphics==<br /> This only affects systems with VERY low FPS(under 60) Most systems get well over 100fps on even old hardware. Also Fog is enforced in 3.0--[[User:JeffM2501|JeffM2501]] 14:26, 6 February 2010 (EST)<br /> <br /> I know fog forced in 3.0. And thats not about performance, its all about better aiming --- without fog and rain you concentrate better. Btw, I'm still writing and its my personal draft. [[User:Yrogirg|Yrogirg]] 14:35, 6 February 2010 (EST)<br /> <br /> First of all, disable rain and fog, so you will be able to see further. This is especially handy with laser flag. But remember, some maps (e.g. Desert War) have very slight fog, that doesn't affect gameplay, but makes the map much more nicer. And note, that in [[BZFlag 3.0|3.0]] fog is enforced.<br /> <br /> Then decide about lightning and shadows. Do you really need them? These settings affect the image contrast. Lightning may distort the appearance of objects, enemy is less visible when he is in a shadow. The only use of shadow is that stealth tanks have one, so it might help you to identify them.<br /> <br /> Now lets turn to textures. You need them, except of one case. If the game is about a dark (black) labyrinth, where you can't tell wall from the ceiling, turn off textures and turn on lightning --- that will help you greatly.<br /> <br /> There is another setting that affects the image, but you can't set it once and for all --- time of the day. When you spawn on the server you will see the map at the server time. You have to use - and = keys to adjust time of the day and to make it actually day.<br /> <br /> ==Tune the radar==<br /> You will find soon, that the [[radar]] is actually the most important part of the screen. So make it as big as possible and transparent. Also set it into Enhanced style. However, on some maps big radar will fool you, if the map author has left some huge unimportant objects visible on a radar, but such maps usually aren't very playable and unpopular.<br /> <br /> Shots must be clearly visible on the radar, so look at the settings "Radar Shot Size" and "Radar Shot Length"<br /> <br /> ==Other settings==<br /> Set Display Threads to off to have larger visible area.<br /> <br /> Set Track Marks setting as high as possible --- that will help you to track cloacked and st tanks.<br /> <br /> ==Get the most information during the game==<br /> Use look button (the same you lock with GM) to find what flag someone carries. This button is a great help on maps without radar --- use it to figure where other tanks are, especially cloacked.<br /> <br /> Hear attentively the sounds to figure weather there is a stealth jumping. It works well if you are somewhere high, so the enemy needs to jump to you.<br /> <br /> As already mentioned, watch tanks marks to figure st's and cl's. Shadows from stealthed tanks can also help.<br /> <br /> Listen for your teammates --- they provide some valuable information, e.g. enemy's st positions. You should be familiar with [[Jargon|bzflag jargon]].<br /> <br /> Use you radar against campers. Imagine there is a laser camper higher then you. Get laser flag, hide some where he cant see you and turn to him. Then use 4 and 5 keys (or shift + wheel) to make him coincide with a special tick on the radar. So now you are aiming at him. Then jump and when you'll see camper, shoot. If you are lucky he won't be able to react fast enough and shoot you.<br /> <br /> ==Key mapping==<br /> There certainly must be a separate article. Players usually find there own input settings, however there are some styles and useful ideas.</div>

Yrogirg https://wiki.bzflag.org/index.php?title=Optimizations&diff=6896 Optimizations 2010-02-06T19:54:41Z

<p>Yrogirg: Let it be.</p> <hr /> <div>Getting the most from your client can give considerable advantages without [[Known Cheats|cheating]] and any [[Essential skills|skills]].<br /> <br /> ==Tune the graphics==<br /> First of all, disable rain and fog, so you will be able to see further. This is especially handy with laser flag. But remember, some maps (e.g. Desert War) have very slight fog, that doesn't affect gameplay, but makes the map much more nicer. And note, that in [[BZFlag 3.0|3.0]] fog is enforced.<br /> <br /> Then decide about lightning and shadows. Do you really need them? These settings affect the image contrast. Lightning may distort the appearance of objects, enemy is less visible when he is in a shadow. The only use of shadow is that stealth tanks have one, so it might help you to identify them.<br /> <br /> Now lets turn to textures. You need them, except of one case. If the game is about a dark (black) labyrinth, where you can't tell wall from the ceiling, turn off textures and turn on lightning --- that will help you greatly.<br /> <br /> There is another setting that affects the image, but you can't set it once and for all --- time of the day. When you spawn on the server you will see the map at the server time. You have to use - and = keys to adjust time of the day and to make it actually day.<br /> <br /> ==Tune the radar==<br /> You will find soon, that the [[radar]] is actually the most important part of the screen. So make it as big as possible and transparent. Also set it into Enhanced style. However, on some maps big radar will fool you, if the map author has left some huge unimportant objects visible on a radar, but such maps usually aren't very playable and unpopular.<br /> <br /> Shots must be clearly visible on the radar, so look at the settings "Radar Shot Size" and "Radar Shot Length"<br /> <br /> ==Other settings==<br /> Set Display Threads to off to have larger visible area.<br /> <br /> Set Track Marks setting as high as possible --- that will help you to track cloacked and st tanks.<br /> <br /> ==Get the most information during the game==<br /> Use look button (the same you lock with GM) to find what flag someone carries. This button is a great help on maps without radar --- use it to figure where other tanks are, especially cloacked.<br /> <br /> Hear attentively the sounds to figure weather there is a stealth jumping. It works well if you are somewhere high, so the enemy needs to jump to you.<br /> <br /> As already mentioned, watch tanks marks to figure st's and cl's. Shadows from stealthed tanks can also help.<br /> <br /> Listen for your teammates --- they provide some valuable information, e.g. enemy's st positions. You should be familiar with [[Jargon|bzflag jargon]].<br /> <br /> Use you radar against campers. Imagine there is a laser camper higher then you. Get laser flag, hide some where he cant see you and turn to him. Then use 4 and 5 keys (or shift + wheel) to make him coincide with a special tick on the radar. So now you are aiming at him. Then jump and when you'll see camper, shoot. If you are lucky he won't be able to react fast enough and shoot you.<br /> <br /> ==Key mapping==<br /> There certainly must be a separate article. Players usually find there own input settings, however there are some styles and useful ideas.<br /> <br /> [[Category:Tactics]]</div>

Yrogirg https://wiki.bzflag.org/index.php?title=User:Yrogirg/Test&diff=6895 User:Yrogirg/Test 2010-02-06T19:47:42Z

<p>Yrogirg: </p> <hr /> <div>Getting the most from your client can give considerable advantages without cheating and any [[Essential skills|skills]].<br /> <br /> ==Tune the graphics==<br /> This only affects systems with VERY low FPS(under 60) Most systems get well over 100fps on even old hardware. Also Fog is enforced in 3.0--[[User:JeffM2501|JeffM2501]] 14:26, 6 February 2010 (EST)<br /> <br /> I know fog forced in 3.0. And thats not about performance, its all about better aiming --- without fog and rain you concentrate better. Btw, I'm still writing and its my personal draft. [[User:Yrogirg|Yrogirg]] 14:35, 6 February 2010 (EST)<br /> <br /> First of all, disable rain and fog, so you will be able to see further. This is especially handy with laser flag. But remember, some maps (e.g. Desert War) have very slight fog, that doesn't affect gameplay, but makes the map much more nicer. And note, that in [[BZFlag 3.0|3.0]] fog is enforced.<br /> <br /> Then decide about lightning and shadows. Do you really need them? These settings affect the image contrast. Lightning may distort the appearance of objects, enemy is less visible when he is in a shadow. The only use of shadow is that stealth tanks have one, so it might help you to identify them.<br /> <br /> Now lets turn to textures. You need them, except of one case. If the game is about a dark (black) labyrinth, where you can't tell wall from the ceiling, turn off textures and turn on lightning --- that will help you greatly.<br /> <br /> There is another setting that affects the image, but you can't set it once and for all --- time of the day. When you spawn on the server you will see the map at the server time. You have to use - and = keys to adjust time of the day and to make it actually day.<br /> <br /> ==Tune the radar==<br /> You will find soon, that the [[radar]] is actually the most important part of the screen. So make it as big as possible and transparent. Also set it into Enhanced style. However, on some maps big radar will fool you, if the map author has left some huge unimportant objects visible on a radar, but such maps usually aren't very playable and unpopular.<br /> <br /> Shots must be clearly visible on the radar, so look at the settings "Radar Shot Size" and "Radar Shot Length"<br /> <br /> ==Other settings==<br /> Set Display Threads to off to have larger visible area.<br /> <br /> Set Track Marks setting as high as possible --- that will help you to track cloacked and st tanks.<br /> <br /> ==Get the most information during the game==<br /> Use look button (the same you lock with GM) to find what flag someone carries. This button is a great help on maps without radar --- use it to figure where other tanks are, especially cloacked.<br /> <br /> Hear attentively the sounds to figure weather there is a stealth jumping. It works well if you are somewhere high, so the enemy needs to jump to you.<br /> <br /> As already mentioned, watch tanks marks to figure st's and cl's. Shadows from stealthed tanks can also help.<br /> <br /> Listen for your teammates --- they provide some valuable information, e.g. enemy's st positions. You should be familiar with [[Jargon|bzflag jargon]].<br /> <br /> Use you radar against campers. Imagine there is a laser camper higher then you. Get laser flag, hide some where he cant see you and turn to him. Then use 4 and 5 keys (or shift + wheel) to make him coincide with a special tick on the radar. So now you are aiming at him. Then jump and when you'll see camper, shoot. If you are lucky he won't be able to react fast enough and shoot you.<br /> <br /> ==Key mapping==<br /> There certainly must be a separate article. Players usually find there own input settings, however there are some styles and useful ideas.</div>

Yrogirg https://wiki.bzflag.org/index.php?title=User:Yrogirg/Test&diff=6894 User:Yrogirg/Test 2010-02-06T19:35:58Z

<p>Yrogirg: </p> <hr /> <div>Getting the most from your client can give considerable advantages without cheating and any skills.<br /> <br /> ==Tune the graphics==<br /> This only affects systems with VERY low FPS(under 60) Most systems get well over 100fps on even old hardware. Also Fog is enforced in 3.0--[[User:JeffM2501|JeffM2501]] 14:26, 6 February 2010 (EST)<br /> <br /> I know fog forced in 3.0. And thats not about performance, its all about better aiming --- withou fog and rain you concentrate better. Btw, I'm still writing and its my personal draft. [[User:Yrogirg|Yrogirg]] 14:35, 6 February 2010 (EST)<br /> <br /> First of all, disable rain and fog, so you will be able to see further. This is especially handy with laser flag. But remember, some maps (e.g. Desert War) have very slight fog, that doesn't affect gameplay, but makes the map much more nicer.<br /> <br /> Then decide about lightning and shadows. Do you really need them? These settings affect the image contrast. Lightning may distort the apppearence of objects, enemy is less visible when he is in a shadow. The only use of shadow is that stealth tanks have one, so it might help you to indicate them.<br /> <br /> Now lets turn to textures. You need them, except of one case. If the game is about a dark (black) labyrinth, where you can't tell wall from the ceiling, turn off textures and turn on lightning --- that will help you greatly.<br /> <br /> There is another setting that affects the image, but you can't set it once and for all --- daytime. When you spawn on the server you will see the map at the server daytime. You have to use - and = keys to adjust daytime and to make it actually day.<br /> <br /> ==Tune the radar==<br /> You will find soon, that the [[radar]] is actually the most important part of the screen. So make it as big as possible and transparent. Also set it into Enhanced style. However, on some maps big radar will fool you, if the map author has left some huge unimportant objects visible on a radar, but such maps usually aren't very playable and unpopular.<br /> <br /> Shots must be clearly visible on the radar, so look at the settings "Radar Shot Size" and "Radar Shot Length"<br /> <br /> ==Other settings==<br /> Set Display Threads to off to have larger visible area.<br /> <br /> Set Track Marks setting as high as possible --- that will help you to track cloacked and st tanks.<br /> <br /> ==Get the most information during the game==<br /> Use look button (the same you lock with GM) to find what flag someone carries. This button is a great help on maps without radar --- use it to figure where other tanks are, especially cloacked.<br /> <br /> Hear attentively the sounds to figure weather there is a stealth jumping. It works well if you are somewhere high, so the enemy needs to jump to you.<br /> <br /> As already mentioned, watch tanks marks to figure st's and cl's. Shadows from stealthed tanks can also help.<br /> <br /> Listen for your teammates --- they provide some valuable information, e.g. enemy's st positions. You should be familiar with [[Jargon|bzflag jargon]].<br /> <br /> Use you radar against campers. Imagine there is a laser camper higher then you. Get laser flag, hide some where he cant see you and turn to him. Then use 4 and 5 keys (or shift plus wheel) to make him coincide with a special tick on the radar. So now you are aiming at him. Then jump and when you'll see camper, shoot. If you are lucky he won't be able to react fast enough or shoot you.</div>

Yrogirg https://wiki.bzflag.org/index.php?title=User:Yrogirg/Test&diff=6893 User:Yrogirg/Test 2010-02-06T19:31:33Z

<p>Yrogirg: </p> <hr /> <div>Getting the most from your client can give considerable advantages without cheating and any skills.<br /> <br /> ==Tune the graphics==<br /> This only affects systems with VERY low FPS(under 60) Most systems get well over 100fps on even old hardware. Also Fog is enforced in 3.0--[[User:JeffM2501|JeffM2501]] 14:26, 6 February 2010 (EST)<br /> <br /> First of all, disable rain and fog, so you will be able to see further. This is especially handy with laser flag. But remember, some maps (e.g. Desert War) have very slight fog, that doesn't affect gameplay, but makes the map much more nicer.<br /> <br /> Then decide about lightning and shadows. Do you really need them? These settings affect the image contrast. Lightning may distort the appearance of objects, enemy is less visible when he is in a shadow. The only use of shadow is that stealth tanks have one, so it might help you to identify them.<br /> <br /> Now lets turn to textures. You need them, except of one case. If the game is about a dark (black) labyrinth, where you can't tell wall from the ceiling, turn off textures and turn on lightning --- that will help you greatly.<br /> <br /> There is another setting that affects the image, but you can't set it once and for all --- time of the day. When you spawn on the server you will see the map at the server time. You have to use - and = keys to adjust time of the day and to make it actually day.<br /> <br /> ==Tune the radar==<br /> You will find soon, that the [[radar]] is actually the most important part of the screen. So make it as big as possible and transparent. Also set it into Enhanced style. However, on some maps big radar will fool you, if the map author has left some huge unimportant objects visible on a radar, but such maps usually aren't very playable and unpopular.<br /> <br /> Shots must be clearly visible on the radar, so look at the settings "Radar Shot Size" and "Radar Shot Length"<br /> <br /> ==Other settings==<br /> Set Display Threads to off to have larger visible area.<br /> <br /> Set Track Marks setting as high as possible --- that will help you to track cloacked and st tanks.<br /> <br /> ==Get the most information during the game==<br /> Use look button (the same you lock with GM) to find what flag someone carries. This button is a great help on maps without radar --- use it to figure where other tanks are, especially cloacked.<br /> <br /> Hear attentively the sounds to figure weather there is a stealth jumping. It works well if you are somewhere high, so the enemy needs to jump to you.<br /> <br /> As already mentioned, watch tanks marks to figure st's and cl's. Shadows from stealthed tanks can also help.<br /> <br /> Listen for your teammates --- they provide some valuable information, e.g. enemy's st positions. You should be familiar with [[Jargon|bzflag jargon]].<br /> <br /> Use you radar against campers. Imagine there is a laser camper higher then you. Get laser flag, hide some where he cant see you and turn to him. Then use 4 and 5 keys (or shift + wheel) to make him coincide with a special tick on the radar. So now you are aiming at him. Then jump and when you'll see camper, shoot. If you are lucky he won't be able to react fast enough and shoot you.<br /> <br /> ==Key mapping==<br /> There certainly must be a separate article. Players usually find there own input settings, however there are some styles and useful ideas.</div>

Yrogirg https://wiki.bzflag.org/index.php?title=User:Yrogirg/Test&diff=6891 User:Yrogirg/Test 2010-02-06T19:21:09Z

<p>Yrogirg: </p> <hr /> <div>Getting the most from your client can give considerable advantages without cheating and any skills.<br /> <br /> ==Tune the graphics==<br /> First of all, disable rain and fog, so you will be able to see further. This is especially handy with laser flag. But remember, some maps (e.g. Desert War) have very slight fog, that doesn't affect gameplay, but makes the map much more nicer.<br /> <br /> Then decide about lightning and shadows. Do you really need them? These settings affect the image contrast. Lightning may distort the apppearence of objects, enemy is less visible when he is in a shadow. The only use of shadow is that stealth tanks have one, so it might help you to indicate them.<br /> <br /> Now lets turn to textures. You need them, except of one case. If the game is about a dark (black) labyrinth, where you can't tell wall from the ceiling, turn off textures and turn on lightning --- that will help you greatly.<br /> <br /> There is another setting that affects the image, but you can't set it once and for all --- daytime. When you spawn on the server you will see the map at the server daytime. You have to use - and = keys to adjust daytime and to make it actually day.<br /> <br /> ==Tune the radar==<br /> You will find soon, that the [[radar]] is actually the most important part of the screen. So make it as big as possible and transparent. Also set it into Enhanced style. However, on some maps big radar will fool you, if the map author has left some huge unimportant objects visible on a radar, but such maps usually aren't very playable and unpopular.<br /> <br /> Shots must be clearly visible on the radar, so look at the settings "Radar Shot Size" and "Radar Shot Length"<br /> <br /> ==Other settings==<br /> Set Display Threads to off to have larger visible area.<br /> <br /> Set Track Marks setting as high as possible --- that will help you to track cloacked and st tanks.<br /> <br /> ==Get the most information during the game==<br /> Use look button (the same you lock with GM) to find what flag someone carries. This button is a great help on maps without radar --- use it to figure where other tanks are, especially cloacked.<br /> <br /> Hear attentively the sounds to figure weather there is a stealth jumping. It works well if you are somewhere high, so the enemy needs to jump to you.<br /> <br /> As already mentioned, watch tanks marks to figure st's and cl's. Shadows from stealthed tanks can also help.<br /> <br /> Listen for your teammates --- they provide some valuable information, e.g. enemy's st positions. You should be familiar with [[Jargon|bzflag jargon]].<br /> <br /> Use you radar against campers. Imagine there is a laser camper higher then you. Get laser flag, hide some where he cant see you and turn to him. Then use 4 and 5 keys (or shift plus wheel) to make him coincide with a special tick on the radar. So now you are aiming at him. Then jump and when you'll see camper, shoot. If you are lucky he won't be able to react fast enough or shoot you.</div>

Yrogirg https://wiki.bzflag.org/index.php?title=User:Yrogirg/Test&diff=6890 User:Yrogirg/Test 2010-02-06T19:05:10Z

<p>Yrogirg: </p> <hr /> <div>Getting the most from your client can give considerable advantages without cheating and any skills.<br /> <br /> ==Tune the graphics==<br /> First of all, disable rain and fog, so you will be able to see further. This is especially handy whith laser flag. But remember, some maps (e.g. Desert War) have very slight fog, that doesn't affect gameplay, but makes the map much more nicer.<br /> <br /> Then decide about lightning and shadows. Do you really need them? This settings affects the image contrast. Lightning may distort the view of objects, enemy is less visible when he is in a shadow. The only use of shadow is that stealth tanks have one, so it might help to indicate them.<br /> <br /> Now lets turn to textures. You need them, except of one case. If the game is about a dark (black) labyrinth, where you cant tell wall from the ceiling, turn off textures and turn on lightning --- that will help you greatly.<br /> <br /> There is another setting that affects the image, but you can't set it once and for all --- daytime. When you spawn on the server you will see the map at the server daytime. You have to use - and = keys to adjust daytime and to make it actually day.<br /> <br /> ==Tune the radar==<br /> You will find soon, that the radar is actually the most important part of the screen. So make it as big as possible and transparent. Also set it into Enhanced style. However, on some maps big radar will if the map author has left some huge unimportant objects visible on a radar, but such maps usually aren't very playable and unpopular.<br /> <br /> Shots must be clearly visible on the radar, so look at the settings "Radar Shot Size" and "Radar Shot Length"<br /> <br /> ==Other settings==<br /> Set Display Threads to off to have larger visible area.<br /> <br /> Set Track Marks setting as high as possible --- that will help you to track cloacked and st tanks.<br /> <br /> ==Smart use of ==<br /> Use you radar against campers. Imagine there is a laser camper higher then you. Get laser flag, hide some where he cant see you and turn to him. Then use 4 and 5 keys (or shift plus wheel) to make him coincide with a special tick on the radar. So now you are aiming at him. Then jump and when you'll see camper, shoot. If you are lucky he won't be able to react fast enough or shoot you.<br /> <br /> Use look button (the same you lock with GM) to find what flag someone carries. This button is a great help on maps without radar --- use it to figure where other tanks are, especially cloacked.<br /> <br /> Hear attentively the sounds to figure weather there is a stealth jumping. It works well if you are somewhere high and so the enemy needs to jump to you.</div>

Yrogirg https://wiki.bzflag.org/index.php?title=User:Yrogirg/Test&diff=6889 User:Yrogirg/Test 2010-02-06T18:41:23Z

<p>Yrogirg: </p> <hr /> <div>Getting the most from your client can give considerable advantages over other players without cheating.<br /> <br /> ==Tune the graphics==<br /> First of all, disable rain and fog, so you will be able to see further. This is especially handy whith laser flag. But remember, some maps (e.g. Desert War) have very slight fog, that doesn't affect gameplay, but makes the map much more nicer.<br /> <br /> Then decide about lightning and shadows. Do you really need them? This settings affects the image contrast. Lightning may distort the view of objects, enemy is less visible when he is in a shadow. The only use of shadow is that stealth tanks have one, so it might help to indicate them.<br /> <br /> Now lets turn to textures. You need them, except of one case. If the game is about a dark (black) labyrinth, where you cant tell wall from the ceiling, turn off textures and turn on lightning --- that will help you greatly.<br /> <br /> There is another setting that affects the image, but you can't set it once and for all --- daytime. When you spawn on the server you will see the map at the server daytime. You have to use - and = keys to adjust daytime and to make it actually day.<br /> <br /> ==Tune the radar==<br /> You will find soon, that the radar is actually the most important part of the screen. So make it as big as possible and transparent. Also set it into Enhanced style. However, on some maps big radar will if the map author has left some huge unimportant objects visible on a radar, but such maps usually aren't very playable and unpopular.<br /> <br /> Shots must be clearly visible on the radar, so look at the settings "Radar Shot Size" and "Radar Shot Length"<br /> <br /> ==Other settings==<br /> Set Display Threads to off to have larger visible area.<br /> <br /> Set Track Marks setting as high as possible --- that will help you to track cloacked and st tanks.</div>

Yrogirg https://wiki.bzflag.org/index.php?title=User:Yrogirg/Test&diff=6888 User:Yrogirg/Test 2010-02-06T18:36:14Z

<p>Yrogirg: </p> <hr /> <div>Getting the most from your client can give considerable advantages over other players without cheating.<br /> <br /> ==Tune the graphics==<br /> First of all, disable rain and fog, so you will be able to see further. This is especially handy whith laser flag. But remember, some maps (e.g. Desert War) have very slight fog, that doesn't affect gameplay, but makes the map much more nicer.<br /> <br /> Then decide about lightning and shadows. Do you really need them? This settings affects the image contrast. Lightning may distort the view of objects, enemy is less visible when he is in a shadow. The only use of shadow is that stealth tanks have one, so it might help to indicate them.<br /> <br /> Now lets turn to textures. You need them, except of one case. If the game is about a dark (black) labyrinth, where you cant tell wall from the ceiling, turn off textures and turn on lightning --- that will help you greatly.<br /> <br /> There is another setting that affects the image, but you can't set it once and for all --- daytime. When you spawn on the server you will see the map at the server daytime. You have to use - and = keys to adjust daytime and to make it actually day.<br /> <br /> ==Tune the radar==<br /> You will find soon, that the radar is actually the most important part of the screen. So make it as big as possible and transparent. Also set it into Enhanced style. However, on some maps big radar will if the map author has left some huge unimportant objects visible on a radar, but such maps usually aren't very playable and unpopular.<br /> <br /> Shots must be clearly visible on the radar, so look at the settings "Radar Shot Size" and "Radar Shot Length"<br /> <br /> ==Effects Setting==</div>

Yrogirg https://wiki.bzflag.org/index.php?title=User:Yrogirg/Test&diff=6887 User:Yrogirg/Test 2010-02-06T18:21:45Z

<p>Yrogirg: </p> <hr /> <div>Getting the most from your client can give considerable advantages over other players without cheating.<br /> <br /> ==Tune the graphics==<br /> First of all, disable rain and fog, so you will be able to see further. This is especially handy whith laser flag. But remember, some maps (e.g. Desert War) have very slight fog, that doesn't affect gameplay, but makes the map much more nicer.<br /> <br /> Then decide about lightning and shadows. Do you really need them? This settings affects the image contrast. Lightning may distort the view of objects, enemy is less visible when he is in a shadow. The only use of shadow is that stealth tanks have one, so it might help to indicate them.<br /> <br /> Now lets turn to textures. You need them, except of one case. If the game is about a dark (black) labyrinth, where you cant tell wall from the ceiling, turn off textures and turn on lightning --- that will help you greatly.<br /> <br /> There is another setting that affects the image, but you can't set it once and for all --- daytime. When you spawn on the server you will see the map at the server daytime. You have to use - and = keys to adjust daytime and to make it actually day.</div>

Yrogirg https://wiki.bzflag.org/index.php?title=User:Yrogirg/Test&diff=6886 User:Yrogirg/Test 2010-02-06T18:08:25Z

<p>Yrogirg: </p> <hr /> <div>Getting the most from your client can give considerable advantages over other players without cheating.<br /> <br /> ==Tune the graphics==<br /> First of all, disable rain and fog, so you will be able to see further. This is especially handy whith laser flag. But remember, some maps (e.g. Desert War) have very slight fog, that doesn't affect gameplay, but makes the map much more nicer.<br /> <br /> Then decide about shadows. Do you really need them? Shadows may distort the view of objects, enemy is less visible when he is in a shadow. The only use of shadow is that stealth tanks have one, so it might help to indicate them.<br /> <br /> Now lets turn to textures. You need them, except of one case. If the game is about a dark (black) labyrinth, where u cant tell wall fromt the ceiling, turn off textures.</div>

Yrogirg https://wiki.bzflag.org/index.php?title=User:Yrogirg/Test&diff=6885 User:Yrogirg/Test 2010-02-06T17:58:14Z

<p>Yrogirg: New page: Getting the most from your client can give considereable advantages over other players. ==Tune the graphics== First of all, disable rain and fog, so you will be able to see further. This ...</p> <hr /> <div>Getting the most from your client can give considereable advantages over other players.<br /> <br /> ==Tune the graphics==<br /> First of all, disable rain and fog, so you will be able to see further. This is especially handy whith laser flag. But remember, some maps (e.g. Desert War) have very slight fog, that doesn't affect gameplay, but makes the map much more nicer.<br /> <br /> Then decide about shadows. Do tou really need them?</div>

Yrogirg