Novice Guide to "Fast Knife"

[AuXAuV]

The "set" command defines a step in a recursive script. 

Wrong.
First off, it's not recursive, it's just looped, USUALLY.
Second, it's just a variable, that may be a step in a script.

[(DEAD) Revolution]

thank you TurbanError[1up] for the:

Code: [Select]

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

In your human.cfg file:

Code: [Select]

//Normal Weapon Scrolling
bind MWHEELUP "weapon prev;"
bind MWHEELDOWN "weapon next;"

In your zombie.cfg

Code: [Select]

//Fast knife Scroll
bind MWHEELUP "+attack; -attack; wait #; +attack; -attack;"
bind MWHEELDOWN "+attack; -attack; wait #; +attack; -attack"

i did have a look at http://www.urbanterror.info/support/108-/ before i posted on this. some use, except it doesnt tell you how to link the z and x with two completely different scripts.

ok lets just say all the scripts above, i copied and pasted it into the autoexec.cfg under the file urban terror. i still get the feeling that when i pressed z the system will say 'zombie more activated' but will not change the mwhweel to attack. why? because the part of the script where it links them together is missing. so far in your words, i now have the mwheel and the z and x sorted out. but what i didnt sort out yet is how these two are linked. (there is no script for that)

and the part about the #, that i should put in a number depending on my fps, if my ingame fps was 94, what number should i put in the #?... 94??

PS. on your next post could you put in the complete codes for me to just copy and paste into the autoexec.cfg and will just work? remember, (press z. system says zombie mode activated. mousewheel up and down becomes attacks..... press x. system says human mode activated. mousewheel up and down switches weapons) could you put in ONE BIG, COMPLETE code to make this happen? thank you.

[AuXAuV]

A block of code, alright.

Code: [Select]

bind x "vstr n_tog"

//Do not change anything below this line unless you know
//what you are doing.

//Declare settings
//---------------------------------------------------------------------------
seta zombie_m1 "weapnext"
seta zombie_mu "+attack; -attack; wait 1; +attack; -attack"
seta zombie_md "+attack; -attack"

seta human_m1 "+attack; set next_mouse1 vstr zombie_mouse1"
//Note: swap weapnext/weapprev if desired. Not everyone
//goes the same way.

seta human_mu "weapnext"
seta human_md "weapprev"
//---------------------------------------------------------------------------

//---------------------------------------------------------------------------
seta m1 "vstr human_m1"
seta mu "vstr human_mu"
seta md "vstr human_md"
//---------------------------------------------------------------------------

//Set the binds for mouse control.
bind MOUSE1 "vstr m1"
bind MWHEELUP "vstr mu"
bind MWHEELDOWN "vstr md"

//Set toggle
seta tog1 "set m1 vstr zombie_m1; set mu vstr zombie_mu; set md vstr zombie_md; ut_echo ^1Zombie ^7Mode Active.; set n_tog vstr tog2"
seta tog2 "set m1 vstr human_m1; set mu vstr human_mu; set md vstr human_md; ut_echo ^4Human ^7Mode active.; set n_tog vstr tog1"
seta n_tog "vstr tog1"

Pressing "x" (or whatever you change it to)
Will swap your controls.
Copy this into your autoexec.cfg if you want.

(controls:
Human Mouse1 fire, mwheel to swap weaps.
Zombie Mouse1 next weapon, mouse wheel to attack)

[Term]

A block of code, alright.

Code: [Select]

bind x "vstr n_tog"

//Do not change anything below this line unless you know
//what you are doing.

//Declare settings
//---------------------------------------------------------------------------
seta zombie_m1 "weapnext"
seta zombie_mu "+attack; -attack; wait 1; +attack; -attack"
seta zombie_md "+attack; -attack"

seta human_m1 "+attack; set next_mouse1 vstr zombie_mouse1"
//Note: swap weapnext/weapprev if desired. Not everyone
//goes the same way.

seta human_mu "weapnext"
seta human_md "weapprev"
//---------------------------------------------------------------------------

//---------------------------------------------------------------------------
seta m1 "vstr human_m1"
seta mu "vstr human_mu"
seta md "vstr human_md"
//---------------------------------------------------------------------------

//Set the binds for mouse control.
bind MOUSE1 "vstr m1"
bind MWHEELUP "vstr mu"
bind MWHEELDOWN "vstr md"

//Set toggle
seta tog1 "set m1 vstr zombie_m1; set mu vstr zombie_mu; set md vstr zombie_md; ut_echo ^1Zombie ^7Mode Active.; set n_tog vstr tog2"
seta tog2 "set m1 vstr human_m1; set mu vstr human_mu; set md vstr human_md; ut_echo ^4Human ^7Mode active.; set n_tog vstr tog1"
seta n_tog "vstr tog1"

Pressing "x" (or whatever you change it to)
Will swap your controls.
Copy this into your autoexec.cfg if you want.

(controls:
Human Mouse1 fire, mwheel to swap weaps.
Zombie Mouse1 next weapon, mouse wheel to attack)

I don't know whats wrong with this but human mode doesn't work. The only way to fire your weapon is to hit t then hit enter or to open the console and close it again. Also when you do that to get the weapon to fire it never stops.
Just keeps on firing until the clip/slip is unloaded and just keep dry firing. You can't even change weapons after you fire the one time.
 

[TurbanError]

The "set" command defines a step in a recursive script. 

Wrong.
First off, it's not recursive, it's just looped, USUALLY.
Second, it's just a variable, that may be a step in a script.

When else would you define a variable in urt?  Usually when your defining a step in a recursive script.  Guides to scripting call them recursive scripts, there is no need to change terminology, especially when recursive and loop are so similar.

and the part about the #, that i should put in a number depending on my fps, if my ingame fps was 94, what number should i put in the #?... 94??

This will take some trial and error on your part.  I run fps 125 and have my wait at 9 with no command dropping.  Since your scrolling, it is ok to have some commands drop, since you don't NEED the wait time.  If my math is right, somewhere around 6 will leave you with no dropped commands, but even try it without wait time and see if its your thing.  Trial and error.

PS. on your next post could you put in the complete codes for me to just copy and paste into the autoexec.cfg and will just work? remember, (press z. system says zombie mode activated. mousewheel up and down becomes attacks..... press x. system says human mode activated. mousewheel up and down switches weapons) could you put in ONE BIG, COMPLETE code to make this happen? thank you.

Everything you need is in my previous post for you to copy and paste for what you want. My bind setup is on the first post for dl and you can just drop into your q3urt folder.  My code is slightly less complicated than ruusan's block of code (which I assume is more of a joke, term).

You need 3 separate files.  Your auto exec, your zombie.cfg and your human.cfg as explained in the first post.  When the game loads it will load your autoexec.cfg by default but not the other two.  Your auto exec has a key bound to running one of the other cfg files (which in turn changes your binds).

the command: /exec "name.cfg"

Runs a script that has the name.cfg.  If you were to type in /exec "autoexec.cfg" the autoexec binds would be loaded (when urt starts, this is part of the commands that happen when urt starts).  Instead of typing that in the console I bound them to a key (since you will be switching back and forth), namly z and x.  This is the reason bind x "exec human.cfg;" is in your auto exec.  This is also why you have two separate cfg files to easily overwrite your current binds with which mode (zombie or human) you want to be in.

Hopefully this makes sense, the code that you want are already there.  Otherwise you can wait till after January 5th and chat with me on ts3.

[TurbanError]

thank you TurbanError[1up] for the:

Code: [Select]

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

In your human.cfg file:

Code: [Select]

//Normal Weapon Scrolling
bind MWHEELUP "weapon prev;"
bind MWHEELDOWN "weapon next;"

In your zombie.cfg

Code: [Select]

//Fast knife Scroll
bind MWHEELUP "+attack; -attack; wait #; +attack; -attack;"
bind MWHEELDOWN "+attack; -attack; wait #; +attack; -attack"

Note this current script is missing +attack bind for huaman mode.  Which means human mode doesn't have a method to fire a weapon. 

Note: We rebind +attack as the key it would have been bindined to (wheelup/down) is no longer bound to that in human mode.

Each cfg file overwrites the previous one.  When you set your scroll to attack it takes that function away from any other button that had it and then you overwrite that to be previous and next weapon, you essentially leave the attack command floating in the abyss.  It doesn't rebind to mouse 1, which is why that is in human mode.

[ShadowSkittles]

"Novice Guide to Fast Knifing, Skittles version" learn to spam click, and be happy 

[AuXAuV]

A block of code, alright.

Code: [Select]

bind x "vstr n_tog"

//Do not change anything below this line unless you know
//what you are doing.

//Declare settings
//---------------------------------------------------------------------------
seta zombie_m1 "weapnext"
seta zombie_mu "+attack; -attack; wait 1; +attack; -attack"
seta zombie_md "+attack; -attack"

seta human_m1 "+attack; set next_mouse1 vstr zombie_mouse1"
//Note: swap weapnext/weapprev if desired. Not everyone
//goes the same way.

seta human_mu "weapnext"
seta human_md "weapprev"
//---------------------------------------------------------------------------

//---------------------------------------------------------------------------
seta m1 "vstr human_m1"
seta mu "vstr human_mu"
seta md "vstr human_md"
//---------------------------------------------------------------------------

//Set the binds for mouse control.
bind MOUSE1 "vstr m1"
bind MWHEELUP "vstr mu"
bind MWHEELDOWN "vstr md"

//Set toggle
seta tog1 "set m1 vstr zombie_m1; set mu vstr zombie_mu; set md vstr zombie_md; ut_echo ^1Zombie ^7Mode Active.; set n_tog vstr tog2"
seta tog2 "set m1 vstr human_m1; set mu vstr human_mu; set md vstr human_md; ut_echo ^4Human ^7Mode active.; set n_tog vstr tog1"
seta n_tog "vstr tog1"

Pressing "x" (or whatever you change it to)
Will swap your controls.
Copy this into your autoexec.cfg if you want.

(controls:
Human Mouse1 fire, mwheel to swap weaps.
Zombie Mouse1 next weapon, mouse wheel to attack)

I don't know whats wrong with this but human mode doesn't work. The only way to fire your weapon is to hit t then hit enter or to open the console and close it again. Also when you do that to get the weapon to fire it never stops.
Just keeps on firing until the clip/slip is unloaded and just keep dry firing. You can't even change weapons after you fire the one time.
 

Whoops, hate writing in the forum post box,

Code: [Select]

bind x "vstr n_tog"

//Do not change anything below this line unless you know
//what you are doing.

//Declare settings
//---------------------------------------------------------------------------
seta zombie_m1 "weapnext"
seta zombie_mu "+attack; -attack; wait 1; +attack; -attack"
seta zombie_md "+attack; -attack"

seta human_m1 "+attack"
//Note: swap weapnext/weapprev if desired. Not everyone
//goes the same way.

seta human_mu "weapnext"
seta human_md "weapprev"
//---------------------------------------------------------------------------

//---------------------------------------------------------------------------
seta m1 "vstr human_m1"
seta mu "vstr human_mu"
seta md "vstr human_md"
//---------------------------------------------------------------------------

//Set the binds for mouse control.
bind MOUSE1 "vstr m1"
bind MWHEELUP "vstr mu"
bind MWHEELDOWN "vstr md"

//Set toggle
seta tog1 "set m1 vstr zombie_m1; set mu vstr zombie_mu; set md vstr zombie_md; ut_echo ^1Zombie ^7Mode Active.; set n_tog vstr tog2"
seta tog2 "set m1 vstr human_m1; set mu vstr human_mu; set md vstr human_md; ut_echo ^4Human ^7Mode active.; set n_tog vstr tog1"
seta n_tog "vstr tog1"

That should work. For obvious reasons, I can't double check.

[(DEAD) Revolution]

Whoops, hate writing in the forum post box,

Code: [Select]

bind x "vstr n_tog"

//Do not change anything below this line unless you know
//what you are doing.

//Declare settings
//---------------------------------------------------------------------------
seta zombie_m1 "weapnext"
seta zombie_mu "+attack; -attack; wait 1; +attack; -attack"
seta zombie_md "+attack; -attack"

seta human_m1 "+attack"
//Note: swap weapnext/weapprev if desired. Not everyone
//goes the same way.

seta human_mu "weapnext"
seta human_md "weapprev"
//---------------------------------------------------------------------------

//---------------------------------------------------------------------------
seta m1 "vstr human_m1"
seta mu "vstr human_mu"
seta md "vstr human_md"
//---------------------------------------------------------------------------

//Set the binds for mouse control.
bind MOUSE1 "vstr m1"
bind MWHEELUP "vstr mu"
bind MWHEELDOWN "vstr md"

//Set toggle
seta tog1 "set m1 vstr zombie_m1; set mu vstr zombie_mu; set md vstr zombie_md; ut_echo ^1Zombie ^7Mode Active.; set n_tog vstr tog2"
seta tog2 "set m1 vstr human_m1; set mu vstr human_mu; set md vstr human_md; ut_echo ^4Human ^7Mode active.; set n_tog vstr tog1"
seta n_tog "vstr tog1"

That should work. For obvious reasons, I can't double check.

ahh i managed to test out your script but sorry to burst your bubble but.. theres something wrong with it.
on red team it works absolutely perfectly. But the most problematic part is the human team. you can switch weapons yes. but if you just shoot ONCE on your first shot, on ANY weapon, after the first shot it wont shoot again. for example: i used a sr8 for my first shot. (BOOM/ reload/ gun never is ready for next shot.) same thing for the shotgun. (BOOM/ reload/ reload freezes/ gun is never ready for next shot.) i tried switching to a different gun using my scroll wheel but only one gun appears which is the gun you fired your first shot with, and you guessed it, still not ready for its next shot. no other gun appears. i tried reloading clips in the lr after exiting and reattempting. (Reload/ reload freezes halfway/ gun is never ready for next shot.) so i am basically stuck with no guns to fire after the first shot on human team. but AuXAuV farr out man, that is one helluva script right there. but remember, a complicated script comes with very annoying problems if something's wrong. is there a possibility that you can downsize this script into a more simpler one?

PS:
The gun will only fire when you open up the console, then close. also when you press t to talk and then enter.
funny thing heppened to me when i tested out the script. in game i typed "dont kill me im testing out my script" to the reds cuz they kept camping (not that i cared). the moment i hit enter, my shotgun whent BOOM to a red's face. they though i tricked them and they killed me xD


PPS: TURBAN ERROR for an odd reason i cant access the mediafire thing. could you just put in your script word for word? kinda like what AuXAuV wrote? i think thats the easiest way.

thanks for the help everyone

[TurbanError]

PPS: TURBAN ERROR for an odd reason i cant access the mediafire thing. could you just put in your script word for word? kinda like what AuXAuV wrote? i think thats the easiest way.

What you want looks like this:

In your Autoexec.cfg file:

Code: [Select]

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

In your human.cfg file:

Code: [Select]

//Normal Weapon Scrolling
bind MWHEELUP "weapon prev;"
bind MWHEELDOWN "weapon next;"

//Normal Firing
bind MOUSE1 "+attack;"

Note: We rebind +attack as the key it would have been bindined to (wheelup/down) is no longer bound to that in human mode.

In your zombie.cfg

Code: [Select]

//Fast knife Scroll
bind MWHEELUP "+attack; -attack; wait #; +attack; -attack;"
bind MWHEELDOWN "+attack; -attack; wait #; +attack; -attack"

Quoting myself twice=end of my help.  Not trying to be mean, there is only so many times I can tell you the answer to your question.

[AuXAuV]

--snip--

ahh i managed to test out your script but sorry to burst your bubble but.. theres something wrong with it.
on red team it works absolutely perfectly. But the most problematic part is the human team. you can switch weapons yes. but if you just shoot ONCE on your first shot, on ANY weapon, after the first shot it wont shoot again. for example: i used a sr8 for my first shot. (BOOM/ reload/ gun never is ready for next shot.) same thing for the shotgun. (BOOM/ reload/ reload freezes/ gun is never ready for next shot.) i tried switching to a different gun using my scroll wheel but only one gun appears which is the gun you fired your first shot with, and you guessed it, still not ready for its next shot. no other gun appears. i tried reloading clips in the lr after exiting and reattempting. (Reload/ reload freezes halfway/ gun is never ready for next shot.) so i am basically stuck with no guns to fire after the first shot on human team. but AuXAuV farr out man, that is one helluva script right there. but remember, a complicated script comes with very annoying problems if something's wrong. is there a possibility that you can downsize this script into a more simpler one?

PS:
The gun will only fire when you open up the console, then close. also when you press t to talk and then enter.
funny thing heppened to me when i tested out the script. in game i typed "dont kill me im testing out my script" to the reds cuz they kept camping (not that i cared). the moment i hit enter, my shotgun whent BOOM to a red's face. they though i tricked them and they killed me xD


PPS: TURBAN ERROR for an odd reason i cant access the mediafire thing. could you just put in your script word for word? kinda like what AuXAuV wrote? i think thats the easiest way.

thanks for the help everyone

It fails because the Frozen Sands dev team sucks,
I forgot how frustrating their work is.

Well, the simplest is 2 configs, human and zombie, that have an exec toggle.

Code: [Select]

bind x "vstr toggle_mode"
seta toggle_mode "vstr zombie_mode"
seta zombie_mode "set toggle_mode vstr human_mode; exec zombie.cfg; echo ^1Zombie ^6Mode Active."
seta human_mode "set toggle_mode vstr zombie_mode; exec human.cfg; echo ^4human ^6Mode Active."

However, that's what Turban has been trying to tell you the whole time.

[(DEAD) Revolution]

lol

[Lancers09]

I am against scripting. But what choice do I got with pingers these days.

Can you recommend how many +attack.
My fps is around 78-99 fps.
My ping is almost always 68-76

Thanks


Sent from my iPod touch using tapatalk
(why do we write these?)

[TurbanError]

Well, the simplest is 2 configs, human and zombie, that have an exec toggle.

Code: [Select]

bind x "vstr toggle_mode"
seta toggle_mode "vstr zombie_mode"
seta zombie_mode "set toggle_mode vstr human_mode; exec zombie.cfg; echo ^1Zombie ^6Mode Active."
seta human_mode "set toggle_mode vstr zombie_mode; exec human.cfg; echo ^4human ^6Mode Active."

However, that's what Turban has been trying to tell you the whole time.

THANKYOU

I am against scripting. But what choice do I got with pingers these days.

Can you recommend how many +attack.
My fps is around 78-99 fps.
My ping is almost always 68-76

I like the script mostly because it is a feature of the server, and you can't use it outside of zombie and super, or any server that doesn't have it as a feature.  In that regards, I don't feel it is unfair or cheating to have it set up.

The number of + attack; -attack  combos in my guide is five.  I imagine that's probably what I have it set to on my comp (away from computer).  I would set up the binds and then test it a few times and count how many attacks your getting per click (I often start a map stabbing and counting and checking my fov script to make sure nothing is screwed up).  If you can get close to 5 per click you are golden, if you get 2, you might have a problem.  The more +attack; -attack; combinations the more you loose control of your movement while stabbing (as the game must resolve your commands before reading other ones). 

My math says the wait time for 78 fps is 5.6... I am not sure if you can do a fraction of a frame, I would bet you couldn't.  In order to minimize unneeded wait time at low fps I would set my wait to 5 and not worry about any dropped commands at higher fps.  Also try 6 and see what works best for you.  Best of luck.

alright, i got another script which i modified to fit my game play.

Code: [Select]

set sl_00 "set sl_f vstr sl_01; ut_echo ^7Human Mode Activated; vstr hum"
set sl_01 "set sl_f vstr sl_00; ut_echo ^3Zombie Mode Activated; vstr zom"
set sl_f "vstr sl_01" // Set Default
bind x "vstr sl_f" // Replace "x" with a key of choice
set zom “bind MWHEELDOWN “+attack; -attack”;”
set zom “bind MWHEELUP “+attack; -attack”;”
set hum “bind MWHEELDOWN “weapprev”;”
set hum “bind MWHEELUP “weapnext”;”
set hum "bind MOUSE1 vstr att"
set att "+attack; -attack"

try it and tell me what you think of it. im rather proud to have endured all those trial and errors. there still may be some mistakes in it but try it and tell me what you think of it. 

I haven't played this, but I can already see a bug you might not know about.  Using the set command sets a variable, using it to set a variable of the same name overwrites what was previously set (like dragging and dropping a file into a folder with the same name).  URT reads from top to bottom, so all those set commands for the same variable will only read your bottom set command line.  With that said, you want all your "zom" binds and "hum" binds on one line, and to set them once.  Also from experience I know that setting human attack to +attack; - attack combo essentially eliminates the use of autos (as it shoots one shot per click).  Just delete the - attack from the hum...att... variable.

[(DEAD) Revolution]

lol