Multiple Timers!

In LSL multiple timers, that are simply assigned to a variable and can be deleted.

Hmm, you mean to have a timer() event with a parameter that lets you identify the particular event? It could be useful, but it's technically possible to do this yourself through LSL scripting, it'd mean using lists but it's do-able using something like:

list events = [];
integer nextEvent = 0;

scheduleEvent(integer id, integer time) {
    events = llListSort((events = []) + events + [time, id], 2, TRUE);
}

setTimer() {
    if ((events != []) > 0) { // Are there any list items?
        integer time   = llList2Integer(events, 0);
        integer id     = llList2Integer(events, 1);

        nextEvent = id;
        float t = (float)(time - llGetUnixTime());
        if (t <= 0.0) t = 0.01;
        llSetTimerEvent(t);
    } else llSetTimerEvent(0.0);
}

handleEvent(integer id) {
    // Enter your handling code here
    if (id == 1) {
        llOwnerSay("Half-way there");
        scheduleEvent(2, llGetUnixTime() + 10);
    } else if (id == 2) llOwnerSay("Done");
}

default {
    state_entry() {
        scheduleEvent(1, llGetUnixTime() + 10);
        setTimer();
    }

    timer() {
        // Clear timer or it might fire again before we're done
        llSetTimerEvent(0.0);
        
        // Get rid of the first item as we're executing it
        integer l = events != [];
        if (l > 0) {
            if (l > 2)
                events = llList2List((events = []) + events, 2, -1);
            else events = [];
        }
        
        handleEvent(nextEvent);

        // Prepare the timer for the next event
        setTimer();
    }
}

Basically you just throw your event handling into the handEvent(integer) function. It can be tailored easily depending on your needs, as this version is intended for events which finish at a specific time (a unix timestamp). If you want events that execute in 30 seconds, then you could modify the script to accept a float value for time in the scheduleEvent(integer, integer) function instead, making sure to change setTimer() accordingly.

Added a slightly more generalised version to the LSL wiki:
https://wiki.secondlife.com/wiki/Scheduler

No......

I mean give it multiple timers like all other languages have,

So you could have like

timer1:Timer = new timer(5);
timer2:Timer = new timer(6);


timer1(){
do whatever ever 5 seconds

}

timer2(){
do whatever ever 6 seconds

}

I know what you mean, but LSL is an event driven language with a finite amount of space for events on its queue. What are your cases? There are possibly other solutions.

I've never encountered a case where I need multiple timers except the ones I'd use a scheduling system for, e.g; closing listens after a minute, freeing up control of an item to other users after two minutes, and so-on.

A lot of languages are event driven they work this way.

As long as you destroy the timers my assigning them to a blank value it would not require more system resources etc and in other language the way I'm proposing is the correct way.

The code your using there is calling a lot more in built functions than mine would to do the same job.

This is a feature request forum, not a scripting help forum.

I know how to go a huge way round to achieve this and take up loads of code and resources, what I'm asking for is a as a feature request is to add the function ability that other languages have.

I understand that, and I'm not really opposed to it. But the thing is that there are two alternatives scheduling and using extra timer scripts, both of which are available now. The problem being that this makes the request fairly minor so I'm not sure it's likely LL will pay attention to it, the other issue being that the current timer() event is not well suited to it; I'm unsure LL are likely to implement a second timer type event to support multiple timers when you there are alternatives.

Unfortunately these are the kinds of hurdles that would be faced in trying to get such a feature implemented. My intention isn't to insult you, and I apologise if I did, but with readily available alternatives LL are unlikely to do this =(

i'm sure it's already been done. i'm thinking about making a door that listens for password when touched. i would want the timer to remove the listen after so many seconds if nothing was said. but also the door itself would be on a timer to make it close if it was opened. i guess an easy solution would be to have 2 scripts? one that listens when touched, if the correct password is said it sends a link message to itself. and then in the second script it would receive the link message, open the door, and turn on the timer to close the door

The scheduler script I linked to should suit your needs, you can of course edit as you require. Since you only really have two events then you may find it better also to take the ideas presented in the script and create a more specific implementation for your door.

i have done multiple timers in one script.
one of many timers gets an integer or even a string as timestamp vvhen it shoud be triggered and set again.
the main timer() checks a vvorld time such as unix time or llgettimestamp and if that is past one of the timers memorized timestamps that event gets triggered and reset to be triggeret --at east every n seconds--
its inaccurate but less effected by time dilation. a usefull sceduer