II. The Forms
        B. Scripting
            1. Script Detail
            2. Event Builder
            3. Script Properties
            4. Script CMD Summary
            5. Script CMD Listing
            6. Command Types
            7. Script Database Edit Buttons

MODULE    : Writer.EXE

    PURPOSE      : The script editor is the central programming interface for Explorations. It allows you to control game events, the story, sprite actions, and special effects.
   
    DATABASE     : {MapName}.MAP, Script.DAT, TScript.DAT
   
    TAB          : Script Editor
   
        PROPERTIES    :

Explorations supports three different script databases: MAP, REL, & TME (Map, Relative, & Time). Each database stores script events for different aspects of Explorations game objects.

MAP databases store map event triggers. A map event trigger is any script event that is executed based on a sprites location on a given map.

TIME databases stored events. Timed scripts can be created to execute periodically, or at a specific time during the game.

RELative databases manages GLOBAL events. Global script events are any event that are not directly connected to a map location. Instead these scripts may be linked to an event of a game object.

Each script record can be set Enabled/Disabled to control execution. When a PC walks on a map event, you can force him to stop movement and face a specific direction with these properties.

Each event must have a simple but unique Title to help you organize your game flow.

Event labels are execution points within the script record. Rather than executing each script from its start, you can create jump points within the recordset. This allows you to organize and control script execution as you see fit.

You can create and rename jump point label at any time. Remember, renaming a label that has been previously referenced can cause problems. (LABELS are like game hyperlinks) Explorations debugger will find/track & report broken label references.

The script area holds the actual script commands. (eScript as well as eMotions script commands are accepted.)

The Command Lists are powered by the .CMD files. Each command type holds all the related commands Explorations supports. As new commands are created these .CMD files will be updated to support the additional commands.

Within the .CMD files are the description of the command, an example of the syntax and an explanation of any return values when the script is used. This is intended to document as you learn eScripting.

        BUTTONS       :

These buttons control the Recordset management of the Objects database. Changing a property value doesn't automatically save to the database. Always remember to UPDATE a changed record before you move to a new recordset.