Difference between revisions of "LSL Protocol/LockMeister System"
| Line 134: | Line 134: | ||
|[[Image:lockmeister-mooring-pts.jpg]] | |[[Image:lockmeister-mooring-pts.jpg]] | ||
|} | |} | ||
NOTE: ltigh/rtigh were typos introduced during LM1 so for compatibility reasons we are keeping them as is. | |||
====Others==== | ====Others==== | ||
Revision as of 06:28, 9 May 2012
| LSL Portal | Functions | Events | Types | Operators | Constants | Flow Control | Script Library | Categorized Library | Tutorials |
LockMeister
The LockMeister System is a keyring of commands used for enhanced functions in bondage toys, its main function is to get the keys needed for particle chains, but as the protocol grow more and more commands are added. This protocol is maintained and designed by Kyrah Abattoir, IM her inworld if you have suggestions.
Features
- Simple to use
- Flexible
- Fully backward compatible
- Sensorless key grabbing (possible on child prims too) for particle chains (several mooring points)
- Boot/shoes animation overrider controlling (on/off)
- Color propagation in a lockmeister item set
How it used to work? (LMV1)
Basically, all LockMeister items listen on channel -8888
Its strongly recommended to use only the llWhisper function for sending the commands
When someone sits on a LockMeister compliant item, this one will sequentially send the ping messages to each of the mooring points it needs, for example for a St. Andree Cross we will ping the wrist and ankle cuffs, in our example we see we will have to send the messages lcuff,rcuff,llcuff,rlcuff (which are the ones for these points).
When a LockMeister attachment detects the message corresponding to itself in the channel -8888 it will answer by the same message completed by "ok"
'An item will send the message using this format:
message shape: <avatar key><command> example: "748bb591-0d9d-4907-8287-dc27b8267e24lcuff" (we ping the left wrist cuff attachment of the avatar whose key is positioned before the name of the attachment point, or command)
The concerned attachment will answer:
message shape: <avatar key><command>" ok" example: "748bb591-0d9d-4907-8287-dc27b8267e24lcuff ok" (the concerned object answer on the channel -8888)
In order to draw a chain of particles we need the key of the object. When we used the listener event to get the answer message, the listen event returned us the key of the object that answered in it's key id field. This is the key of the speaking prim, which should be the prim we need to attach the chain to.
How does it work now? (LMV2)
The LockMeister protocol version 2 (LMV2) is built over the initial protocol (LMV1) and is designed to allow scripters to create furnitures and attachments without needing a slave script in every anchor prims. Linden Labs declared that they wouldn't be supporting any method for sending chat from a root prim and making it come from a child prim ( no "llLinkSay(integer link_number,integer channel,string message )" for example. ), the LMV2 protocol adds an extra set of commands to get around this problem.
'An item will send the message using this format:
message shape: <avatar key><command>
example: "748bb591-0d9d-4907-8287-dc27b8267e24lcuff"
(we ping the left wrist cuff attachment of the avatar whose key is positioned before the name of the attachment point, or command)
The concerned attachment will answer:
message shape: <avatar key><command>" ok"
example: "748bb591-0d9d-4907-8287-dc27b8267e24lcuff ok" (the concerned object answer on the channel -8888)
We now have in the listen event 'id' parameter a key, we should start using it as a particle target, if the object is only LMV1 it will be the proper target id, but if the object is LMV2, this will most likely be the root prim of the object.
now we can use this id to send the lmv2 messages using llRegionSayTo()
LMV2 MESSAGES SHOULD ALWAYS USE llRegionSayTo() !!
'The item can now send an LMV2 message using this format:
message shape: <avatar key>|LMV2|RequestPoint|<anchor point>
example: "748bb591-0d9d-4907-8287-dc27b8267e24|LMV2|RequestPoint|lcuff"
The concerned attachment will answer (if it is LMV2 compatible):
message shape: <avatar key>|LMV2|ReplyPoint|<anchor point>|<anchor point key>
example: "748bb591-0d9d-4907-8287-dc27b8267e24|LMV2|ReplyPoint|lcuff|636bbccc-0d9d-4907-8287-dc27b8267e24"
If the target object doesn't support LMV2, we won't receive any answer, so it's important to start drawing the particles before the LMV2 reply comes. If the reply DOES arrive, we can grab the new target key and synchronise our particle system.
Complete List of Mooring Points
NOTE: THERE ARE NO TYPO ERRORS IN THE MOORING POINT NAMES (like ltigh/rtigh)
|
|
NOTE: ltigh/rtigh were typos introduced during LM1 so for compatibility reasons we are keeping them as is.
Others
- handle - type "leash handle" , this is useful for leashing to a leash handle.
- tether - type "tether point" , this is useful for leashing to some fixed anchor.
Special Commands
<avatar key>col<vector> - order a color change (used in LockMeister collars to tint the cuffs like the collar) OPTIONAL
ex: "748bb591-0d9d-4907-8287-dc27b8267e24col<1.0,1.0,1.0>" will say to an item able to understand it (color yourself in white)
<avatar key>booton/bootoff = commands sent by collar objects, asking that the shoes animation overrider be started or stopped
ex: "748bb591-0d9d-4907-8287-dc27b8267e24booton" activate the animation overrider
ex: "748bb591-0d9d-4907-8287-dc27b8267e24bootoff" deactivate the animation overrider
Amethyst extension commands (LMV1)
The following commands are not part of the main lockmeister protocol, but additions Amethyst Rosencrans made in her sold and free cuff scripts. They are here to document the extensions so others can utilize them.
<avatar key>target|point1|point2 = Connect a chain from mooring point 1 to mooring point 2 ex: "748bb591-0d9d-4907-8287-dc27b8267e24target|lcuff|rcuff" will create a chain from the left cuff to the right cuff
<avatar key>target|point = Remove a chain from mooring point ex: "748bb591-0d9d-4907-8287-dc27b8267e24target|lcuff" will remove a chain from the left cuff
<avatar key>texture|<texture key> = Change the texture of the chains used by the target command ex: "748bb591-0d9d-4907-8287-dc27b8267e24texture|1ffb37fa-2fc1-dbec-d8ea-0607583a03c6" will change the chain texture
<avatar key>gravity|<downward acceleration float> = Change the rate at which the chain particles move down ex: "748bb591-0d9d-4907-8287-dc27b8267e24gravity|0.5" will change the chain texture to move down half a meter a second
<avatar key>age|<age float> = Change how fast the chain particles move from point 1 to point 2 ex: "748bb591-0d9d-4907-8287-dc27b8267e24age|2.0" will change the chain texture to move the distance in 2 seconds
Cool Products extension commands (LMV1)
The following commands are not part of the main lockmeister protocol, but additions Henri Beauchamp made for use by his Cool Products (such as the Cool Collar). They are here to document the extensions so others can utilize them.
<avatar key>point here = Signals that anchoring point "point" just appeared. ex: "748bb591-0d9d-4907-8287-dc27b8267e24handle here" could be emitted by the on_rez event of a leash handle to signal the collars connected to the owner of the leash handle that they should connect to it instead of staying connected to the center of the avatar.
<avatar key>point gone = Signals that anchoring point "point" just disappeared. ex: "748bb591-0d9d-4907-8287-dc27b8267e24handle gone" could be emitted by the a leash handle when it is detached to signal the collars connected to it that they should unleash.
(unknown) extension commands (LMV1)
<toucher key>post ok = Signals that <toucher key> has touched an object. The toy will then issue an "<object key>handle" command to the object, which will return "<object key>handle ok" to activate the leash.
Note about message sending
- It is recommended to send the LMV1 "ping" messages through llWhisper so only close proximity objects will receive them.
- Now that llRegionSayTo() is available, it is strongly recommended to send "pong" messages through llRegionSayTo(), because of this, it is NOT recommended to have objects rely on "message snooping", because they won't be able to see message replies with llRegionSayTo.
- LMV2 Messages should ALWAYS be send using llRegionSayTo().
Seal Of Approval (optional)
The seal of aproval program is currently discontinued.
Example Scripts
Example Attachment Script
<lsl>//KDC sample LockMeister attachment version 1.1 // //NOTE: This script must be in the root prim of the object for working properly // Please ensure that you named the anchor prim properly too, this is the prim the script will look for // when sending LMV2 replies. // ... // in a general way this script is here as an explanation to the LockMeister System so ... WRITE YOUR OWN CODE!! // //KDC, kyrah design concept
string mooring_point = "lcuff"; //write here the mooring point you want to use
string anchor_name = ""; //write here the name of the child prim that will act as the anchor point, leave blank to use the root.
integer attach_control = TRUE; //TRUE if you want to control the attach point (and detach if attached on the wrong part of the body, else, FALSE
integer attach_point = ATTACH_LLARM; //write here the attachment point that need to be controlled //example : //left wrist/arm = ATTACH_LLARM //right wrist/arm = ATTACH_RLARM string attach_text = "this cuff must be attached to the left forearm"; //the text to display when the object detach itself default {
attach(key id)
{
if(id != NULL_KEY)
llResetScript();
}
state_entry()
{
if(llGetAttached() != attach_point && attach_control)
llRequestPermissions(llGetOwner(), PERMISSION_ATTACH);
else
llListen(-8888,"","","");//open the lockmeister channel
}
listen(integer channel,string name,key id,string message)
{
if (message == (string)llGetOwner()+ mooring_point)//did we get a V1 ping message for us?
{
llRegionSayTo(id, -8888, (string)llGetOwner()+ mooring_point+" ok");//answering it
}
else if( llGetSubString(message,0,41) == ( llGetOwner() + "|LMV2|" ) //did we receive a V2 command?
{
list params = llParseString2List( message, ["|"], [] );
//key destination = llList2Key( params, 0);
//string protocol = llList2String( params, 1);
string command = llList2String( params, 2);
string lm_point = llList2String( params, 3);
if( command == "RequestPoint" && lm_point == mooring_point)
{
//This is a request for us
//If no anchor name is specified, no need to send LMV2 message as the pong we sent was the proper key.
if( anchor_name == "" )
return;
//Otherwise, we loop through the link set to find the anchor prim and reply.
integer i;
for( i = 1; i <= llGetNumberOfPrims(); i++)
{
if( llGetLinkName(i) == anchor_name )
{ //If this is our anchor prim, we reply
llRegionSayTo( id, -8888, llDumpList2String( [llGetOwner(), "LMV2", "ReplyPoint", lm_point, llGetLinkKey(i)], "|" ) );
return;
}
}
}
}
}
run_time_permissions(integer perm)
{
if(perm & PERMISSION_ATTACH)
{
llOwnerSay(attach_text);
llDetachFromAvatar();
}
}
}</lsl>