Moon Corrigible

Oh my gosh that's brilliant!!!! You all are amazing!!

Yes, exactly - I just need to find them once and have it report it's position back to the rest of the script. You are all are so awesome! Honestly that llSensor script is SO much more elegant than anything I would have come up with. THANK YOU!!!!

I'm just a little worried that there might be more than 16 scripted objects in the vicinity, and that the sensors might not find it then. But honestly I have no idea how realistic that worry is. Dumb question - would running two sensors (one for each) take up less script resources? I read that each llSensor will return up to 16 responses and I'm wondering if that would be overly taxing? Thanks again!

I apologize, I don't know the correct terminology. I'm using an llSesnor and I would like it to detect both objects with the name "Left Corner Setter" and "Right Corner Setter". Is there a way to use a character or code to to get it to detect anything with the words 'Corner Setter' in the name? Thanks!

I guess I've just never used this in a capacity where the agent wasn't actually around in one way or another so I've never run into the problem. Thanks for the info!

So it does.. I was thinking llName2Key

Holy macaroni that worked: key name_key_query; key back_again; default { state_entry() { llListen(1, "", NULL_KEY, ""); } listen(integer channel, string name, key id, string message) { name_key_query = llRequestUserKey(message); } dataserver(key queryid, string data) { if(name_key_query == queryid) { llSay(0, "That key is: " + data); back_again = llRequestAgentData(data, DATA_NAME); } else if(back_again == queryid) { llSay(0, "So the name is: " + data); } } } [08:33] Object: That key is: f70d9f76-1d94-4fd9-9535-ab9d3bab51ba [08:33] Object: So the name is: Moon Corrigible I still don't understand why llKey2Name didn't work but I'll take my victories where I can get them!

I used llRequestUserKey to get the key.. did you mean llRequestAgentData to get the name instead of llKey2Name?

I can not for the life of me figure out what I am doing wrong here. Why doesn't this work? key name_key_query; default { state_entry() { llListen(1, "", NULL_KEY, ""); } listen(integer channel, string name, key id, string message) { name_key_query = llRequestUserKey(message); } dataserver(key queryid, string data) { if(name_key_query == queryid) { llSay(0, "That key is: " + data); key handle = (key)data; llSay(0, "So the name is: " + llKey2Name(handle)); key other_way = llList2Key([data], 0); llSay(0, "or perhaps this will work: " + llKey2Name(other_way)); } } } These are the results I get: [08:04] Object: That key is: f70d9f76-1d94-4fd9-9535-ab9d3bab51ba [08:04] Object: So the name is: [08:04] Object: or perhaps this will work: I get the correct numbers for the key just fine and dandy but I can not get llKey2Name to give me the name back again. Granted I could just store everything as a strided list, but that seems inelegant at best. Anyone have any idea what I'm missing? Thanks in advance!!

So after two days of poking at the script frenetically and tearing apart every script I could find, I decide to go see if maybe other people have done it differently .. which is when I realized that that funciton doesn't work for me with anyone's script.. ever.. even if it works for other people.... and THIS boys and girls, is why you grab a bright shiny new RLV interface every time. DOH! Thank you anyway!

I am loosing my mind. The rest of my RLV scripting works peachy keen. All the force sits, the controlling communications, the playing with items - all works fine. But for some odd reason I can NOT get the strip command to work for the life of me! I'm using llSay(-1812221819, "Strip,(person's key),@remoutfit:gloves=force|@remoutfit:jacket=force|@remoutfit:pants=force|@remoutfit:shirt=force|@remoutfit:shoes=force|@remoutfit:skirt=force|@remoutfit:socks=force|@remoutfit:underpants=force|@remoutfit:undershirt=force|@addoutfit:gloves=n|@addoutfit:jacket=n|@addoutfit:pants=n|@addoutfit:shirt=n|@addoutfit:shoes=n|@addoutfit:skirt=n|@addoutfit:socks=n|@addoutfit:underpants=n|@addoutfit:undershirt=n) I thought the length may have been an issue so I tried llSay(-1812221819, "Strip,(person's key),@remoutfit:jacket=force). That didn't work either. For contrast llSay(-1812221819, "Force Gag,bade0deb-45ab-47be-be1b-c5f8f3417e66,@attach:~MSBallGag=force"); works great. Anyone have any clue what I am doing wrong? Thanks in advance!!

Oh awesome!! Thank you!!!!

I have the feeling I'm missing something blatantly obvious .. not an uncommon occurrance! I've got a pretty standard RLV cage and I'm trying to put in that nifty little feature where, if the subject is locked into the cage, when they relog the cage grabs them again. Is there a way to do that OTHER than using an llSensor? That just seems so laggy but I'm darned if I can see a different way. Thanks in advance!!

At least now I know what to call it!! lol THANK YOU!!

I'm so lost I can't even figure out what to call this! When you edit an object an click to make the object emit light - this would be PRIM_POINT_LIGHT in the parameters - to the right of the box where you determine the color of the light emitted, there is a box where you can use a texture to shape the beam of light emitted. I LOVE this but I can not for the life of me think of what to call that box and I can't seem to find it in the wiki. My end goal is to find out if this can be changed via script. llSetPrimitiveParams(PRIM_POINT_LIGHT) does not have a parameter for it and I'm darned if I can think of another way to access it. Any help is appreciated!! Thanks!!