Well recently I've been trying to make a skill that when a user swings his knife, he gains a certain amount of speed for a certain amount of time. This is what I have for the skill, I just don't know how to get it to work...
.

I have this coding in for the skill.

GeSHi (eventscripts):
    "skill2_setting"    	"0"
    "skill2_cmd"        	"es es_xkeysetvalue WCSuserdata server_var(wcs_userid) knifeshit 1"
    "skill2_sfx"        	"0"

This is what is in es_wcs.txt

GeSHi (eventscripts):
And this is what is in player_spawn_cmd
 
 
    "preloadcmd" es_xdoblock corelib/noisy_on"

I dont see any mistakes. I'm so lost. =-(

Avast I think his way is better he just messed up in the spawn command by using wcs_userid as a server var instead of event_var(userid)

I would do something like this:

This is the command part  player_spawn  your problem is you used wcs_userid instead of event_var(userid)


Then in es_wcs.txt add this line to player_spawn otherwise after switchin races it will still work

and further down in the weapon_fire block

lol

wcs_knifespeed is just a variable... u gotta declare it before you use it..

guess what I meant with "declaration"

Lol, this is something I've never actually known about keysetvalues. Why exactly do I need to declare it? Btw, thanks for all the help you guys are providing.

Well say if you bought 3 buckets, bucket_a bucket_b and bucket_c. You can fill those with water right? So you tell someone to go fill bucket_a with water then a while later you ask them to give you bucket_a and it's still filled with water (hopefully). So you've retrived what you wanted to store, which is the measure of water or a variable in the case of ESS.

So what if you told someone to go fill bucket_d? Oh shit you don't have a bucket_d so how could you possibly fill it? What happens when you then ask someone to bring you bucket_d full of water? You wont get anything, they'll just say no bucket_d sir, can't fill it up. This is seen in the console with "variable not set". Imaginary buckets just don't hold water, as do non existing variables in ESS.

So you do keygetvalue with variable omgnewvariable. Wont work. You have to "buy" the new "bucket" to hold the variable by having "es_xset omgnewvariable 0" somewhere before that line is triggered. The es_xset 0 creates the variable, allowing it to store variables. This es_xset 0 can be in preload_cmd or in block load of es_wcs or even just right before you do es_keygetvalue. Of course there are loads of pre-bought "buckets" which you can use such as wcs_tmp wcs_tmp1 wcs_health wcs_divider wcs_alpha ect ect.

Hopefully thinking of it in that way makes sense

Well if you set the variables on server start it really causes no lag at all. Despite it causing almost no lag at all to begin with. Takes about 3 milliseconds to set a variable and a tenth of that to change one. Considering a couple hundred are set when WCS is loaded, it really amounts to nothing.