Exec: Difference between revisions
Jump to navigation
Jump to search

Tip:The
Tip:
Warning:Recursive executions crash the game!
Example:If the CFG
m (Category:Core Console Commands (good cat tbh)) |
(Recursive exec crashes the game.) |
||
Line 1: | Line 1: | ||
{{lang|exec}} | {{lang|exec}} | ||
<code>'''exec'''</code> is a [[console command]] available in all | <code>'''exec'''</code> is a [[console command]] available in all {{game name|src|name=Source}} games. | ||
It is used to execute [[CFG]] files, namely a sequence of console commands. | It is used to execute [[CFG]] files, namely a sequence of console commands. | ||
Line 10: | Line 10: | ||
* The optional <code>[path id]</code> argument can be used to specify a different path to execute CFG files from. Its first character must be <code>*</code>. | * The optional <code>[path id]</code> argument can be used to specify a different path to execute CFG files from. Its first character must be <code>*</code>. | ||
{{tip|The <code>exec</code> command can be used in the [[launch options]] with <code>-exec <filename></code>, for example <code>-exec [[autoexec]]</code> will always execute the CFG file <code><game>/cfg/autoexec.cfg</code> when the game starts.}} | {{tip|The <code>exec</code> command can be used in the [[launch options]] with <code>-exec <filename></code>, for example <code>-exec [[autoexec]]</code> will always execute the CFG file <code><game>/cfg/autoexec.cfg</code> when the game starts (which is overkill, because the game already executes autoexec.cfg even without this launch option).}} | ||
{{tip|<code>exec</code> can save a lot of time if a sequence of commands should be executed multiple times. Instead of typing the commands into the console every time, one can save them in a CFG file and execute it using <code>exec</code>.}} | {{tip|<code>exec</code> can save a lot of time if a sequence of commands should be executed multiple times. Instead of typing the commands into the console every time, one can save them in a CFG file and execute it using <code>exec</code>.}} | ||
{{warning|Recursive executions crash the game! {{Example|If the CFG <code><game>/cfg/a.cfg</code> contains the line <code>exec a</code>, then its execution will cause a game crash!}}}} | |||
== Examples == | == Examples == |
Revision as of 18:42, 19 December 2021


exec
is a console command available in all Template:Game name games.
It is used to execute CFG files, namely a sequence of console commands.
Usage
exec <filename> [path id]
The command executes the file "//[path id]/cfg/<filename>"
if it exists. The default value of [path id]
is *
, resulting in the default path <game>/cfg/<filename>
.
- The
<filename>
argument is the name of the file either with or without the .cfg extension. A path can also be prefixed. If the<filename>
argument is given, the game always prints the lineExecing config: <filename>
in the console. If the file does not exist, the game also prints the lineexec: couldn't exec <filename>
. - The optional
[path id]
argument can be used to specify a different path to execute CFG files from. Its first character must be*
.

exec
command can be used in the launch options with -exec <filename>
, for example -exec autoexec
will always execute the CFG file <game>/cfg/autoexec.cfg
when the game starts (which is overkill, because the game already executes autoexec.cfg even without this launch option).
exec
can save a lot of time if a sequence of commands should be executed multiple times. Instead of typing the commands into the console every time, one can save them in a CFG file and execute it using exec
.

<game>/cfg/a.cfg
contains the line exec a
, then its execution will cause a game crash!Examples
Command | Executed file |
---|---|
exec config
|
<game>/cfg/config.cfg
|
exec config.cfg
| |
exec config *
| |
exec config */maps
|
<game>/maps/cfg/config.cfg
|
exec folder/config
|
<game>/cfg/folder/config.cfg
|
exec folder/config */maps
|
<game>/maps/cfg/folder/config.cfg
|
Similar Commands
There are console commands that are identical to exec
, but with slight differences.
ConCommand | Availability | Description |
---|---|---|
execifexists
|
![]() ![]() ![]() ![]() ![]() ![]() |
There is no error message execifexists: couldn't exec <filename> in the console if the specified file does not exist.
|
execwithwhitelist
|
![]() |
All console commands in the specified CFG file are executed with whitelistcmd. Commands are ignored if they are not whitelisted in <game>/bspconvar_whitelist.txt .
|