
;List of includes for Virtual Scene scripting.
;Please read HTML\vsmanual.html for help.
;Here are the includes, the part WoS cares about:

	#include VS\VSgui.txt

;That file is the thing that world devvers are going to see: the GUI that helps them make the scenes.

	#include VS\VS2242.txt

;A scene interpreter.  The world developer may add more, and change the scene numbers, so long as they remember to change all the scene numbers inside the file as well.
;It's best to keep the original around in case you need to add more scenes; especially if you renumber the scene to something below 100.

;Virtual Scenes, once inputted and saved in the VSIDE, can be called up, modified, and "printed".
;This means that it is useful for testing new quests.
;This can be accomplished by bugtesting the virtual scenes publicly, and "printing" them and hardcoding the finished versions in the next patch of the world.

;Virtual Scenes can be CALLed as functions.  To do this, you might use the following bit of code:

;CALL 2242@vs2242execute97 functionlabel

;That would call the virtual scene's Action 97[1], which would search for the virtual label, then jump to it when it was found.  If the label is not found, the label finder will return with arg0 set to "error".


;---
;[1]: Each QUEST command is identified as an Action with a unique ID.  Special actions range from 95 to 99, and the normal quest commands are Actions 01 through 71.

;---
;Please note that certain characters cannot be processed correctly due to a denesting procedure.  The following characters, when not part of cookie wrappers, cannot be processed correctly:

;  #
;  *

;And these cannot be used in a cookie name:

;  (
;  )

;Embedded cookies MUST have the parenthesis adjacent to the wrapper to process correctly:

;  #<(#<cookie1>#<cookie2>)> OK!
;  #<(cookie#<cookie2>)>     OK!
   #<cookie(#<cookie2>)>     BAD!