From 6f0cb6566e8f8ec91143c4ec3c1ab3cf2a4f7e78 Mon Sep 17 00:00:00 2001
From: eaac <eaac@54d463be-8e91-2dee-dedb-b68131a5f0ec>
Date: Fri, 9 Feb 2007 02:09:33 +0000
Subject: eAAC has checked the source and added missing commands to the
 script_commands.txt (the long-awaited mob control suit made by Lance, for
 example), also explained the logical operators AND,OR,XOR, left and right
 shift. We also sorted the commands according to what they do.

I'd also like feedback of the new version, to either me, Trancid or Dj-Yhn, to see what should be changed or what is incorrect / missing.

~erKURITA.

git-svn-id: https://rathena.svn.sourceforge.net/svnroot/rathena/trunk@9831 54d463be-8e91-2dee-dedb-b68131a5f0ec
---
 doc/script_commands.txt | 6674 ++++++++++++++++++++++++++---------------------
 1 file changed, 3658 insertions(+), 3016 deletions(-)

(limited to 'doc/script_commands.txt')

diff --git a/doc/script_commands.txt b/doc/script_commands.txt
index 212ad25d6..8dc6cf8e5 100644
--- a/doc/script_commands.txt
+++ b/doc/script_commands.txt
@@ -9,7 +9,7 @@
 //= Maeki Rika - A section on general concepts and lots of
 //=              other updates and additions.
 //===== Version ===========================================
-//= 2.11.20070109
+//= 3.00.20070208
 //=========================================================
 //= 1.0 - First release, filled will as much info as I could
 //=       remember or figure out, most likely there are errors,
@@ -45,10 +45,19 @@
 //=       [FlavioJS]
 //= 2.12.20070201 - Added npcshopitem, npcshopadditem, npcshopdelitem and
 //=       npcshopattach [Skotlex]
+//= 3.00.20070208
+//=		 - Explained Logical Bitwise Operators. 
+//=		   Dj-Yhn contributed to AND (&) operator, rest by myself. [erKURITA]
+//=		 - Added a resume of allowed variable and arrays scopes. [erKURITA]
+//=		 - Re-organized the script commands, and grouped them depending
+//=		   on what they do. [erKURITA]
+//=		 - Added a packload of commands that were missing, 
+//=		   and corrected some of the wrong ones [Dj-Yhn, erKURITA & Trancid]
 //===== Compatible With ===================================
 //= LOL, can be used by anyone hopefully
 //===== Description =======================================
-//= A reference manual for the eAthena scripting language
+//= A reference manual for the eAthena scripting language,
+//= sorted out depending on their functionality.
 //=========================================================
 
 This document is a reference manual for all the scripting commands and functions 
@@ -61,16 +70,6 @@ and lots of them don't speak English and never left any notes - or are otherwise
 not available for comments. As such, anything written in here might not be 
 correct, it is only correct to the best of our knowledge, which is limited.
 
-This document is poorly structured and rather messy in general. In fact, further 
-cleaning up and reordering this document is probably pointless, due to upcoming 
-switch to Lua scripting language, which will rid us of most of the problems 
-mentioned herein and make a new manual necessary. But while we have this one, we 
-should make the most of it, and it might be helpful in making sure the new Lua 
-engine can actually do everything useful that the old engine could.
-Note: The change to lua isn't going to happen because we are switching to eApp.
-      eApp has it's own scripting language and a converter to convert scripts
-      from the current script language.
-
 This is not a place to teach you basic programming. This document will not teach 
 you basic programming by itself. It's more of a reference for those who have at 
 least a vague idea of what they want to do and want to know what tools they have 
@@ -344,7 +343,7 @@ prices for items in different shops.
 
 ** Define a function object
 
-function%TAB%<function name>%TAB%{<code>}
+function%TAB%script%TAB%<function name>%TAB%{<code>}
 
 This will define a function object, callable with the 'callfunc' command (see 
 below). This object will load on every map server separately, so you can get at 
@@ -370,6 +369,8 @@ valid and mean what exactly is pending.
 Once an object is defined which has a 'code' field to it's definition, it 
 contains script commands which can actually be triggered and executed. 
 
+~ RID? GID? ~
+
 What a RID is and why do you need to know
 -----------------------------------------
 
@@ -396,6 +397,17 @@ used to check which is the currently attached player to the script (it will
 return 0 if the there is no player attached or the attached player no longer
 is logged on to the map-server).
 
+But what about GID?
+--- ---- ----- ----
+
+GID stands for the Game ID of something, this can either be the GID obtained
+through mobspawn (mob control commands) or the account ID of a character.
+Another way would be to right click on a mob, 
+NPC or char as GM sprited char to view the GID.
+
+This is mostly used for the new version of skill and the mob control commmands
+implemented (but NEVER documented by Lance. Shame on you...).
+
 Item and pet scripts
 --------------------
 
@@ -594,6 +606,41 @@ Arrays can naturaly store strings:
 the '$', normally denoting a string variable, before the square brackets that 
 denotes an array index.
 
+Resume of the allowed variable and array scopes
+------ -- --- ------- -------- --- ----- ------
+
++==========+======+=======+
+|VarType   | Norm | Array |
++==========+======+=======+
+|$Str$     | OK!  | OK!   |
++----------+------+-------+
+|$@Str$    | OK!  | OK!   |
++----------+------+-------+
+|@Str$     | OK!  | OK!   |
++----------+------+-------+
+|#Str$     | OK!  | FAIL! |
++----------+------+-------+
+|Str$      | OK!  | FAIL! |
++----------+------+-------+
+|$Int      | OK!  | OK!   |
++----------+------+-------+
+|$@Int     | OK!  | OK!   |
++----------+------+-------+
+|@Int      | OK!  | OK!   |
++----------+------+-------+
+|#Int      | OK!  | FAIL! |
++----------+------+-------+
+|Int       | OK!  | FAIL! |
++----------+------+-------+
+|.Str$     | OK!  | OK!   |
++----------+------+-------+
+|.Int      | OK!  | OK!   |
++----------+------+-------+
+|.@Str$    | OK!  | OK!   |
++----------+------+-------+
+|.@Int     | OK!  | OK!   |
++----------+------+-------+
+
 Operators
 ---------
 
@@ -645,15 +692,71 @@ Comparisons can be stacked in the same condition:
  1=1 && 2=1 is False.
  1=1 || 2=1 is True.
 
-Logical operators work only on numbers:
+Logical bitwise operators work only on numbers, and they are the following:
 
  << - Left shift.
  >> - Right shift.
+ 	Left shift moves the binary 1(s) of a number n positions to the left,
+	which is the same as multiplying by 2, n times.
+	In the other hand, Right shift moves the binary 1(s) of a number n positions
+	to the right, which is the same as dividing by 2, n times.
+		Example:
+		set b,2;
+		set a, b << 3;
+		mes a;
+		set a, a >> 2;
+		mes a;
+	The first mes command would display 16, which is the same as 2 x (2 x 2 x 2) = 16.
+	The second mes command would display 4, which is the same as 16 / 2 = 8. 8 / 2 = 4.
  &  - And.
  |  - Or.
+	The bitwise operator AND (&) is used to test two values against eachother, 
+	and results in setting bits which are active in both arguments. This can
+	be used for a few things, but in eAthena this operator is usually used to
+	create bitmasks in scripts. 
+	
+	The bitwise operator OR (|)sets to 1 a binary position if the binary position
+	of one of the numbers is 1. This way a variable can hold several values we can check,
+	known as bitmaks. A variable currently can hold up to 32 bitmasks (from position 0
+	to position 1). This is a cheap(skate) and easy way to avoid using arrays to store several checks
+	that a player can have.
+	
+	A bitmask basically is (ab)using the variables bits to set various options in 
+	one variable. With the current limit if variables it is possible to store 32 
+	different options in one variable (by using the bits on position 0 to 31).
+
+	Example(s):
+	- Basic example of the & operator, bit example:
+		10 & 2 = 2
+	Why? :
+		10 = 2^1 + 2^3 (2 + 8), so in bits, it would be 1010
+		2 = 2^1 (2), so in bits (same size) it would be 0010
+		The & (AND) operator sets bits which are active (1) in both arguments, so in the
+		example 1010 & 0010, only the 2^1 bit is active (1) in both. Resulting in the bit
+		0010, which is 2.
+	- Basic example of creating and using a bit mask:
+		set @options,2|4|16; //(note: this is the same as 2+4+16, or 22)
+		if (@options & 1)	mes "Option 1 is activated";
+		if (@options & 2) mes "Option 2 is activated";
+		if (@options & 4) mes "Option 3 is activated";
+		if (@options & 8) mes "Option 4 is activated";
+		if (@options & 16) mes "Options 5 is activated";
+	This would return the messages about option 2, 3 and 5 being shown (since we've set
+	the 2,4 and 16 bit to 1).
  ^  - Xor.
-
-If you don't know what these five mean, don't bother, you don't need them.
+	The bitwise operator XOR (eXclusive OR) sets to 0 a binary position if both numbers have a 1
+	in the said position. On the other hand, it sets to 1 if there's a 1 in any of the number in
+	the said binary position.
+	This is the counter-part of the OR operator, the opposite if you like. This is used to remove a
+	bitmask, which is the same as substracting it.
+	
+	Example:
+	- We set the variable first:
+		set a,2|4|8|16; // this would be the same as 2+4+8+16 = 30
+	- After some checks, we find he didn't do the third quest, which we asigned the 3rd value (8)
+	  so now we have to remove it:
+		set a,a^8; //this would be the same as 30-8 = 22. 22 = 16+4+2, which are the flags left.
+		
 
 Labels
 ------
@@ -720,6 +823,14 @@ altering the configuration options in 'script_athena.conf'. It's pretty obvious
 when those will get triggered. For more information, see 
 'npc/sample/PCLoginEvent.txt'
 
+OnPCLoadMapEvent:
+
+This special label will trigger once a player steps in a map marked with the 
+'loadmap' mapflag and attach its RID. The fact that this label requires a 
+mapflag for it to work is because, otherwise, it'd be server-wide and trigger
+everytime a player would change maps. Imagine the server load with 1,000 players
+(oh the pain...)
+
 Only the special labels which are not associated with any script command are 
 listed here. There are other kinds of labels which may be triggered in a similar 
 manner, but they are described with their associated commands.
@@ -764,16 +875,20 @@ behave nicely if you do.
 
 -------------------------
 
-*playerattached;
 
-Returns the ID of the player currently attached to the script. It will return
-0 if noone is attached, or if the attached player no longer exists on the map
-server. It is wise to check for the attached player in script functions that
-deal with timers as there's no guarantee the player will still be logged on
-when the timer triggers. Note that the ID of a player is actually their
-account ID.
+From here on, we will have the commands sorted as follow:
 
--------------------------
+1.- Basic commands.
+2.- Information-retrieving commands.
+3.- Checking commands.
+4.- Player-related commands.
+5.- Mob / NPC -related commands.
+6.- Other commands.
+
+=====================
+|1.- Basic commands.|
+=====================
+---------------------------------------
 
 *mes "<string>";
 
@@ -805,177 +920,6 @@ either side solves the problem.
 
 ---------------------------------------
 
-*goto <label>;
-
-This command will make the script jump to a label, usually used in conjunction 
-with other command, such as "if", but often used on it's own.
-
-           goto Label;
-           mes "This will not be seen";
-    Label:
-           mes "This will be seen";
-
----------------------------------------
-
-*callfunc "<function>"{,<argument>,...<argument>};
-*callfunc("<function>"{,<argument>,...<argument>})
-
-This command lets you call up a function NPC. A function NPC can be called from 
-any script on any map server. Using the 'return' command it will come back to 
-the place that called it.
-
-    place.gat,50,50,6%TAB%script%TAB%Woman%TAB%115,{
-        mes "[Woman]"
-        mes "Lets see if you win";
-        callfunc "funcNPC";
-        mes "Well done you have won";
-        close;
-    }
-    function%TAB%script%TAB%funcNPC%TAB%{
-        set @win, rand(2);
-        if(@win==0) return;
-        mes "Sorry you lost";
-        end;
-    }
-
-You can pass arguments to your function - values telling it what exactly to do -
-which will be available there with getarg() (see 'getarg')
-Notice that returning is not mandatory, you can end execution right there.
-
-If you want to return a real value from inside your function NPC, it is better 
-to write it in the function form, which will also work and will make the script 
-generally cleaner:
-
-    place.gat,50,50,6%TAB%script%TAB%Man%TAB%115,{
-        mes "[Man]"
-        mes "Gimme a number!";
-        next;
-        input @number;
-        if (callfunc("OddFunc",@number)) mes "It's Odd!";
-        close;
-    }
-    function%TAB%script%TAB%OddFunc%TAB%{
-            if (getarg(0)%2==0) goto ItsEven;
-            return (1);
-        ItsEven:
-            return (0);
-    }
-
----------------------------------------
-
-*callsub <label name>{,<argument>,...<argument>};
-
-This command will go to a specified label within the current script (do NOT use 
-quotes around it) coming in as if it were a 'callfunc' call, and pass it 
-arguments given, if any, which can be recovered there with 'getarg'. When done 
-there, you should use the 'return' command to go back to the point from where 
-this label was called. This is used when there is a specific thing the script 
-will do over and over, this lets you use the same bit of code as many times as 
-you like, to save space and time, without creating extra NPC objects which are 
-needed with 'callfunc'. A label is not callable in this manner from another 
-script.
-
-           mes "[Woman]"
-           mes "Lets see if you win";
-           callsub Check;
-           mes "Well done you have won";
-    Check:
-           set @win, rand(2);
-           if(@win==0) return;
-           mes "Sorry you lost";
-           
----------------------------------------
-
-*return {(<value>)};
-
-When you use callsub or callfunc, this command allows you to go back to the 
-calling script. You can optionally return with a value telling the calling 
-program what exactly happened. To get at this value, you will have to use the 
-'set' command:
-
-    set <variable>,callfunc "<your function>"
-
-Note the round brackets. Turns out you have to enclose just about anything in 
-brackets if it isn't a straight number for the return command to work with it:
-
-    return (@x+@y);
-
-Also note that
-
-    if (<condition>) return (<whatever>);
-
-does NOT always work, even though it would make scripts a lot cleaner, and it 
-might be wiser to avoid using it like that.
-
-For an example see 'callfunc' and 'callsub'
-
----------------------------------------
-
-*getarg(<number>)
-
-This function is used when you use the 'callsub' or 'callfunc' commands. In the 
-call you can specify variables that will make that call different from another 
-one. This function willwill return an argument the function or subroutine was 
-called with, and is the normal way to get them. 
-This is another thing that can let you use the same but of code more than once. 
-
-Argument numbering starts with 0, i.e. the first argument you gave is number 0. 
-If no such argument was given, a zero is returned.
-
-    place.gat,50,50,6%TAB%script%TAB%Woman1%TAB%115,{
-        mes "[Woman]";
-        mes "Lets see if you win";
-        callfunc "funcNPC",2;
-        mes "Well done you have won";
-
-    ...
-
-    place.gat,52,50,6%TAB%script%TAB%Woman2%TAB%115,{
-        mes "[Woman]";
-        mes "Lets see if you win";
-        callfunc "funcNPC",5;
-        mes "Well done you have won";
-
-    ...
-
-    function%TAB%script%TAB%funcNPC%TAB%{
-        set @win, rand(getarg(0));
-        if(@win==0) return;
-        mes "Sorry you lost";
-
-"woman1" NPC object calls the funcNPC. The argument it gives in this call is 
-stated as 2, so when the random number is generated by the 'rand' function, it 
-can only be 0 or 1. Whereas "woman2" gives 5 as the argument number 0 when 
-calling the function, so the random number could be 0, 1, 2, 3 or 4, this makes 
-"woman2" less likely to say the player won. 
-
-You can pass multiple arguments in a function call:
-
-    callfunc "funcNPC",5,4,3;
-
-getarg(0) would be 5, getarg(1) would be 4 and getarg(2) would be 3.
-
-'getarg()' can also be used to carry information back from using the "callfunc" 
-script command, if the 'return' command is set to return a value: 
-
-    place.gat,50,50,6%TAB%script%TAB%Woman%TAB%115,{
-        mes "[Woman]";
-        mes "Lets see if you win";
-        callfunc "funcNPC";
-        mes "Well it seems you have "+getarg(0);
-    }
-    function%TAB%script%TAB%funcNPC%TAB%{
-        set @win, rand(2);
-        if(@win==0) return(won);
-        return(lost);
-    }
-        
-It is, however, better to use 'set' to get this value instead (see 'callfunc') 
-because otherwise you can't call functions from within other functions. (Return 
-values mess up the stack.)        
-
----------------------------------------
-
 *next;
 
 This command will create a 'next' button in the message window for the invoking 
@@ -1024,44 +968,146 @@ Don't expect things to run smoothly if you don't make your scripts 'end'.
 
 ---------------------------------------
 
-*menu "<menu option>",<label>{,"<menu option>",<label>...};
+*end;
 
-This command will create a selectable menu for the invoking character. Only one 
-menu can be on screen at the same time.
+This command will stop the execution for this particular script. The two 
+versions are prefectly equivalent. It is the normal way to end a script which 
+does not use 'mes'.
 
-Depending on what the player picks from the menu, the script execution will 
-continue from the corresponding label. (it's string-label pairs, not label-
-string)
+        if (BaseLevel<=10) goto L_Lvl10;
+        if (BaseLevel<=20) goto L_Lvl20;
+        if (BaseLevel<=30) goto L_Lvl30;
+        if (BaseLevel<=40) goto L_Lvl40;
+        if (BaseLevel<=50) goto L_Lvl50;
+        if (BaseLevel<=60) goto L_Lvl60;
+        if (BaseLevel<=70) goto L_Lvl70;
+    L_Lvl10:
+        npctalk "Look at that you are still a n00b";
+        end;
+    L_Lvl20:
+        npctalk "Look at that you are getting better, but still a n00b";
+        end;
+    L_Lvl30:
+        npctalk "Look at that you are getting there, you are almost 2nd profession now right???";
+        end;
+    L_Lvl40:
+        npctalk "Look at that you are almost 2nd profession";
+        end;
 
-It also sets a special temporary character variable @menu, which contains the 
-number of option the player picked. (Numbering of options starts at 1.)
+Without the use if 'end' it would travel through the labels until the end of the 
+script. If you were lvl 10 or less, you would see all the speech lines, the use 
+of 'end' stops this, and ends the script.
 
-       menu "I want to Start",L_Start,"I want to end",L_End;
-    L_Start:
-       //If they click "I want to Start" they will end up here
-    L_End:
-       //If they click "I want to end" they will end up here
+---------------------------------------
 
-If a label is '-', the script execution will continue right after the menu 
-command if that option is selected, this can be used to save you time, and 
-optimize big scripts.
+*set <variable>,<expression>;
 
-        menu "I want to Start",-,"I want to end",L_End;
-        //If they click "I want to Start" they will end up here
-    L_End:
-        //If they click "I want to end" they will end up here
+This command will set a variable to the value that the expression results in. 
+This is the only way to set a variable directly.
 
-Both these examples will perform the same task.
+This is the most basic script command and is uses a lot whenever you try to do 
+anything more advanced than just printing text into a messagebox.
 
-If you give an empty string as a menu item, the item will not display. This
-can effectively be used to script dynamic menus by using empty string for
-entries that should be unavailable at that time.
+    set @x,100;
+    
+will make @x equal 100.
 
-You can do it by using arrays, but watch carefully - this trick isn't high 
-wizardry, but minor magic at least. You can't expect to easily duplicate it 
-until you understand how it works.
+    set @x,1+5/8+9;
+    
+will compute 1+5/8+9 (which is, surprisingly, 10 - remember, all numbers are 
+integer in this language) and make @x equal it.
 
-Create a temporary array of strings to contain your menu items, and populate it 
+---------------------------------------
+
+*setd "variable name",<value>;
+
+Works almost identical as set, just that the variable name is identified as a string, 
+thus can be constructed dynamically.
+
+Example:
+set $var$, "Poring";
+
+setd "$var$", "Poporing";
+mes $var$; // Will return Poporing
+
+setd "$" + $var$ + "123$", "Poporing is cool";
+mes $Poporing123$; // Will return Poporing is cool.
+
+---------------------------------------
+
+*getd("<variable name>")
+
+Retrieves variable, name can be constructed dynamically. Refer to setd for usage.
+
+Example:
+set @i, getd("$pikachu");
+
+---------------------------------------
+
+*getvariableofnpc <variable name>,<npc name>;
+
+Enables you to get a NPC variable (. prefix) from the given NPC. This can only be used to get . variables.
+Example(s):
+
+//This will return the value or .var, note that this can't be used, since the value isn't catched.
+	getvariableofnpc .var,"A NPC";
+	
+//This will set the .v variable to the value of the A NPC's .var variable.
+	set .v,getvariableofnpc(.var,"A NPC");
+
+---------------------------------------
+
+*goto <label>;
+
+This command will make the script jump to a label, usually used in conjunction 
+with other command, such as "if", but often used on it's own.
+
+		   ...
+           goto Label;
+           mes "This will not be seen";
+    Label:
+           mes "This will be seen";
+
+---------------------------------------
+
+*menu "<menu option>",<label>{,"<menu option>",<label>,...};
+
+This command will create a selectable menu for the invoking character. Only one 
+menu can be on screen at the same time.
+
+Depending on what the player picks from the menu, the script execution will 
+continue from the corresponding label. (it's string-label pairs, not label-
+string)
+
+It also sets a special temporary character variable @menu, which contains the 
+number of option the player picked. (Numbering of options starts at 1.)
+
+       menu "I want to Start",L_Start,"I want to end",L_End;
+    L_Start:
+       //If they click "I want to Start" they will end up here
+    L_End:
+       //If they click "I want to end" they will end up here
+
+If a label is '-', the script execution will continue right after the menu 
+command if that option is selected, this can be used to save you time, and 
+optimize big scripts.
+
+        menu "I want to Start",-,"I want to end",L_End;
+        //If they click "I want to Start" they will end up here
+    L_End:
+        //If they click "I want to end" they will end up here
+
+Both these examples will perform the same task.
+
+If you give an empty string as a menu item, the item will not display. This
+can effectively be used to script dynamic menus by using empty string for
+entries that should be unavailable at that time.
+
+You can do it by using arrays, but watch carefully - this trick isn't high 
+wizardry, but minor magic at least. You can't expect to easily duplicate it 
+until you understand how it works.
+
+Create a temporary array of strings to contain your menu items, and populate it 
 with the strings that should go into the menu at this execution, making sure not 
 to leave any gaps. Normally, you do it with a loop and an extra counter, like 
 this:
@@ -1104,9 +1150,9 @@ that should actually go into the menu based on your condition, and an array
 (Remember, arrays start with 0.) There's less of them than the possible menu 
 items you've defined, but the menu command can handle the empty lines - only if 
 they are last in the list, and if it's made this way, they are. Now comes a 
-dirty trick:
 
     // X is whatever the most menu items you expect to handle.
+dirty trick:
     menu @menulist$[0],-,@menulist$[1],-,....@menulist$[<X>],-;
 
 This calls up a menu of all your items. Since you didn't copy some of the 
@@ -1152,312 +1198,465 @@ perfectly equivalent.
 
 ---------------------------------------
 
-*rand(<number>{,<number>});
-
-This function returns a number, randomly positioned between 0 and the number you 
-specify (if you only specify one) and the two numbers you specify if you give it 
-two.
+*select("<option>"{,"<option>"..."<option>"})
+*prompt("<option>"{,"<option>"..."<option>"})
 
-rand(10) would result in 0,1,2,3,4,5,6,7,8 or 9
+This function is a handy replacement for 'menu' for some specific cases where 
+you don't want a complex label structure - like, for example, asking simple yes-
+no questions. It will return the number of menu option picked, starting with 1. 
+Like 'menu', it will also set the variable @menu to contain the option the user 
+picked.
 
-rand(2,10) would result in 2,3,4,5,6,7,8,9 or 10
+    if (select("Yes","No")==1) mes "You said yes, I know.";
 
----------------------------------------
+And like 'menu', this command has a problem with empty strings - if some of the 
+option strings given to it are empty, you won't be able to tell which one the 
+user really picked. The number it returns will only make sense if all the empty 
+strings are last in the list of options.
 
-*warp "<map name>",<x>,<y>;
+prompt works almost the same as select, except that when a character clicks
+the Cancel button, this function will return 255 instead.
 
-This command will take the invoking character to the specifed map, and if 
-wanted, specified coordinates too, but these can be random.
+---------------------------------------
 
-    warp "place.gat",50,55;
+*input <variable>;
 
-This would take them to X 50 Y 55 on the map called "place". If your X and Y 
-coordinates land on an unwalkable map square, it will send the warped character 
-to a random place. Same will happen if they are both zero:
+This command will make an input box pop up on the client connected to the 
+invoking character, to allow entering of a number or a string. This has many 
+uses, one example would be a guessing game, also making use of the 'rand' 
+function:
 
-    warp "place.gat",0,0;
+        mes "[Woman]";
+        mes "Try and guess the number I am thinking of.";
+        mes "The number will be between 1 and 10.";
+        next;
+        set @number, rand(1,10);
+        input @guess;
+        if(@guess==@number) goto L_Correct;
+        mes "[Woman]";
+        mes "Sorry, that wasn't the number I was thinking of.";
+        close;
+    L_Correct:
+        mes "[Woman]";
+        mes "Well done that was the number I was thinking of";
+        close;
 
-Notice that while warping people to coordinates 0,0 will normally get them into 
-a random place, it's not certain to always be so. Darned if I know where this is 
-actually coded, it might be that this happens because square 0,0 is unwalkable 
-on all official maps. If you're using custom maps, beware.
+If you give the input command a string variable to put the input in, it will 
+allow the player to enter text. Otherwise, only numbers will be allowed.
 
-There are also three special 'map names' you can use.
+        mes "[Woman]";
+        mes "Please say HELLO";
+        next;
+        input @var$;
+        if(@var$=="HELLO") goto L_Correct;
+        mes "[Woman]";
+        mes "Sorry you got it wrong";
+        close;
+    L_Correct:
+        mes "[Woman]";
+        mes "Well done you typed it correctly";
+        close;
 
-"Random" will warp the player randomly on the current map.
-"Save" and "SavePoint" will warp the player back to their savepoint.
+Notice that in current SVN, you may not input a negative number with this 
+command. This was done to prevent exploits in badly written scripts, which would 
+let people, for example, put negative amounts of zeny into a bank script and 
+recieve free zeny as a result. Unfortunately it limits the uses of the 'input' 
+command quite a bit.
 
 ---------------------------------------
 
-*areawarp "<from map name>",<x1>,<y1>,<x2>,<y2>,"<to map name>",<x3>,<y3>;
+*callfunc "<function>"{,<argument>,...<argument>};
+*callfunc("<function>"{,<argument>,...<argument>})
 
-This command is similar to 'warp', however, it will not refer to the invoking 
-character, but instead, all characters within a specified area, defined by the 
-x1/y1-x2/y2 square, will be warped. Nobody outside the area will be affected, 
-including the activating character, if they are outside the area.
+This command lets you call up a function NPC. A function NPC can be called from 
+any script on any map server. Using the 'return' command it will come back to 
+the place that called it.
 
-    areawarp "place.gat",10,10,120,120,"place2.gat",150,150;
+    place.gat,50,50,6%TAB%script%TAB%Woman%TAB%115,{
+        mes "[Woman]"
+        mes "Lets see if you win";
+        callfunc "funcNPC";
+        mes "Well done you have won";
+        close;
+    }
+    function%TAB%script%TAB%funcNPC%TAB%{
+        set @win, rand(2);
+        if(@win==0) return;
+        mes "Sorry you lost";
+        end;
+    }
 
-Everyone that is in the area between X 10 Y 10 and X 120 Y 120, in a square 
-shape, on the map called "place", will be affected, and warped to "place2" X 150 
-Y 150
+You can pass arguments to your function - values telling it what exactly to do -
+which will be available there with getarg() (see 'getarg')
+Notice that returning is not mandatory, you can end execution right there.
 
-    areawarp "place.gat",10,10,120,120,"place2.gat",0,0;
+If you want to return a real value from inside your function NPC, it is better 
+to write it in the function form, which will also work and will make the script 
+generally cleaner:
 
-By using ,0,0; as the destination coordinates it will take all the characters in 
-the affected area to a random set of co-ordinates on "place2".
+    place.gat,50,50,6%TAB%script%TAB%Man%TAB%115,{
+        mes "[Man]"
+        mes "Gimme a number!";
+        next;
+        input @number;
+        if (callfunc("OddFunc",@number)) mes "It's Odd!";
+        close;
+    }
+    function%TAB%script%TAB%OddFunc%TAB%{
+            if (getarg(0)%2==0) goto ItsEven;
+            return (1);
+        ItsEven:
+            return (0);
+    }
 
-Like 'warp', areawarp will also explicitly warp characters randomly into the 
-current map if you give the 'to map name' as "Random".
+---------------------------------------
 
-See also 'warp'.
+*callsub <label name>{,<argument>,...<argument>};
+
+This command will go to a specified label within the current script (do NOT use 
+quotes around it) coming in as if it were a 'callfunc' call, and pass it 
+arguments given, if any, which can be recovered there with 'getarg'. When done 
+there, you should use the 'return' command to go back to the point from where 
+this label was called. This is used when there is a specific thing the script 
+will do over and over, this lets you use the same bit of code as many times as 
+you like, to save space and time, without creating extra NPC objects which are 
+needed with 'callfunc'. A label is not callable in this manner from another 
+script.
 
+           mes "[Woman]"
+           mes "Lets see if you win";
+           callsub Check;
+           mes "Well done you have won";
+    Check:
+           set @win, rand(2);
+           if(@win==0) return;
+           mes "Sorry you lost";
+           
 ---------------------------------------
 
-*heal <hp>,<sp>;
+*getarg(<number>)
 
-This command will heal a set amount of HP and/or SP on the invoking character.
+This function is used when you use the 'callsub' or 'callfunc' commands. In the 
+call you can specify variables that will make that call different from another 
+one. This function willwill return an argument the function or subroutine was 
+called with, and is the normal way to get them. 
+This is another thing that can let you use the same but of code more than once. 
 
-    heal 30000,0; // This will heal 30,000 HP
-    heal 0,30000; // This will heal 30,000 SP
-    heal 300,300; // This will heal 300 HP and 300 SP
+Argument numbering starts with 0, i.e. the first argument you gave is number 0. 
+If no such argument was given, a zero is returned.
 
-This command just alters the hit points and spell points of the invoking 
-character and produces no other output whatsoever.
+    place.gat,50,50,6%TAB%script%TAB%Woman1%TAB%115,{
+        mes "[Woman]";
+        mes "Lets see if you win";
+        callfunc "funcNPC",2;
+        mes "Well done you have won";
 
----------------------------------------
+    ...
 
-*itemheal <hp>,<sp>;
+    place.gat,52,50,6%TAB%script%TAB%Woman2%TAB%115,{
+        mes "[Woman]";
+        mes "Lets see if you win";
+        callfunc "funcNPC",5;
+        mes "Well done you have won";
 
-This command works on the invoking character like 'heal', however, it is not 
-normally used in NPC scripts and will not work as expected there, but is used 
-all over in item scripts. 
-
-Unlike 'heal', which just alters hp/sp and doesn't do anything else at all, this 
-command also shows healing animations for potions and other stuff, checks 
-whether the potion was made by a famous alchemist and alters the amount healed, 
-etc, etc. Since which kind of effect is shown depends on what item was used, 
-using it in an NPC script will not have a desired effect.
+    ...
 
-There is also a nice example on using this with the 'rand' function, to give you 
-a random ammount of healing.
+    function%TAB%script%TAB%funcNPC%TAB%{
+        set @win, rand(getarg(0));
+        if(@win==0) return;
+        mes "Sorry you lost";
 
-    // This will heal anything thing from 100 to 150 HP and no SP
-    itemheal rand(100,150),0; 
+"woman1" NPC object calls the funcNPC. The argument it gives in this call is 
+stated as 2, so when the random number is generated by the 'rand' function, it 
+can only be 0 or 1. Whereas "woman2" gives 5 as the argument number 0 when 
+calling the function, so the random number could be 0, 1, 2, 3 or 4, this makes 
+"woman2" less likely to say the player won. 
 
----------------------------------------
+You can pass multiple arguments in a function call:
 
-*percentheal <hp>,<sp>;
+    callfunc "funcNPC",5,4,3;
 
-This command will heal the invoking character. It heals the character, but not 
-by a set value - it adds percent of their maximum HP/SP.
+getarg(0) would be 5, getarg(1) would be 4 and getarg(2) would be 3.
 
-    percentheal 100,0; // This will heal 100% HP
-    percentheal 0,100; // This will heal 100% SP
-    percentheal 50,50; // This will heal 50% HP and 50% SP
+'getarg()' can also be used to carry information back from using the "callfunc" 
+script command, if the 'return' command is set to return a value: 
 
-So the amount that this will heal will depend on the total ammount of HP or SP 
-you have maximum. Like 'heal', this will not call up any animations or effects.
+    place.gat,50,50,6%TAB%script%TAB%Woman%TAB%115,{
+        mes "[Woman]";
+        mes "Lets see if you win";
+        callfunc "funcNPC";
+        mes "Well it seems you have "+getarg(0);
+    }
+    function%TAB%script%TAB%funcNPC%TAB%{
+        set @win, rand(2);
+        if(@win==0) return(won);
+        return(lost);
+    }
+        
+It is, however, better to use 'set' to get this value instead (see 'callfunc') 
+because otherwise you can't call functions from within other functions. (Return 
+values mess up the stack.)        
 
 ---------------------------------------
 
-*jobchange <job number>{,<upper flag>};
+*return {(<value>)};
 
-This command will change the job class of the invoking character.
+When you use callsub or callfunc, this command allows you to go back to the 
+calling script. You can optionally return with a value telling the calling 
+program what exactly happened. To get at this value, you will have to use the 
+'set' command:
 
-    jobchange 1; // This would change your player into a Swordman
-    jobchange 4002; // This would change your player into a Swordman High
+    set <variable>,callfunc "<your function>"
 
-This command does work with numbers, but you can also use job names. The full 
-list of job names and the numbers they correspond to can be found in 
-'db/const.txt'.
+Note the round brackets. Turns out you have to enclose just about anything in 
+brackets if it isn't a straight number for the return command to work with it:
 
-    // This would change your player into a Swordman
-    jobchange Job_Swordman; 
-    // This would change your player into a Swordman High
-    jobchange Job_Swordman_High; 
+    return (@x+@y);
 
-'upper flag' can alternatively be used to specify the type of job one changes
-to. For example, jobchange Job_Swordman,1; will change the character to a high
-swordsman. The upper values are:
--1 (or when omitted): preserves the current job type.
-0: Normal/standard classes
-1: High/Advanced classes
-2: Baby classes
+Also note that
 
-This command will also set a permanent character-based variable 
-'jobchange_level' which will contain the job level at the time right before 
-changing jobs, which can be checked for later in scripts.
+    if (<condition>) return (<whatever>);
+
+does NOT always work, even though it would make scripts a lot cleaner, and it 
+might be wiser to avoid using it like that.
+
+For an example see 'callfunc' and 'callsub'
 
 ---------------------------------------
 
-*jobname <job number>
+*function <function name>;
+*<function name>;
+*function <function name> {
+<code>
+}
 
-This command retrieves the name of the given job using the msg_athena entries 550->650.
+(Skotlex stop being so selfish and give us all the commands T~T! J/k lol :P)
 
-		mes "[Kid]";
-		mes "I never thought I'd met a "+jobname(Class)+" here of all places.";
-		close;
+This works like callfunc, but doesn't support arguments like callfunc. It's used for cleaner
+and fast script that doesn't require arguments for it to work. Also they must be inside a script. 
+They're not separated scripts and they work more like labels.
 
----------------------------------------
+Note it looks like the normal declaration
 
-*eaclass {<job number>}
+Usage:
 
-This commands returns the "eA job-number" corresponding to the given class (if none is given, it returns uses
-the invoking player's class as argument). The eA job-number is also a class number system, but it's one that
-comes with constants which make it easy to convert among classes. The command will return -1 if you pass it a
-job number which doesn't has a eA Job value equivalent.
+You first Declare the function with function <function name>;.
 
-	set @eac, eaclass();
-	if ((@eac&EAJ_BASEMASK) == EAJ_SWORDMAN)
-		mes "You must be a swordman, knight, crusader, paladin, high swordman, lord knight, baby swordman,";
-		mes "baby knight or baby crusader.";
-	if (@eac&EAJL_UPPER)
-		mes "You are a rebirth job.";
-	if ((@eac&EAJ_UPPERMASK) == EAJ_SWORDMAN)
-		mes "You must be a Swordman, Baby Swordman or High Swordman.";
+Put the rest of your code. You can use then <function name>; to call the function. If it returns a value is unsure,
+test it if you want and give us some comments ;3
 
-For more information on the eA Job System, see the docs/ea_job_system.txt file.
+And at least, but inside the script itself, put the function <function name> {<code>}.
 
----------------------------------------
-*roclass <job number> {,<gender>}
+Example:
 
-Does the opposite of eaclass. That is, given a eA Job class, it returns which is the corresponding RO class number. 
-A gender is required because both Bard and Dancers share the same eA Job value (EAJ_BARDDANCER), if it isn't given, the
-gender of the executing player is taken (if there's no player running the script, male will be used by default).
-The command returns -1 when there isn't a valid class to represent the required job (for example, if you try to get the
-baby version of a Taekwon class).
+prontera.gat,154,189,4	script	Item seller	767,{
 
-	set @eac, eaclass();
-	//Check if class is already rebirth
-	if (@eac&EAJL_UPPER) {
-		mes "You look strong.";
+function SF_Selling;
+
+mes "I'll open this now if you have more than 50z and you are level 50 or bigger";
+next;
+
+if (Zeny > 50) && (BaseLevel > 50) {
+	mes "Welcome";
+	next;
+	SF_Selling;
+	close;
+} else
+
+set @needed,50-BaseLevel;
+mes "You either are Level "+BaseLevel+", thus you need "+@needed+" more levels";
+mes "to be able to use this npc; or you don't have enough zeny, so get some please";
+close;
+
+function SF_Selling {
+
+	mes "Would you like to buy a phracon for 50z?";
+	switch(select("Yes","No, thanks")) {
+
+	case 1:
+		mes "Ok, how many?";
+		input @quantity;
+		set @check,Zeny/50;
+		if (@quantity > @check) {
+			mes "Sorry but you can only have "+@check+" Phracons with "+Zeny;
+			close;
+		} else
+		next;
+		mes "here you have";
+		set Zeny,Zeny-@quantity*50;
+		getitem 1010,@quantity;
 		close;
-	}
-	set @eac, roclass(@eac|EAJL_UPPER);
-	//Check if class has a rebirth version
-	if (@eac != -1) {
-		mes "Bet you can't wait to become a "+jobname(@eac)+"!";
+	case 2:
+		mes "Good bye then";
 		close;
+		}
 	}
+	return;
+}
 
----------------------------------------
 
-*input <variable>;
+---------------------------------------
 
-This command will make an input box pop up on the client connected to the 
-invoking character, to allow entering of a number or a string. This has many 
-uses, one example would be a guessing game, also making use of the 'rand' 
-function:
+*if (<condition>) <statement>;
 
-        mes "[Woman]";
-        mes "Try and guess the number I am thinking of.";
-        mes "The number will be between 1 and 10.";
-        next;
-        set @number, rand(1,10);
-        input @guess;
-        if(@guess==@number) goto L_Correct;
-        mes "[Woman]";
-        mes "Sorry, that wasn't the number I was thinking of.";
-        close;
-    L_Correct:
-        mes "[Woman]";
-        mes "Well done that was the number I was thinking of";
-        close;
+This is the basic conditional statement command, and just about the only one 
+available in this scripting language. 
 
-If you give the input command a string variable to put the input in, it will 
-allow the player to enter text. Otherwise, only numbers will be allowed.
+The condition can be any expression. All expressions resulting in a non-zero 
+value will be considered True, including negative values. All expressions 
+resulting in a zero are false.
 
-        mes "[Woman]";
-        mes "Please say HELLO";
-        next;
-        input @var$;
-        if(@var$=="HELLO") goto L_Correct;
-        mes "[Woman]";
-        mes "Sorry you got it wrong";
-        close;
-    L_Correct:
-        mes "[Woman]";
-        mes "Well done you typed it correctly";
-        close;
+If the expression results in True, the statement will be executed. If it isn't 
+true, nothing happens and we move on to the next line of the script.
 
-Notice that in current SVN, you may not input a negative number with this 
-command. This was done to prevent exploits in badly written scripts, which would 
-let people, for example, put negative amounts of zeny into a bank script and 
-recieve free zeny as a result. Unfortunately it limits the uses of the 'input' 
-command quite a bit.
+    if (1)  mes "This will always print.";
+    if (0)  mes "And this will never print.";
+    if (5)  mes "This will also always print.";
+    if (-1) mes "Funny as it is, this will also print just fine.";
 
----------------------------------------
+For more information on conditional operators see the operators section above.
+Anything that is returned by a function can be used in a condition check without 
+bothering to store it in a specific variable:
 
-*setlook <look type>,<look value>;
+    if (strcharinfo(0)=="Daniel Jackson") mes "It is true, you are Daniel!";
 
-This command will alter the look data for the invoking character. It is used 
-mainly for changing the palette used on hair and clothes, you specify which look 
-type you want to change, then the palette you want to use. Make sure you specify 
-a palette number that exists/is usable by the client you use.
+More examples of using the 'if' command in the real world:
 
-    // This will change your hair(6), so that it uses palette 8, what ever your 
-    // palette 8 is your hair will use that colour
+Example 1:
 
-    setlook 6,8; 
+        set @var1,1;
+        input @var2;
+        if(@var1==@var2) goto L_Same;
+        mes "Sorry that is wrong";
+        close;
+    L_Same:
+        close;
 
-    // This will change your clothes(7), so they are using palette 1, whatever 
-    // your palette 1 is, your clothes will then use that set of colours.
+Example 2:
     
-    setlook 7,1; 
+    set @var1,1;
+    input @var2;
+    if(@var1!=@var2) mes "Sorry that is wrong";
+    close;
 
-Here are the possible look types:
- 
- 0 - Base sprite
- 1 - Hairstyle
- 2 - Weapon
- 3 - Head bottom
- 4 - Head top
- 5 - Head mid
- 6 - Hair color
- 7 - Clothes color
- 8 - Shield
- 9 - Shoes
+(Notice examples 1 and 2 have the same effect.)
 
-Whatever 'shoes' means is anybody's guess, ask Gravity - the client does nothing 
-with this value. It still wants it from the server though, so it is kept, but 
-normally doesn't do a thing.
- 
-Only the look data for hairstyle, hair color and clothes color are saved to the 
-char server's database and will persist. The rest freely change as the character 
-puts on and removes equipment, changes maps, logs in and out and otherwise you 
-should not expect to set them. In fact, messing with them is generally 
-hazardous, do it at your own risk, it is not tested what will this actually do -
-it won't cause database corruption and probably won't cause a server crash, but 
-it's easy to crash the client with just about anything unusual.
+Example 3:
 
-However, it might be an easy way to quickly check for empty view IDs for 
-sprites, which is essential for making custom headgear. 
+    set @var1,@var1+1;
+    mes "[Forgetfull Man]";
+    if (@var==1) mes "This is the first time you have talked to me";
+    if (@var==2) mes "This is the second time you have talked to me";
+    if (@var==3) mes "This is the third time you have talked to me";
+    if (@var==4) mes "This is the forth time you have talked to me, but I think I am getting amnesia, I have forgoten about you";
+    if (@var==4) set @var,0;
+    close;
 
-Since a lot of people have different palettes for hair and clothes, it's 
-impossible to tell you what all the colour numbers are. If you want a serious 
-example, there is a Stylist script inside the default eAthena installation that 
-you can look at, this may help you create a Stylist of your own: 
-'custom\dye.txt'
+Example 4:
 
----------------------------------------
+        mes "[Quest Person]";
+        if(countitem(512)>=1) goto L_GiveApple;
+        // The number 512 was found from item_db, it is the item number for the Apple.
+        mes "Can you please bring me an apple?";
+        close;
+    L_GiveApple:
+        mes "Oh an apple, I didnt want it, I just wanted to see one";
+        close;
 
-*set <variable>,<expression>;
+Example 5:
 
-This command will set a variable to the value that the expression results in. 
-This is the only way to set a variable directly.
+        mes "[Person Checker]";
+        if($name$!=null) goto L_Check;
+        mes "Please tell me someones name";
+        next;
+        input $name$;
+        set $name2$,strcharinfo(0);
+        mes "[Person Checker]";
+        mes "Thank you";
+    L_Check:
+        if($name$==strcharinfo(0) ) goto L_SameName;
+        mes "[Person Checker]";
+        mes "You are not the person that " +$name2$+ " mentioned";
+    L_End:
+        set $name$,null;
+        set $name2$,null;
+        close;
+    L_SameName:
+        mes "[Person Checker]";
+        mes "You are the person that " +$name2$+ " just mentioned";
+        mes "nice to meet you";
+        goto L_End;
 
-This is the most basic script command and is uses a lot whenever you try to do 
-anything more advanced than just printing text into a messagebox.
+See 'strcharinfo' for explanation of what this function does.
 
-    set @x,100;
-    
-will make @x equal 100.
+Example 6: Using complex conditions.
 
-    set @x,1+5/8+9;
-    
-will compute 1+5/8+9 (which is, surprisingly, 10 - remember, all numbers are 
-integer in this language) and make @x equal it.
+        mes "[Multi Checker]";
+        if( (@queststarted==1) && (countitem(512)>=5) ) goto L_MultiCheck;
+        // Only if the quest has been started AND You have 5 apples will it goto "L_MultiCheck"
+        mes "Please get me 5 apples";
+        set @queststarted,1;
+        close;
+    L_MultiCheck:
+        mes "[Multi Checker]";
+        mes "Well done you have started the quest of got me 5 apples";
+        mes "Thank you";
+        set @queststarted,0;
+        delitem 512,5;
+        close;
+
+With the Advanced scripting engine, we got nested if's. That is:
+
+if (<condition>)
+	dothis;
+else
+	dothat;
+	
+If the condition doesn't meet, it'll do the action following the else.
+We can also group several actions depending on a condition, the following way:
+
+if (<condition)
+{
+	dothis1;
+	dothis2;
+	dothis3;
+} else {
+	dothat1;
+	dothat2;
+	dothat3;
+	dothat4;
+}
+
+Remember that if you plan to do several actions upon the condition being false, and 
+you forget to use the curlies (the { } ), the second action will be executed regardless
+the output of the condition, unless of course, you stop the execution of the script if the
+condition is true (that is, in the first grouping using a return; , and end; or a close; )
+
+Also, you can have multiple conditions nested or chained, and don't worry about limits as to
+how many nested if you can have, there is no spoon ;)
+
+...
+if (<condition 1>)
+	dothis;
+else if (<condition 2>)
+{
+	dotheother;
+	do that;
+	end;
+} else
+	do this;
+...
+
+---------------------------------------
+
+*jump_zero (<condition>),<label>;
+
+This command works kinda like an 'if'+'goto' combination in one go. (See 'if'). 
+If the condition is false (equal to zero) this command will immediately jump to 
+the specified label like in 'goto'.
+
+While 'if' is more generally useful, for some cases this could be an 
+optimisation.
 
 ---------------------------------------
 
@@ -1498,7 +1697,7 @@ See 'setarray'.
 
 ---------------------------------------
 
-*copyarray <to array>[<first value>],<from array>[<first value>],<amount to copy>;
+*copyarray <destination array>[<first value>],<source array>[<first value>],<amount of data to copy>;
 
 This command lets you quickly shuffle a lot of data between arrays, which is in 
 some cases invaluable.
@@ -1517,37 +1716,18 @@ So using the examples above:
  @array[3]  = 400
  @array[4]  = 500
  @array[5]  = 600
-
+ 
+New Array:
  @array2[0] = 300
  @array2[1] = 400
- @array2[2] = 500
- @array2[3] = 0 
+ @array2[2] = 0
+ @array2[3] = 0
 
-Notice that @array[5] wont be coppied to the second array, and it will return a 
+Notice that @array[4] and @array[5] won't be copied to the second array, and it will return a 
 0.
 
 ---------------------------------------
 
-*getarraysize(<array name>);
-
-This function returns the number of values that are contained inside the 
-specified array. Notice that zeros and empty strings at the end of this array 
-are not counted towards this number.
-
-For example:
-
-    setarray @array[0], 100, 200, 300, 400, 500, 600;
-    set @arraysize,getarraysize(@array);
-
-This will make @arraysize == 6. But if you try this:
-
-    setarray @array[0], 100, 200, 300, 400, 500, 600, 0;
-    set @arraysize,getarraysize(@array);
-    
-@arraysize will still equal 6, even though you've set 7 values.    
-
----------------------------------------
-
 *deletearray <array name>[<first value>],<how much to delete>
 
 This command will delete a specified number of array elements totally from an 
@@ -1569,7 +1749,46 @@ memory entirely. This would be very handy, if it always worked.
 
 ---------------------------------------
 
-*getelementofarray(<array name>,<index>);
+======================================
+|2.- Information-retrieving commands.|
+======================================
+---------------------------------------
+
+*strcharinfo(<type>)
+
+This function will return either the name, party name or guild name for the 
+invoking character. Whatever it returns is determined by type.
+
+ 0 - Character's name.
+ 1 - The name of the party they're in if any.
+ 2 - The name of the guild they're in if any.
+ 
+If a character is not a member of any party or guild, an empty string will be 
+returned when requesting that information.
+
+---------------------------------------
+
+*getarraysize(<array name>)
+
+This function returns the number of values that are contained inside the 
+specified array. Notice that zeros and empty strings at the end of this array 
+are not counted towards this number.
+
+For example:
+
+    setarray @array[0], 100, 200, 300, 400, 500, 600;
+    set @arraysize,getarraysize(@array);
+
+This will make @arraysize == 6. But if you try this:
+
+    setarray @array[0], 100, 200, 300, 400, 500, 600, 0;
+    set @arraysize,getarraysize(@array);
+    
+@arraysize will still equal 6, even though you've set 7 values.    
+
+---------------------------------------
+
+*getelementofarray(<array name>,<index>)
 
 This function will return an array's element when given an index.
 
@@ -1584,1071 +1803,858 @@ which has the same effect.
 
 ---------------------------------------
 
-*if (<condition>) <statement>;
+*readparam(<parameter number>)
 
-This is the basic conditional statement command, and just about the only one 
-available in this scripting language. 
+This function will return the basic stats of an invoking character, referred to 
+by the parameter number. Instead of a number, you can use a parameter name if it 
+is defined in "db/const.txt".
 
-The condition can be any expression. All expressions resulting in a non-zero 
-value will be considered True, including negative values. All expressions 
-resulting in a zero are false.
+For reference, in there these things are defined:
 
-If the expression results in True, the statement will be executed. If it isn't 
-true, nothing happens and we move on to the next line of the script.
+StatusPoint, BaseLevel, SkillPoint, Class, Upper, Zeny, Sex, Weight, MaxWeight,
+JobLevel, BaseExp, JobExp, NextBaseExp, NextJobExp, Hp, MaxHp, Sp, MaxSp,
+BaseJob, Karma, Manner, bVit, bDex, bAgi, bStr, bInt, bLuk
 
-    if (1)  mes "This will always print.";
-    if (0)  mes "And this will never print.";
-    if (5)  mes "This will also always print.";
-    if (-1) mes "Funny as it is, this will also print just fine.";
+All of these also behave as variables, but don't expect to be able to just 'set' 
+all of them - some will not work for various internal reasons.
 
-For more information on conditional operators see the operators section above.
-Anything that is returned by a function can be used in a condition check without 
-bothering to store it in a specific variable:
+    // This would return how many status points you haven't spent yet
+    readparam(9)
 
-    if (strcharinfo(0)=="Daniel Jackson") mes "It is true, you are Daniel!";
+Using this particular information as a function call is not required. Just 
+putting
 
-More examples of using the 'if' command in the real world:
+    StatusPoint 
 
-Example 1:
+will give you the same result, and some of these parameters work just like 
+variables (i.e. you can 'set Zeny,100' to make the character have 100 zeny, 
+destroying whatever zeny they had before, or 'set Zeny,Zeny+100' to give them 
+100 zeny)
 
-        set @var1,1;
-        input @var2;
-        if(@var1==@var2) goto L_Same;
-        mes "Sorry that is wrong";
-        close;
-    L_Same:
-        close;
+You can also use this command to get stat values:
 
-Example 2:
-    
-    set @var1,1;
-    input @var2;
-    if(@var1!=@var2) mes "Sorry that is wrong";
+    readparam(bVit)
+    if(readparam(bVit)<=77) goto L_End;
+    mes "Only people with over 77 Vit are reading this";
+L_End:
     close;
 
-(Notice examples 1 and 2 have the same effect.)
-
-Example 3:
+---------------------------------------
 
-    set @var1,@var1+1;
-    mes "[Forgetfull Man]";
-    if (@var==1) mes "This is the first time you have talked to me";
-    if (@var==2) mes "This is the second time you have talked to me";
-    if (@var==3) mes "This is the third time you have talked to me";
-    if (@var==4) mes "This is the forth time you have talked to me, but I think I am getting amnesia, I have forgoten about you";
-    if (@var==4) set @var,0;
-    close;
+*getcharid(<type>{,"<character name>"})
 
-Example 4:
+This function will return a unique ID number of the invoking character, or, if a 
+character name is specified, of that character.
 
-        mes "[Quest Person]";
-        if(countitem(512)>=1) goto L_GiveApple;
-        // The number 512 was found from item_db, it is the item number for the Apple.
-        mes "Can you please bring me an apple?";
-        close;
-    L_GiveApple:
-        mes "Oh an apple, I didnt want it, I just wanted to see one";
-        close;
+Type is the kind of associated ID number required:
 
-Example 5:
+ 0 - Character ID number.
+ 1 - Party ID number.
+ 2 - Guild ID number.
+ 3 - Account ID number.
 
-        mes "[Person Checker]";
-        if($name$!=null) goto L_Check;
-        mes "Please tell me someones name";
-        next;
-        input $name$;
-        set $name2$,strcharinfo(0);
-        mes "[Person Checker]";
-        mes "Thank you";
-    L_Check:
-        if($name$==strcharinfo(0) ) goto L_SameName;
-        mes "[Person Checker]";
-        mes "You are not the person that " +$name2$+ " mentioned";
-    L_End:
-        set $name$,null;
-        set $name2$,null;
-        close;
-    L_SameName:
-        mes "[Person Checker]";
-        mes "You are the person that " +$name2$+ " just mentioned";
-        mes "nice to meet you";
-        goto L_End;
+For most purposes other than printing it, a number is better to have than a name 
+(people do horrifying things to their character names).
 
-See 'strcharinfo' for explanation of what this function does.
+If the character is not in a party or not in a guild, the function will return 0 
+if guild or party number is requested. If a name is specified and the character 
+is not found, 0 is returned.
 
-Example 6: Using complex conditions.
+If getcharid(0) returns a zero, the script got called not by a character and 
+doesn't have an attached RID. Note that this will cause the map server to
+print "player not attached!" error messages, so it is preferred to use
+"playerattached" to check for the character attached to the script.
 
-        mes "[Multi Checker]";
-        if( (@queststarted==1) && (countitem(512)>=5) ) goto L_MultiCheck;
-        // Only if the quest has been started AND You have 5 apples will it goto "L_MultiCheck"
-        mes "Please get me 5 apples";
-        set @queststarted,1;
-        close;
-    L_MultiCheck:
-        mes "[Multi Checker]";
-        mes "Well done you have started the quest of got me 5 apples";
-        mes "Thank you";
-        set @queststarted,0;
-        delitem 512,5;
-        close;
+if (getcharid(2)) mes "Only members of a guild are allowed beyond this point!";
 
 ---------------------------------------
 
-*getitem <item id>,<amount>{,<character ID>};
-*getitem "<item name>",<amount>{,<character ID>};
+*getchildid()
+*getmotherid()
+*getfatherid()
 
-This command will give a specific amount of specified items to the target 
-character. If the character is not online, nothing will happen.
-If <character ID> is not specified, items will be created in the invoking 
-character inventory instead.
+These functions return the characters (shild/mother/father) ID
 
-In the first and most commonly used version of this command, items are 
-referred to by their database ID number found inside 'db/item_db.txt'.
+    if (getmotherid()) mes "Oh... I know your mother's ID:"+getmotherid();
 
-    getitem 502,10 // The person will receive 10 apples
-    getitem 617,1  // The person will receive 1 Old Violet Box
+---------------------------------------
 
-Giving an item ID of -1 will give a specified number of random items from the 
-list of those that fall out of Old Blue Box. Unlike in all other cases, these 
-will be unidentified, if they turn out to be equipment. This is exactly what's 
-written in the Old Blue Box's item script.
+*ispartneron()
 
-Other negative IDs also correspond to other random item generating item tables:
+This function returns 1 if the invoking character's marriage partner is 
+currently online and 0 if they are not or if the character has no partner.
 
-Giving an item ID of -2 will produce the effects of Old Violet Box.
-Giving an item ID of -3 will produce the effects of Old Card Album.
-Giving an item ID of -4 will produce the effects of Gift Box.
-Giving an item ID of -5 will produce the effects of Worn Out Scroll, which, in 
-current SVN, drops only Jellopies anyway.
+---------------------------------------
 
-This transaction is logged if the log script generated transactions option is 
-enabled.
+*getpartnerid()
 
-You may also create an item by it's name in the 'english name' field in the 
-item database:
+This function returns the character ID of the invoking character's marriage 
+partner, if any. If the invoking character is not married, it will return 0, 
+which is a quick way to see if they are married:
 
-    getitem "RED_POTION",10;
+    if (getpartnerid()) mes "I'm not going to be your girlfriend!";
+    if (getpartnerid()) mes "You're married already!";
 
-Which will do what you'd expect. If it can't find that name in the database, 
-apples will be created anyway. It is often a VERY GOOD IDEA to use it like this.
+---------------------------------------
 
-This is used in pretty much all NPC scripts that have to do with items and 
-quite a few item scripts. For more examples check just about any official script.
+*getpartyname(<party id>)
 
----------------------------------------
+This function will return the name of a party that has the specified ID number. 
+If there is no such party ID, "null" will be returned.
 
-*getitem2 <item id>,<amount>,<identify>,<refine>,<attribute>,<card1>,<card2>,<card3>,<card4>{,<character ID>};
-*getitem2 "<Item name>",<amount>,<identify>,<refine>,<attribute>,<card1>,<card2>,<card3>,<card4>{,<character ID>};
+Lets say the ID of a party was saved as a global variable:
 
-This command will give an amount of specified items to the invoking character. 
-If an optional character ID is specified, and that character is currently 
-online, items will be created in their inventory instead. If they are not 
-online, nothing will happen. It works essentially the same as 'getitem' (it even 
-works for negative ID numbers the same way, which is kinda silly) but is a lot 
-more flexible, since it allows you to give the player an item altered with it's 
-specific properties. 
+    // This would return the name of the party from the ID stored in a variable
+    mes "You're in the '"+getpartyname($@var)"' party, I know!";
 
-Those parameters that are different from 'getitem' are:
+---------------------------------------
 
-identify    - Whether you want the item to be identified or not, 0 unidentified, 
-              1 identified.
-refine      - For how many plusses will it be refined.
-              It will not let you refine an item higher than +10, if you 
-              specify more it'll still be 10.
-attribute   - Whether the item is broken (1) or not (0) and NOT an elemental 
-              attribute. 
-card1,2,3,4 - If you want a card compound to it, place the card ID number into 
-              the specific card slot. Card ID numbers also found in 
-              'db/item_db.txt'
+*getpartymember <party id>,{<type>};
 
-Card1-card4 values are also used to store name information for named items, as 
-well as the elemental property of weapons and armor. You can create a named item 
-in this manner, however, if you just need a named piece of standard equipment, 
-it is much easier to the 'getnameditem' function instead.
+Thank you to HappyDenn for all this information.
 
-You will need to keep these values if you want to destroy and then perfectly 
-recreate a named item, for this see 'getinventorylist'.
+This command will finds all members of a specified party and returns their names 
+(or character id or account id depending on the value of "type") into an array
+of temporary global variables. There's actually quite a few commands like this
+which will fill a special variable with data upon execution and not do anything
+else.
 
-If you still want to try creating a named item with this command because 
-'getnameditem' won't do it for you cause it's too limited, you can do it like 
-this. Careful, minor magic ahead.
+Upon executing this,
 
-    // First, let's get an ID of a character who's name will be on the item.
-    // Only an existing character's name may be there.
-    // Let's assume our character is 'Adam' and find his ID.
-    
-    set @charid,getcharid(0,"Adam");
+$@partymembername$[] is a global temporary stringarray which contains all the 
+                     names of these party members
+                     (only set when type is 0 or not specified)
 
-    // Now we split the character ID number into two portions with a binary
-    // shift operation. If you don't understand what this does, just copy it.
-    
-    set @card3, @charid & 65535;
-    set @card4, @charid >> 16;
+$@partymembercid[]   is a global temporary number array which contains the 
+                     character id of these party members.
+                     (only set when type is 1)
 
-    // If you're inscribing non-equipment, @card1 must be 254.
-    // Arrows are also not equipment. :)
-    set @card1,254;
-    
-    // For named equipment, card2 means the Star Crumbs and elemental 
-    // crystals used to make this equipment. For everything else, it's 0.
-     
-    set @card2,0;
-    
-    // Now, let's give the character who invoked the script some 
-    // Adam's Apples:
-    
-    getitem2 512,1,1,0,0,@card1,@card2,@card3,@card4;
+$@partymemberaid[]   is a global temporary number array which contains the 
+                     account id of these party members.
+                     (only set when type is 2)
 
-This wasn't tested with all possible items, so I can't give any promises, 
-experiment first before relying on it.
+$@partymembercount   is the number of party members that were found.
 
-To create equipment, continue this example it like this:
+The party members will (apparently) be found regardless of whether they are 
+online or offline. Note that the names come in no particular order.
 
-    // We've already have card3 and card4 loaded with correct
-    // values so we'll just set up card1 and card2 with data
-    // for an Ice Stiletto.
+Be sure to use $@partymembercount to go through this array, and not 
+'getarraysize', because it is not cleared between runs of 'getpartymember'. If 
+someone with 7 party members invokes this script, the array would have 7 
+elements. But if another person calls up the NPC, and he has a party of 5, the 
+server will not clear the array for you, overwriting the values instead. So in 
+addition to returning the 5 member names, the 6th and 7th elements from the last 
+call remain, and you will get 5+2 members, of which the last 2 don't belong to 
+the new guy's party. $@partymembercount will always contain the correct number, 
+(5) unlike 'getarraysize()' which will return 7 in this case.
 
-    // If you're inscribing equipment, @card1 must be 255.
-    set @card1,255;
-    
-    // That's the number of star crumbs in a weapon.
-    set @sc,2;
-    
-    // That's the number of elemental property of the weapon.
-    set @ele,1;
+Example:
 
-    // And that's the wacky formula that makes them into
-    // a single number.    
-    set @card2,@ele+((@sc*5)<<8);
+   // get the character's party ID
+       getpartymember(getcharid(1));
 
-    // That will make us an Adam's +2 VVS Ice Stiletto:
-    
-    getitem2 1216,1,1,2,0,@card1,@card2,@card3,@card4;
+   // immediately copy $@partymembercount value to a new variable, since
+   // you don't know when 'getpartymember' will get called again for someone 
+   // else's party, overwriting your global array.
+       set @partymembercount,$@partymembercount;
 
-Experiment with the number of star crumbs - I'm not certain just how much will 
-work most and what it depends on. The valid element numbers are:
+   // copy $@partymembername array to a new array
+       copyarray @partymembername$[0],$@partymembername$[0],@partymembercount;
 
- 1 - Ice, 2 - Earth 3 - Fire 4 - Wind.
-    
-You can, apparently, even create duplicates of the same pet egg with this 
-command, creating a pet which is the same, but simultaneously exists in two 
-eggs, and may hatch from either, although, I'm not sure what kind of a mess will 
-this really cause.
+   //list the party members in NPC dialog
+       set @count,0;
+   L_DisplayMember:
+       if(@count == @partymembercount) goto L_DisplayMemberEnd;
+       mes (@count + 1) + ". ^0000FF" + @partymembername$[@count] + "^000000";
+       set @count,@count+1;
+       goto L_DisplayMember;
+   L_DisplayMemberEnd:
+       close;
 
 ---------------------------------------
-*groupranditem <group id>;
 
-Returns the item_id of a random item picked from the group specified. The
-different groups and their group number are specified in db/item_group_db.txt
+*getpartyleader <party id>,{<type>};
 
-When used in conjunction with other functions, you can get a random item. For
-example, for a random pet lure:
+This function returns some information about the given party-id's leader.
+When type is ommitted, the default information retrieved is the leader's name.
+Possible types are:
 
-getitem groupranditem(15),1;
+	1: Leader account id
+	2: Leader character id
+	3: Leader's class
+	4: Leader's current map name
+	5: Leader's current level as stored on the party structure (may not be
+	   current level if leader leveled up recently).
+
+If retrieval fails (leader not found or party does not exist), this function
+returns "null" instead of the character name, and -1 is for the other types.
 
 ---------------------------------------
 
-*makeitem <item id>,<amount>,<X>,<Y>,"<map name>";
-*makeitem "<item name>",<amount>,<X>,<Y>,"<map name>";
+*getlook(<type>)
 
-This command will create an item lying around on a specified map in the 
-specified location.
+This function will return the number for the currentcharacter look value 
+specified by type. See 'setlook' for valid look types.
 
- itemid   - Found in 'db/item_db.txt'
- amount   - Amount you want produced
- X        - The X coordinate
- Y        - The Y coordinate
- map name - The map name.
-
-This item will still disappear just like any other dropped item. Like 'getitem', 
-it also accepts an 'english name' field from the database and creates apples if 
-the name isn't found.
+This can be used to make a certain script behave differently for characters 
+dressed in black. :)
 
 ---------------------------------------
 
-*delitem <item id>,<amount>;
-*delitem "<item name>",<amount>;
-
-This command will take a specified amount of items from the invoking character. 
-As all the item commands, this one uses the ID of the item found inside 
-'db/item_db.txt'. The items are destroyed - there is no way an NPC can simply 
-own items and have an inventory of them, other as by destroying and recreating 
-them when needed.
-
-    delitem 502,10 // The person will lose 10 apples
-    delitem 617,1  // The person will lose 1 Old Violet Box
-
-It is always a good idea to to check if the player actually has the item before 
-you take it from them, Otherwise, you could try to delete items which the 
-players don't actually have, which won't fail and won't give an error message, 
-but might open up ways to exploit your script.
-
-Like 'getitem' this command will also accept an 'english name' field from the 
-database. If the name is not found, nothing will be deleted.
-
----------------------------------------
+*getsavepoint(<information type>)
 
-*delitem2 <item id>,<amount>,<identify>,<refine>,<attribute>,<card1>,<card2>,<card3>,<card4>{,<character ID>};
-*delitem2 "<Item name>",<amount>,<identify>,<refine>,<attribute>,<card1>,<card2>,<card3>,<card4>{,<character ID>};
+This function will return information about the invoking character's save point. 
+You can use it to let a character swap between several recorded savepoints. 
+Available information types are:
 
-This command will take a specified amount of items from the invoking character. 
-Check 'getitem2' to understand its expanded parameters.
+ 0 - Map name (a string)
+ 1 - X coordinate
+ 2 - Y coordinate
 
 ---------------------------------------
-
-*enable_items;
-*disable_items;
-
-These commands enable item usage while an npc is running. When enable_items is
-run, items can be used during scripts until disable_items is called. 
-To avoid possible exploits, when enable_items is invoked, it will only enable
-item usage while running that script in particular. Note that if a different
-script also calls enable_items, it will override the last call (so you may
-want to call this command at the start of your script without assuming the
-effect is still in effect).
-
+\\
+2,2 Item-related commands
+\\
 ---------------------------------------
 
-*viewpoint <action>,<x>,<y>,<point number>,<color>;
+*getequipid(<equipment slot>)
 
-This command will mark places on the mini map in the client connected to the 
-invoking character. It uses the normal X and Y coordinates from the main map. 
-The colors of the marks are defined using a hexidecimal number, same as the ones 
-used to color text in 'mes' output, but are written as hexadecimal numbers in C. 
-(They look like 0x<six numbers>.)
+This function returns the item ID of the item equipped in the equipment slot 
+specified on the invoking character. If nothing is equpped there, it returns -1. 
+Valid equipment slots are:
 
-Action is what you want to do with a point, 1 will set it, while 2 will clear 
-it. Point number is the number of the point - you can have several. If more than 
-one point is drawn at the same coordinates, they will cycle, which can be used 
-to create flashing marks.
+1  - Upper head gear
+2  - Armor (Where you keep your Jackets and Robes)
+3  - What is in your Left hand.
+4  - What is in your Right hand.
+5  - The garment slot (Mufflers, Hoods, Manteaus)
+6  - What foot gear the player has on.
+7  - Accessory 1.
+8  - Accessory 2.
+9  - Middle Headgear (masks and glasses)
+10 - Lower Headgear (beards, some masks)
 
-    // This command will show a mark at coordinates X 30 Y 40, is mark number 1, 
-    // and will be red.
-    
-    viewpoint 1,30,40,1,0xFF0000;
+Notice that a few items occupy several equipment slots, and if the character is 
+wearing such an item, 'getequipid' will return it's ID number for either slot.
 
-This will create three points:
+Can be used to check if you have something equiped, or if you haven't got 
+something equiped:
 
-    viewpoint 1,30,40,1,0xFF0000;
-    viewpoint 1,35,45,2,0xFF0000;
-    viewpoint 1,40,50,3,0xFF0000;
+        if(getequipid(1)==2234) goto L_WearingTiara;
+        mes "Come back when you have a Tiara on";
+        close;
+    L_WearingTiara:
+        mes "What a lovely Tiara you have on";
+        close;
 
-And this is how you remove them:
+You can also use it to make sure people don't pass a point before removing an 
+item totally from them. Let's say you don't want people to wear Legion Plate 
+armor, but also don't want them to equip if after the check, you would do this:
 
-    viewpoint 2,30,40,1,0xFF0000;
-    viewpoint 2,35,45,2,0xFF0000;
-    viewpoint 2,40,50,3,0xFF0000;
-    
-The client determines what it does with the points entirely, the server keeps no 
-memory of where the points are set whatsoever.
+        if ((getequipid(2) == 2341) || (getequipid(2) == 2342) goto L_EquipedLegionPlate; 
+    // the || is used as an or argument, there is 2341 and 2342 cause there are 
+    // two different legion plate armors, one with a slot one without.
+        if ((countitem(2341) > 0) || (countitem(2432) > 0) goto L_InventoryLegionPlate;
+        mes "I will lets you pass";
+        close2;
+        warp "place.gat",50,50;
+        end;
+    L_EquipedLegionPlate:
+        mes "You are wearing some Legion Plate Armor, please drop that in your stash before continuing";
+        close;
+    L_InventoryLegionPlate:
+        mes "You have some Legion Plate Armor in your inventory, please drop that in your stash before continuing";
+        close;
 
 ---------------------------------------
 
-*countitem(<item id>)
-*countitem("<item name>")
-
-This function will return the number of items for the specified item ID that the 
-invoking character has in the inventory.
-
-    mes "[Item Checker]";
-    mes "Hmmm, it seems you have "+countitem(502)+" apples";
-    close;
+*getequipname(<equpment slot>)
 
-Like 'getitem', this function will also accept an 'english name' from the 
-database as an argument.
+This function will return the name of the item equipped in the specified 
+equipment slot on the invoking character. Almost identical to 'getequipid', good 
+for an NPC to state what your are wearing, or maybe saving as a string variable. 
+See 'getequipid' for a full list of valid equipment slots.
 
-If you want to state the number at the end of a sentence, you can do it by 
-adding up strings:
+        if (getequipname(1)==0) goto L_No_HeadGear;
+        mes "So you are wearing a "+getequipname(1)+" on your head";
+        close;
+    L_No_HeadGear:
+        mes "You are not wearing any head gear";
+        close;
 
-    mes "[Item Checker]";
-    mes "Hmmm, the total number of apples you are holding is "+countitem("APPLE");
-    close;
-    
 ---------------------------------------
 
-*countitem2(<item id>,<identify>,<refine>,<attribute>,<card1>,<card2>,<card3>,<card4>)
-*countitem2("<item name>",<identify>,<refine>,<attribute>,<card1>,<card2>,<card3>,<card4>)
+*getitemname(<item id>)
 
-Expanded version of 'countitem' function, used for created/carded/forged items.
+Given the database ID number of an item, this function will return the text 
+stored in the 'japanese name' field (which, in eAthena, stores an english name 
+the players would normally see on screen.)
 
-This function will return the number of items for the specified item ID and
-other parameters that the invoking character has in the inventory.
-Check 'getitem2' to understand the arguments of the function.
-    
 ---------------------------------------
 
-*checkweight(<item id>,<amount>)
-*checkweight("<item name>",<amount>)
+*getbrokenid(<number>)
 
-This function will compute and return 1 if the total weight of a specified 
-number of specific items does not exceed the invoking character's carrying 
-capacity, and 0 otherwise. It is important to see if a player can carry the 
-items you expect to give them, failing to do that may open your script up to 
-abuse or create some very unfair errors.
+This function will search the invoking character's inventory for any broken 
+items, and will return their item ID numbers. Since the character may have 
+several broken items, 0 given as an argument will return the first one found, 1 
+will return the second one, etc. Will return 0 if no such item is found.
 
-Like 'getitem', this function will also accept an 'english name' from the 
-database as an argument.
+    // Let's see if they have anything broken:
+        if (getbrokenid(0)==0) goto Skip;
+    // They do, so let's print the name of the first broken item:
+        mes "Oh, I see you have a broken "+getitemname(getbrokenid(0))+" here!";
+    Skip:
+        mes "You don't have anything broken, quit bothering me.";
 
-    checkweight(502,10) // 10 apples
+---------------------------------------
 
-        if (checkweight(502,10) == 0 ) goto L_OverWeight;
-        getitem 502,10;
-        close;
-    L_OverWeight:
-        mes "Sorry you cannot hold this ammount of apples";
-        close;
+*getequipisequiped(<equipment slot>)
 
-Or to put this another way:
+This functions will return 1 if there is an equipment placed on the specified
+equipment slot and 0 otherwise. For a list of equipment slots 
+see 'getequipid'. Function originally used by the refining NPCs:
 
-        if (checkweight("APPLE",10)) goto L_Getapples;
-        mes "Sorry you cannot hold this ammount of apples";
+    if (getequipisequiped(1)) goto L_equipped;
+        mes "[Refiner]";
+        mes "Do you want me to refine your dumb head?";
         close;
-    L_Getapples:
-        getitem 502,10;
+    L_equipped:
+        mes "[Refiner]";
+        mes "That's a fine hat you are wearing there...";
         close;
 
-Both these examples have the same effect.
 
 ---------------------------------------
 
-*readparam(<parameter number>)
-
-This function will return the basic stats of an invoking character, referred to 
-by the parameter number. Instead of a number, you can use a parameter name if it 
-is defined in "db/const.txt".
-
-For reference, in there these things are defined:
-
-StatusPoint, BaseLevel, SkillPoint, Class, Upper, Zeny, Sex, Weight, MaxWeight,
-JobLevel, BaseExp, JobExp, NextBaseExp, NextJobExp, Hp, MaxHp, Sp, MaxSp,
-BaseJob, Karma, Manner, bVit, bDex, bAgi, bStr, bInt, bLuk
+*getequipisenableref(<equipment slot>)
 
-All of these also behave as variables, but don't expect to be able to just 'set' 
-all of them - some will not work for various internal reasons.
+Will return 1 if the item equipped on the invoking character in the specified 
+equipment slot is refinable, and 0 if it isn't. For a list of equipment slots 
+see 'getequipid'.
 
-    // This would return how many status points you haven't spent yet
-    readparam(9)
+        if (getequipisenableref(1)) goto L_Refine;
+        mes "[Refiner]";
+        mes "I can't refine this hat!...";
+        close;
+    L_Refine:
+        mes "[Refiner]";
+        mes "Ok I can refine this";
+        close;
 
-Using this particular information as a function call is not required. Just 
-putting
+---------------------------------------
 
-    StatusPoint 
+*getequiprefinerycnt(<equipment slot>)
 
-will give you the same result, and some of these parameters work just like 
-variables (i.e. you can 'set Zeny,100' to make the character have 100 zeny, 
-destroying whatever zeny they had before, or 'set Zeny,Zeny+100' to give them 
-100 zeny)
+Returns the current number of plusses for the item in the specified equipment 
+slot. For a list of equipment slots see 'getequipid'.
 
-You can also use this command to get stat values:
+Can be used to check if you have reached a maximum refine value, default for 
+this is +10:
 
-    readparam(bVit)
-    if(readparam(bVit)<=77) goto L_End;
-    mes "Only people with over 77 Vit are reading this";
-L_End:
-    close;
+        if(getequiprefinerycnt(1) < 10) goto L_Refine_HeadGear;
+        mes "Sorry, it's not possible to refine hats better than +10";
+        close;
+    L_Refine_HeadGear:
+        mes "I will now upgrade your "+getequipname(1);
 
 ---------------------------------------
 
-*getcharid(<type>{,"<character name>"})
+*getequipweaponlv(<equipment slot>)
 
-This function will return a unique ID number of the invoking character, or, if a 
-character name is specified, of that character.
-
-Type is the kind of associated ID number required:
-
- 0 - Character ID number.
- 1 - Party ID number.
- 2 - Guild ID number.
- 3 - Account ID number.
+This function returns the weapon level for the weapon equipped in the specified 
+equipment slot on the invoking character. For a list of equipment slots see 
+'getequipid'.
 
-For most purposes other than printing it, a number is better to have than a name 
-(people do horrifying things to their character names).
+Only 3 (Left hand) and 4 (Right hand) normally make sense, since only weapons 
+have a weapon level. You can, however, probably, use this field for other 
+equippable custom items as a flag or something. 
+If no item is equipped in this slot, or if it doesn't have a weapon level 
+according to the database, 0 will be returned.
 
-If the character is not in a party or not in a guild, the function will return 0 
-if guild or party number is requested. If a name is specified and the character 
-is not found, 0 is returned.
+    if(getequipweaponlv(4)==0) mes "Seems you don't have a weapon on";
+    if(getequipweaponlv(4)==1) mes "You are holding a lvl 1 weapon";
+    if(getequipweaponlv(4)==2) mes "You are holding a lvl 2 weapon";
+    if(getequipweaponlv(4)==3) mes "You are holding a lvl 3 weapon";
+    if(getequipweaponlv(4)==4) mes "You are holding a lvl 4 weapon";
+    if(getequipweaponlv(4)==5) mes "You are holding a lvl 5 weapon, hm, must be a custom design";
 
-If getcharid(0) returns a zero, the script got called not by a character and 
-doesn't have an attached RID. Note that this will cause the map server to
-print "player not attached!" error messages, so it is preferred to use
-"playerattached" to check for the character attached to the script.
+Or for the left hand, cause it can hold a weapon or a shield:
 
-if (getcharid(2)) mes "Only members of a guild are allowed beyond this point!";
+        if(getequipid(3)==0) goto L_NothingEquiped;
+        if(getequipweaponlv(3)==0) mes "You are holding a shield, so it doesnt have a level";
+        if(getequipweaponlv(3)==1) mes "You are holding a lvl 1 weapon";
+        if(getequipweaponlv(3)==2) mes "You are holding a lvl 2 weapon";
+        if(getequipweaponlv(3)==3) mes "You are holding a lvl 3 weapon";
+        if(getequipweaponlv(3)==4) mes "You are holding a lvl 4 weapon";
+        if(getequipweaponlv(3)==5) mes "You are holding a lvl 5 weapon, hm, must be a custom design";
+        close;
+    L_NothingEquiped:
+        mes "Seems you have nothing equiped";
+        close;
 
 ---------------------------------------
 
-*getpartyname(<party id>)
+*getequippercentrefinery(<equipment slot>)
 
-This function will return the name of a party that has the specified ID number. 
-If there is no such party ID, "null" will be returned.
+This function calculates and returns the percent value chance to successfully 
+refine the item found in the specified equipment slot of the invoking character 
+by +1. The actual formula is beyond the scope of this document, however, it is 
+calculated as if the character was a blacksmith trying to refine this particular 
+weapon, and depends on lots and lots of stuff. For a list of equipment slots see 
+'getequipid'.
 
-Lets say the ID of a party was saved as a global variable:
+These values can be displayed for the player to see, or used to calculate the 
+random change of a refine succeeding or failing and then going through with it 
+(which is what the official NPC refinery scripts use it for)
 
-    // This would return the name of the party from the ID stored in a variable
-    mes "You're in the '"+getpartyname($@var)"' party, I know!";
+// This will find a random number from 0 - 99 and if that is equal to or more 
+// than the value recoverd by this command it will go to L_Fail
+    if (getequippercentrefinery(3)<=rand(100)) goto L_Fail;
 
 ---------------------------------------
 
-*getpartymember <party id>,[<type>];
+*getareadropitem("<map name>",<x1>,<y1>,<x2>,<y2>,<item>)
 
-Thank you to HappyDenn for all this information.
+This function will count all the items with the specified ID number lying on the 
+ground on the specified map within the x1/y1-x2/y2 square on it and return that 
+number.
 
-This command will finds all members of a specified party and returns their names 
-(or character id or account id depending on the value of "type") into an array
-of temporary global variables. There's actually quite a few commands like this
-which will fill a special variable with data upon execution and not do anything
-else.
+This is the only function around where a parameter may be either a string or a 
+number! If it's a number, it means that only the items with that item ID number 
+will be counted. If it is a string, it is assumed to mean the 'english name' 
+field from the item database. If you give it an empty string, or something that 
+isn't found from the item database, it will count items number '512' (apples).
 
-Upon executing this,
+---------------------------------------
 
-$@partymembername$[] is a global temporary stringarray which contains all the 
-                     names of these party members
-                     (only set when type is 0 or not specified)
+*getequipcardcnt(<equipment slot>)
 
-$@partymembercid[]   is a global temporary number array which contains the 
-                     character id of these party members.
-                     (only set when type is 1)
+This function will return the number of cards that have been compounded onto a 
+specific equipped item for the invoking character. See 'getequipid' for a list 
+of possible equipment slots.
 
-$@partymemberaid[]   is a global temporary number array which contains the 
-                     account id of these party members.
-                     (only set when type is 2)
+---------------------------------------
 
-$@partymembercount   is the number of party members that were found.
+*getinventorylist;
 
-The party members will (apparently) be found regardless of whether they are 
-online or offline. Note that the names come in no particular order.
+This command sets a bunch of arrays with a complete list of whatever the 
+invoking character has in their inventory, including all the data needed to 
+recreate these items perfectly if they are destroyed. Here's what you get:
 
-Be sure to use $@partymembercount to go through this array, and not 
-'getarraysize', because it is not cleared between runs of 'getpartymember'. If 
-someone with 7 party members invokes this script, the array would have 7 
-elements. But if another person calls up the NPC, and he has a party of 5, the 
-server will not clear the array for you, overwriting the values instead. So in 
-addition to returning the 5 member names, the 6th and 7th elements from the last 
-call remain, and you will get 5+2 members, of which the last 2 don't belong to 
-the new guy's party. $@partymembercount will always contain the correct number, 
-(5) unlike 'getarraysize()' which will return 7 in this case.
+@inventorylist_id[]        - array of item ids.
+@inventorylist_amount[]    - their corresponding item amounts.
+@inventorylist_equip[]     - whether the item is equipped or not.
+@inventorylist_refine[]    - for how much it is refined.
+@inventorylist_identify[]  - whether it's refined.
+@inventorylist_attribute[] - whether it is broken.
+@inventorylist_card1[]     - These four arrays contain card data for the items.
+@inventorylist_card2[]       These data slots are also used to store names
+@inventorylist_card3[]       inscribed on the items, so you can explicitly check
+@inventorylist_card4[]       if the character owns an item made by a specific 
+                             craftsman.
+@inventorylist_count       - the number of items in these lists.
 
-Example:
+This could be handy to save/restore a character's inventory, since no other 
+command returns such a complete set of data, and could also be the only way to 
+correctly handle an NPC trader for carded and named items who could resell them 
+- since NPC objects cannot own items, so they have to store item data in 
+variables and recreate the items.
 
-   // get the character's party ID
-       getpartymember(getcharid(1));
+Notice that the variables this command generates are all local and numeric. 
 
-   // immediately copy $@partymembercount value to a new variable, since
-   // you don't know when 'getpartymember' will get called again for someone 
-   // else's party, overwriting your global array.
-       set @partymembercount,$@partymembercount;
+---------------------------------------
 
-   // copy $@partymembername array to a new array
-       copyarray @partymembername$[0],$@partymembername$[0],@partymembercount;
+*cardscnt()
 
-   //list the party members in NPC dialog
-       set @count,0;
-   L_DisplayMember:
-       if(@count == @partymembercount) goto L_DisplayMemberEnd;
-       mes (@count + 1) + ". ^0000FF" + @partymembername$[@count] + "^000000";
-       set @count,@count+1;
-       goto L_DisplayMember;
-   L_DisplayMemberEnd:
-       close;
+This function will return the number of cards inserted into the weapon currently 
+equipped on the invoking character.
+While this function was meant for item scripts, it will work outside them:
 
----------------------------------------
+    if (cardscnt()==4) mes "So you've stuck four cards into that weapon, think you're cool now?";
 
-*getpartyleader <party id>,[<type>];
+---------------------------------------
 
-This function returns some information about the given party-id's leader.
-When type is ommitted, the default information retrieved is the leader's name.
-Possible types are:
+*getrefine()
 
-	1: Leader account id
-	2: Leader character id
-	3: Leader's class
-	4: Leader's current map name
-	5: Leader's current level as stored on the party structure (may not be
-	   current level if leader leveled up recently).
+This function will return the number of plusses the weapon currently equipped on 
+the invoking character has been refined for.
+While this function was meant for item scripts, it will work outside them:
 
-If retrieval fails (leader not found or party does not exist), this function
-returns "null" instead of the character name, and -1 is for the other types.
+    if (getrefine()==10) mes "Wow. That's a murder weapon.";
 
 ---------------------------------------
-*getguildname(<guild id>)
 
-This function returns a guild's name given an ID number. If there is no such 
-guild, "null" will be returned;
-
-   // Would print what ever guild 10007 is, in my case this would return "AlcoROhics"
-   mes "The guild "+GetGuildName(10007)+" are all nice people.";
+*getnameditem(<item id>,"<name to inscribe>");
+*getnameditem("<item name>","<name to inscribe>");
 
-   // This will do the same as above:
-   set @var,10007;
-   mes "We have some friends in "+GetGuildName(@var)+", you know.";
+This function is equivalent to using 'getitem', however, it will not just give 
+the character an item object, but will also inscribe it with a specified 
+character's name. You may not inscribe items with arbitrary strings, only with 
+names of characters that actually exist. While this isn't said anywhere 
+specifically, apparently, named items may not have cards in them, slots or no -
+these data slots are taken by the character ID who's name is inscribed. Only one 
+remains free and it's not quite clear if a card may be there.
 
-This is used all over the WoE controlling scripts. You could also use it for a 
-guild-based event.
+This function will return 1 if an item was successfully created and 0 if it
+wasn't for whatever reason. Like 'getitem', this function will also accept an
+'english name' from the item database as an item name and will return 0 if no
+such item exists.
 
 ---------------------------------------
 
-*getguildmaster(<guild id>)
+*getitemslots(<item ID>)
 
-This function return the name of the master of the guild which has the specified 
-ID number. If there is no such guild, "null" will be returned.
+This function will look up the item with the specified ID number in the database 
+and return the number of slots this kind of items has - 0 if they are not 
+slotted. It will also be 0 for all non-equippable items, naturally, unless 
+someone messed up the item database. It will return -1 if there is no such item.
 
-// Would return the guild master of guild 10007, whatever that might be.
-// In this example it would return "MissDjax" cause she owns "AlcoROhics" (10007)
-    mes getguildmaster(10007)+" runs "+getguildname(10007);
+---------------------------------------
 
-Can be used to check if the character is the guildmaster of the specified guild.
+*getiteminfo(<item ID>,<type>)
 
-Maybe you want to make a room only guildmasters can enter:
+This function will look up the item with the specified ID number in the database 
+and return the info set by TYPE argument.
+It will return -1 if there is no such item.
 
-        set @GID,getcharid(2);
-        if(@GID==0) goto L_NoGuild;
-        if(strcharinfo(0)==getguildmaster(@GID)) goto L_GuildMaster;
-        mes "Sorry you don't own the guild you are in";
-        close;
-    L_NoGuild:
-        mes "Sorry you are not in a guild";
-        close;
-    L_GuildMaster:
-        mes "Welcome guild master of "+GetGuildName(@GID);
-        close;
+Valid types are:
+	0 - Buy Price; 1 - Sell Price; 2 - Item Type;
+	3 - maxchance (Max drop chance of this item e.g. 1 = 0.01% , etc..
+		if = 0, then monsters don't drop it at all (rare or a quest item)
+		if = 10000, then this item is sold in NPC shops only
+	4 - sex; 5 - equip; 6 - weight; 7 - atk; 8 - def; 9 - range;
+	10 - slot; 11 - look; 12 - elv; 13 - wlv;
 
+Check sample in nps\sample\getiteminfo.txt
 
 ---------------------------------------
-*guildchangegm(<guild id>,<new master's name>)
 
-This function will change the Guild Master of a guild. The ID is the guild's
-id, and the new guildmaster's name must be passed.
+*getequipcardid (<equipment slot>,<card slot>);
 
-Returns 1 on success, 0 otherwise.
+Returns value from equipped item slot in the indicated slot:
 
----------------------------------------
-*getguildmasterid(<guild id>)
+getequipcardid(num,slot)
 
-This function will return the character ID number of the guildmaster of the 
-guild specified by the ID. 0 if the character is not a guildmaster of any guild.
+where:
+	num = eqip position slot
+	slot = 0,1,2,3 (Card Slot N)
 
----------------------------------------
+This func returns CARD ID, 255,254,-255 (for card 0, if the item is produced) it's useful 
+when you want to check item cards or if it's signed. Useful for such quests as 
+"Sign this refined item with players name" etc;
+	Hat[0] +4 -> Player's Hat[0] +4
+	
+--------------------------------------
 
-*strcharinfo(<type>)
+* getitemslots (<item id>);
 
-This function will return either the name, party name or guild name for the 
-invoking character. Whatever it returns is determined by type.
+Returns the amount of slots the item has.
 
- 0 - Character's name.
- 1 - The name of the party they're in if any.
- 2 - The name of the guild they're in if any.
- 
-If a character is not a member of any party or guild, an empty string will be 
-returned when requesting that information.
+Example(s):
 
+//@slots now has the amount of slots of the item with ID 1205.
+	set @slots, getItemSlots(1205);
+	
+--------------------------------------
+//
+2,1.- End of item-related commands.
+//
 ---------------------------------------
 
-*getequipid(<equipment slot>)
+*getmapxy("<variable for map name>",<variable for x>,<variable for y>,<type>{,"<search string>"})
 
-This function returns the item ID of the item equipped in the equipment slot 
-specified on the invoking character. If nothing is equpped there, it returns -1. 
-Valid equipment slots are:
+This function will locate a character object, NPC object or pet's coordinates 
+and place their coordinates into the variables specified when calling it. It 
+will return 0 if the search was successful, and -1 if the parameters given were 
+not variables or the search was not successful.
 
-1  - Upper head gear
-2  - Armor (Where you keep your Jackets and Robes)
-3  - What is in your Left hand.
-4  - What is in your Right hand.
-5  - The garment slot (Mufflers, Hoods, Manteaus)
-6  - What foot gear the player has on.
-7  - Accessory 1.
-8  - Accessory 2.
-9  - Middle Headgear (masks and glasses)
-10 - Lower Headgear (beards, some masks)
+Type is the type of object to search for:
 
-Notice that a few items occupy several equipment slots, and if the character is 
-wearing such an item, 'getequipid' will return it's ID number for either slot.
+  0 - Character object
+  1 - NPC object
+  2 - Pet object
+  3 - Monster object.
+  
+While 3 is meant to look for a monster object, no searching will be done if you 
+specify type 3, and the function will always return -1.
 
-Can be used to check if you have something equiped, or if you haven't got 
-something equiped:
+The search string is optional. If it is not specified, the location of the 
+invoking character will always be returned for types 0 and 2, the location of 
+the NPC running this function for type 1.
+If a search string is specified, for types 0 and 1, the character or NPC with 
+the specified name will be located. If type is 3, the search will locate the 
+current pet of the character who's name is given in the search string, it will 
+NOT locate a pet by name.
 
-        if(getequipid(1)==2234) goto L_WearingTiara;
-        mes "Come back when you have a Tiara on";
-        close;
-    L_WearingTiara:
-        mes "What a lovely Tiara you have on";
-        close;
+What a mess. Example, a working and tested one now:
 
-You can also use it to make sure people don't pass a point before removing an 
-item totally from them. Let's say you don't want people to wear Legion Plate 
-armor, but also don't want them to equip if after the check, you would do this:
+    prontera.gat,164,301,3%TAB%script%TAB%Meh%TAB%730,{
+        mes "My name is Meh. I'm here so that Nyah can find me.";
+        close;
+    }
 
-        if ((getequipid(2) == 2341) || (getequipid(2) == 2342) goto L_EquipedLegionPlate; 
-    // the || is used as an or argument, there is 2341 and 2342 cause there are 
-    // two different legion plate armors, one with a slot one without.
-        if ((countitem(2341) > 0) || (countitem(2432) > 0) goto L_InventoryLegionPlate;
-        mes "I will lets you pass";
-        close2;
-        warp "place.gat",50,50;
-        end;
-    L_EquipedLegionPlate:
-        mes "You are wearing some Legion Plate Armor, please drop that in your stash before continuing";
+    prontera.gat,164,299,3%TAB%script%TAB%Nyah%TAB%730,{
+        mes "My name is Nyah.";
+        mes "I will now search for Meh all across the world!";
+        if (getmapxy(@mapname$,@mapx,@mapy,1,"Meh")!=0) goto Notfound;
+        mes "And I found him on map "+@mapname$+" at X:"+@mapx+" Y:"+@mapy+" !";
         close;
-    L_InventoryLegionPlate:
-        mes "You have some Legion Plate Armor in your inventory, please drop that in your stash before continuing";
+    Notfound:
+        mes "I can't seem to find Meh anywhere!";
         close;
+   }
+   
+Notice that NPC objects disabled with 'disablenpc' will still be located.
 
 ---------------------------------------
 
-*getequipname(<equpment slot>)
+*getgmlevel()
 
-This function will return the name of the item equipped in the specified 
-equipment slot on the invoking character. Almost identical to 'getequipid', good 
-for an NPC to state what your are wearing, or maybe saving as a string variable. 
-See 'getequipid' for a full list of valid equipment slots.
+This function will return the GM level of the account to which the invoking 
+character belongs. If this is somehow executed from a console command, 99 will 
+be returned, and 0 will be returned if the account has no GM level.
 
-        if (getequipname(1)==0) goto L_No_HeadGear;
-        mes "So you are wearing a "+getequipname(1)+" on your head";
-        close;
-    L_No_HeadGear:
-        mes "You are not wearing any head gear";
-        close;
+This allows you to make NPC's only accessable for certain GM levels, or behave 
+specially when talked to by GMs.
+
+   if (getgmlevel()) mes "What is your command, your godhood?";
+   if (getgmlevel()) goto Wherever;
 
 ---------------------------------------
 
-*getbrokenid(<number>)
+*gettimetick(<tick type>)
 
-This function will search the invoking character's inventory for any broken 
-items, and will return their item ID numbers. Since the character may have 
-several broken items, 0 given as an argument will return the first one found, 1 
-will return the second one, etc. Will return 0 if no such item is found.
+This function will return the system time in UNIX epoch time (if tick type is 2) 
+or the time since the start of the current day in seconds if tick type is 1.
+Passing 0 will make it return the server's tick, which is a measurement in
+milliseconds used by the server's timer system. The server's tick is an
+unsigned int which loops every ~50 days.
 
-    // Let's see if they have anything broken:
-        if (getbrokenid(0)==0) goto Skip;
-    // They do, so let's print the name of the first broken item:
-        mes "Oh, I see you have a broken "+getitemname(getbrokenid(0))+" here!";
-    Skip:
-        mes "You don't have anything broken, quit bothering me.";
+Just in case you don't know, UNIX epoch time is the number of seconds elapsed 
+since 1st of January 1970, and is useful to see, for example, for how long the 
+character has been online with OnPCLoginEvent and OnPCLogoutEvent, which could allow 
+you to make an 'online time counted for conviction only' jail script.
 
 ---------------------------------------
 
-*repair <broken item number>;
+*gettime(<type>)
 
-This command repairs a broken peice of equipment, using the same list of broken 
-items as available through 'getbrokenid'.
+This function will return specified information about the current system time.
 
-The official scripts seem to use the repair command as a function instead: 
-'repair(<number>)' but it returns nothing on the stack. Probably only Valaris, 
-who made it, can answer why is it so.
+1 - Seconds (of a minute)
+2 - Minutes (of an hour)
+3 - Hour (of a day)
+4 - Week day (0 for Sunday, 6 is Saturday)
+5 - Day of the month.
+6 - Number of the month.
+7 - Year.
+8 - Day of the year.
+
+It will only return numbers.
+
+    if (gettime(4)==6) mes "It's a Saturday. I don't work on Saturdays.";
 
 ---------------------------------------
 
-*getequipisequiped(<equipment slot>)
+*gettimestr(<format string>,<max length>)
 
-This functions will return 1 if there is an equipment placed on the specified
-equipment slot and 0 otherwise. For a list of equipment slots 
-see 'getequipid'. Function originally used by the refining NPCs:
+This function will return a string containing time data as specified by the 
+format string.
 
-    if (getequipisequiped(1)) goto L_equipped;
-        mes "[Refiner]";
-        mes "Do you want me to refine your dumb head?";
-        close;
-    L_equipped:
-        mes "[Refiner]";
-        mes "That's a fine hat you are wearing there...";
-        close;
+This uses the C function 'strfmtime', which obeys special format characters. For 
+a full description see, for example, the description of 'strfmtime' at 
+http://www.delorie.com/gnu/docs/glibc/libc_437.html
+All the format characters given in there should properly work.
+Max length is the maximum length of a time string to generate.
+
+The example given in eAthena sample scripts works like this:
 
+  mes gettimestr("%Y-%m/%d %H:%M:%S",21);
+  
+This will print a full date and time like 'YYYY-MM/DD HH:MM:SS'.
 
 ---------------------------------------
 
-*getequipisenableref(<equipment slot>)
+*getusers(<type>)
 
-Will return 1 if the item equipped on the invoking character in the specified 
-equipment slot is refinable, and 0 if it isn't. For a list of equipment slots 
-see 'getequipid'.
+This function will return a number of users on a map or the whole server. What 
+it returns is specified by Type.
 
-        if (getequipisenableref(1)) goto L_Refine;
-        mes "[Refiner]";
-        mes "I can't refine this hat!...";
-        close;
-    L_Refine:
-        mes "[Refiner]";
-        mes "Ok I can refine this";
-        close;
+Type is a bitmask, add up to get the effects you want:
+
+  8 - This will count all characters on the same map as the current NPC.
+      (By default, it will count people on the same map as the character)
+  7 - Return the amount of players for the entire server.
+      (By default, only the players on the map will be counted.)
+      
+So 'getusers(0)' will return the number of characters on the same map as the 
+invoking character, while 'getusers(7)' will give the count for entire server.
 
 ---------------------------------------
 
-*getequipisidentify(<equipment slot>)
+*getmapusers("<map name>")
 
-This function will return 1 if an item in the specified equipment slot is 
-identified and 0 if it isn't. Since you can't even equip unidentified equipment, 
-there's a question of whether it can actually end up there, and it will normally 
-return 1 all the time if there is an item in this equipment slot.
-Which is kinda pointless.
-For a list of equipment slots see 'getequipid'.
+This function will return the number of users currently located on the specified 
+map.
+
+Currently being used in the PVP scripts to check if a PVP room is full of not, 
+if the number returned it equal to the maximum allowed it will not let you 
+enter.
 
 ---------------------------------------
 
-*getequiprefinerycnt(<equipment slot>)
+*getareausers("<map name>",<x1>,<y1>,<x2>,<y2>)
 
-Returns the current number of plusses for the item in the specified equipment 
-slot. For a list of equipment slots see 'getequipid'.
+This function will return the count of connected characters which are located 
+within the specified area - an x1/y1-x2/y2 square on the specified map.
 
-Can be used to check if you have reached a maximum refine value, default for 
-this is +10:
+This is useful for maps that are split into many buildings, such as all the 
+"*_in.gat" maps, due to all the shops and houses.
 
-        if(getequiprefinerycnt(1) < 10) goto L_Refine_HeadGear;
-        mes "Sorry, it's not possible to refine hats better than +10";
-        close;
-    L_Refine_HeadGear:
-        mes "I will now upgrade your "+getequipname(1);
+---------------------------------------
+
+*getusersname;
+
+This command will give the invoking character a list of names of the connected 
+characters (including themselves) into an NPC script message window (see 'mes') 
+paging it by 10 names as if with the 'next' command.
+
+You need to put a 'close' after that yourself.
 
 ---------------------------------------
+\\
+2,2.- Guild-related commands
+\\
+---------------------------------------
+*getguildname(<guild id>)
 
-*getequipweaponlv(<equipment slot>)
+This function returns a guild's name given an ID number. If there is no such 
+guild, "null" will be returned;
 
-This function returns the weapon level for the weapon equipped in the specified 
-equipment slot on the invoking character. For a list of equipment slots see 
-'getequipid'.
+   // Would print what ever guild 10007 is, in my case this would return "AlcoROhics"
+   mes "The guild "+GetGuildName(10007)+" are all nice people.";
 
-Only 3 (Left hand) and 4 (Right hand) normally make sense, since only weapons 
-have a weapon level. You can, however, probably, use this field for other 
-equippable custom items as a flag or something. 
-If no item is equipped in this slot, or if it doesn't have a weapon level 
-according to the database, 0 will be returned.
+   // This will do the same as above:
+   set @var,10007;
+   mes "We have some friends in "+GetGuildName(@var)+", you know.";
 
-    if(getequipweaponlv(4)==0) mes "Seems you don't have a weapon on";
-    if(getequipweaponlv(4)==1) mes "You are holding a lvl 1 weapon";
-    if(getequipweaponlv(4)==2) mes "You are holding a lvl 2 weapon";
-    if(getequipweaponlv(4)==3) mes "You are holding a lvl 3 weapon";
-    if(getequipweaponlv(4)==4) mes "You are holding a lvl 4 weapon";
-    if(getequipweaponlv(4)==5) mes "You are holding a lvl 5 weapon, hm, must be a custom design";
+This is used all over the WoE controlling scripts. You could also use it for a 
+guild-based event.
 
-Or for the left hand, cause it can hold a weapon or a shield:
+---------------------------------------
 
-        if(getequipid(3)==0) goto L_NothingEquiped;
-        if(getequipweaponlv(3)==0) mes "You are holding a shield, so it doesnt have a level";
-        if(getequipweaponlv(3)==1) mes "You are holding a lvl 1 weapon";
-        if(getequipweaponlv(3)==2) mes "You are holding a lvl 2 weapon";
-        if(getequipweaponlv(3)==3) mes "You are holding a lvl 3 weapon";
-        if(getequipweaponlv(3)==4) mes "You are holding a lvl 4 weapon";
-        if(getequipweaponlv(3)==5) mes "You are holding a lvl 5 weapon, hm, must be a custom design";
-        close;
-    L_NothingEquiped:
-        mes "Seems you have nothing equiped";
-        close;
-
----------------------------------------
-
-*getequippercentrefinery(<equipment slot>)
-
-This function calculates and returns the percent value chance to successfully 
-refine the item found in the specified equipment slot of the invoking character 
-by +1. The actual formula is beyond the scope of this document, however, it is 
-calculated as if the character was a blacksmith trying to refine this particular 
-weapon, and depends on lots and lots of stuff. For a list of equipment slots see 
-'getequipid'.
+*getguildmaster(<guild id>)
 
-These values can be displayed for the player to see, or used to calculate the 
-random change of a refine succeeding or failing and then going through with it 
-(which is what the official NPC refinery scripts use it for)
+This function return the name of the master of the guild which has the specified 
+ID number. If there is no such guild, "null" will be returned.
 
-// This will find a random number from 0 - 99 and if that is equal to or more 
-// than the value recoverd by this command it will go to L_Fail
-    if (getequippercentrefinery(3)<=rand(100)) goto L_Fail;
+// Would return the guild master of guild 10007, whatever that might be.
+// In this example it would return "MissDjax" cause she owns "AlcoROhics" (10007)
+    mes getguildmaster(10007)+" runs "+getguildname(10007);
 
----------------------------------------
+Can be used to check if the character is the guildmaster of the specified guild.
 
-*successrefitem <equipment slot>;
+Maybe you want to make a room only guildmasters can enter:
 
-This command will refine an item in the specified equipment slot of the invoking 
-character by +1. For a list of equipment slots see 'getequipid'. This command 
-will not only add the +1, but also display a 'refine success' effect on the 
-character and put appropriate messages into their chat window. It will also give 
-the character fame points if a weapon reached +10 this way, even though these 
-will only take effect for blacksmith who will later forge a weapon.
+        set @GID,getcharid(2);
+        if(@GID==0) goto L_NoGuild;
+        if(strcharinfo(0)==getguildmaster(@GID)) goto L_GuildMaster;
+        mes "Sorry you don't own the guild you are in";
+        close;
+    L_NoGuild:
+        mes "Sorry you are not in a guild";
+        close;
+    L_GuildMaster:
+        mes "Welcome guild master of "+GetGuildName(@GID);
+        close;
 
-The official scripts seem to use the 'successrefitem' command as a function 
-instead: 'successrefitem(<number>)' but it returns nothing on the stack. 
-This is since jAthena, so probably nobody knows for sure why is it so.
 
 ---------------------------------------
 
-*failedrefitem <equipment slot>;
-
-This command will fail to refine an item in the specified equipment slot of the 
-invoking character. The item will be destroyed. This will also display a 'refine 
-failure' effect on the character and put appropriate messages into their chat 
-window.
-
-The official scripts seem to use the 'failedrefitem' command as a function 
-instead: 'failedrefitem(<number>)' but it returns nothing on the stack. This is 
-since jAthena, so probably nobody knows for sure why is it so.
+*getguildmasterid(<guild id>)
 
+This function will return the character ID number of the guildmaster of the 
+guild specified by the ID. 0 if the character is not a guildmaster of any guild.
 
 ---------------------------------------
 
-*cutin "<filename with no extension>",<position>;
-
-This command will display a picture stored in the GRF file in the client for the 
-player. 
-
-The files are taken from '\data\texture\A_AŁAIŹI’„AI«§\illust' directory in the 
-GRF file. The filename must be given with no extension, '.bmp' is added by the 
-client itself and you can't have any other picture format displayed as a cutin. 
-The biggest one that comes with the client is 400x503 pixels, and the smallest 
-is 303x493 pixels, it is not known how big a picture has to be before the client 
-goes insane. Bright magenta (color FF00FF) is considered to be transparent in 
-these pictures. You can easily add and alter them, but how to do this is outside 
-of the scope of this document.
-
-The position determines just where on screen the picture will appear:
-  0 - bottom left corner
-  1 - bottom middle
-  2 - bottom right corner
-  3 - middle of screen in a movable window with an empty title bar.
-  4 - middle of screen without the window header, but still movable.
-  255 - will remove the cutin previously displayed.
- 
-Giving an empty string for the filename and 255 for the position will remove all 
-cutin pictures. Any other position value will not cause a script error but will 
-cause the player's client to curl up and die. Only one cutin may be on screen at 
-any given time, any new cutins will replace it.
-
-    // This will display the picture of the 7th kafra,
-    // the one in orange and the mini-skirt :P
-    cutin "kafra_7",2;
-
-    // This will remove the displayed picture.
-    cutin "Kafra_7",255;
-
-    // This will remove all pictures displayed.
-    cutin "",255;
-
-The client comes with those cutin pictures preinstalled which you can use:
+*getcastlename("<map name>")
 
-mets_alpha  - This is a old fat man, holding a pipe, also with a pocket watch 
-              and cane
-pay_soldier - Wanna take a wild guess, thats right, the Soldiers that appear in 
-              Payon :D
-prt_soldier - Obvious
-ein_soldier - This guy looks cool, you've got to see him ;) This picture is for 
-              the new Einbroch guards
-moc_soldier - Obvious
-gef_soldier - Obvious
-katsua01    - It is not certain who this girl is (There is no sprite coming with 
-katsua02    - the client that seems to match very well) but she is believed to 
-katsua03    - be an NPC in official Comodo. The three pictures give different 
-              facial expressions.
-kafra_01    - Obvious
-kafra_02    - Obvious
-kafra_03    - Obvious
-kafra_04    - Obvious
-kafra_05    - Obvious
-kafra_06    - Obvious
-kafra_07    - Do I need to mention this one again ;)
+This function returns the name of the castle when given the map name for that 
+castle. The data is read from 'db/castle_db.txt'.
 
 ---------------------------------------
 
-*cutincard <item id>;
-
-This command will display a card picture as a cutin on the client connected to 
-the invoking character, with position number 4 (middle of screen, movable, but 
-no title bar). See 'cutin'. To remove this cutin, use the regular 'cutin' 
-command. Unlike the 'cutin' command, it will not take a filename, but will 
-instead take an item ID. It will then refer to the text file listing card images 
-which is normally found within your server's copy of the GRF file to find the 
-real (korean) filename.
+*getcastledata("<map name>",<type of data>)
+*setcastledata "<map name>",<type of data>,<value>;
 
-If your server doesn't have that text file in that GRF or can't read it, it 
-probably won't work.
+This function returns the castle ownership information for the castle referred 
+to by it's map name. Castle information stored in 'save\castle.txt' for the TXT 
+version of the server and in 'guild_castle' table for the SQL version.
 
----------------------------------------
+Valid types of data are:
 
-*statusup <stat>;
+ 0 - Will make the map server request the castle data from the char server, and 
+     always return 0. This, apparently, will also cause indirectly the execution 
+     of an 'OnAgitInit:' event mentioned at the beginning of this document.
+ 1 - Guild ID
+ 2 - Castle Economy score.
+ 3 - Castle Defence score.
+ 4 - Number of times the economy was invested in today.
+ 5 - Number of times the defence was invested in today.
+ 9 - Will return 1 if a Kafra was hired for this castle, 0 otherwise.
+10 - Is 1 if the 1st guardian is present (Soldier Guardian)
+11 - Is 1 if the 2nd guardian is present (Soldier Guardian)
+12 - Is 1 if the 3rd guardian is present (Soldier Guardian)
+13 - Is 1 if the 4th guardian is present (Archer Guardian)
+14 - Is 1 if the 5th guardian is present (Archer Guardian)
+15 - Is 1 if the 6th guardian is present (Knight Guardian)
+16 - Is 1 if the 7th guardian is present (Knight Guardian)
+17 - Is 1 if the 8th guardian is present (Knight Guardian)
 
-This command will bump a specified stat of the invoking character up by one 
-permanently. Stats are to be given as number, but you can use these constants to 
-replace them:
+18-25 types of data will return current hit point values for guardians 1-8 
+respectively.
 
-bStr -  Strength
-bVit -  Vitality
-bInt -  Intelligence
-bAgi -  Agility
-bDex -  Dexterity
-bLuk -  Luck
+The 'setcastledata' command will behave identically, but instead of returning 
+values for the specified types of accessible data, it will alter them and cause 
+them to be sent to the char server for storage. Data type of 0 won't do 
+anything, obviously.
 
 ---------------------------------------
 
-*statusup2 <stat>,<amount>;
-
-This command will bump a specified stat of the invoking character up by the 
-specified amount permanently. The amount can be negative. See 'statusup'.
+*getgdskilllv(<guild id>,<skill id>)
 
-    // This will decrease a character's Vit forever.
-    statusup bVit,-1;
+This function returns the level of the skill <skill id> of the guild <guild id>.
+If the guild does not have that skill, 0 is returned.
+If the guild does not exist, -1 is returned.
+Refer to 'db/skill_db.txt' for the full list of skills. (GD_* are guild skills)
 
 ---------------------------------------
 
-*bonus <bonus type>,<val1>;
-*bonus2 <bonus type>,<val1>,<val2>;
-*bonus3 <bonus type>,<val1>,<val2>,<val3>;
-*bonus4 <bonus type>,<val1>,<val2>,<val3>,<val4>;
-
-These commands are meant to be used in item scripts. They will probably work 
-outside item scripts, but the bonus will not persist for long. They, as 
-expected, refer only to an invoking character.
+*requestguildinfo <guild id>,"<event label>";
 
-You can find the full list of possible bonuses and which command to use for each 
-kind in 'doc/item_bonus.txt'.
+This command requests the guild data from the char server and merrily continues 
+with the execution. Whenever the guild information becomes available (which 
+happens instantly if the guild information is already in memory, or later, if it 
+isn't and the map server has to wait for the char server to reply) it will run 
+the specified event as in a 'doevent' call.
 
 ---------------------------------------
 
-*skill <skill id>,<level>{,<flag>};
-*addtoskill <skill id>,<level>{,<flag>}
-
-These commands will give the invoking character a specified skill. This is also 
-used for item scripts.
-
-Level is obvious. Skill id is the ID number of the skill in question as per 
-'db/skill_db.txt'. It is not known for certain whether this can be used to give 
-a character a monster's skill, but you're welcome to try with the numbers given 
-in 'db/mob_skill_db.txt'.
+*getmapguildusers <mapname>,<guild id>;
 
-Flag is 0 if the skill is given permanently (will get written with the character 
-data) or 1 if it is temporary (will be lost eventually, this is meant for card 
-item scripts usage.).  The flag parameter is optional, and defaults to 1 in 
-'skill' and to 2 in 'addtoskill'.
+Returns the amount of persons from the given guild that are on the given map.
+Example(s):
 
-Flag 2 means that the level parameter is to be interpreted as a stackable 
-additional bonus to the skill level. If the character did not have that skill 
-previously, they will now at 0+the level given.
+//Will set the @persons variable to the amount of persons from the guild
+//which ID's = 10 and are at prontera.
 
-// This will permanently give the character Stone Throw (TF_THROWSTONE,152), at 
-// level 1.
-    skill 152,1,0; 
+	set @persons,getMapGuildUsers "prontera.gat",10;
 
 ---------------------------------------
-
-*guildskill <skill id>,<level>
-
-This command will bump up the specified guild skill by the specified number of 
-levels. This refers to the invoking character and will only work if the invoking 
-character is a member of a guild AND it's guildmaster, otherwise no failure 
-message will be given and no error will occur, but nothing will happen - same 
-about the guild skill trying to exceed the possible maximum. The full list of 
-guild skills is available in 'db/skill_db.txt', these are all the GD_ skills at 
-the end.
-
-The flag parameter is currently not functional and it's a mystery of what it 
-would actually do. (Though probably, like for character skills, it would allow 
-temporary bumping.) Using this command will bump the guild skill up permanently.
-
-// This would give your character's guild one level of Approval (GD_APPROVAL ID 
-// 10000). Notice that if you try to add two levels of Approval, or add
-// Approval when the guild already has it, it will only have one level of 
-// Approval afterwards.
-    guildskill 10000,1,0;
-
-You might want to make a quest for getting a certain guild skill, make it hard 
-enough that all the guild needs to help or something. Doing this for the Glory 
-of the Guild skill, which allows your guild to use an emblem, is a good idea for 
-a fun quest. (Wasting a level point on that is really annoying :D)
-
+//
+2,2.- End of guild-related commands
+//
 ---------------------------------------
 
 *getskilllv(<skill id>)
@@ -2684,70 +2690,200 @@ Example 2:
 
 ---------------------------------------
 
-*getgdskilllv(<guild id>,<skill id>)
+*getskilllist;
 
-This function returns the level of the skill <skill id> of the guild <guild id>.
-If the guild does not have that skill, 0 is returned.
-If the guild does not exist, -1 is returned.
-Refer to 'db/skill_db.txt' for the full list of skills. (GD_* are guild skills)
+This command sets a bunch of arrays with a complete list of skills the 
+invoking character has. Here's what you get:
+
+@skilllist_id[]   - skill ids.
+@skilllist_lv[]   - skill levels.
+@skilllist_flag[] - see 'skill' for the meaning of skill flags.
+@skilllist_count  - number of skills in the above arrays.
+
+While 'getskillv' is probably more useful for most situations, this is the 
+easiest way to store all the skills and make the character something else for a 
+while. Advanced job for a day? :) This could also be useful to see how many 
+skills a character has.
 
 ---------------------------------------
 
-*basicskillcheck()
+*getpetinfo(<type>)
 
-This function will return the state of the configuration option 
-'basic_skill_check' in 'battle_athena.conf'. It returns 1 if the option is 
-enabled and 0 if it isn't. If the 'basic_skill_check' option is enabled, which 
-it is by default, characters must have a certain number of basic skill levels to 
-sit, request a trade, use emoticons, etc. Making your script behave differently 
-depending on whether the characters must actually have the skill to do all these 
-things might in some cases be required.
+This function will return pet information for the pet the invoking character 
+currently has active. Valid types are:
+
+ 0 - Unique pet ID number as stored by the char server and distinguishing it 
+     from all other pets the characters actually have. This value is currently 
+     useless, at most you can use it to tell pets apart reliably.
+ 1 - Pet ID number as per 'db/pet_db.txt' - will tell you what kind of a pet it 
+     is.
+ 2 - Pet name. Will return "null" if there's no pet. 
+ 3 - Pet friendly level (intimacy score). 1000 is full loyalty.
+ 4 - Pet hungry level. 100 is completely full.
 
 ---------------------------------------
 
-*getgmlevel()
+*petstat(<flag>)
 
-This function will return the GM level of the account to which the invoking 
-character belongs. If this is somehow executed from a console command, 99 will 
-be returned, and 0 will be returned if the account has no GM level.
+Returns current pet status, all are integers except name.
+Returns 0 or "" if the player doesn't have pets.
 
-This allows you to make NPC's only accessable for certain GM levels, or behave 
-specially when talked to by GMs.
+Flags usable >>
+PET_CLASS
+PET_NAME
+PET_LEVEL
+PET_HUNGRY
+PET_INTIMATE
+
+Example:
+set @i, petstat(PET_CLASS);
 
-   if (getgmlevel()) mes "What is your command, your godhood?";
-   if (getgmlevel()) goto Wherever;
 
 ---------------------------------------
 
-*end;
+*getmonsterinfo(<item ID>,<type>)
 
-This command will stop the execution for this particular script. The two 
-versions are prefectly equivalent. It is the normal way to end a script which 
-does not use 'mes'.
+This function will look up the monster with the specified ID number in the database 
+and return the info set by TYPE argument.
+It will return -1 if there is no such item. Due to specific of MOB DB routines,
+it's better to check monster name. It'd return "Dummy" for a non-existing monster.
 
-        if (BaseLevel<=10) goto L_Lvl10;
-        if (BaseLevel<=20) goto L_Lvl20;
-        if (BaseLevel<=30) goto L_Lvl30;
-        if (BaseLevel<=40) goto L_Lvl40;
-        if (BaseLevel<=50) goto L_Lvl50;
-        if (BaseLevel<=60) goto L_Lvl60;
-        if (BaseLevel<=70) goto L_Lvl70;
-    L_Lvl10:
-        npctalk "Look at that you are still a n00b";
-        end;
-    L_Lvl20:
-        npctalk "Look at that you are getting better, but still a n00b";
-        end;
-    L_Lvl30:
-        npctalk "Look at that you are getting there, you are almost 2nd profession now right???";
-        end;
-    L_Lvl40:
-        npctalk "Look at that you are almost 2nd profession";
-        end;
+Valid types are listed in const.txt:
+	MOB_NAME	0		MOB_LV	1
+	MOB_MAXHP	2		MOB_BASEEXP	3
+	MOB_JOBEXP	4		MOB_ATK1	5
+	MOB_ATK2	6		MOB_DEF	7
+	MOB_MDEF	8		MOB_STR	9
+	MOB_AGI		10		MOB_VIT		11
+	MOB_INT		12		JOB_DEX		13
+	MOB_LUK		14		MOB_RANGE	15
+	MOB_RANGE2	16		MOB_RANGE3	17
+	MOB_SIZE	18		MOB_RACE	19
+	MOB_ELEMENT	20		MOB_MODE	21
 
-Without the use if 'end' it would travel through the labels until the end of the 
-script. If you were lvl 10 or less, you would see all the speech lines, the use 
-of 'end' stops this, and ends the script.
+Check sample in nps\sample\getmonsterinfo.txt
+
+---------------------------------------
+
+*getmapmobs("<map name>")
+
+This function will return the total count of monsters currently located on the 
+specified map. If the map name is given as "this", the map the invoking 
+character is on will be used. If the map is not found, or the invoker is not a 
+character while the map is "this", it will return -1.
+
+---------------------------------------
+
+*getstrlen("<string>")
+
+This function will return the length of the string given as an argument. It is 
+useful to check if anything input by the player exceeds name length limits and 
+other length limits and asking them to try to input something else.
+
+---------------------------------------
+
+*skillpointcount; 
+
+Returns the total amount of skill points a character posesses (SkillPoint+SP's used in skills)
+This command can be used to check the currently attached characters total amount of skillpoints.
+This means the skillpoints used in skill are counted, and added to SkillPoints (number of skill points not used).
+
+Example:
+
+//This will set the temp character variable @skillPoints to the amount of skillpoints,
+//and then tell the player the value.
+	set @skillPoints, skillPointCount();
+	mes "You have "+@skillPoints+" skillpoints in total!";
+	
+//Self-explanatory... :P
+	if (skillPointCount() > 20)
+		mes "Wow, you have more then 20 Skill Points in total!"; 
+
+---------------------------------------
+
+*getscrate(<effect type>,<base rate>{,<target ID number>})
+
+This function will return the chance of a status effect affecting the invoking 
+character, in percent, modified by the their current defense against said 
+status. The 'base rate' is the base chance of the status effect being inflicted, 
+in percent.
+
+    if (rand(100) > getscrate(Eff_Blind, 50)) goto BlindHimNow;
+  
+You can see the full list of available effect types you can possibly inflict in 
+'db/const.txt' under 'Eff_'.
+
+It is pretty certain that addressing the target by an ID number will not 
+currently work due to a bug.
+
+---------------------------------------
+
+========================
+|3.- Checking commands.|
+========================
+-------------------------
+
+*playerattached;
+
+Returns the ID of the player currently attached to the script. It will return
+0 if noone is attached, or if the attached player no longer exists on the map
+server. It is wise to check for the attached player in script functions that
+deal with timers as there's no guarantee the player will still be logged on
+when the timer triggers. Note that the ID of a player is actually their
+account ID.
+
+-------------------------
+
+*isloggedin(<character id>)
+
+This function returns 1 if the specified character is logged in and 0 if they 
+aren't.
+
+---------------------------------------
+
+*checkweight(<item id>,<amount>)
+*checkweight("<item name>",<amount>)
+
+This function will compute and return 1 if the total weight of a specified 
+number of specific items does not exceed the invoking character's carrying 
+capacity, and 0 otherwise. It is important to see if a player can carry the 
+items you expect to give them, failing to do that may open your script up to 
+abuse or create some very unfair errors.
+
+Like 'getitem', this function will also accept an 'english name' from the 
+database as an argument.
+
+    checkweight(502,10) // 10 apples
+
+        if (checkweight(502,10) == 0 ) goto L_OverWeight;
+        getitem 502,10;
+        close;
+    L_OverWeight:
+        mes "Sorry you cannot hold this ammount of apples";
+        close;
+
+Or to put this another way:
+
+        if (checkweight("APPLE",10)) goto L_Getapples;
+        mes "Sorry you cannot hold this ammount of apples";
+        close;
+    L_Getapples:
+        getitem 502,10;
+        close;
+
+Both these examples have the same effect.
+
+---------------------------------------
+
+*basicskillcheck()
+
+This function will return the state of the configuration option 
+'basic_skill_check' in 'battle_athena.conf'. It returns 1 if the option is 
+enabled and 0 if it isn't. If the 'basic_skill_check' option is enabled, which 
+it is by default, characters must have a certain number of basic skill levels to 
+sit, request a trade, use emoticons, etc. Making your script behave differently 
+depending on whether the characters must actually have the skill to do all these 
+things might in some cases be required.
 
 ---------------------------------------
 
@@ -2863,656 +2999,1085 @@ bird and 0 if they don't.
 
 ---------------------------------------
 
-*savepoint "<map name>",<x>,<y>;
-*save "<map name>",<x>,<y>;
+*checkvending ({"<player name>"})
+*checkchatting ({"<Player Name>"})
 
-This command saves where the invoking character will return to upon 
-'return to save point', if dead or in some other cases. The two versions are 
-equivalent. Map name, X coordinate and Y coordinate should be perfectly obvious. 
-This ignores any and all map flags, and can make a character respawn where no 
-teleportation is otherwise possible.
+If the player's name is given, this command checks for that player
+to be online and wether he/she is chatting or vending.
+When no name is given, the attached player is used for checking.
+Returns true or false (1 or 0) when the player is chatting/vending or not.
 
-    savepoint "place.gat",350,75;
+Example(s):
+if (checkVending("Aaron")) mes "Aaron is currently vending!";	
+	//This will check if Aaron is vending, and if so, put a message in front
+	//of the attached player saying Aaron is vending.
 
+if (checkChatting()) mes "You are currently chatting!";
+	//This will check if you're in a chat room or not
+	
 ---------------------------------------
 
-*gettimetick(<tick type>)
-
-This function will return the system time in UNIX epoch time (if tick type is 2) 
-or the time since the start of the current day in seconds if tick type is 1.
-Passing 0 will make it return the server's tick, which is a measurement in
-milliseconds used by the server's timer system. The server's tick is an
-unsigned int which loops every ~50 days.
+*agitcheck()
 
-Just in case you don't know, UNIX epoch time is the number of seconds elapsed 
-since 1st of January 1970, and is useful to see, for example, for how long the 
-character has been online with OnPCLoginEvent and OnPCLogoutEvent, which could allow 
-you to make an 'online time counted for conviction only' jail script.
+This function will let you check whether the server is currently in WoE mode.
+It will return 1 if the War of Emperium is on and 0 if it isn't.
 
 ---------------------------------------
 
-*gettime(<type>)
-
-This function will return specified information about the current system time.
-
-1 - Seconds (of a minute)
-2 - Minutes (of an hour)
-3 - Hour (of a day)
-4 - Week day (0 for Sunday, 6 is Saturday)
-5 - Day of the month.
-6 - Number of the month.
-7 - Year.
-8 - Day of the year.
+*isnight()
+*isday()
 
-It will only return numbers.
+These functions will return 1 or 0 depending on whether the server is in night 
+mode or day mode. 'isnight' returns 1 if it's night and 0 if it isn't, 'isday' 
+the other way around. They can be used interchangeably, pick the one you like 
+more:
 
-    if (gettime(4)==6) mes "It's a Saturday. I don't work on Saturdays.";
+    // These two are equivalent:
+    if (isday()) mes "I only prowl in the night.";
+    if (isnight()!=1) mes "I only prowl in the night.";
 
 ---------------------------------------
+\\
+3,1.- Item-related commands
+\\
+---------------------------------------
+*isequipped(<id>{,<id>{,<id>{,<id>}}})
 
-*gettimestr(<format string>,<max length>)
-
-This function will return a string containing time data as specified by the 
-format string.
-
-This uses the C function 'strfmtime', which obeys special format characters. For 
-a full description see, for example, the description of 'strfmtime' at 
-http://www.delorie.com/gnu/docs/glibc/libc_437.html
-All the format characters given in there should properly work.
-Max length is the maximum length of a time string to generate.
-
-The example given in eAthena sample scripts works like this:
+This function will return 1 if the invoking character has all of the item 
+IDs given equipped (if card IDs are passed, then it checks if the cards are
+inserted into slots in the equipment they are currently wearing). Theorically
+there is no limit to the number of items that may be tested for at the same time. 
+If even one of the items given is not equipped, 0 will be returned.
 
-  mes gettimestr("%Y-%m/%d %H:%M:%S",21);
-  
-This will print a full date and time like 'YYYY-MM/DD HH:MM:SS'.
+    // (Poring,Santa Poring,Poporing,Marin)
+    if (isequipped(4001,4005,4033,4196)) mes "Wow! You're wearing a full complement of possible poring cards!";
+    // (Poring)
+    if (isequipped(4001)) mes "A poring card is useful, don't you think?";
+    
+The function was meant for item scripts to support the cards released by Gravity 
+in February 2005, but it will work just fine in normal NPC scripts.
 
 ---------------------------------------
 
-*openstorage;
-
-This will open a character's Kafra storage window on the client connected to the 
-invoking character. It does not check wherever it is run from, so you can allow 
-any feasible NPC to open a kafra storage. (It's not certain whether this works 
-in item scripts, but if it does, it could be interesting.)
+*isequippedcnt(<card id>{,<card id>{,<card id>{,<card id>}}})
 
-The storage window might not open if a message box or a trade deal is present on 
-screen already, so you should at least make sure the message box is closed 
-before you open storage.
+This function is similar to 'isequipped', but instead of 1 or 0, it will return 
+the number of cards in the list given that were found on the invoking character.
 
-    mes "I will now open your stash for you";
-    close2;
-    openstorage;
-    end;
+    if (isequippedcnt(4001,4005,4033,4196)=4) mes "Finally got all four poring cards?";
 
 ---------------------------------------
 
-*guildopenstorage()
-
-This function works the same as 'openstorage' but will open a guild storage 
-window instead for the guild storage of the guild the invoking character belongs 
-to. This is a function because it returns a value - 0 if the guild storage was 
-opened successfully and 1 if it wasn't. (Notice, it's a ZERO upon success.) 
-Since guild storage is only accessible to one character at one time, it may fail 
-if another character is accessing the guild storage at the same time.
+*checkequipedcard(<card id>)
 
-This will also fail and return 2 if the character does not belong to any guild.
+This function will return 1 if the card specified by it's item ID number is 
+inserted into any equipment they have in their inventory, currently equipped or 
+not.
 
 ---------------------------------------
 
-*itemskill <skill id>,<skill level>,"<skill name to show>";
-
-This is a command meant for item scripts to replicate single-use skills. It will 
-not work properly in NPC scripts a lot of the time because casting a skill is 
-not allowed when there is a message window or menu on screen. If there isn't one 
-cause you've made sure to run this when they already closed it, it should work 
-just fine and even show a targeting pointer if this is a targeting skill.
-
-// When you use Anodyne, you will cast Endure(8) level 1, 
-// and "Endure" will appear above your head as you use it.
-605,Anodyne,Anodyne,11,2000,0,100,,,,,10477567,2,,,,,{ itemskill 8,1,"Endure"; },{}
+*hasitems(0)
 
+This function will return 1 if the invoking character has anything at all in 
+their inventory and 0 if they do not. Even though the argument is not used for 
+anything, it is required.
 
 ---------------------------------------
 
-*produce <item level>;
-
-This command will open a crafting window on the client connected to the invoking 
-character. The 'item level' is a number which determines what kind of a crafting 
-window will pop-up. You can see the full list of such item levels in 
-'db/produce_db.txt' which determines what can actually be produced.
-The window will not be empty only if the invoking character can actually produce 
-the items of that type and has the appropriate raw materials in their inventory.
-
-Valid item levels are:
+*getequipisidentify(<equipment slot>)
 
- 1   - Level 1 Weapons
- 2   - Level 2 Weapons
- 3   - Level 3 Weapons
- 16  - Blacksmith's Stones and Metals
- 32  - Alchemist's Potions
- 64  - Whitesmith's Coins
- 123 - Whitesmith's Nuggets
- 256 - Assassin Cross's Deadly Poison
+This function will return 1 if an item in the specified equipment slot is 
+identified and 0 if it isn't. Since you can't even equip unidentified equipment, 
+there's a question of whether it can actually end up there, and it will normally 
+return 1 all the time if there is an item in this equipment slot.
+Which is kinda pointless.
+For a list of equipment slots see 'getequipid'.
 
+---------------------------------------
+//
+3,1.- End of item-related commands
+//
 ---------------------------------------
 
-*monster "<map name>",<x>,<y>,"<name to show>",<mob id>,<amount>{,"<event label>"};
-*areamonster "<map name>",<x1>,<y1>,<x2>,<y2>,"<monster name>",<amount>{,"<event label>"};
+==============================
+|4.- Player-related commands.|
+==============================
+-------------------------
 
-This command will spawn a monster on the specified coordinates on the specified 
-map. If the script is invoked by a character, a special map name, "this", will 
-be recognised to mean the name of the map the invoking character is located at. 
-This command works fine in the item scripts.
+*attachrid(<character ID>)
+*detachrid;
 
-The same command arguments mean the same things as described above in the 
-beginning of this document when talking about permanent monster spawns. Monsters 
-spawned in this manner will not respawn upon being killed.
+A 'RID' is an ID of a character who caused the NPC script to run, as has been 
+explained above in the introduction section. Quite a bit of commands want a RID 
+to work, since they wouldn't know where to send information otherwise. And in 
+quite a few cases the script gets invoked with a RID of zero (like through 
+OnTime special labels). If an NPC script needs this, it can attach a specified 
+character's id to itself. by calling the 'attachrid' function.
 
-Unlike the permanent monster spawns, if the mob id is -1, a random monster will 
-be picked from the entire database according to the rules configured in the 
-server for dead branches. This will work for all other kinds of non-permanent 
-monster spawns.
+'attachrid' returns 1 if the character was found online and 0 if it wasn't.
 
-The only very special thing about this command is an event label, which is an 
-optional parameter. This label is written like '<NPC object name>::<label name>' 
-and upon the monster being killed, it will execute the script inside of the 
-specified NPC object starting from the label given. The RID of the player 
-attached at this execution will be the RID of the killing character.
+This could also be used, while running in a script invoked by a character 
+through talking to an NPC, to mess with other characters.
+Detaching the RID will make the RID of the script zero.
 
-    monster "place.gat",60,100,"Poring",1002,1,"NPCNAME::OnLabel";
+---------------------------------------
 
-If you do not specify any event label, a label in the NPC object that ran this 
-command, called 'OnMyMobDead:' will execute anyway, if present.
+*rid2name(<rid>)
 
-The coordinates of 0,0 will spawn the monster on a random place on the map.
+Converts rid to name. Note: The player/monster/NPC must be online/enabled.
+Good for PCKillEvent where you can convert 'killedrid' to the name of the player.
 
-The 'areamonster' command works much like the 'monster' command and is not 
-significantly different, but spawns the monsters within a square defined by 
-x1/y1-x2/y2.
+Note: rid2name may not produce correct character names since rid = account id.
+      It will return the current online character of the account only.
 
-Simple monster killing script:
+---------------------------------------
 
-        <Normal NPC object definition. Let's assume you called him NPCNAME.>
-        mes "[Summon Man]";
-        mes "Want to start the kill?";
-        next;
-        menu "Yes",L_Yes,"No",-;
-        mes "[Summon Man]";
-        mes "Come back later";
-        close;
-    L_Yes:
-        monster "prontera.gat",0,0,"Quest Poring",1002,10,"NPCNAME::OnPoringKilled";
-        // By using 0,0 it will spawn them in a random place.
-        mes "[Summon Man]";
-        mes "Now go and kill all the Poring I summoned";
-        // He summoned ten.
-        close;
-    L_PoringKilled:
-        set $PoringKilled,$PoringKilled+1;
-        if ($PoringKilled==10) goto L_AllDead;
-        end;
-    L_AllDead:
-        announce "Summon Man: Well done all the poring are dead",3;
-        set $PoringKilled,0;
-        end;
+*message "<character name>","<message>";
 
-For more good examples see just about any official 2-1 or 2-2 job quest script.
+That command will send a message to the chat window of the character specified 
+by name. The text will also appear above the head of that character. It will not 
+be seen by anyone else.
 
 ---------------------------------------
 
-*killmonster "<map name>","<event label>";
-
-This command will kill all monsters that were spawned with 'monster' or 
-'addmonster' and have a specified event label attached to them. Commonly used to 
-get rid of remaining quest monsters once the quest is complete.
+*dispbottom "<message>";
 
-If the label is given as "All", all monsters which have their respawn times set 
-to -1 (like all the monsters summoned with 'monster' or 'areamonster' script 
-command, and all monsters summoned with GM commands, but no other ones - that 
-is, all non-permanent monsters) on the specified map will be killed regardless 
-of the event label value.
+This command will send the given message into the invoking character's chat 
+window.
 
 ---------------------------------------
 
-*killmonsterall "<map name>";
+*warp "<map name>",<x>,<y>;
 
-This command will kill all monsters on a specified map name, regardless of how 
-they were spawned or what they are.
+This command will take the invoking character to the specifed map, and if 
+wanted, specified coordinates too, but these can be random.
 
----------------------------------------
-*clone "<map name>",<x>,<y>,"<event>",<char id>{,<master_id>{,<mode>{,<flag>,<duration>}}}
+    warp "place.gat",50,55;
 
-This command creates a monster which is a copy of another player. The first
-four arguments serve the same purpose as in the monster script command, The
-<char id> is the character id of the player to clone (player must be online).
-If <master id> is given, the clone will be a 'slave/minion' of it. Master_id
-must be a character id of another online player.
+This would take them to X 50 Y 55 on the map called "place". If your X and Y 
+coordinates land on an unwalkable map square, it will send the warped character 
+to a random place. Same will happen if they are both zero:
 
-The mode can be specified to determine the behaviour of the clone, it's
-values are the same as the ones used for the mode field in the mob_db. The
-default mode is aggressive, assists, can move, can attack.
+    warp "place.gat",0,0;
 
-Flag can be either zero or one currently. If zero, the clone is a normal
-monster that'll target players, if one, it is considered a summoned monster,
-and as such, it'll target other monsters. Defaults to zero.
+Notice that while warping people to coordinates 0,0 will normally get them into 
+a random place, it's not certain to always be so. Darned if I know where this is 
+actually coded, it might be that this happens because square 0,0 is unwalkable 
+on all official maps. If you're using custom maps, beware.
 
-The duration specifies how long the clone will live before it is auto-removed.
-Specified in seconds, defaults to no limit (zero).
+There are also three special 'map names' you can use.
 
-Returned value is the monster ID of the spawned clone. If command fails,
-returned value is zero.
+"Random" will warp the player randomly on the current map.
+"Save" and "SavePoint" will warp the player back to their savepoint.
 
 ---------------------------------------
 
-*doevent "<NPC object name>::<event label>";
-
-This command will start a new execution thread in a specified NPC object at the 
-specified label. The execution of the script running this command will not stop. 
-No parameters may be passed with a doevent call.
-
-The script of the NPC object invoked in this manner will run as if it's been 
-invoked by the RID that was active in the script that issued a 'doevent'.
+*areawarp "<from map name>",<x1>,<y1>,<x2>,<y2>,"<to map name>",<x3>,<y3>;
 
-    place.gat,100,100,1%TAB%script%TAB%NPC%TAB%53,{
-        mes "This is what you will see when you click me";
-        close;
-    Label:
-        mes "This is what you will see if the doevent is activated";
-        close;
-    }
+This command is similar to 'warp', however, it will not refer to the invoking 
+character, but instead, all characters within a specified area, defined by the 
+x1/y1-x2/y2 square, will be warped. Nobody outside the area will be affected, 
+including the activating character, if they are outside the area.
 
-    ....
+    areawarp "place.gat",10,10,120,120,"place2.gat",150,150;
 
-    doevent "NPC::Label";
+Everyone that is in the area between X 10 Y 10 and X 120 Y 120, in a square 
+shape, on the map called "place", will be affected, and warped to "place2" X 150 
+Y 150
 
----------------------------------------
+    areawarp "place.gat",10,10,120,120,"place2.gat",0,0;
 
-*donpcevent "<event label>";
+By using ,0,0; as the destination coordinates it will take all the characters in 
+the affected area to a random set of co-ordinates on "place2".
 
-This command is kinda confusing cause it performs in two completely different 
-ways.
+Like 'warp', areawarp will also explicitly warp characters randomly into the 
+current map if you give the 'to map name' as "Random".
 
-If the event label is phrased like "::<label name>", all NPC objects that have a 
-specified label in them will be invoked as if by a 'doevent', but no RID 
-whatsoever will be attached while they execute.
+See also 'warp'.
 
-Otherwise, if the label is given as "<NPC name>::<label name>", a label within 
-the NPC object that runs this command will be called, but as if it was running 
-inside another, specified NPC object. No RID will be attached to it in this case 
-either.
+---------------------------------------
+ 
+*warpparty "<mapname.gat>",<x>,<y>,<party_id>;
+ 
+Warps a party to specified map and coordinate given the party ID, which you can get with
+getcharid(1). You can also request another party id given a member's name with getcharid(1,<player_name>).
+ 
+Example:
+mes "[Party Warper]";
+mes "Here you go!";
+close2;
+set @id,getcharid(1);
+warpparty "prontera.gat",150,100,@id;
+close;
+ 
+---------------------------------------
+ 
+*warpchar "<mapname.gat>",<x>,<y>,<char_id>;
+ 
+Warps another player to specified map and coordinate given the char id, which you can get with
+getcharid(0,<player_name>). Obviously this is useless if you want to warp the same player that
+is executing this script, unless it's some kind of "chosen" script. 
+ 
+Example:
+ 
+warpchar "prontera.gat",150,100,20000001;
+ 
+---------------------------------------
+ 
+*warpguild "<mapname.gat>",<x>,<y>,<guild_id>;
+ 
+Warps a guild to specified map and coordinate given the guild id, which you can get with 
+getcharid(2). You can also request another guild id given the member's name with getcharid(2,<player_name>).
+ 
+Example:
+ 
+warpguild "prontera.gat",x,y,Guild_ID;
+
+---------------------------------------
+
+*warppartner("<map name>",<x>,<y>);
+
+This function will find the invoking character's marriage partner, if any, and 
+warp them to the map and coordinates given. Go kidnap that spouse. :) It will 
+return 1 upon success and 0 if the partner is not online, the character is not 
+married, or if there's no invoking character (no RID). 0,0 will, as usual, 
+normally translate to random coordinates.
+
+---------------------------------------
+
+*savepoint "<map name>",<x>,<y>;
+*save "<map name>",<x>,<y>;
+
+This command saves where the invoking character will return to upon 
+'return to save point', if dead or in some other cases. The two versions are 
+equivalent. Map name, X coordinate and Y coordinate should be perfectly obvious. 
+This ignores any and all map flags, and can make a character respawn where no 
+teleportation is otherwise possible.
+
+    savepoint "place.gat",350,75;
+
+---------------------------------------
+
+*heal <hp>,<sp>;
+
+This command will heal a set amount of HP and/or SP on the invoking character.
+
+    heal 30000,0; // This will heal 30,000 HP
+    heal 0,30000; // This will heal 30,000 SP
+    heal 300,300; // This will heal 300 HP and 300 SP
+
+This command just alters the hit points and spell points of the invoking 
+character and produces no other output whatsoever.
+
+---------------------------------------
+
+*itemheal <hp>,<sp>;
+
+This command works on the invoking character like 'heal', however, it is not 
+normally used in NPC scripts and will not work as expected there, but is used 
+all over in item scripts. 
+
+Unlike 'heal', which just alters hp/sp and doesn't do anything else at all, this 
+command also shows healing animations for potions and other stuff, checks 
+whether the potion was made by a famous alchemist and alters the amount healed, 
+etc, etc. Since which kind of effect is shown depends on what item was used, 
+using it in an NPC script will not have a desired effect.
+
+There is also a nice example on using this with the 'rand' function, to give you 
+a random ammount of healing.
+
+    // This will heal anything thing from 100 to 150 HP and no SP
+    itemheal rand(100,150),0; 
+
+---------------------------------------
+
+*percentheal <hp>,<sp>;
+
+This command will heal the invoking character. It heals the character, but not 
+by a set value - it adds percent of their maximum HP/SP.
+
+    percentheal 100,0; // This will heal 100% HP
+    percentheal 0,100; // This will heal 100% SP
+    percentheal 50,50; // This will heal 50% HP and 50% SP
+
+So the amount that this will heal will depend on the total ammount of HP or SP 
+you have maximum. Like 'heal', this will not call up any animations or effects.
+
+---------------------------------------
+
+*recovery;
+
+This command will revive and restore full HP and SP to all characters currently 
+connected to the server.
+
+---------------------------------------
+
+*jobchange <job number>{,<upper flag>};
+
+This command will change the job class of the invoking character.
+
+    jobchange 1; // This would change your player into a Swordman
+    jobchange 4002; // This would change your player into a Swordman High
+
+This command does work with numbers, but you can also use job names. The full 
+list of job names and the numbers they correspond to can be found in 
+'db/const.txt'.
+
+    // This would change your player into a Swordman
+    jobchange Job_Swordman; 
+    // This would change your player into a Swordman High
+    jobchange Job_Swordman_High; 
+
+'upper flag' can alternatively be used to specify the type of job one changes
+to. For example, jobchange Job_Swordman,1; will change the character to a high
+swordsman. The upper values are:
+-1 (or when omitted): preserves the current job type.
+0: Normal/standard classes
+1: High/Advanced classes
+2: Baby classes
+
+This command will also set a permanent character-based variable 
+'jobchange_level' which will contain the job level at the time right before 
+changing jobs, which can be checked for later in scripts.
+
+---------------------------------------
+
+*jobname (<job number>)
+
+This command retrieves the name of the given job using the msg_athena entries 550->650.
+
+		mes "[Kid]";
+		mes "I never thought I'd met a "+jobname(Class)+" here of all places.";
+		close;
+
+---------------------------------------
+
+*eaclass ({<job number>})
+
+This commands returns the "eA job-number" corresponding to the given class (if none is given, it returns uses
+the invoking player's class as argument). The eA job-number is also a class number system, but it's one that
+comes with constants which make it easy to convert among classes. The command will return -1 if you pass it a
+job number which doesn't has a eA Job value equivalent.
+
+	set @eac, eaclass();
+	if ((@eac&EAJ_BASEMASK) == EAJ_SWORDMAN)
+		mes "You must be a swordman, knight, crusader, paladin, high swordman, lord knight, baby swordman,";
+		mes "baby knight or baby crusader.";
+	if (@eac&EAJL_UPPER)
+		mes "You are a rebirth job.";
+	if ((@eac&EAJ_UPPERMASK) == EAJ_SWORDMAN)
+		mes "You must be a Swordman, Baby Swordman or High Swordman.";
+
+For more information on the eA Job System, see the docs/ea_job_system.txt file.
+
+---------------------------------------
+*roclass <job number> {,<gender>}
+
+Does the opposite of eaclass. That is, given a eA Job class, it returns which is the corresponding RO class number. 
+A gender is required because both Bard and Dancers share the same eA Job value (EAJ_BARDDANCER), if it isn't given, the
+gender of the executing player is taken (if there's no player running the script, male will be used by default).
+The command returns -1 when there isn't a valid class to represent the required job (for example, if you try to get the
+baby version of a Taekwon class).
+
+	set @eac, eaclass();
+	//Check if class is already rebirth
+	if (@eac&EAJL_UPPER) {
+		mes "You look strong.";
+		close;
+	}
+	set @eac, roclass(@eac|EAJL_UPPER);
+	//Check if class has a rebirth version
+	if (@eac != -1) {
+		mes "Bet you can't wait to become a "+jobname(@eac)+"!";
+		close;
+	}
+
+---------------------------------------
+
+*changebase <job ID number>;
+
+This will change the appearance of the invoking character to that of a specified 
+job class. Nothing but appearance will change. This command is used in item 
+scripts for "Wedding Dress" and "Tuxedo" so the character like job 22, which is 
+the job number of the wedding sprites.
+
+It would be entered in the equip bonus section of an item
+
+2338,Wedding_Dress,Wedding Dress,5,43000,,500,,0,,0,119529470,7,0,16,,0,1,0,{ bonus bMdef,15; changebase 22; }
+
+This command only works when inside item scripts.
+
+---------------------------------------
+
+*classchange <view id>,<type>;
+
+This command is very ancient, it's origins are clouded in mystery. 
+It will send a 'display id change' packet to everyone in the immediate area of 
+the NPC object, which will supposedly make the NPC look like a different sprite, 
+an NPC sprite ID, or a monster ID. This effect is not stored anywhere and will 
+not persist (Which is odd, cause it would be relatively easy to make it do so) 
+and most importantly, will not work at all since this command was broken with 
+the introduction of advanced classes. The code is written with the assumption 
+that the lowest sprite IDs are the job sprites and the anything beyond them is 
+monster and NPC sprites, but since the advanced classes rolled in, they got the 
+ID numbers on the other end of the number pool where monster sprites float.
+
+As a result it is currently impossible to call this command with a valid view 
+id. It will do nothing whatsoever if the view ID is below 4047. Getting it to 
+run will actually just crash the client.
+
+It could be a real gem if it can be gotten to actually do what it's supposed to 
+do, but this will only happen in a later SVN revision.
+
+---------------------------------------
+
+*changesex;
+
+This command will change the gender for the attached character's account. If it 
+was male, it will become female, if it was female, it will become male. The 
+change will be written to the character server, but there is no way to send this 
+information to the client, so the player will continue to see their character as 
+the gender it previously was. What the other players will see before the 
+relogin is not clear.
+
+If the character currently connected when this command was invoked was a 
+Dancer/Gypsy or Bard/Clown, they will become a Swordman upon 'changesex'. 
+Whatever happens to their skills is not clear. Whatever happens if another 
+character on the same account was a gender-specific class is not clear either, 
+but it's likely that the client will have serious issues with that, since no 
+other characters on the same account will get altered.
+
+There's good reasons to be very careful when using this command.
+
+---------------------------------------
+
+*getexp <base xp>,<job xp>;
+
+This command will give the invoking character a specified number of base and job 
+experience points. Can be used as a quest reward. Negative amounts of experience 
+were not tested but should work.
+
+    getexp 10000,5000;
+
+You can also use the "set" command with the constants defined in 'db/const.txt':
+
+    // These 2 combined has the same effect as the above command
+    set BaseExp,BaseExp+10000;
+    set JobExp,JobExp+5000;
+
+You can also reduce the ammount of experience points:
+
+    set BaseExp,BaseExp-10000;
+
+---------------------------------------
+
+*setlook <look type>,<look value>;
+
+This command will alter the look data for the invoking character. It is used 
+mainly for changing the palette used on hair and clothes, you specify which look 
+type you want to change, then the palette you want to use. Make sure you specify 
+a palette number that exists/is usable by the client you use.
+
+    // This will change your hair(6), so that it uses palette 8, what ever your 
+    // palette 8 is your hair will use that colour
+
+    setlook 6,8; 
+
+    // This will change your clothes(7), so they are using palette 1, whatever 
+    // your palette 1 is, your clothes will then use that set of colours.
+    
+    setlook 7,1; 
+
+Here are the possible look types:
+ 
+ 0 - Base sprite
+ 1 - Hairstyle
+ 2 - Weapon
+ 3 - Head bottom
+ 4 - Head top
+ 5 - Head mid
+ 6 - Hair color
+ 7 - Clothes color
+ 8 - Shield
+ 9 - Shoes
+
+Whatever 'shoes' means is anybody's guess, ask Gravity - the client does nothing 
+with this value. It still wants it from the server though, so it is kept, but 
+normally doesn't do a thing.
+ 
+Only the look data for hairstyle, hair color and clothes color are saved to the 
+char server's database and will persist. The rest freely change as the character 
+puts on and removes equipment, changes maps, logs in and out and otherwise you 
+should not expect to set them. In fact, messing with them is generally 
+hazardous, do it at your own risk, it is not tested what will this actually do -
+it won't cause database corruption and probably won't cause a server crash, but 
+it's easy to crash the client with just about anything unusual.
+
+However, it might be an easy way to quickly check for empty view IDs for 
+sprites, which is essential for making custom headgear. 
+
+Since a lot of people have different palettes for hair and clothes, it's 
+impossible to tell you what all the colour numbers are. If you want a serious 
+example, there is a Stylist script inside the default eAthena installation that 
+you can look at, this may help you create a Stylist of your own: 
+'custom\dye.txt'
+
+---------------------------------------
+\\
+4,1.- Item-related commands
+\\
+---------------------------------------
+
+*getitem <item id>,<amount>{,<character ID>};
+*getitem "<item name>",<amount>{,<character ID>};
+
+This command will give a specific amount of specified items to the target 
+character. If the character is not online, nothing will happen.
+If <character ID> is not specified, items will be created in the invoking 
+character inventory instead.
+
+In the first and most commonly used version of this command, items are 
+referred to by their database ID number found inside 'db/item_db.txt'.
+
+    getitem 502,10 // The person will receive 10 apples
+    getitem 617,1  // The person will receive 1 Old Violet Box
+
+Giving an item ID of -1 will give a specified number of random items from the 
+list of those that fall out of Old Blue Box. Unlike in all other cases, these 
+will be unidentified, if they turn out to be equipment. This is exactly what's 
+written in the Old Blue Box's item script.
+
+Other negative IDs also correspond to other random item generating item tables:
+
+Giving an item ID of -2 will produce the effects of Old Violet Box.
+Giving an item ID of -3 will produce the effects of Old Card Album.
+Giving an item ID of -4 will produce the effects of Gift Box.
+Giving an item ID of -5 will produce the effects of Worn Out Scroll, which, in 
+current SVN, drops only Jellopies anyway.
+
+This transaction is logged if the log script generated transactions option is 
+enabled.
+
+You may also create an item by it's name in the 'english name' field in the 
+item database:
 
-This can be used for making another NPC react to an action that you have done 
-with the NPC that has this command in it, i.e. show an emotion, or say 
-something.
+    getitem "RED_POTION",10;
 
-    place.gat,100,100,1%TAB%script%TAB%NPC%TAB%53,{
-        mes "Hey NPC2 copy what I do";
-        close2;
-        set @emo, rand(1,30);
-        donpcevent "NPC2::Emo";
-    Emo:
-        emotion @emo;
-        end;
-    }
+Which will do what you'd expect. If it can't find that name in the database, 
+apples will be created anyway. It is often a VERY GOOD IDEA to use it like this.
 
-    place.gat,102,100,1%TAB%script%TAB%NPC2%TAB%53,{
-        mes "Hey NPC copy what I do";
-        close2;
-        set @emo, rand(1,30);
-        donpcevent "NPC::Emo";
-    Emo:
-        emotion @emo;
-        end;
-    }
+This is used in pretty much all NPC scripts that have to do with items and 
+quite a few item scripts. For more examples check just about any official script.
 
-This will make both NPC perform the same random emotion from 1 to 30, and the 
-emotion will appear above each of their heads.
+---------------------------------------
+
+*getitem2 <item id>,<amount>,<identify>,<refine>,<attribute>,<card1>,<card2>,<card3>,<card4>{,<character ID>};
+*getitem2 "<Item name>",<amount>,<identify>,<refine>,<attribute>,<card1>,<card2>,<card3>,<card4>{,<character ID>};
+
+This command will give an amount of specified items to the invoking character. 
+If an optional character ID is specified, and that character is currently 
+online, items will be created in their inventory instead. If they are not 
+online, nothing will happen. It works essentially the same as 'getitem' (it even 
+works for negative ID numbers the same way, which is kinda silly) but is a lot 
+more flexible, since it allows you to give the player an item altered with it's 
+specific properties. 
+
+Those parameters that are different from 'getitem' are:
+
+identify    - Whether you want the item to be identified or not, 0 unidentified, 
+              1 identified.
+refine      - For how many plusses will it be refined.
+              It will not let you refine an item higher than +10, if you 
+              specify more it'll still be 10.
+attribute   - Whether the item is broken (1) or not (0) and NOT an elemental 
+              attribute. 
+card1,2,3,4 - If you want a card compound to it, place the card ID number into 
+              the specific card slot. Card ID numbers also found in 
+              'db/item_db.txt'
+
+Card1-card4 values are also used to store name information for named items, as 
+well as the elemental property of weapons and armor. You can create a named item 
+in this manner, however, if you just need a named piece of standard equipment, 
+it is much easier to the 'getnameditem' function instead.
+
+You will need to keep these values if you want to destroy and then perfectly 
+recreate a named item, for this see 'getinventorylist'.
+
+If you still want to try creating a named item with this command because 
+'getnameditem' won't do it for you cause it's too limited, you can do it like 
+this. Careful, minor magic ahead.
+
+    // First, let's get an ID of a character who's name will be on the item.
+    // Only an existing character's name may be there.
+    // Let's assume our character is 'Adam' and find his ID.
+    
+    set @charid,getcharid(0,"Adam");
+
+    // Now we split the character ID number into two portions with a binary
+    // shift operation. If you don't understand what this does, just copy it.
+    
+    set @card3, @charid & 65535;
+    set @card4, @charid >> 16;
+
+    // If you're inscribing non-equipment, @card1 must be 254.
+    // Arrows are also not equipment. :)
+    set @card1,254;
+    
+    // For named equipment, card2 means the Star Crumbs and elemental 
+    // crystals used to make this equipment. For everything else, it's 0.
+     
+    set @card2,0;
+    
+    // Now, let's give the character who invoked the script some 
+    // Adam's Apples:
+    
+    getitem2 512,1,1,0,0,@card1,@card2,@card3,@card4;
+
+This wasn't tested with all possible items, so I can't give any promises, 
+experiment first before relying on it.
+
+To create equipment, continue this example it like this:
+
+    // We've already have card3 and card4 loaded with correct
+    // values so we'll just set up card1 and card2 with data
+    // for an Ice Stiletto.
+
+    // If you're inscribing equipment, @card1 must be 255.
+    set @card1,255;
+    
+    // That's the number of star crumbs in a weapon.
+    set @sc,2;
+    
+    // That's the number of elemental property of the weapon.
+    set @ele,1;
+
+    // And that's the wacky formula that makes them into
+    // a single number.    
+    set @card2,@ele+((@sc*5)<<8);
+
+    // That will make us an Adam's +2 VVS Ice Stiletto:
+    
+    getitem2 1216,1,1,2,0,@card1,@card2,@card3,@card4;
+
+Experiment with the number of star crumbs - I'm not certain just how much will 
+work most and what it depends on. The valid element numbers are:
+
+ 1 - Ice, 2 - Earth 3 - Fire 4 - Wind.
+    
+You can, apparently, even create duplicates of the same pet egg with this 
+command, creating a pet which is the same, but simultaneously exists in two 
+eggs, and may hatch from either, although, I'm not sure what kind of a mess will 
+this really cause.
 
 ---------------------------------------
 
-*addtimer <ticks>,"<NPC object name>::<label>";
-*deltimer "<NPC object name>::<event label>";
-*addtimercount <ticks>,"<NPC object name>::<event label>";
+* getnameditem <item name|item id>,<Character name|character ID>;
 
-These commands will create, destroy, and delay a countdown timer - 'addtimer' to 
-create, 'deltimer' to destroy and 'addtimercount' to delay it by the specified 
-number of ticks. For all three cases, the event label given is the identifier of 
-that timer.
+-Note: there's a total of 4 possible combinations of this command.
+E.g: item name and character name, or with character id, etc...
+
+Create a item signed with the given character's name. 
+This is the same as using the hard(ly) explained way with getitem2.
+
+The command returns 1 when the item is created succesfully, or 0 when failed.
+Failure occurs when there is:
+- no player attached
+- Item name or ID is not valid
+- The given character ID/name is offline.
+
+Example:
+
+//This will give the currently attached player a Aaron's Apple (if Aaron is online).
+	getnameditem "Apple","Aaron"; 
+	
+//Self-explanatory (I hope).
+	if (getnameitem("Apple,"Aaron")) {
+		mes "You now have a Aaron's Apple!"; 
+	}
+
+---------------------------------------
+
+*makeitem <item id>,<amount>,<X>,<Y>,"<map name>";
+*makeitem "<item name>",<amount>,<X>,<Y>,"<map name>";
+
+This command will create an item lying around on a specified map in the 
+specified location.
+
+ itemid   - Found in 'db/item_db.txt'
+ amount   - Amount you want produced
+ X        - The X coordinate
+ Y        - The Y coordinate
+ map name - The map name.
+
+This item will still disappear just like any other dropped item. Like 'getitem', 
+it also accepts an 'english name' field from the database and creates apples if 
+the name isn't found.
+
+---------------------------------------
+
+*delitem <item id>,<amount>;
+*delitem "<item name>",<amount>;
+
+This command will take a specified amount of items from the invoking character. 
+As all the item commands, this one uses the ID of the item found inside 
+'db/item_db.txt'. The items are destroyed - there is no way an NPC can simply 
+own items and have an inventory of them, other as by destroying and recreating 
+them when needed.
+
+    delitem 502,10 // The person will lose 10 apples
+    delitem 617,1  // The person will lose 1 Old Violet Box
+
+It is always a good idea to to check if the player actually has the item before 
+you take it from them, Otherwise, you could try to delete items which the 
+players don't actually have, which won't fail and won't give an error message, 
+but might open up ways to exploit your script.
+
+Like 'getitem' this command will also accept an 'english name' field from the 
+database. If the name is not found, nothing will be deleted.
+
+---------------------------------------
+
+*delitem2 <item id>,<amount>,<identify>,<refine>,<attribute>,<card1>,<card2>,<card3>,<card4>{,<character ID>};
+*delitem2 "<Item name>",<amount>,<identify>,<refine>,<attribute>,<card1>,<card2>,<card3>,<card4>{,<character ID>};
+
+This command will take a specified amount of items from the invoking character. 
+Check 'getitem2' to understand its expanded parameters.
+
+---------------------------------------
+
+*countitem(<item id>)
+*countitem("<item name>")
+
+This function will return the number of items for the specified item ID that the 
+invoking character has in the inventory.
+
+    mes "[Item Checker]";
+    mes "Hmmm, it seems you have "+countitem(502)+" apples";
+    close;
+
+Like 'getitem', this function will also accept an 'english name' from the 
+database as an argument.
+
+If you want to state the number at the end of a sentence, you can do it by 
+adding up strings:
+
+    mes "[Item Checker]";
+    mes "Hmmm, the total number of apples you are holding is "+countitem("APPLE");
+    close;
+    
+---------------------------------------
+
+*countitem2(<item id>,<identify>,<refine>,<attribute>,<card1>,<card2>,<card3>,<card4>)
+*countitem2("<item name>",<identify>,<refine>,<attribute>,<card1>,<card2>,<card3>,<card4>)
+
+Expanded version of 'countitem' function, used for created/carded/forged items.
+
+This function will return the number of items for the specified item ID and
+other parameters that the invoking character has in the inventory.
+Check 'getitem2' to understand the arguments of the function.
+    
+---------------------------------------
+
+*groupranditem <group id>;
+
+Returns the item_id of a random item picked from the group specified. The
+different groups and their group number are specified in db/item_group_db.txt
+
+When used in conjunction with other functions, you can get a random item. For
+example, for a random pet lure:
+
+getitem groupranditem(15),1;
+
+---------------------------------------
+
+*enable_items;
+*disable_items;
+
+These commands enable item usage while an npc is running. When enable_items is
+run, items can be used during scripts until disable_items is called. 
+To avoid possible exploits, when enable_items is invoked, it will only enable
+item usage while running that script in particular. Note that if a different
+script also calls enable_items, it will override the last call (so you may
+want to call this command at the start of your script without assuming the
+effect is still in effect).
+
+---------------------------------------
+
+*itemskill <skill id>,<skill level>,"<skill name to show>";
+
+This is a command meant for item scripts to replicate single-use skills. It will 
+not work properly in NPC scripts a lot of the time because casting a skill is 
+not allowed when there is a message window or menu on screen. If there isn't one 
+cause you've made sure to run this when they already closed it, it should work 
+just fine and even show a targeting pointer if this is a targeting skill.
 
-When this timer runs out, a new execution thread will start in the specified NPC 
-object at the specified label. If no such label is found in the NPC object, it 
-will run as if clicked. In either case, no RID will be attached during 
-execution.
+// When you use Anodyne, you will cast Endure(8) level 1, 
+// and "Endure" will appear above your head as you use it.
+605,Anodyne,Anodyne,11,2000,0,100,,,,,10477567,2,,,,,{ itemskill 8,1,"Endure"; },{}
 
-The ticks are given in 1/1000ths of a second.
 
 ---------------------------------------
 
-*stoptimer;
-*inittimer;
-*enablearena;
-*disablearena;
-*cmdothernpc "<npc name?>","<command?>";
+*produce <item level>;
 
-This set of commands is marked as added by someone going under the nickname 
-'RoVeRT', as mentioned the source code comments, and has to do with timers and 
-scheduling working entirely unlike any other timing commands. It is not certain 
-that they actually even work properly anymore, and most of these read no 
-arguments, though the 'inittimer'/'stoptimer' pair of commands has to do 
-something with an 'OnTimer' label and will probably invoke it and 'cmdothernpc' 
-will execute starting with the label 'OnCommand'. Whatever they actually do, the 
-other commands can most likely do it better. The two arena commands definitely 
-do not do anything useful at all.
+This command will open a crafting window on the client connected to the invoking 
+character. The 'item level' is a number which determines what kind of a crafting 
+window will pop-up. You can see the full list of such item levels in 
+'db/produce_db.txt' which determines what can actually be produced.
+The window will not be empty only if the invoking character can actually produce 
+the items of that type and has the appropriate raw materials in their inventory.
 
-None of these commands are used in any scripts bundled with eAthena. Most 
-probably they are deprecated and left in by mistake.
+Valid item levels are:
 
-Unless RoVeRT can be found and asked to clarify what these were made for, that 
-is.
+ 1   - Level 1 Weapons
+ 2   - Level 2 Weapons
+ 3   - Level 3 Weapons
+ 16  - Blacksmith's Stones and Metals
+ 32  - Alchemist's Potions
+ 64  - Whitesmith's Coins
+ 123 - Whitesmith's Nuggets
+ 256 - Assassin Cross's Deadly Poison
 
 ---------------------------------------
 
-*initnpctimer{ "<NPC object name>"};
-*stopnpctimer{ "<NPC object name>"};
-*startnpctimer{ "<NPC object name>"};
-*setnpctimer <tick>{,"<NPC object name>"};
-*getnpctimer(<type of information>{,"<NPC object name>"});
-*attachnpctimer {"<character name>"};
-*detachnpctimer {"<NPC object name>"};
+*successremovecards <equipment slot>;
 
-This set of commands and functions will create and manage an NPC-object based 
-timer. The NPC object may be declared by name, or the name in all cases may be 
-omitted, in that case this timer will be based in the object the current script 
-is running in.
+This command will remove all cards from the item found in the specified 
+equipment slot of the invoking character, create new card items and give them to 
+the character. If any cards were removed in this manner, it will also show a 
+success effect.
 
-Why is it actually part of an NPCs structure we aren't sure, but it is, and 
-while 'addtimer'/'deltimer' commands will let you have many different timers 
-referencing different labels in the same NPC, one each and each with their own 
-countdown, 'initnpctimer' can only have one per NPC object. But it can trigger 
-many labels and it can let you know how many were triggered already and how many 
-still remain.
+---------------------------------------
 
-This timer is counting up from 0 in ticks of 1/1000ths of a second each. Upon 
-creating this timer, the execution will not stop, but will happily continue 
-onward. The timer will then invoke new execution threads at labels 
-"OnTimer<time>:" in the NPC object it is attached to. 
+*failedremovecards <equipment slot>,<type>;
 
-To create the timer, use the 'initnpctimer', which will start it running. 
-'stopnpctimer' will pause the timer, without clearing the current tick, while 
-'startnpctimer' will let the paused timer continue.
+This command will remove all cards from the item found in the specified 
+equipment slot of the invoking character. 'type' determines what happens to the 
+item and the cards:
 
-It is not quite clear whether the new invocations will always have a RID. 
-Apparently, the RID that was in effect when the timer was initialised will still 
-be attached to these executions in some cases, but it's not quite clear -
-experiment with RID-dependent commands, like 'mes', and tell us what happens and 
-who gets the message, if anyone.
+ 0 - will destroy both the item and the cards.
+ 1 - will keep the item, but destroy the cards.
+ 2 - will keep the cards, but destroy the item.
+  
+Whatever the type is, it will also show a failure effect on screen.
 
-Even if they don't have a RID by default, 'attachnpctimer' will allow you to 
-explicitly attach a character's RID to the timer, which will make them the 
-target for all character-referencing commands and functions, not to mention 
-variables. 'detachnpctimer' will make the RID zero, making all character-
-referencing functions fail with an error.
+---------------------------------------
 
-'setnpctimer' will explicitly set the timer to a given tick. To make it useful, 
-you will need the 'getnpctimer' function, which the type of information argument 
-means:
+*repair <broken item number>;
 
- 0 - Will return the current tick count of the timer.
- 1 - Will return 1 if there are remaining "OnTimer<ticks>:" labels in the 
-     specified NPC waiting for execution.
- 2 - Will return the number of times the timer has triggered an "OnTimer<tick>:" 
-     label in the specified NPC.
+This command repairs a broken peice of equipment, using the same list of broken 
+items as available through 'getbrokenid'.
 
-Example 1:
+The official scripts seem to use the repair command as a function instead: 
+'repair(<number>)' but it returns nothing on the stack. Probably only Valaris, 
+who made it, can answer why is it so.
 
-    <NPC Header> {
-        initnpctimer;
-        npctalk "I cant talk right now, give me 10 seconds";
-        end;
-    OnTimer5000:
-        npctalk "Ok 5 seconds more";
-        end;
-    OnTimer6000:
-        npctalk "4";
-        end;
-    OnTimer7000:
-        npctalk "3";
-        end;
-    OnTimer8000:
-        npctalk "2";
-        end;
-    OnTimer9000:
-        npctalk "1";
-        end;
-    OnTimer10000:
-        stopnpctimer;
-        mes "[Man]";
-        mes "Ok we can talk now";
-    }
+---------------------------------------
 
-Example 2:
+*successrefitem <equipment slot>;
 
-    OnTimer15000:
-        set $quote,rand(5);
-        if($quote == 0) goto Lquote0;
-        if($quote == 1) goto Lquote1;
-        if($quote == 2) goto Lquote2;
-        if($quote == 3) goto Lquote3;
-        if($quote == 4) goto Lquote4;
-    Lquote0:
-        npctalk "If 0 is randomly picked you will see this";
-        setnpctimer 0;
-        end;
-    Lquote1:
-        npctalk "If 1 is randomly picked you will see this";
-        setnpctimer 0;
-        end;
-    Lquote2:
-        npctalk "If 2 is randomly picked you will see this";
-        setnpctimer 0;
-        end;
-    Lquote3:
-        npctalk "If 3 is randomly picked you will see this";
-        setnpctimer 0;
-        end;
-    Lquote4:
-        npctalk "If 4 is randomly picked you will see this";
-        setnpctimer 0;
-        end;
-       
-    // This OnInit label will run when the script is loaded, so that the timer 
-    // is initialised immediately as the server starts. It is dropped back to 0 
-    // every time the NPC says something, so it will cycle continiously.
-    OnInit:
-        initnpctimer;
-        end;
+This command will refine an item in the specified equipment slot of the invoking 
+character by +1. For a list of equipment slots see 'getequipid'. This command 
+will not only add the +1, but also display a 'refine success' effect on the 
+character and put appropriate messages into their chat window. It will also give 
+the character fame points if a weapon reached +10 this way, even though these 
+will only take effect for blacksmith who will later forge a weapon.
 
-Example 3:
+The official scripts seem to use the 'successrefitem' command as a function 
+instead: 'successrefitem(<number>)' but it returns nothing on the stack. 
+This is since jAthena, so probably nobody knows for sure why is it so.
 
-    mes "[Man]";
-    mes "I have been waiting "+(getnpctimer(0)/1000)+" seconds for you";
-    // we divide the timer returned by 1000 cause it will be displayed in 
-    // milliseconds otherwise
-    close;
+---------------------------------------
+
+*failedrefitem <equipment slot>;
+
+This command will fail to refine an item in the specified equipment slot of the 
+invoking character. The item will be destroyed. This will also display a 'refine 
+failure' effect on the character and put appropriate messages into their chat 
+window.
+
+The official scripts seem to use the 'failedrefitem' command as a function 
+instead: 'failedrefitem(<number>)' but it returns nothing on the stack. This is 
+since jAthena, so probably nobody knows for sure why is it so.
 
-Example 4:
 
-    mes "[Man]";
-    mes "Ok I will let you have 30 sec more";
-    close2;
-    setnpctimer (getnpctimer(0)-30000); 
-    // Notice the 'close2'. If there were a 'next' there the timer would be 
-    // changed only after the player pressed the 'next' button.
-    end;
- 
 ---------------------------------------
- 
-*sleep {<milliseconds>};
-*sleep2 {<milliseconds>};
-*awake "<NPC name>";
 
-Sleep Timers:
-'sleep' and 'sleep2' pauses the execution of the script.
-'sleep' detaches the player from the script and 'sleep2' doesn't.
-'awake' forces all sleep queues on an NPC to execute.
+*unequip <equipment slot>;
+
+This command will unequip whatever is currently equipped in the invoking 
+character's specified equipment slot. For a full list of possible equipment 
+slots see 'getequipid'.
 
-    sleep 10000; // Sleep for 10 seconds, without player attached.
-    sleep2 5000; // Sleep for 5 seconds, with player attached.
-    awake "npc_name"; // Awakes the NPC.
+If an item occupies several equipment slots, it will get unequipped from all of 
+them. (Which is a good thing.)
 
 ---------------------------------------
 
-*announce "<text>",<flag>{,<color>}
+*clearitem;
 
-This command will broadcast a message to all or most players, similar to 
-@kami/@kamib GM commands.
+This command will destroy all items the invoking character has in their 
+inventory. (that includes equipped items) It will not affect anything else, like 
+storage or cart.
 
-The region the broadcast is heard in and the color the message will come up as 
-will be determined by the flags:
+---------------------------------------
 
-    announce "This will be shown to everyone at all in yellow.",0;
+*equip <item id>;
+*autoEquip <item id>,<option>;
 
-The flag values are coded as constants in db/const.txt to make them easier to use:
-- bc_all: Broadcast message is sent server-wide
-- bc_map: Message is sent to everyone in the same map
-- bc_area: Message is sent to players in the vecinity of the source.
-- bc_self: Message is sent only to current player.
+These commands are to equip a equipment on the attached character. 
+The equip function will equip the item ID given when the player has
+this item in his/her inventory, while the autoequip function will 
+equip the given item ID when this is looted. The option parameter of
+the autoequip is 1 or 0, 1 to turn it on, and 0 to turn it off.
 
-- bc_npc: Broadcast source is the npc, not the player attached to the script
-  (useful when a player is not attached or the message should be sent to those
-  nearby the npc)
+Example(s):
 
-- bc_yellow: The default is to send broadcasts in yellow color.
-- bc_blue: Alternate broadcast is displayed in blue color.
+//This will equip a 1104 (falchion) on the character if this is in the inventory.
+	equip 1104;
+	
+//The invoked character will now automatically equip a falchion when it's looted.
+	autoequip 1104,1;
+	
+//The invoked character will no longer automatically equip a falchion.
+	autoequip 1104,0;
 
-The optional parameter, color, allows usage of broadcasts in any custom color.
-The color parameter is a single number which can be in hexadecimal notation.
-For example:
-    announce "This will be shown to everyone at all in yellow.",bc_all,0xFFFF00;
-Will display a global announce in yellow. The color format is in RGB (0xRRGGBB).
+---------------------------------------
+//
+4,1.- End of item-related commands
+//
+---------------------------------------
 
-Using this for private messages to players is probably not that good an idea,
-but it can be used instead in NPCs to "preview" an announce.
+*openstorage;
 
-    // This will be a private message to the player using the NPC that made the 
-    // annonucement
-    announce "This is my message just for you",bc_blue|bc_self;
+This will open a character's Kafra storage window on the client connected to the 
+invoking character. It does not check wherever it is run from, so you can allow 
+any feasible NPC to open a kafra storage. (It's not certain whether this works 
+in item scripts, but if it does, it could be interesting.)
 
-    // This will be shown on everyones screen that is in sight of the NPC.
-    announce "This is my message just for you people here",bc_area;
+The storage window might not open if a message box or a trade deal is present on 
+screen already, so you should at least make sure the message box is closed 
+before you open storage.
 
+    mes "I will now open your stash for you";
+    close2;
+    openstorage;
+    end;
+---------------------------------------
+\\
+4,2.- Guild-related commands
+\\
 ---------------------------------------
 
-*mapannounce "<map name>","<text>",<flag>[,<color>];
+*guildopenstorage()
 
-This command will work like 'announce' but will only broadcast to characters 
-currently residing on the specified map. The flag and optional color
-parameters are the same as in 'announce', even though the only ones that make
-sense are the color related ones.
+This function works the same as 'openstorage' but will open a guild storage 
+window instead for the guild storage of the guild the invoking character belongs 
+to. This is a function because it returns a value - 0 if the guild storage was 
+opened successfully and 1 if it wasn't. (Notice, it's a ZERO upon success.) 
+Since guild storage is only accessible to one character at one time, it may fail 
+if another character is accessing the guild storage at the same time.
+
+This will also fail and return 2 if the character does not belong to any guild.
 
 ---------------------------------------
 
-*areaannounce "<map name>",<x1>,<y1>,<x2>,<y2>,"<text>",<flag>[,<color>];
+*guildchangegm(<guild id>,<new master's name>)
 
-This command works like 'announce' but will only broadcast to characters 
-residing in the specified x1/y1-x2/y2 square on the map given. The flags and
-color parameter given are the same as in 'announce', but only the color
-related ones have effect.
+This function will change the Guild Master of a guild. The ID is the guild's
+id, and the new guildmaster's name must be passed.
 
-    areaannounce "prt_church.gat",0,0,350,350,"God's in his heaven, all right with the world",0;
+Returns 1 on success, 0 otherwise.
 
 ---------------------------------------
 
-*getusers(<type>)
-
-This function will return a number of users on a map or the whole server. What 
-it returns is specified by Type.
-
-Type is a bitmask, add up to get the effects you want:
+*guildgetexp <amount>;
 
-  8 - This will count all characters on the same map as the current NPC.
-      (By default, it will count people on the same map as the character)
-  7 - Return the amount of players for the entire server.
-      (By default, only the players on the map will be counted.)
-      
-So 'getusers(0)' will return the number of characters on the same map as the 
-invoking character, while 'getusers(7)' will give the count for entire server.
+This will give the specified amount of guild experience points to the guild the 
+invoking character belongs to. It will silently fail if they do not belong to 
+any guild.
 
 ---------------------------------------
 
-*getmapusers("<map name>")
+*guildskill <skill id>,<level>
 
-This function will return the number of users currently located on the specified 
-map.
+This command will bump up the specified guild skill by the specified number of 
+levels. This refers to the invoking character and will only work if the invoking 
+character is a member of a guild AND it's guildmaster, otherwise no failure 
+message will be given and no error will occur, but nothing will happen - same 
+about the guild skill trying to exceed the possible maximum. The full list of 
+guild skills is available in 'db/skill_db.txt', these are all the GD_ skills at 
+the end.
 
-Currently being used in the PVP scripts to check if a PVP room is full of not, 
-if the number returned it equal to the maximum allowed it will not let you 
-enter.
+The flag parameter is currently not functional and it's a mystery of what it 
+would actually do. (Though probably, like for character skills, it would allow 
+temporary bumping.) Using this command will bump the guild skill up permanently.
 
----------------------------------------
+// This would give your character's guild one level of Approval (GD_APPROVAL ID 
+// 10000). Notice that if you try to add two levels of Approval, or add
+// Approval when the guild already has it, it will only have one level of 
+// Approval afterwards.
+    guildskill 10000,1,0;
 
-*getareausers("<map name>",<x1>,<y1>,<x2>,<y2>)
+You might want to make a quest for getting a certain guild skill, make it hard 
+enough that all the guild needs to help or something. Doing this for the Glory 
+of the Guild skill, which allows your guild to use an emblem, is a good idea for 
+a fun quest. (Wasting a level point on that is really annoying :D)
 
-This function will return the count of connected characters which are located 
-within the specified area - an x1/y1-x2/y2 square on the specified map.
+---------------------------------------
+//
+4,2 End of guild-related commands.
+//
+---------------------------------------
 
-This is useful for maps that are split into many buildings, such as all the 
-"*_in.gat" maps, due to all the shops and houses.
+*resetlvl <action type>;
 
----------------------------------------
+This is a character reset command, meant mostly for rebirth script supporting 
+Advanced jobs, which will reset the invoking character's stats and level 
+depending on the action type given. Valid action types are:
 
-*getareadropitem("<map name>",<x1>,<y1>,<x2>,<y2>,<item>)
+ 1 - Base level 1, Job level 1, 0 skill points, 0 base xp, 0 job xp, wipes the 
+     status effects, sets all stats to 1. If the new job is 'Novice High', give 
+     100 status points, give First Aid and Play Dead skills.
+ 2 - Base level 1, Job level 1, 0 skill points, 0 XP/JXP. Skills and attribute 
+     values are not altered.
+ 3 - Base level 1, base xp 0. Nothing else is changed.
+ 4 - Job level 1, job xp 0. Nothing else is changed.
 
-This function will count all the items with the specified ID number lying on the 
-ground on the specified map within the x1/y1-x2/y2 square on it and return that 
-number.
+In all cases it will also unequip everything the character has on.
 
-This is the only function around where a parameter may be either a string or a 
-number! If it's a number, it means that only the items with that item ID number 
-will be counted. If it is a string, it is assumed to mean the 'english name' 
-field from the item database. If you give it an empty string, or something that 
-isn't found from the item database, it will count items number '512' (apples).
+Even though it doesn't return a value, it is used as a function in the official 
+rebirth scripts. Ask AppleGirl why.
 
 ---------------------------------------
 
-*disablenpc "<NPC object name>";
-*enablenpc "<NPC object name>";
+*resetstatus;
 
-These two commands will disable and enable, respectively, an NPC object 
-specified by name. The disabled NPC will disappear from sight and will no longer 
-be triggerable in the normal way. It is not clear whether it will still be 
-accessible through 'donpcevent' and other triggering commands, but it probably 
-will be. You can disable even warp NPCs if you know their object names, which is 
-an easy way to make a map only accessible through walking half the time. Then 
-you 'enablenpc' them back.
+This is a character reset command, which will reset the stats on the invoking 
+character and give back all the stat points used to raise them previously. 
+Nothing will happen to any other numbers about the character.
 
-You can also use these commands to create the illusion of an NPC switching 
-between several locations, which is often better than actually moving the NPC -
-create one NPC object with a visible and a hidden part to their name, make a few 
-copies, and then disable all except one.
+Used in reset NPC's (duh!)
 
 ---------------------------------------
 
-*hideonnpc "<NPC object name>";
-*hideoffnpc "<NPC object name>";
+*resetskill;
 
-These commands will make the NPC object specified display as hidden/visible, 
-even though not actually disabled per se. Hidden as in thief Hide skill, but 
-unfortunately, not detectable by Ruwach or Sight.
+This command takes off all the skill points on the invoking character, so they 
+only have Basic Skill blanked out (lvl 0) left, and returns the points for them 
+to spend again. Nothing else will change but the skills. Quest skills will also 
+reset if 'quest_skill_reset' option is set to Yes in 'battle_athena.conf'. If 
+the 'quest_skill_learn' option is set in there, the points in the quest skills 
+will also count towards the total.
 
-As they are now, these commands are pointless, it is suggested to use 
-'disablenpc'/'enablenpc', because these two commands actually unload the NPC 
-sprite location and other accompanying data from memory when it is not used.
-However, you can use these for some quest ideas (such as cloaking npcs talking 
-while hidden then revealing.... you can wonder around =P
+Used in reset NPC's (duh!)
 
 ---------------------------------------
 
-*sc_start <effect type>,<ticks>,<extra argument>{,<target ID number>};
-*sc_start2 <effect type>,<ticks>,<extra argument>,<percent chance>{,<target ID number>};
-*sc_start4 <effect type>,<ticks>,<value 1>,<value 2>,<value 3>,<value 4>{,<target ID number>};
-*sc_end <effect type>{,<target ID number>};
+*sc_start 	<effect type>,<ticks>,<extra argument>{,<target ID number>};
+*sc_start2 	<effect type>,<ticks>,<extra argument>,<percent chance>{,<target ID number>};
+*sc_start4	<effect type>,<ticks>,<value 1>,<value 2>,<value 3>,<value 4>{,<target ID number>};
+*sc_end 	<effect type>{,<target ID number>};
 
 These command bestow a status effect on the invoking character. This command is 
 used a lot in the item scripts.
@@ -3558,1072 +4123,1283 @@ should be rather obvious.
 
 ---------------------------------------
 
-*getscrate(<effect type>,<base rate>{,<target ID number>})
-
-This function will return the chance of a status effect affecting the invoking 
-character, in percent, modified by the their current defense against said 
-status. The 'base rate' is the base chance of the status effect being inflicted, 
-in percent.
+*skilleffect <skill id>,<number>;
 
-    if (rand(100) > getscrate(Eff_Blind, 50)) goto BlindHimNow;
-  
-You can see the full list of available effect types you can possibly inflict in 
-'db/const.txt' under 'Eff_'.
+This command will display the visual and sound effects of a specified skill (see 
+'db/skill_db.txt' for a full list of skills) on the invoking character's sprite. 
+Nothing but the special effects and animation will happen. If the skill's normal 
+effect displays a floating number, the number given will float up.
 
-It is pretty certain that addressing the target by an ID number will not 
-currently work due to a bug.
+    // This will heal the character with 2000 hp, buff with 
+    // Bless 10 and Increase AGI 5, and display appropriate
+    // effects.
+    mes "Blessed be!";
+    skilleffect 28,2000;
+    heal 2000,0;
+    skilleffect 34,0;
+    // That's bless 10.
+    sc_start 10,240000,10;
+    skilleffect 29,0;
+    // That's agi 5
+    sc_start 12,140000,5;
 
 ---------------------------------------
 
-*callshop "<shop name>",<flag>;
+*npcskilleffect <skill id>,<number>,<x>,<y>;
+
+This command behaves identically to 'skilleffect', however, the effect will not 
+be centered on the invoking character's sprite, nor on the NPC sprite, if any, 
+but will be centered at map coordinates given on the same map as the invoking 
+character.
 
-This command forces an npc shop to be invoked as if the player clicked on it.
-With normal shops it will not work unless the player is within clicking range,
-but the real use of this script command is together with "invisible shops",
-which are specified in the same way an invisible npc would be specified.
-For example, a generic invisible tool shop could be:
+---------------------------------------
 
--	shop	INVISIBLE_SHOP	-,611:-1,1750:-1,501:-1,502:-1,503:-1,504:-1,506:-1
+*specialeffect <effect number>;
 
-Which players cannot click on, but can be invoked using:
+This command will display special effect with the given number, centered on the 
+specified NPCs coordinates, if any. For a full list of special effect numbers 
+known see 'doc/effect_list.txt'. Some effect numbers are known not to work in 
+some client releases. (Notably, rain is absent from any client executables 
+released after April 2005.)
 
-callshop "INVISIBLE_SHOP", 0;
+---------------------------------------
 
-The flag values are: 1 invokes the buying window, 2 invokes the selling
-window, any other value invokes the buy/sell dialogue.
+*specialeffect2 <effect number>;
 
-The function returns 1 on success, and the script is not automatically
-closed, so be careful to not do any item trading on the same script to prevent
-possible exploits (if possible, use close or close2 before invoking the shop
-itself).
+This command behaves identically to the 'specialeffect', but the effect will be 
+centered on the invoking character's sprite.
 
 ---------------------------------------
 
-*npcshopitem "<name>",<itemId>,<Price>{,<itemId>,<Price>{,<itemId>,<Price>{,...}}}
-
-This command lets you override the contents of an existing npc shop. The
-current sell list will be wiped, and only the items specified with the price
-specified will be for sale.
+*statusup <stat>;
 
-The function returns 1 if shop was updated successfully, or 0 if not found.
+This command will bump a specified stat of the invoking character up by one 
+permanently. Stats are to be given as number, but you can use these constants to 
+replace them:
 
-Note that you cannot use -1 to specify default selling price!
+bStr -  Strength
+bVit -  Vitality
+bInt -  Intelligence
+bAgi -  Agility
+bDex -  Dexterity
+bLuk -  Luck
 
 ---------------------------------------
 
-*npcshopadditem "<name>",<itemId>,<Price>{,<itemId>,<Price>{,<itemId>,<Price>{,...}}}
-
-This command will add more items at the end of the selling list for the
-specified npc shop. If you specify an item already for sell, that item will
-appear twice on the sell list.
+*statusup2 <stat>,<amount>;
 
-The function returns 1 if shop was updated successfully, or 0 if not found.
+This command will bump a specified stat of the invoking character up by the 
+specified amount permanently. The amount can be negative. See 'statusup'.
 
-Note that you cannot use -1 to specify default selling price!
+    // This will decrease a character's Vit forever.
+    statusup bVit,-1;
 
 ---------------------------------------
 
-*npcshopdelitem "<name>",<itemId>{,<itemId>{,<itemId>{,...}}}
+*bonus <bonus type>,<val1>;
+*bonus2 <bonus type>,<val1>,<val2>;
+*bonus3 <bonus type>,<val1>,<val2>,<val3>;
+*bonus4 <bonus type>,<val1>,<val2>,<val3>,<val4>;
 
-This command will remove items from the specified npc shop.
-If the item to remove exists more than once on the shop, all instances will be
-removed.
+These commands are meant to be used in item scripts. They will probably work 
+outside item scripts, but the bonus will not persist for long. They, as 
+expected, refer only to an invoking character.
 
-Note that the function returns 1 even if no items were removed. The return
-value is only to confirm that the shop was indeed found.
+You can find the full list of possible bonuses and which command to use for each 
+kind in 'doc/item_bonus.txt'.
 
 ---------------------------------------
 
-*npcshopattach "<name>"{,<flag>}
+*skill <skill id>,<level>{,<flag>};
+*addtoskill <skill id>,<level>{,<flag>}
 
-This command will attach the current script to the given npc shop.
-When a script is attached to a shop, the events "OnBuyItem" and "OnSellItem"
-of your script will be executed whenever a player buys/sells from the shop.
-Additionally, the arrays @bought_nameid[], @bought_quantity[] or @sold_nameid[]
-and @sold_quantity[] will be filled up with the items and quantities
-bought/sold.
+These commands will give the invoking character a specified skill. This is also 
+used for item scripts.
 
-The optional parameter specifies whether to attach ("1") or detach ("0") from
-the shop (the default is to attach). Note that detaching will detach any npc
-attached to the shop, even if it's from another script, while attaching will
-override any other script that may be already attached.
+Level is obvious. Skill id is the ID number of the skill in question as per 
+'db/skill_db.txt'. It is not known for certain whether this can be used to give 
+a character a monster's skill, but you're welcome to try with the numbers given 
+in 'db/mob_skill_db.txt'.
+
+Flag is 0 if the skill is given permanently (will get written with the character 
+data) or 1 if it is temporary (will be lost eventually, this is meant for card 
+item scripts usage.).  The flag parameter is optional, and defaults to 1 in 
+'skill' and to 2 in 'addtoskill'.
+
+Flag 2 means that the level parameter is to be interpreted as a stackable 
+additional bonus to the skill level. If the character did not have that skill 
+previously, they will now at 0+the level given.
 
-The function returns 0 if the shop was not found, 1 otherwise.
+// This will permanently give the character Stone Throw (TF_THROWSTONE,152), at 
+// level 1.
+    skill 152,1,0; 
 
 ---------------------------------------
 
-*debugmes "<message>";
+*nude; 
 
-This command will send the message to the server console (map-server window). It 
-will not be displayed anywhere else.
+This command will unequip anything equipped on the invoking character.
 
-    debugmes strcharinfo(0)+" has just done this that and the other";
-    // You would see in the map-server window "NAME has just done this that and 
-    // the other"
+It is not required to do this when changing jobs since 'jobchange' will unequip 
+everything not equippable by the new job class anyway.
 
 ---------------------------------------
 
-*pet <pet id>;
+*disguise <Monster ID>;
+*undisguise;
 
-This command is used in all the item scripts for taming items. Running this 
-command will make the pet catching cursor appear on the client connected to the 
-invoking character, usable on the monsters with the specified pet ID number. It 
-will still work outside an item script.
+This command disgueses current player with a monster sprite.
+The disguise is disappearing on re-login or on 'undisguise' command.
 
-A full list of pet IDs can be found inside 'db/pet_db.txt'
+Note: It doesn't work with "Pets with equipment on"
+Note: If u're a Sniper, u'd get an old Falcon over your head
+Note: You can kill yourself with some skills
+Note: Monsters of your type could heal you
+
+Example:
+
+disquise 1002; //Yay! You're a Poring!!!
+next;
+undisquise; //Yay!!!! You're a human again!!
 
 ---------------------------------------
+\\
+4,3 Marriage-related commands
+\\
+---------------------------------------
+*marriage("<spouse name>");
 
-*bpet;
+This function will marry two characters, the invoking character and the one 
+referred to by name given, together, setting them up as each other's marriage 
+partner. No second function call has to be issued (in current SVN at least) to 
+make sure the marriage works both ways. The function returns 1 upon success, or 
+0 if the marriage could not be completed, either because the other character 
+wasn't found or because one of the two characters is already married.
 
-This command opens up a pet hatching window on the client connected to the 
-invoking character. It is used in item script for the pet incubators and will 
-let the player hatch an owned egg. If the character has no eggs, it will just 
-open up an empty incubator window.
-This is still usable outside item scripts.
+This will do nothing else for the marriage except setting up the spouse ID for 
+both of these characters. No rings will be given and no effects will be shown.
 
 ---------------------------------------
 
-*resetlvl <action type>;
+*wedding;
 
-This is a character reset command, meant mostly for rebirth script supporting 
-Advanced jobs, which will reset the invoking character's stats and level 
-depending on the action type given. Valid action types are:
+This command will call up wedding effects - the music and confetti - centered on 
+the invoking character.
 
- 1 - Base level 1, Job level 1, 0 skill points, 0 base xp, 0 job xp, wipes the 
-     status effects, sets all stats to 1. If the new job is 'Novice High', give 
-     100 status points, give First Aid and Play Dead skills.
- 2 - Base level 1, Job level 1, 0 skill points, 0 XP/JXP. Skills and attribute 
-     values are not altered.
- 3 - Base level 1, base xp 0. Nothing else is changed.
- 4 - Job level 1, job xp 0. Nothing else is changed.
+---------------------------------------
 
-In all cases it will also unequip everything the character has on.
+*divorce()
 
-Even though it doesn't return a value, it is used as a function in the official 
-rebirth scripts. Ask AppleGirl why.
+This function will un-marry the invoking character from whoever they were 
+married to. Both will no longer be each other's marriage partner, (at least in 
+current SVN, which prevents the cases of multi-spouse problems). It will return 
+1 upon success or 0 if the character was not married at all.
+
+This function will also destroy both wedding rings and send a message to both 
+players, telling them they are now divorced.
 
 ---------------------------------------
 
-*resetstatus;
+*adopt "<parent name>","<parent name>","<novice name>";
+*adopt("<parent name>","<parent name>","<novice name>")
 
-This is a character reset command, which will reset the stats on the invoking 
-character and give back all the stat points used to raise them previously. 
-Nothing will happen to any other numbers about the character.
+This command will set up a novice as a baby of a married couple. All three are 
+referred to by character name. The correct variables are set on all three 
+characters in the same call. The command will unequip anything the novice has 
+equipped and make them a Job_Baby class, as well as send them a 'your job has 
+been changed' message.
 
-Used in reset NPC's (duh!)
+Beware of calling this from inside a 'callfunc' function, cause upon successful 
+adoption, this command returns a zero, as if it were a function. This is likely 
+to screw up execution of a 'return' command. You may try to call it as a 
+function instead, but it doesn't return anything upon an error, which may also 
+cause script execution to throw up errors.
+
+Nothing will happen (and nothing will be returned either) if either future 
+parent is below base level 70 and/or if any of the three characters is not found 
+online.
 
+---------------------------------------
+//
+4,3.- End of marriage-related commands
+//
 ---------------------------------------
 
-*resetskill;
+*pcfollow <id>,<target id>;
+*pcstopfollow <id>; 
 
-This command takes off all the skill points on the invoking character, so they 
-only have Basic Skill blanked out (lvl 0) left, and returns the points for them 
-to spend again. Nothing else will change but the skills. Quest skills will also 
-reset if 'quest_skill_reset' option is set to Yes in 'battle_athena.conf'. If 
-the 'quest_skill_learn' option is set in there, the points in the quest skills 
-will also count towards the total.
+Makes a character follow or stop following someone. This command does the same as the @follow command.
+The main difference is that @follow can use character names, and this commands needs the Account ID for the target.
 
-Used in reset NPC's (duh!)
+Example(s):
 
+//This will make Aaron follow Bullah, when both of these characters are online.
+	PCFollow getCharID(3,"Aaron"),getCharID(3,"Bullah");
+	
+//Makes Aaron stop following whoever he is following.
+	PCStopFollow getCharID(3,"Aaron");
+	
 ---------------------------------------
 
-*changebase <job ID number>;
+* pcblockmove <id>,<option>;
 
-This will change the appearance of the invoking character to that of a specified 
-job class. Nothing but appearance will change. This command is used in item 
-scripts for "Wedding Dress" and "Tuxedo" so the character like job 22, which is 
-the job number of the wedding sprites.
+Prevents the given ID from moving when the option != 0, 0 enables the ID to move again.
+ID should be able to be GID of a monster/npc or AID from a character.
 
-It would be entered in the equip bonus section of an item
+Example(s):
 
-2338,Wedding_Dress,Wedding Dress,5,43000,,500,,0,,0,119529470,7,0,16,,0,1,0,{ bonus bMdef,15; changebase 22; }
+//prevents the current char from moving away;
+	pcblockmove getcharid(3),1;
+	
+//enables the current char to move again.	
+	pcblockmove getcharid(3),0;
 
-This command only works when inside item scripts.
+--------------------------------------- 
 
+==================================
+|5.- Mob / NPC -related commands.|
+==================================
 ---------------------------------------
 
-*changesex;
+*monster "<map name>",<x>,<y>,"<name to show>",<mob id>,<amount>{,"<event label>"};
+*areamonster "<map name>",<x1>,<y1>,<x2>,<y2>,"<monster name>",<amount>{,"<event label>"};
 
-This command will change the gender for the attached character's account. If it 
-was male, it will become female, if it was female, it will become male. The 
-change will be written to the character server, but there is no way to send this 
-information to the client, so the player will continue to see their character as 
-the gender it previously was. What the other players will see before the 
-relogin is not clear.
+This command will spawn a monster on the specified coordinates on the specified 
+map. If the script is invoked by a character, a special map name, "this", will 
+be recognised to mean the name of the map the invoking character is located at. 
+This command works fine in the item scripts.
 
-If the character currently connected when this command was invoked was a 
-Dancer/Gypsy or Bard/Clown, they will become a Swordman upon 'changesex'. 
-Whatever happens to their skills is not clear. Whatever happens if another 
-character on the same account was a gender-specific class is not clear either, 
-but it's likely that the client will have serious issues with that, since no 
-other characters on the same account will get altered.
+The same command arguments mean the same things as described above in the 
+beginning of this document when talking about permanent monster spawns. Monsters 
+spawned in this manner will not respawn upon being killed.
 
-There's good reasons to be very careful when using this command.
+Unlike the permanent monster spawns, if the mob id is -1, a random monster will 
+be picked from the entire database according to the rules configured in the 
+server for dead branches. This will work for all other kinds of non-permanent 
+monster spawns.
 
----------------------------------------
+The only very special thing about this command is an event label, which is an 
+optional parameter. This label is written like '<NPC object name>::<label name>' 
+and upon the monster being killed, it will execute the script inside of the 
+specified NPC object starting from the label given. The RID of the player 
+attached at this execution will be the RID of the killing character.
 
-*waitingroom "<chatroom name>",<limit>{,<event label>,<trigger>};
+    monster "place.gat",60,100,"Poring",1002,1,"NPCNAME::OnLabel";
 
-This command will create a chat room, owned by the NPC object running this 
-script and displayed above the NPC sprite.
-The maximum length of a chatroom name is 60 letters.
+If you do not specify any event label, a label in the NPC object that ran this 
+command, called 'OnMyMobDead:' will execute anyway, if present.
 
-The limit is the maximum number of people allowed to enter the chat room. If the 
-optional event and trigger parameters are given, the event label 
-("<NPC object name>::<label name>") will be invoked as if with a 'doevent' upon 
-the number of people in the chat room reaching the given triggering amount.
+The coordinates of 0,0 will spawn the monster on a random place on the map.
 
-It's funny, but for compatibility with jAthena, you can swap the event label and 
-the trigger parameters, and it will still work.
+The 'areamonster' command works much like the 'monster' command and is not 
+significantly different, but spawns the monsters within a square defined by 
+x1/y1-x2/y2.
 
-// The NPC will just show a box above its head that says "Hello World", clicking 
-// it will do nothing, since the limit is zero.
-    waitingroom "Hello World",0;
+Simple monster killing script:
 
-// The NPC will have a box above its head, it will say "Disco - Waiting Room" 
-// and will have 8 waiting slots. Clicking this will enter the chat room, where 
-// the player will be able to wait until 8 people accumulate. Once this happens, 
-// it will cause the NPC "Bouncer" run the label "OnStart"
+        <Normal NPC object definition. Let's assume you called him NPCNAME.>
+        mes "[Summon Man]";
+        mes "Want to start the kill?";
+        next;
+        menu "Yes",L_Yes,"No",-;
+        mes "[Summon Man]";
+        mes "Come back later";
+        close;
+    L_Yes:
+        monster "prontera.gat",0,0,"Quest Poring",1002,10,"NPCNAME::OnPoringKilled";
+        // By using 0,0 it will spawn them in a random place.
+        mes "[Summon Man]";
+        mes "Now go and kill all the Poring I summoned";
+        // He summoned ten.
+        close;
+    L_PoringKilled:
+        set $PoringKilled,$PoringKilled+1;
+        if ($PoringKilled==10) goto L_AllDead;
+        end;
+    L_AllDead:
+        announce "Summon Man: Well done all the poring are dead",3;
+        set $PoringKilled,0;
+        end;
 
-    waitingroom "Disco - Waiting Room",8,"Bouncer::OnStart",8;
+For more good examples see just about any official 2-1 or 2-2 job quest script.
 
-Creating a waiting room does not stop the execution of the script and it will 
-continue to the next line.
+---------------------------------------
 
-For more examples see the 2-1 and 2-2 job quest scripts which make extensive use 
-of waiting rooms.
+*killmonster "<map name>","<event label>";
+
+This command will kill all monsters that were spawned with 'monster' or 
+'addmonster' and have a specified event label attached to them. Commonly used to 
+get rid of remaining quest monsters once the quest is complete.
+
+If the label is given as "All", all monsters which have their respawn times set 
+to -1 (like all the monsters summoned with 'monster' or 'areamonster' script 
+command, and all monsters summoned with GM commands, but no other ones - that 
+is, all non-permanent monsters) on the specified map will be killed regardless 
+of the event label value.
 
 ---------------------------------------
 
-*delwaitingroom {"<NPC object name"};
+*killmonsterall "<map name>";
 
-This command will delete a waiting room. If no parameter is given, it will 
-delete a waiting room attached to the NPC object running this command, if it is, 
-it will delete a waiting room owned by another NPC object. This is the only way 
-to get rid of a waiting room, nothing else will cause it to disappear.
+This command will kill all monsters on a specified map name, regardless of how 
+they were spawned or what they are.
 
-It's not clear what happens to a waiting room if the NPC is disabled with 
-'disablenpc', by the way.
+---------------------------------------
+
+*strmobinfo(<type>,<monster id>);
+
+This function will return information about a monster record in the database, as 
+per 'db/mob_db.txt'. Type is the kind of information returned. Valid types are:
+
+ 1 - 'english name' field in the database, a string.
+ 2 - 'japanese name' field in the database, a string.
+     All other returned values are numbers:
+ 3 - Level.
+ 4 - Maximum HP.
+ 5 - Maximum SP.
+ 6 - Experience reward.
+ 7 - Job experience reward.
 
 ---------------------------------------
 
-*enablewaitingroomevent {"<NPC object name>"};
-*disablewaitingroomevent {"<NPC object name>"};
+*mobcount("<map name>","<event label>")
 
-This will enable and disable triggering the waiting room event (see 
-'waitingroom') respectively. Optionally giving an NPC object name will do that 
-for a specified NPC object. The chat room will not disappear when triggering is 
-disabled and enabled in this manner and players will not be kicked out of it.
-Enabling a chat room event will also cause it to immediately check whether the 
-number of users in it exceeded the trigger amount and trigger the event 
-accordingly.
+This function will count all the monsters on the specified map that have a given 
+event label and return the number or 0 if it can't find any. Naturally, only 
+monsters spawned with 'monster' and 'areamonster' script commands can be like 
+this.
 
-Normally, whenever a waiting room was created to make sure that only one 
-character is, for example, trying to pass a job quest trial, and no other 
-characters are present in the room to mess up the script.
+However, apparently, if you pass this function an empty string for the event 
+label, it should return the total count of normal permanently respawning 
+monsters instead. With the current dynamic mobs system, where mobs are not kept 
+in memory for maps with no actual people playing on them, this will return a 0 
+for any such map.
 
 ---------------------------------------
 
-*getwaitingroomstate(<information type>{,"<NPC object name>"})
+*clone "<map name>",<x>,<y>,"<event>",<char id>{,<master_id>{,<mode>{,<flag>,<duration>}}}
 
-This function will return information about the wating room state for the 
-attached waiting room or for a waiting room attached to the specified NPC if 
-any.
+This command creates a monster which is a copy of another player. The first
+four arguments serve the same purpose as in the monster script command, The
+<char id> is the character id of the player to clone (player must be online).
+If <master id> is given, the clone will be a 'slave/minion' of it. Master_id
+must be a character id of another online player.
 
-The valid information types are:
+The mode can be specified to determine the behaviour of the clone, it's
+values are the same as the ones used for the mode field in the mob_db. The
+default mode is aggressive, assists, can move, can attack.
 
- 0  - Number of users currently chatting.
- 1  - Maximum number of users allowed.
- 2  - Will return 1 if the waiting room has a trigger set.
-      0 otherwise.
- 3  - Will return 1 if the waiting room is currently disabled.
-      0 otherwise.
- 4  - The Title of the waiting room (string)
- 5  - Password of the waiting room, if any. Pointless, since there is no way to 
-      set a password on a waiting room right now.
- 16 - Event name of the waiting room (string)
- 32 - Whether or not the waiting room is full.
- 33 - Whether the amount of users in the waiting room is higher than the trigger 
-      number.
+Flag can be either zero or one currently. If zero, the clone is a normal
+monster that'll target players, if one, it is considered a summoned monster,
+and as such, it'll target other monsters. Defaults to zero.
 
----------------------------------------
+The duration specifies how long the clone will live before it is auto-removed.
+Specified in seconds, defaults to no limit (zero).
 
-*warpwaitingpc "<map name>",<x>,<y>{,<number of people>};
+Returned value is the monster ID of the spawned clone. If command fails,
+returned value is zero.
 
-This command will warp the amount of characters equal to the trigger number of 
-the waiting room chat attached to the NPC object running this command to the 
-specified map and coordinates, kicking them out of the chat. Those waiting the 
-longest will get warped first. It can also do a random warp on the same map 
-("Random" instead of map name) and warp to the save point ("SavePoint").
+---------------------------------------
 
-The list of characters to warp is taken from the list of the chat room members. 
-Those not in the chat room will not be considered even if they are talking to 
-the NPC in question. If the number of people is given, exactly this much people 
-will be warped.
+*summon "Monster name",<monster id>{,<Time Out>{,"event label"}};
 
-This command can also keep track of who just got warped. It does this by setting 
-special variables:
+This command will summon a monster. (see also 'monster') Unlike monsters spawned
+with other commands, this one will set up the monster to fight to protect the
+invoking character. Monster name and mob id obey the same rules as the one given
+at the beginning of this document for permanent monster spawns with the
+exceptions mentioned when describing 'monster' command.
 
-$@warpwaitingpc[] is an array containing the character id numbers of the 
-                  characters who were just warped.
-$@warpwaitingpcnum contains the number of the character it just warped.
+The effect for the skill 'Call Homonuculus' will be displayed centered on the
+invoking character.
 
-See also 'getpartymember' for advice on what to do with those variables.
+Timeout is the time in milliseconds the summon lives, and is set default 
+to 60000 (1 minute). Note that also the value 0 will set the timer to default,
+and it is not possible to create a spawn that lastst forever.
+If an event label is given, upon the monster being killed, the event label will
+run as if by 'donpcevent'.
 
-The obvious way of using this effectively would be to set up a waiting room for 
-two characters to be warped onto a random PVP map for a one-on-one duel, for 
-example.
+// Will summon a dead branch-style monster to fight for the character.
+summon "--ja--",-1;
 
 ---------------------------------------
 
-*waitingroomkickall {"<NPC object name>"};
+* homunculus_evolution;
 
-This command would kick everybody out of a specified waiting room chat. IF it 
-was properly linked into the script interpreter which it isn't, even though the 
-code for it is in place. Expect this to become available in upcoming SVN 
-releases.
+This command will try to evolve the current player's homunculus.
+If it doesn't work, the /swt emoticon is shown.
 
----------------------------------------
+To evolve a homunculus, the invoking player must have a homunculus,
+the homunculus must not be the last evolution and
+the homunculus must be on at least 91000/100000 intimacy with it's owner.
 
-*attachrid(<character ID>)
-*detachrid
+---------------------------------------
+------------------------------------------------
+//===========================================\\
+||         Mob Control Suit Commands         ||
+\\===========================================//
+------------------------------------------------
 
-A 'RID' is an ID of a character who caused the NPC script to run, as has been 
-explained above in the introduction section. Quite a bit of commands want a RID 
-to work, since they wouldn't know where to send information otherwise. And in 
-quite a few cases the script gets invoked with a RID of zero (like through 
-OnTime special labels). If an NPC script needs this, it can attach a specified 
-character's id to itself. by calling the 'attachrid' function.
+---------------------------------------
 
-'attachrid' returns 1 if the character was found online and 0 if it wasn't.
+* mobspawn (<monster name>,<monster ID>,<mapname>,<x>,<y>)
+* mobRemove <GID>;
 
-This could also be used, while running in a script invoked by a character 
-through talking to an NPC, to mess with other characters.
-Detaching the RID will make the RID of the script zero.
+This is used to spawn a monster and return it's Game ID, to be used
+in the unit/mobcontrol commands.
 
----------------------------------------
+Note, I will use the stuff here in the examples for the unitcontrol.
 
-*isloggedin(<character id>)
+Example(s):
 
-This function returns 1 if the specified character is logged in and 0 if they 
-aren't.
+//Spawns a poring named poi poi and put's it's GID in .GID.
+	set .GID,mobspawn("Poi Poi",1002,"prontera.gat",160,180);
+//would kill our poring.
+	mobRemove .GID;
 
 ---------------------------------------
 
-*setmapflagnosave "<map name>","<alternate map name>",<x>,<y>;
-
-This command sets the 'nosave' flag for the specified map and also gives an 
-alternate respawn-upon-relogin point.
-
-It does not make a map impossible to make a savepoint on as you would normally 
-think, 'savepoint' will still work. It will, however, make the specified map 
-kick the reconnecting players off to the alternate map given to the coordinates 
-specified.
+* getmobdata (<GID>,<arrayname>)
+* setmobdata <GID>,<parameter>,<new value>;
 
----------------------------------------
+This is used to get and set special data related to the monster.
+With getmobdata, the array given will be filled with the current data. In setmobdata
+the indexes in the array would be used to set that data on the monster. 
+Parameters (indexes) are:
 
-*setmapflag "<map name>",<flag>;
+0 = class (big, small, normal)			7  = y						14 = hair style		21 = weapon
+1 = level					8  = speed					15 = hair color		22 = shield (again)
+2 = HP						9  = mode (see doc/mob_db_mode_list.txt)	16 = head gear bottom	23 = looking dir
+3 = max HP					10 = special AI state (?)			17 = head gear middle	24 = killer state (1 or 0)
+4 = master ID (aid of the master, summon)	11 = SC option					18 = head gear top	25 = callback flag
+5 = map index					12 = sex					19 = cloth color	26 = no random walk (1 or 0)
+6 = x						13 = class (Monster ID, Job ID)			20 = shield		
 
-This command marks a specified map with a map flag given. Map flags alter the 
-behavior of the map, you can see the list of the available ones in 
-'db/const.txt' under 'mf_'.
+Example(s):
 
-The map flags alter the behavior of the map regarding teleporting (mf_nomemo, 
-mf_noteleport, mf_nowarp, mf_nogo) storing location when disconnected 
-(mf_nosave), dead branch usage (mf_nobranch), penalties upon death 
-(mf_nopenalty, mf_nozenypenalty), PVP behavior (mf_pvp, mf_pvp_noparty, 
-mf_pvp_noguild, mf_nopvp), WoE behavior (mf_gvg,mf_gvg_noparty), ability to use 
-skills or open up trade deals (mf_notrade, mf_novending, mf_noskill, mf_noicewall),
-current weather effects (mf_snow, mf_fog, mf_sakura, mf_leaves, mf_rain, mf_clouds, 
-mf_fireworks) and whether day/night will be in effect on this map (mf_indoors).
+//this will set all the mobdata in the @array variable. (@array[1] being level, @array[13] class etc)
+	getmobdata .GID,@array;
+	
+//set the max hp of our poring to 1000.
+	setmobdata .GID,3,1000;
 
 ---------------------------------------
 
-*removemapflag "<map name>",<flag>;
+* mobassist <GID>,<target id>;
+This will make the monster assist the Target ID as if it was a summon of it.
+Example(s):
 
-This command removes a mapflag from a specified map. See 'setmapflag'.
+/this will make our poring assist the current attached player! >:3
+	mobassist .GID,getcharid(3);
 
 ---------------------------------------
 
-*pvpon "<map name>";
-*pvpoff "<map name>";
+* mobattach <GID>{,"<NPC Name>"};
 
-These commands will turn PVP mode for the specified maps on and off. Beside 
-setting the flags referred to in 'setmapflag', 'pvpon' will also create a PVP 
-timer and ranking as will @pvpon GM command do.
+GID is the GID of a monster, NPC or account id. The NPC running or
+he NPC name given is used to attach the monster.
+
+By attaching a monster, the NPC to which it is attached is ran on special actions by the monster.
+The system will set specific data in the .ai_action variable array on the NPC invoked.
+The special AI actions types are set in the .ai_action at place AI_ACTION_TAR_TYPE
+
+More AI_ vars are set in const.txt, and you can also look at sample/monstercontroller.cpp:
 
 ---------------------------------------
 
-*gvgon "<map name>";
-*gvgoff "<map name>";
+* unitwalk <GID>,<x>,<y>;
+* unitwalk <GID>,<mapid>;
 
-These commands will turn GVG mode for the specified maps on and off, setting up 
-appropriate map flags. In GVG mode, maps behave as if during the time of WoE, 
-even though WoE itself may or may not actually be in effect. 
+This is one command, but can be used in two ways. If only the first argument is given,
+the unit whose GID is given will start walking towards the map with the given mapid 
+(we believe these are the mapindexes found in db/map_index.txt).
 
----------------------------------------
+When 2 arguments are passed, the given unit will walk to the given x,y coordinates on 
+the map where the unit currently is.
 
-*emotion <emotion number>{, target};
+Example(s):
 
-This command makes an object display an emoticon sprite above their own as 
-if they were doing that emotion. For a full list of emotion numbers, 
-see 'db/const.txt' under 'e_'. The inobvious ones are 'e_what' (a question mark) 
-and 'e_gasp' (the exclamation mark).
+//Will move/walk the poring we made to the coordinates 150,150
+	unitwalk .GID,150,150;
 
-The optional target parameter specifies who will get the emotion on top of
-their head. If 0 (the default if omitted), the NPC in current use will show
-the emotion, if 1, the player that is running the script will display it.
+//Will move the poring towards alberta (if my assumed mapindexes are correct).
+	unitwalk .GID,3;
 
 ---------------------------------------
 
-*maprespawnguildid "<map name>",<guild id>,<flag>;
-
-This command goes through the specified map and for each player and monster 
-found there does stuff.
+* unitkill <GID>;
+* unitwarp <GID>,<Mapname>,<x>,<y>;
+* unitattack <GID>,<Target ID>;
+* unitstop <GID>;
+* unittalk <GID>,<Text>;
+* unitemote <GID>,<Emote>;
+* unitdeadsit <GID>,<Action?>;
 
-Flag is a bitmask (add up numbers to get effects you want)
- 1 - warp all guild members to their savepoints.
- 2 - warp all non-guild members to their savepoints.
- 4 - remove all monsters which are not guardian or emperium.
+Okay, these commands should be fairly self explaining.
 
-Flag 7 will, therefore, mean 'wipe all mobs but guardians and the emperium and 
-kick all characters out', which is what the official scripts do upon castle 
-surrender. Upon start of WoE, the scripts do 2 (warp all intruiders out).
+For the emotions, you can look in db/const.txt for prefixes with e_
+The unitdeadsit uses an action, not exactly sure why it's named unitdeadsit...
 
-Characters not belonging to any guild will warp out regardless of the flag setting.
+Anyhoo: actions are
+0: normal attack
+1: pick stone like
+2: normal sit	
+3: nothing?
 
-For examples, check the WoE scripts in the distribution.
+---------------------------------------
 
+------------------------------------------------
+//===========================================\\
+||      End of Mob Control Suit Commands     ||
+\\===========================================//
+------------------------------------------------
 ---------------------------------------
 
-*agitstart;
-*agitend;
+*disablenpc "<NPC object name>";
+*enablenpc "<NPC object name>";
 
-These two commands will start and end War of Emperium.
+These two commands will disable and enable, respectively, an NPC object 
+specified by name. The disabled NPC will disappear from sight and will no longer 
+be triggerable in the normal way. It is not clear whether it will still be 
+accessible through 'donpcevent' and other triggering commands, but it probably 
+will be. You can disable even warp NPCs if you know their object names, which is 
+an easy way to make a map only accessible through walking half the time. Then 
+you 'enablenpc' them back.
 
-This is a bit more complex than it sounds, since the commands themselves won't 
-actually do anything interesting, except causing all 'OnAgitStart:' and 
-'OnAgitEnd:' events to run everywhere, respectively. They are used as 
-simple triggers to run a lot of complex scripts all across the server, and they, 
-in turn, are triggered by clock with an 'OnClock<time>:' time-triggering label.
+You can also use these commands to create the illusion of an NPC switching 
+between several locations, which is often better than actually moving the NPC -
+create one NPC object with a visible and a hidden part to their name, make a few 
+copies, and then disable all except one.
 
 ---------------------------------------
 
-*agitcheck()
+*hideonnpc "<NPC object name>";
+*hideoffnpc "<NPC object name>";
 
-This function will let you check whether the server is currently in WoE mode.
-It will return 1 if the War of Emperium is on and 0 if it isn't.
+These commands will make the NPC object specified display as hidden/visible, 
+even though not actually disabled per se. Hidden as in thief Hide skill, but 
+unfortunately, not detectable by Ruwach or Sight.
+
+As they are now, these commands are pointless, it is suggested to use 
+'disablenpc'/'enablenpc', because these two commands actually unload the NPC 
+sprite location and other accompanying data from memory when it is not used.
+However, you can use these for some quest ideas (such as cloaking npcs talking 
+while hidden then revealing.... you can wonder around =P
 
 ---------------------------------------
 
-*flagemblem <guild id>;
+*doevent "<NPC object name>::<event label>";
 
-This command only works when run by the NPC objects which have sprite id 722, 
-which is a 3D guild flag sprite. If it isn't, the data will change, but nothing 
-will be seen by anyone. If it is invoked in that manner, the emblem of the 
-specified guild will appear on the flag, though, if any players are watching it 
-at this moment, they will not see the emblem change until they move out of sight 
-of the flag and return.
+This command will start a new execution thread in a specified NPC object at the 
+specified label. The execution of the script running this command will not stop. 
+No parameters may be passed with a doevent call.
 
-This is commonly used in official guildwar scripts with a function call which 
-returns a guild id:
+The script of the NPC object invoked in this manner will run as if it's been 
+invoked by the RID that was active in the script that issued a 'doevent'.
 
-// This will change the emblem on the flag to that of the guild that owns
-// "guildcastle"
+    place.gat,100,100,1%TAB%script%TAB%NPC%TAB%53,{
+        mes "This is what you will see when you click me";
+        close;
+    Label:
+        mes "This is what you will see if the doevent is activated";
+        close;
+    }
 
-    flagemblem GetCastleData("guildcastle.gat",1); 
+    ....
 
----------------------------------------
+    doevent "NPC::Label";
 
-*getcastlename("<map name>")
+---------------------------------------
 
-This function returns the name of the castle when given the map name for that 
-castle. The data is read from 'db/castle_db.txt'.
+*donpcevent "{NPC NAME}::<event label>";
 
----------------------------------------
+This command is kinda confusing cause it performs in two completely different 
+ways.
 
-*getcastledata("<map name>",<type of data>)
-*setcastledata "<map name>",<type of data>,<value>;
+If the event label is phrased like "::<label name>", all NPC objects that have a 
+specified label in them will be invoked as if by a 'doevent', but no RID 
+whatsoever will be attached while they execute.
 
-This function returns the castle ownership information for the castle referred 
-to by it's map name. Castle information stored in 'save\castle.txt' for the TXT 
-version of the server and in 'guild_castle' table for the SQL version.
+Otherwise, if the label is given as "<NPC name>::<label name>", a label within 
+the NPC object that runs this command will be called, but as if it was running 
+inside another, specified NPC object. No RID will be attached to it in this case 
+either.
 
-Valid types of data are:
+This can be used for making another NPC react to an action that you have done 
+with the NPC that has this command in it, i.e. show an emotion, or say 
+something.
 
- 0 - Will make the map server request the castle data from the char server, and 
-     always return 0. This, apparently, will also cause indirectly the execution 
-     of an 'OnAgitInit:' event mentioned at the beginning of this document.
- 1 - Guild ID
- 2 - Castle Economy score.
- 3 - Castle Defence score.
- 4 - Number of times the economy was invested in today.
- 5 - Number of times the defence was invested in today.
- 9 - Will return 1 if a Kafra was hired for this castle, 0 otherwise.
-10 - Is 1 if the 1st guardian is present (Soldier Guardian)
-11 - Is 1 if the 2nd guardian is present (Soldier Guardian)
-12 - Is 1 if the 3rd guardian is present (Soldier Guardian)
-13 - Is 1 if the 4th guardian is present (Archer Guardian)
-14 - Is 1 if the 5th guardian is present (Archer Guardian)
-15 - Is 1 if the 6th guardian is present (Knight Guardian)
-16 - Is 1 if the 7th guardian is present (Knight Guardian)
-17 - Is 1 if the 8th guardian is present (Knight Guardian)
+    place.gat,100,100,1%TAB%script%TAB%NPC%TAB%53,{
+        mes "Hey NPC2 copy what I do";
+        close2;
+        set @emo, rand(1,30);
+        donpcevent "NPC2::Emo";
+    Emo:
+        emotion @emo;
+        end;
+    }
 
-18-25 types of data will return current hit point values for guardians 1-8 
-respectively.
+    place.gat,102,100,1%TAB%script%TAB%NPC2%TAB%53,{
+        mes "Hey NPC copy what I do";
+        close2;
+        set @emo, rand(1,30);
+        donpcevent "NPC::Emo";
+    Emo:
+        emotion @emo;
+        end;
+    }
 
-The 'setcastledata' command will behave identically, but instead of returning 
-values for the specified types of accessible data, it will alter them and cause 
-them to be sent to the char server for storage. Data type of 0 won't do 
-anything, obviously.
+This will make both NPC perform the same random emotion from 1 to 30, and the 
+emotion will appear above each of their heads.
 
 ---------------------------------------
 
-*requestguildinfo <guild id>,"<event label>";
+*npctalk "<message>";
 
-This command requests the guild data from the char server and merrily continues 
-with the execution. Whenever the guild information becomes available (which 
-happens instantly if the guild information is already in memory, or later, if it 
-isn't and the map server has to wait for the char server to reply) it will run 
-the specified event as in a 'doevent' call.
+This command will display a message to the surrounding area as if the NPC object 
+running it was a player talking - that is, above their head and in the chat 
+window. The display name of the NPC will get appended in front of the message to 
+complete the effect.
+
+    // This will make everyone in the area see the NPC greet the character
+    // who just invoked it.
+    npctalk "Hello "+strcharinfo(0)+" how are you";
 
 ---------------------------------------
+\\
+5,1.- Time-related commands
+\\
+---------------------------------------
+*addtimer <ticks>,"<NPC object name>::<label>";
+*deltimer "<NPC object name>::<event label>";
+*addtimercount <ticks>,"<NPC object name>::<event label>";
 
-*getequipcardcnt(<equipment slot>)
+These commands will create, destroy, and delay a countdown timer - 'addtimer' to 
+create, 'deltimer' to destroy and 'addtimercount' to delay it by the specified 
+number of ticks. For all three cases, the event label given is the identifier of 
+that timer.
 
-This function will return the number of cards that have been compounded onto a 
-specific equipped item for the invoking character. See 'getequipid' for a list 
-of possible equipment slots.
+When this timer runs out, a new execution thread will start in the specified NPC 
+object at the specified label. If no such label is found in the NPC object, it 
+will run as if clicked. In either case, no RID will be attached during 
+execution.
+
+The ticks are given in 1/1000ths of a second.
 
 ---------------------------------------
 
-*successremovecards <equipment slot>;
+*stoptimer;
+*inittimer;
+*enablearena;
+*disablearena;
+*cmdothernpc "<npc name?>","<command?>";
 
-This command will remove all cards from the item found in the specified 
-equipment slot of the invoking character, create new card items and give them to 
-the character. If any cards were removed in this manner, it will also show a 
-success effect.
+This set of commands is marked as added by someone going under the nickname 
+'RoVeRT', as mentioned the source code comments, and has to do with timers and 
+scheduling working entirely unlike any other timing commands. It is not certain 
+that they actually even work properly anymore, and most of these read no 
+arguments, though the 'inittimer'/'stoptimer' pair of commands has to do 
+something with an 'OnTimer' label and will probably invoke it and 'cmdothernpc' 
+will execute starting with the label 'OnCommand'. Whatever they actually do, the 
+other commands can most likely do it better. The two arena commands definitely 
+do not do anything useful at all.
+
+None of these commands are used in any scripts bundled with eAthena. Most 
+probably they are deprecated and left in by mistake.
+
+Unless RoVeRT can be found and asked to clarify what these were made for, that 
+is.
 
 ---------------------------------------
 
-*failedremovecards <equipment slot>,<type>;
+*initnpctimer{ "<NPC object name>"};
+*stopnpctimer{ "<NPC object name>"};
+*startnpctimer{ "<NPC object name>"};
+*setnpctimer <tick>{,"<NPC object name>"};
+*getnpctimer(<type of information>{,"<NPC object name>"});
+*attachnpctimer {"<character name>"};
+*detachnpctimer {"<NPC object name>"};
 
-This command will remove all cards from the item found in the specified 
-equipment slot of the invoking character. 'type' determines what happens to the 
-item and the cards:
+This set of commands and functions will create and manage an NPC-object based 
+timer. The NPC object may be declared by name, or the name in all cases may be 
+omitted, in that case this timer will be based in the object the current script 
+is running in.
 
- 0 - will destroy both the item and the cards.
- 1 - will keep the item, but destroy the cards.
- 2 - will keep the cards, but destroy the item.
-  
-Whatever the type is, it will also show a failure effect on screen.
+Why is it actually part of an NPCs structure we aren't sure, but it is, and 
+while 'addtimer'/'deltimer' commands will let you have many different timers 
+referencing different labels in the same NPC, one each and each with their own 
+countdown, 'initnpctimer' can only have one per NPC object. But it can trigger 
+many labels and it can let you know how many were triggered already and how many 
+still remain.
 
----------------------------------------
+This timer is counting up from 0 in ticks of 1/1000ths of a second each. Upon 
+creating this timer, the execution will not stop, but will happily continue 
+onward. The timer will then invoke new execution threads at labels 
+"OnTimer<time>:" in the NPC object it is attached to. 
 
-*marriage("<spouse name>");
+To create the timer, use the 'initnpctimer', which will start it running. 
+'stopnpctimer' will pause the timer, without clearing the current tick, while 
+'startnpctimer' will let the paused timer continue.
 
-This function will marry two characters, the invoking character and the one 
-referred to by name given, together, setting them up as each other's marriage 
-partner. No second function call has to be issued (in current SVN at least) to 
-make sure the marriage works both ways. The function returns 1 upon success, or 
-0 if the marriage could not be completed, either because the other character 
-wasn't found or because one of the two characters is already married.
+It is not quite clear whether the new invocations will always have a RID. 
+Apparently, the RID that was in effect when the timer was initialised will still 
+be attached to these executions in some cases, but it's not quite clear -
+experiment with RID-dependent commands, like 'mes', and tell us what happens and 
+who gets the message, if anyone.
 
-This will do nothing else for the marriage except setting up the spouse ID for 
-both of these characters. No rings will be given and no effects will be shown.
+Even if they don't have a RID by default, 'attachnpctimer' will allow you to 
+explicitly attach a character's RID to the timer, which will make them the 
+target for all character-referencing commands and functions, not to mention 
+variables. 'detachnpctimer' will make the RID zero, making all character-
+referencing functions fail with an error.
 
----------------------------------------
+'setnpctimer' will explicitly set the timer to a given tick. To make it useful, 
+you will need the 'getnpctimer' function, which the type of information argument 
+means:
 
-*wedding;
+ 0 - Will return the current tick count of the timer.
+ 1 - Will return 1 if there are remaining "OnTimer<ticks>:" labels in the 
+     specified NPC waiting for execution.
+ 2 - Will return the number of times the timer has triggered an "OnTimer<tick>:" 
+     label in the specified NPC.
 
-This command will call up wedding effects - the music and confetti - centered on 
-the invoking character.
+Example 1:
 
----------------------------------------
+    <NPC Header> {
+        initnpctimer;
+        npctalk "I cant talk right now, give me 10 seconds";
+        end;
+    OnTimer5000:
+        npctalk "Ok 5 seconds more";
+        end;
+    OnTimer6000:
+        npctalk "4";
+        end;
+    OnTimer7000:
+        npctalk "3";
+        end;
+    OnTimer8000:
+        npctalk "2";
+        end;
+    OnTimer9000:
+        npctalk "1";
+        end;
+    OnTimer10000:
+        stopnpctimer;
+        mes "[Man]";
+        mes "Ok we can talk now";
+    }
 
-*divorce()
+Example 2:
 
-This function will un-marry the invoking character from whoever they were 
-married to. Both will no longer be each other's marriage partner, (at least in 
-current SVN, which prevents the cases of multi-spouse problems). It will return 
-1 upon success or 0 if the character was not married at all.
+    OnTimer15000:
+        set $quote,rand(5);
+        if($quote == 0) goto Lquote0;
+        if($quote == 1) goto Lquote1;
+        if($quote == 2) goto Lquote2;
+        if($quote == 3) goto Lquote3;
+        if($quote == 4) goto Lquote4;
+    Lquote0:
+        npctalk "If 0 is randomly picked you will see this";
+        setnpctimer 0;
+        end;
+    Lquote1:
+        npctalk "If 1 is randomly picked you will see this";
+        setnpctimer 0;
+        end;
+    Lquote2:
+        npctalk "If 2 is randomly picked you will see this";
+        setnpctimer 0;
+        end;
+    Lquote3:
+        npctalk "If 3 is randomly picked you will see this";
+        setnpctimer 0;
+        end;
+    Lquote4:
+        npctalk "If 4 is randomly picked you will see this";
+        setnpctimer 0;
+        end;
+       
+    // This OnInit label will run when the script is loaded, so that the timer 
+    // is initialised immediately as the server starts. It is dropped back to 0 
+    // every time the NPC says something, so it will cycle continiously.
+    OnInit:
+        initnpctimer;
+        end;
 
-This function will also destroy both wedding rings and send a message to both 
-players, telling them they are now divorced.
+Example 3:
+
+    mes "[Man]";
+    mes "I have been waiting "+(getnpctimer(0)/1000)+" seconds for you";
+    // we divide the timer returned by 1000 cause it will be displayed in 
+    // milliseconds otherwise
+    close;
+
+Example 4:
 
+    mes "[Man]";
+    mes "Ok I will let you have 30 sec more";
+    close2;
+    setnpctimer (getnpctimer(0)-30000); 
+    // Notice the 'close2'. If there were a 'next' there the timer would be 
+    // changed only after the player pressed the 'next' button.
+    end;
+ 
 ---------------------------------------
+ 
+*sleep {<milliseconds>};
+*sleep2 {<milliseconds>};
+*awake "<NPC name>";
 
-*ispartneron()
+These commands are used to control the pause of a NPC.
+sleep and sleep2 will pause the script for the given amount of milliseconds.
+Awake is used to cancel a sleep. When awake is callen on a NPC it will run as
+if the sleep timer ran out, and thus making the script continue. Sleep and sleep2
+basically do the same, but the main difference is that sleep will not keep the rid,
+while sleep2 does.
 
-This function returns 1 if the invoking character's marriage partner is 
-currently online and 0 if they are not or if the character has no partner.
+Examples:
+	sleep 10000; //pause the script for 10 seconds and ditch the RID (so no player is attached anymore)
+	sleep2 5000; //pause the script for 5 seconds, and continue with the RID attached.
+	awake "NPC"; //Cancels any running sleep timers on the NPC 'NPC'.
 
 ---------------------------------------
+//
+5,1.- End of time-related commands
+//
 
-*getpartnerid()
+*announce "<text>",<flag>{,<color>};
 
-This function returns the character ID of the invoking character's marriage 
-partner, if any. If the invoking character is not married, it will return 0, 
-which is a quick way to see if they are married:
+This command will broadcast a message to all or most players, similar to 
+@kami/@kamib GM commands.
 
-    if (getpartnerid()) mes "I'm not going to be your girlfriend!";
-    if (getpartnerid()) mes "You're married already!";
+The region the broadcast is heard in and the color the message will come up as 
+will be determined by the flags:
 
----------------------------------------
+    announce "This will be shown to everyone at all in yellow.",0;
+
+The flag values are coded as constants in db/const.txt to make them easier to use:
+- bc_all: Broadcast message is sent server-wide
+- bc_map: Message is sent to everyone in the same map
+- bc_area: Message is sent to players in the vecinity of the source.
+- bc_self: Message is sent only to current player.
+
+- bc_npc: Broadcast source is the npc, not the player attached to the script
+  (useful when a player is not attached or the message should be sent to those
+  nearby the npc)
+
+- bc_yellow: The default is to send broadcasts in yellow color.
+- bc_blue: Alternate broadcast is displayed in blue color.
 
-*warppartner("<map name>",<x>,<y>);
+The optional parameter, color, allows usage of broadcasts in any custom color.
+The color parameter is a single number which can be in hexadecimal notation.
+For example:
+    announce "This will be shown to everyone at all in yellow.",bc_all,0xFFFF00;
+Will display a global announce in yellow. The color format is in RGB (0xRRGGBB).
 
-This function will find the invoking character's marriage partner, if any, and 
-warp them to the map and coordinates given. Go kidnap that spouse. :) It will 
-return 1 upon success and 0 if the partner is not online, the character is not 
-married, or if there's no invoking character (no RID). 0,0 will, as usual, 
-normally translate to random coordinates.
+Using this for private messages to players is probably not that good an idea,
+but it can be used instead in NPCs to "preview" an announce.
 
----------------------------------------
+    // This will be a private message to the player using the NPC that made the 
+    // annonucement
+    announce "This is my message just for you",bc_blue|bc_self;
 
-*adopt "<parent name>","<parent name>","<novice name>";
-*adopt("<parent name>","<parent name>","<novice name>");
+    // This will be shown on everyones screen that is in sight of the NPC.
+    announce "This is my message just for you people here",bc_area;
 
-This command will set up a novice as a baby of a married couple. All three are 
-referred to by character name. The correct variables are set on all three 
-characters in the same call. The command will unequip anything the novice has 
-equipped and make them a Job_Baby class, as well as send them a 'your job has 
-been changed' message.
+---------------------------------------
 
-Beware of calling this from inside a 'callfunc' function, cause upon successful 
-adoption, this command returns a zero, as if it were a function. This is likely 
-to screw up execution of a 'return' command. You may try to call it as a 
-function instead, but it doesn't return anything upon an error, which may also 
-cause script execution to throw up errors.
+*mapannounce "<map name>","<text>",<flag>{,<color>};
 
-Nothing will happen (and nothing will be returned either) if either future 
-parent is below base level 70 and/or if any of the three characters is not found 
-online.
+This command will work like 'announce' but will only broadcast to characters 
+currently residing on the specified map. The flag and optional color
+parameters are the same as in 'announce', even though the only ones that make
+sense are the color related ones.
 
 ---------------------------------------
 
-*getchildid()
-*getmotherid()
-*getfatherid()
+*areaannounce "<map name>",<x1>,<y1>,<x2>,<y2>,"<text>",<flag>[,<color>];
 
-These functions return the characters (shild/mother/father) ID
+This command works like 'announce' but will only broadcast to characters 
+residing in the specified x1/y1-x2/y2 square on the map given. The flags and
+color parameter given are the same as in 'announce', but only the color
+related ones have effect.
 
-    if (getmotherid()) mes "Oh... I know your mother's ID:"+getmotherid();
+    areaannounce "prt_church.gat",0,0,350,350,"God's in his heaven, all right with the world",0;
 
 ---------------------------------------
 
-*getitemname(<item id>)
+*callshop "<name>",<option>;
 
-Given the database ID number of an item, this function will return the text 
-stored in the 'japanese name' field (which, in eAthena, stores an english name 
-the players would normally see on screen.)
+These are a series of commands used to create dynamic shops. 
+The callshop function calls a invisible shop (view -1) as if the player clicked on it.
 
----------------------------------------
+For the options on callShop:
+	0 = The normal window (buy, sell and cancel)
+	1 = The buy window
+	2 = The sell window
+	
+Example(s):
 
-*makepet <pet id>;
+callshop "DaShop",1;	//Will call the shop named DaShop and opens the buy menu.
 
-This command will create a pet egg and put it in the invoking character's 
-inventory. The kind of pet is specified by pet ID numbers listed in 
-'db/pet_db.txt'. The egg is created exactly as if the character just successfuly 
-caught a pet in the normal way.
+The shop which is called by callshop (as long as an npcshop* command is executed
+from that NPC (see note 1)) will trigger the labels OnBuyItem and OnSellitem. These
+labels can take over handling for relatively the buying of items from the shop 
+and selling the items to a shop. Via these labels you can customize the way an item
+is bought or sold by a player. 
 
-    // This will make you a poring:
-    makepet 1002;
+In the OnBuyItem, two arrays are set (@bought_nameid and @bough_quantity), which
+hold information about the name id (item id) sold and the amount sold of it. Same 
+goes for the OnSellItem label, only the variables are named different 
+(@sold_nameid and @sold_quantity). An example on a shop comes with eAthena, and 
+can be found in the npc/sample/npc_dynamic_shop.txt file.
+ 
+This example shows how to use the labels and their set variables to create a dynamic shop.
 
-Notice that you absolutely have to create pet eggs with this command. If you try 
-to give a pet egg with 'getitem', pet data will not be created by the char 
-server and the egg will disappear when anyone tries to hatch it.
+Note 1: These labels will only be triggered if a npcshop* command is executed, this is
+because these commands set a special data on the shop npc,named master_nd in the source. 
+The OnSellItem and OnBuyItem are triggered in the NPC whose master_nd is given in the shop.
+This was found out thanks to 'Hondacrx', noticing the OnBuyItem wasn't triggered unless
+npcshopitem was used. After rechecking the source, I found what caused this.
 
 ---------------------------------------
 
-*getexp <base xp>,<job xp>;
+*npcshopitem "<name>",<item id>,<price>{,<item id>,<price>{,<item id>,<price>{,...}}}
 
-This command will give the invoking character a specified number of base and job 
-experience points. Can be used as a quest reward. Negative amounts of experience 
-were not tested but should work.
+This command lets you override the contents of an existing npc shop. The
+current sell list will be wiped, and only the items specified with the price
+specified will be for sale.
 
-    getexp 10000,5000;
+The function returns 1 if shop was updated successfully, or 0 if not found.
 
-You can also use the "set" command with the constants defined in 'db/const.txt':
+Note that you cannot use -1 to specify default selling price!
 
-    // These 2 combined has the same effect as the above command
-    set BaseExp,BaseExp+10000;
-    set JobExp,JobExp+5000;
+---------------------------------------
 
-You can also reduce the ammount of experience points:
+*npcshopadditem "<name>",<item id>,<price>{,<item id>,<price>{,<item id>,<price>{,...}}}
 
-    set BaseExp,BaseExp-10000;
+This command will add more items at the end of the selling list for the
+specified npc shop. If you specify an item already for sell, that item will
+appear twice on the sell list.
 
----------------------------------------
+The function returns 1 if shop was updated successfully, or 0 if not found.
 
-*getinventorylist;
+Note that you cannot use -1 to specify default selling price!
 
-This command sets a bunch of arrays with a complete list of whatever the 
-invoking character has in their inventory, including all the data needed to 
-recreate these items perfectly if they are destroyed. Here's what you get:
+---------------------------------------
 
-@inventorylist_id[]        - array of item ids.
-@inventorylist_amount[]    - their corresponding item amounts.
-@inventorylist_equip[]     - whether the item is equipped or not.
-@inventorylist_refine[]    - for how much it is refined.
-@inventorylist_identify[]  - whether it's refined.
-@inventorylist_attribute[] - whether it is broken.
-@inventorylist_card1[]     - These four arrays contain card data for the items.
-@inventorylist_card2[]       These data slots are also used to store names
-@inventorylist_card3[]       inscribed on the items, so you can explicitly check
-@inventorylist_card4[]       if the character owns an item made by a specific 
-                             craftsman.
-@inventorylist_count       - the number of items in these lists.
+*npcshopdelitem "<name>",<item id>{,<item id>{,<item id>{,...}}}
 
-This could be handy to save/restore a character's inventory, since no other 
-command returns such a complete set of data, and could also be the only way to 
-correctly handle an NPC trader for carded and named items who could resell them 
-- since NPC objects cannot own items, so they have to store item data in 
-variables and recreate the items.
+This command will remove items from the specified npc shop.
+If the item to remove exists more than once on the shop, all instances will be
+removed.
 
-Notice that the variables this command generates are all local and numeric. 
+Note that the function returns 1 even if no items were removed. The return
+value is only to confirm that the shop was indeed found.
 
 ---------------------------------------
 
-*getskilllist;
+*npcshopattach "<name>"{,<flag>}
 
-This command sets a bunch of arrays with a complete list of skills the 
-invoking character has. Here's what you get:
+This command will attach the current script to the given npc shop.
+When a script is attached to a shop, the events "OnBuyItem" and "OnSellItem"
+of your script will be executed whenever a player buys/sells from the shop.
+Additionally, the arrays @bought_nameid[], @bought_quantity[] or @sold_nameid[]
+and @sold_quantity[] will be filled up with the items and quantities
+bought/sold.
 
-@skilllist_id[]   - skill ids.
-@skilllist_lv[]   - skill levels.
-@skilllist_flag[] - see 'skill' for the meaning of skill flags.
-@skilllist_count  - number of skills in the above arrays.
+The optional parameter specifies whether to attach ("1") or detach ("0") from
+the shop (the default is to attach). Note that detaching will detach any npc
+attached to the shop, even if it's from another script, while attaching will
+override any other script that may be already attached.
 
-While 'getskillv' is probably more useful for most situations, this is the 
-easiest way to store all the skills and make the character something else for a 
-while. Advanced job for a day? :) This could also be useful to see how many 
-skills a character has.
+The function returns 0 if the shop was not found, 1 otherwise.
 
 ---------------------------------------
 
-*clearitem;
-
-This command will destroy all items the invoking character has in their 
-inventory. (that includes equipped items) It will not affect anything else, like 
-storage or cart.
-
----------------------------------------
+*waitingroom "<chatroom name>",<limit>{,<event label>,<trigger>};
 
-*classchange <view id>,<type>;
+This command will create a chat room, owned by the NPC object running this 
+script and displayed above the NPC sprite.
+The maximum length of a chatroom name is 60 letters.
 
-This command is very ancient, it's origins are clouded in mystery. 
-It will send a 'display id change' packet to everyone in the immediate area of 
-the NPC object, which will supposedly make the NPC look like a different sprite, 
-an NPC sprite ID, or a monster ID. This effect is not stored anywhere and will 
-not persist (Which is odd, cause it would be relatively easy to make it do so) 
-and most importantly, will not work at all since this command was broken with 
-the introduction of advanced classes. The code is written with the assumption 
-that the lowest sprite IDs are the job sprites and the anything beyond them is 
-monster and NPC sprites, but since the advanced classes rolled in, they got the 
-ID numbers on the other end of the number pool where monster sprites float.
+The limit is the maximum number of people allowed to enter the chat room. If the 
+optional event and trigger parameters are given, the event label 
+("<NPC object name>::<label name>") will be invoked as if with a 'doevent' upon 
+the number of people in the chat room reaching the given triggering amount.
 
-As a result it is currently impossible to call this command with a valid view 
-id. It will do nothing whatsoever if the view ID is below 4047. Getting it to 
-run will actually just crash the client.
+It's funny, but for compatibility with jAthena, you can swap the event label and 
+the trigger parameters, and it will still work.
 
-It could be a real gem if it can be gotten to actually do what it's supposed to 
-do, but this will only happen in a later SVN revision.
+// The NPC will just show a box above its head that says "Hello World", clicking 
+// it will do nothing, since the limit is zero.
+    waitingroom "Hello World",0;
 
----------------------------------------
+// The NPC will have a box above its head, it will say "Disco - Waiting Room" 
+// and will have 8 waiting slots. Clicking this will enter the chat room, where 
+// the player will be able to wait until 8 people accumulate. Once this happens, 
+// it will cause the NPC "Bouncer" run the label "OnStart"
 
-*misceffect <effect number>;
+    waitingroom "Disco - Waiting Room",8,"Bouncer::OnStart",8;
 
-This command, if run from an NPC object that has a sprite, will call up a 
-specified effect number, centered on the NPC sprite. If the running code does 
-not have an object ID (a 'floating' npc) or is not running from an NPC object at 
-all (an item script) the effect will be centered on the character who's RID got 
-attached to the script, if any. For usable item scripts, this command will 
-create an effect centered on the player using the item.
+Creating a waiting room does not stop the execution of the script and it will 
+continue to the next line.
 
-A full list of known effects is found in 'doc/effect_list.txt'. The list of 
-those that actually work may differ greatly between client versions.
+For more examples see the 2-1 and 2-2 job quest scripts which make extensive use 
+of waiting rooms.
 
 ---------------------------------------
 
-*soundeffect "<effect filename>",<number>
-*soundeffectall "<effect filename>",<number>
-
-These two commands will play a sound effect to either the invoking character 
-only 'soundeffect' or everyone around ('soundeffectall'). If the running code 
-does not have an object ID (a 'floating' npc) or is not running from an NPC 
-object at all (an item script) the sound will be centered on the character who's 
-RID got attached to the script, if any. If it does, it will be centered on that 
-object. (an NPC sprite)
-
-Effect filename is the filename of the wav in GRF. It must have an extension.
+*delwaitingroom {"<NPC object name"};
 
-It's not quite certain what the number actually does, it is sent to the client 
-directly, probably it determines which directory of the GRF the effect is played 
-from - the sound effect type. It's certain that giving 0 for the number will 
-play sound files from 'data/wav', but where the other numbers will read from is 
-unclear.
+This command will delete a waiting room. If no parameter is given, it will 
+delete a waiting room attached to the NPC object running this command, if it is, 
+it will delete a waiting room owned by another NPC object. This is the only way 
+to get rid of a waiting room, nothing else will cause it to disappear.
 
-You can add your own effects this way, naturally.
+It's not clear what happens to a waiting room if the NPC is disabled with 
+'disablenpc', by the way.
 
 ---------------------------------------
 
-*mapwarp "<from map>","<to map>",<x>,<y>;
+*enablewaitingroomevent {"<NPC object name>"};
+*disablewaitingroomevent {"<NPC object name>"};
 
-This command will collect all characters located on the From map and warp them 
-wholesale to the same point on the To map, or randomly distribute them there if 
-the coordinates are zero. "Random" is understood as a special To map name and 
-will mean randomly shuffling everyone on the same map.
+This will enable and disable triggering the waiting room event (see 
+'waitingroom') respectively. Optionally giving an NPC object name will do that 
+for a specified NPC object. The chat room will not disappear when triggering is 
+disabled and enabled in this manner and players will not be kicked out of it.
+Enabling a chat room event will also cause it to immediately check whether the 
+number of users in it exceeded the trigger amount and trigger the event 
+accordingly.
+
+Normally, whenever a waiting room was created to make sure that only one 
+character is, for example, trying to pass a job quest trial, and no other 
+characters are present in the room to mess up the script.
 
 ---------------------------------------
 
-*mobcount("<map name>","<event label>")
+*getwaitingroomstate(<information type>{,"<NPC object name>"})
 
-This function will count all the monsters on the specified map that have a given 
-event label and return the number or 0 if it can't find any. Naturally, only 
-monsters spawned with 'monster' and 'areamonster' script commands can be like 
-this.
+This function will return information about the wating room state for the 
+attached waiting room or for a waiting room attached to the specified NPC if 
+any.
 
-However, apparently, if you pass this function an empty string for the event 
-label, it should return the total count of normal permanently respawning 
-monsters instead. With the current dynamic mobs system, where mobs are not kept 
-in memory for maps with no actual people playing on them, this will return a 0 
-for any such map.
+The valid information types are:
+
+ 0  - Number of users currently chatting.
+ 1  - Maximum number of users allowed.
+ 2  - Will return 1 if the waiting room has a trigger set.
+      0 otherwise.
+ 3  - Will return 1 if the waiting room is currently disabled.
+      0 otherwise.
+ 4  - The Title of the waiting room (string)
+ 5  - Password of the waiting room, if any. Pointless, since there is no way to 
+      set a password on a waiting room right now.
+ 16 - Event name of the waiting room (string)
+ 32 - Whether or not the waiting room is full.
+ 33 - Whether the amount of users in the waiting room is higher than the trigger 
+      number.
 
 ---------------------------------------
 
-*strmobinfo(<type>,<monster id>);
+*warpwaitingpc "<map name>",<x>,<y>{,<number of people>};
 
-This function will return information about a monster record in the database, as 
-per 'db/mob_db.txt'. Type is the kind of information returned. Valid types are:
+This command will warp the amount of characters equal to the trigger number of 
+the waiting room chat attached to the NPC object running this command to the 
+specified map and coordinates, kicking them out of the chat. Those waiting the 
+longest will get warped first. It can also do a random warp on the same map 
+("Random" instead of map name) and warp to the save point ("SavePoint").
 
- 1 - 'english name' field in the database, a string.
- 2 - 'japanese name' field in the database, a string.
-     All other returned values are numbers:
- 3 - Level.
- 4 - Maximum HP.
- 5 - Maximum SP.
- 6 - Experience reward.
- 7 - Job experience reward.
+The list of characters to warp is taken from the list of the chat room members. 
+Those not in the chat room will not be considered even if they are talking to 
+the NPC in question. If the number of people is given, exactly this much people 
+will be warped.
 
----------------------------------------
+This command can also keep track of who just got warped. It does this by setting 
+special variables:
 
-*guardian "<map name>",<x>,<y>,"<name to show>",<mob id>,<amount>{,"<event label>"}{,<guardian index>};
+$@warpwaitingpc[] is an array containing the character id numbers of the 
+                  characters who were just warped.
+$@warpwaitingpcnum contains the number of the character it just warped.
 
-This command is roughly equivalent to 'monster', but is meant to be used with 
-castle guardian monsters and will only work with them. It will set the guardian 
-characteristics up according to the castle's investment values and otherwise 
-set the things up that only castle guardians need.
+See also 'getpartymember' for advice on what to do with those variables.
+
+The obvious way of using this effectively would be to set up a waiting room for 
+two characters to be warped onto a random PVP map for a one-on-one duel, for 
+example.
 
 ---------------------------------------
 
-*guardianinfo(<guardian number>)
+*waitingroomkickall {"<NPC object name>"};
 
-This function will return the current hit point value for the specified guardian 
-number, if such guardian is currently installed. This function will only work if 
-the invoking character is on a castle map, and will refer only to the guardians 
-of that castle, regardless of anything else, i.e. whether the character is a 
-member of the guild owning the castle, etc, etc.
-If no guardian is installed in this slot, the function will return -1.
+This command would kick everybody out of a specified waiting room chat. IF it 
+was properly linked into the script interpreter which it isn't, even though the 
+code for it is in place. Expect this to become available in upcoming SVN 
+releases.
 
 ---------------------------------------
 
-* The Pet AI commands
+*setmapflagnosave "<map name>","<alternate map name>",<x>,<y>;
 
-These commands will only work if the invoking character has a pet, and are meant 
-to be executed from pet scripts. They will modify the pet AI decision-making for 
-the current pet of the invoking character, and will NOT have any independent 
-effect by themselves, which is why only one of them each may be in effect at any 
-time for a specific pet. A pet may have 'petloot', 'petskillbonus', 
-'petskillattack' OR 'petpetskillattack2' and 'petskillsupport' OR 'petheal' at 
-the same time. 'petheal' is deprecated and is no longer used in the default pet 
-scripts. 
+This command sets the 'nosave' flag for the specified map and also gives an 
+alternate respawn-upon-relogin point.
 
-*petskillbonus <bonus type>,<value>,<duration>,<delay>;
+It does not make a map impossible to make a savepoint on as you would normally 
+think, 'savepoint' will still work. It will, however, make the specified map 
+kick the reconnecting players off to the alternate map given to the coordinates 
+ specified.
 
-This command will make the pet give a bonus to the owner's stat (bonus type -
-bInt,bVit,bDex,bAgi,bLuk,bStr,bSpeedRate - for a full list, see the values 
-starting with 'b' in 'db/const.txt')
+---------------------------------------
 
-*petrecovery <status type>,<delay>;
+*setmapflag "<map name>",<flag>;
 
-This command will make the pet cure a specified status condition. The curing 
-actions will occur once every Delay seconds. For a full list of status 
-conditions that can be cured, see the list of 'SC_' status condition constants 
-in 'db/const.txt'
+This command marks a specified map with a map flag given. Map flags alter the 
+behavior of the map, you can see the list of the available ones in 
+'db/const.txt' under 'mf_'.
 
-*petloot <max items>;
+The map flags alter the behavior of the map regarding teleporting (mf_nomemo, 
+mf_noteleport, mf_nowarp, mf_nogo) storing location when disconnected 
+(mf_nosave), dead branch usage (mf_nobranch), penalties upon death 
+(mf_nopenalty, mf_nozenypenalty), PVP behavior (mf_pvp, mf_pvp_noparty, 
+mf_pvp_noguild, mf_nopvp), WoE behavior (mf_gvg,mf_gvg_noparty), ability to use 
+skills or open up trade deals (mf_notrade, mf_novending, mf_noskill, mf_noicewall),
+current weather effects (mf_snow, mf_fog, mf_sakura, mf_leaves, mf_rain, mf_clouds, 
+mf_fireworks) and whether day/night will be in effect on this map (mf_indoors).
 
-This command will turn on pet looting, with a maximum number of items to loot 
-specified. Pet will store items and return them when the maximum is reached or 
-when pet performance is activated.
+---------------------------------------
 
-*petskillsupport <skill id>,<skill level>,<delay>,<percent hp>,<percent sp>;
-*petheal <level>,<delay>,<percent hp>,<percent sp>;
+*setbattleflag "<battle flag>",<value>;
+*getbattleflag "<battle flag>";
 
-This will make the pet use a specified support skill on the owner whenever the 
-HP and SP are below the given percent values, with a specified delay time 
-between activations. The skill numbers are as per 'db/skill_db.txt'.
-'petheal' works the same as 'petskillsupport' but has the skill ID hardcoded to 
-28 (Heal). This command is deprecated.
-It's not quite certain who's stats will be used for the skills cast, the 
-character's or the pets. Probably, Skotlex can answer that question.
+Sets or gets the value of the given battle flag.
+Battle flags are the flags found in the battle/*.conf files and is also used in Lupus' variable rates script.
 
-*petskillattack <skill id>,<skill level>,<rate>,<bonusrate>;
-*petskillattack2 <skill id>,<damage>,<number of attacks>,<rate>,<bonusrate>;
+Example(s):
 
-These two commands will make the pet cast an attack skill on the enemy the pet's 
-owner is currently fighting. Skill IDs and levels are as per 'petskillsupport'. 
-'petskillattack2' will make the pet cast the skill with a fixed amount of damage 
-inflicted and the specified number of attacks.
+//will set the base experience rate to 20x (2000%)
+	setBattleFlag "base_exp_rate",2000;
+	
+//will return the value of the base experience rate (when used after the above example, it would return 2000).
+	getBattleFlag "base_exp_rate";
 
-All commands with delays and durations will only make the behavior active for 
-the specified duration of seconds, with a delay of the specified number of 
-seconds between activations. Rates are a chance of the effect occuring and are 
-given in percent. 'bonusrate' is added to the normal rate if the pet intimacy is 
-at the maximum possible.
+---------------------------------------
 
-The behavior modified with the abovementioned commands will only be exibited if 
-the pet is loyal and appropriate configuration options are set in 
-'battle_athena.conf'.
+*removemapflag "<map name>",<flag>;
 
-Pet scripts in the database normally run whenever a pet of that type hatches 
-from the egg. Other commands usable in item scripts (see 'bonus') will also 
-happily run from pet scripts. Apparently, the pet-specific commands will also 
-work in NPC scripts and modify the behavior of the current pet up until the pet 
-is hatched again. (Which will also occur when the character is logged in again 
-with the pet still out of the egg.) It is not certain for how long the effect of 
-such command running from an NPC script will eventually persist, but apparently, 
-it is possible to usefully employ them in usable item scripts to create pet 
-buffing items.
+This command removes a mapflag from a specified map. See 'setmapflag'.
 
-Nobody tried this before, so you're essentially on your own here.
+---------------------------------------
 
---------------------------------------
+*warpportal <x>,<y>,"<mapname>",<x>,<y>;
 
-*skilleffect <skill id>,<number>;
+Creates a warp Portal as if a acolyte class character did it.
+The first x and y is the place of the warp portal on the map where the NPC is on
+The mapname and second x and y is the target area of the warp portal.
 
-This command will display the visual and sound effects of a specified skill (see 
-'db/skill_db.txt' for a full list of skills) on the invoking character's sprite. 
-Nothing but the special effects and animation will happen. If the skill's normal 
-effect displays a floating number, the number given will float up.
+Example(s):
 
-    // This will heal the character with 2000 hp, buff with 
-    // Bless 10 and Increase AGI 5, and display appropriate
-    // effects.
-    mes "Blessed be!";
-    skilleffect 28,2000;
-    heal 2000,0;
-    skilleffect 34,0;
-    // That's bless 10.
-    sc_start 10,240000,10;
-    skilleffect 29,0;
-    // That's agi 5
-    sc_start 12,140000,5;
+//Will create a warp portal on the NPC's map at 150,150 leading to prontera, coords 150,180.
+	warpPortal 150,150,"prontera.gat",150,180;
 
 ---------------------------------------
 
-*npcskilleffect <skill id>,<number>,<x>,<y>;
+*mapwarp "<from map>","<to map>",<x>,<y>;
 
-This command behaves identically to 'skilleffect', however, the effect will not 
-be centered on the invoking character's sprite, nor on the NPC sprite, if any, 
-but will be centered at map coordinates given on the same map as the invoking 
-character.
+This command will collect all characters located on the From map and warp them 
+wholesale to the same point on the To map, or randomly distribute them there if 
+the coordinates are zero. "Random" is understood as a special To map name and 
+will mean randomly shuffling everyone on the same map.
 
 ---------------------------------------
-
-*specialeffect <effect number>;
-
-This command will display special effect with the given number, centered on the 
-specified NPCs coordinates, if any. For a full list of special effect numbers 
-known see 'doc/effect_list.txt'. Some effect numbers are known not to work in 
-some client releases. (Notably, rain is absent from any client executables 
-released after April 2005.)
-
+\\
+5,2.- Guild-related Commands
+\\
 ---------------------------------------
 
-*specialeffect2 <effect number>;
+*maprespawnguildid "<map name>",<guild id>,<flag>;
 
-This command behaves identically to the 'specialeffect', but the effect will be 
-centered on the invoking character's sprite.
+This command goes through the specified map and for each player and monster 
+found there does stuff.
 
----------------------------------------
+Flag is a bitmask (add up numbers to get effects you want)
+ 1 - warp all guild members to their savepoints.
+ 2 - warp all non-guild members to their savepoints.
+ 4 - remove all monsters which are not guardian or emperium.
 
-*nude; 
+Flag 7 will, therefore, mean 'wipe all mobs but guardians and the emperium and 
+kick all characters out', which is what the official scripts do upon castle 
+surrender. Upon start of WoE, the scripts do 2 (warp all intruiders out).
 
-This command will unequip anything equipped on the invoking character.
+Characters not belonging to any guild will warp out regardless of the flag setting.
 
-It is not required to do this when changing jobs since 'jobchange' will unequip 
-everything not equippable by the new job class anyway.
+For examples, check the WoE scripts in the distribution.
 
 ---------------------------------------
 
-*atcommand "<command line>";
-
-This command will run the given command line exactly as if it was typed in from 
-the keyboard by the player connected to the invoking character, and that 
-character belonged to an account which had GM level 99.
+*agitstart;
+*agitend;
 
-    // This will ask the invoker for a character name and then use the '@nuke'
-    // GM command on them, killing them mercilessly.
-    input @player$;
-    gmcommand "@nuke "+@player$
+These two commands will start and end War of Emperium.
 
-This command has a lot of good uses, I am sure you can have some fun with this 
-one.
+This is a bit more complex than it sounds, since the commands themselves won't 
+actually do anything interesting, except causing all 'OnAgitStart:' and 
+'OnAgitEnd:' events to run everywhere, respectively. They are used as 
+simple triggers to run a lot of complex scripts all across the server, and they, 
+in turn, are triggered by clock with an 'OnClock<time>:' time-triggering label.
 
 ---------------------------------------
 
-*message "<character name>","<message>";
+*gvgon "<map name>";
+*gvgoff "<map name>";
 
-That command will send a message to the chat window of the character specified 
-by name. The text will also appear above the head of that character. It will not 
-be seen by anyone else.
+These commands will turn GVG mode for the specified maps on and off, setting up 
+appropriate map flags. In GVG mode, maps behave as if during the time of WoE, 
+even though WoE itself may or may not actually be in effect. 
 
 ---------------------------------------
 
-*npctalk "<message>";
-
-This command will display a message to the surrounding area as if the NPC object 
-running it was a player talking - that is, above their head and in the chat 
-window. The display name of the NPC will get appended in front of the message to 
-complete the effect.
+*flagemblem <guild id>;
 
-    // This will make everyone in the area see the NPC greet the character
-    // who just invoked it.
-    npctalk "Hello "+strcharinfo(0)+" how are you";
+This command only works when run by the NPC objects which have sprite id 722, 
+which is a 3D guild flag sprite. If it isn't, the data will change, but nothing 
+will be seen by anyone. If it is invoked in that manner, the emblem of the 
+specified guild will appear on the flag, though, if any players are watching it 
+at this moment, they will not see the emblem change until they move out of sight 
+of the flag and return.
 
----------------------------------------
+This is commonly used in official guildwar scripts with a function call which 
+returns a guild id:
 
-*hasitems(0)
+// This will change the emblem on the flag to that of the guild that owns
+// "guildcastle"
 
-This function will return 1 if the invoking character has anything at all in 
-their inventory and 0 if they do not. Even though the argument is not used for 
-anything, it is required.
+    flagemblem GetCastleData("guildcastle.gat",1); 
 
 ---------------------------------------
 
-*getlook(<type>)
-
-This function will return the number for the currentcharacter look value 
-specified by type. See 'setlook' for valid look types.
+*guardian "<map name>",<x>,<y>,"<name to show>",<mob id>,<amount>{,"<event label>"}{,<guardian index>};
 
-This can be used to make a certain script behave differently for characters 
-dressed in black. :)
+This command is roughly equivalent to 'monster', but is meant to be used with 
+castle guardian monsters and will only work with them. It will set the guardian 
+characteristics up according to the castle's investment values and otherwise 
+set the things up that only castle guardians need.
 
 ---------------------------------------
 
-*getsavepoint(<information type>)
-
-This function will return information about the invoking character's save point. 
-You can use it to let a character swap between several recorded savepoints. 
-Available information types are:
+*guardianinfo(<guardian number>)
 
- 0 - Map name (a string)
- 1 - X coordinate
- 2 - Y coordinate
+This function will return the current hit point value for the specified guardian 
+number, if such guardian is currently installed. This function will only work if 
+the invoking character is on a castle map, and will refer only to the guardians 
+of that castle, regardless of anything else, i.e. whether the character is a 
+member of the guild owning the castle, etc, etc.
+If no guardian is installed in this slot, the function will return -1.
 
+---------------------------------------
+//
+5,2.- End of guild-related commands
+//
 ---------------------------------------
 
 *npcspeed <speed value>;
@@ -4654,75 +5430,34 @@ sprite based sprite id in 'db/mob-avail.txt' with this.
 
 ---------------------------------------
 
-*getmapxy("<variable for map name>",<variable for x>,<variable for y>,<type>{,"<search string>"})
-
-This function will locate a character object, NPC object or pet's coordinates 
-and place their coordinates into the variables specified when calling it. It 
-will return 0 if the search was successful, and -1 if the parameters given were 
-not variables or the search was not successful.
-
-Type is the type of object to search for:
-
-  0 - Character object
-  1 - NPC object
-  2 - Pet object
-  3 - Monster object.
-  
-While 3 is meant to look for a monster object, no searching will be done if you 
-specify type 3, and the function will always return -1.
-
-The search string is optional. If it is not specified, the location of the 
-invoking character will always be returned for types 0 and 2, the location of 
-the NPC running this function for type 1.
-If a search string is specified, for types 0 and 1, the character or NPC with 
-the specified name will be located. If type is 3, the search will locate the 
-current pet of the character who's name is given in the search string, it will 
-NOT locate a pet by name.
+*movenpc <NPC name>,x,y;
 
-What a mess. Example, a working and tested one now:
+This command looks like the NPCWalkToxy function,but is a little different.
 
-    prontera.gat,164,301,3%TAB%script%TAB%Meh%TAB%730,{
-        mes "My name is Meh. I'm here so that Nyah can find me.";
-        close;
-    }
+While NPCWalkToXY just makes the NPC 'walk' to the coordinates given 
+(which sometimes gives problems if the path isn't a straight line without objects),
+this command just moves the NPC. It basically warps out and in on the current and given spot.
 
-    prontera.gat,164,299,3%TAB%script%TAB%Nyah%TAB%730,{
-        mes "My name is Nyah.";
-        mes "I will now search for Meh all across the world!";
-        if (getmapxy(@mapname$,@mapx,@mapy,1,"Meh")!=0) goto Notfound;
-        mes "And I found him on map "+@mapname$+" at X:"+@mapx+" Y:"+@mapy+" !";
-        close;
-    Notfound:
-        mes "I can't seem to find Meh anywhere!";
-        close;
-   }
-   
-Notice that NPC objects disabled with 'disablenpc' will still be located.
+Example(s):
 
+//This will move Bugga from it's current position to the coords 100,20 (if those coords are walkable (legit)).
+	moveNPC "Bugga",100,20;
+	
 ---------------------------------------
 
-*guildgetexp <amount>;
-
-This will give the specified amount of guild experience points to the guild the 
-invoking character belongs to. It will silently fail if they do not belong to 
-any guild.
-
+=====================
+|6.- Other commands.|
+=====================
 ---------------------------------------
 
-*skilluseid <skill>,<level>;
-*doskill <skill>,<level>;
-*skillusepos <skill>,<level>,<x>,<y>;
-
-These commands will cause the invoking character to use a specified skill at the 
-specified level, as if they had that skill, with their current level and stats. 
-If the skill involves targeting a character, no targeting pointer will come up -
-the invoking character will automatically be the skill target.
+*debugmes "<message>";
 
-'doskill' is an alias for 'skilluseid'.
+This command will send the message to the server console (map-server window). It 
+will not be displayed anywhere else.
 
-'skillusepos' will specify a target map square for the skill to be used. If that 
-skill is an area effect skill, it will be centered at the square specified. It 
-will not work if the skill is supposed to be targeted on character or monster.
+    debugmes strcharinfo(0)+" has just done this that and the other";
+    // You would see in the map-server window "NAME has just done this that and 
+    // the other"
 
 ---------------------------------------
 
@@ -4738,83 +5473,260 @@ If logs are not enabled, nothing will happen.
 
 ---------------------------------------
 
-*summon "<monster name>",<mob id>{,"<event label>"};
+*globalmes "<message>"{,"<NPC name>"};
+
+This command will send a message to the chat window of all currently connected 
+characters.
+
+If NPC name is specified, the message will be sent as if the sender would be
+the npc with the said name.
+
+---------------------------------------
+
+*rand(<number>{,<number>});
+
+This function returns a number, randomly positioned between 0 and the number you 
+specify (if you only specify one) and the two numbers you specify if you give it 
+two.
+
+rand(10) would result in 0,1,2,3,4,5,6,7,8 or 9
+
+rand(2,10) would result in 2,3,4,5,6,7,8,9 or 10
+
+---------------------------------------
+
+*viewpoint <action>,<x>,<y>,<point number>,<color>;
+
+This command will mark places on the mini map in the client connected to the 
+invoking character. It uses the normal X and Y coordinates from the main map. 
+The colors of the marks are defined using a hexidecimal number, same as the ones 
+used to color text in 'mes' output, but are written as hexadecimal numbers in C. 
+(They look like 0x<six numbers>.)
+
+Action is what you want to do with a point, 1 will set it, while 2 will clear 
+it. Point number is the number of the point - you can have several. If more than 
+one point is drawn at the same coordinates, they will cycle, which can be used 
+to create flashing marks.
+
+    // This command will show a mark at coordinates X 30 Y 40, is mark number 1, 
+    // and will be red.
+    
+    viewpoint 1,30,40,1,0xFF0000;
+
+This will create three points:
+
+    viewpoint 1,30,40,1,0xFF0000;
+    viewpoint 1,35,45,2,0xFF0000;
+    viewpoint 1,40,50,3,0xFF0000;
+
+And this is how you remove them:
+
+    viewpoint 2,30,40,1,0xFF0000;
+    viewpoint 2,35,45,2,0xFF0000;
+    viewpoint 2,40,50,3,0xFF0000;
+    
+The client determines what it does with the points entirely, the server keeps no 
+memory of where the points are set whatsoever.
+
+---------------------------------------
+
+*cutin "<filename with no extension>",<position>;
+
+This command will display a picture stored in the GRF file in the client for the 
+player. 
+
+The files are taken from '\data\texture\A_AŁAIŹI’„AI«§\illust' directory in the 
+GRF file. The filename must be given with no extension, '.bmp' is added by the 
+client itself and you can't have any other picture format displayed as a cutin. 
+The biggest one that comes with the client is 400x503 pixels, and the smallest 
+is 303x493 pixels, it is not known how big a picture has to be before the client 
+goes insane. Bright magenta (color FF00FF) is considered to be transparent in 
+these pictures. You can easily add and alter them, but how to do this is outside 
+of the scope of this document.
+
+The position determines just where on screen the picture will appear:
+  0 - bottom left corner
+  1 - bottom middle
+  2 - bottom right corner
+  3 - middle of screen in a movable window with an empty title bar.
+  4 - middle of screen without the window header, but still movable.
+  255 - will remove the cutin previously displayed.
+ 
+Giving an empty string for the filename and 255 for the position will remove all 
+cutin pictures. Any other position value will not cause a script error but will 
+cause the player's client to curl up and die. Only one cutin may be on screen at 
+any given time, any new cutins will replace it.
+
+    // This will display the picture of the 7th kafra,
+    // the one in orange and the mini-skirt :P
+    cutin "kafra_7",2;
+
+    // This will remove the displayed picture.
+    cutin "Kafra_7",255;
+
+    // This will remove all pictures displayed.
+    cutin "",255;
+
+The client comes with those cutin pictures preinstalled which you can use:
+
+mets_alpha  - This is a old fat man, holding a pipe, also with a pocket watch 
+              and cane
+pay_soldier - Wanna take a wild guess, thats right, the Soldiers that appear in 
+              Payon :D
+prt_soldier - Obvious
+ein_soldier - This guy looks cool, you've got to see him ;) This picture is for 
+              the new Einbroch guards
+moc_soldier - Obvious
+gef_soldier - Obvious
+katsua01    - It is not certain who this girl is (There is no sprite coming with 
+katsua02    - the client that seems to match very well) but she is believed to 
+katsua03    - be an NPC in official Comodo. The three pictures give different 
+              facial expressions.
+kafra_01    - Obvious
+kafra_02    - Obvious
+kafra_03    - Obvious
+kafra_04    - Obvious
+kafra_05    - Obvious
+kafra_06    - Obvious
+kafra_07    - Do I need to mention this one again ;)
+
+---------------------------------------
+
+*cutincard <item id>;
+
+This command will display a card picture as a cutin on the client connected to 
+the invoking character, with position number 4 (middle of screen, movable, but 
+no title bar). See 'cutin'. To remove this cutin, use the regular 'cutin' 
+command. Unlike the 'cutin' command, it will not take a filename, but will 
+instead take an item ID. It will then refer to the text file listing card images 
+which is normally found within your server's copy of the GRF file to find the 
+real (korean) filename.
+
+If your server doesn't have that text file in that GRF or can't read it, it 
+probably won't work.
+
+---------------------------------------
+
+*pet <pet id>;
+
+This command is used in all the item scripts for taming items. Running this 
+command will make the pet catching cursor appear on the client connected to the 
+invoking character, usable on the monsters with the specified pet ID number. It 
+will still work outside an item script.
+
+A full list of pet IDs can be found inside 'db/pet_db.txt'
+
+---------------------------------------
+
+*emotion <emotion number>{, target};
+
+This command makes an object display an emoticon sprite above their own as 
+if they were doing that emotion. For a full list of emotion numbers, 
+see 'db/const.txt' under 'e_'. The inobvious ones are 'e_what' (a question mark) 
+and 'e_gasp' (the exclamation mark).
+
+The optional target parameter specifies who will get the emotion on top of
+their head. If 0 (the default if omitted), the NPC in current use will show
+the emotion, if 1, the player that is running the script will display it.
+
+---------------------------------------
+
+*misceffect <effect number>;
+
+This command, if run from an NPC object that has a sprite, will call up a 
+specified effect number, centered on the NPC sprite. If the running code does 
+not have an object ID (a 'floating' npc) or is not running from an NPC object at 
+all (an item script) the effect will be centered on the character who's RID got 
+attached to the script, if any. For usable item scripts, this command will 
+create an effect centered on the player using the item.
+
+A full list of known effects is found in 'doc/effect_list.txt'. The list of 
+those that actually work may differ greatly between client versions.
+
+---------------------------------------
+
+*soundeffect "<effect filename>",<number>
+*soundeffectall "<effect filename>",<number>
+
+These two commands will play a sound effect to either the invoking character 
+only 'soundeffect' or everyone around ('soundeffectall'). If the running code 
+does not have an object ID (a 'floating' npc) or is not running from an NPC 
+object at all (an item script) the sound will be centered on the character who's 
+RID got attached to the script, if any. If it does, it will be centered on that 
+object. (an NPC sprite)
+
+Effect filename is the filename of the wav in GRF. It must have an extension.
+
+It's not quite certain what the number actually does, it is sent to the client 
+directly, probably it determines which directory of the GRF the effect is played 
+from - the sound effect type. It's certain that giving 0 for the number will 
+play sound files from 'data/wav', but where the other numbers will read from is 
+unclear.
 
-This command will summon a monster. (see also 'monster') Unlike monsters spawned 
-with other commands, this one will set up the monster to fight to protect the 
-invoking character. Monster name and mob id obey the same rules as the one given 
-at the beginning of this document for permanent monster spawns with the 
-exceptions mentioned when describing 'monster' command.
+You can add your own effects this way, naturally.
 
-The effect for the skill 'Call Homonuculus' will be displayed centered on the 
-invoking character.
+---------------------------------------
 
-If an event label is given, upon the monster being killed, the event label will 
-run as if by 'donpcevent'.
+*pvpon "<map name>";
+*pvpoff "<map name>";
 
-    // Will summon a dead branch-style monster to fight for the character.
-    summon "--ja--",-1;
+These commands will turn PVP mode for the specified maps on and off. Beside 
+setting the flags referred to in 'setmapflag', 'pvpon' will also create a PVP 
+timer and ranking as will @pvpon GM command do.
 
 ---------------------------------------
 
-*isnight()
-*isday()
+*atcommand "<command line>";
 
-These functions will return 1 or 0 depending on whether the server is in night 
-mode or day mode. 'isnight' returns 1 if it's night and 0 if it isn't, 'isday' 
-the other way around. They can be used interchangeably, pick the one you like 
-more:
+This command will run the given command line exactly as if it was typed in from 
+the keyboard by the player connected to the invoking character, and that 
+character belonged to an account which had GM level 99.
 
-    // These two are equivalent:
-    if (isday()) mes "I only prowl in the night.";
-    if (isnight()!=1) mes "I only prowl in the night.";
+    // This will ask the invoker for a character name and then use the '@nuke'
+    // GM command on them, killing them mercilessly.
+    input @player$;
+    atcommand "@nuke "+@player$;
 
----------------------------------------
+This command has a lot of good uses, I am sure you can have some fun with this 
+one.
 
-*isequipped(<id>{,<id>{,<id>{,<id>}}})
+---------------------------------------
 
-This function will return 1 if the invoking character has all of the item 
-IDs given equipped (if card IDs are passed, then it checks if the cards are
-inserted into slots in the equipment they are currently wearing). Theorically
-there is no limit to the number of items that may be tested for at the same time. 
-If even one of the items given is not equipped, 0 will be returned.
+*charcommand <command>;
 
-    // (Poring,Santa Poring,Poporing,Marin)
-    if (isequipped(4001,4005,4033,4196)) mes "Wow! You're wearing a full complement of possible poring cards!";
-    // (Poring)
-    if (isequipped(4001)) mes "A poring card is useful, don't you think?";
-    
-The function was meant for item scripts to support the cards released by Gravity 
-in February 2005, but it will work just fine in normal NPC scripts.
+NOTE: This command is changed a bit on newer trunk versions, 
+scroll down a bit for the new version!
 
----------------------------------------
+On older trunk versions and stable:
 
-*isequippedcnt(<card id>{,<card id>{,<card id>{,<card id>}}})
+command is the name of the current character (strcharinfo(0))
+followed by ':' and the command and it's parameters.
 
-This function is similar to 'isequipped', but instead of 1 or 0, it will return 
-the number of cards in the list given that were found on the invoking character.
+Example(s):
 
-    if (isequippedcnt(4001,4005,4033,4196)=4) mes "Finally got all four poring cards?";
+//Will be executed as if a lvl 99 GM done the #option command.
+	charCommand strcharinfo(0)+":#option 0 0 0 Roy";
 
----------------------------------------
+Newer Trunk version:
 
-*cardscnt()
+The big change is that the character name is no longer needed.
+This also enabled the commands to run without a player attached (according to Lance).
 
-This function will return the number of cards inserted into the weapon currently 
-equipped on the invoking character.
-While this function was meant for item scripts, it will work outside them:
+Example(s):
 
-    if (cardscnt()==4) mes "So you've stuck four cards into that weapon, think you're cool now?";
+//this would do the same as above, but now doesn't need a player attached by default.
+	charCommand "#option 0 0 0 Roy";
 
 ---------------------------------------
 
-*getrefine()
+*unitskilluseid <GID>,<skill id>,<skill lvl>;
+*unitskillusepos <GID>,<skill id>,<skill lvl>,<x>,<y>;
 
-This function will return the number of plusses the weapon currently equipped on 
-the invoking character has been refined for.
-While this function was meant for item scripts, it will work outside them:
+This is the replacement of the older commands, these use the same values for
+GID as the other unit* commands (See 'GID').
 
-    if (getrefine()==10) mes "Wow. That's a murder weapon.";
+Skill ID is the ID of the skill, skill level is the level of the skill.
+For the position, the x and y are given in the unitSkillUsePos.
 
 ---------------------------------------
 
@@ -4858,109 +5770,6 @@ OnInit:
 
 ---------------------------------------
 
-*getusersname;
-
-This command will give the invoking character a list of names of the connected 
-characters (including themselves) into an NPC script message window (see 'mes') 
-paging it by 10 names as if with the 'next' command.
-
-You need to put a 'close' after that yourself.
-
----------------------------------------
-
-*dispbottom "<message>";
-
-This command will send the given message into the invoking character's chat 
-window.
-
----------------------------------------
-
-*recovery;
-
-This command will revive and restore full HP and SP to all characters currently 
-connected to the server.
-
----------------------------------------
-
-*getpetinfo(<type>)
-
-This function will return pet information for the pet the invoking character 
-currently has active. Valid types are:
-
- 0 - Unique pet ID number as stored by the char server and distinguishing it 
-     from all other pets the characters actually have. This value is currently 
-     useless, at most you can use it to tell pets apart reliably.
- 1 - Pet ID number as per 'db/pet_db.txt' - will tell you what kind of a pet it 
-     is.
- 2 - Pet name. Will return "null" if there's no pet. 
- 3 - Pet friendly level (intimacy score). 1000 is full loyalty.
- 4 - Pet hungry level. 100 is completely full.
-
----------------------------------------
-
-*checkequipedcard(<card id>)
-
-This function will return 1 if the card specified by it's item ID number is 
-inserted into any equipment they have in their inventory, currently equipped or 
-not.
-
----------------------------------------
-
-*globalmes "message";
-
-This command will send a message to the chat window of all currently connected 
-characters.
-
----------------------------------------
-
-*jump_zero (<condition>),<label>;
-
-This command works kinda like an 'if'+'goto' combination in one go. (See 'if'). 
-If the condition is false (equal to zero) this command will immediately jump to 
-the specified label like in 'goto'.
-
-While 'if' is more generally useful, for some cases this could be an 
-optimisation.
-
----------------------------------------
-
-*select("<option>"{,"<option>"..."<option>"})
-
-This function is a handy replacement for 'menu' for some specific cases where 
-you don't want a complex label structure - like, for example, asking simple yes-
-no questions. It will return the number of menu option picked, starting with 1. 
-Like 'menu', it will also set the variable @menu to contain the option the user 
-picked.
-
-    if (select("Yes","No")==1) mes "You said yes, I know.";
-
-And like 'menu', this command has a problem with empty strings - if some of the 
-option strings given to it are empty, you won't be able to tell which one the 
-user really picked. The number it returns will only make sense if all the empty 
-strings are last in the list of options.
-
----------------------------------------
-
-*getmapmobs("<map name>")
-
-This function will return the total count of monsters currently located on the 
-specified map. If the map name is given as "this", the map the invoking 
-character is on will be used. If the map is not found, or the invoker is not a 
-character while the map is "this", it will return -1.
-
----------------------------------------
-
-*unequip <equipment slot>;
-
-This command will unequip whatever is currently equipped in the invoking 
-character's specified equipment slot. For a full list of possible equipment 
-slots see 'getequipid'.
-
-If an item occupies several equipment slots, it will get unequipped from all of 
-them. (Which is a good thing.)
-
----------------------------------------
-
 *defpattern <set number>,"<regular expression pattern>","<event label>";
 *activatepset <set number>;
 *deactivatepset <set number>;
@@ -4993,101 +5802,17 @@ set number in this case will deactivate all pattern sets defined.
 pattern set in it's place.
 
 Using regular expressions is high wizardry. But with this high wizardry comes 
-unparallelled power of text manipulation. For an explanation of what a regular 
-expression pattern is, see a few web pages:
-
-http://www.regular-expressions.info/
-http://www.weitz.de/regex-coach/
-
-For an example of this in use, see 'npc\custom\eliza.txt'.
-
-With this you could, for example, automagically punish players for asking for 
-zeny in public places, or alternatively, automagically give them zeny instead if 
-they want it so much.
-
----------------------------------------
-
-*getstrlen("<string>")
-
-This function will return the length of the string given as an argument. It is 
-useful to check if anything input by the player exceeds name length limits and 
-other length limits and asking them to try to input something else.
-
----------------------------------------
-
-*charisalpha("<string>",<position>)
-
-This function will return 1 if the character number Position in the given string 
-is a letter, 0 if it isn't a letter but a digit or a space.
-
----------------------------------------
-
-*getnameditem(<item id>,"<name to inscribe>");
-*getnameditem("<item name>","<name to inscribe>");
-
-This function is equivalent to using 'getitem', however, it will not just give 
-the character an item object, but will also inscribe it with a specified 
-character's name. You may not inscribe items with arbitrary strings, only with 
-names of characters that actually exist. While this isn't said anywhere 
-specifically, apparently, named items may not have cards in them, slots or no -
-these data slots are taken by the character ID who's name is inscribed. Only one 
-remains free and it's not quite clear if a card may be there.
-
-This function will return 1 if an item was successfully created and 0 if it
-wasn't for whatever reason. Like 'getitem', this function will also accept an
-'english name' from the item database as an item name and will return 0 if no
-such item exists.
-
----------------------------------------
-
-*getitemslots(<item ID>)
-
-This function will look up the item with the specified ID number in the database 
-and return the number of slots this kind of items has - 0 if they are not 
-slotted. It will also be 0 for all non-equippable items, naturally, unless 
-someone messed up the item database. It will return -1 if there is no such item.
-
----------------------------------------
-
-*getiteminfo(<item ID>,<type>)
-
-This function will look up the item with the specified ID number in the database 
-and return the info set by TYPE argument.
-It will return -1 if there is no such item.
-
-Valid types are:
-	0 - Buy Price; 1 - Sell Price; 2 - Item Type;
-	3 - maxchance (Max drop chance of this item e.g. 1 = 0.01% , etc..
-		if = 0, then monsters don't drop it at all (rare or a quest item)
-		if = 10000, then this item is sold in NPC shops only
-	4 - sex; 5 - equip; 6 - weight; 7 - atk; 8 - def; 9 - range;
-	10 - slot; 11 - look; 12 - elv; 13 - wlv;
-
-Check sample in nps\sample\getiteminfo.txt
-
----------------------------------------
-
-*getmonsterinfo(<item ID>,<type>)
-
-This function will look up the monster with the specified ID number in the database 
-and return the info set by TYPE argument.
-It will return -1 if there is no such item. Due to specific of MOB DB routines,
-it's better to check monster name. It'd return "Dummy" for a non-existing monster.
-
-Valid types are listed in const.txt:
-	MOB_NAME	0		MOB_LV	1
-	MOB_MAXHP	2		MOB_BASEEXP	3
-	MOB_JOBEXP	4		MOB_ATK1	5
-	MOB_ATK2	6		MOB_DEF	7
-	MOB_MDEF	8		MOB_STR	9
-	MOB_AGI		10		MOB_VIT		11
-	MOB_INT		12		JOB_DEX		13
-	MOB_LUK		14		MOB_RANGE	15
-	MOB_RANGE2	16		MOB_RANGE3	17
-	MOB_SIZE	18		MOB_RACE	19
-	MOB_ELEMENT	20		MOB_MODE	21
+unparallelled power of text manipulation. For an explanation of what a regular 
+expression pattern is, see a few web pages:
 
-Check sample in nps\sample\getmonsterinfo.txt
+http://www.regular-expressions.info/
+http://www.weitz.de/regex-coach/
+
+For an example of this in use, see 'npc\custom\eliza.txt'.
+
+With this you could, for example, automagically punish players for asking for 
+zeny in public places, or alternatively, automagically give them zeny instead if 
+they want it so much.
 
 ---------------------------------------
 
@@ -5117,7 +5842,9 @@ Example:
 set @i, distance(100,200,101,202);
 
 ---------------------------------------
-*query_sql "your MySQL query", <array name>, [<array name>]
+
+*query_sql "your MySQL query", <array name>{,<array name>{;
+
 Returns up to 127 values into array and return the number of row
 
 Example:
@@ -5130,250 +5857,165 @@ mes "4."+@name$[3]+"("+@fame[3]+")";
 mes "5."+@name$[4]+"("+@fame[4]+")";
 
 Note: In the TXT version it doesn't fill the array and always return -1.
-Note: Use Text$[] array to recieve all data as text.
-
----------------------------------------
-
-*setd "variable name", <value>
-
-Works almost identical as set, just that the variable name is identified as a string, 
-thus can be constructed dynamically.
-
-Example:
-set $var$, "Poring";
-
-setd "$var$", "Poporing";
-mes $var$; // Will return Poporing
-
-setd "$" + $var$ + "123$", "Poporing is cool";
-mes $Poporing123$; // Will return Poporing is cool.
-
----------------------------------------
-
-*getd("variable name")
-
-Retrieves variable, name can be constructed dynamically. Refer to setd for usage.
-
-Example:
-set @i, getd("$pikachu");
-
----------------------------------------
-
-*petstat(<flag>)
-
-Returns current pet status, all are integers except name.
-Returns 0 or "" if the player doesn't have pets.
-
-Flags usable >>
-PET_CLASS
-PET_NAME
-PET_LEVEL
-PET_HUNGRY
-PET_INTIMATE
-
-Example:
-set @i, petstat(PET_CLASS);
-
+Note: Use $ as suffix in the array to recieve all data as text.
 
 ---------------------------------------
 
-*setitemscript(<ItemID>,<"{ new item script }">)
+*setitemscript(<ItemID>,<"{ new item script }">);
 
 Set a new script bonus to the Item. Very useful for game events.
+You can remove an item's itemscript by leaving empty the itemscript argument.
 
 Example:
 
 setitemscript 2637,"{ bonus bDamageWhenUnequip,40; if(isequipped(2236)==0)end; if(getskilllv(26)){skill 40,1;}else{skill 26,1+isequipped(2636);} }";
+setitemscript 2639,"";
 
 ---------------------------------------
 
-*disguise <Monster ID>;
-*undisguise;
-
-This command disgueses current player with a monster sprite.
-The disguise is disappearing on re-login or on 'undisguise' command.
+*atoi ("<string>")
+*axtoi ("<string>")
 
-Note: It doesn't work with "Pets with equipment on"
-Note: If u're a Sniper, u'd get an old Falcon over your head
-Note: You can kill yourself with some skills
-Note: Monsters of your type could heal you
+These commands are used to convert strings to numbers. 
+atoi will convert string using normal number (0,1,2,3,etc) while axtoi converts them to 
+hexadecimal numbers (0,1,11,01).
 
 Example:
-disquise 1002; //Yay! You're a Poring!!!
-next;
-undisquise; //Yay!!!! You're a human again!!
-
----------------------------------------
 
-*axtoi(<hexadecimal_value>);
+	mes atoi("11"); 		// Will display 11 (can also be used to set a @var to 11)
+	set @var, axtoi("FF"); 	// Will set the @var to 255
+	mes axtoi("11"); 		// Will display 17 (1 = 1, 10 = 16, 
+							// hexadecimal number set: {0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F})
 
-This command will convert an hexadecimal value into integers (numbers).
-The inputted value must not have neither # or 0x in it, just 6 numbers and/or letters.
-The variable registering this value, if so, must be a string (letter) variable, due that
-it contains letters in some cases.
+---------------------------------------
 
-This is mostly used for the new announce command, which uses hexadecimal values for announce
-colors, using the Ragnarok coloring system.
+*compare (<string>,<substring>)
 
-Example:
+This command returns 1 or 0 when a the substring is in the main string (1) or not (0).
+This command is not case sensitive.
 
-amatsu.gat,171,166,4	script	Testing npc	767,{
+Example(s):
 
-mes "Input hex color";
-input @trying$;
-next;
-set @try2$,axtoi(@trying$);
-announce "zOMG TEH PWNZ0RDZ",bc_all,@try2$;
-close;
-}
+//dothis; will be executed ('Bloody Murderer' contains 'Blood').
+	if (compare("Bloody Murderer","Blood"))
+		dothis;
+//dothat; will not be executed ('Blood butterfly' does not contain 'Bloody').
+	if (compare("Blood Butterfly","Bloody"))
+		dothat;
 
-If you want a list of hexadecimal colors, check these two links:
+--------------------------------------
 
-http://webmonkey.wired.com/webmonkey/reference/color_codes/
+*charisalpha("<string>",<position>)
 
-http://www.december.com/html/spec/color.html
+This function will return 1 if the character number Position in the given string 
+is a letter, 0 if it isn't a letter but a digit or a space.
 
 ---------------------------------------
 
-*rid2name(rid)
-
-Converts rid to name. Note: The player/monster/NPC must be online/enabled.
-Good for PCKillEvent where you can convert 'killedrid' to the name of the player.
+*wedding_effect;
+Starts the effect used when a wedding is done (music and everything else)
+Example can be found in the wedding script.
 
-Note: rid2name may not produce correct character names since rid = account id.
-      It will return the current online character of the account only.
+--------------------------------------
 
----------------------------------------
+* The Pet AI commands
 
-*function <function name>;
-*<function name>;
-*function <function name> {
-<code>
-}
+These commands will only work if the invoking character has a pet, and are meant 
+to be executed from pet scripts. They will modify the pet AI decision-making for 
+the current pet of the invoking character, and will NOT have any independent 
+effect by themselves, which is why only one of them each may be in effect at any 
+time for a specific pet. A pet may have 'petloot', 'petskillbonus', 
+'petskillattack' OR 'petpetskillattack2' and 'petskillsupport' OR 'petheal' at 
+the same time. 'petheal' is deprecated and is no longer used in the default pet 
+scripts. 
 
-(Skotlex stop being so selfish and give us all the commands T~T! J/k lol :P)
+*petskillbonus <bonus type>,<value>,<duration>,<delay>;
 
-This works like callfunc, but doesn't support arguments like callfunc. It's used for cleaner
-and fast script that doesn't require arguments for it to work. Also they must be inside a script. 
-They're not separated scripts and they work more like labels.
+This command will make the pet give a bonus to the owner's stat (bonus type -
+bInt,bVit,bDex,bAgi,bLuk,bStr,bSpeedRate - for a full list, see the values 
+starting with 'b' in 'db/const.txt')
 
-Note it looks like the normal declaration
+*petrecovery <status type>,<delay>;
 
-Usage:
+This command will make the pet cure a specified status condition. The curing 
+actions will occur once every Delay seconds. For a full list of status 
+conditions that can be cured, see the list of 'SC_' status condition constants 
+in 'db/const.txt'
 
-You first Declare the function with function <function name>;.
+*petloot <max items>;
 
-Put the rest of your code. You can use then <function name>; to call the function. If it returns a value is unsure,
-test it if you want and give us some comments ;3
+This command will turn on pet looting, with a maximum number of items to loot 
+specified. Pet will store items and return them when the maximum is reached or 
+when pet performance is activated.
 
-And at least, but inside the script itself, put the function <function name> {<code>}.
+*petskillsupport <skill id>,<skill level>,<delay>,<percent hp>,<percent sp>;
+*petheal <level>,<delay>,<percent hp>,<percent sp>;
 
-Example:
+This will make the pet use a specified support skill on the owner whenever the 
+HP and SP are below the given percent values, with a specified delay time 
+between activations. The skill numbers are as per 'db/skill_db.txt'.
+'petheal' works the same as 'petskillsupport' but has the skill ID hardcoded to 
+28 (Heal). This command is deprecated.
+It's not quite certain who's stats will be used for the skills cast, the 
+character's or the pets. Probably, Skotlex can answer that question.
 
-prontera.gat,154,189,4	script	Item seller	767,{
+*petskillattack <skill id>,<skill level>,<rate>,<bonusrate>;
+*petskillattack2 <skill id>,<damage>,<number of attacks>,<rate>,<bonusrate>;
 
-function SF_Selling;
+These two commands will make the pet cast an attack skill on the enemy the pet's 
+owner is currently fighting. Skill IDs and levels are as per 'petskillsupport'. 
+'petskillattack2' will make the pet cast the skill with a fixed amount of damage 
+inflicted and the specified number of attacks.
 
-mes "I'll open this now if you have more than 50z and you are level 50 or bigger";
-next;
+All commands with delays and durations will only make the behavior active for 
+the specified duration of seconds, with a delay of the specified number of 
+seconds between activations. Rates are a chance of the effect occuring and are 
+given in percent. 'bonusrate' is added to the normal rate if the pet intimacy is 
+at the maximum possible.
 
-if (Zeny > 50) && (BaseLevel > 50) {
-	mes "Welcome";
-	next;
-	SF_Selling;
-	close;
-} else
+The behavior modified with the abovementioned commands will only be exibited if 
+the pet is loyal and appropriate configuration options are set in 
+'battle_athena.conf'.
 
-set @needed,50-BaseLevel;
-mes "You either are Level "+BaseLevel+", thus you need "+@needed+" more levels";
-mes "to be able to use this npc; or you don't have enough zeny, so get some please";
-close;
+Pet scripts in the database normally run whenever a pet of that type hatches 
+from the egg. Other commands usable in item scripts (see 'bonus') will also 
+happily run from pet scripts. Apparently, the pet-specific commands will also 
+work in NPC scripts and modify the behavior of the current pet up until the pet 
+is hatched again. (Which will also occur when the character is logged in again 
+with the pet still out of the egg.) It is not certain for how long the effect of 
+such command running from an NPC script will eventually persist, but apparently, 
+it is possible to usefully employ them in usable item scripts to create pet 
+buffing items.
 
-function SF_Selling {
+Nobody tried this before, so you're essentially on your own here.
 
-	mes "Would you like to buy a phracon for 50z?";
-	switch(select("Yes","No, thanks")) {
+--------------------------------------
 
-	case 1:
-		mes "Ok, how many?";
-		input @quantity;
-		set @check,Zeny/50;
-		if (@quantity > @check) {
-			mes "Sorry but you can only have "+@check+" Phracons with "+Zeny;
-			close;
-		} else
-		next;
-		mes "here you have";
-		set Zeny,Zeny-@quantity*50;
-		getitem 1010,@quantity;
-		close;
-	case 2:
-		mes "Good bye then";
-		close;
-		}
-	}
-	return;
-}
+*bpet;
 
+This command opens up a pet hatching window on the client connected to the 
+invoking character. It is used in item script for the pet incubators and will 
+let the player hatch an owned egg. If the character has no eggs, it will just 
+open up an empty incubator window.
+This is still usable outside item scripts.
 
 ---------------------------------------
 
-*getequipcardid (<equipment slot>,<card slot>);
-
-Returns value from equipped item slot in the indicated slot:
-
-getequipcardid(num,slot)
+*makepet <pet id>;
 
-where:
-	num = eqip position slot
-	slot = 0,1,2,3 (Card Slot N)
+This command will create a pet egg and put it in the invoking character's 
+inventory. The kind of pet is specified by pet ID numbers listed in 
+'db/pet_db.txt'. The egg is created exactly as if the character just successfuly 
+caught a pet in the normal way.
 
-This func returns CARD ID, 255,254,-255 (for card 0, if the item is produced) it's useful 
-when you want to check item cards or if it's signed. Useful for such quests as 
-"Sign this refined item with players name" etc;
-	Hat[0] +4 -> Player's Hat[0] +4
+    // This will make you a poring:
+    makepet 1002;
 
-By Lupus
+Notice that you absolutely have to create pet eggs with this command. If you try 
+to give a pet egg with 'getitem', pet data will not be created by the char 
+server and the egg will disappear when anyone tries to hatch it.
 
---------------------------------------
- 
-*warpparty "mapname.gat",x,y,<party_id>;
- 
-Warps a party to specified map and coordinate given the party ID, which you can get with
-getcharid(1). You can also request another party id given a member's name with getcharid(1,<player_name>).
- 
-Example:
-mes "[Party Warper]";
-mes "Here you go!";
-close2;
-set @id,getcharid(1);
-warpparty "prontera.gat",150,100,@id;
-close;
- 
----------------------------------------
- 
-*warpchar "mapname.gat",x,y,<char_id>;
- 
-Warps another player to specified map and coordinate given the char id, which you can get with
-getcharid(0,<player_name>). Obviously this is useless if you want to warp the same player that
-is executing this script, unless it's some kind of "chosen" script. 
- 
-Example:
- 
-warpchar "prontera.gat",150,100,20000001;
- 
----------------------------------------
- 
-*warpguild "mapname.gat",x,y,<guild_id>;
- 
-Warps a guild to specified map and coordinate given the guild id, which you can get with 
-getcharid(2). You can also request another guild id given the member's name with getcharid(2,<player_name>).
- 
-Example:
- 
-warpguild "prontera.gat",x,y,Guild_ID;
- 
 ---------------------------------------
 
 Whew.
-What's about all of them.
+That's about all of them.
-- 
cgit v1.2.3-70-g09d2