DiZaRkYs Script Compilation and Autoexec Guide

DiZaRkY’s Script Compilation and Autoexec Guide

In this post I’m going to add a compilation of scripts I’ve found from around the interweb and the steam forums. I’ll try and give credit where credit’s due, but if I fail, and you notice it, please tell me so I can correct it. Let me preface this by saying some of these scripts take the skill out of the game, and really should only be used for educational purposes. Don’t download or script skill, learn it! That is a much more rewarding way to play.

Well, with that out of the way here we go!

Know your config route!

First some basics that I want to mention. This guide utilizes your autoexec cfg. Know where this is so you can edit it, and also note that all other cfg’s will go in here. You can typically find this in X:\steamapps\(your username)\team fortress 2\tf\cfg (All cfg’s go in this folder)

• The “X” stands for whatever drive you have steam installed to, typically C.

• You may need to make the autoexec.cfg if it’s not there. To do this, make a new txt document with notepad, click save-as, in the drop down box where “text documents” is, click all files, enter autoexec.cfg as the save name, and save. It’ll make a new document called autoexec for you that has a cfg extension.

• With the exception of the autoexec, you can rename any cfg’s you have to make. Just make sure to update your script. Also, you can bind these to whatever key you please.

Ok, now for the fun stuff!

Setting up cfg’s to execute with your selected class.

Remember how in TFC you could use the setinfo "ec" "1" command to auto execute class scripts? Well you can’t here. So forget about it. Instead, add this to the autoexec.cfg. (Credit: Patty)

//CLASS ALIASES
Alias scoutcfg "exec scout.cfg"
Alias snipercfg "exec sniper.cfg"
Alias soldiercfg "exec soldier.cfg"
Alias demomancfg "exec demoman.cfg"
Alias mediccfg "exec medic.cfg"
Alias hwguycfg "exec hwguy.cfg"
Alias pyrocfg "exec pyro.cfg"
Alias spycfg "exec spy.cfg"
Alias engineercfg "exec engineer.cfg"

//CLASS BINDINGS
BIND "KP_END" "scoutcfg"
BIND "KP_DOWNARROW" "snipercfg"
BIND "KP_PGDN" "soldiercfg"
BIND "KP_LEFTARROW" "demomancfg"
BIND "KP_5" "mediccfg"
BIND "KP_RIGHTARROW" "hwguycfg"
BIND "KP_HOME" "pyrocfg"
BIND "KP_UPARROW" "spycfg"
BIND "KP_PGUP" "engineercfg"

This will make it so that every time you press the corresponding button, it will load that config for the class, which will set up your keys and activate your scripts. That does mean you’ll have to make the configs stated above, but that shouldn’t be an issue now.