This shows you the upcoming nice function called "wcs_setfx". (300 lines of code!!)
Basically it gives game effects to a player (not graphical!), enables a large number of skills/ideas and is error-proof.
Here is the syntax:


supported types are: freeze speed god invis(0-255) invisp(in %) health armor gravity disguiser 1stclip 2ndclip longjump

in future, this will replace the "wcs_removefx", because you can do very more with this and it also checks for dead players on delayed effects

looks complicated, but this enables you to do non-trivial skills within one command!
eg.

giving a player 20% more speed, for 10 seconds (STACKABLE and return to previous value after the time)

take from an enemy 100 armor for 15 seconds (back to previous armor after this)

set a player to 20% longjump action, for 5 seconds

give a player permanent +30 bullets for his primary weapon (works after reload, if eventscripts_noisy=1)

disguise for 30 seconds (after, switch back)

the special about this is, it doesn't raise ERRORS in console log, it checks all values for correctness (eg. invisibility percent between 0-100), enables giving and taking, is stackable and supports timed effects.
So you can have a race with 70% invis, and if you buy a shopitem that gives you +50% invis for 30 seconds, you are complete invis for this time and AFTER you switch back to 70%

be prepared to code some nice skills 

[note for the pro's: this enables safe skill coding with different aspects and is very good for fast balancing races. Also, beginners are now able to create not so easy skills, like timed effects or enable stacking of skills]

hehe yes, you made a small mistake. With that one command, you would reduce your error sources

your skill in the support forum would be like this:


just two lines of code. if you compare with your code, the new commands saves some work and is less error sensitive 

Wow...this is going to create thousands of races....maybe non copy + paste with this  function

please do not remove wcs_removefx since it's smaller and runs faster.

hmm right...if you have complex commands and still need removefx, this command is better (because of performance!)
here a benchmark

removefx: 28 lines code, 3 choices
setfx: 303 lines code, 12 choices

so, especially because less if(...) checks, removefx is almost 2x faster. The difference for a single call is 0.006 seconds.

wcs_removefx will still stay in the mod, but its not extended in future (so it keeps fast )

Thats a lot easier