What are the aliases checkjump and checkcrouch for? Seem pretty useless.

If you want to ctap, a tip that I've seen players use is to bind mouse2 to +duck. It apparently feels much easier(I've tried it myself and can somewhat confirm) to ctap.

that's it, tf2 is finished

jump maps>? yeah go play them

you can make a script for legitimate ctaps without wait if you're creative enough

your script seems to be missing something. even though people have -fragged #2, he's right - you don't call the checkjump and checkcrouch aliases in that script. here is the one that i came up with if you want to modify yours or just use this one instead:

alias +ctap   "alias duckon;       alias duckoff;       ctapon; +jump"
alias -ctap   "alias duckon +duck; alias duckoff -duck; -jump;  ctapoff"
alias +fduck  "alias ctapon;       alias ctapoff;       duckon"
alias -fduck  "alias ctapon +duck; alias ctapoff -duck; duckoff"
alias ctapon  +duck
alias ctapoff -duck
alias duckon  +duck
alias duckoff -duck

bind ALT +ctap
bind SHIFT +fduck

it makes it so you can jump out of a crouch, and if you continue holding crouch you will crouch again after releasing your jump key. the main point is that it just makes your keys feel more responsive like the null-movement cancelling script (which i like to use in combination with this one)

make sure to change the last two lines to your desired keys for jump and crouch

couldnt you just stop holding down crouch then jump...

esdf > wasd
a>ctrl

whooooaaaaaaaaaaaaaa!! feels pretty awesome

That doesn't happen with your script.

it should, because that is what i've used for months

edit: oh, i read it and it's the script for ctapping with anti-stick, not jumping out of crouch. my bad

i play on ewdf
your elitism is invalid

I play on 03070809

I was being honest about playing on ewdf though

What is anti-stick?

And do you have one for not jumping out of crouch? Would like to try it

I tried it out and all it does is make me uncrouch when I press jump. It doesn't seem to allow you to jump straight out of a crouch. Does someone know of a way to do that? I want to learn to c-tap for real (jump to spire from EVERYWHERE), but it'd be an interesting scripting challenge to get it to work without the wait command.

What exactly is c-tapping?

its called cunt tapping, you press your cunt against the ground and propel yourself to great heights also known as the queef tap

Can someone possibly tell me how you use this thing called a script? I have never attempted such a thing and any clarification would be nice to a noob like me.

If your mouse/keyboard has the ability to set up macros you can make a perfect ctap script out of game (pretty sure a fair number of players do this). The same can be done to perform bhops on a flat surface, glitching player models, etc.

C-tapping means you tap crouch and then release and jump when only partially crouched, not fully crouched. The script won't make you jump out of a full crouch, but it helps with the timing of releasing crouch when c-tapping.

ah, well that makes a bit more sense. I thought it was supposed to work exactly like the null-movement one in that if you have one state active (jumping or crouch), then pressing the other button will enable the other state. But I see what you're saying.

could use autohotkey,

this seems to work i guess:

;List of Keynnames can be found here: http://www.autohotkey.com/docs/KeyList.htm

#IfWinActive Team Fortress 2
{
	;*******EDIT IN BETWEEN*******
	;needs to be the key you bound +duck to ingame
	duckkey = LCtrl

	;needs to be the key you bound +jump to ingame (Can't be a duckjump script key)
	jumpkey = Space 

	;needs to be the key you bound +attack to ingame only when manualfire is 0
	attackkey = LButton 

	;is the key that will suspend the whole script if you go another Class for example and need the key for something else
	suspendkey = F7 

	;is the key to perform the ctap
	ctapkey = Numpad0 

	;set this to 1 if you want to fire manually
	manualfire = 1

	:sets the delay between pressing and releasing duck 150 seems to be close to the limit where you dont lose velocity. Guess lower numbers could work. 1000 = 1 second
	duckdelay = 150

	;*******EDIT IN BETWEEN*******

	Hotkey, %suspendkey%, SUSPEND

	If manualfire = 1
	{
		Hotkey, %ctapkey%, CTAPNOFIRE
	}
	else
	{
		Hotkey, %ctapkey%, CTAP
	}
}
return

CTAP:
	Send {%duckkey% down}
	Sleep %duckdelay%
	Send {%duckkey% up}
	Send {%jumpkey%}
	Send {%attackkey%}
	return

CTAPNOFIRE:
	Send {%duckkey% down}
	Sleep %duckdelay%
	Send {%duckkey% up}
	Send {%jumpkey%}
	return

SUSPEND:
	suspend
	return

due to the nature of ctapping there is a noticeable delay between pressing the ctapkey and actually firing, you need to make sure you keep looking in the right direction for the jump to work.

set manualfire = 1 if you want to shoot yourself.

would love to hear some feedback, has anyone tried it?

I'm wondering if it is dependant on ping or anything, basicly if it works for me only or anyone else.

I tried it on the last jump of jump_klanana and it never worked properly once.

;List of Keynnames can be found here: http://www.autohotkey.com/docs/KeyList.htm

#IfWinActive Team Fortress 2
{
	;*******EDIT IN BETWEEN*******
	;needs to be the key you bound +duck to ingame
	duckkey = LCtrl

	;needs to be the key you bound +jump to ingame (Can't be a duckjump script key)
	jumpkey = Space 

	;needs to be the key you bound +attack to ingame only when manualfire is 0
	attackkey = LButton 

	;is the key that will suspend the whole script if you go another Class for example and need the key for something else
	suspendkey = F7 

	;is the key to perform the ctap
	ctapkey = Numpad0 

	;set this to 1 if you want to fire manually
	manualfire = 1

	:sets the delay between pressing and releasing duck 150 seems to be close to the limit where you dont lose velocity. Guess lower numbers could work. 1000 = 1 second
	duckdelay = 150

	;*******EDIT IN BETWEEN*******

	Hotkey, %suspendkey%, SUSPEND

	If manualfire = 1
	{
		Hotkey, %ctapkey%, CTAPNOFIRE
	}
	else
	{
		Hotkey, %ctapkey%, CTAP
	}
}
return

CTAP:
	Send {%duckkey% down}
	Sleep %duckdelay%
	Send {%duckkey% up}
	Send {%jumpkey%}
	Send {%attackkey%}
	return

CTAPNOFIRE:
	Send {%duckkey% down}
	Sleep %duckdelay%
	Send {%duckkey% up}
	Send {%jumpkey%}
	return

SUSPEND:
	suspend
	return

I received some feedback recently, that duckdelay = 60, works best. I haven't tested myself, but if someone wants to give a shot.