I'm gonna be honest, there are a LOT of console commands. Way too many to fit into a reasonably sized steam guide. Instead, I've decided to put the basic commands right here, and the extras in the complete list you can find here[www.reign-gaming.co.uk]

As of this moment, there are 4 categories, as you can see on the guide. Each category has approximately 6 basic examples here, with a range of 8-16 commands in the full list. The full list is being updated and added to, so those numbers will be increasing.

The multiplayer, mp commands, are used when you want to change settings for the gamemode. These are good when you want to set up a custom gamemode, when you want to change one variable, or if you want to make your own gamemode all together. Basically, these are all the commands that affect the gamemode directly. For the sake of not making the steam guide ridiculously long, you can find the rest of the mp commands in the list at our website[www.reign-gaming.co.uk]




Usage: mp_warmup_end
Description: Yeah, it's just how it sounds. It ends the warmup.



Usage: mp_restartgame <0,1>
Description: Yup, set it to 1 to restart the game, and set it to 0 to.... not restart the game. Obviously, this is defaulted to 0.



Usage: mp_repawn_on_death_ct <0,1>
Description: 0, ct's don't respawn. 1, they do.



Usage: mp_repawn_on_death_t <0,1>
Description: 0, t's don't respawn. 1, they do.



Usage: mp_friendlyfire <0,1>
Description: Enable or disable friendly fire. If you don't know what that is, it means can you or can't you damage your teammates.



Usage: mp_solid_teammates <0,1>
Description: Enables or disables team collide. Basically, if the teammates are solid, you can't go through them. If they aren't you can. O_o

The sv, server commands, are the ones that affect the server, or indirectly affect the gamemode. Within this list I've also included client side commands, like name, say, or the stuff that is set on the client that the client must tell the server. Many of these commands require sv_cheats to be set to 1.




Usage: sv_cheats <0,1>
Description: Activate cheat commands, defaulted to 0. A cheat command is defined as an sv property, or a server property, or an mp property, or anything that's disabled on valve competitive servers. Setting to 0 restores them to disabled.



Usage: sv_showimpacts <0,1>
Description: Shows where your bullets hit, if it hits a playermodel it leaves the hitbox displayed with where it was hit. It will disappear after a bit.



Usage: sv_grenade_trajectory <0,1>
Description: Shows the path of the grenade, leaves a green trail where it's been and shows where it bounces. Useful for practicing throws so you know how exactly to correct yourself



Usage: sv_infinite_ammo <0,1>
Description: This one's pretty obvious, 1 for infinite ammo (never lose ammo, you don't need to reload), 0 for finite ammo



usage: noclip
Description: Toggles noclip. Most useful if it is bound to a key. I use 'p' on my keyboard for noclipping when I'm offline.



Usage: god
Description: Toggles god mode, which means you can't be killed.

These are all the commands that you really need to know when using GOTV, when you're looking at changing voice and sound in game, and when spectating. I threw all these together because, well, there's not too many that you really NEED to know.



Usage: voice_enable <0,1>
Description: Turns on and off voice chat in game. What?!? I don't have to listen to annoying kids when I'm warming up on deathmatch? AWESOME



Usage: demoui
Description: Toggles the ui for the demo, which basically just gives you the following commands in the user interface form. Pretty self explanatory.



Usage: demo_pause
Description: Pauses the demo. If you type it again, it doesn't resume, you'll need to use demo_resume.



Usage: tv_enable <0,1>
Description: Enables or disables GOTV



Usage: tv_nochat <0,1>
Description: 1 for no chat in GOTV, 0 puts it back.



Usage: spec_show_xray <0,1>
Description: defaulted to 1 (usually) which means you have xray when spectating. 0 means you don't. This only does anything when spectating.

If you're playing offline with bots (or dealing with bots on a server), these are the commands that are helpful to deal with the bots. This is, of course, the smallest list, because there's really not that much you need to do with bots. There's not a whole lot that you really do need to know, so I have all the basic commands here. As I myself learn and add the more complicated bot commands, they'll be added to the complete list but not here. Right now, these are all the commands I have in this section.




Usage: bot_kick <team (t, ct)>
Description: It does just what it sounds like, it kicks ]bots from a game. When you don't have a value for the team, it kicks all bots in the game which is good if you want to play with friends on a private server.
When you do have a value for the team, it kicks a single bot from the team designated.



Usage: bot_add <team(t, ct)>
Description: Again, much like it sounds it adds a bot to the designated team. If you don't specify a team, it will go to the team with fewer players, or will randomly assign itself to a team.



Usage: bot_difficulty <integer value(0,1,2, 3)>
Description: Changes the difficulty of bots added to the game. This will NOT change the difficulty of bots already in the game. You can afterwards use the kick command to kick the bot by name, which will just replace it with a new bot of the new difficulty setting. The values are 0 (easy), 1(normal), 2 (hard), and 3(extreme).



Usage: kick <player name>
Description: You can use this to remove a player from your game by name. When you use this for bots you enter the bot's name (do not include the word BOT), and it will replace that bot with a new bot with a different name.



Usage: mp_autoteambalance <0, 1>
Description: I'm sure most of the people here will know this, but 0 means false, and 1 means true. What this means is that when the value is zero, auto team balance is false, or off. Meaning if you wish you can stack teams so you can 1v5 with bots, without the game always balancing the teams. When the value is set to 1, it returns to true, or on. That just means the game will once again balance the teams automatically.



Usage: mp_limitteams <Integer Value>
Description: This command controls the stacking of teams. Yes, you'd think autobalance would be it, but this command also keeps you from having stacked teams. The default value is 2, which means at any given time a team can only have 2 more players than the other team. Set the value to 0 to turn it off completely, otherwise the value you enter is the number of players you can have on each team.
NOTE: Each team can only have 1/2 the total number of players allowed on the server. This is dependent on the gamemode you started in.



Usage: bot_freeze <0,1>
Description: When the value is set to 0, bot freeze is off and allows bots to move again. This is the default. When you change it to 1 bots freeze and remain in place.
NOTE: This command doesn't seem to work on it's own. You need to use bot_freeze 1, then bot_zombie 1, then bot_freeze 1 again. This will, unfortunately, make them zombies in addition to being frozen.



Usage: bot_zombie <0,1>
Description: 0 turns this command off, is the default. When you turn this on with bot_zombie 1, bots will act like zombies. They will not shoot you, but will follow you.

Thank you for checking out this guide. If you notice a useful command that isn't on the list, please comment it below and I'll get it in! Please don't suggest adding anything if you haven't checked out the full list. If you missed the link at the top, and you're too lazy to scroll back up (I feel you). You can find it by clicking right here[www.reign-gaming.co.uk]

While you're there, feel free to check out the rest[www.reign-gaming.co.uk] of our website. If you have any questions, or need help with anything, you can go to our forums, comment, or add me on steam. Thanks again, and enjoy the rest of your day!