Due to my 2018 University schedule/studies having to take priority I have not kept pages as updated as I would have liked. You may find things slightly outdated. I hope to resume updating the pages in 2019.

I am currently in the process of moving to a new website at Wordpress https://purrslikeakitten.wordpress.com/

My CTS Wardrobe - Inventory Management

Early 2017 I contacted Carlyle and offered my services to be part of the wardrobe support team. That became the trigger to writing these pages which I hope are written in an order to assist as a tutorial for someone new to the wardrobe.

To assist with page navigation, there are links at the top and bottom of the subsequent pages in this series. There are also quick links at the bottom of this page to each page in the series as well as links on the side bar of this blog under CTS Wardrobe.

The purpose of the pages in this series are to provide a glimpse into the way I use the wardrobe system. There are many ways to use the wardrobe, my advise is to experiment and find a way which works best for you. For myself through trial and error I eventually found a way to use the system that works alongside my Open Collar and also provides me with the option to easily find things in inventory natively within the SL viewer. I also had a key requirement that it should be minimal effort to add new items. I didn't want to get bogged down into a click frenzy of having to take snapshots and went for the preference of using the images vendors use for their products. I also wanted the flexibility to mix and match what I am wearing 99% of the time. Obviously there are exceptions such as a rare Gacha outfit.

With that said and I possible say this elsewhere in these pages. "My way" is just one way of using the Wardrobe. Its not the only way and these pages should simply be viewed as a help guide and under no circumstance should be viewed as this is the way the wardrobe should be used. You need to setup your wardrobe the way that works best for you.

Images used on these pages may be OUT-OF-DATE as my #RLV folder, Open Collar and CTS Wardrobe are always in a state of constant changes.

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 clean out of inventory due to upgrading to a Mesh body. At the time I also took the drastic option of deleting my entire wardrobe and starting from scratch.


My inventory count after the rework and cull was reduced from, over 50K to 4.5k so I was ruthless. Most of what I kept has not been added back to my wardrobe, its now all sitting in my 2016 .zArchive box. My inventory now sits around the 6 - 8k mark depending on rate of expansion and the number of demo's I may have at any one time. When I do purchase something new, I immediately copy the package to .zbackups, I then unpack and discard all none Maitreya related objects.

During the process of culling I did notice a performance improvement when using my laptop. I later tracked this down to memory usage and a reduction in OS paging. I also found that when using my laptop I got better performance using Catznip over Firestorm. This is totally a computer resourcing issue on my laptop since it is 5 years old with limited memory. My desktop does not suffer from computer resources issues. For more details read the "Inventory Memory Usage" section on my Quick Tips & Hints page. In saying that I have fully converted over to using Catznip now simply cause it is way more reliable in terms of RLV usage, understandable considering the author of Catznip is the person who maintains the RLVa code.

As you cans see in the image on right my inventory is organised to a handful of root folders.

Another big decision I made as part of my cull was to move away from using Links as much as possible. I dramatically reduced the number of links and most can be located in one of two areas in inventory.
a). #RLV/+<prefix folders>/*
b). #RLV/.CTS Base Avatar [Links]/<folders>

Now to My Wardrobe which I use to add/detach all items I wear on my avatar or as a HuD. If your interested in purchasing the system, under the CTS Wardrobe widget on the right sidebar are links to purchase either in world or from the Marketplace, its a one off cost so it is great value for $Linden.

Regardless of if your going to use the wardrobe as a simple catalog system or fully functional, I recommend you do the following. One day you may want to allow dressing(add)/undressing(detach) and your not going to want to revisit folder/wardrobe item names to get things working.

  1. Create a #RLV folder as a new root folder under the Inventory folder, use UPPER case.
  2. In the SL viewer preferences make sure RLV is enabled, it may be called RLVa or say something like "Restrained Love API Support" depending on the viewer used.
  3. Wardrobe folder names must be unique and must match the item name in the wardrobe, I recommend using unique prefix rather than suffix. 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.
  4. RLV sub folder levels is a bit of an iffy as to how many levels. Some RLV blogs recommend no greater than 3 levels, others don't say much about it, 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 have gone down to a 4th level however I mainly try and stick with the 3 level rule. For example path #RLV/Level 1/Level 2/Level 3/<wardrobe item folder here>/<wardrobe item sub folders>.
  5. RLV like everything else that communicates in SL uses a channel. RLV is coded to use positive integer as this allows the LSL message size to contain up to 1024 bytes in length. This means its unlikely you will exceed a RLV limit in two areas; (1) the number of level 1 sub-folders and (2) then maximum length of a search criteria.
Special characters that "Do" work within folder paths.
  • The following symbols all work in folder names ! @ # $ % ^ & * ( ) - _ = + ~ . [ ] { } \ ; : ' " ? < and > as per extensive testing by Kate Feb/Mar 2018.
  • The use of . and + as well as a few other characters do have special functions when it comes to RLV. In most situations these will work fine, its more how the Wardrobe interprets the usage based on the RLV API. For example the use of period ["."] provides specific control function that enables the submissive to restrict access to various folders within their #RLV inventory structure from access from anyone who has access to their collar. This does have a slight impact on how the Wardrobe deals with folders prefixed with a period. If the folder is a Wardrobe item's subfolder that folder becomes hidden when using the "Show the Wear Dialogue.
"To Avoid" when it comes to folder paths.
  • 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 in RLV. For example folder names around 9-10 characters long at this level will exceed the byte limit after approx 100 folders.
  • Folder paths should never exceed 255 characters in total as this will exceed the RLV search character limit. If you ever have a path this long then you really do need to seriously think about how you structure your folders.
  • Never use a Pipe ("|"), it wont work and its understandable since its used in most programming languages as an "or" and if doubled ("||") as a "logical expression". Same goes for comma (",") and slash ("/"), both are often used as line continuation control characters in programming.
  • Also certain combinations of special characters may cause issues if those combinations are used within an expression.
I strongly recommend that anyone using the CTS Wardrobe Join the in world SL support group. Past this link into local chat and click to join: Wardrobe Support Group

A great starting point is the Getting Started Guide by Buttacwup Pwincess. There are plenty of other great video tutorials on Butta's blog, also do a search on Youtube as others have also put together some good video tutorials. For written documentation I will always point you to the official wardrobe page and then my pages here as I am not sure if anyone else is maintaining written tutorials and/or help.

You can view my wardrobes public link HERE. For me it is extremely important, it is my visual interface to my inventory, I use it to find what I want so I can easily add/detach items in an efficient manner. When I start the SL viewer and log in the first thing I do is click the Wardrobe HuD to load my web page.
As I mentioned above I use the wardrobe system to dress and it does use RLV to do this. I therefore place everything within the #RLV/ path. Under this I have several "+" and "." prefixed level 1 folders. I did mention not to use "+" or "." in folder names unless you understand their usage, I do explain this below.


IMPORTANT: #RLV/<here>/ is were that folder limit applies I mentioned above.

"/+" prefixed folders are specifically used by Open Collar functions.

"/.outfits/" folders are used by Open Collar functions. All other folders prefix by (".") flags the folder as hidden to Open Collar which is why I prefix all my folders with a period ("."). Best to hide them from anyone who has access to my Collars menu.

#RLV/+ Prefixed folders:
These are related to Open Collar [RLV:># Folders] and allow anyone with collar access to add/detach or lock/unlock the items in the folders. You can prevent detachment by adding the suffix "(nostrip)" to a folder name. Since this is not about Open Collar the only additional comment I will make here is that if a folder name here matches an item name in the wardrobe then both Open Collar and the wardrobe will have shared access. This is the first place in my inventory were I use links.

#RLV/.CTS prefix folders:
These are the folders I keep everything that has been added to my CTS Wardrobe system. I have up to 3 levels of groupings or categories, they are;

1st group/category level folders are the .CTS prefix folders, under this are the
2nd group/category level folders and then finally under those are the
3rd group/category level folders. For example #RLV/.CTS Level 1/Level 2/Level 3

Although I could in theory have wardrobe item folders sit under any of the levels, I tend to place them under level 3.

Currently all my wardrobe item folder names are prefixed with yyyymmddx

yyyy=year
mm=month
dd=day
x=A, B, C, D, E, etc.

This date prefix component for folder names is equal to the date I added the item to my wardrobe system and matches the wardrobe item name. This ensures every folder has a unique numeric-alpha prefix removing any potential for RLV to have conflicts when searching for items.
For example #RLV/.CTS Clothing/Dresses/Mini/yyyymmddx Item name/Item subfolders

I am moving to a new folder structure and item naming standard of "vendor xxxxxx item-name" were xxxxxx is a HEX value converted from the date I added the item to the wardrobe in the format of yymmddx were x is a sequence number. Yea its a bit geeky but it means no folder will ever match.
For example #RLV/.CTS Outfits/Vendor/vendor xxxxxx Item name/Item subfolders


#RLV/.Decor:
This is were I keep all my Rez items for my home etc. In most cases I am only using the wardrobe as a visual catalog. However in some cases I do use the wardrobe to attach the package, especially when it comes in the form of a HuD package which seems to be the new trend these days.

#RLV/.nonCTS:

This simply contains folders for items that I have purchased, stored the backups in boxes, removed all the non Maitreya versions and are now simply waiting for me to move to .CTS and add to my wardrobe. Or I may have added them but have not finished deciding on tags etc, in this case they will also have a ".nonCTS" tag and flagged as Private in my Wardrobe. Its my WIP area. Once I move it to .CTS I remove the tag and make it Public.

#RLV/.outfits:
These are related to Open Collar [RLV>Outfits] and allow anyone with collar access to force me to wear/unwear items in the folder. Unless you know what your doing I would strongly recommend you stay away from having folders under this path especially if your using a mesh body and/or head. If you do end up using this then make sure you create a #RLV/.outfits/.core folder and put everything that must be worn in this folder.

#RLV/.zArchives & #RLV/.zBackups:
As I mentioned these are part of my inventory archiving and backup methodology. I integrated this with the CTS Wardrobe in May 2017 after doing a restructure so my boxes could be either REZ or HuD attached.


#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.