Adding your own scripts

Your land is full of scripted things: doors, levers, bells, traps, lamps. They can be part of your story. There are two directions:

• Script to story: your script tells the story that something happened (the lever was pulled), and the story moves on.
• Story to script: the story tells your objects what happened (the box has started, they won the fight), and they do something: a door opens, a lamp lights, smoke pours out.

Script to story: "When my script says..."

1. 1
   Step 1: Click the box on Your story map, press More..., then A script moves it on.... Choose the box it leads to. (Or tell the helper: “When my lever script says pulled, they go to the vault.”)
2. 2
   Step 2: The box now shows When my script says “…” under Scripts, with a name made from the box’s name.
3. 3
   Step 3: Press Copy a script next to it. A ready touch script goes on your clipboard, with your game and the name filled in.
4. 4
   Step 4: In your object: Content, New Script, open it, select all its text, paste over it, and save.

This is the kind of script you get (your game’s key and the name are filled in):

// Wolf Adventure: when touched, tells the adventure "vault-script" (the box's script step).
default
{
    touch_start(integer n)
    {
        if (!wolfAdventureFire(llDetectedKey(0), "<your adventure key>", "vault-script", ""))
            llOwnerSay("Not now: " + wolfGetLastError());
    }
}

wolfAdventureFire only works while that player’s party is on the box with that script step: pulling the lever too early does nothing, and the script is told why.

Story to script: "Your scripts hear..."

1. 1
   Step 1: Click the box, press More..., then Tell my scripts it starts. (Or tell the helper: “When they choose to ring the bell, tell my scripts.” The helper can also send a signal when they make a choice, or when they win or lose a fight.)
2. 2
   Step 2: The box shows Your scripts hear “…”. Press Copy a script for a ready listening script.
3. 3
   Step 3: Paste it into your object, then add what the object should do where the script says so.

// Wolf Adventure: hears "lamp-starts" from the adventure's story.
integer CHANNEL = -7346;
default
{
    state_entry()
    {
        wolfAdventureListen(CHANNEL);
        llListen(CHANNEL, "", NULL_KEY, "");
    }
    listen(integer ch, string from, key id, string msg)
    {
        list f = llParseStringKeepNulls(msg, ["|"], []);
        if (llList2String(f, 0) == "signal" && llList2String(f, 2) == "<your adventure key>" && llList2String(f, 3) == "lamp-starts")
        {
            key player = llList2Key(f, 1);
            string data = llList2String(f, 4);
            // what your object does now (open a door, play a sound, set off an effect)
            llOwnerSay("lamp-starts for " + llKey2Name(player));
        }
    }
}

wolfAdventureListen(channel) sends the story’s events to your object as chat on that channel, so the script listens there too. The channel is your choice. Each event is one line of fields separated by |; the second field is the player’s key and the third the game’s key. (The event for reaching a box is spelt beat on the wire: it is the same thing as a box.)

Your own scripts, scripts you trust and the region holder’s scripts hear the events. An object someone wears hears only its wearer’s events.

Ask the helper to write one

Tell the helper what you want: “Write me a script for a lamp that turns on when the lighthouse box starts.” It writes a short script, and Copy the script it wrote appears in its column (WolfStorm: Copy the script). Paste it into your own object and read it all before you save it. The helper never puts a script into anything by itself: you decide where it goes.

All the Wolf Adventure functions

adventure is the game’s key; "" means the only game that player is playing on this region (wolfAdventureSay needs the game named). Box, battle, reward and character ids are the ids in your game.

Every function is also listed in the LSL guide once the region update is live.