Hammer++/Docs/Installation for Other Games

is a powerful mapping tool that solves many issues that the introduces, and adds some much needed features that useful to every mapper. However the only official versions of Hammer++ available are for ( and ), (, , ), ( and ), , and . 
Thankfully, it is possible to configure Hammer++ to use assets and compilers for other games that they were not originally intended for, including , and more! Almost every Source game can run using some version of Hammer++. The games in the list below have been proven to work using the method below:
This method and accompanying pictures were taken from this steam guide by the user RosemaryWebs.
==Installing Hammer++==
For games that are supported by Hammer++, simply download then extract the contents to the game's folder normally.
===Installing Hammer++ on unsupported games===
For games that are not officially supported by Hammer++ (example: ), users can try other version of Hammer++, such as one made for .
First, make sure that you have the "x86-64" (64-bit) branch of Garry's Mod installed by going to Properties -> Betas -> Change "Beta Participation" to "x86-64 - Chromium + 64-bit binaries". Then wait for everything to be downloaded and installed.
Next step is actually installing Hammer++ into the files. Open the downloaded file, open the folder "", extract the bin folder in the archive into the Garry's Mod folder in your steamapps/common/GarrysMod folder. Now, go into the bin folder and launch Hammer++ (), which will default to Garry's Mod configuration. We will create a new configuration pointed at the Portal 2 assets. This is where things can get complicated.
First, go to Tools -> Options, click "Edit", add "Portal 2" as game name, then close. After that, copy the information that is seen above into the respective boxes. If your game is in a separate folder than your normal steam directory, you will have to replace $SteamUserDir with the full file directory. Now click "OK" to close and save this information.
You will get two popups which said that some changes will not update until Hammer++ restarts, but they are not important so just click "OK" on both. With this completed, you are halfway done with configuring Hammer++.
Now, for compiling the map, we need to define the build programs. Go to the Build Programs tab and copy the information below:
After you do this, click "Apply" then click "OK" to save your changes. Then, close Hammer++. Now, we will have to bring over Portal 2's lighting data into GMod. Because Portal 2 had different texlights compared to GMod, we need to define Portal 2's lights in the GMod directory. Open Portal 2's lights.rad located in Portal 2/portal2 with any text editor and copy all of its contents. Then, go to GMod's lights file and paste Portal 2's contents at the bottom of the file. It should look similar to this (comments not needed):
You have now completed the setup of Hammer++! However if you load a new map you will find that many of your custom models and textures are missing. This is because the program is searching through the GMod directory for the necessary files and then it doesn't find them it presents you with a missing model/texture. To fix this, we will need to mount Portal 2 into Garry's Mod.
==Adding custom content==
To mount Portal 2 content into Garry's Mod, and in turn, Hammer++, go to your Garry's Mod directory "", open and follow the instructions on the file.
Here are the examples:
"portal2"	"C:\Program Files\Steam\steamapps\common\Portal 2\portal2"
"portal2_dlc1"	"C:\Program Files\Steam\steamapps\common\Portal 2\portal2_dlc1"
"portal2_dlc2"	"C:\Program Files\Steam\steamapps\common\Portal 2\portal2_dlc2"
===Previous versions (CS:GO Hammer++, unsupported)===
This is where things can get complicating. You can copy-paste all your custom files, but that can bloat your hard drive more than it needs to. Instead, it can be more space effective to create symbolic links. This is where the Link Shell Extension can help, but it is possible to use command prompt.
First, navigate to Portal 2\portal2\Gameinfo.txt and add all the Portal_dlcx folders as well as all your custom folders following the format seen below: 
 
We do this because CS:GO's engine, and in turn CS:GO Hammer++, do not search automatically for the dlcs folders, so we have to manually list them.
====Link Shell Extension====
First, download Link Shell Extension and install it.
Next, go to your base Portal 2 directory and Ctrl+Left click all your custom folders and dlcs folders and right click. Select "Choose link source" to start creating links. Then, go to your CS:GO directory and right click an empty space. Hover over "Drop link as" and select "Symbolic Links".
====Command Prompt Method====
Press the Windows key on your keyboard and type "cmd". Right click "Command Prompt" and click "Run as Administrator." A User Account Control prompt should pop up, press "Ok".
We will now use the command to create a symbolic link. The syntax for this command is as follows: 
The first directory is the name of the folder the link will be named. The second directory is the name of the folder you are linking to. To simplify, by running this command you are creating a folder in the first directory that, when you open it, will show all the contents of the linked folder in the second directory. By creating a link from your CS:GO directory to your Portal 2 directory, you are not actually copying the files in those folders, you are essentially tricking Hammer++ into thinking that it is accessing a folder in CS:GO's directory when it is actually seeing files located in Portal 2's directory. This also works across drives, so you can have symbolic links on your D: drive that point to folders in your C: drive. 
An example of this command is as follows: 
You will now repeat this process for every custom folder you use, including the dlc folders. This is not needed for the base game (in this example ) folder, as hammer automatically mounts this directory.
====Final Result====
After you make links to all the folders, your CS:GO folder should look similar to this, just with all your custom folders instead: 
 
Now to fix the Hammer models, open the Counter-Stike Global Offensive\platform folder and delete/rename the materials and Models folder and replace them with Symbolic Links to their respective folders in the Portal 2\platform folder. It should look similar to this: 
 
After you do this, open Hammer++ again. Now, you should be set! To get a list of all new features, try checking out the Hammer++ website and its page on this wiki. For general Hammer assistance, check out this article.
==External links==
*Installing Hammer++ For Portal 2 (original guide) 
*Hammer++ Website
*Link Shell Extension Website
Category:Hammer++