OmniPrezident
The 47 Ronin
Hey guys,
As many of you know we use a separate file from our config.cfg file as a place or buy scripts or whathaveyou. This was my first time in doing-so, and needless to say, I ran into a bit of trouble.
If you've followed what seems to be the general consensus on how to create a autoexec.cfg file, and you are still having issues, this post is for you!
1. This tutorial worked fine for me, although where as he modifies the .cfg files with a notepad, I chose to dl a cheapo text editor. The TextPad demo works for what we need to do here. Your Notepad will work fine, but I found it easier to read the code with the editor.
TextPad 6
autoexec.cfg tutorial
Ok, you've written your script, saved it as autoexec.cfg, saved it in your CSGO Cfg folder, and you've added exec autoexec.cfg to your config.cfg file.
We're good to go. So, you boot CSGO and none of your settings in autoexec.cfg are uploaded.
Open the console in-game and execute the autoexec.cfg folder you've created to see if it will even upload your settings. This should work, if not, double-check the name/formatting of the file, and make sure you're using the correct command.
Assuming your autoexec.cfg file is in working condition, we can take a look at the config.cfg file and see what happened.
In my situation, I could add the line to execute the autoexec.cfg file, but each time I opened CSGO, closed the program, and looked at the config.cfg file, it had automatically reverted back to a more recently saved state, thus removing any/all modifications I made to it. Maybe someone here knows why, but I'm guessing it was Steam trying to repair the file after it had been modified.
This problem is rare, but if you run into it, here's what you do:
Open up config.cfg
Put the command exec autoexec.cfg (or whatever the heck you named your autoexec folder).
Save it, and close the program.
Right click on the config.cfg file you've just modified, and select properties, and set the file to Read Only.
SOLVED.
If any of you guys think setting your config.cfg file to read only is a bad idea, let me know!
As many of you know we use a separate file from our config.cfg file as a place or buy scripts or whathaveyou. This was my first time in doing-so, and needless to say, I ran into a bit of trouble.
If you've followed what seems to be the general consensus on how to create a autoexec.cfg file, and you are still having issues, this post is for you!
1. This tutorial worked fine for me, although where as he modifies the .cfg files with a notepad, I chose to dl a cheapo text editor. The TextPad demo works for what we need to do here. Your Notepad will work fine, but I found it easier to read the code with the editor.
TextPad 6
autoexec.cfg tutorial
Ok, you've written your script, saved it as autoexec.cfg, saved it in your CSGO Cfg folder, and you've added exec autoexec.cfg to your config.cfg file.
We're good to go. So, you boot CSGO and none of your settings in autoexec.cfg are uploaded.
Open the console in-game and execute the autoexec.cfg folder you've created to see if it will even upload your settings. This should work, if not, double-check the name/formatting of the file, and make sure you're using the correct command.
Assuming your autoexec.cfg file is in working condition, we can take a look at the config.cfg file and see what happened.
In my situation, I could add the line to execute the autoexec.cfg file, but each time I opened CSGO, closed the program, and looked at the config.cfg file, it had automatically reverted back to a more recently saved state, thus removing any/all modifications I made to it. Maybe someone here knows why, but I'm guessing it was Steam trying to repair the file after it had been modified.
This problem is rare, but if you run into it, here's what you do:
Open up config.cfg
Put the command exec autoexec.cfg (or whatever the heck you named your autoexec folder).
Save it, and close the program.
Right click on the config.cfg file you've just modified, and select properties, and set the file to Read Only.
SOLVED.
If any of you guys think setting your config.cfg file to read only is a bad idea, let me know!