However it is becoming necessary to write scripts which have more control over their 'flow'. That is to say they have the need to go not just forwards, but to skip forwards and backwards.
The first command to help you do this is: stop
Stop makes the script end. Finished. Done. Even if it's in the middle of the script.
You'll see why this is very important in just a second.
To allow you to jump to specific locations in your script you can denote 'jump points' in your script with the 'label' command. When you use the label command and pass it a string, you can later (or sooner) 'jump' to that label.
Doing an endless loop using a label and jump would look like this:
(WARNING! THIS IS AN EXAMPLE! DO NOT DO THIS!)
tell %player "Hello!"
This would tell the player Hello! over and over and over and over again until a Wizard came and killed the task, and probablly killed your charcater as well for writing such a harmful script.
Now, the ability to jump in and of itself is pretty powerful. It's intended purpose is to allow you to do things like start the script over (A LIMITED NUMBER OF TIMES), or skip over entire parts of the script.
However, if you only use label and jump to do complex things, your logic can become -very- confusing.
So we introduce the concept of 'start' and 'finish'.
start works exactly like jump in that it takes a label name and jumps you to that label. What's different about start is it -remembers- where you are in the script, and upon encountering a 'finish', returns you to that place.
Let's try an example.
//Doin some stuff here
tell %player "And that's how you give a blowjob."
//Note the use of stop here to end the script before we go into the 'blowjob' code
//tell the player how to give a good blowjob here
So, what happens there is we 'do some stuff' per the comment, then -remember- where we are and jump to the label blowjob. Upon encountering the 'finish' statement, we go BACK to where we 'start'ed "blowjob", and continue on from there until we encounter the 'stop'.
You can also do nested starts, like a start in blowjob that takes you elsewhere, and the first finish will return you to back inside blowjob, while the second finish will take you back to the begining. Thus you can come up with very complex scripts which do all kinds of interesting things.
Here's a rather contrived but valid example of how you might use this:
tell %player "Please choose from the following options. For a burger, say burger. For fries, say fries. To end this, say goodbye."
if match %response "burger"
elseif match %response "fries"
elseif match %response "goodbye"
�tell %player "Goodbye!"
�tell %player "That's not one of the options. Please try again."
//do burger stuff here
tell %player "Do you want curly or regular?"
if match %response "curly"
elseif match %response "regular"
�tell %player "Please choose from the following options:
//Do curly fries here
//Do regular fries here
As you can see, with the creative use of jump and start you can do some really complex flow control which reads rather well.
Now I suggest you take the use of these things VERY SERIOUSLY as their improper use can REALLY fuck things up in a BIG way if your not VERY careful. It's very easy to write crappy code with this. The key lies in modularity and simplicity. KISS: Keep it simple stupid.
Any questions, comments, or screams of agony?
PS: Many of you will reconize this as a 'function' or 'sub-routine'. Yes, it is in fact just a simple stack machine, the premise on which all modern computing is based. I never claimed to invent the concept. I'm just making really effective use of it.
(Edited by Kevlar at 1:26 pm on Mar. 15, 2003)