Description:

When placing a scripted object inside a mesh prim, even after disabling all other scripts, the object refuses to move despite having full permissions (including "take control"). The same script works perfectly when placed inside a regular prim (box). This behavior strongly suggests that residual effects from previously running scripts (such as lingering llSitTarget or similar calls) persist within the mesh prim and prevent proper control, even if those scripts are disabled or removed.

Steps to Reproduce:

Place the scripted object inside a mesh prim.

Disable or remove all other scripts in the prim except the movement control script.

Attempt to move or control the object — it fails to respond despite correct permissions and input.

Replace the mesh root prim or rezz a new prim and the same script works correctly.

The issue does not occur if the object is placed in a regular prim (box).

Debug confirms physical presence, permissions, and input detection are correct; however, the object does not move.

Expected Behavior:

Disabling or removing scripts should fully stop any lingering script effects such as llSitTarget or control overrides, allowing the object to move normally under script control.

Actual Behavior:

Residual script effects remain active even after disabling/removing scripts, causing the object to become immobile inside mesh prims unless the root prim is replaced or a new prim is rezzed.

Impact:

This is a critical bug affecting scripted object control and physics within mesh prims, disrupting expected behavior and causing significant development and usage issues.

Additional Notes:

The bug seems specific to mesh prims and does not appear in regular prims.

Replacing the mesh root prim clears the issue temporarily, indicating state persistence at the prim level.

Suspected causes include improper cleanup of llSitTarget or similar functions.