steph Arnott

I added this because code block seperation with touch event never seems to get mentioned. Which is a shame as it is rather usefull. key owner_id; integer a = 3;//or whatever the face is integer b = 1; default { state_entry() { owner_id = llGetOwner(); } touch_start(integer num_detected) { key avatar_key = llDetectedKey(0); string avatar_name = llDetectedName(0); integer face = llDetectedTouchFace(0); if(avatar_key != owner_id) { if(face == a) { llInstantMessage(owner_id, "I was touched by " + avatar_name + " inside" ); } if(face == b) { llInstantMessage(owner_id, "I was touched by " + avatar_name + " outside" ); } } else return; } touch_end(integer total_number) { if(owner_id) { llOwnerSay("only for me this code block"); } } }

There was a function but LL broke it and have no interest in fixing it. That function is depreciated and has been for years. You could spew a few temp prims but it would have to be a FEW. Or use a sensor. Or as above.

Your RLV does not work if the person opens a second viewer using a second account. RLV commands are only active in one account and the agent can revoke perms at any time Any how you was give what you asked. We are not here to write scripts for you. Also this is LSL main not OS cludge code forum.

You do know it is consentual RP and not a real cage? A person could simply open second veiwer using another account and swan off doing whatever while you think they are locked in your cage having a jolly good laugh at you. Consentual means following agreed rules, totally pointless if an agent is not going to. The code i gave is a baseline starter which can be added to with stuff like the outside face ignoring the agent inside with a simple conditional. I gave you what you requested, the rest is upto you.

It was a concept script. It would only take a few lines to ignore the agents touch on the outside face while they are inside by using their key. You do not need the agents pos. Any how it would tell you if they cammed because it tell you which face was touched.

Or this. key owner_id; integer a = 3;//or whatever the face is integer b = 1; default { state_entry() { owner_id = llGetOwner(); } touch_start(integer num_detected) { key avatar_key = llDetectedKey(0); string avatar_name = llDetectedName(0); integer face = llDetectedTouchFace(0); if(avatar_key != owner_id) { if(face == a) { llInstantMessage(owner_id, "I was touched by " + avatar_name + " inside" ); } if(face == b) { llInstantMessage(owner_id, "I was touched by " + avatar_name + " outside" ); } } else return; } }

key owner_id; default { state_entry() { owner_id = llGetOwner(); } touch_start(integer num_detected) { key avatar_key = llDetectedKey(0); string avatar_name = llDetectedName(0); if(avatar_key != owner_id) { llInstantMessage(owner_id, "I was touched by " + avatar_name ); } else { } } }

Rollig has already done it as i posted.

Okay. I have not had the problem you describe so either there is something in the script or something you are doing and i have no idea what that is.

Well i use a timer and each is loaded every 0.1. Can not see what a script stall would achieve as population is subject to the servers priority protocols. Dropping transfer when it decides to.

Try pasting the script code into a fresh script and use that as the usage script. An edited script can retain corruped data.

Maybe true but i found that passing scripts from a copy to another copy was too unreliable.

I do not do mine like that. The HUD contains the original object with virgin scripts in the objects and rezzes a copy from the HUD.

'relevant stakeholders' is typical Linden Lab word salad. Can mean whatever you want it to mean.

You are talking about a system that is way beyond your capabilities. Also the two examples supplied for this type of system are too crude. The touchers ID KEY should be used to lock out all other agents from script usage while the timer is active. First thing you need to do is write flow chart of what has to do what before you can even start scripting the elements. Without that flow chart you would be just guessing as you go along which will keep throwing you back to scripts you have already written and have to modify. The system you describe is no easy feat using LSL.

Strip put what is not needed and get the RLV command to message the script with the camara. You can then lock the camera rotation parameters.

You are not the only one. There was a split where one was not updating and the other was. The other set up a commercial MP with locked code. You could try this. It is over bloated but you could direct the RLV to a satilite script with a cut down version of this. http://wiki.secondlife.com/wiki/FollowCam

What was confusing for you in my post? The RLV code used now is not open source and a lot of code no longer works on the viewer up to date viewer.

FYI most actually find it disgusting. I also gave you a probable reason but you have not checked the perms of what you changed. This started with this 'Then I decided to update the box art (of all things) and so it's technically a new product in a new box.' therefor the fault is in that part. A simple test of dropping the script into a blank box and passing it will rule out a fault in that or those scripts.

Could be done with an object name, object desription or both and if they do not match its caput.

I no longer do RLV. Some of the commands have been changed and the person who changed them will not release the changes.

How about you look at the perms of what you used rather than the disgusting cussing. A simple texture incorrectly set will cause that.

Apart from the automatic abuse against LL for something you clearly have caused the issue is obviously in the thing you changed.

The minds of men never cease to re-inforce my view of them.

Suggest you start here http://wiki.secondlife.com/wiki/A_Basic_LSL_Tutorial