Configuration

• Game (start and setup a game)
• Local Game (Starts a local game)
• Network Game (Connects to or creates a network game)
• Game Setup (Sets your favourite single player game mode: number of AI opponents)
• Player Setup (Player customisation: keyboard input, camera setup, multiplayer mode on one computer)
• Player 1-4 (the settings for this player)
• Input Configuration (keyboard and mouse setup)
• Camera Input Configuration (keyboard and mouse setup for camera controls)
• Camera Setup (camera mode options)
• Instant Chat (things you can say with one keystroke)
• Assign Viewports To Players (which player sees himself on which part of the screen)
• System Setup (Configure sound)
• Display Settings (screen resolution and graphic details/preferences)
• Screen Mode (resolution and windowed/fullscreen selection)
• Preferences (things that depend more on your personal taste)
• Detail Settings (things that affect visual quality and depend on your system's OpenGL power)
• Performance Tweaks (settings that increase graphics speed, but may not work on your system)
• Sound Settings (sound quality)
• Misc Stuff (things that did not fit anywhere else: Moviepack, console text output, menu wrap option and global keyboard configuration)
• Global Keyboard Configuration (keyboard setup for player-independent functions (console, scores))
• Language settings (Choose the language of Armagetron here)

Some of the new and maybe less obvious game settings in "Game Setup" available since version 0.2 are explained here:

• The AIs come in various intelligence grades. Select it in the "AI IQ" menu item.
• Explosions can blow away walls. Select in "Blast Radius" how much destruction they bring.
• Cycle walls can be of finite length ( a la snake ). Choose in "Wall Length" how long they should be.
• The delay between the a cycle explosion and the disappearing of its wall can be configured in "Wall Delay".
• Arena size and overall game speed can be adjusted in "Arena Size" and "Speed". Note that the setting here is logarithmic; that means that by increasing the value by 2, you double the arena size/game speed. by increasing the value by 6, you multiply the size/speed by a factor of 8.

• Limits on the number of teams and the number of players per team can be set in the "Min/Max teams/players per team" settings.
• You can control team ballance with the "Max imbalance" and "Ballance with AIs" settings.

The game is too slow for you? Then take a look at the files settings.cfg and settings_dedicated.cfg for the dedicated server (best save all your changes to autoexec.cfg if you don't want the next release of Armagetron to overwrite them). Play a bit with CYCLE_SPEED and all the other nice variables and see what happens. You can place comments preceeded by #. In a network game, the game physics settings are transferred from the server to the clients. Not all possible setting items are included in these files, you can add everything you find in this document.

The acceleration caused by the wall at distance D is

acceleration=CYCLE_ACCEL / (CYCLE_ACCEL_OFFSET + D)-
             CYCLE_ACCEL / (CYCLE_ACCEL_OFFSET + CYCLE_WALL_NEAR)

The CYCLE_RUBBER setting is a niceness thing, especially useful in an internet game where player prediction is poor: if you hit a wall, you are not directly deleted; you are stopped for a short time and your supply of "rubber" is decreased. If you manage to turn fast enough, you won't die. the rubber supply will slowly increase again (on a timescale of 10 seconds, approximately). CYCLE_RUBBER gives the maximum amount of rubber you have got. Setting it too high (~1000000) will make all cycles (your opponents, too!) immortal, setting it to zero is the way it used to be until version 000518. One is a good value for single player games, 3 .. 10 for network games (the more ping, the higher the setting should be). In the current version, the setting on the clients is in effect, so you can cheat a little bit in network mode if you increase your rubber.

A special feature are the CAMERA_FORBID_* settings; if you think for example that using the free floating camera is cheating, simply set CAMERA_FORBID_FREE to 1 on your server; none of the clients will then be able to use the free camera. (Of course, it is possible for a modified client to cheat at this point, using the forbidden camera perspectives anyway.) Try a match with all but the internal camera disabled :-)

The settings that affect only the visual appearance (FLOOR_* ...) are not transferred; It stays a matter of taste if you want the floor red or yellow.

All the settings you alter permanently in the .cfg-files can be tested temporarily if you enter them at the console. To enter a line to the console, you have to bind a key to it (in "Misc Stuff/Global Keyboard Configuration") and press it, of course. The line you enter will be interpreted just as if it was read from a config file. if you type in an incomplete name, you'll get a list of settings that contain that name. Just typing the name of a setting will print the current value.
If you run a dedicated server, everything you type will be considered console input.

Settings for single player highscore hunt on this server:

SP_SCORE_WIN n	points you gain for being last one alive
SP_LIMIT_ROUNDS n	max number of rounds to play
SP_LIMIT_TIME n	max time (in minutes)
SP_AIS n	number of opponents you will face

Ladder league constants:

LADDER_PERCENT_BET x	percentage of your score to be put in the pot
LADDER_MIN_BET x	minimum credits to be put in the pot
LADDER_TAX x	percentage the IRS takes from the pot
LADDER_LOSE_PERCENT_ON_LOAD x	you loose this percentage of your score every time the server is restarted
LADDER_LOSE_MIN_ON_LOAD x	but minimum this value
LADDER_GAIN_EXTRA x	the winner gets his ping+ping charity (in seconds) times this value extra

A complete list of all available commands is available here.

This document was created by Manuel Moos

Last modification: Tue Oct 14 09:46:43 CEST 2003