First off, the main reason for this post is because of an request...

Now to start, most of all the "wcs_" stuff is just variables. The main reason for this is so that other Event Scripts scripts  don't conflict with WCS, so that when you store data in a variable another script won't overwrite your data that is stored within the variable.

Commands can sometimes be difficult to use, and also you may think something is a command and it really is not... With WCS comes a bunch of commands which are all documented within the various *.txt files_{(I will list them all as of WCS v0.77)}. Also all if not most of the ES commands are very well documented on their wiki, which can be found here. And the commands here. Now the same goes for EST, but one major difference between EST and ES is that EST is not documented as well as ES, there is some documentation here, and some documented commands here.

A quick little explanation of the "es" before commands! For most commands you will use in your races and what not you will need a "es" in-front  of the command so that the server knows to expand event_var's and server_var's. What that means is if you put an "es" in-front of any command, if you set a variable or it is and event variable inside of the event the server will replace the event_var or the server_var with its value. Also note that all "es_" commands automatically expand these variables, but any "es_x" commands do not! as well as any "wcs_" and "est_" commands will not expand any variables. A little trick that most advanced scripter's would use to speed up their scripts was to use "es_x" commands and add a "es" before it to get a "es es_x" which was just a tad faster.

Now for the list off all the "wcs_" console commands and their syntax!

• wcs_addonreload <NAME>
• wcs_givecredits <userid> <amount> <reason> <forced>
• wcs_menuzero <userid>
• wcs_flash <userid> <targetid>
• wcs_showcredits <userid>
• wcs_removefx <userid> <effectype>
• wcs_setfx <userid> <effectype> [<time>]
• wcs_giveitem <userid> <item>
• wcs_explode <userid> <targetid> <magnitude> <radius>
• wcs_dealdamage <userid> <targetid> <magnitude> <radius>
• wcs_saveplayer <userid> <full>
• wcs_getplayer <userid> <full>
• wcs_checkevents <userid> <type>
• wcs_showinfohandle <type>
• wcs_notice <userid> <text>
• wcs_debuglog <text>
• wcs_restrict_purge <userid>
• wcs_restrict <userid> restrict <weapon>
• wcs_restrict <userid> allow <weapon> <give> <knife>
• wcs_restrict <userid> addallow <weapon>
• wcs_restrict <userid> knife
• wcs_restrict <userid> knifeonly
• wcs_givexp <userid> <amount> <reason> <forced>
• wcs_givelevel <userid> <amount> <reason> <forced>
• wcs_showxp <userid>
• wcs_deathhandle <userid> <attackerid> <weapon> <headshot>
• wcs_getlanguage <var> <id>
• wcs_race_menu <userid>
• wcs_showraceinfo <userid>
• wcs_shopmenu <userid>
• wcs_giveshopitem <userid> <itemid>
• wcs_showshopinfo <userid>
• wcs_deathhandle_items <userid>
• wcs_showtop10 <userid>
• wcs_checktop10 <userid>
• wcs_cleartop10
• wcs_mole_activate <userid>
• wcs_regeneration <userid> <amount> <time> <maxHP> <maxHeal> <radius>
• wcs_warden  <userid> <duration> <damage> <radius> <target team> <team target name> <x> <y> <z> <round>
• wcs_spendskills <userid>
• wcs_showplayerinfo <userid>
• wcs_showskills <userid>
• wcs_resetskills <userid>

Yes I do know that there are other commands but they are not really useful for scripting...

NOTE: To find the SYNTAX of a command all you must do is type it in the server console and it should tell you its SYNTAX!!! And if the command does in fact NOT exist it will tell you the command is unknown!!!

no
if (server_var(wcs_amount) >= 0) do {.....}
es_xelse do
{
...
es_xmath wcs_amount * -1
...
}