Add a "push(vector impulse)" event

I want a push() event that gives out what impulse is applied to the object in which the script runs whenever a "llPushObject()" targets it or something collides in it and pushes it (in the case of physical objects).

This would make it easier to create antigriefing utilities and combat systems.

sweet that would be great. best we can do is a fast timer checking out position now right?

I expected a little more suport for this feature, thanks Zuzi

Events, while desirous to us scripters, are hard on the system.

There is no limit to how many scripts can be reactive to any particular event, so when that event happens there is potential for a large hit to the system. Also, if there is no limit to how often the event can be triggered then there is another way the system can be lagged.

Look at all the events we have now. Most of them are either unique to the object and/or limited in how often they trigger. The big two baddies are listens and timers, and we know how they can be either abused or badly coded to lag a sim, especially in large numbers.

Another issue with events is, the more you have, the more likely it is that chain reactions can be started. The more complex the system, the longer it can take to reach a steady-state.

That said, an impulse detecting event would not be that hard on the system, I would think. Not by itself. But if I were in charge of LSL development, I would think long and hard before adding a new event catcher to the language, even if it does seem benign.

(Of course, if I were in charge of LSL development, I'd throw the lot out and start from scratch with a better core design... One that's even now fermenting in my brain. )

Agreed Tiger. One thing I wanted to bring up, though, is the system does already actively track applied force/impulse from others and their scripts in the form of the Abuse Report system.

That said, push() event handling is thinking way too small IMO. How about on_impulse() to handle any applied movement, directly, with push, or with another script?

...Or by force imparted from a collision? The more often the event gets thrown, the more potential for lag it gains.

Potentially, Tiger. I mean, it throws a collision event already, so that functionality could be added as a runner to collision in theory, yes?