Your Own Face in the Sandbox
You’ve spent countless hours in Garry’s Mod, building contraptions, staging scenes, and causing chaos with friends. But as you look around the server, everyone is a familiar face—Gordon Freeman, a Combine soldier, or one of the default HL2 models. You have a character in mind, a unique persona for your machinima or roleplay server, but it doesn’t exist in the Workshop. The desire to step into the sandbox as something truly your own is a powerful itch for any dedicated GMod player.
Creating a custom player model is that final frontier of personalization. It transforms you from a participant using the game’s assets into a creator defining your place within it. While the process involves several steps and specific tools, it is far from an impossible task reserved for professional game developers. With patience and this guide, you can learn how to make a GMod player model that is uniquely yours.
Understanding the GMod Model Pipeline
Before diving into software, it’s crucial to understand what a “player model” actually is in Source Engine terms. It’s not a single file. It’s a collection of interdependent components that the game engine assembles. You cannot simply paint a 3D object and drop it into your addons folder.
A functional Garry’s Mod player model requires three core pieces: the model itself (.mdl), a texture that skins it (.vtf/.vmt), and a QC file that instructs the compiler on how to build everything. The model is typically created in a 3D modeling program like Blender, Maya, or 3ds Max. The texture is painted in an image editor like Photoshop or GIMP. The QC file is a plain text script that ties it all together using Valve’s proprietary tools.
Essential Tools You Will Need
Gathering the right software is your first practical step. Here is the non-negotiable toolkit.
– A 3D Modeling Program: Blender is the overwhelming community favorite. It’s free, open-source, and has excellent Source Engine export support via plugins.
– The Source SDK: This is the official toolkit from Valve, available for free on Steam. You need the “Source SDK Base 2013 Singleplayer” installed. It contains the critical compilers.
– Crowbar: This is a modern, community-developed decompiler and model compiler. It simplifies the QC process and is much more user-friendly than the old GUIStudioMDL. It is essential.
– VTFEdit: This program converts standard image files (.png, .jpg) into the .vtf texture format the Source Engine uses and creates the accompanying .vmt material files.
– A Text Editor: Notepad++ or Visual Studio Code for writing and editing your QC files.
Starting with a Base: The Smart Approach
Unless you are an experienced 3D artist, do not start from a blank scene. The most reliable method is to modify an existing GMod-compatible model. This ensures the underlying skeleton, hitboxes, and attachment points (like for weapons) are already correctly configured.
Use Crowbar to decompile an existing player model you like from Garry’s Mod. This will give you a clean .smd (model data) file and its associated .qc. You now have a perfect template. In your 3D software, you will import this .smd, make your modifications to the mesh, and then re-export it, preserving the original armature.
Decompiling Your Base Model
First, locate the model file. Common player models are in `garrysmod/models/player/`. Open Crowbar. In the “Decompile” tab, set the “Game Path” to your Garry’s Mod directory. Click “Browse” and select the .mdl file you want to use as a base. Choose an output folder for the extracted files. Click “Decompile”.
You will now have several files. The key ones are `yourmodel_reference.smd` (the base mesh) and `yourmodel.qc`. Open the QC file with your text editor—this is your new project’s blueprint.
Modeling and Editing the Mesh
Open Blender. You need to set it up for Source Engine work. Install the Blender Source Tools add-on. This provides the SMD import/export functionality. Once installed, go to Edit > Preferences > Add-ons, search for “Source”, and enable “Import-Export: Source Engine”.
Clear the default scene (Select All, press X, and confirm). Now, import your decompiled reference SMD file. The model will appear, likely in a T-pose, with its armature (the skeleton).
Your task now is to edit the mesh, not the skeleton. Select the mesh object. Enter Edit Mode. You can now extrude, scale, and sculpt the geometry. Want to add a hat? Model it onto the head. Want a longer coat? Extrude the torso geometry. Remember to keep the mesh “skinned” to the armature; the add-on handles this, but avoid deleting the original vertex groups.
A critical rule: Do not alter the bone structure. Do not rename bones, delete them, or change their hierarchy. The Source Engine relies on specific bone names for player rigging and animation. Changing them will break the model.
Creating and Applying New Textures
When you decompiled the model, you also received its texture files (usually in a materials folder). You can edit these directly or create new ones from scratch.
In your image editor, open the decompiled texture. It will likely be a square, flattened UV map that looks like a colorful puzzle. This is your guide. Paint your new design over this map. If you are creating a new accessory you modeled, you will need to unwrap that part of the mesh in Blender to create a new section of the UV map and paint for it.
Save your final texture as a .png or .tga file. Now, open VTFEdit. Go to File > Import. Select your image file. In the window that appears, you can usually leave the default settings, though for player models, “Format: DXT1” and “Generate Mipmaps” is standard. Click “OK” and save the file as a .vtf in your project’s `materials/models/yourmodel/` folder.
VTFEdit will automatically create a basic .vmt file. You may need to edit this text file to ensure the “Shader” is set to “VertexLitGeneric” and the paths are correct.
The Heart of the Process: The QC File
This is the step that intimidates most newcomers, but Crowbar makes it manageable. Your decompiled QC file is already 90% correct. You need to update it to point to your new files.
Open the QC in your text editor. You will see lines like:
$modelname “player/yourmodel/yourmodel.mdl”
$cdmaterials “models/yourmodel/”
$body “body” “yourmodel_reference.smd”
$sequence “idle” “yourmodel_idle.smd”
You need to change the `$modelname` to your desired in-game path. Update the `$cdmaterials` path if you moved your textures. Most importantly, the `$body` line must point to your newly edited and exported SMD file, not the original decompiled one.
You must also define collision hulls (the hitboxes). Your base QC will have `$collisionmodel` lines. Ensure these point to the correct collision SMD file (often decompiled as `yourmodel_phys.smd`). Do not modify the collision model itself unless you know what you’re doing.
Compiling with Crowbar
Once your QC file is updated and saved, and your new SMD model file is exported from Blender, you are ready to compile.
Open Crowbar. Go to the “Compile” tab. Set the “Game Path” to your Garry’s Mod directory. Click “QC File” and select your modified .qc file. Click “Compile”.
If everything is correct, Crowbar will run without errors. The final .mdl file will be created in the location you specified in the `$modelname` QC command. You must place this .mdl file in the exact same relative folder within your Garry’s Mod directory or addon for the game to find it.
Testing and Troubleshooting Your Model
Launch Garry’s Mod. Open the spawn menu (Q by default) and go to the Entities tab. Type “player” in the search bar. You should see a “player_manager” or similar tool. Spawn it, and use its menu to set your model path (e.g., “models/player/yourmodel/yourmodel.mdl”). Press C to switch to third-person view. Your model should appear.
If it doesn’t, or if it appears as a bright pink and black checkerboard, you have a problem. The pink/black error means a missing texture. Double-check all the paths in your QC file and your .vmt file. Ensure the .vtf and .vmt files are in the correct `materials/` folder.
If the model is distorted, stretches wildly, or breaks when you move, the issue is with the mesh or skeleton in your SMD file. Re-import your final SMD into Blender and check that the armature is intact and the mesh is properly weighted. A common mistake is accidentally moving bones in Object Mode.
If the model simply doesn’t appear in the menu, the compilation failed silently. Check Crowbar’s log output for any warnings or errors. The most common QC errors are typos in file paths or missing `$` commands.
Advanced Steps and Polish
Once your basic model works, you can add polish. Create custom facial flexes for expressions in the Facial Animation Editor (part of the Source SDK). Add support for player color groups by defining `$color` in your QC and painting specific regions of your texture. You can even create custom hold types for weapons if your model has unique hands or attachments.
For public release, you will want to package everything into a proper addon. Create a folder named `addons/yourmodeladdon/`. Inside, replicate the `models/` and `materials/` directory structure and place all your files there. Add a proper `addon.txt` with a description. This allows easy sharing via the Steam Workshop.
From Concept to In-Game Reality
The journey from wanting a custom model to seeing it in-game is a series of logical, technical steps. It demystifies a part of game development and grants you a deeper ownership over your gameplay experience. The process teaches valuable skills in 3D asset pipelines, problem-solving, and attention to detail.
Start small. Use a simple base model, make a minor modification like adding a badge or changing a color scheme, and follow the compile process through. That first successful spawn, seeing your tweak in the third-person view, is the proof of concept. From there, your ambitions can grow—more complex edits, entirely new meshes, or fully original characters.
The tools are free. The knowledge is available. The only remaining ingredient is your willingness to follow the steps, confront the errors in the log, and persist. Open Blender, find a model you like, and start decompiling. Your unique place in the Garry’s Mod sandbox is waiting to be built.
