Noclip is one of the most powerful (and most abused) abilities in Garry’s Mod. It lets a player drop collision and fly straight through walls, floors, and props — fantastic for an admin inspecting a build, disastrous when a random Sandbox player uses it to grief, peek through prop hunt walls, or skip past your map’s intended flow. If you run a public or community GMod server, “how do I stop players from using noclip while keeping it for my staff?” is one of the first questions you’ll hit.
The good news: disabling noclip for regular players is a one-line change. The important news: there is a wrong way to do it (turning on sv_cheats) and a right way (using the Sandbox convar plus your admin mod). This guide walks through exactly how noclip is gated in GMod, how to block it for everyone except your authorized admins, and why the permission-based approach is the standard on every well-run server.
How noclip actually works in Garry’s Mod
There are two separate systems that decide whether a given player can fly through your map. Understanding both is the key to controlling noclip correctly instead of accidentally opening the floodgates.
- The vanilla
noclipconsole command is cheat-protected. By default it does nothing unless the server hassv_cheats 1set, OR the gamemode/admin-mod permission system grants the ability some other way. - In Sandbox, a dedicated convar governs player noclip. The convar
sbox_noclipdecides whether players in the Sandbox gamemode are allowed to noclip at all:1means players can noclip,0means it’s disabled.
In single-player and listen-server contexts, the noclip command is commonly bound to the V key (this binding is rebindable). On a properly configured dedicated server you don’t want regular players triggering it at all — which is what sbox_noclip is for.
The fast answer: set sbox_noclip 0
To stop regular, non-privileged players from noclipping, set the Sandbox convar to 0. The cleanest place to do this is your server’s auto-executed config file, garrysmod/cfg/server.cfg, so the setting survives every restart.
// garrysmod/cfg/server.cfg
// Block noclip for regular Sandbox players
sbox_noclip 0You can also run it live from the server console or via RCON to apply it immediately without restarting:
sbox_noclip 0With sbox_noclip 0 active, ordinary players in Sandbox can no longer fly through your map. They’ll be locked to normal physics and collision like everyone else. This is the single change most server owners are looking for — and it does not require enabling cheats.
A quick note on confidence: sbox_noclip and its 0/1 behavior are documented consistently across GMod host guides. It controls whether players can noclip in Sandbox. It wasn’t located on a single canonical Facepunch wiki convar page during research, but its name and effect are uniform across sources, so it’s safe to rely on.
| Value | Effect | Where to set it |
|---|---|---|
sbox_noclip 1 | Players in Sandbox can noclip (default permissive behavior) | server.cfg or console |
sbox_noclip 0 | Players cannot noclip — blocked for non-privileged users | server.cfg or console |
Why you should NOT use sv_cheats to control noclip
It’s tempting to think “noclip is a cheat command, so I’ll just leave sv_cheats 0 and that blocks it.” There’s a kernel of truth there — the vanilla noclip command is cheat-protected — but managing noclip through sv_cheats is the wrong lever for a couple of reasons.
First, sv_cheats is an all-or-nothing, server-wide switch. The default is 0, and when you flip it to 1 it unlocks every cheat-gated command for everyone on the server at once:
noclip— fly through wallsgod— full invincibilitybuddha— can’t die but still takes damageimpulse 101— give all weapons and ammogive— spawn arbitrary entities/weapons- assorted debug and physics commands
So if you enable sv_cheats 1 just to let your admins fly, you’ve simultaneously handed god mode, free weapons, and noclip to every single player connected. That’s the opposite of what you want. Cheat-protected commands also stop working the instant sv_cheats returns to 0, so it’s not even a stable way to grant a persistent ability.
This is precisely why production servers leave sv_cheats at 0 and grant individual abilities — noclip, god, and so on — through an admin mod’s permission system instead. If you genuinely need cheats for a private testing session, see our companion walkthrough on how to enable cheats on your Garry’s Mod server, but understand it’s a blunt instrument you should turn back off afterward.
The right pattern: sbox_noclip 0 plus admin-mod grants
The model nearly every serious GMod server uses is a combination:
- Set
sbox_noclip 0to block noclip for regular players. - Install an admin mod (ULX or SAM) that grants noclip through a permission, which bypasses
sbox_noclipentirely.
Admin systems don’t rely on the cheat flag. They hook the noclip ability and gate it behind a user-group permission, so an authorized admin can noclip even while sbox_noclip 0 blocks everyone else. Regular players stay grounded; your staff fly freely; cheats stay off. That’s the whole point of the permission-based approach.
ULX + ULib
ULX is the long-standing GMod admin suite. It requires ULib as a dependency — install both. Once it’s running, admins toggle their own flight with a chat command:
// In-game chat (ULX)
!noclip
// Console equivalent
ulx noclipWhether a given user can run that command is controlled by their ULX user group, so you can hand noclip to your “admin” or “superadmin” group while denying it to “user.” Because this runs through ULX’s permission layer, it works regardless of the sbox_noclip value.
SAM (Simple Admin Mod)
SAM is a popular modern alternative with a clean menu UI and equivalent chat commands. It uses the same permission-driven philosophy: noclip is a grantable ability tied to a rank, not a server-wide cheat toggle. If you’re starting fresh, either ULX or SAM will get you the “admins fly, players don’t” outcome that sbox_noclip 0 alone can’t provide.
Note that the exact ULX/SAM chat-command syntax above is host-guide-sourced and consistent across the community rather than quoted from a single official spec — but it reflects the standard usage you’ll see documented everywhere.
Putting it together in server.cfg
Your garrysmod/cfg/server.cfg is executed automatically every time the server starts, so it’s the canonical home for persistent settings. A minimal anti-noclip configuration looks like this:
// garrysmod/cfg/server.cfg
// Keep cheats OFF server-wide — do not use sv_cheats to manage noclip
sv_cheats 0
// Disable noclip for regular Sandbox players
sbox_noclip 0
// Admin noclip is granted separately via ULX (!noclip) or SAM
// — permission-based, bypasses sbox_noclip automaticallyAfter editing the file, restart the server (or run the commands live in console/RCON to apply them without a restart). If you administer the box remotely, you can push the change through RCON — see our guide on how to modify the RCON feature on your Garry’s Mod server for setting an rcon_password and connecting safely. For example:
rcon sbox_noclip 0If you’d rather not hand-edit config files at all, a managed control panel makes this trivial. On our Garry’s Mod hosting plans you can drop these lines straight into server.cfg through the file manager and restart with one click, and the panel keeps ULX/SAM addons easy to install. The full setup walkthrough lives in the Garry’s Mod documentation.
Verifying it worked
To confirm your change took effect:
- Check the convar value. Type
sbox_noclipon its own in the server console — it should report0. - Test as a non-admin. Join with an account that has no admin group and try to noclip (default V). Nothing should happen.
- Test as an admin. Run
!noclip(ULX) or use the SAM menu — flight should still work, proving the permission bypass is intact. - Confirm cheats are off.
sv_cheatsshould report0, so the abuse-prone cheat commands stay locked.
If a regular player can still noclip after all this, the usual culprits are: an addon or gamemode that re-grants noclip independently of Sandbox, a player who is actually in an admin group you forgot about, or sv_cheats being left at 1 somewhere in your config. Check those three before anything else.
Where noclip control fits in your wider admin setup
Disabling noclip is usually one piece of locking down a public server. Once you’ve installed ULX or SAM for the noclip permission, you’ve also got the tools to deal with the players who were abusing it — see how to ban players from your Garry’s Mod server for vanilla banid/kickid commands and the admin-mod !ban equivalents. And if your server runs DarkRP or any addon that needs persistent storage, you’ll likely want to read up on adding MySQLoo to your Garry’s Mod server next.
Frequently asked questions
What’s the difference between sbox_noclip and sv_cheats for blocking noclip?
sbox_noclip is a targeted Sandbox convar that controls only whether players may noclip (0 disables, 1 enables). sv_cheats is a server-wide cheat switch that, when set to 1, unlocks every cheat command — noclip, god, give, impulse 101 and more — for everyone at once. Use sbox_noclip 0 to disable player noclip; never use sv_cheats for this.
Will sbox_noclip 0 stop my admins from flying too?
No — as long as your admins get noclip through an admin mod. ULX (!noclip / ulx noclip) and SAM grant noclip via permissions that bypass sbox_noclip entirely. Authorized staff keep flying while regular players are blocked.
Where do I put sbox_noclip 0?
In garrysmod/cfg/server.cfg, which the server auto-executes on every start, so the setting persists across restarts. You can also run sbox_noclip 0 in the live server console or over RCON to apply it immediately.
Do I need to restart the server after changing it?
Not necessarily. Editing server.cfg makes the change permanent and it applies on the next start, but running sbox_noclip 0 directly in the console or via rcon sbox_noclip 0 takes effect right away on the running server.
A player can still noclip even with sbox_noclip 0 — why?
Three common causes: the player is in an admin group with noclip permission; sv_cheats is set to 1 somewhere, unlocking the cheat command for everyone; or an addon/gamemode re-grants noclip on its own. Confirm sv_cheats 0, verify the player’s user group, and check your installed addons.
What key triggers noclip by default?
The noclip command is commonly bound to the V key in single-player and listen-server contexts, and it’s rebindable. On a dedicated server with sbox_noclip 0, pressing that key does nothing for a non-privileged player.
Summary
Disabling noclip on a Garry’s Mod server comes down to one line and one principle. Set sbox_noclip 0 in garrysmod/cfg/server.cfg to block regular Sandbox players from flying. Leave sv_cheats at 0 so you don’t accidentally hand the entire cheat menu to everyone. Then let an admin mod — ULX or SAM — grant noclip to your staff through permissions, which bypasses sbox_noclip cleanly. That combination gives you exactly what a public server needs: players grounded, admins flying, cheats off.
Ready to play?
Run your own Garry's Mod server with XGamingServer
Spin up an always-on Garry's Mod server your friends can join in minutes — no port-forwarding, no tech headaches.
