Not sure the proper terminology, but I should clarify what I mean by "physics deactivated." As I understand it, a collection of physical objects, and/or an avatar, once they come to a rest, are "deactivated" so as to save the physics engine cycles. Once a physical interaction is due to happen, they are reactivated and processed. From my testing, once an avatar comes to a rest and is deactivated, any scripted physics call on that avatar fails. Persistent physics effects such as llSetForce or llMoveToTarget take effect once the avatar is activated, such as by the user moving the avatar. One-off physics calls such as llApplyImpulse or llPushObject simply fail, as their effect happens on an avatar that is not in the active state. This applies to: llApplyImpulse llPushObject llSetForce llMoveToTarget All physics functions excluding llPushObject must be in an attachment, and thus "part of the avatar" to affect the avatar. llPushObject may be called from an inworld object. Even when not attached, it still fails. I'm guessing there should be a code path that each physics call goes through that just needs to activate the avatar before taking effect. SVC-734 Falls under this but, although it only specifically names llMoveToTarget,