Armagetron Advanced - User contributions [en]

User:Adam1213

2005-12-13T13:23:23Z

Adam1213:

==<big><big>[http://en.wikipedia.org/wiki/User:Adam1213 My user page on wikipedia]</big></big>==

Settings I like to use for a game: 
cycle_speed 2 
cycle_brake -200 
cycle_rubber 100 
and trail length of 400

links
[[Special:Specialpages]]

User:Adam1213

2005-12-13T13:22:48Z

Adam1213:

====<big><big><big><big><big>[http://en.wikipedia.org/wiki/User:Adam1213 My user page on wikipedia]</big></big></big></big></big>====

Settings I like to use for a game: 
cycle_speed 2 
cycle_brake -200 
cycle_rubber 100 
and trail length of 400

links
[[Special:Specialpages]]

Server Administration Guide

2005-11-23T07:15:13Z

Adam1213:

Setting up a server for Armagetron Advanced isn't terribly difficult, but there are a few things you need to consider when you do it. Taking a few minutes to figure out what you're trying to do will save you a whole lot of headache/heartache later on when people start playing your server.

== Starting out ==

Before you consider what OS you're going to use, what version of the game to run, and so forth, you should figure out a few basic parameters of the server. Here are some you should consider.

=== Private or Public? ===
The setting <code>TALK_TO_MASTER</code> is off by default. To make your server public (available on the master server list), you must turn on this setting. If it is off, players will only be able to connect to your server through the [[Server Bookmarks]] using your IP address.

=== Moderated? ===

Armagetron Advanced supports a limited but expanding set of in game administration commands(in 0.2.8, it will be a fairly comprehensive set). The catch is that you can only have one administration password. So in order to make moderators on your server, all you have to do is give out the administration password.

The alternative is to use the voting features that are intended to allow players to moderate the server as they see fit.

You can go either way, of course. It's entirely up to you.

=== Round or Match ===

There are plenty of ways to setup scoring on a server. A common setting is one point for each kill. While this scoring method encourages competitive play, it's not always desirable. On some servers, just surviving to the end of the round is quite an accomplishment, and you may wish to reward players for doing so. Too much of a reward will encourage players to just screw around instead of fighting.

You should also consider if you even want the standard gladiator-style fighting. It's certainly possible to set up scoring to allow for different games, such as [[Roulette]], and to encourage different playing styles. So just take a few minutes to think about it. It'll pay off in the end, because the default game server settings aren't necessarily the most popular scoring rules, and unless you really want the default scoring, you could lose most of your audience in the first two hours of operation if you didn't think about scoring.

== Setting Up ==

So now you've figured out what kind of server you want and how you want people to play on it, and you want to know how to set it up and optionally make it available on the master server browser. Setting up is fairly straightforward.

=== Install the Server ===

First you need to install the server. It's common to think of any given "server" as a special machine built by old women in third-world countries, but actually, a "server" is just any machine that makes a "service" available to other users. In this case, you're going to install software on a computer, possibly your desktop computer, that will make a game service available for other users to use.

So first you need to acquire the package called "armagetronad-dedicated". If you're using Linux, get one that says "linux" on it. For Windows, get the one that has ".exe" on the end of it. For Mac OS X, there's one with a ".dmg" extension for you. Usually the CPU architecture and OS are embedded in the filename, so pick the right one and install it.

We won't go into too many details here about installation, consult the regular documentation for how to install the server for your architecture.

=== Test the Server ===

After installing the server, the first thing you should do is test it. So start it up. If you're in Linux, you will want to become the superuser and type, in a terminal, "/etc/init.d/armagetronad-dedicated start". If you're in Windows, find the icon in your Start menu and click it. Then fire up a client and see if you can connect to it as a LAN game (under Network Game). If you can do this, then you have successfully tested the server. Now you need to shut it down. In Windows, go to the console window for the server (it opens when you start the game) and type "QUIT". In Linux, just do "/etc/init.d/armagetronad-dedicated stop".

=== Secure the Server ===

There isn't really a lot to do here, but you should consider how you want to secure the machine. If you think it will be necessary to ban certain players, then a firewall is your only option. You will need a firewall that allows you to deny connections from users by IP address. It's not foolproof, but it's the only thing that is possible right now to ban players.

If you want your server to be known on the internet, you will probably need to open a port in your router. The default port is 4534, and you need to open it for "udp". Instructions on how to configure this on your router are beyond the scope of this document, you should consult your owner's manual for further information.

Contrarily, if you do not want internet players to be able to use your server, you will need to make sure your router prevents such players but making the port mentioned above inaccessible through the router.

== Make your Settings ==

At this point you should have a good idea of what kind of server you're going to run and you should also have a working server running, but you don't yet have the server you set out to build. Now you need to configure the server itself.

The server is very flexible. As of the 0.2.8 release, you have pretty complete control over the simulation, and you also have some settings that you can configure the game rules a bit. So now all you need to do is make the settings, right? Wrong. :) First you need to understand how the settings are loaded and in what order.

=== Finding the Settings ===
* Linux -> <code>/etc/games/armagetronad-dedicated</code>
* Mac OS X -> <code>~/Library/Application Support/Armagetron Advanced</code>
* Windows -> <code>C:\program files\armagetronad</code>

Here are the files you will find (Note: this is for the 0.2.8 server, older servers vary):

;aiplayers.cfg
:This file contains the information used to determine the AI player names and skills. You can edit this file to make a more customized set of AI players, but make sure to take backups. When you upgrade or reinstall the server this file will be overwritten.

;default.cfg
:This file contains a reasonable set of defaults and shouldn't be edited.

;master.srv
:This file contains the location of the master server and connection parameters. You can edit it, but then your server won't be able to communicate with the master server that everyone uses, so only do so if you really know what you're doing and have a good reason to do it.

;rc.config
:This file is used to configure the UNIX daemon. It may not be present in Windows/Mac OS X.

;settings.cfg
:This file contains the basic set of settings used by both the client and the server. You should not edit this file.

;settings_dedicated.cfg
:This file contains an extended set of settings used by the dedicated server. You should not edit this file either.

So where should you make your changes? There are 4 files that were not listed, but they are the files you should edit! Why aren't they listed? ''You'' are supposed to make them, using a regular text editor. So, open settings_dedicated.cfg and copy the appropriate lines into the following files:

;autoexec.cfg
:I don't know what this is for, I don't use it. (Lucifer)

;server_info.cfg
:You should put server policy settings here, as well as the SERVER_NAME and connection information.

;settings_custom.cfg
:This is the file that should contain game rule and simulation settings. If you obey the convention for <code>server_info.cfg</code> and <code>settings_custom.cfg</code>, your server will not only be easier to maintain, but also easier to exchange settings with other administrators.

;everytime.cfg
:This file is loaded and processed every round. In a running server, that means you can use this file to change settings on the fly. It also means you can put special information using console commands here. For example:

<code>
SAY Server stats at http://www.armagetronadstats.com/
</code>

...will display "Admin: Server stats at http://www.armagetronadstats.com/" between every round. Very useful! You can also put:

<code>
INCLUDE settings_custom.cfg
</code>

...and your settings_custom.cfg file will be reloaded every round. Not particularly useful, but it can be helpful when you need to tweak simulation settings.

=== Making your own Settings ===

The most common settings to change affect game logic, scoring, and some basic simulation such as cycle speed, acceleration, and so forth.

==== Simulation Settings ====
;EXPLOSION_RADIUS
:Blast radius of cycle explosions. Set to 0 to have no explosion radius (obviously).
;WALLS_LENGTH
:Cycle trail length. Set to -1 to have infinite trails.
;WALLS_STAY_UP_DELAY
:Cycle trail stay up this long after the cycle's destruction, measured in seconds.
;SPEED_FACTOR
:Cycle speed factor. Increase this by two to double the speed
;CYCLE_RUBBER
:This affects grinding. Higher numbers allow players to get closer to walls before crashing. It's intended to be used solely to correct for lag, but it's usually not used that way.

==== Map Settings ====
;ARENA_AXES
:Sets the number of possible driving directions (used only when map is axes-independent, otherwise the map overwrite this value)
;MAP_FILE
:This describe how to retreive a map. It uses a special syntax to allow to describe the location of the map on the local disk and a possible list of network based location, such as web url, where to retreive the file. The syntax is "[./][directory[/directory[...]]]/filename [(fulluri[; fulluri[; fulluri[...]]])]". By default, missing files are looked up by the client on the central resource repository. If one of more URI are given in the MAP_FILE, they will be queried before going to the resource repository.

==== Game Rules ====

;SCORE_WIN
:Points you gain for being last one alive. Also known as "camping points"
;SCORE_SUICIDE
:Points you gain for every stupid death (race into the rim/your own wall). It is added, so negative numbers are appropriate here unless you want to reward people for being stupid.
;SCORE_KILL
:Points you gain for everyone racing into your wall.
;SCORE_DIE
:Points you gain for every time you race into someone else's wall. Like SCORE_SUICIDE, you should make this a negative number unless you want to reward people for sucking.

;LIMIT_SCORE
:Score limit. When a player reaches this score, the match ends and that player wins. Ties are resolved by playing another round until one player has more points than the rest.
;LIMIT_ROUNDS
:Max number of rounds to play. When this is reached, the highest-scoring player is named the winner.
;LIMIT_TIME
:Max time (in minutes). When this is reached, the highest-scoring player is named the winner of the match.

Here is a pretty common setup:

<pre>
SCORE_WIN 0
SCORE_SUICIDE 0
SCORE_KILL 1
SCORE_DIE 0

LIMIT_SCORE 10
LIMIT_ROUNDS 40
LIMIT_TIME 30
</pre>

This is the scoring system used on servers like Swampland, the old Tigers Network servers, and the goshdarn clones that are floating around. It basically means you have to get 10 points by killing other players to win the match. Breakfast in Hell used a variation:

<pre>
SCORE_WIN 0
SCORE_SUICIDE 0
SCORE_KILL 1
SCORE_DIE 0

LIMIT_SCORE 1000
LIMIT_ROUNDS 40
LIMIT_TIME 7
</pre>

You still had to kill people to win, but the match was limited to 7 minutes. After 7 minutes, a winner was declared. The Crack Pipe still uses these settings at the time of writing but may change in the future.

'''This isn't a complete list!'''

There are a whole slew of configuration items available. Since the config items are the same as console commands, you can see a pretty complete list on the [[Console Commands]] page.

== Finishing Up ==

The last thing you need to figure out is usually the first thing you know. Do you want this server to be known by the master server? If so, you need to add this line to your settings_custom.cfg:

<code>
TALK_TO_MASTER 1
</code>

Note: in previous versions, this was the default, but as of 0.2.8, the default will be to not talk to master. You will have to manually set that, so make it the last thing you do before starting the server up for play.

Of course, when that's all done, you need to start the server. Use the same procedure already referenced.

== Conclusion ==

This article is the basic "How to setup a game server" article. After reading through this article and getting your server running, the best thing you can do is to play your server for awhile, talk to other administrators, and so forth. Find out what people want, or figure out what you want. Tweak your settings however you'd like, it's your server. When you feel like you've got the hang of running a server, check out the [[Advanced Server Administration Guide]] for more cool things you can do with your server.

In the meantime, have fun!

[[Category:Server/config]]

Advanced Server Administration Guide

2005-11-23T07:09:14Z

Adam1213:

So you've been running a server for awhile and now you'd like to do more with it? Maybe you've found that there are some punk-ass players out there that you really want to kick off your server? Maybe your players are asking for more, and you're saying "Hell yeah!" but you don't know what to actually do about it?

You've come to the right place!

== Dealing with unruly players ==

There are several ways to deal with unruly players. We'll touch on each of them here.

=== Moderation ===

A common way is to have a group of moderators available so that your server usually has people logged in and playing who can use in-game admin to kick evil doers out of the server. You do this by setting <code>ADMIN_PASS</code> in your settings_custom.cfg file and then giving that password out to your preferred moderators. Then they will use the password like this:

While playing on the server, in a chat prompt, type <code>/login ADMIN_PASS</code>, replacing <code>ADMIN_PASS</code> with the password you have set for the server. This logs the player into the in-game admin system. Now you can execute commands with <code>/admin COMMAND ARGUMENTS</code>. Use <code>/logout</code> to leave the in-game admin system.

Every command is available, so be cautious to whom you give your <code>ADMIN_PASS</code>!

=== Voting ===

Voting is a popular way to deal with unruly players. It has the advantage of giving power to the players on the server and letting them decide how they want the grid to be when playing. It comes at a cost, though. First, as an admin you need to respect your players' choices. This doesn't mean you should let them walk all over you, but what's the point of letting them vote in the first place if you're just going to override it? Second, it is possible to exploit the voting system as an unruly player. There will be some more safeguards in 0.2.8 to deal with this, but in the meantime it is an issue you may need to face.

To enable voting, you should copy the group of settings from settings_dedicated.cfg into your server_info.cfg. The reason it goes in server_info.cfg is because these settings are considered "policy" and are not something you'd necessarily share with someone who asked. You might still share them, don't get me wrong, but if someone wants to clone your server and you want to help them, you'd normally just send them settings_custom.cfg and let them come up with their own server policies.

Here are the setting items you'll want to address, along with their default values:

==== Voting Policy Settings ====

These are the ones that really define how voting is to be accomplished.

;ALLOW_VOTING 1
:Turns on voting.
;ALLOW_VOTING_SPECTATOR 0
:Allows spectator players to vote. Generally not something you want to enable, hence the default.
;VOTING_BIAS 0
:Number of virtual voters opposing every change. You can think of this as the Republican Party simulated by the game server, where the game server will always oppose every vote in favor of maintaining the status quo.
;VOTING_PRIVACY 1
:Level of secrecy of the votes. 2 makes the vote as secret as possible, -2 makes it fully public. There are those who consider voting to be very personal and private, and would prefer to keep votes secret so nobody can retaliate against voters for voting against them. There are others (me) who find that making the votes public keeps voters honest and prevents people from backstabbing one another.
;VOTING_SPAM 50
:Voting spam protection. This is new in 0.2.8 and is intended to prevent people from filling the server with polls and annoying everybody.
;MIN_VOTERS 3
:Number of voters that need to be online to enable voting. So it's a quorum threshold.

==== Voting Simulation Settings ====

You won't normally need to adjust these, but if you want to make votes happen quicker or something, you'll change these.

;VOTING_TIMEOUT 300
:Number of seconds before a vote times out. A vote will time out if nobody votes either way and action will not be taken.
;VOTING_START_DECAY 60
:Number of seconds after that the non-voters start to get ignored
;VOTING_DECAY 60
:One non-voter is ignored everytime this many seconds pass
;VOTING_SPAM_ISSUE 1.0
:The spam level of issuing a vote.
;VOTING_SPAM_REJECT 5.0
:The spam level of getting your vote rejected.

=== Firewall ===

Installing a firewall is a big job, potentially. There are firewalls that are really rockin' and do all sorts of stuff, and there are firewalls that don't rock. In order to use a firewall to deal with unruly players, you'll need one that supports some sort of IP-based filtering, such as iptables in Linux. In that case, banning a player is a matter of figuring out their IP address and adding it to your firewall.

The most basic way of banning an evil doer is to just drop UDP packets from their IP address that are going to port 4534 (or whatever port your server runs on). For many admins, this is not only a complicated rule to write, but ineffective to deal with the player, so you'll probably find it better to just ban the IP address completely. Be warned, however, that a common way around this is for the evil doer to just turn off their cable modem (or dsl router) and turn it back on. The good news is that it's more inconvenient to them to do that than it is for you to add their new IP address to your firewall. :) The bad news is that this isn't a foolproof method of banning a user.

To help you, Armagetron Advanced supports some additional logging, listed here.

;CONSOLE_DECORATE_ID 1
:Decorates every line of console output with the client ID
;CONSOLE_DECORATE_IP 0
:Decorates every line of console output with the client IP

There is more good news, actually. Many consumer-grade NAT routers come with built-in firewalls or at least make available a firewall option, and will do the job for you--from a web browser! If you have such a beast, you should use it and save your players the hit of the evil-doers packets making another hop down the wire before being cut off.

== Going further - Game Variations ==

There are a number of combinations of settings that make for interesting variations of the game. Here you will find more information on what you can and can't do.

{{:Game Variations}}

[[Category:Server/config]]

Advanced Server Administration Guide

2005-11-23T07:04:54Z

Adam1213:

Mazing

2005-11-23T07:02:22Z

Adam1213:

== What is it? ==

Mazing is a game played by one or more players. The player(s) create designs with their wall and then enter back into the maze. When the player reaches the ''end'' of the maze he turns around and navigates back out. On servers with finite wall lengths a player may make a maze, enter it, and exit it ad infinitum. More complex designs are more difficult to create and navigate.

== Designs ==

=== Square ===
The most basic design you can make to maze is a square. Create a boundary square large enough for you to make revolutions inside. Instead of closing off this boundary square enter it, leaving enough room to exit out. When you reach the center turn around and exit the maze.

[[Image:Square_maze_completed.png|center|thumbnail|A completed square maze]]

=== Inside Out ===

Some players create an ''inside out'' maze by spiraling out from their spawn position, and then enter into the maze. This maze will only work at the beginning of rounds, or when a hole is created in your wall.

(needs image)

=== Dented Box ===
[[Image:Dented_box_maze_inside.png|center|thumbnail|A player inside a dented box maze]]

=== Cross ===
[[Image:Cross_maze_inside.png|center|thumbnail|A player inside a cross maze]]

[[Category:Tactics]]
[[Category:Game Play]]

Console Commands

2005-11-23T07:01:02Z

Adam1213:

== List of Commands ==

This list was generated by starting Armagetron Advanced version 0.2.8_beta3 with the <code>--doc</code> option and using vim to turn it into a table.

{| border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#F9F9F9; font-size:95%; empty-cells:show;"
! Command
! Meaning
|-
| ADMIN_PASS || Password for the basic in game admin
|-
| AI_IQ || IQ of the AI opponents
|-
| ALLOW_CAM_1_0 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_1_1 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_1_2 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_1_3 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_1_4 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_1_5 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_1_6 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_2_0 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_2_1 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_2_2 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_2_3 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_2_4 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_2_5 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_2_6 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_3_0 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_3_1 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_3_2 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_3_3 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_3_4 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_3_5 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_3_6 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_4_0 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_4_1 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_4_2 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_4_3 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_4_4 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_4_5 || Allow/forbid the different camera modes
|-
| ALLOW_CAM_4_6 || Allow/forbid the different camera modes
|-
| ALLOW_ENEMIES_SAME_CLIENT || If set to 1, this allows two players that play on the same client to fight for points with each other.
|-
| ALLOW_ENEMIES_SAME_IP || If set to 1, this allows two players that apparently come from the same machine to fight for points with each other.
|-
| ALLOW_TEAM_NAME_COLOR || Allow a team to be named after a color
|-
| ALLOW_TEAM_NAME_PLAYER || Allow a team to be named after the leading player
|-
| ALLOW_VOTING || If set to 1, voting will be allowed for players.
|-
| ALLOW_VOTING_SPECTATOR || If set to 1, voting will be allowed for spectators.
|-
| ALPHA_BLEND || Enable alpha blending
|-
| ARENA_AXES || arena_axes_help
|-
| ARENA_AXES_OVERRIDE || arena_axes_override_help
|-
| ARMAGETRON_LAST_SCREENMODE || Last screen resolution
|-
| ARMAGETRON_LAST_SCREENMODE_H || armagetron_last_screenmode_h_help
|-
| ARMAGETRON_LAST_SCREENMODE_W || armagetron_last_screenmode_w_help
|-
| ARMAGETRON_LAST_WINDOWSIZE || Last Window size
|-
| ARMAGETRON_LAST_WINDOWSIZE_H || armagetron_last_windowsize_h_help
|-
| ARMAGETRON_LAST_WINDOWSIZE_W || armagetron_last_windowsize_w_help
|-
| ARMAGETRON_SCREENMODE || Screen resolution
|-
| ARMAGETRON_SCREENMODE_H || armagetron_screenmode_h_help
|-
| ARMAGETRON_SCREENMODE_W || armagetron_screenmode_w_help
|-
| ARMAGETRON_WINDOWSIZE || Window size
|-
| ARMAGETRON_WINDOWSIZE_H || armagetron_windowsize_h_help
|-
| ARMAGETRON_WINDOWSIZE_W || armagetron_windowsize_w_help
|-
| AUTO_AIS || Automatically spawn AI players?
|-
| AUTO_INCAM_1 || Automatically switch to internal camera in a maze
|-
| AUTO_INCAM_2 || Automatically switch to internal camera in a maze
|-
| AUTO_INCAM_3 || Automatically switch to internal camera in a maze
|-
| AUTO_INCAM_4 || Automatically switch to internal camera in a maze
|-
| AUTO_IQ || Automatically adjust AI IQ?
|-
| BACKWARD_COMPATIBILITY || Maximum number of old protocol versions to support.
|-
| BAN || Bans the specified player from the server (kicks him first) for a variable time in minutes.
|-
| BAN_IP || Bans the spedified IP address from the server for a variable time.
|-
| BAN_LIST || Prints a list of currently banned IPs.
|-
| BIG_BROTHER || Did we already send the big brother information?
|-
| BOOKMARK_10_ADDRESS || bookmark_10_address_help
|-
| BOOKMARK_10_NAME || bookmark_10_name_help
|-
| BOOKMARK_10_PORT || bookmark_10_port_help
|-
| BOOKMARK_1_ADDRESS || bookmark_1_address_help
|-
| BOOKMARK_1_NAME || bookmark_1_name_help
|-
| BOOKMARK_1_PORT || bookmark_1_port_help
|-
| BOOKMARK_2_ADDRESS || bookmark_2_address_help
|-
| BOOKMARK_2_NAME || bookmark_2_name_help
|-
| BOOKMARK_2_PORT || bookmark_2_port_help
|-
| BOOKMARK_3_ADDRESS || bookmark_3_address_help
|-
| BOOKMARK_3_NAME || bookmark_3_name_help
|-
| BOOKMARK_3_PORT || bookmark_3_port_help
|-
| BOOKMARK_4_ADDRESS || bookmark_4_address_help
|-
| BOOKMARK_4_NAME || bookmark_4_name_help
|-
| BOOKMARK_4_PORT || bookmark_4_port_help
|-
| BOOKMARK_5_ADDRESS || bookmark_5_address_help
|-
| BOOKMARK_5_NAME || bookmark_5_name_help
|-
| BOOKMARK_5_PORT || bookmark_5_port_help
|-
| BOOKMARK_6_ADDRESS || bookmark_6_address_help
|-
| BOOKMARK_6_NAME || bookmark_6_name_help
|-
| BOOKMARK_6_PORT || bookmark_6_port_help
|-
| BOOKMARK_7_ADDRESS || bookmark_7_address_help
|-
| BOOKMARK_7_NAME || bookmark_7_name_help
|-
| BOOKMARK_7_PORT || bookmark_7_port_help
|-
| BOOKMARK_8_ADDRESS || bookmark_8_address_help
|-
| BOOKMARK_8_NAME || bookmark_8_name_help
|-
| BOOKMARK_8_PORT || bookmark_8_port_help
|-
| BOOKMARK_9_ADDRESS || bookmark_9_address_help
|-
| BOOKMARK_9_NAME || bookmark_9_name_help
|-
| BOOKMARK_9_PORT || bookmark_9_port_help
|-
| BRAKE_GAUGE_LOCX || brake_gauge_locx_help
|-
| BRAKE_GAUGE_LOCY || brake_gauge_locy_help
|-
| BRAKE_GAUGE_SIZE || brake_gauge_size_help
|-
| BROWSER_CONTACTLOSS || browser_contactloss_help
|-
| BROWSER_NUM_QUERIES || browser_num_queries_help
|-
| BROWSER_QUERIES_SIMULTANEOUS || browser_queries_simultaneous_help
|-
| BROWSER_QUERY_DELAY_GLOBAL || browser_query_delay_global_help
|-
| BROWSER_QUERY_DELAY_SINGLE || browser_query_delay_single_help
|-
| BROWSER_QUERY_FILTER || browser_query_filter_help
|-
| BUG_RIP || bug_rip_help
|-
| BUG_TRANSPARENCY || Unsupported: make all rim walls semi-transparent by rendering them without occlusion tests
|-
| BUG_TRANSPARENCY_DEMAND || Unsupported: use transparency instead of lowering walls
|-
| BUG_TUNNEL || bug_tunnel_help
|-
| CAMCENTER_1 || Center internal camera on driving direction
|-
| CAMCENTER_2 || Center internal camera on driving direction
|-
| CAMCENTER_3 || Center internal camera on driving direction
|-
| CAMCENTER_4 || Center internal camera on driving direction
|-
| CAMERA_CUSTOM_BACK || Position of the custom camera: how much is it moved back from the cycle?
|-
| CAMERA_CUSTOM_PITCH || Position of the custom camera: how much does it look up/down?
|-
| CAMERA_CUSTOM_RISE || Position of the custom camera: how much is it moved up from the cycle?
|-
| CAMERA_FOLLOW_START_X || Start position of the fixed external camera
|-
| CAMERA_FOLLOW_START_Y || Start position of the fixed external camera
|-
| CAMERA_FOLLOW_START_Z || Start position of the fixed external camera
|-
| CAMERA_FORBID_CUSTOM || Forbids the use of the custom camera on all clients
|-
| CAMERA_FORBID_FOLLOW || Forbids the use of the fixed external camera on all clients
|-
| CAMERA_FORBID_FREE || Forbids the use of the free camera on all clients
|-
| CAMERA_FORBID_IN || Forbids the use of the internal camera on all clients
|-
| CAMERA_FORBID_SERVER_CUSTOM || camera_forbid_server_custom_help
|-
| CAMERA_FORBID_SMART || Forbids the use of the internal camera on all clients
|-
| CAMERA_FREE_START_X || Start position of the free camera
|-
| CAMERA_FREE_START_Y || Start position of the free camera
|-
| CAMERA_FREE_START_Z || Start position of the free camera
|-
| CAMERA_SERVER_CUSTOM_BACK || Position of the custom camera: how much is it moved back from the cycle?
|-
| CAMERA_SERVER_CUSTOM_PITCH || Position of the custom camera: how much does it look up/down?
|-
| CAMERA_SERVER_CUSTOM_RISE || Position of the custom camera: how much is it moved up from the cycle?
|-
| CAMERA_SMART_GLANCE_CUSTOM || use custom camera settings when glancing with the smart camera
|-
| CAMERA_SMART_START_X || Start position of the smart camera
|-
| CAMERA_SMART_START_Y || Start position of the smart camera
|-
| CAMERA_SMART_START_Z || Start position of the smart camera
|-
| CAMERA_VISIBILITY_CLIP_SPEED || Speed with wich the visibility targets is brought into view
|-
| CAMERA_VISIBILITY_EXTENSION || Distance (measured in seconds, gets multiplied by speed) of the visibility targets from the watched object
|-
| CAMERA_VISIBILITY_LOWER_WALL || If set to 1, walls are lowerd when they block the view and the camera is not moved
|-
| CAMERA_VISIBILITY_LOWER_WALL_SMART || Like CAMERA_VISIBILITY_LOWER_WALL, but special setting for the smart camera
|-
| CAMERA_VISIBILITY_RECOVERY_SPEED || The speed the external visibility targets recovers from wall hits
|-
| CAMERA_VISIBILITY_SIDESKEW || Extra forward component of the sideways visibility targets
|-
| CAMERA_VISIBILITY_WALL_DISTANCE || The distance the visibility targets keep from walls
|-
| CAMWOBBLE_1 || Lets the internal camera move with your cycle
|-
| CAMWOBBLE_2 || Lets the internal camera move with your cycle
|-
| CAMWOBBLE_3 || Lets the internal camera move with your cycle
|-
| CAMWOBBLE_4 || Lets the internal camera move with your cycle
|-
| CENTER_MESSAGE || Prints a big message on the screen of all connected clients.
|-
| CHECK_ERRORS || Listen to errors claiming a video mode does not exist
|-
| CLIENT_PORT || Port we try to connect to
|-
| CM_LOCY || cm_locy_help
|-
| COLORDEPTH || Color depth to use (0: 16 1: desktop 2: 24)
|-
| COLOR_B_1 || Cycle and wall color, blue component.
|-
| COLOR_B_2 || Cycle and wall color, blue component.
|-
| COLOR_B_3 || Cycle and wall color, blue component.
|-
| COLOR_B_4 || Cycle and wall color, blue component.
|-
| COLOR_G_1 || Cycle and wall color, green component.
|-
| COLOR_G_2 || Cycle and wall color, green component.
|-
| COLOR_G_3 || Cycle and wall color, green component.
|-
| COLOR_G_4 || Cycle and wall color, green component.
|-
| COLOR_R_1 || Cycle and wall color, red component.
|-
| COLOR_R_2 || Cycle and wall color, red component.
|-
| COLOR_R_3 || Cycle and wall color, red component.
|-
| COLOR_R_4 || Cycle and wall color, red component.
|-
| COLOR_STRINGS || Print colored strings
|-
| CONSOLE_MESSAGE || Prints a message on the console of all connected clients.
|-
| CUSTOM_SCREEN_ASPECT || Custom screen aspect ratio ( pixel width/pixel height)
|-
| CUSTOM_SCREEN_HEIGHT || Custom screen size
|-
| CUSTOM_SCREEN_WIDTH || Custom screen size
|-
| CUSTOM_SERVER_NAME || Name of the server to connect to
|-
| CYCLE_ACCEL || Wall acceleration factor
|-
| CYCLE_ACCEL_ENEMY || Multiplicator to CYCLE_ACCEL for your enemies' walls
|-
| CYCLE_ACCEL_ENEMY_OVERRIDE || cycle_accel_enemy_override_help
|-
| CYCLE_ACCEL_OFFSET || Minimum numeric wall distance, must be positive
|-
| CYCLE_ACCEL_RIM || Multiplicator to CYCLE_ACCEL for the rim walls
|-
| CYCLE_ACCEL_RIM_OVERRIDE || cycle_accel_rim_override_help
|-
| CYCLE_ACCEL_SELF || Multiplicator to CYCLE_ACCEL for your own wall
|-
| CYCLE_ACCEL_SELF_OVERRIDE || cycle_accel_self_override_help
|-
| CYCLE_ACCEL_SLINGSHOT || Multiplicator to the total effect of CYCLE_ACCEL, if the cycle is between its own wall and another wall
|-
| CYCLE_ACCEL_SLINGSHOT_OVERRIDE || cycle_accel_slingshot_override_help
|-
| CYCLE_ACCEL_TEAM || Multiplicator to CYCLE_ACCEL for your temmates' walls
|-
| CYCLE_ACCEL_TEAM_OVERRIDE || cycle_accel_team_override_help
|-
| CYCLE_AVOID_OLDCLIENT_BAD_SYNC || If set to 1, old clients will not get sync messages in situations that are known to confuse them
|-
| CYCLE_BRAKE || Brake intensity
|-
| CYCLE_BRAKE_DEPLETE || Rate at which the brake reservoir depletes when you are braking
|-
| CYCLE_BRAKE_REFILL || Rate at which the brake reservoir refills when you are not braking
|-
| CYCLE_DELAY || Minimum time between turns (must be greater than 0)
|-
| CYCLE_DELAY_TIMEBASED || Turn delays will be based on the time since the last turn if this is 1 (default) and the distance if this is 0. Intermediate values and values out of these bounds are supported as well.
|-
| CYCLE_DELAY_TIMEBASED_OVERRIDE || cycle_delay_timebased_override_help
|-
| CYCLE_FAIR_ANTILAG || If set to 1, this deactivates the anti lag-sliding code when old clients are connected
|-
| CYCLE_MAX_REFCOUNT || Maximum allowed reference count on cycles before they self destruct. This setting is to protect against performance related DOS attacks.
|-
| CYCLE_PACKETLOSS_TOLERANCE || Cycle death is prevented as long as the player's failure to turn can be explained by the loss of this many network packets. Enabling this allows cheating.
|-
| CYCLE_PING_RUBBER || Additional niceness for high ping players
|-
| CYCLE_RUBBER || Niceness factor to allow you drive really close to a wall
|-
| CYCLE_RUBBER_DELAY || cycle_rubber_delay_help
|-
| CYCLE_RUBBER_DELAY_BONUS || cycle_rubber_delay_bonus_help
|-
| CYCLE_RUBBER_DELAY_BONUS_OVERRIDE || cycle_rubber_delay_bonus_override_help
|-
| CYCLE_RUBBER_DELAY_OVERRIDE || cycle_rubber_delay_override_help
|-
| CYCLE_RUBBER_LEGACY || cycle_rubber_legacy_help
|-
| CYCLE_RUBBER_MALUS_TIME || cycle_rubber_malus_time_help
|-
| CYCLE_RUBBER_MALUS_TURN || cycle_rubber_malus_turn_help
|-
| CYCLE_RUBBER_MALUS_TURN_OVERRIDE || cycle_rubber_malus_turn_override_help
|-
| CYCLE_RUBBER_MINADJUST || When adjusting to or 180ing into a wall, allow going closer by at least this amount (relative to the last distance)
|-
| CYCLE_RUBBER_MINADJUST_OVERRIDE || cycle_rubber_minadjust_override_help
|-
| CYCLE_RUBBER_MINDISTANCE || The minimal distance rubber code keeps you from the wall in front of you
|-
| CYCLE_RUBBER_MINDISTANCE_LEGACY || Extra factor for minimal distance to walls enforced by the rubber code, active when peers with the rip bug are connected
|-
| CYCLE_RUBBER_MINDISTANCE_OVERRIDE || cycle_rubber_mindistance_override_help
|-
| CYCLE_RUBBER_MINDISTANCE_PREPARATION || Timescale in seconds a cycle's last turn time is compared with to determine the effect of CYCLE_RUBBER_MINDISTANCE_UNPREPARED.
|-
| CYCLE_RUBBER_MINDISTANCE_PREPARATION_OVERRIDE || cycle_rubber_mindistance_preparation_override_help
|-
| CYCLE_RUBBER_MINDISTANCE_RATIO || Additional distance to CYCLE_RUBBER_MINDISTANCE for every length unit of the wall you have in front of you
|-
| CYCLE_RUBBER_MINDISTANCE_RATIO_OVERRIDE || cycle_rubber_mindistance_ratio_override_help
|-
| CYCLE_RUBBER_MINDISTANCE_RESERVOIR || Addidional distance if you have an empty rubber meter (gets faded out gradually as you use up all your rubber)
|-
| CYCLE_RUBBER_MINDISTANCE_RESERVOIR_OVERRIDE || cycle_rubber_mindistance_reservoir_override_help
|-
| CYCLE_RUBBER_MINDISTANCE_UNPREPARED || Additional distance for unprepared grinds; it gets applied when the cycle's last turn was just a fraction of a second ago and faded out preparation times larger than CYCLE_RUBBER_MINDISTANCE_PREPARATION.
|-
| CYCLE_RUBBER_MINDISTANCE_UNPREPARED_OVERRIDE || cycle_rubber_mindistance_unprepared_override_help
|-
| CYCLE_RUBBER_SPEED || Logarithmic speed of wall approximation when rubber is in effect (every second, you get closer to the wall by a factor of ~0.4^{this value})
|-
| CYCLE_RUBBER_SPEED_OVERRIDE || cycle_rubber_speed_override_help
|-
| CYCLE_RUBBER_TIME || cycle_rubber_time_help
|-
| CYCLE_RUBBER_TIMEBASED || Rubber usage is based on distance travelled if this is 0 (default) and the time passed if this is 1. Intermediate values and values out of these bounds are supported as well.
|-
| CYCLE_RUBBER_TIMEBASED_OVERRIDE || cycle_rubber_timebased_override_help
|-
| CYCLE_RUBBER_TIME_OVERRIDE || cycle_rubber_time_override_help
|-
| CYCLE_SMOOTH_MIN_SPEED || cycle_smooth_min_speed_help
|-
| CYCLE_SMOOTH_THRESHOLD || Only syncs that differ from your position by less than this amount (measured in speed) will be handled smoothly, bigger differences will be applied instantly.
|-
| CYCLE_SMOOTH_TIME || Timescale for smoothing options. Increasing this will make interpolation smoother, but less accurate. Decreasing it will make network synchronization jumpy.
|-
| CYCLE_SOUND_SPEED || Sound speed divisor
|-
| CYCLE_SPEED || Basic speed of your cycle if you drive straight and not close to walls
|-
| CYCLE_SPEED_DECAY_ABOVE || Rate of cycle speed approaching the value of CYCLE_SPEED from above
|-
| CYCLE_SPEED_DECAY_ABOVE_OVERRIDE || cycle_speed_decay_above_override_help
|-
| CYCLE_SPEED_DECAY_BELOW || Rate of cycle speed approaching the value of CYCLE_SPEED from below
|-
| CYCLE_SPEED_DECAY_BELOW_OVERRIDE || cycle_speed_decay_below_override_help
|-
| CYCLE_START_SPEED || Initial cycle speed
|-
| CYCLE_SYNC_FF || Speed of simulation of the extrapolating sync; decrease for lower CPU load, but higher effective ping
|-
| CYCLE_SYNC_FF_STEPS || Number of extrapolation simulation timesteps each real timestep; increase for better accuracy
|-
| CYCLE_SYNC_INTERVAL_ENEMY || Time in seconds between server-client updates of enemy cycles
|-
| CYCLE_SYNC_INTERVAL_SELF || Time in seconds between server-client updates of enemy cycles owned by the client itself
|-
| CYCLE_TIME_TOLERANCE || Maximum time difference of execution of turns on server and client (for clients that send timing information)
|-
| | || CYCLE_TIME_TOLERANCE_OVERRIDEcycle_time_tolerance_override_help
|-
| CYCLE_TURN_SPEED_FACTOR || cycle_turn_speed_factor_help
|-
| CYCLE_TURN_SPEED_FACTOR_OVERRIDE || cycle_turn_speed_factor_override_help
|-
| CYCLE_WALL_NEAR || Maximum accelerating wall distance
|-
| DEDICATED_IDLE || After running this time (in hours), the dedicated server takes the next chance to quit.
|-
| DITHER || Use dithering
|-
| DOUBLEBIND_TIME || Time in seconds during which no two different keyboard events can trigger the same action
|-
| DOUBLEBIND_TIME_OVERRIDE || doublebind_time_override_help
|-
| ENEMIES_LOCX || enemies_locx_help
|-
| ENEMIES_LOCY || enemies_locy_help
|-
| ENEMIES_SIZE || enemies_size_help
|-
| EXPLOSION || explosion_help
|-
| EXPLOSION_RADIUS || Blast radius of the cycle explosions
|-
| EXTRAPOLATOR_SYNC || extrapolator_sync_help
|-
| FADEOUT_NAME_DELAY || Time the player names are shown. Set to 0 if you don't want to show them at all or -1 if you want to show them always.
|-
| FAILED_ATTEMPTS || Number of failed attemts to initialize graphics mode
|-
| FASTEST_LOCX || fastest_locx_help
|-
| FASTEST_LOCY || fastest_locy_help
|-
| FASTEST_SIZE || fastest_size_help
|-
| FAST_FORWARD_MAXSTEP || Maximum recording time between rendered frames in fast forward mode
|-
| FAST_FORWARD_MAXSTEP_REAL || Maximum real time between rendered frames in fast forward mode
|-
| FAST_FORWARD_MAXSTEP_REL || Maximum fraction of the time left until the end of FF mode between rendered frames
|-
| FAV_NUM_PER_TEAM_PLAYER_1 || The favorite number of players per team for this player
|-
| FAV_NUM_PER_TEAM_PLAYER_2 || The favorite number of players per team for this player
|-
| FAV_NUM_PER_TEAM_PLAYER_3 || The favorite number of players per team for this player
|-
| FAV_NUM_PER_TEAM_PLAYER_4 || The favorite number of players per team for this player
|-
| FINISH_TYPE || What happens when the last human is dead?
|-
| FIRST_USE || Is this the first time you use Armagetron Advanced?
|-
| FLOOR_BLUE || Floor color
|-
| FLOOR_DETAIL || Floor detail settings
|-
| FLOOR_GREEN || Floor color
|-
| FLOOR_MIRROR || Floor mirror mode
|-
| FLOOR_MIRROR_INT || Intensity of the floor mirror effect
|-
| FLOOR_RED || Floor color
|-
| FORTRESS_CONQUEST_DECAY_RATE || fortress_conquest_decay_rate_help
|-
| FORTRESS_CONQUEST_RATE || fortress_conquest_rate_help
|-
| FORTRESS_DEFEND_RATE || fortress_defend_rate_help
|-
| FULLSCREEN || Fullscreen or windowed mode?
|-
| GAMEOBJECT_MOVE_TIMEOUT || gameobject_move_timeout_help
|-
| GAME_TIMEOUT || Base timeout for game state synchronisation; gives appoximately the maximum time between rounds.
|-
| GAME_TYPE || Type of game played
|-
| GL_EXTENSIONS || OpenGL system information
|-
| GL_RENDERER || OpenGL system information
|-
| GL_VENDOR || OpenGL system information
|-
| GL_VERSION || OpenGL system information
|-
| GRID_SIZE || Distance between gridlines
|-
| GRID_SIZE_MOVIEPACK || Distance between gridlines when moviepack is active
|-
| HIGH_RIM || Draw high rim walls
|-
| INCLUDE || Includes the following file
|-
| INFINITY_PLANE || Use infinite points (Does not work properly on most Windows systems)
|-
| INSTANT_CHAT_STRING_1_1 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_1_10 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_1_11 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_1_12 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_1_2 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_1_3 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_1_4 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_1_5 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_1_6 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_1_7 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_1_8 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_1_9 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_2_1 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_2_10 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_2_11 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_2_12 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_2_2 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_2_3 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_2_4 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_2_5 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_2_6 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_2_7 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_2_8 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_2_9 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_3_1 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_3_10 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_3_11 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_3_12 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_3_2 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_3_3 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_3_4 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_3_5 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_3_6 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_3_7 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_3_8 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_3_9 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_4_1 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_4_10 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_4_11 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_4_12 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_4_2 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_4_3 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_4_4 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_4_5 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_4_6 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_4_7 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_4_8 || Instant chat available with hotkeys
|-
| INSTANT_CHAT_STRING_4_9 || Instant chat available with hotkeys
|-
| KEEP_WINDOW_ACTIVE || keep_window_active_help
|-
| KEYBOARD || Keyboard settings
|-
| KICK || Kicks the specified player from the server.
|-
| KILL || kill_help
|-
| LADDER_GAIN_EXTRA || Ping dependent ladder extra score for the winner
|-
| LADDER_LOSE_MIN_ON_LOAD || Minimum of you ladder score lost on each load
|-
| LADDER_LOSE_PERCENT_ON_LOAD || Percentage of your ladder score lost on each load
|-
| LADDER_MIN_BET || Minimum score you put in the ladder pot
|-
| LADDER_PERCENT_BET || Percentage of your score you put in the ladder pot
|-
| LADDER_TAX || Percentage of the ladder pot the IRS takes
|-
| LAG_O_METER || Draw Lag-O-Meter in network play
|-
| LANGUAGE_FIRST || The language Armagetron Advanced will use
|-
| LANGUAGE_SECOND || Fallback language if the first language is not available
|-
| LAST_CHECK_ERRORS || Listen to errors claiming a video mode does not exist, last successful init
|-
| LAST_COLORDEPTH || Color depth, last successful init
|-
| LAST_FULLSCREEN || Fullscreen or windowed mode, last successful init
|-
| LAST_ZDEPTH || z buffer depth, last successful init
|-
| LIMIT_ROUNDS || End the match after this number of rounds
|-
| LIMIT_SCORE || End the match when a player reaches this score
|-
| LIMIT_TIME || End the match after this number of minutes
|-
| LINE_ANTIALIAS || Enable line antialiasing
|-
| LOWER_SKY || Draw lower sky plane
|-
| MAP_FILE || map_file_help
|-
| MAP_FILE_OVERRIDE || map_file_override_help
|-
| MAP_URI || map_uri_help
|-
| MAX_CLIENTS || Maximum number of network clients to accept
|-
| MAX_CLIENTS_SAME_IP_HARD || Maximum number of network clients to accept from the same IP; more logins will be ignored
|-
| MAX_CLIENTS_SAME_IP_SOFT || Maximum number of network clients to accept from the same IP; more logins will get kicked when the server is full
|-
| MAX_IN_RATE || Maximum network input rate
|-
| MAX_OUT_RATE || Maximum network output rate
|-
| MAX_PLAYERS_SAME_IP || maximum number of players from the same IP (note that each client can legally host up to four players)
|-
| MAX_VOTES || The maximum number of total votes that can be active at any given moment.
|-
| MAX_VOTES_PER_VOTER || The maximum number of votes suggested by each voter that can be active at any given moment.
|-
| MESSAGE_OF_DAY_1 || Message sent to clients
|-
| MESSAGE_OF_DAY_2 || Message sent to clients
|-
| MESSAGE_OF_DAY_3 || Message sent to clients
|-
| MESSAGE_OF_DAY_4 || Message sent to clients
|-
| MESSAGE_OF_DAY_5 || Message sent to clients
|-
| MIN_PLAYERS || Minimum number of players
|-
| MIN_VOTERS || Number of voters that need to be online to enable voting.
|-
| MOUSE_GRAB || Grab the mouse pointer, so it can't leave the window
|-
| MOVIEPACK || Use the moviepack if available
|-
| MOVIEPACK_FLOOR_BLUE || Floor color
|-
| MOVIEPACK_FLOOR_GREEN || Floor color
|-
| MOVIEPACK_FLOOR_RED || Floor color
|-
| MOVIEPACK_WALL_STRETCH || The distance of the vertical lines on the moviepack walls
|-
| NAME_TEAM_AFTER_PLAYER_1 || If set, the team is named after the leading player
|-
| NAME_TEAM_AFTER_PLAYER_2 || If set, the team is named after the leading player
|-
| NAME_TEAM_AFTER_PLAYER_3 || If set, the team is named after the leading player
|-
| NAME_TEAM_AFTER_PLAYER_4 || If set, the team is named after the leading player
|-
| NETWORK_AUTOBAN_FACTOR || Autoban players for NETWORK_AUTOBAN_FACTOR * ( kph - NETWORK_AUTOBAN_OFFSET ) minutes when they get kicked; kph is the average number of kicks per hour they get.
|-
| NETWORK_AUTOBAN_MAX_KPH || Maximal value of the kicks per hour; larger values are smoothly clamped.
|-
| NETWORK_AUTOBAN_OFFSET || Autoban players for NETWORK_AUTOBAN_FACTOR * ( kph - NETWORK_AUTOBAN_OFFSET ) minutes when they get kicked; kph is the average number of kicks per hour they get.
|-
| NETWORK_MIN_BAN || When a client's connection is blocked because he's banned, make him banned for at least this many seconds.
|-
| NEW_FEATURE_DELAY || Disable features that only came in during the last X protocol versions.
|-
| NEW_TEAM_ALLOWED || Is it currently allowed to create a new team?
|-
| NUM_AIS || Number of AI players
|-
| PASSWORD || Password setting
|-
| PASSWORD_STORAGE || Determines where your passwords are stored: 1 means on harddisk (dangerous), 0 in memory and -1 means they are not stored at all.
|-
| PERSP_CORRECT || Enable perspective correction
|-
| PING_CHARITY || How much ping are you willing to take over from your opponent?
|-
| PING_LOCX || ping_locx_help
|-
| PING_LOCY || ping_locy_help
|-
| PING_SIZE || ping_size_help
|-
| PLAYERS || players_help
|-
| PLAYER_1 || Player name
|-
| PLAYER_2 || Player name
|-
| PLAYER_3 || Player name
|-
| PLAYER_4 || Player name
|-
| PNG_SCREENSHOT || png_screenshot_help
|-
| POLY_ANTIALIAS || Enable polygon antialiasing
|-
| PREDICT_OBJECTS || predict cycle movement in network play
|-
| REAL_ARENA_SIZE_FACTOR || The currently active arena size. Leave it alone! Change size_factor instead.
|-
| REAL_CYCLE_SPEED_FACTOR || The currently active cycle speed multiplier. Leave it alone! Change speed_factor instead.
|-
| RECORDING_DEBUGLEVEL || Level of additonal information in recording file.
|-
| RESOURCE_REPOSITORY_CLIENT || resource_repository_client_help
|-
| RESOURCE_REPOSITORY_SERVER || resource_repository_server_help
|-
| ROUND_CENTER_MESSAGE || Big message sent to clients after every round
|-
| ROUND_CONSOLE_MESSAGE_1 || Message sent to clients after every round
|-
| ROUND_CONSOLE_MESSAGE_2 || Message sent to clients after every round
|-
| ROUND_CONSOLE_MESSAGE_3 || Message sent to clients after every round
|-
| ROUND_CONSOLE_MESSAGE_4 || Message sent to clients after every round
|-
| ROUND_CONSOLE_MESSAGE_5 || Message sent to clients after every round
|-
| RUBBER_GAUGE_LOCX || rubber_gauge_locx_help
|-
| RUBBER_GAUGE_LOCY || rubber_gauge_locy_help
|-
| RUBBER_GAUGE_SIZE || rubber_gauge_size_help
|-
| SAY || Dedicated server only: let the server administator say something.
|-
| SCORE_DEATHZONE || What you get for hitting the Death Zone
|-
| SCORE_DIE || What you get for dying
|-
| SCORE_KILL || What you get for killing someone
|-
| SCORE_LOCX || score_locx_help
|-
| SCORE_LOCY || score_locy_help
|-
| SCORE_SIZE || score_size_help
|-
| SCORE_SUICIDE || What you get for stupidly dying
|-
| SCORE_WIN || What you get for winning a round
|-
| SERVER_DNS || server_dns_help
|-
| SERVER_IP || server_ip_help
|-
| SERVER_NAME || Name of this server
|-
| SERVER_PORT || Port this server listens on
|-
| SETTING_LEGACY_BEHAVIOR_ANNOYING || Default legacy behavior for settings that only cause minor annoyances on old clients, like enemy cycles stopping for .1 seconds after each turn. Example: CYCLE_RUBBER_MINDISTANCE
|-
| SETTING_LEGACY_BEHAVIOR_BREAKING || Default legacy behavior for settings that absolutely break the client and make play impossible. Example of an affected setting: MAP_FILE
|-
| SETTING_LEGACY_BEHAVIOR_BUMPYDefault || legacy behavior for settings that allow play on old clients in principle, but with severe limitations (cycles bouncing around, player commands not executed on time). Example: CYCLE_DELAY_TIMEBASED
|-
| SETTING_LEGACY_BEHAVIOR_CHEATING || Default legacy behavior for settings where the default behavior could be considered cheating if nondefault was set. Example: DOUBLEBIND_TIME
|-
| SETTING_LEGACY_BEHAVIOR_VISUAL || Default legacy behavior for settings that only affect status displays and visuals, not game physics. Example: CYCLE_RUBBER_* (the client displays the rubber meter, but it's not used for anything)
|-
| SHOW_BRAKE || show_brake_help
|-
| SHOW_ENEMIES || show_enemies_help
|-
| SHOW_FASTEST || show_fastest_help
|-
| SHOW_FPS || Enable fps display
|-
| SHOW_HUD || show_hud_help
|-
| SHOW_OWN_NAME || Should your name be displayed above your cycle on your screen?
|-
| SHOW_PING || show_ping_help
|-
| SHOW_RUBBER || show_rubber_help
|-
| SHOW_SCORE || show_score_help
|-
| SHOW_SPEED || show_speed_help
|-
| SHOW_TIME || show_time_help
|-
| SILENCE_ALL || If set to 1, all chat messages will be omitted.
|-
| SIZE_FACTOR || Arena size modifier
|-
| SKY_WOBBLE || Sky animation
|-
| SMOOTH_SHADING || Enable smooth shading
|-
| SOFTWARE_RENDERER || Is the OpenGL renderer not hadware accelerated?
|-
| SOUND_BUFFER_SHIFT || Buffer size multiplier
|-
| SOUND_QUALITY || Sound quality [0=off, 3=high]
|-
| SOUND_SOURCES || Number of sound sources to be heard at the same time
|-
| SPAM_AUTOKICK || Spam score that causes you to get kicked instantly.
|-
| SPAM_MAXLEN || Maximal length of chat message.
|-
| SPAM_MAXLEN_OVERRIDE || spam_maxlen_override_help
|-
| SPAM_PENALTY || Number of seconds to silence a spammer.
|-
| SPAM_PROTECTION || Harshness of spam protection; determines min delay between chat messages accepted.
|-
| SPAM_PROTECTION_CHAT || Extra factor for SPAM_PROTECTION for chat messages.
|-
| SPAM_PROTECTION_VOTE || Extra factor for SPAM_PROTECTION for votes.
|-
| SPARKS || Draw sparks when going too close to a wall
|-
| SPECTATOR_MODE_1 || Sets spectator mode for this player
|-
| SPECTATOR_MODE_2 || Sets spectator mode for this player
|-
| SPECTATOR_MODE_3 || Sets spectator mode for this player
|-
| SPECTATOR_MODE_4 || Sets spectator mode for this player
|-
| SPEED_FACTOR || Speed modifier for the cycles
|-
| SPEED_GAUGE_LOCX || speed_gauge_locx_help
|-
| SPEED_GAUGE_LOCY || speed_gauge_locy_help
|-
| SPEED_GAUGE_SIZE || speed_gauge_size_help
|-
| SP_AI_IQ || IQ of the AI opponents in single player mode
|-
| SP_AUTO_AIS || Automatically spawn AI players in single player mode?
|-
| SP_AUTO_IQ || Automatically adjust AI IQ in single player mode?
|-
| SP_EXPLOSION_RADIUS || Blast radius of the cycle explosions in single player mode
|-
| SP_FINISH_TYPE || What happens when the last human is dead in single player mode?
|-
| SP_GAME_TYPE || Type of game played in single player mode
|-
| SP_LIMIT_ROUNDS || End the match after this number of rounds in single player mode
|-
| SP_LIMIT_SCORE || End the match when a player reaches this score in single player mode
|-
| SP_LIMIT_TIME || End the match after this number of minutes in single player mode
|-
| SP_MIN_PLAYERS || Minimum number of players in single player mode
|-
| SP_NUM_AIS || Number of AI players in single player mode
|-
| SP_SCORE_WIN || What you get for winning a round in single player mode
|-
| SP_SIZE_FACTOR || Arena size modifier
|-
| SP_SPEED_FACTOR || Speed modifier for the cycles
|-
| SP_TEAMS_MAX || Maximum number of teams in single player mode
|-
| SP_TEAMS_MIN || Minimum number of teams in single player mode
|-
| SP_TEAM_BALANCE_ON_QUIT || Balance teams on player quit in single player mode?
|-
| SP_TEAM_BALANCE_WITH_AIS || Balance teams with AI players in single player mode?
|-
| SP_TEAM_MAX_IMBALANCE || Maximum allowed temporary team imbalance in single player mode
|-
| SP_TEAM_MAX_IMBALANCE_PERM || Maximum allowed permanent team imbalance in single player mode
|-
| SP_TEAM_MAX_PLAYERS || Maximum number of players per team in single player mode
|-
| SP_TEAM_MIN_PLAYERS || Minimum number of players per team in single player mode
|-
| SP_WALLS_LENGTH || Length of the cycle walls in meters; negative values will make the walls infinite.
|-
| SP_WALLS_STAY_UP_DELAY || Number of seconds the walls stay up after a player died; negative values will keep them up forever.
|-
| SP_WIN_ZONE_MIN_LAST_DEATH || Minimum number of seconds since the last death before the instant win zone is activated in single player mode
|-
| SP_WIN_ZONE_MIN_ROUND_TIME || Minimum number of seconds the round has to be going on before the instant win zone is activated in single player mode
|-
| START_CAM_1 || Initial Camera
|-
| START_CAM_2 || Initial Camera
|-
| START_CAM_3 || Initial Camera
|-
| START_CAM_4 || Initial Camera
|-
| START_FOV_1 || Initial field of vision
|-
| START_FOV_2 || Initial field of vision
|-
| START_FOV_3 || Initial field of vision
|-
| START_FOV_4 || Initial field of vision
|-
| START_NEW_MATCH || Initiates a new match
|-
| SWAP_MODE || Determines the commands used to sync graphics and input. 0: do nothing, 1: call glFlush(), 2: call glFinish().
|-
| TALK_TO_MASTER || Announce this server on the internet?
|-
| TEAMS_MAX || Maximum number of teams
|-
| TEAMS_MIN || Minimum number of teams
|-
| TEAM_BALANCE_ON_QUIT || Balance teams on player quit?
|-
| TEAM_BALANCE_WITH_AIS || Balance teams with AI players?
|-
| TEAM_MAX_IMBALANCE || Maximum allowed temporary team imbalance
|-
| TEAM_MAX_IMBALANCE_PERM || Maximum allowed permanent team imbalance
|-
| TEAM_MAX_PLAYERS || Maximum number of players per team
|-
| TEAM_MIN_PLAYERS || Minimum number of players per team
|-
| TEXTURES_HI || Use high color textures
|-
| TEXTURE_MODE_0 || Floor Texture:
|-
| TEXTURE_MODE_1 || Wall Textures:
|-
| TEXTURE_MODE_2 || Object Textures:
|-
| TEXTURE_MODE_3 || Font:
|-
| TEXT_OUT || Enable console text output
|-
| TOPOLOGY_POLICE || The topology police does posteriori checks to determine whether game moves were legal.
|-
| UNBAN_IP || Revokes the ban of the specified IP address.
|-
| UPPER_SKY || Draw upper sky plane
|-
| URL || HTTP URI assiciated with a server
|-
| USE_DISPLAYLISTS || Use display lists for rendering the cycles?
|-
| VIEWPORT_CONF || Viewport configuration; decides how many players can play on this computer
|-
| VIEWPORT_TO_PLAYER_1 || Assign this viewport to a player
|-
| VIEWPORT_TO_PLAYER_2 || Assign this viewport to a player
|-
| VIEWPORT_TO_PLAYER_3 || Assign this viewport to a player
|-
| VIEWPORT_TO_PLAYER_4 || Assign this viewport to a player
|-
| VOTING_BIAS || Add virtual voters that oppose every change.
|-
| VOTING_DECAY || One non-voter is ignored everytime this many secons pass.
|-
| VOTING_KICK_TIME || The minimum time in seconds between two kick votes against the same player.
|-
| VOTING_PRIVACY || Controls logging of voting process. 2: nothing gets logged 1: vote submission is logged for the server admin 0: voting is logged for the server admin -1: vote submission is made public -2: everything is made public
|-
| VOTING_SPAM_ISSUE || The spam level of issuing a vote.
|-
| VOTING_SPAM_REJECT || The spam level of getting your vote rejected.
|-
| VOTING_START_DECAY || Number of seconds after that the non-voters start to get ignored.
|-
| VOTING_TIMEOUT || Votes older than this time out and are rejected.
|-
| WALLS_LENGTH || Length of the cycle walls in meters; negative values will make the walls infinite.
|-
| WALLS_STAY_UP_DELAY || Number of seconds the walls stay up after a player died; negative values will keep them up forever.
|-
| WHITE_SPARKS || white_sparks_help
|-
| WIN_ZONE_DEATHS || A value of 1 turns it into a death zone.
|-
| WIN_ZONE_EXPANSION || Expansion speed of the instant win zone
|-
| WIN_ZONE_INITIAL_SIZE || win_zone_initial_size_help
|-
| WIN_ZONE_MIN_LAST_DEATH || Minimum number of seconds since the last death before the instant win zone is activated
|-
| WIN_ZONE_MIN_ROUND_TIME || Minimum number of seconds the round has to be going on before the instant win zone is activated
|-
| WIN_ZONE_RANDOMNESS || Randomness factor of the initial win zone position. 0 fixes it at the arena center, 1 spreads the zone all over it.
|-
| WRAP_MENU || If set, you leave a menu to the top and reenter it at the bottom.
|-
| ZDEPTH || z buffer depth to use (0: 16 1: from color depth 2: 32)
|-
| ZTRICK || Performance tweak; does not work on most Windows systems
}

[[Category:Game Play]]

Console

2005-11-23T07:00:45Z

Adam1213:

==Console==

Many players ask, "How did you change your name within the game?" or "What is the wall length in this server?"
There is a very easy way of changing your name or cycle color and finding out the settings within the game.
The [[Console]].

=== The Console Button ===
The first step in using the console, is figuring out which button it is bound to it. To bind a new button to the console go to:

1. [[image:console1.jpg|center|thumbnail|system setup]]

2. [[image:console2.jpg|center|thumbnail|Misc Stuff]]

3. [[image:console3.jpg|center|thumbnail|Global Keyboard Configuration]]

4. [[image:console4.jpg|center|thumbnail|Console Input]]

5. Set a button for console input. You are now qualified to tell people that you have ub3rl33t +ron h4x.

=== Using T3h Console ===
The console can be used inside or outside of the grid. So. Press the button. You now see "Con:" where it normally shows "Says:".
You may now type in commands to alter your settings or view server settings.

== Commands of T3h Console ==

If you do not know a command you may input a search word into the console. You will be given a list of commands containing the given word. You may also find a complete list of [[Console Commands]] here.

=== Various Personal Settings ===

Player_1 xXx
This would change your name to xXx.

----

color_g_1 n
color_r_1 n
color_b_1 n

Replace n with a number. Any number. Put red at 16 and blue and 4 and green at 0 for example. It's best to figure out the combinations yourself.

----

ping_charity n
This setting determines how much of your opponent's you are willing to take over. If you have a slow connection, set it to 0, if you have a fast connection set it to however generous you feel. But keep in mind, the server has a habit of deciding your ping charity for you! So setting this is more like asking the server nicely for something, but usually has no effect.

----

camera_custom_back -- The position of the camera behind the cycle.
camera_custom_pitch -- The angle the camera is at.
camera_custom_rise -- The height of the camera.

The [[Custom Camera]] page can help you decide your settings for the custom camera.

----

Raoul_Duke_Ping 0
This never works, unfortunately.

=== Server Settings Commands ===
cycle_walls_length
cycle_speed
cycle_accel
cycle_brake
cycle_brake_deplete and cycle_brake_refill
cycle_delay
cycle_explosion_radius
cycle_rubber
win_zone_deaths (if set at 1, watch out, it's a kill zone)

Type these commands in the console when:
* You wish to find out the settings of the internet server you are playing in (do not type values after the words).
* You wish to alter your own single player game settings (type values after the words, ex: cycle_speed 30).

There are many other console commands. I do not know all of them. Try typing keywords such as '''cycle''', '''speed''', '''ping''', '''walls''', '''rubber''', or any other setting you can think off.

==0xffoo==
Players can change the color of their text by using oxffoo code.

*Example: Type in, "0xff0000 Hi I am new at using oxffoo" without the quotations marks of course, and use zeroes, not the letter "o".

0xff0000 codes are RGB triplets, just like you would write in html or something. Basically, split it up like this:

0x ff 00 00

The 0x can be ignored. It's required to tell the game you want to use color here, but otherwise you can throw it away and not think about it. The first number is the amount of Red to put in the color. The second is Green, and the third is Blue. Hence the phrase "RGB triplet".

The tricky part is that these numbers aren't in base 10 like your normal counting numbers. They're in base 16. So ff=255. Just think of it as a two digit number where you can choose from numbers 0-f. The counting progression is { 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, a, b, c, d, e, f }. As you can see, "a" is number 10. You don't really need to know much more than that 0xff0000 has more Red than 0xaa0000, and stuff like that.

== External Resources ==
For 0xff00 codes and for bike and trail colors visit [http://www.firstdigital.plus.com/iceman// Iceman's site.]

[[Category:Game Play]]

Player Tricks

2005-11-23T06:59:55Z

Adam1213:

There are a number of things you can do, as a player, to make the game easier, more fun, or to totally thrash yourself. Here are some of them:

== [[Double Binding]] ==

Double Binding is a common technique in which two keys are pressed to turn around quickly.

== [[Custom Camera]] ==

Are you tired of smart cam? Don't like in-cam? Wouldn't you like to have your own cam?

== Camera Glance Keys ==

Use them! By default they are bound to the arrow keys.

== [[Effects and Display]] ==

A Guide to video display and effects.

[[Category:Tactics]]
[[Category:Game Play]]

Fortress

2005-11-23T06:59:17Z

Adam1213:

The fortress game is what is referred to when a map is built around the concept of a fortress zone. A fortress zone is an area that one team is supposed to defend against the other teams, while trying to capture the other teams' zones.

== History ==

Proof of concept of Fortress mode was created by Z-Man, and is still in the works.

== Objective ==

In this mode, your goal is to aquire your oposing teams "zone". To do this there are a number of stratagies.

== Strategies ==

* Use one or more players to defend your base looping around it and generally keeping the other team(s) out.

* If theres more then 3 people on your team and your off to the side try turning off earlier so the guy in the center isn't stuck and will not end up plowing into an enimy wall.

* Try bulldozing through the other teams offence using yourself as a kamikazi, you can blow a hole in the other teams defence and let another player on your team get through easier.

* If the server has the team chat code use it (/team ''secret message here'') using this is helpful for building stratagy and keeping your enemies in the dark.

There is a more detailed discussion of [[Fortress Tactics]] available.

== Settings on the Test Server ==

*Just in case anyone was wondering, the current fortress test server is Z-mans(the games creator).

*Explosions are set to 2 to make blocking a ramrod/plow/steamroll easier.

To conquer a zone you need to follow this guideline
(Attackers are opposing team members inside the defenders zone)
(Defenders spawn inside their zone, they must stay in the zone to count as defending)
*1 attacker, 0 defenders: 5 seconds to conquer.
*1 attacker, 1 or more defenders: not conquerable.
*2 attackers, 0 defenders: 2 seconds to conquer.
*2 attackers, 1 defender: 3.3 seconds to conquer.
*2 attackers, 2 defenders: 10 seconds to conquer.

reference - http://forums.armagetronad.net/viewtopic.php?t=2529&postdays=0&postorder=asc&start=0

== Screen shots ==

TODO

[[Category:Game Play]]

Fortress Tactics defense

2005-11-23T06:58:42Z

Adam1213:

{{:Fortress Tactics_defense_intro}}

== Skills ==

The skills a defender needs will vary according to his role, but generally speaking a defender should be able to:

* Maze indefinitely in a confined area
* Fight and win in a confined area
* Follow his tail indefinitely
* Play a zone defense (as in soccer or any other sport)
* Play a man-to-man defense
* Switch smoothly between zone and man-to-man tactics

== Defensive Roles ==

Typically, on a 7 person team, the inner three players are the offense and the remaining 4 players are the defense. But what does each defensive player do, exactly? Well, simply put, each defender should do what he does best. A defender who is a good fighter should take up a position well away from the fortress and wait for opponents to arrive, at which point he should kill any opponents that come near him. All defenders need to be alert of one another's positions and what's going on in each position so that they can lend assistance. For example, if the right-hand guard is being attacked by three opponents, and the left-hand guard has no opponents, then the left-hand guard should shift to the right and help contain the opponents.

It's not necessary for defenders to kill opponents. While it is the defense's primary method of scoring points for their team, strictly speaking it is only necessary to deny access to the fortress. Because of this nuance in the role of the defense, a defender does not have to be a better fighter in order to fend off the offense. If a defender can just put up a wall and maintain it so that the offense can't get by him, then he has done his job.

Depending on how the defense has decided to organize, each individual will have a different role. Each method of defense is assumed to have at least 2 defenders, and scales up to 4 defenders with very little modification. The important thing to remember is that extra defenders should deploy to the flanks to cover the avenues of defense.

=== Zone Defender ===

A zone defender will stake some part of the grid as his own and prevent any player from passing. His purpose isn't necessarily to attack and kill every opponent that comes his way, rather it's to prevent the attackers from passing. Sometimes, more often than not, it's easiest and best to kill the attacker. Occasionally, however, it's best to just deny access. The defender may choose this tactic instead if, for example, the attacker is a much stronger fighter than the defender. In that case, the defender could do a better job by repelling the attacker instead of killing.

Zone defense is like most sports and is a common tactic found in soccer, basketball, American football, rugby, and numerous other sports. By default, baseball is all zone defense.

=== Goalie ===

While most people refer to the goalie as simply "defense" or "defender", we use goalie here to differentiate between the larger defensive team. The goalie is a zone defender with the team's fortress as his zone. As such, his tactics and methods vary dramatically from the typical zone defender and center around mazing and chasing his tail.

=== Guard ===

Guards are the players that don't directly defend the fortress. Instead they take up positions away from the fortress that are chosen as good places to stand and wait for attackers which they can then engage when they arrive. A defense may have many guards, or none, depending on the size of the team. When the back of the grid starts to get fairly congested with defenders, some defenders may choose to take positions in the middle part of the grid instead. In any case, the guards will deploy early in the round after grinding to the center and make sure they leave room for the goalie to setup his maze. They will also try to keep attackers from penetrating while the goalie is still setting up.

== Organizing the Defense ==

The defense organizes separately from the offense. Obviously this is because the offense has no idea what the defense is doing, and there's no reason it needs to know and vice versa. On a large team that has 3-4 defenders, one of them needs to take charge of the defense. On a smaller team, the team captain can probably give some direction to the defense.

=== Zone Defense ===

In the zone defense, there is no goalie. While it is generally accepted that a goalie is needed, it is difficult to field an offense against a team that outnumbers yours. In this case, if the players are all strong players, they may elect to field a zone defense of 2 players and send the other player or players off to storm the other team's fortress. The team may also elect to have a goalie and play all players as zone defenders until they have whittled away the opponent's forces, clearing an opening to storm the opponent's fortress.

However, the zone defense is a very risky strategy. It requires that all defenders be capable of holding their zones, and usually only one defender will be close enough to the fortress that he can drop back and defend it directly. It also requires that no players can make any mistakes that results in death. This is a big deal, because if the right-hand defender should screw up and crash, there aren't any defenders able to take over his zone to compensate and the opponent's offense will storm right through. Obviously, this is a defensive strategy to be used sparingly and with great care and consideration of your team's capabilities. If your team composition lends itself to it, this defense is very difficult to break. But the risk is high, so consider yourself warned.

=== Inner/Outer Defense ===

The Inner/Outer Defense strategy has two goalies. One goalie mazes inside the other, and both cover the zone. There are numerous advantages to recommend this defense over most others available. If you have a player who is fairly weak and needs practice, you can place him as one of the two goalies to gain experience as a defender. When the opposing offense arrives at the fortress, they will have to penetrate two defensive walls to take the fortress. Moreover, if an opponent manages to get into a zone, there is backup readily available. The outer defender can easily switch to inner defense if the inner defender should fall, and vice versa, although it doesn't usually make sense to take outer defense and leave no inner defender.

=== Guard Defense ===

[[Image:defensivezones.png|thumb|right|Guard Defense Diagram]]

The guard defense only has one goalie. Instead of an outer defender, the second defender will take up a guard position in front of the fortress. From there he can lend aid to either side, switch to play an outer defense and run an inner/outer defense, and/or take over for the goalie should the goalie crash. This is a good defensive strategy to adopt when you have one really good goalie and a player who is normally an offensive player because it allows the offensive player to play offensively while defending the fortress. It requires stronger players than the inner/outer defense strategy and carries some of the risk of the zone defense strategy.

== Defensive Avenues ==

Defense revolves around making sure there is a defender in a place where an opponent is going to be to prevent that opponent from reaching the defender's fortress. While the offense has avenues of attack, the defense has avenues of defense. There are three main areas through which an opponent is likely to arrive, and each of those areas will usually develop paths through which an opponent will come. The paths themselves are very dynamic, so it is very important for a defender to watch the action in the middle and far side of the grid and constantly assess what paths an attacker will follow to reach the fortress. By doing so, the defender can move to close the defensive avenues and deny access to an area that is much larger than the fortress itself. For more information, defenders should read the [[Fortress Tactics_offense|offense page]].

[[Category:Tactics]]
[[Category:Game Play]]

Fortress Tactics offense intro

2005-11-23T06:58:28Z

Adam1213:

Offense is relatively simple. The two players who will usually rush the opposing fortress are the point and the person to the right of point. The person to the left of point can rush, but usually doesn't get to do so right away. So the two rushers need to account for at least one opponent between them, two is preferred, on their way to the zone. If they don't even get one, they need to double back and go pick one off. The reason is simple, there's probably one goalie at the zone, and if they don't kill anyone on their way, they leave their defense outnumbered.

The left of point is usually an offensive position as well, but his is a little unique from the rest. He has to take out one opponent before he can rush the zone, and it's this fact that usually causes him to show up after the other two. It's not a big deal because three players at the enemy's fortress wind up killing each other in their rush for the zone. So left of point is usually better off playing a forward defensive position until it's time to go to the zone. When he goes to the zone, his best bet is usually to prevent opponents from returning to protect the zone and buying time for the two rushers (who should already be there) to take the zone. In either capacity, he's playing a defensive role, but he's playing it in offensive positions.

All other players are defensive players until the opposing team has been reduced to a point where it's safe to leave the goalie by himself.

[[Category:Tactics]]
[[Category:Game Play]]

Fortress Tactics defense intro

2005-11-23T06:58:15Z

Adam1213:

Defense is also relatively simple. There are currently two defensive models in use. The dominant one is the inner/outer defense model. Put simply, one person follows his tail immediately inside his team's fortress, creating a barrier to entering the zone. The other person will create a similar barrier farther out, usually touching the rim wall in his circuit. The inside player, the goalie, is the inner defense. The outside player's position has no name, other than outer defense.

The second model is a goalie/guard model like that used in soccer. It has some advantages over the inner/outer defense model, but some disadvantages as well. In this model, you have a goalie that plays just like the inner defense already mentioned. The second player takes up a guard position in front of the goalie and works his area like a zone defense. In this model he will hunt anyone who comes to his side of the grid.

The tradeoffs are huge. In the inner/outer defense model, the inner player doesn't have to be particularly strong if the outer player is strong. The converse is also true. So if you have new players, or just players who are new to fortress play, the inner/outer defense model is very effective. The goalie/guard model requires both players to be strong players, and the guard has to be a strong dueling player. The advantage to the goalie/guard model is that the guard can switch easily to offense if his offensive players should crumble. He can also easily switch to take a winzone, should one appear. He can also switch to outer defense on the fly if need be. Obviously this requires a lot more skill and experience on the part of the guard. In the end, let the goalie make the call on which he prefers. The best defense he can set up is the one he can play best, regardless of what the tradeoffs are.

The other defensive players will deploy early in the round and take up what are essentially zone defenses. If the offense deploys well, the defensive line will only receive 2 or 3 players, but it needs to be ready to take 5, and there's only 4 defensive players at the most. The mission of the defense, combined, is to deny the rear part of the grid to the other team. This is a larger area than the fortress itself, and it makes sense. If an opposing player can get into the area of denial, he can prevent defensive players from coming to peel him out. But if the defense can deny the whole area to him, they keep him off the goalie's back.

Depending on the strength of the defense and the skills and experience of each player, as a defensive player you may be able to let 1 or 2 opposing players get by in order to get 1 or 2 others.

[[Category:Tactics]]
[[Category:Game Play]]

Fortress Tactics offense

2005-11-23T06:58:03Z

Adam1213:

{{:Fortress Tactics_offense_intro}}

== Offensive Roles ==

On a 7 person team, you will have 3 offensive players. The number of offensive players generally starts at 2 because 2 are required to take the opponent's fortress. The role of the offense is pretty simple. Rush the opposing team's fortress, and on the way take out 1-2 of the opposing team members. Depending on how the line separates, each player will have a slightly different role.

=== Center ===

The center has all the responsibility, so choose your center wisely. He has to come up with a way for the line to split without killing everybody, usually by making a call of some sort. After the line splits, he will be the fastest player on his team, typically, and you'll want him to take advantage of the speed to get as close to the opposing fortress as possible.

Which direction he turns is going to depend on a number of things. If the line splits early, he can turn left. If the line splits late, he must turn right, because there's an opposing wall on his left.

==== The Responsibility of the Center ====

This is a very important role in the offense. The center really needs to be in tactical command of the team, so if your center isn't in tactical command, you need to get rid of him. Since the server chooses who goes in what positions, you might need to take drastic measures to get rid of the guy. Since he's an offensive player, he needs to be making calls to tell the offense when to attack, when to pull back, and so forth. He's also the player who will get killed in the first 5 seconds of play if he doesn't do something to split up the line, so he has the most to lose by not taking his role seriously.

On your team, it may not make sense to actually give tactical command to the center. In that case, if your team captain isn't close enough to the center to split the line properly, the center will still need to make the appropriate call to split the line. So he doesn't have to be in tactical command of the team to split the line, but in that case he needs to respect the team captain's wishes about splitting the line.

=== Offensive Guards ===

I call the other two offensive players "guards" for lack of a better word, and the term is borrowed from basketball. These are the players immediately to the left and right of the center. Their individual roles will vary depending on how the line breaks. If the line breaks early, then they each need to account for one opponent before rushing the zone. If the line breaks late, then the guard on the right and the center together need to account for one opponent before rushing the zone and the guard on the left must account for one opponent before rushing the zone.

If the offense doesn't account for any opponents, then their defense is likely to be overwhelmed. In that case, and regardless of that fact, they need to take the opposing team's fortress as quickly as possible. It goes without saying that they need to take the opposing team's fortress before their own defense falls.

== Rushing the Fortress ==

Rushing the fortress only takes one offensive player, but the player that gets there first needs to decide quickly if he can take it by himself. If not, then he needs to wait for assistance before proceeding. There are plenty of tactics that work when taking a fortress, but not all of them work against the same people. The only rule that seems to hold true is that two attackers can take a fortress, but three can't. So when the third attacker arrives, he needs to hold back and be prepared to lend assistance while playing a rear guard position in case the opponent's team arrives to help defend.

[[Category:Tactics]]
[[Category:Game Play]]

User:Adam1213

2005-11-23T06:48:22Z

Adam1213:

====<big><big><big><big><big>[http://en.wikipedia.org/wiki/User:Adam1213 My user page on wikipedia]</big></big></big></big></big>'''====

Settings I like to use for a game: 
cycle_speed 2 
cycle_brake -200 
cycle_rubber 100 
and trail length of 400

links
[[Special:Specialpages]]

User:Adam1213

2005-11-23T06:47:12Z

Adam1213:

User talk:Adam1213

2005-11-23T06:43:40Z

Adam1213:

====<big><big><big><big><big>[http://en.wikipedia.org/wiki/User_talk:Adam1213 My talk page on wikipedia]</big></big></big></big></big>'''====

User:Adam1213

2005-11-23T06:42:06Z

Adam1213:

====<big><big><big><big><big>[http://en.wikipedia.org/wiki/User:Adam1213 My user page on wikipedia]</big></big></big></big></big>'''====

User:Adam1213

2005-11-23T06:41:36Z

Adam1213:

====<big><big><big><big><big><bhttp://en.wikipedia.org/wiki/User:Adam1213 My user page on wikipedia]</big></big></big></big></big>'''====

User:Adam1213

2005-11-23T06:41:07Z

Adam1213:

====<big><big><big><big><big>[[wikipedia:User:Adam1213|My user page on wikipedia]]</big></big></big></big></big>'''====