|
1 | | -== Why would a function be useful? == |
| 1 | +## Why would a function be useful? |
2 | 2 |
|
3 | | -A function is mainly a chunk of code that either is used for multiple actions of the same item, or a simple way to check the status of something. This eliminates lots of code from the main script and makes it a bit cleaner for you to see and debug. |
| 3 | +A function is mainly a chunk of code that either is used for multiple actions of the same item, or a simple way to check |
| 4 | +the status of something. This eliminates lots of code from the main script and makes it a bit cleaner for you to see and |
| 5 | +debug. |
4 | 6 |
|
5 | | -== Creating a Function == |
| 7 | +## Creating a Function |
6 | 8 |
|
7 | | -In order to create a function, you can do one of many things. Many scripters place their functions in 1 of 2 locations. I, myself, place my functions in a functions.txt script file and load that independently. By doing this, you can organize your functions and keep all your other scripts clean and free of clutter. Another method is to simply place them inside the script itself, however, I find this to lengthen the script quite a bit, and makes it complicated to find where the function is located in case another script file is calling it. |
| 9 | +In order to create a function, you can do one of many things. Many scripters place their functions in 1 of 2 locations. |
| 10 | +I, myself, place my functions in a functions.txt script file and load that independently. By doing this, you can |
| 11 | +organize your functions and keep all your other scripts clean and free of clutter. Another method is to simply place |
| 12 | +them inside the script itself, however, I find this to lengthen the script quite a bit, and makes it complicated to find |
| 13 | +where the function is located in case another script file is calling it. |
8 | 14 |
|
9 | | -<pre>function(TAB)script(TAB)name(TAB){ |
10 | | - // code |
11 | | -}</pre> |
12 | | - |
13 | | - |
14 | | -== The RETURN Command == |
| 15 | + function(TAB)script(TAB)name(TAB){ |
| 16 | + // code |
| 17 | + } |
15 | 18 |
|
16 | | -Sometimes it's necessary to send back information that you retrieved from your function. Such as a TRUE/FALSE 0/1 response, or sometimes even more. In order to do this, your function needs a return statement. |
| 19 | +## The RETURN Command |
17 | 20 |
|
18 | | -<pre>return <Value>; |
19 | | -return <Variable>;</pre> |
| 21 | +Sometimes it's necessary to send back information that you retrieved from your function. Such as a TRUE/FALSE 0/1 |
| 22 | +response, or sometimes even more. In order to do this, your function needs a return statement. |
20 | 23 |
|
| 24 | + return <Value>; |
| 25 | + return <Variable>; |
21 | 26 |
|
22 | | -== Calling a Function == |
| 27 | +## Calling a Function |
23 | 28 |
|
24 | 29 | There are a few ways to call functions, depends on what information you are retrieving. |
25 | 30 |
|
26 | | -<pre>callfunc "MyFunction";</pre> // Simply calls the function that does not use a RETURN command |
| 31 | + callfunc "MyFunction"; |
27 | 32 |
|
28 | | -=== Using Arguments in a Function === |
| 33 | +// Simply calls the function that does not use a RETURN command |
29 | 34 |
|
30 | | -Sometimes it's helpful to pass variables or values to a function in order to retrieve the information that you would like. These values are called arguments. Many people use these in order to make calculations. |
| 35 | +### Using Arguments in a Function |
31 | 36 |
|
32 | | -==== The Function ==== |
| 37 | +Sometimes it's helpful to pass variables or values to a function in order to retrieve the information that you would |
| 38 | +like. These values are called arguments. Many people use these in order to make calculations. |
33 | 39 |
|
34 | | -<pre>function(TAB)script(TAB)calc(TAB){ |
35 | | - set @a, getarg(0) + getarg(1); |
36 | | - return @a; |
37 | | -}</pre> |
| 40 | +#### The Function |
38 | 41 |
|
| 42 | + function(TAB)script(TAB)calc(TAB){ |
| 43 | + set @a, getarg(0) + getarg(1); |
| 44 | + return @a; |
| 45 | + } |
| 46 | + |
| 47 | +#### Calling the Function |
39 | 48 |
|
40 | | -==== Calling the Function ==== |
| 49 | + set @a, callfunc("calc",1,2) |
| 50 | + mes @a; |
41 | 51 |
|
42 | | -<pre>set @a, callfunc("calc",1,2) |
43 | | -mes @a;</pre> |
| 52 | +#### The Result/Return |
44 | 53 |
|
45 | | -==== The Result/Return ==== |
| 54 | + 3 |
46 | 55 |
|
47 | | -<pre>3</pre> |
| 56 | +#### Passing Arrays as Arguments |
48 | 57 |
|
49 | | -==== Passing Arrays as Arguments ==== |
| 58 | +Calling the Function: |
50 | 59 |
|
51 | | -Calling the Function: |
52 | | -<pre>callfunc "calc", MyArrayName;</pre> |
| 60 | + callfunc "calc", MyArrayName; |
53 | 61 |
|
54 | 62 | The Function: |
55 | | -<pre>function(TAB)script(TAB)calc(TAB){ |
56 | | - getelementofarray(getarg(0), 1); |
57 | | -} |
58 | | -</pre> |
59 | 63 |
|
60 | | -* Please note, that npc variable arrays will not function in the same manner (this will be updated at a later date) |
| 64 | + function(TAB)script(TAB)calc(TAB){ |
| 65 | + getelementofarray(getarg(0), 1); |
| 66 | + } |
| 67 | + |
| 68 | +- Please note, that npc variable arrays will not function in the same manner (this will be updated at a later date) |
61 | 69 |
|
62 | | -==== Calling Function as a Script Command ==== |
| 70 | +#### Calling Function as a Script Command |
63 | 71 |
|
64 | | -<pre> |
65 | | -prontera,150,150,5<TAB>script<TAB>Calculator<TAB>999,{ |
| 72 | + prontera,150,150,5<TAB>script<TAB>Calculator<TAB>999,{ |
66 | 73 |
|
67 | | - function<TAB>Add<TAB>{ |
68 | | - return (getarg(0)+getarg(1)); |
69 | | - } |
| 74 | + function<TAB>Add<TAB>{ |
| 75 | + return (getarg(0)+getarg(1)); |
| 76 | + } |
70 | 77 |
|
71 | | - mes Add(1,2); |
72 | | -} |
73 | | -</pre> |
| 78 | + mes Add(1,2); |
| 79 | + } |
74 | 80 |
|
75 | | -=== Special Notes === |
| 81 | +### Special Notes |
76 | 82 |
|
77 | 83 | Variables are passed to functions by reference |
78 | 84 |
|
79 | 85 | This means that you can do normal variable operations on a variable reference returned by getarg. |
80 | 86 |
|
81 | 87 | Ex: |
82 | 88 |
|
83 | | -<pre>function<tab>script<tab>F_Increment<tab>-1,{ |
84 | | - // getarg(0) returns a reference to the .@num variable in NPC_Test |
85 | | - // NOTE: you can't use .@num directly, it's a different variable from the .@num in NPC_Test |
86 | | - set getarg(0), getarg(0) + 1; |
87 | | - return; |
88 | | -} |
89 | | - |
90 | | -prontera,156,156,4<tab>script<tab>NPC_Test<tab>56,{ |
91 | | - // initial number |
92 | | - set .@num, 123; |
93 | | - mes .@num; |
94 | | - |
95 | | - // increment inside the function |
96 | | - callfunc("F_Increment", .@num); |
97 | | - mes .@num; |
98 | | - |
99 | | - close; |
100 | | -}</pre> |
| 89 | + function<tab>script<tab>F_Increment<tab>-1,{ |
| 90 | + // getarg(0) returns a reference to the .@num variable in NPC_Test |
| 91 | + // NOTE: you can't use .@num directly, it's a different variable from the .@num in NPC_Test |
| 92 | + set getarg(0), getarg(0) + 1; |
| 93 | + return; |
| 94 | + } |
| 95 | + |
| 96 | + prontera,156,156,4<tab>script<tab>NPC_Test<tab>56,{ |
| 97 | + // initial number |
| 98 | + set .@num, 123; |
| 99 | + mes .@num; |
| 100 | + |
| 101 | + // increment inside the function |
| 102 | + callfunc("F_Increment", .@num); |
| 103 | + mes .@num; |
| 104 | + |
| 105 | + close; |
| 106 | + } |
101 | 107 |
|
102 | 108 | Operators always return values, so this would provoke an error on the set inside F_Increment: |
103 | 109 |
|
104 | | -<pre>callfunc("F_Increment", .@num + 1);</pre> |
| 110 | + callfunc("F_Increment", .@num + 1); |
105 | 111 |
|
106 | 112 | It's important to note the difference between the reference of the variable and the value of the variable: |
107 | 113 |
|
108 | | -* ''reference'' : the variable itself. It knows it's name, value and index. The type of variable is determined from the name. |
109 | | -* ''value'': the value of the variable (string or number). |
| 114 | +- *reference* : the variable itself. It knows it's name, value and index. The type of variable is determined from the |
| 115 | + name. |
| 116 | +- *value*: the value of the variable (string or number). |
0 commit comments