Open Source LockMeister Script Kit

I have a basic set of LockMeister Scripts and I am considering making them open source and distributing them in world. I have an odd style of coding, so I am looking for other scripters who can help me review and refine the code for this purpose. From what I can see, the code requires several scripts that I have.

Sit On Me! - Broadcasts the UUID of an avatar sitting on the poseball in which it resides.

LockMeister Ping - A script that recieves the Sit On Me! status and pings the LockMeister Cuffs identified in a notecard, and listens for the responses from said cuffs. When those responses arrive, it relays them to the object via linked messages so the LockMeister Chain Scripts can do their thing.

LockMeister Chain Script - The script that sets the Particle Perimeters and awaits a link message from the LockMeister Ping Script identifying the target UUID that it is to fire the particles to. When that message comes, it fires the particles off at the identified target, until Sit On Me! returns a NULL_KEY result, at which point, it turns off the particles it has so fired.

LockGuard has been given the following "features:"

-Notecard configurability, including Particle Configuration.
-"Drop In Scripts" which are notably (No Modify).

The intention of this project is to create a series of Open Source LockMeister Scripts that emulate the Closed Source LockGuard Scripts. The thing I have noted most when discussing the two protocols with new coders is they're claiming LockMeister is too difficult to use becuase they can not get LockMeister Scripts. My argument would be that if we make an open source set of LockMeister Scripts, then perhaps we will be able to give people scripts that they can drop in to their products to make them LockMeister Compatible, while also allowing them to view the scripts and learn from them how they actually work.

Please help me on this project by helping me develop and refine my source scripts and distributing them freely where ever we can. We do not need to have an invaluable, open source standard such as LockMeister replaced by a closed source standard such as LockGuard simply because LockGuard provides scripts and LockMeister does not.

Could be probably useful to contact the system author, so the scripts could be maybe included in the relevant Wiki page? ^^;; (http://secondlife.com/badgeo/wakka.php?wakka=exchangeLockMeisterSystem)

hello, it's me, personally i am all for making lockmeister more accessible, my main fear was that it act as a "value maker" for cheap designers if i released a "plug and play" script . But well on the other side it need to spread more ^_^

i would be happy to have a look at the scripts you talk about if i can give some help for optimizing and lag reduction.

It would seem to me if you supervised the script development as best as you can, perhaps you can help us make sure the overall script set was very efficient.

I understand your concern about LockMeister becoming a "value maker" for cheap designs. My product is "LockMeister Compliant" because you have not personally given me approval of it, so I daren't say "LockMeister Approved."

Perhaps we can come up with a way to make a list of "Approved" products so we can all look for products that claim approval without actually being approved? Also, we might be able to find some recourse we can do to people who try to sell unapproved LockMeister equipment as approved equipment?

We can sort that all out. I gave you a copy of the LockGuard Build Kit to give you an idea of my objective, and the three base scripts I have provided that I am open sourcing.

Perhaps we can see what we can do to prevent LockGuard from overrunning LockMeister in the New Developer Market.

Same for me... I'm waiting for the LockMeister compatible status myself.. For several weeks now...

That isn't helping spreading the word of LockMeister either, tbh.
My items are both LockMeister and LockGuard compatible, and with all respect, the creator of LG is much faster in response then LM's is.
I'm not using the LM Logo or whatever there is lying around to show something is compatible anyway with LM tho.

I'm sorry, but as a scripter, when I ask something, I cant wait for weeks myself and I decide to go on with the next thing.

soryy for all that i made myself a promise to deintoxicate myself from SL , thus my very little presence the last 2 weeks. COnsidering i loggerd in sl every days since 2 years i can call that addiction hm?

That would indeed classify as an addiction. So how is detox going?
*smiles*
You should stay of the forums as well if you want to become "clean", otherwise SL will still have its influence...

I'll be the first to say Lockmeister is not a bad system, I own almost every piece of Lockmeister furniture worth buying, and have a lot of respect for KDC (another place I've shopped until I dropped). From a buyer's perspective, it's absolutely fabulous!

And as the creator of LockGuard, I'm all for the improvement of Lockmeister, I absolutely encourage it..... in fact, if the existence of LockGuard is the reason which drives people into making Lockmeister become more accessible to the masses and easier for *everyone* to use, then LockGuard has achieved more than I could have hoped. After all, my original goal was to make particle chains easy, simple, and easily accessible to "everyone and anyone". So, Kyrah, get on-board, get involved, and help Lynn in her quest to bring Lockmeister to everyone and help make the bondage builder world a little friendlier..... you have nothing to lose by doing it, and I'm sure a lot of people will thank you for doing so. Imagine all of the people you will help by involving yourself and promoting the developement of Lockmeister, there's no reason for you not to do it.

However, at the same time, I will also point out LockGuard will hold its own and remain a solid system simply because of the basic, underpinning design of the differing systems. LockGuard is modular, designed for "on the fly" expansion, user adaptability and user customization, and it's far from being limited to only attachments. I've seen LockGuard used for everything from creating bathtub plug chains to chains on a drawbridge, to elaborate spider web designs.... with no modification of the system. When people start to use your system for off-the-wall items, you know you're succeeding. And I do love the silly things people do with LockGuard..... I mean, a bathtub plug chain? That was just hilarious (might I mention it was GIANT bathtub, at that)!

Also, I'm not against offering Lockmeister compatibility in the LockGuard Builder, I've offered it before but never received a response. Heck, if Kyrah is willing to drop *all* restrictions on the distribution and use of Lockmeister, I'm willing to combine them both into one, powerful suite of tools which combines the advantages of both systems into one killer sytem which is backwards compatible with both. Standing alone, Lockmeister and LockGuard are both very powerful systems..... but combine them naturally together in one streamlined system..... absolute Domination. I look forward to LockGuard and Lockmeister standing side-by-side, hand-in-hand, giving power to the people, but that decision.... is up to Kyrah.

Finally, if some people fear LockGuard is becoming "popular" among the new builders, it will be interesting to see how they react with the new and upcoming features in the next LockGuard release..... it will be an evolutionary step forward in the system, like going from monkey to man (while maintaining 100% backward compatibility).... and of course, no longer limited to particle chains, as LockGuard is moving away from being a particle chain system to becoming an entire "furniture design suite" covering all aspects of building.

Um, your product is either Lockmeister compatible or it isn't depending on how it functions. If you mean you're waiting for the approval logo, that's fine, but you don't need to wait for anyone else to make your products Lockmeister compatible, you just make them so.

You can advertise them as such, too. Saying a product is "X compatible" is a simple statement of fact, not a statement of endorsement, no one can deny you the right to advertise that if it's true. I used to use a Hayes-compatible modem on my IBM PC-compatible computer all the time, and I'm sure neither IBM nor Hayes endorsed my use of their competitors' products.

If you want the logo, great, go for it, but you definitely don't need anybody's approval to make, sell, and advertise Lockmeister compatible products as such. You just can't call them "approved", for whatever that's worth.

As for LockGuard, I still don't see any documentation for the protocol up on the Wiki...

Complete documentation for LockGuard is included in the Scripter Dev Kit, including script examples of how to command the LockGuard library.

In the meantime, I've added a bare bones explaination of how to use LockGuard to the Wiki, which I'll be updating throughout the coming week. It was an oversight on my part to leave it out of the Wiki for such a long period of time, and I do apologize for the overdue entry.

I dont get the point of the whole discussion.

Kyrah Abattoir doumented the Lockmeister-Protocoll very well at the wiki and attached a sample-Script to it - ok, its not the friendliest of all scripts, but it works and shows how the server and the client works.. Lockmeister is not a bunch of business-secrets - its just a protocoll everyone can use.

Lillani Lowell, the creator of LockGuard, stated, that LockGuard is documented too and there are Scripting-Examples. And - thats the point - there is a ready-to-use Plug and Play-Kit, which everyone can put into your attachments and Furniture with an ease! It works quite well - i used it too.


Well ... If someone whats to make (read: create) lockmeister-stuff, there is really enough documentation on the wiki to get the server (furniture) and the client (cuffs) running.

If someone - who cant script - whats to make bondage-tools, he/she can use Lockguard.

So, where is the point?
Creating Scripts to learn from: Use the wiki.
Creating Scripts for the lazy/impatient *: Use Lockguard.


Just my 2c,
Ninn


ad Lillani Lowell: I dont get it why you would need Kyrah Abattoir to talk to Lynn Kukulcan to create something you already created (talking about lockmeister-compatibility). :-?

ad Lynn Kukulcan: You are missed the Scripts for the Attachment.


* no offend to Lillani Lowell or their customers.

LockGuard isn't about being lazy/impatient though..... there's some amazing builders in Second Life who work *hard* at building, but they just can't script, or they don't have time to script because they concentrate on building. I know a few great scripters who've adopted LockGuard simply because they don't want to re-invent the wheel, and at the same time don't want to deal with Lockmeister. LockGuard can also be used on the scripter level, without the builder. The Builder is the non-scripter variety, the Script Dev Kit, on the flip side, is designed with scripters in mind.


No, no, what I said was Kyrah should get onboard with Lynn to help her create an open source version of Lockmeister that anybody can use (make it simple, make it easy, make it plug and play!).

And thanks for the compliment on LockGuard, by the way. I'm glad you found it worked well, and I hope you'll try the next release and be pleasantly surprised by the new features.

Indeed, I meant I was waiting for the Approved part so I could show the logo. I do advertize being LM compatible.

Compatibility. As opposed to wanting to learn how to script, some people might want to just create items which allow customers to use them, no matter if the gear these customers own is Lockmeister or Lockguard compatible.

Nothing wrong in making it easier for them, by providing 'drop-and-play' scripts that can cover Lockmeister part.

i tried to keep lockmeister as a simple guideline related to I/O communications between attachments/fixed points, it was initially meat as a scripter document, kind of bdsm chaining language, like html is an hypertext definition language.

My base scripts are just that, basic scripts, their goal is to show a working implementation of the lockmeister protocol. by staying simple it allow the scripter to adapt it to more complex behaviors and to make totally unexpected things. The more pre-chewed material will be provided the less peoples will search and learn.
As for the "builders that want to "enable" their stuffs, i am sorry i am a builder too, I always wrote my scripts myself and i don't think i am an exeption.

its one thing to want to spread something but then look in 10 months from today into a cuff set made by a non scripter: one lockmeister script, one lockguard script, one color changer script, one animation overrider,... what else?

it's this kind of behavior that make 90% of the wasted script resources in SL, scripts are plug and play usually, yes, but perf wise it is the worst thing you can do.

Hmm i suppose you can look at it this way, but i don't think this is necessarily the most practical approach. That is, i don't see much benefit in requiring a talented animator or a builder to also be talented scripter just so they can fully utilize their primary ability. Yes, some builders may have what it takes to do both. Good for them, the extra potential will allow them to stand out. But for these who _don't_, i'd rather they use efficiently wrote solutions from a 3rd party that actually *know* what they're doing, than try to 'roll their own' and wind up with stuff that may be one script (but may as well be 10) that'll eat more resources than example combination you mention, just to do the same thing.

To encourage people to search and learn is one thing, to require them do that just so they can do something they're interested in is another. Am not forced to learn programming, OS api, openGL and graphics theory if i want to make 3d animation or paint a 2d picture with my tablet. I can get ready-to-use applications that'll allow me that, and which were built by people who together possess few dozen years of experience and often skills which i don't even have in the first place. Forcing me to play catch up with them just so i can *maybe* get to my original goal would be cute, but extremely ineffective.

While I suspect it's a moot point now that LG is open sourced, I have to wholeheartedly agree, Joannah. For the efficient use of both the scripter's time and the sim's performance, it's better that each scripter not re-implement particle chains afresh for each application.

If I had nothing better to do and lived long enough, I could write my own X server from the protocol spec, too--and I wonder how that would perform.