I have marked this issue a showstopper because it is effecting the order events are triggered including the crytical events like on_rez and state_entry. This is going to be breakign a lot of stuff and it is goign to drive people nutty trying to work out why. I was just lucky enough to be working on a stargate script effected by this at the time so I had all the debugging information in my script which quickly demonstrated the events were being triggered in the wrong order. I have noticed some of my products have recently broken. I have tracked the casue to the timer event triggering before other events such as state_entry and on_rez. In the case of state_entry() it appears that the timer event in the new state is triggered before the state_entry on a state change if the timer is due to trigger at the time the state is changed. The timer() event is triggered before the on_rez event() if the timer was due to be triggered when the item was take into inventory. These problems have caused a lot of trouble with temp-rez items that are programmed to die. I have noticed this problem with my stargate event horizon and some (but not all) temp bullets. I'm not sure why, and it dosnt seem to make any sence to me, but i cant force this to happen deliberatly with a new script. However removing the timer before switching states & before taking an object into inventory ensures that the state_entry & on_rez events are triggered correctly. I have the original script which was in world when mono was rolled out which still has the problem and can hand it to a linden when required. Note this script is LSL.