{"id":21385,"date":"2026-06-07T10:36:15","date_gmt":"2026-06-07T10:36:15","guid":{"rendered":"https:\/\/xgamingserver.com\/blog\/sbox-console-commands-concmd-convar-explained\/"},"modified":"2026-06-07T10:36:15","modified_gmt":"2026-06-07T10:36:15","slug":"sbox-console-commands-concmd-convar-explained","status":"publish","type":"post","link":"https:\/\/xgamingserver.com\/blog\/sbox-console-commands-concmd-convar-explained\/","title":{"rendered":"s&box Console Commands: ConCmd & ConVar Explained"},"content":{"rendered":"

If you come from Garry’s Mod or Source 1, s&box’s console works differently — there’s no big server.cfg<\/code> or fixed ConVar list. Instead, commands and variables are defined in C# with attributes, and you pass them on the launch line. Here’s how ConCmd and ConVar actually work in s&box.<\/p>\n

The big difference from Source 1<\/h2>\n

s&box has a deliberately small configuration surface. There’s no server.cfg<\/code> and no master ConVar list like the old engine. Anything you’d put in a config, you instead pass as a launch parameter when the server boots — those run as ConVars or ConCmds at startup.<\/p>\n

ConCmd — console commands<\/h2>\n

A [ConCmd]<\/code> attribute turns a C# method into a console command. The backend converts your string arguments to the method’s parameter types automatically:<\/p>\n

[ConCmd( \"greet\" )]\npublic static void Greet( string name )\n{\n    Log.Info( $\"Hello {name}\" );\n}<\/code><\/pre>\n
Add the ConVarFlags.Server<\/code> flag to force a command to run on the server, and make the first parameter a Connection<\/code> to know who<\/em> ran it — essential for admin commands.<\/p>\n
ConVar — console variables<\/h2>\n
A [ConVar]<\/code> exposes a value you can read and change from the console. ConVars take flags that can be combined:<\/p>\n