LSL Protocol/Restrained Love Open Relay Group/ORG Introduction

ORG - The OpenRelay Group

• • • THIS IS A WORK IN PROGRESS, NOT LINKED ***

ORG, the OpenRelay Group, are scripters and builders of Restrained Life Enabled furniture and devices. ORG wants to see the RLV Relay Spec grow and evolve to meet the needs of ALL users, even to meet needs OUTSIDE the capabilities of the RL Viewer.

The purpose of an ORG Enhanced Relay is two-fold: First, to capture and validate the necessary commands to pass to the RL Viewer to enable its functionalities for whatever purpose. Second, to do the things that the Viewer DOSEN'T (or WON'T) do that may have use in the RLV environment, but to do it in an OPEN, DOCUMENTED form to avoid a confusing flood of 'secret', or 'special purpose' relays. Any extension documented here are, by definition NON-PROPRIETARY and open for ANYONE to use in their products. We specifically REJECT the "not invented here", closed minded position. There are already several builders using the RLV for NON-BDSM solutions to problems, the RLV is slowly becoming 'mainstream' and we can help that process along.

The job of a relay is to deliver a properly formed "llOwnerSay" command to the RLViewer.. whatever else done in the relay proper is to enable features the viewer can't. The viewer starts at "llOwnerSay".. the viewer starts at "llOwnerSay" anything else is up to us, and it's our responsibility to make sure that EVERYONE knows what and how we do it and make it easier for them to do it. From a furniture builder's perspective, the more standard the set of features, the easier it is to design furniture and other devices to enhance the RLV-user's experience, no matter if it's BDSM or any use. Imagination is a good thing that should be encouraged.

We will say that not EVERY extension may be accepted to ORG. If it's dangerous, uses undocumented hacks to the viewer and are not user friendly, then this may not be the place. But we WILL discuss every suggested extension and consider how to make them more compatible to the user and the viewer.

One caveat for our discussions. Personal, ad-honimen attacks are NOT WELCOME and NOT PERMITTED. We're here to HELP BUILDERS, not BUILD EMPIRES. No one is REQUIRED to use ANY of these extensions, but EVERYONE is WELCOME to do so. We want to help people avoid 're-inventing the wheel' and we want to do so in the spirit of cooperation, not control.

We plan to make x-tensions to the existing relay spec as metacommands, adopting the !x- convention. Other x-tensions that might be implemented in a viewer could use the !x- convention or adopt some other prefix such as #. The group will decide how best to proceed.

The relay spec is silent with respect to unknown commands and the behavior has been dependent on each relay maker's whim's, e.g., they may not even be ko'ed. So you can NEVER ASSUME the extensions to always be recognized or even acknowledged. We do SUGGEST that any ORG Enabled relay or script respond to the !impversion with a string that contains:

           "*ORGEnabled\extension\extension\..."
           

so you can know which extensions the relay you are talking to are supported. Alternatively, we may develop an x-tension that returns the supported x-tensions.

Some example x-tensions (!x-vision has been discussed for a while, the others need definition) are:

!x-vision - provide a means of obscuring the subjects vision WITHOUT having to muck about with extra wearables. Originally conceived as a MOUSELOOK ENFORCER/PUNISHER and REQUIRES a HUDstyle relay.

'!x-gender - allow the users to set their defined sex, be queried by a device AND SET BY THE DEVICE.

!x-species - ditto for species.

!x-freeze - stop the victim dead in their tracks. Effecively disables the arrow movement keys, jump and crouch. Sure you can do it other ways, but this keeps down extra script/attachment counts. Nice for 'area effects' (prison lockdown perhaps), cages (hold them in place so you can open the cage and take out one specific.

Come join us and help us make our Restrained LIfe, the best life.