Customizing the game - Revision history

Sinewav: /* Cycle Colors */ Replaced the long gone armagetron.co.uk color picker link with Nelg's tool.

2026-04-21T04:58:25Z

Cycle Colors: Replaced the long gone armagetron.co.uk color picker link with Nelg's tool.

← Older revision		Revision as of 23:58, 20 April 2026
Line 162:		Line 162:
	Also check out this useful link for helping you in picking colors:		Also check out this useful link for helping you in picking colors:

	~~http~~://~~armagetron~~.co.uk/~~colours~~/~~colourpicker.php~~		https://www.armanelgtron.tk/tools/cycle/

	==Chat Colors==		==Chat Colors==

Armanelgtron: /* Autoexec.cfg */

2025-07-10T17:37:41Z

Autoexec.cfg

← Older revision		Revision as of 12:37, 10 July 2025
Line 202:		Line 202:
	1. '''Locate the configuration directories.''' Launch Armagetron and select "About" from the main menu. This will list directories where Arma stores/reads data. The configuration directory you want access to is usually in your $HOME folder (this is dependent on your operating system). Open and bookmark/shortcut the configuration directory, you'll probably want to come back here later. On Arma v0.4 and greater the path is “Help” -> “Open Directories” -> “Open User Configuration”.		1. '''Locate the configuration directories.''' Launch Armagetron and select "About" from the main menu. This will list directories where Arma stores/reads data. The configuration directory you want access to is usually in your $HOME folder (this is dependent on your operating system). Open and bookmark/shortcut the configuration directory, you'll probably want to come back here later. On Arma v0.4 and greater the path is “Help” -> “Open Directories” -> “Open User Configuration”.

	2. '''Create or edit autoexec.cfg.''' If this file does not exist, create it. There is nothing special about CFG files, they can be edited with any simple text editor like Notepad on Windows. Armagetron looks for and loads this file when it starts. Any settings you put in there will override default values.		2. '''Create or edit <code>autoexec.cfg</code>.''' If this file does not exist, create it. There is nothing special about CFG files, they can be edited with any simple text editor like Notepad on Windows. Armagetron looks for and loads this file when it starts. Any settings you put in there will override default values.

	3. '''Add your custom settings.''' Some of the most common setting are for Custom Camera (rise, pitch, etc.). You can see a list of these and many, many more on the [[Console_Commands\|Console Commands]] page. Put each setting on it's own line followed by a space, then the value of your choice. Save the file when finished.		3. '''Add your custom settings.''' Some of the most common setting are for Custom Camera (rise, pitch, etc.). You can see a list of these and many, many more on the [[Console_Commands\|Console Commands]] page. Put each setting on it's own line followed by a space, then the value of your choice. Save the file when finished.

Cadillac at 02:27, 23 August 2021

2021-08-23T02:27:50Z

← Older revision		Revision as of 21:27, 22 August 2021
Line 215:		Line 215:
	6. '''Even more advanced usage.''' Configurations can be loaded at any time, not just at start. Maybe you have texture settings and instant chats that are specific to a server such as Fortress. Let's say it's called fortress.cfg. You can enter chat and type: ''/console include fortress.cfg'' to load those settings. To make things easier and faster, set an instant chat key to ''/console include \\'' and type the filename. (Remember, loading custom settings in this way will override others, so you probably want to save your custom default values in autoexec.cfg or make a reset.cfg file to reverse the changes.)		6. '''Even more advanced usage.''' Configurations can be loaded at any time, not just at start. Maybe you have texture settings and instant chats that are specific to a server such as Fortress. Let's say it's called fortress.cfg. You can enter chat and type: ''/console include fortress.cfg'' to load those settings. To make things easier and faster, set an instant chat key to ''/console include \\'' and type the filename. (Remember, loading custom settings in this way will override others, so you probably want to save your custom default values in autoexec.cfg or make a reset.cfg file to reverse the changes.)

	[[Category:~~Client Features~~]]		[[Category:Customization]]

Sinewav: /* Autoexec.cfg */ Added path for v0.4

2020-12-17T19:19:09Z

Autoexec.cfg: Added path for v0.4

← Older revision		Revision as of 14:19, 17 December 2020
Line 200:		Line 200:
	As you can tell from above, Armagetron is insanely customizable. But what if you want to make semi-permanent changes to settings you might type into the [[Console]]? The answer is the autoexec.cfg file. Here is how it use it:		As you can tell from above, Armagetron is insanely customizable. But what if you want to make semi-permanent changes to settings you might type into the [[Console]]? The answer is the autoexec.cfg file. Here is how it use it:

	1. '''Locate the configuration directories.''' Launch Armagetron and select "About" from the main menu. This will list directories where Arma stores/reads data. The configuration directory you want access to is usually in your $HOME folder (this is dependent on your operating system). Open and bookmark/~~shorcut~~ the configuration directory, you'll probably want to come back here later.		1. '''Locate the configuration directories.''' Launch Armagetron and select "About" from the main menu. This will list directories where Arma stores/reads data. The configuration directory you want access to is usually in your $HOME folder (this is dependent on your operating system). Open and bookmark/shortcut the configuration directory, you'll probably want to come back here later. On Arma v0.4 and greater the path is “Help” -> “Open Directories” -> “Open User Configuration”.

	2. '''Create or edit autoexec.cfg.''' If this file does not exist, create it. There is nothing special about CFG files, they can be edited with any simple text editor like Notepad on Windows. Armagetron looks for and loads this file when it starts. Any settings you put in there will override default values.		2. '''Create or edit autoexec.cfg.''' If this file does not exist, create it. There is nothing special about CFG files, they can be edited with any simple text editor like Notepad on Windows. Armagetron looks for and loads this file when it starts. Any settings you put in there will override default values.

	3. '''Add your custom settings.''' Some of the most common setting are for Custom Camera (rise, pitch, etc.). You can see a list of these and many, many more on the [[Console_Commands\|Console Commands]] page Put each setting on it's own line followed by a space, then the value of your choice. Save the file when finished.		3. '''Add your custom settings.''' Some of the most common setting are for Custom Camera (rise, pitch, etc.). You can see a list of these and many, many more on the [[Console_Commands\|Console Commands]] page. Put each setting on it's own line followed by a space, then the value of your choice. Save the file when finished.

	4. '''More settings.''' autoexec.cfg will also override settings in your user.cfg. You can copy instant chats, your player name, even keybindings found in user.cfg to autoexec.cfg and modify them without breaking your user.cfg file.		4. '''More settings.''' autoexec.cfg will also override settings in your user.cfg. You can copy instant chats, your player name, even keybindings found in user.cfg to autoexec.cfg and modify them without breaking your user.cfg file.

Sinewav: /* Autoexec.cfg */ reworded for clarity

2020-12-17T19:16:09Z

Autoexec.cfg: reworded for clarity

← Older revision		Revision as of 14:16, 17 December 2020
Line 213:		Line 213:
	INCLUDE my_cycle.cfg		INCLUDE my_cycle.cfg

	6. '''Even more advanced usage.''' Configurations can be loaded at any time, not just at start. Maybe you have texture settings and instant chats that are specific to a server such as Fortress. Let's say it's called fortress.cfg. You can enter chat and type: ''/console include fortress.cfg'' to load those settings. To make things easier and faster, set an instant chat key to ''/console include \\'' and type the filename. (Remember, loading custom settings in this way ~~overrides~~ others, so you probably want to save your custom default values in autoexec.cfg or make a reset.cfg file ~~you can call at will~~.)		6. '''Even more advanced usage.''' Configurations can be loaded at any time, not just at start. Maybe you have texture settings and instant chats that are specific to a server such as Fortress. Let's say it's called fortress.cfg. You can enter chat and type: ''/console include fortress.cfg'' to load those settings. To make things easier and faster, set an instant chat key to ''/console include \\'' and type the filename. (Remember, loading custom settings in this way will override others, so you probably want to save your custom default values in autoexec.cfg or make a reset.cfg file to reverse the changes.)

	[[Category:Client Features]]		[[Category:Client Features]]

Sinewav: /* Autoexec.cfg */ words, spelling

2020-12-17T19:13:08Z

Autoexec.cfg: words, spelling

← Older revision		Revision as of 14:13, 17 December 2020
Line 200:		Line 200:
	As you can tell from above, Armagetron is insanely customizable. But what if you want to make semi-permanent changes to settings you might type into the [[Console]]? The answer is the autoexec.cfg file. Here is how it use it:		As you can tell from above, Armagetron is insanely customizable. But what if you want to make semi-permanent changes to settings you might type into the [[Console]]? The answer is the autoexec.cfg file. Here is how it use it:

	1. '''Locate the configuration directories.''' Launch Armagetron and select "About" from the main menu. This will list directories where Arma stores/reads data. The configuration you want access to is usually in your $HOME folder (this is dependent on your operating system). Open and bookmark/shorcut the configuration directory, you'll ~~proably~~ want to come back here later.		1. '''Locate the configuration directories.''' Launch Armagetron and select "About" from the main menu. This will list directories where Arma stores/reads data. The configuration directory you want access to is usually in your $HOME folder (this is dependent on your operating system). Open and bookmark/shorcut the configuration directory, you'll probably want to come back here later.

	2. '''Create or edit autoexec.cfg.''' If this file does not exist, create it. There is nothing special about CFG files, they can be edited with any simple text editor like Notepad on Windows. Armagetron looks for and loads this file when it starts. Any settings you put in there will override default values.		2. '''Create or edit autoexec.cfg.''' If this file does not exist, create it. There is nothing special about CFG files, they can be edited with any simple text editor like Notepad on Windows. Armagetron looks for and loads this file when it starts. Any settings you put in there will override default values.

Sinewav: autoexec.cfg, I've been talking about it a lot. Now I don't have to anymore.

2020-12-17T07:39:20Z

autoexec.cfg, I've been talking about it a lot. Now I don't have to anymore.

← Older revision		Revision as of 02:39, 17 December 2020
Line 196:		Line 196:

	Developer's note: these color codes were not intended for use by the players; the choice of 0x as intro string was a bit unfortunate. Some servers will filter away your codes, so do your testing in a local game. Since it was not intended for use, no thought was given on usability, and for example upper case codes are not accepted. So use 0xff0000 for red, not 0xFF0000. And don't be angry about future unannounced changes to the format.		Developer's note: these color codes were not intended for use by the players; the choice of 0x as intro string was a bit unfortunate. Some servers will filter away your codes, so do your testing in a local game. Since it was not intended for use, no thought was given on usability, and for example upper case codes are not accepted. So use 0xff0000 for red, not 0xFF0000. And don't be angry about future unannounced changes to the format.

			== Autoexec.cfg ==
			As you can tell from above, Armagetron is insanely customizable. But what if you want to make semi-permanent changes to settings you might type into the [[Console]]? The answer is the autoexec.cfg file. Here is how it use it:

			1. '''Locate the configuration directories.''' Launch Armagetron and select "About" from the main menu. This will list directories where Arma stores/reads data. The configuration you want access to is usually in your $HOME folder (this is dependent on your operating system). Open and bookmark/shorcut the configuration directory, you'll proably want to come back here later.

			2. '''Create or edit autoexec.cfg.''' If this file does not exist, create it. There is nothing special about CFG files, they can be edited with any simple text editor like Notepad on Windows. Armagetron looks for and loads this file when it starts. Any settings you put in there will override default values.

			3. '''Add your custom settings.''' Some of the most common setting are for Custom Camera (rise, pitch, etc.). You can see a list of these and many, many more on the [[Console_Commands\|Console Commands]] page Put each setting on it's own line followed by a space, then the value of your choice. Save the file when finished.

			4. '''More settings.''' autoexec.cfg will also override settings in your user.cfg. You can copy instant chats, your player name, even keybindings found in user.cfg to autoexec.cfg and modify them without breaking your user.cfg file.

			5. '''Advanced usage.''' You can have any number of config files in the directory alongside of autoexec.cfg, with any name you choose. This is helpful if you want a modular setup. For instance, you can store camera settings in a file named "my_camera.cfg" and dual cycle colors in "my_cycle.cfg", then use autoexec.cfg to load them with the INCLUDE command. Example:

			INCLUDE my_camera.cfg
			INCLUDE my_cycle.cfg

			6. '''Even more advanced usage.''' Configurations can be loaded at any time, not just at start. Maybe you have texture settings and instant chats that are specific to a server such as Fortress. Let's say it's called fortress.cfg. You can enter chat and type: ''/console include fortress.cfg'' to load those settings. To make things easier and faster, set an instant chat key to ''/console include \\'' and type the filename. (Remember, loading custom settings in this way overrides others, so you probably want to save your custom default values in autoexec.cfg or make a reset.cfg file you can call at will.)

	[[Category:Client Features]]		[[Category:Client Features]]

Armanelgtron: /* Chat Colors */ Its supposed to be 0xffff7f for chat not 0xffff88, according to Light

2015-01-01T00:19:54Z

Chat Colors: Its supposed to be 0xffff7f for chat not 0xffff88, according to Light

← Older revision		Revision as of 19:19, 31 December 2014
Line 193:		Line 193:
	0xff8800 this is orange		0xff8800 this is orange
	0xffffff this is white		0xffffff this is white
	~~0xffff88~~ this appears in the normal chat yellow (no change)		0xffff7f this appears in the normal chat yellow (no change)

	Developer's note: these color codes were not intended for use by the players; the choice of 0x as intro string was a bit unfortunate. Some servers will filter away your codes, so do your testing in a local game. Since it was not intended for use, no thought was given on usability, and for example upper case codes are not accepted. So use 0xff0000 for red, not 0xFF0000. And don't be angry about future unannounced changes to the format.		Developer's note: these color codes were not intended for use by the players; the choice of 0x as intro string was a bit unfortunate. Some servers will filter away your codes, so do your testing in a local game. Since it was not intended for use, no thought was given on usability, and for example upper case codes are not accepted. So use 0xff0000 for red, not 0xFF0000. And don't be angry about future unannounced changes to the format.

	[[Category:Client Features]]		[[Category:Client Features]]

Z-man: /* Default Armagetron Advanced User Configuration Folder for user specific installation (recommended) */

2011-10-15T10:59:32Z

Default Armagetron Advanced User Configuration Folder for user specific installation (recommended)

← Older revision		Revision as of 05:59, 15 October 2011
Line 23:		Line 23:
	(click on "Armagetron Advanced.app" in Finder then Click Action Icon (looks like Gear) and choose "Show Package Contents" to open package bundle)		(click on "Armagetron Advanced.app" in Finder then Click Action Icon (looks like Gear) and choose "Show Package Contents" to open package bundle)

	==== Default Armagetron Advanced User ~~Configuration~~ Folder for user specific installation (recommended) ====		==== Default Armagetron Advanced User Data Folder for user specific installation (recommended) ====

	* Note that you have to enable viewing hidden files to see some directories.		* Note that you have to enable viewing hidden files to see some directories.
			* For all systems, unpacking the moviepack so that it sits as a 'moviepack' folder inside the user data folder works.

	'''Windows 2000/XP''': C:\Documents and Settings\[Username]\Application Data\Armagetron		'''Windows 2000/XP''': C:\Documents and Settings\[Username]\Application Data\Armagetron

Z-man: /* Default Armagetron Advanced User Configuration Folder. */

2011-10-15T10:53:15Z

Default Armagetron Advanced User Configuration Folder.

← Older revision		Revision as of 05:53, 15 October 2011
Line 23:		Line 23:
	(click on "Armagetron Advanced.app" in Finder then Click Action Icon (looks like Gear) and choose "Show Package Contents" to open package bundle)		(click on "Armagetron Advanced.app" in Finder then Click Action Icon (looks like Gear) and choose "Show Package Contents" to open package bundle)

	==== Default Armagetron Advanced User Configuration Folder. ====		==== Default Armagetron Advanced User Configuration Folder for user specific installation (recommended) ====

	* Note that you have to enable viewing hidden files to see some directories.		* Note that you have to enable viewing hidden files to see some directories.