"Auto Executables" automatically execute when the game is launched, so whatever is written into this file will be executed, aliased, bound, and set before the game even fully loaded.

This is useful for launching cfg files like outline glow scripts, setting aliases as shortcuts for commands, binding keys that you don't want to bind ingame, and also just setting cvars like the noclip speed.

Why would you need this?
Because some mods require you to change a Cvar or execute a file on game launch.
Examples:

• Font mods require you to change the resolution on game launch.
  
• Outline glow scripts require you to execute a config.
  
• Talker scripts with radial menus require you to execute a config.
  
• Adding reminders of certain commands like rebuilding audiocaches for a specific folder, allowing you to just copypaste the written line and execute it as a command.

In your steam library, go to L4D2, right click it and pick "Properties".


In the General settings, at the bottom is the Launch Options.
Add +exec !exec.cfg.


In "Installed Files" Click Browse.


An explorer window pops up, showing where L4D2 is installed.
Open the left4dead2 folder and then the cfg folder within it.
Create a new text file called !exec.cfg.

Open !exec.cfg with a text editor and paste this empty prefab.
You don't really need this specific text, it's just organized and easy to spot ingame.

Here's an example of how you might want to set up the contents of your settings:

Executables do one thing: Executes multiple cfg files on game launch.
Like Doktor Haus' (Zaeryn's) vocalizer mod, or my outline glow scripts.

Usage:

Aliases function as "Shortcuts" to commands.

Say you have to use the command mat_reloadallmaterials often, but you don't want to bind the command to a key, and you don't want to write the entire command either cause its quite long.
Using aliases you can make one word execute the command.

Or you want to execute a cfg file for testing, like the "singleplayer versus" commands, but you don't want to type out "exec !versus" manually, you can just type "vs" instead, thanks to the alias.

Or, perhaps you just want multiple commands to execute, without writing a new cfg.
Which requires you to separate each cvar with a ; .

Usage:

Binds allow you to bind a key to a command.
Press the key while playing and the command you bound to it triggers.

Walking, jumping, shooting, are all keybinds. But the ingame keybind menu won't allow you to bind anything but basic movement and gameplay related inputs.
So a CFG or manual entering in the ingame console is required.

Usage:

This section is meant for anything else that has no place above.
Such as setting a convar's default, or writing a message into the console log as a reminder.
You could also add the "Swap resolution" thing to reload fonts in here.
Usage:

Here's how a finished exec.cfg would look like ingame, and as raw file.

That's all.

Some people would say "just make a file called autoexec.cfg the game's loading that anyways."
- No, it doesn't always. Plus, having your own file gives your more controll over its name.

Have fun modding your game!

My Discord[discord.gg] - For whatever
My Paypal[paypal.me] - For don't-ations.