LockGuard V2 Open Source Release

As promised, the LockGuard V2 Script has been open sourced.

http://secondlife.com/badgeo/wakka.php?wakka=exchangeLockGuard (follow the link therein to the open source code).

The Wiki entry might not be the cleanest, but you know. I've tried to include all necessary information.

If you want the actual V2 package (which contains a little more info plus ready made V2 (modifiable) test objects) message me in-world and I'll send one to you, or you can drop by the Dictatorshop at http://www.slurl.com/secondlife/knieff/223/233/169 and pick up your copy there.

And I apologize in advanced for my style of coding, it's old MUD-server C style coding.

Lillani - what can I say - awsome and thanks. This solves all problems I had with understanding LockGuard fully and the list for recommended tags is ... impressive. Restraint builders will be hard pressed to come up with a set, that covers them all ... and I do not envy the victim wearing them.

Only one small thing might be missing - not really sure if it is *neccessary* - I need to experiment a bit first - but I think a *ping* command might be useful. Depending on how you want to chain up someone you might like to know which item tags are available first, then deciding which ones to chain. As far as I understand it, in the current version this is not possible.

Well - I freel admit that most furniture designers will probably not make a design that is dynamic and responds to the items worn but such a ping command could also be used to check if the avatar is wearing LockGuard items at all and could either offer the avatar a basic set from the furniture's inventory or tell the avatar to get a set from a nearby dispensor.

The use for the availability check is probably more useful than the other option (dynamic chaining) - unless, of course, I overlooked how to check for the existance of LockGurad compatible items worn by the avatar with the available and documented commands:

link, unlink, gravity. life, color, size, texture

The availability of multiple tags is a great new invention and I want to thank you yet again for your great contribution. Can't wait for the new kit ...

EDIT: Looking at the Open Source code I see a ping command - please disregard the last paragraphs.

Hey HtF..... thank you for the compliments on LockGuard.

There is actually a ping command for determining of an item exists, and there is also a free command to determine whether the item has an active particle chain or not.


Send this string for a ping:

lockguard <avatarkey> <itemtag> ping

Which would respond with: lockguard <avatarkey> <itemtag> okay


And send this string to determine if the chain is free (a freed chain is not linked) or not:

lockguard <avatarkey> <itemtag> free

Which would respond with: lockguard <avatarkey> <itemtag> yes/no

EDIT: I just noticed your edit, silly me!

Hi Lillani,

well - reading your post is actually much better than reengineering from the script how to use the commands, so I say thanks again.

No edit to this one, promise!

Good ting releasing open source. but still not understand way go lockguard.
i stull wud use lockmeister. sins used it xxx times befor.

The difference between LockGuard and LockMeister - as stated numerous times in other threads - is that LockMeister is a "mere" protocol whereas LockGuard is a full fledged chaining system.

When you wish to use LockMeister you (currently) have to write the whole particle system yourself - from scratch unless someone gives you a script for it. Scripting with LockGuard is usually only onle line of code per restraint (or less if one ring attaches to more restraints than one) - ONE LINE! No particle system, no worries.

So - even when you are not yet a competent scripter you can create great things with LockGuard - with LockMeister you have to get proficient in mastering the particle systems first, do your own textures for the chain links, etc.