---
title: "How to Add Custom Player and Weapon Models Server-Side"
excerpt: "Place custom player and weapon models on the server, distribute them over FastDL, precache them safely, and avoid the model-overflow crash that kills busy servers."
category: "installation"
tags: "models, custom-content"
image: ""
read_time: "8 min read"
---
<p>Custom models &mdash; a fresh AK viewmodel, reskinned player models, a distinctive knife &mdash; make a server feel like yours. Doing it server-side means every player sees the same content, downloaded automatically. The work is in three parts: placing the files, distributing them, and precaching them without blowing the engine's model limit. That last part is what separates a stable custom server from one that crashes on a full house.</p>
<h2>1. Understand the two kinds of model swap</h2>
<ul>
<li><strong>Weapon models</strong> come in three variants per weapon: <code>v_</code> (viewmodel, what you hold), <code>p_</code> (player model attachment others see), and <code>w_</code> (world/dropped model). They live in <code>cstrike/models/</code> (e.g. <code>v_ak47.mdl</code>).</li>
<li><strong>Player models</strong> live in <code>cstrike/models/player/&lt;name&gt;/&lt;name&gt;.mdl</code>. Replacing the default team models changes everyone; adding new ones requires a plugin to assign them.</li>
</ul>
<h2>2. Place the files</h2>
<p>To replace a default weapon skin globally, drop the custom <code>.mdl</code> over the default path:</p>
<pre>cstrike/models/v_ak47.mdl
cstrike/models/p_ak47.mdl
cstrike/models/w_ak47.mdl</pre>
<p>The client downloads whichever files it lacks and uses them in place of its own. For player models, place them under <code>models/player/</code> in their own subfolder; the folder name must match the <code>.mdl</code> name or the model will not load.</p>
<h2>3. Distribute over FastDL</h2>
<p>Custom models only reach players if downloads are enabled and the files are on your mirror. Set the download cvars:</p>
<pre>sv_allowdownload 1
sv_downloadurl "http://dl.example.com"</pre>
<p>Copy the exact <code>models/</code> paths into the FastDL web root's <code>cstrike/models/</code> and bzip2-compress them. The mechanics are in <a href="/tutorials/install-cs16-server-nginx-fastdl">the Nginx FastDL guide</a> and <a href="/tutorials/sv-allowdownload-settings">sv_allowdownload settings</a>. A client with <code>cl_allowdownload 0</code> will see the default model regardless &mdash; you cannot override their choice.</p>
<h2>4. Precache so the model is transmitted</h2>
<p>Simply overwriting a default file works because the engine already precaches that path. For <em>new</em> models &mdash; ones the base game does not reference &mdash; the server must precache them at map start or clients never receive them. The standard approach is a small AMX Mod X plugin using the plugin-precache forward:</p>
<pre>public plugin_precache() {
    precache_model("models/player/ninja/ninja.mdl")
    precache_model("models/v_customknife.mdl")
}</pre>
<p>Or list them in the map's <code>.res</code> file so they download without being precached as active models. Player-model assignment plugins such as <a href="/plugins/csb-weapon-models">CSB Weapon Models</a> handle both the precache and the per-player <code>SetUserModel</code> call for you.</p>
<h2>5. Respect the model limit</h2>
<p>The GoldSrc engine caps the number of precached models. Every custom model you add counts against that budget alongside the map's own models, and a busy custom server that piles on weapon skins, player models and decorative props can exceed it &mdash; producing a hard crash, not a warning. Quote the symptom people search for:</p>
<blockquote>Host_Error: PF_precache_model_I: Model ... overflow</blockquote>
<p>The fix is budgeting: remove models you do not need, combine variants, and prefer replacing existing default models (which cost no extra precache slot) over adding brand-new ones. The full diagnosis is in <a href="/tutorials/fix-model-overflow-precache">the model-overflow fix</a>.</p>
<h2>6. Keep filenames and structure exact</h2>
<p>Models reference their own textures and sequences by internal name. A player model in <code>models/player/ninja/</code> whose <code>.mdl</code> is not named <code>ninja.mdl</code> will not load; a weapon model missing its <code>.bmp</code>-style external textures (for older models) shows as a checkerboard. Test each model in a listen server before deploying to a public one, and add custom sounds the same way under <code>sound/</code>, listed in the <code>.res</code>.</p>
<h2>Troubleshooting</h2>
<ul>
<li><strong>Model shows as a giant <code>ERROR</code> sign</strong> &mdash; the file failed to precache or download. Confirm it is on the FastDL mirror and precached in <code>plugin_precache()</code>.</li>
<li><strong>Server crashes on a full server with <code>... overflow</code></strong> &mdash; you exceeded the precache model limit. Trim models; see <a href="/tutorials/fix-model-overflow-precache">the fix</a>.</li>
<li><strong>One player sees defaults, everyone else sees the skin</strong> &mdash; that client set <code>cl_allowdownload 0</code>. Only they can change it.</li>
<li><strong>Purple/black checkerboard model</strong> &mdash; missing external textures or a corrupt <code>.mdl</code>. Re-export the model with textures embedded.</li>
</ul>
<h2>Verification</h2>
<p>Join with a clean client (delete the custom files locally first) and confirm it downloads and displays the custom model, not the default and not an <code>ERROR</code> sign. Then fill the server or run a bot-heavy map to confirm you stay under the precache limit &mdash; a crash only when many models and players are active is the overflow signature. If a fresh client downloads and renders every model on a full server without crashing, your custom content is deployed correctly.</p>