Fix "Server Is Enforcing Consistency for This File"

This Source-engine kick means a file on your PC doesn't match what the server expects — usually a custom model or skin you installed. Here's the fix from both sides.

What "enforcing consistency" means

The server has sv_consistency on and is checking that certain files (models, textures, sounds) match its versions. Your custom replacement file differs, so you're kicked. It's an anti-cheat measure against see-through walls and oversized models.

Player fix: remove your custom files

Whatever custom model/skin/texture you added for that game is the culprit. Remove it from the custom/ folder (or verify the game's files in Steam to restore originals), then rejoin.

steamapps/common/<game>/<game>/custom/
# move your custom .vpk/files out, then verify game files

Admin fix: don't over-enforce

If legit players keep getting kicked, the server may be enforcing files it shouldn't. Either ensure your FastDL serves the exact files clients must match, or relax which files are forced. sv_consistency 0 disables the check entirely (less secure):

sv_consistency 1   // on (default, secure)
sv_consistency 0   // off — only if it's wrongly kicking players

Player side: remove your custom skins. Admin side: serve matching files via FastDL, or relax consistency.

Which custom file is being flagged?

The kick message often names the offending file path, or you can narrow it down by what you changed most recently — a weapon skin, a player model, a HUD, or a sound pack. On Source games, custom content lives in the custom/ folder as loose files or .vpk archives; move them out in groups to find which one triggers the kick, then leave that one out for servers that enforce consistency.

Admin: why consistency exists and when to relax it

sv_consistency stops players using modified models or textures to gain an unfair view (thin walls, bright skins, oversized hitbox models). Turning it fully off with sv_consistency 0 removes that protection, so prefer serving the correct files through FastDL so legitimate players auto-match, and only force consistency on the specific files that matter for fairness rather than everything.

How to prevent consistency kicks

• Players: keep a "clean" install for servers that enforce consistency, and only load custom content on servers that allow it.
• Players: verify game files in Steam after removing custom content to be sure the originals are back.
• Admins: keep FastDL serving the exact file versions the server uses so clients match automatically.
• Admins: enforce consistency narrowly on fairness-critical files, not on cosmetic-only content.

Related Source-engine guides

If addons or textures fail to load in the first place, see Garry's Mod addons not loading & missing textures. If a plugin/module won't load on a CS 1.6 server, read AMX Mod X "Couldn't load library". For CS2 verification kicks, see CS2 "VAC was unable to verify the game session".

Counter-Strike, Steam, VAC and the Source engine are trademarks of Valve Corporation. ESAGAMES is an independent hosting provider, not affiliated with or endorsed by Valve. You must own a legitimate copy of the game.