Category talk:LSL Events

Why all events have a code ender? should be starting with both brackets.

Not this... event(integer);

Should be this... event(integer){ }

But I am unable to correct this format in the wiki, what's the deal? -Vincent Nacon

Sorry thats my fault, I've been meaning to fix it, it's a bug in the template. I just kept forgetting. Strife Onizuka

Fixed, the variable for that part of the title was getting double defined; the latter overwriting the former. Strife Onizuka 18:17, 6 April 2007 (PDT)

Attach under S letter

The Attach event is listed under S letter. I have no idea about how to fix it. Can someone fix that? (and explain here how it was done) --CrazyTB Oh 11:37, 21 August 2007 (PDT)

I fixed it. What I do is delete the part that says this is part of the "LSL_EVENTS" category and then put it back. That usually fixes it, and when it doesn't then I just mess around with the page and it eventually gets fixed... Xaviar Czervik 15:43, 17 September 2007 (PDT)

Script Ban Zones

I have spend many hours on trying to figure out how events are handled in script ban zones. I have some text to describe it. But I am not sure where to put it, so for a start I put it here, someone might then help me put the logical place (which I have not yet figured out).

All the usual events are happening in script-banned zones, only the script does not react to them, but keep them in the event queue for later execution. This might potentially cause problems with the 64 length of the queue, though I have not tried this out.

Notice, even listen events are stored. Also notice, pending listen events are removed when moving to a new region, but not other events I have tried.

The big surprise is that scripts can be made to execute in a script ban zone - pending events to a script in an attachment are all executed when the attachment is detached. By attaching and detaching an attachment, one can therefore execute code in a no script zone, even listen events. However, this will most often not be very useful.

I have verified that, change, rezzing, attachment, touch are all registered and stored in the event queue for later execution. I have not investigated the behavior of other events in depth.

Finally, there are some restrictions regarding repetition of events I have not fully explored. For instance, it seems that only one touch event is queued even if one touches an attachment multiple times.

2008 jan 17 -Boreal Latte

State_entry

I don't see it mentioned in this overview. --Vernes 22:03, 17 December 2008 (UTC)