Quintin Patel
Registered User
Join date: 3 Jul 2004
Posts: 1
|
11-16-2004 15:39
Okay, I am at a complete and utter loss - how do I use llRemoteLoadScriptPin? The help file, the wiki, and google are all of no help, and the same can be said of the live help, all of my groups, and any of the Lindens I've been able to talk to (no offense)... My current project relies on copying/starting a script, and since there's apparently not a way to start a script that's been copied, this is my only choice. I'm not asking anyone to write my script for me, just for an extremely simple example of the proper way to use it and assign the pin on the other script; all of my attempts have been complete failures with the sending object saying I'm illegally trying to send the script
|
Water Rogers
Registered User
Join date: 1 May 2003
Posts: 286
|
11-16-2004 16:55
Make 2 objects next to eachother. Name one object "Send" name the other object "Receive". In the "Receive" object, make a new script, and put this in it: default{ state_entry(){ llSetRemoteScriptAccessPin( 111 ); } } That will set the pin on your receive object so your send object can send a script to it. now in the "Send" object, make a new script, and put this in it: default{ state_entry(){ llSay( 0, "Sup, av" ); } touch_start(integer total_number){ llSensor( "Receive", "", 12, 100, PI ); } sensor( integer s ){ llRemoteLoadScriptPin( llDetectedKey(0), "New Script", 111, TRUE, 1 ); } } Ok, now touch your send object. What happens is your "Send" object will send the script named "New Script" over to your "Receive" object (and since we have a state_entry in our New Script, it will say "Sup, av"  . This is just a practical example for you to kinda learn as to what it does. There are much more useful reasons to use this other then this. And here's the explanations taken from the Linden Scripting Reference Guide: A.227. llSetRemoteScriptAccessPin
llSetRemoteScriptAccessPin(integer pin);
If pin is set to a non-zero number, the task will accept remote script loads via llRemoteLoadScriptPin if it passes in the correct pin. Othersise, llRemoteLoadScriptPin is ignored.
-and-
A.179. llRemoteLoadScriptPin
llRemoteLoadScriptPing(key target, string name, integer pin, integer running, integer param);
If the owner of the object this script is attached can modify target, it has the correct pin and the objects are in the same region, copy script name onto target, if running == TRUE, start the script with param. If name already exists on target, it is replaced.Hope this helps. --Water
_____________________
From: Philip Linden For the more technically minded - the problem is actually NOT the asset server (or 'asshat' as you prefer to affectionately call it herein).
|
Strife Onizuka
Moonchild
Join date: 3 Mar 2004
Posts: 5,887
|
11-16-2004 18:14
yeah, i've been using them for a good long time to clean up ugly messes left by rezzers.
_____________________
Truth is a river that is always splitting up into arms that reunite. Islanded between the arms, the inhabitants argue for a lifetime as to which is the main river. - Cyril Connolly
Without the political will to find common ground, the continual friction of tactic and counter tactic, only creates suspicion and hatred and vengeance, and perpetuates the cycle of violence. - James Nachtwey
|