Valve Hammer Editor 3.5 Setup for CS 1.6

Valve Hammer Editor 3.5 is the classic GoldSrc level editor, and getting it to compile CS 1.6 maps is entirely a matter of configuration: telling it which game you are building for, where the textures and entity definitions are, and which compile tools to run. Skip a field and you get missing entities, no textures in the 3D view, or a compile that never runs. This walks the whole setup once, cleanly. If you prefer a modern editor, J.A.C.K. is an alternative, but the concepts below map one-to-one.

1. Open Game Configurations

Go to Tools → Options → Game Configurations and click Add to create a profile named Counter-Strike 1.6. Everything else hangs off this profile, so create it first.

2. Load the FGD (entity definitions)

The FGD file defines every entity you can place — without it, the entity tool is empty. Add the CS FGD (commonly halflife-cs.fgd) to the Game Data files list for this profile. If you use ZHLT/VHLT features such as func_detail, also add zhlt.fgd so those entities appear. You can load more than one FGD; add both.

3. Set the texture (WAD) format and directories

Set Texture Format to WAD3 (Half-Life / TFC) and Map Type to Half-Life / TFC. Then point the profile at your game so textures and content resolve:

Game Executable Directory:  ...\Steam\steamapps\common\Half-Life
Mod Directory:              ...\Steam\steamapps\common\Half-Life\cstrike
Game Directory:             ...\Steam\steamapps\common\Half-Life\valve
RMF/MAP directory:          your working maps folder

These paths are how Hammer finds the game to run the map, and where it looks for content.

4. Add your WADs

Under the Textures tab, add the WAD files the editor should load: halflife.wad and cstrike.wad at minimum, plus any custom WADs. These populate the texture browser and get written into the map's wad key. Keep this list tidy — every WAD here ends up referenced by the map, and a stale entry causes a could not open wad file error at compile.

5. Configure the compile tools (Build Programs)

Go to Tools → Options → Build Programs and point Hammer at your ZHLT/VHLT executables — use Vluzacn's VHLT v34 for a modern map:

Game executable:  hl.exe (in the Half-Life dir)
CSG tool:         hlcsg.exe
BSP tool:         hlbsp.exe
VIS tool:         hlvis.exe
RAD tool:         hlrad.exe
Place compiled maps in: ...\cstrike\maps

The four tools run in the order hlcsg → hlbsp → hlvis → hlrad. Setting the output directory to cstrike\maps means Run Map drops the .bsp where the game can load it. For the flags each tool takes, see the compile parameters guide.

One caveat with Hammer 3.5 specifically: it was written for the old ZHLT and its expert compile dialog stores flags per configuration. When you point it at Vluzacn's VHLT v34, keep an eye on any flags the dialog inserted automatically — a legacy default that VHLT renamed or dropped will make a tool error out immediately. If a compile aborts on the first tool with an unknown-parameter message, open the expert dialog and remove the offending flag rather than assuming the executable is broken. Many mappers keep a plain batch file of the exact command lines as a fallback and only use Hammer's dialog for quick test builds.

6. Run Map

With the profile complete, File → Run Map (F9) opens the compile dialog. Choose the CSG/BSP/VIS/RAD detail levels (Normal for a release, or expert mode to type exact flags), tick "Don't run the game" if you only want the BSP, and compile. Watch the log window — every warning and error the four tools emit appears there, which is where you catch leaks, WAD problems, and texture-axis warnings before they reach players.

Common errors

• Entity tool is empty / entities missing — no FGD loaded. Add halflife-cs.fgd (and zhlt.fgd) to Game Data files.
• No textures in the browser or 3D view — WADs not added, or Texture Format is not WAD3. Add the WADs and set WAD3.
• Run Map does nothing / tool not found — the Build Programs paths point at missing executables. Set them to your actual hlcsg/hlbsp/hlvis/hlrad.
• Compile succeeds but the game does not load the map — output directory is not cstrike\maps. Fix the "Place compiled maps in" path.
• Could not open wad file at compile — a stale WAD in the list; remove entries the map no longer uses.

Verification

Build the classic first map — a sealed room with a light, an info_player_start, and one textured floor — and press F9. If the compile log runs all four tools without a leak and the game launches into your room with textures and lighting, the configuration is correct. If textures are missing in the editor but the compile runs, revisit the WAD list; if entities are missing, revisit the FGD. From here, follow make your first CS 1.6 map to build something real.