.cfg's are basically text files with some commands in them. They execute the commands in order from top to bottom, and if you find yourself always typing the same stuff over and over again, you can stuff them into a script that automates it for you.

So let's get to it.

They are in your Insurgency folder, tucked under insurgency\cfg\.

For those of you on Windows with default installs, the full path would look something like this:

For Mac players, in the Finder press Apple + Shift + G to open the "Go to Folder" dialog. Alternatevely, in the Finder you can click "Go" in your menubar at the top and select "Go To Folder" and paste this in:

That should work, I don't have a Mac with Steam to doublecheck but based on my past experience it should do the trick.

Linux people? You probably already know where your game is. If you don't, sorry but neither do I. I never touched the stuff.

They are simple text files, but instead of ending in .txt, they end in .cfg.

So just use your basic text editor (Notepad for PC, TextEdit for Mac) and make a text file and save it to the correct location.

If you are doing this on a Mac, make sure you're making a plain text file, meaning it doesn't have fonts or styling in it. To make sure it's plain text, click Format in the menubar and select Make Plain Text, or press Apple + Shift + T.

Simply throw the commands you want in there, one per line, and save it to the appropriate location above. Make sure that instead of ending in .txt, it ends in .cfg, and you'll be good to go.

This is perhaps the easiest part. Press ~ to bring up your console, and use the exec command.

If you named your file, say.... takbir.cfg, you'd enter this command:

And it will execute the commands in that file.

But keep in mind some files are executed at the main menu, like the weapon penetration cfg, while others are executed while you are in the server... like the one for checking server options. You obviously can't check server settings until you are in one, right?

Some servers are setup differently. Sometimes you can harm your teammates, and other times you can't. Some servers let you type to alive teammates when you're dead, and some don't.

Luckily, there's a way to check the most common stuff with a simple .cfg file!

I call mine options.cfg and it contains these commands:

Execute this command using the exec command at any time when you're in the server, and your console will fill up with the current values.

Each of those commands will return a value of 1 or 0, except for the last one.

• mp_friendlyfire - This one tells you... as you guessed it... if there's friendly fire in the server! This is usually what I check for. Lets me know if explosives can be used more freely or not.
  
• sv_deadvoice - Can dead players speak to the living?
  
• sv_deadtalk - Can chat messages from dead players be seen by living? This means global chat, not teamchat. So the other team can see the messages too from the dead player.
  
• sv_deadtalk_team - Can dead players use teamchat to speak to the living? The other team won't be able to see.
  
• sv_hq_messages_allowed - This one tells you if "HQ messages" are enabled. These are the audio cues you hear when an enemy enters the objective you're currently on ("Enemies in Bravo!") and stuff like that. Some servers disable it, most leave it on. But it's nice to know which is which before you get yourself shot.
  
• sv_maxcmdrate - By default, this returns 64 meaning its a 64 tick server. But some servers run at 128 tick, which gives smoother and more responsive gameplay. To fully take advantage of 128 tick servers though, you need to set your own tickrate to 128 following the instructions below...

To fully take advantage of those 128 tick servers, you need to tell your game that it's possible to update that much. Don't worry, it won't cause any ill effects for 64 tick servers.

In your autoexec.cfg file (if it doesn't exist, make it), enter this:

There are other things you can put in that file to execute @ launch, but I'm not a big autoexec guy and that isn't the purpose of this guide. I'll let you find the best autoexec for your needs elsewhere (some people use it to change gfx settings really low to increase fps, etc.).

This is the fun one! Ever wonder what you can and can't shoot through, and how much damage comes out the other side?

One small fact that alot of players don't know is that you can shoot through the corners and edges of walls that you otherwise can't shoot through. I made a short video to show my friends about it, using the .cfg I'm about to give you below.

Place these into a .cfg file, I used "damage.cfg" for mine but you can name it whatever you want.

An explanation of each command...

• ins_bot_quota 0 - We don't want no bots interrupting us, do we? This may not be needed, but better safe than sorry.
  
• sv_cheats 1 - The rest of these commands only work under cheat mode, which means that you can't enter these online and use them against other players. I mean, you can try, and nothing bad will happen... but unless the server has enabled cheat commands on their end (for everybody), the commands simply won't work. But even though we are loading a map offline, and playing with ourselves (kek), we need to enable cheat commands anyway.
  
• sv_showimpacts 1 - This will show big blocks where your bullets hit, and if they pass through stuff.
  
• sv_showimpacts_time 20 - By default, impacts will show for only 4 seconds. But what if you want to run around to the other side of the wall and see what happened? This extends it to 20 seconds.
  
• sv_showdamage 2 - This will display the damage levels after you shoot through stuff. You'll notice quickly how much the damage dropoff is when shooting through cover... 100 damage going in, usually 10 or so coming out on the other side. This means if you do shoot through cover, you need to be accurate and you need to hit them alot of times. Not just 1 or 2 extra shots like in Call of Duty, but maybe 5 or more.

At the main menu, we execute our cfg then load a map like this...

But what if you want to test a certain spot on a map that's only reachable on a certain mode, like Station Push? The map command lets you specify a mode too, just add it after the mapname seperated by a space like so...

Some other useful console commands for testing are...

• give_weapon - This gives you a weapon, dummy. After you hit a space after the command, the autocomplete kicks in and gives you a list of weaponnames. Start typing the name of the weapon and it'll do a pretty good job of giving you the full name of it.
  
• give_ammo 99 - Sometimes 2 or 3 mags aren't enough. So let's say we want 99 mags or whatever, and it'll load us up with enough lead to really have some fun.
  
• noclip - This one toggles on/off. So entering it will turn it on, entering it again disables it. You can use this to fly around and through stuff, if you want to see how much damage reached its target if it's too far away.

There's also a way to test between HP and AP ammo using the console command, but I find it's easier just to switch to that team sometimes and do it the old fashioned way by pressing M to bring up the inventory menu.

When you're done just join a server, the server blocks all the stuff you just entered so don't worry about resetting stuff.