What scripting screw up would mess up attachments?

I've been going through some of my guns again and I noticed, that when I attached a gun in a no-script zone, the attachment positions where fine. However, when I flew up high enough to trigger the script, the attachment rezeroed automatically.

This makes me think that somewhere in the state entry, on rez, or attach events in the script is causing the attachment to lose it's settings. Not only does the gun attach fine in no-script areas, but I can drop it and pick it up.

I had never heard of this before and I had thought it was an issue with 1.7 (it might still be, possibly connected to the new llsetpos functionality in attachments). Would anyone have a clue what could be happening? I suspected it was a menu control script that I've been using, as it had a link_message with a null key. Any ideas?

Some guns would "right" themselves if dropped or rezzed on the ground - taking advantage of the fact attachments cold not move.

Well, they can move now. Look for llSetRot() in those events.

I'll double check. I am now 100% sure it's the menu control script. I've gone ahead and turned it off, and the gun will keep it's position settings whenever I drop or detach it. I haven't logged in since I did that, so I'm not sure if the client or asset server will screw me whenever I log in and try again. I'm wondering if there's a scripting parameter mix-up in the main script that would.

I'm using scripts that technically predate 1.7. For one, I'm using the Linden Revolver Script as a base. All I've done to that one is mod it for listens, for now.

I'm really thinking I should avoid using that script and instead go with a HUD. The HUD would most likely be easier to control and play with. Of course, it does open a whole other set of issues I'd have to work out.


ON EDIT: Yeah, that's the culprit. I think the attachment script was conflicting with the main script' permissions and began causing this. I've gone in and corrected them, and they position correctly now.