AutoExec - Revision history

ReyalP: fix autoexec usage, case

2006-04-28T04:51:14Z

fix autoexec usage, case

← Older revision		Revision as of 04:51, 28 April 2006
Line 1:		Line 1:
	== Default AutoExec ==		== Default AutoExec ==

	When ~~connecting~~ to ~~any server, the client will look for~~ the file ''~~AutoExec~~.cfg'' ~~in the base folder of whatever mod the '''client''' is running, in ETPro's case this would be ''\Wolfenstein - Enemy Territory\etpro\'' and if found that file will be launched~~. ~~It is advised that~~ you start ~~up the client~~ with ~~the~~ mod of the server you ~~are connecting~~ to~~. This~~ is ~~especially true if you have~~ a ~~different config for each~~ mod.		When started, ET attempts to load and the file ''autoexec.cfg''. If you start with <tt>+set fs_game <mod directory></tt> ET looks in the fs_game directory first. Some external server browsers may do this for you when you connect to a server that is running a mod.

	This is often used to store important settings that would normally be in your ''~~ETConfig~~.cfg'' file, as if the server forces a cvar to a value that does not match what you set the cvar's value to in your ~~ETConfig~~.cfg file then that value will then be changed in your config file.		This is often used to store important settings that would normally be in your ''etconfig.cfg'' file, as if the server forces a cvar to a value that does not match what you set the cvar's value to in your etconfig.cfg file then that value will then be changed in your config file.

	However if you store the cvar setting in your ~~AutoExec~~.cfg file, then even if a server changes the cvar value, the next time you connect to a server the original setting you chose will be used again.		However if you store the cvar setting in your autoexec.cfg file, then even if a server changes the cvar value, the next time you connect to a server the original setting you chose will be used again.

	== Client Auto Map Scripts ==		== Client Auto Map Scripts ==

Lagger: corrected autoexec launch mixup

2006-04-28T02:32:53Z

corrected autoexec launch mixup

← Older revision		Revision as of 02:32, 28 April 2006
Line 1:		Line 1:
	== Default AutoExec ==		== Default AutoExec ==

	When connecting to any server, the client will look for the file ''AutoExec.cfg'' in the base folder of whatever mod the ~~server~~ is running, in ETPro's case this would be ''\Wolfenstein - Enemy Territory\etpro\'' and if found that file will be launched.		When connecting to any server, the client will look for the file ''AutoExec.cfg'' in the base folder of whatever mod the '''client''' is running, in ETPro's case this would be ''\Wolfenstein - Enemy Territory\etpro\'' and if found that file will be launched. It is advised that you start up the client with the mod of the server you are connecting to. This is especially true if you have a different config for each mod.

	This is often used to store important settings that would normally be in your ''ETConfig.cfg'' file, as if the server forces a cvar to a value that does not match what you set the cvar's value to in your ETConfig.cfg file then that value will then be changed in your config file.		This is often used to store important settings that would normally be in your ''ETConfig.cfg'' file, as if the server forces a cvar to a value that does not match what you set the cvar's value to in your ETConfig.cfg file then that value will then be changed in your config file.

WeblionX at 17:53, 5 November 2005

2005-11-05T17:53:36Z

← Older revision		Revision as of 17:53, 5 November 2005
Line 31:		Line 31:

	These are only run when the team or class changes, they are not run on every spawn.		These are only run when the team or class changes, they are not run on every spawn.

			[[Category:ETPro]]

Fusen at 15:57, 5 November 2005

2005-11-05T15:57:54Z

← Older revision		Revision as of 15:57, 5 November 2005
Line 1:		Line 1:
			== Default AutoExec ==

			When connecting to any server, the client will look for the file ''AutoExec.cfg'' in the base folder of whatever mod the server is running, in ETPro's case this would be ''\Wolfenstein - Enemy Territory\etpro\'' and if found that file will be launched.

			This is often used to store important settings that would normally be in your ''ETConfig.cfg'' file, as if the server forces a cvar to a value that does not match what you set the cvar's value to in your ETConfig.cfg file then that value will then be changed in your config file.

			However if you store the cvar setting in your AutoExec.cfg file, then even if a server changes the cvar value, the next time you connect to a server the original setting you chose will be used again.

	== Client Auto Map Scripts ==		== Client Auto Map Scripts ==

Fusen at 15:48, 5 November 2005

2005-11-05T15:48:56Z

← Older revision		Revision as of 15:48, 5 November 2005
Line 3:		Line 3:
	When a map loads or restarts, the client will look for the following scripts and run them if found:		When a map loads or restarts, the client will look for the following scripts and run them if found:

	* autoexec_''(mapname)''.cfg		* autoexec_''mapname''.cfg
	* autoexec_default.cfg		* autoexec_default.cfg

Fusen at 15:48, 5 November 2005

2005-11-05T15:48:43Z

← Older revision		Revision as of 15:48, 5 November 2005
Line 1:		Line 1:

	== Client Auto Map Scripts ==		== Client Auto Map Scripts ==

	When a map loads or restarts, the client will look for the following scripts and run them if found:		When a map loads or restarts, the client will look for the following scripts and run them if found:

	* autoexec_(mapname).cfg		* autoexec_''(mapname)''.cfg
	* autoexec_default.cfg		* autoexec_default.cfg

Fusen at 15:48, 5 November 2005

2005-11-05T15:48:14Z

New page

== Client Auto Map Scripts ==

When a map loads or restarts, the client will look for the following scripts and run them if found:

* autoexec_(mapname).cfg
* autoexec_default.cfg

For example if the map rotates to battery, the client would look for autoexec_battery.cfg and run it. If autoexec_battery.cfg is not found, it would try to run autoexec_default.cfg instead.

== Client Auto Team/Class Scripts ==

When players spawn with a changed team or class, the client will look for the following scripts and run them if found:

* autoexec_axis.cfg
* autoexec_allies.cfg
* autoexec_spectator.cfg

* autoexec_soldier.cfg
* autoexec_medic.cfg
* autoexec_engineer.cfg
* autoexec_fieldops.cfg
* autoexec_covertops.cfg

These are only run when the team or class changes, they are not run on every spawn.