Hammer Manual Configuration

==Read This First!==
If you launch the Hammer editor with no proper game configurations set up, the Hammer Editor has not automatically configured itself after installing the game Authoring Tools or Source SDK. You can follow these steps to manually configure it. Before following these steps to repair a bad configuration, it is strongly suggested that you first attempt to fix your configuration by following the steps outlined in Reset the Source SDK Game Configuration.
==Adding a New Game Configuration==
# Launch Hammer.
# The First Time Setup dialog box may appear. If it does, click the No button:
#: 
# If the First Time Setup window did appear, this Configure Hammer dialog should now be open. Otherwise, click Options in the Tools menu, and then open the Game Configurations tab.
#: 
# Click on the Edit button to the right of the Configuration drop-down list, which will open the Edit Game Configurations dialog:
#: 
# Press the Add button. This will open the Add a game dialog:
#: 
# Enter a name for the new configuration, usually the name of the game or mod. Press OK to confirm your choice and close the dialog.
# Press the Close button in the Edit Game Configurations dialog.
==Setting Game Directory and Basic Parameters==
# You should now be back in the Configure Hammer dialog with your configuration selected in the Configuration drop-down list:
#: 
# Press Add to the right of the Game Data files list. An Open dialog will appear:
#: 
# Select the appropriate .FGD file for your game or mod:
#* For a Counter-Strike: Source configuration, click on and then the Open button.
#* For a Half-Life 2 (or episodes) configuration, click on and then the Open button.
#* For a Half-Life 2 Deathmatch configuration, click on and then the Open button.
#* For a Portal configuration, click on and then the Open button.
#* For a Team Fortress 2 configuration, click on and then the Open button.
# Now you'll be back in the Configure Hammer dialog with these fields filled out:
#: 
# Type 0.25 into the Default texture scale field. Paste tools\toolsskybox into the Cordon texture field.
# Under Game Executable Directory, hit Browse and select the folder where the game executable (such as ) is located.
#: For example, the directory for a Counter-Strike configuration might be:
#:: $SteamUserDir\Counter-Strike Source
# Under Game Directory, enter the path of the folder that contains gameinfo.txt.
#: For example, the game directory for a Half-Life 2 configuration might be:
#:: $SteamUserDir\Half-Life 2\hl2
#: For mods located in the sourcemods folder, the game directory would be of the form:
#:: C:\Program Files (x86)\Steam\steamapps\sourcemods\mod
# Under Hammer Map Directory, you should enter the folder where you wish to save your .VMF map source files.
#* Example for Counter-Strike:
#: C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Source\cstrike\mapsrc or
#: C:\Program Files (x86)\Steam\steamapps\common\sourcesdk_content\cstrike\mapsrc
#* Example for Half-Life 2:
#: C:\Program Files (x86)\Steam\steamapps\common\Half-Life 2\hl2\mapsrc or
#: C:\Program Files (x86)\Steam\steamapps\common\sourcesdk_content\hl2\mapsrc
#* Example for Half-Life 2 Deathmatch:
#: C:\Program Files (x86)\Steam\steamapps\common\Half-Life 2 Deathmatch\hl2\mapsrc or
#: C:\Program Files (x86)\Steam\steamapps\common\sourcesdk_content\hl2mp\mapsrc
#* Example for Team Fortress 2:
#: C:\Program Files (x86)\Steam\steamapps\common\Team Fortress 2\tf\mapsrc or
#: C:\Program Files (x86)\Steam\steamapps\common\sourcesdk_content\tf\mapsrc
== Setting up the Build Programs ==
# Click on the Build Programs tab:
#: 
# In Game Executable, enter the path of the .exe file used to launch the game.
#* For example, for a Counter-Strike configuration, your Game Executable might be:
#: $SteamUserDir\counter-strike source\hl2.exe
#* For a Half-Life 2 configuration, your Game Executable might be:
#: $SteamUserDir\half-life 2\hl2.exe
#* For a Half-Life 2 Deathmatch configuration, your Game Executable might be:
#: $SteamUserDir\half-life 2 deathmatch\hl2.exe
#* For a Team Fortress 2 configuration, your Game Executable might be:
#: $SteamUserDir\team fortress 2\tf_win64.exe (64-bit)
#: $SteamUserDir\team fortress 2\tf.exe (32-bit)
# In BSP executable, enter the location of vbsp.exe:
#: EXEDIR\bin\vbsp.exe</code>
#:: EXEDIR</code> is the value that was entered into Game Executable Directory field earlier, usually where the game is installed.
# In VIS executable, enter the location of the vvis.exe:
#: EXEDIR\bin\vvis.exe</code>
#:: EXEDIR</code> is the value that was entered into Game Executable Directory field earlier, usually where the game is installed.
# In RAD executable, enter the location of the vrad.exe:
#: EXEDIR\bin\vrad.exe</code>
#:: EXEDIR</code> is the value that was entered into Game Executable Directory field earlier, usually where the game is installed.
# In Place compiled maps in this directory before running the game, enter the Game Directory with \maps appended to the end of it:
#* Example for Counter-Strike:
#: $SteamUserDir\counter-strike source\cstrike\maps
#* Example for Half-Life 2:
#: $SteamUserDir\half-life 2\hl2\maps
#* Example for Half-Life 2 Deathmatch:
#: $SteamUserDir\half-life 2 deathmatch\hl2mp\maps
#* Example for Source SDK mod:
#: C:\Program Files (x86)\Steam\steamapps\sourcemods\MODDIR\maps
#:: MODDIR is the name of your game directory for your mod.
# Press OK. Hammer is now configured for use. Category:Hammer DialogsCategory:Source SDK FAQCategory:Tutorials