Novice Guide to "Fast Knife"

[TurbanError]

Because it was asked of me, and I have thought about adding this topic to the zombie bomb forum in the past; I wanted to go over a feature in Zombie Bomb, ts, and Super ts.  Namely, the ability to use your knife quickly, without the limitations of the knife animation.  This is a feature in the named servers, and will not work in all servers.  I will do my best to explain this as plainly and concisely as possible (starting with the simpilist of idea, and working to more complicated). 

So how does one get a fast knife?

Scrolling

Spoiler:  All About Scrolling (click to show/hide)

The first method and easiest is often referred to as scrolling.  This method involves setting your attack to your scroll wheel up or down (that's scrolling upward or downward).  Every time you feel a bump when you scroll your middle mouse button, the game will register as an attack.  So, when you have a knife in hand you may attack very fast. 

To set this up is incredibly easy. 

Method 1:
In the URT Client, go to setup>Shoot> and click on the words next to attacks (it is most likely set to mouse 1) and scroll up or down on your scroll wheel. 
*The direction is important to remember
**If your next/previous weapon (a few below shoot) is set to Mwheelup or down, you will need to bind that to another key.

Method 2:
Open up your console "~" and type in /bind mwheelup "+attack;-attack;"

Scripting

Spoiler:  All about Knife Scripts (click to show/hide)

Scripting can seem like a complicated process but it is actually quiet easy.  Scripting involves binding a key to run more than one command at a time.  The main benefit of scripting is called recursive scripting, that is setting a button to execute one type of command and then changing the command upon completion.  Further reading on scripting check this out.

The basic premise is to set a key to do multiple attacks at the push of a button.  To do this you will need the +attack and -attack commands.  Think of these commands as an on/off.  For spamable weapons, like autos, holding down the mouse keeps you sending the +attack command lifting your finger up sends the -attack command.  The same +/- commands can be used for buttons (thinking button down or up.  Now the knife is a weapon that needs you to push the button down than up to get a single slash.  So the basic "fast knife script" looks something like this:

/bind X "+attack; -attack; +attack; -attack; +attack; -attack; +attack; -attack; +attack; -attack;"

((Where X is any button you see fit)). 

This binds a key that will give you 5 +/- attacks per single button push.  However, there are only so many commands urt client/server can resolve.  Do too many commands too quickly, and they simply wont happen.  So if you run the basic script provided, you won't get all 5 attacks on a single mouse click.  To slow down these commands we will use the "wait" command.  The wait command will pause the commands your sending for a certain amount of time MEASURED IN FPS. 

Spoiler: why fps is important (click to show/hide)

FPS is important for a variety of reasons.  The first is that everything in the game is measured in fps.  You want to have a stable fps at a specific number to send a full packet of information (even though it happens so fast, that small delay in sending commands to the server can mean life or death).  So in my book a stable lower fps> higher unstable fps.  Here is a link to the FPS plateaus, you want to limit your fps at to send full packets.

So, for those of you who do not play at a stable max of 125 fps, you will want to test your wait times to see what works for you.  For 125 I often use a wait time of 9, without losing many knife stabs.  lowering the wait time means faster stabing, but also the risk of dropping stabs from sending too many commands to the server (which is what you want to avoid, since that means having wait time without a stab).

The downside to knife scripts are the wait time.  Wait time prevents you from doing ANYTHING.  No adding momentum, no adding movement, no item switching, until the entire script + wait time is done (it essentially freezes all other commands).  Many people prefer scrolling because you don't need a wait time.  That doesn't mean you only need to bind your wheel up to a single attack.  Try /bind mwheelup  "+attack; -attack; +attack; -attack;" for twice as many attacks while scrolling without the wait time.

So if we add in wait times, our bind/script looks like this:
/bind X "+attack; -attack; wait 9; +attack; -attack; wait 9; +attack; -attack; wait 9; +attack; -attack; wait 9; +attack; -attack;"

((Where X is any button you see fit)). 

So, you stabbed a bit, got excited, your zombie game improved by 100%, but everything else that relies on the attack command (switching in spec, autos) you now lack control over.  So what do you do? 

Organization and Implementation

Spoiler: organization (click to show/hide)

Method 1:
One idea is to set a recursive script for the number 1 key to bind your knife script to mouse 1 any time you hit 1, and then return to normal upon hitting 1 again.  That should look like this:

//Fast Knife Script
set attackspeed1 "weapon 1; bind MOUSE1 "+attack; -attack; wait 9; +attack; -attack; wait 9; +attack; -attack; wait 9; +attack; -attack; wait 9; +attack; -attack"; set attackspeed "vstr attackspeed2";"
//After hitting 1 you have you switch to your knife and have your fast knife script, REMEBER TO CHANGE THE WAIT TIME BASED ON YOUR FPS
set attackspeed2 "weapnext; bind MOUSE1 "+attack"; set attackspeed "vstr attackspeed1";"
//Hit 1 again and you go back to normal and your previous weapon
set attackspeed "vstr attackspeed1"
bind 1 "vstr attackspeed"

So, pretty straight forward, but not perfect for the differences in zombie ts or bomb, where throwing knives are very useful.  Not to mention I have a few scripts I use as a human that I wouldn't as a zombie. 

Method 2:
So the second method (and method I ascribe to) is to make two seperate config files that can bind keys by the push of the button.  In this example I made two new files in the q3ut folder called human.cfg and zombie.cfg.  To switch between those two cfg I have a small script in my autoexec.cfg.   It is very simple, and looks like this:


//Main zombie, human switch
bind z "exec zombie.cfg; ut_echo "Zombie Mode Activated";"
bind x "exec human.cfg; ut_echo "Human Mode Activated";"

Then within the human.cfg you can put whatever you like.  For this example we are going to put in a very simple field of view script ((to change the field of view and sensitivity while scoping in to give a mini zoom in on pressing mouse 2)).  Note: I also bound the N key to change weapon modes, the reason for this is once you bind that ability to another key (which we will do in the zombie setup) and then take that command away (by changing what mouse2 does in the human setup), it does not default back to any value.  So here is what a human.cfg will look like without my weapon selection binds.

Spoiler: Human.cfg (click to show/hide)

//Human.cfg
Set cg_fov "110"

bind MOUSE1 "+attack;"

bind n "+button3; -button3;"

set zoom1 " ut_zoomin; cg_fov 90; set zoom "vstr zoom2";"
set zoom2 " ut_zoomreset; cg_fov 110; set zoom "vstr zoom1";"
set zoom "vstr zoom1"
bind MOUSE2 "vstr zoom"

Alright, so humans are setup lets look at zombies.  Now we want a script that will change our attack from the fast attack to normal when we change to a throwing knife.  To do that, we will make another script that will have our two weapon attack speeds bound to mouse1 (normal, and +/-;wait).  We will then write another script that changes these stats as we change to our throwing knife.  That looks something like this:

Spoiler: Zombie.cfg (click to show/hide)

//zombie.cfg
Set cg_fov "110"

//faster knife

set knifestab1 "+attack; -attack; wait 9; +attack; -attack; wait 9; +attack; -attack; wait 9; +attack; -attack; wait 9; +attack; -attack;"
set knifestab2 "+attack; -attack;"
set knifestab "vstr knifestab1;"
bind MOUSE1 "vstr knifestab;"

//Toggle zoomin and knife throw
set knifethrow1 "+button3; -button3; cg_fov 90; set knifestab "vstr knifestab2"; set knifethrow "vstr knifethrow2";"
set knifethrow2 "+button3; -button3; cg_fov 110; set knifestab "vstr knifestab1"; set knifethrow "vstr knifethrow1";"
set knifethrow "vstr knifethrow1"
bind MOUSE2 "vstr knifethrow"

understanding this script will help you use it (it is easy to get your attack state -fast or regular- confused).  Remember that with this method you can always go back to the z or x key and reset your binds back to normal.  Since this is the method I ascribe to and you have been a great audience (assuming you have read this all the way through) I have attached the needed files to drop into your q3ut4 folder without you needing to open up your text editor at all.  Human mode is bound to X, Zombie Mode is bound to Z.  Test it out, see what you think, figure out what works for you.

If your getting a index.php on the attachement just rename it to what the file should be or download from here:
http://www.mediafire.com/?5lnzli0v7i9ndic

[Replay]

Nice, but I already have the best knife script for my fps

[Gautch]

Yay for Turban

[BoBThEImaM]

Lol doesnt seem like much until u hit those spoilers, then, holy crap thats a lot .  Good work but already got my knife perfect.

[Replay]

Lol doesnt seem like much until u hit those spoilers, then, holy crap thats a lot .  Good work but already got my knife perfect.

Whats your fps?

[BoBThEImaM]

91-92

[SnKcoffee]

Why not just use a mouse with scripting? This way you can use a wait command and it won't stop all input in urt. The problem is cooking nades, but there are probably work arounds. This is probably illegal in most leagues.

[TurbanError]

Why not just use a mouse with scripting? This way you can use a wait command and it won't stop all input in urt. The problem is cooking nades, but there are probably work arounds. This is probably illegal in most leagues.

Well, this wouldn't for league play because your knife is limited to the normal attack animation in league play.  What I described is how to utilize a feature of the 1upservers.  If you look under the organization and implementation spoiler you will notice that I address the issue of using a bind button to switch your binds mid game (like a toggle, on/off) so you would be able to cook your nade and fast knife when needed. 

You are correct, using a mouse that has form of auto scroll or scripting language, would be an advantage over the wait commands.  Since, I personally do not own such a mouse (nor my drivers support that) I explained how to do it with only the urt client.

[Wargasm]

Ugh, hate the fact that zombies can scroll knife or script on 1up zombie servers. I don't want to be a whiny *****, but I will for the sake of expressing myself lmao. People who argue that taking it out would screw zombies don't realize that blue can always be nerfed to compensate. Not to mention it could be taken out and the game would still prob be balanced.

[Zhalix[1up]]

No.

[BoBThEImaM]

Scrolling is fine tbh.  And The servers are pretty balanced atm...

[rondonboy]

I'm gonna stick to good old scrolling

[Wargasm]

Lol I got -2 karma for criticizing 1up servers for fast knife..

[TurbanError]

Better add some karma   

I do understand the criticism of fast knife, since not everyone knows how to do it, it makes a vast gap when determining balance.  But it is also one of the fundamental parts of the zombie server.  Someone correct me if I am wrong, but it is my understanding that both zombie servers are/were originally set up so that zombies shouldn't have to worry about aim, only getting to the enemy, while humans need to be more skilled at shooting specific body parts and running for there life.  Zombies mindless, Humans mindful.  So in that regard, I enjoy fast knife.  Also it doesn't feel like a nerf bringing a knife to a gun fight.

Hopefully those who are using a basic knife will see this and take a bit of time figuring out what works for them.  I feel like playing without it, especially in bomb, you become a living pinball people just push around till death.

[Wargasm]

I agree, but with scripting I feel that you take away another facet of concentration zombie players don't have to worry about so they can put all their energy into look the direction of their enemy and jumping to catch their enemy.

I would say that it is an APM factor or "actions per minute". It is commonly referred to in Starcraft because players with high apm often have the ability to concentrate on several things at the same time and maintain upwards of 200+ apm. Why does this matter with zombie mode? Humans probably need to master several times the apm of a zombie player, switching between weapons, aiming at body parts, cooking grenades, jumping and evading zombies while doing all that. Zombie players with a knife script essentially have to do two things. Jump to reach the enemy, and look in the general direction of the human prey. That makes it that much easier for zombies as they don't have to do as much multitasking, they can focus on just killing.

Lol, I came back and lost another -2 karma. I don't understand who would do such a thing to me for voicing an opinion?