|See in this page: Exceptions||Force Sit||Restrictions||Folders|
To call the RLV menu:
NOTE: RLV (Restrained Love Viewer) is a set of permissions coded into the viewer, that allows other avatars limited control over some viewer functions. There are several approved third party viewers that allow you to enable / disable RLV. Among the most popular for many users are Firestorm, Restrained Love Viewer, and Singularity.
Please remember that one of the most basic safety features about RLV is your ability to turn it off and on in the viewer. Any RLV restriction can be cleared by turning off RLV and relogging; or logging on in the official SL Viewer.
On / Off
Toggles RLV on and off in the collar (not in the viewer). The collar lock is not affected. Turning RLV Off in the collar does disable the collar relay and turns off access to the RLV menu.
[prefix] rlv on/off
Clears all collar RLV restrictions, including those enforced by the relay. Available to anyone with collar access but the wearer unless self owned.
Gives a list of occupied attachment points with the names of the objects attached to each. Pressing the button with the corresponding name will detach the item (unless there is a lock on detach or Dress is restricted).
[prefix] detach (opens the “detach” menu)
RLV SETTINGS (new in V 7.4)
This menu contains Exceptions, which lets you set Exceptions to RLV restrictions for Owners and Trusted; plus allows you to set values for Camera and Chat Restrictions.
Here you can set Exceptions to RLV restrictions for Owners and Trusted. Exceptions allow owners and trusted to communicate with you and teleport you when these are otherwise restricted. When the boxes are checked the Exceptions are enforced.
Default Exceptions: Owner is exempt by default.
List of Exceptions:
IM exempts owner/trusted from a block on the wearer’s ability to send IMs.
RcvIM exempts owner/trusted from a block on the wearer’s ability to receive IMs.
RcvChat exempts owner/trusted from a block on the wearer’s ability to read local chat.
RcvEmote exempts owner/trusted from a block on the wearer’s ability to read emotes.
Lure exempts owner/trusted from a block on the wearer’s ability to accept a teleport offer.
refuseTP exempts owner/trusted from the wearer’s ability to refuse teleport offers. When active, the wearer’s viewer automatically accepts a tp offer from an owner. More commonly known as “force TP.” On by default for owners, must be set for trust.
Opens a menu of nearby objects on which the wearer can be forced to sit. When the wearer is force sat, forbid stand is also enforced. (in V 7.3 the Strict setting did this)
[UNSIT] (previously GETUP) unsits the wearer and also revokes forbid stand.
[prefix] sit (forces the wearer to sit and forbids stand)
[prefix] unsit (forces the wearer to stand and allows stand)
Opens a menu of restrictions and macros which are shortcuts to apply groups of restrictions. When the boxes are checked, the restrictions are active. Ability to manage macros is new in V 7.4. Each button gives you the option to add, replace, or clear the restriction or macro. Add will add the restriction to your existing restrictions if any. Replace will replace existing restrictions with the one on the button. Clear will end the restriction.
Frequently used restrictions are on the same page as the macros. They include:
- Hear: (single restriction)
@rcvchatrestricts wearer’s ability to receive chat.
- Talk: (single restriction)
@sendchatrestricts wearer’s ability to send chat.
- Touch: (single restriction)
touchworldrestricts wearer’s ability to touch objects.
- Dress: Restricts the wearer’s ability to add or remove attachments and clothing layers. [prefix] forbid dress / allow dress
- Stray: Restricts the wearer’s ability to accept teleport offers, teleport to landmarks and map locations, sit on an object from a distance greater than 1 meter from the object center; and teleport to a point on the landscape. [prefix] forbid stray / allow stray
- Rummage: This group restricts building abilities including: edit, open the inventory window, rez objects, view scripts and textures. [prefix] forbid rummage / allow rummage
- Dazzle: uses RLV to enforce the debug setting “RenderResolutionDivisor” and create a blurred vision of the environment on the viewer screen. [prefix] forbid dazzle / allow dazzle
- Daze: This group restricts navigation data. When active the wearer cannot see names, hovertext (group tags), minimap, world map, or locations at the viewer top menu. [prefix] forbid daze / allow daze
- IM: Restricts ability to send and receive IMs.
Here you can save a group of restrictions as a new macro, and Delete an existing macro.
List of individual restrictions are also grouped for convenience. These can be applied and removed by toggling the button.
- Chat: Includes individual restrictions having to do with local chat, IMs and gestures.
- Show/Hide: Includes individual restrictions that hide Locations, Maps, and hovertext.
- Teleport: Includes individual restrictions involving teleportation.
- Misc: At the moment just one miscellaneous individual restriction,
@acceptpermissionwhich automatically accepts all attach and take control permission requests.
- Edit/Mod: Includes individual restrictions having to do with rezzing and editing objects, textures, scripts, and notecards.
- Interact: Includes individual restrictions having to do with touch.
- Movement: Includes individual restrictions having to do with Running, Flying, Jumping, Sitting and Standing.
- Camera: Includes blurring view, unlock camera, camera minimum and maximum distance.
- Outfit: Includes individual restrictions on adding and removing clothing and attachments.
This button in RLV brings up the relay menu. See Relay for more. To call the relay menu:
Folders is used to add, and detach individual items to and from existing worn outfits. To add and detach items, the items or links to them must be in an #RLV folder.
To call this menu:
Making the #RLV Folder: The wearer creates a top folder in inventory named #RLV for this menu to work. The name must be exactly these four characters [#RLV] and it must be a top folder, not a sub folder of any other folder in the inventory. It allows users and scripted objects to force wear the clothing and attachments contained in those folders.
Once you have your #RLV folder set up, make folders in #RLV for attachments you want to allow other avatars to force you to wear. These usually include items like cuffs and gags (to force wear complete outfits, see .outfits below).
Sample folder arrangement: #RLV > Gags > Ringgag Ballgag where the ringgag and the ballgag are each in their own folder, inside the “gags” folder, inside #RLV.
Note: Stripping works differently than force wearing. An RLV strip command targets the attachment point or layer on the avatar and does not search #RLV folders in inventory.
Actions to apply to each folder or subfolder include:
- Add all : adds the entire contents of the folder including its subfolders.
- xLock att. / all: Prevents the wearer from attaching the contents of this folder. This toggles to an exception button which allows a folder to be worn if its parent folder is locked; and toggles once more to clear the restriction.
Folders and subfolders may be worn by chat command, for instance:
[prefix] &ringgag adds the contents of the folder named ringgag to the wearer.
[prefix] &&gags adds the contents of the folder named gags and all its subfolders.
[prefix] +ringgag wears the contents of the folder named ringgag
[prefix] ++gags wears the contents of the folder named gags and all its subfolders
[prefix] -ringgag removes the contents of the folder named ringgag.
[prefix] –gags removes the contents of the folder named gags and its subfolders
Changes for V 7.4 (beta)
- Configure: Allows Wearers and Owners to set access to Folders separately.
- Detach: Detach is now an allowed Action in folders.
In V 7.3, Outfits uses Replace to force outfit changes. Included in Outfits can be a folder named .core where you place links or copies of only those things you always wear, never exchange, and never take off. This folder will “protect” these items by force wearing everything in the folder every time you change outfits.
To call this menu:
This menu requires the wearer to set up a folder inside #RLV, precisely named .outfits . The dot preceding outfits is required.
Inside this folder make folders for your named outfits which you have set up using the SL Edit Outfit function. Then drag in the links from the outfits folder into the new folder. The outfit names will appear as menu buttons in RLV > Outfits and can be force worn using the SL Replace function. Make sure the outfits include all necessary parts of your outfit except possibly required system layers that cannot be removed. Do not include your locked collar in the outfit folder. Locking the collar ensures that Replace will not remove it and deleting the link to your locked collar prevents accidents like doubling your collar or wearing an outdated version.
- To “strip” using outfits: Inside your .outfits folder make a folder and name it something like Naked. Include in there what you want to be wearing when stripped, including mesh body, hair, mesh eyes, etc. Users can then strip you by force wearing your “Naked” outfit!
Changes to Outfits for V 7.4 (beta)
- Outfits is optional and has been moved to the Apps Menu.
- Changes to .core: the .core folder now issues a temporary lock on detach when Outfits is used.
- Outfits no longer uses Replace. It will only detach items that are defined in another folder or outfit, and add the items in the Outfits folder. You no longer have to include the complete avatar in each outfit. Lock Core: Lock the Core folder to enable a temporary lock on detach of items in .core when Outfits is used.
- When .core is locked, you cannot change the contents of the folder in the inventory window. Unlock it to add and remove items to the .core folder. Configure: In Configure the wearer and owner can set access for controlling the Outfits menu separately. Whether or not the Wearer can use outfits is also configurable. “Jail” allows the Outfits menu to browse the entire #RLV folder instead of just Outfits. “Strip All” allows Outfits to detach items that are not in a defined outfit folder.
Using a (nostrip) tag:
- (nostrip). You have items that you do not wear all the time but when you are wearing them, they should never be stripped; such as hair. The best way to prevent this is to append a (nostrip) tag to the end of the folder name or item name:
[foldername] (nostrip)Note for V 7.4 (beta): You should not need to use (nostrip) if your folders are set up for V 7.4 with a lock on the .core folder. Items that are not in #RLV will not be removed by Folders or Outfits, by default.
Since the RLV strip search does not see your inventory but only sees worn items by folder name, this will only work on the bottom folder the item is immediately in. Appending (nostrip) to the end of a folder name and then inserting subfolders without the tag will not work.
- You do not necessarily have to place the folders in #RLV for (nostrip) to work.
- Links to an original with the (nostrip) tag will work. The (nostrip) tag must be applied to the original, not a link.
More on RLV
Davros Harkness’ RLV folders walkthrough here
subscribe via RSS