Need some script help :)

I have made a chest of drawers and each drawer has a script in it to open the drawer when touched.

I know how to change the script so that the drawers open correctly if I decided to change the rotation of my chest.

But what if I wanted to sell this chest of drawers? How can I sell it when the script will only work correctly if the chest is facing a certain way?

I assume there must be a way to fix this so any buyer can place this chest wherever they like and still have correctly opening drawers?

Here is the script I am currently using.....



default
{
state_entry()
{
llGetLocalPos();
}

touch_start(integer total_number)

{
state off;
}
}

state off
{
state_entry()
{
llSetPos(llGetPos() + <-0.5, 0, 0
>;
}
touch_start(integer total_number)
{
llSetPos(llGetLocalPos() + <0.5, 0, 0>;


state default;
}
}

for starters:

default
{
    state_entry()
    {
        llGetLocalPos();
    }

    touch_start(integer total_number)
    {
        state off;
    }
}

state off
{
    state_entry()
    {
        llSetPos(llGetPos() + <-0.5, 0, 0>);
    }
    touch_start(integer total_number)
    {
        llSetPos(llGetLocalPos() + <0.5, 0, 0>);
        state default;
    }
}

and now that it's legible

i removed the state_entry from the default state since it had no bearing on the script at all. i also changed the state_entry on the 'off' state to use llGetLocalPos() instead of llGetPos() this way you are actually modifying the proper position when you add/subtract the 0.5m

this script is currently moving the drawer along it's local x axis, so if instead of moving in/out of the chest it moves side to side or up and down, change the <-0.5,0,0> to <0,-0.5,0> or <0,0,-0.5> and obviously do the same to the other one below it one of them will move it in the direction you want it to go.

default
{
    touch_start(integer total_number)
    {
        state off;
    }
}

state off
{
    state_entry()
    {
        llSetPos(llGetLocalPos() + <-0.5, 0, 0>);
    }
    touch_start(integer total_number)
    {
        llSetPos(llGetLocalPos() + <0.5, 0, 0>);
        state default;
    }
}

This will work for any rotation, assuming that the child prim is at ZERO_ROTATION relative to the root prim. if not, you'll have to adjust the movement vectors.

default
{
    touch_start(integer total_number)
    {
        state off;
    }
}

state off
{
    state_entry()
    {
        llSetPos(llGetLocalPos() + <-0.5, 0, 0>*llGetLocalRot());
    }
    touch_start(integer total_number)
    {
        llSetPos(llGetLocalPos() + <0.5, 0, 0>*llGetLocalRot());
        state default;
    }
}

Nope. It is incorrect to rotate the offset vectors since llSetPos is intelligent enough to know whether it's performing a local or global translation.

Raeyan's code is correct.