stillcamping.blogg.se

1. #How to make an autoexec file tf2 how to#
2. #How to make an autoexec file tf2 update#
3. #How to make an autoexec file tf2 code#
4. #How to make an autoexec file tf2 professional#

Typical location for this file on most computers would look like that: C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\csgo\cfg\autoexec.cfg You can find the configuration file inside your Counter Strike installation directory. Example Of Autoexec Config File For CS:GO Autoexec Config Location Your autoexec would be there to make sure your sensitivity stays 2 at all times.

#How to make an autoexec file tf2 update#

Then you wouldn’t have to worry about your settings being reset or deleted with, for example, an update to the Counter Strike game.

#How to make an autoexec file tf2 professional#

This would set your in-game sensitivity to value of 2, which is approximate average of all the professional CS:GO players. For example, you could have this simple command inside your autoexec file: sensitivity 2

Once created, it will be run every time you start up CS:GO. In simple terms, it’s a text file that contains all the commands, that tell the game what should be set in a way you want it to. One of the important things to look into is autoexec config file. In our case it is a properly configured game, with all the settings set to commonly known standards. There are so many things you can improve to become better player. Thanks for your time! I know this wasn’t an amazing tutorial, but I am working on another.Counter Strike Global Offensive is a fantastic game, where skill ceiling level is practically infinite. But If your making a really big config or edit something like windy’s config I would do it. So i don't need to do this?No, you don't need to split your files if you don't want to. Then edit it! The bonu is that you don't have to scroll through 50+ lines of scripts that you don't care about! It just makes things easier on you. If you want to edit a certain file or script you can just find the file that contains it. OK! It works now! But what if I want to edit a file?This is the beauty of making multiple files.

So if you put exec “script file name here” into the autoexec file, it will act like if it was in the autoexec file itself! But if you move the scripts into separate files they don't get ran! But there is an easy fix! The exec command allows you to run any file in your cfg folder. The autoexec file is ran at the beginning of the game so the alias commands don’t ever really go away. But it won’t work!The reason why you put anything in your autoexec file is because alias commands get forgotten at the restart of each game (opening and closing TF2). So a zooming and a viewmodel hiding script would be in the same file. But if I have multiple, similar, small scripts I usually put them in an overarching file. this is what i'm here for! I usually do either 1 very long/complicated scripts in separate files. But if your a serious scripter future you will thank present you. Of course you don’t need to split your files. If you can understand it, then that's great! But if your posting scripts and tutorials to gamebanana you need to have it readable and organized! So having 20 different scripts in your autoexec.cfg file isn’t that good of an idea.

#How to make an autoexec file tf2 code#

I'm not an actual programmer but I know enough so that I can keep my code organized and readable. It seems strange why someone would split files for the sake of splitting files but this isn’t just for fun. So here I am with another tutorial!īut why should I split up my files?Ok, ok.

#How to make an autoexec file tf2 how to#

Now i've seen some messy autoexec.cfg files in the past but I feel like I need to explain how to do this. Hello! Its me again! And today i'm back with how to split up your config files.