Flow Control problem

I'm mostly done with a script but I want to build a safeguard into it and everything I've tried so far has failed.

The object in question is supposed to interact with an avatar in the following way:

1. Object is in closed position

2. TOUCH Object moves to open position

3. SIT Avatar sits and object returns to closed position

4. TOUCH Object moves to open position

5. STAND UP Avatar stands and object returns to closed position. Script goes to default state.

All that works fine. But if the Avatar stands while the object is in the closed position (uses STAND UP instead of TOUCH in step four) then the object moves to what would be the closed position, except since it was never opened, it ends up misplaced and you have to drag it back to the closed position.

So what I would like to have is a sequence that would return the script to the default state without moving the object if the avatar stands at the wrong time. Nothing I've tried (mostly a variety of if-else statements) has worked.

How do I do this?

I'm thinking you just need to keep track of whether it's open or closed, like with a TRUE/FALSE integer, and avoid closing unless open

My preferred way is to use states like so:

default {
    state_entry() {
        llSetPos(<1.0, 2.0, 3.0>); // The 'closed' position
    }

    touch_start(integer x) {
        state open;
    }
}

state open {
    state_entry() {
        llSetPos(<3.0, 2.0, 1.0>); // The 'open' positon
        llSetSitTarget(<1.0, 2.0, 3.0>, ZERO_ROTATION); // Where the avatar sits on this
    }

    changed(integer x) {
        if ((x & CHANGED_LINK) && (llAvatarOnSitTarget() != NULL_KEY)) state default;
    }

    touch_start(integer x) {
        state default;
    }
}

Something along those lines anyway. Since your item has only a limited set of clearly defined states then it makes more sense than storing integers, and allows you to make your code much neater.

Plus, it allows you much greater control over how you get into each state. You can guarantee that the only way code in the open state can execute is after you've called "state open;" .

It also ensures it does the right thing on a script reset or a copy being taken.

I think that's solved it. Thanks!