PrimLink

docs

Adding and Refreshing Items

Choose between registration, sync, and cache import when getting PrimLink caught up with your #RLV inventory.

PrimLink gives you three ways to get item folders into the app:

  • Register by name when you want the HUD to find one or more items now.
  • Sync when an item is already in PrimLink and you want to refresh its tags, settings, or subfolders.
  • Import a viewer cache file when you want to catch up on many items you already set up in Second Life.

All three methods use the same item rule: an item is the folder under #RLV that directly contains a #primlink subfolder.

📁 #RLV
  📁 PrimLink Outfitters - My Fave Outfit
      📁 #primlink
          📁 #creator.uuid=e03b8af7-191d-4ee2-84bf-644010445dfb
          📁 #image.gyazo=8e8da6b5834c0bc8e13b47a70396bc85
      📁 #tags clothing top bottoms shoes
      📁 HUD
      📁 boots
      📁 sweater
      📁 pants

In this example, PrimLink treats PrimLink Outfitters - My Fave Outfit as the item. The folder can move around under #RLV; so long as the item name is still PrimLink Outfitters - My Fave Outfit, it does not matter if you reorganize where in your inventory you store PrimLink Outfitters - My Fave Outfit after item-registration.

Register By Name

Use this when you just set up an item and want PrimLink to find it right away.

You can start registration from the dashboard or from the PrimLink Bridge HUD. In both cases, give PrimLink the item folder name:

PrimLink Outfitters - My Fave Outfit

The PrimLink Bridge HUD looks in your inventory's #RLV folder and only accepts a match when that folder contains #primlink.

Register-by-name is best for:

  • newly created item folders
  • a small list of specific item names
  • same-session work where you are still logged into Second Life
  • items that did not appear in a cache import

Sync Existing Items

Use Sync when an item is already known to PrimLink and you want to refresh what PrimLink knows about it.

Every inventory item has a sync button that can trigger this action.

Sync can update:

  • tags from #tags ... folders
  • settings inside #primlink
  • visible subfolders such as wearable parts
  • whether the item still exists under the same item name

Sync does not scan every folder in #RLV. It checks the items PrimLink already knows about. If you rename an item folder, register the new name again.

If Sync cannot access an item, PrimLink keeps the last-known record and marks it inactive. Use status:inactive in Search to find that last-known record again, then sync again, register the new name, or forget the old record when you know you no longer need it.

Import A Viewer Cache File

Use cache import when you are asking:

What did I already set up?

This is the catch-up path. If you already made many #RLV folders with #primlink, cache import can review them in one pass without typing each name.

If you don't have a working HUD, and you'd like to use tag-based search, this is also the mechanism to try out PrimLink with your own inventory!

The inventory cache file is usually named:

<avatar-uuid>.inv.llsd.gz

PrimLink reads the selected file in your browser. It does not upload the full cache file. After parsing, PrimLink shows a report of matching #RLV folders and lets you remove rows before upload. Only the rows you confirm are sent to PrimLink.

Cache import is best for:

  • first-time setup after you already organized many items
  • catching up after making a batch of #primlink folders in a previous session
  • reviewing duplicates before they collapse to one PrimLink item
  • checking which configured items PrimLink can see from the saved cache

Cache Import Limitations

Cache import reads a saved viewer snapshot. It is not a live view of your currently open inventory.

If you just created #primlink, added #tags ..., renamed folders, or moved folders in the current Second Life session, the cache file may not include those changes yet. For near-live updates, use Register by name or Sync.

For the freshest cache import:

  1. Let your viewer finish fetching inventory.
  2. Open or search the relevant #RLV folders if they were not already loaded.
  3. Log out of the viewer cleanly.
  4. Import the .inv.llsd.gz file after logout.

If the import report is missing items you expected, use Register by name for those items, or log back in, make sure the folders are fetched, log out, and import again.

Why The Cache Works This Way

Second Life viewers write inventory cache files as locally saved cache data. They do not promise that the file is updated immediately every time you change inventory.

The current official Second Life Viewer source saves inventory cache during viewer disconnect/logout. Firestorm follows the same pattern. The viewer cache code also only writes inventory folders it considers complete, which means an unloaded or partially fetched folder can be missing from the cache file.

Privacy

You may be asking...

How much of my Inventory Cache file is PrimLink reading and saving?

Only things that have a #primlink folder!

Yes, your cache file can contain more inventory information than PrimLink needs. PrimLink's import flow is designed so the full file stays in your browser.

Before anything is uploaded, you review the matching PrimLink rows. The server receives compact item data for confirmed rows only, not the full cache file.

And, of course, this is not the only path through; the HUD is truly limited to what's exposed in the #RLV folder, if you'd prefer not to expose your entire inventory.

Which Item-Registry Option Should I Use?

Use Register by name when the item is new, recently edited, or missing from PrimLink.

Use Sync when the item is already in PrimLink and you want to refresh it through the HUD.

Use Import Cache when you already set up a batch of items and want PrimLink to catch up from the viewer's saved inventory snapshot.