Updated: 31st October 2019

The following pages are meant to be read in sequence from Step 1.1 through Step 6.2 and used mainly as a tutorial for new people that need examples when setting up Wardrobe for the first time or as a reference for the entrenched wardrobe addict. I do have some preamble on the parent page talking about “My way is just one way” of using the Wardrobe. Its “not the only way”, You need to find “your way that works for you”. Feel free to read it, otherwise continue reading.

Firstly, I should point out that there are two implementations of RLV, the original RLV and RLVa. Depending on which viewer you use determines which implementation your using. Any terminology related in these pages that discuss RLV should be viewed based on the fact the primary viewer I use is Catznip and therefore uses the RLVa implementation.

1.1 Organizing Your Inventory

Here I am starting with the basics, if your going to use a tool like CTS Wardrobe that is efficient at providing an organized visual structure or your inventory that is accessible via the web dashboard or in-world Wardrobe then you really should organize your SL inventory.

My wardrobe as it is now is the result of a major rework of my whole inventory between July and September 2016 when I did a mass cull of inventory as part of my upgrade to a Mesh body. At the same time I also took the drastic option of deleting my entire CTS Wardrobe and re-starting from scratch.

The first step was to create a zz folder at the root level that would sit at the bottom of My Inventory in SL. I moved everything from other folders to here except for my new Mesh body/Head and newly purchased attachable items like clothing and shoes etc. This zz folder is were I culled from, in most cases I simply trashed it only boxing up and archiving things I wasn’t sure about.

My inventory count after the rework and cull was reduced from, over 100K to 4.5k so I was ruthless dumping well over two thirds. The other one third is still archived in several inventory scripted HUD’s under the zz folder. My inventory now fluctuates between 9K – 12K depending on the number of demos I have and the number of objects I either purge or archive.

I do go into more detail in how I organize my inventory under RLV on a dedicated page 1-1: RLV Inventory Expanded.

I only add to Wardrobe when I start using something for the first time, until then it often sits in a folder waiting to be used.

During the process of culling I did notice a slight performance improvement. I tracked this down to two reasons;

  1. Large numbers of items sitting inside a single folder slows down the login process as your inventory is downloaded to inventory cache.
  2. Decreased inventory also means less download to inventory cache at login.

By running some diagnostics on my PC (credit to the University IT Department, according to them SL viewers is not the most efficient code). They tracked this down to how inventory impacts PC memory usage and increased paging. For more details read the “Inventory Memory Usage” section on my SL Tips & Hints page.

As you cans see in the image on right my inventory is fairly flat at the My Inventory root level. If I drilled down you would also see it is structured and well organized.

Another big decision I made as part of my cull was to move away from using Links as much as possible. I will explain why later, for now all you need to know is I dramatically reduced the number of links sitting in 3 folder paths.

  • #RLV\/.Private\<open collar private menu>
  • #RLV\/Stuff\<open collar shared menu>
  • #RLV\.CTS Base [items]\LinkBase\

In total I would have around 80 links which are used for my Open Collar or for my CTS Wardrobe Base Outfits. I will discuss base outfits later in section 4.

Under the standard My Outfits folder is a single outfit which is basically just an Agent rest. Basically its just the 4 system components that must be worn.

Now lets start and setup RLV and then Wardrobe.

1.2: #RLV Setup

  1. Create a #RLV folder as a new root folder under My Inventory, use UPPER case. I have toggled mine to show as a System Folder, hence why it is at the top. NOTE: You can only have one #RLV folder in inventory, more than one will result in RLV issues.
  2. In the SL viewer preferences make sure RLV is enabled, depending on the viewer used it will be called either RLV or RLVa or something like Restrained Love API Support.
  3. Now recycle, log off and restart the viewer to activate the API, then log back in.

That’s it, your now RLV ready so therefore Wardrobe ready. Before we continue with Wardrobe setup lets run through a few RLV fundamentals and how I structure my inventory.

Firstly, wardrobe folder names must be unique and must match the item name in the wardrobe. My recommendation is to use unique prefixing rather than suffixing. RLV can get a bit screwy with folder selection when folders names are similar and what it does may not equate to what you expected it to do. It will select based on the first match it sees when reading through the #RLV folder structure and in some cases if there are conflicts it will fail to locate a folder.

Secondly, the number of sub folder levels you can have in a given path is a bit iffy as to how many levels work. Some RLV users recommend no greater than 3 levels, others don’t say much about it. I have done testing and I expect its more related to the character length of a full path name not reaching a RLV max byte search limit. In saying that I  generally use 3 levels in my folder path, however in some situations I have gone down to a 4th level.

An examples of a 3 Level path would be #RLV\Level 1\Level 2\Level 3\<wardrobe item folder here>\<item sub folders>

An example of a 4 level path would be #RLV\Level 1\Level 2\Level 3\Level 4<wardrobe item folder here>\<item sub folders>

Lets now talk special characters as these can often be a love/hate relationship in terms of RLV. I along with others have done some fairly robust testing, the following are known to work;

! @ # $ % ^ & * ( ) – _ = + ~ . [ ] { } / ; : ‘ ” ? < >

I do however try and stay away from using special characters within a folder path under #RLV. Especially ones that are used in Boolean logic and I also avoid using combinations. RLV can get confused at times especially when it comes across nested strings such as 3 single quotes (”’).

NOTE: The use of several special characters do have special functions when using them as a prefix in a folder name. So use them with care.

1. Using ~ (tilda) could be a little confusing if your also a collar user who is heavily involved in any kind of Dom/Sub RP were items may be sent to your #RLV folder from scripted devices. If you do wish to use tildas and avoid confusion then using “Forbid Give to #RLV” in your RLVa drop down will prevent this from occurring.

2. Using / (forward slash) is more related to Peanut N9/Open Collar.

3. Prefixing a folder with + (plus) means ADD in terms of RLV. I haven’t specifically tested this, but I believe regardless of what your dressing polices state. This will always result in an ADD.

4. Prefixing folders with a . (dot) is slightly more complex in terms of how it impacts Wardrobe.

  • Prefixing #RLV\.LEVEL1 with . (dot) will hide it and anything under its path to other avatars when viewing your #RLV\ folder path via any RLV enabled tool that allows that functionality. For example, what is visible by the dashboards Inventory Browser button when you have navigated to a web browser by clicking open URL in Browser from the in-world Wardrobe or via a Wardrobe Link were you have allowed wearing and undressing.
  • Prefixing a Wardrobe item folder with . (dot) will hide that item folder from Wardrobe. DON’T DO IT.
  • Prefixing a Wardrobe item’s sub-folder with . (dot) will hide that sub-folder from the Show the Wear Dialogue.

Some things To Avoid when it comes to folder paths when the RLV API is enabled.

  1. Avoid cluttering the root #RLV folder with 1st level folders and keep these as short as possible. There is a LSL protocol limit at this 1st level. For example folder names around 9-10 characters long at this level will exceed the byte limit after approx 100 folders. #RLV|<LEVEL 1>|level 2|level 3|… Level 1 is were the folder limit applies. For the geeks out there, this is related to the @getinv command and chat messages are limited to 1023 characters.
  2. Folder paths should never exceed 255 characters in total as this will exceed limits. If you ever have a path this long then you really do need to seriously think about how you name and structure your folders. For the purpose of full disclosure, the folder separator \ (back slash) is also counted as a character offset.
  3. Never use a | (pipe), or , (comma).
  4. I recommend sticking to a rule of prefixing unique item folder names rather than suffixing or at least have something that is unique between character offsets 8-16 which is what I do. RLV can get a little fiddly when a search comes across similar named folders.

As of Peanut N9 for Open Collar there have been changes on how #RLV\<here>\ level folders function if they are prefixed with a (“/”) or (“/.”). If you do intend to use these then you should have an understanding of what it does if you do wear an Open Collar. Refer Open Collar site for details

1.3: #RLV Level 1 Folders

I am now going to break down my #RLV Level 1 folders with brief explanations of what they all represent. How you name your Level 1 folders is up to you, just stick with the rule of keeping them as short as possible so you do not reach that max limit. Currently the max byte limit used by myself for Level 1 folder names is approx 130 which is well below the LSL protocol max limit which I think is 1024.

I do recommend when possible that you do prefix these Level 1 folders with a . (dot), as per the reason I explained in NOTE 1 above. If you do not prefix them, then the subsequent folder paths will be visible if another person has gained access to a web dashboard either via the in-world closet or a managed link that has wearing/undressing enabled.

#RLV\.CTS prefixed folders: These are the folders I keep everything that is related to my CTS Wardrobe. At the next level I have up to 2 or 3 levels of groupings/categories with most item folders sitting at the 3rd level.

At the actual item level I use a unique hex string within the item folder name, the convention I use is \<storename> xx_<itemname>\ were xx_=  00 through FF for each store name. This unique key prevents any folder conflicts from occurring.

#RLV\.nonCTS\: This simply contains folders for items that I have purchased and only created the items in my wardrobe but are still not in a usable state. In the wardrobe they are tagged as .nonCTS and set as Private. View this as my WIP area, once I have set the item up I move it to the relevant .CTS folders, remove the tag and make it Public.

#RLV\/.Private\: This is related to Open Collar [RLV:># Folders] and is restricted to the collar owner to add/detach listed objects within a folder, I do use links here.

#RLV\/Stuff\: This is related to Open Collar [RLV:># Folders] and allow anyone with access to me collar to add/detach listed objects within a folder, I do use links here.

Inventory 3


#RLV\.zFolders\: Contains a set of common empty folders that I simply copy and past to other folders when setting up an item for the wardrobe. They are my wardrobe item empty sub folder templates. This just makes life a lot easier than having to right click, create new folder.

You will also see sub folders here prefixed with z<NAME>. Under these are many more template folders specific to those kind of items.

Lets now expand one set of Wardrobe folders out for a given creator. I have chosen to use Limerence as an example. These are hairs so will sit under the path #RLV\.CTS Hair\[Limerence]\<item folder>\>item sub folder>\

were <item folder> = Limerence xx_itemname

Inventory 2

Here you can see the folder naming convention I use for each wardrobe item in practice. What you name your wardrobe items is up to you, there is no right or wrong way other than the issues of RLV searching conflicts. To avoid those I have simply added a unique key into every items name. In this example RLV search is always going to find a unique identifier for any Limerence item folder at search character offset 11 for a length of 2.

For the purpose of showing a full path, I have also expanded out two sub folders under Limerence 07_Rebecca to show were the objects reside.

Your now set and ready to 2: Wardrobe Setup.

If you wish to see a more expanded view of how I organize my inventory under RLV then click the following link 1-1: RLV Inventory Expanded.