Vultr.com - Instant Cloud Server Deployment
TOYS IN THE ATTIC 63 MEMBERS:
Home
Forum
News
Share on Facebook
Share on Twitter
Share on Google+
Forum Home > scripts and cfg help > scripting 101 (part 2)
cybersquare420PM
#1
scripting 101 (part 2)
Jul 08, 2009 10:05 PM
{TIA}--DrPuffin'Kind--($$$) Founder - Joined: Nov 02, 2008
Posts: 332
Oh, you wanted to actually do something USING class configs? How about a simple rocket jump script for your soldier bound to the key you normally use for +attack2 in your other classes? No problem. Open up Soldier.cfg and put in the following AFTER that "exec autoexec.cfg" that you already put there:

code:
// Max Rocket Jump // =============== alias +soldier_maxrj "+duck; +attack; +jump" alias -soldier_maxrj "-duck; -attack; -jump" bind MOUSE3 +soldier_maxrj

Now what happens when you play the game, it all goes something like this:

1) TF2 started up.
2) autoexec.cfg was executed automatically (hence the name).
3) Inside autoexec.cfg, MOUSE3 was bound to +attack2.
4) You play as a Medic, and use MOUSE3 to fire your Ubercharge.
5) You die and pick Soldier.
6) soldier.cfg gets executed.
7) Inside soldier.cfg, autoexec.cfg gets executed again (binding MOUSE3 to +attack).
MOUSE3 is then bound AGAIN to +soldier_maxrj. Because it came after the bind command for MOUSE3 in autoexec.cfg, +soldier_maxrj takes precedence.
9) You pick a non-soldier class.
10) Autoexec.cfg gets executed at the top of any class, and thus MOUSE3 gets rebound to +attack2.

Any questions?

Ignoring all the "scripts are cheating" nonsense, I will say that the auto-pistol script is a good example of something that the console can simply perform much better than a human in just about all cases. In cases like this, it should be the game that is altered such that using the console is not an actual advantage.

Now, if you read that carefully, you'll notice that that does NOT mean disabling the use of the pistol script or any functionality used in said script to get the fast pistol shooting result. A better solution would simply to make holding down +attack fire just as fast as the fastest button mashing would yield in the game.

If that means they slow button mashing effectiveness down such that it matches the current state of holding down +attack, so be it (although that speed is pretty horrible in my opinion). I imagine a compromise in rate of fire would be the best course of action so that mashing a moderate speed now is as fast as it would ever fire... holding the button down or mashing it.