The inventory commands allows an user to manipulate Corrade's inventory by using a set of commands comparable to UNIX commands for manipulating directory paths. When Corrade is started, each group has its own unique current directory set to My Inventory, which can then be manipulated and altered separately by each group in part.

llInstantMessage(CORRADE,
    wasKeyValueEncode(
        [
            // show current directory.
            "command", "inventory",
            "group", wasURLEscape(GROUP),
            "password", wasURLEscape(PASSWORD),
            "action", "cwd"
        ]
    )
);

• For a discussion on how to specify paths and escaping path components please see the scripting considerations page.
• Every group has a separate and private filesystem pointer that can be obtained by issuing the command with action set to cwd. The pointer describes where in the inventory folder tree the user finds itself and issuing commands will take the current working directory cwd as parameter when the path parameter is not provided. For instance, issuing cd /My Inventory/Objects will make the pointer reference the folder /My Inventory/Objects and any commands such as ls will list the contents of the /My Inventory/Objects folder. The pointer will be reset upon each Corrade restart.
• The ls sub-parameter will make the command return a CVS list of the following fields:
  • name - the name of the inventory item,
  • item - the inventory UUID of the inventory item,
  • type - the inventory item type,
  • permissions - a permission string representing the permissions of the inventory item,
  • time - a string representing the last modification date of the inventory item.
• The command always operates in the context of the SL inventory and will return and accept only inventory UUIDs. In case more data is required, such as, for example, the asset UUID for textures, sounds, etc, then a followup getinventorydata command can be used.

This command uses the Corrade permissions notation. As an example, let us enumerate a notecard called test and placed in the Notecards sub-folder of My Inventory:

llInstantMessage(CORRADE, 
    wasKeyValueEncode(
        [
            // show current directory.
            "command", "inventory",
            "group", wasURLEscape(GROUP),
            "password", wasURLEscape(PASSWORD),
            "action", "ls",
            "path", wasURLEscape("/My Inventory/Notecards/test"),
            "callback", wasURLEscape(URL)
        ]
    )
);

the callback will receive a data key with the following CSV:

name, test, item, b815f8e4-0367-b361-9227-f1ab7e036eef, type, notecard, permissions, c--mvt------------c--mvtc--mvt

we can thus observe that the permissions for the test notecard are:

c--mvt------------c--mvtc--mvt

these permissions are similar to UNIX commands and are compatible with Corrade's chmod action of the inventory command. They describe all the permissions governing our test notecard.

To dissect these permissions, you can use the following guide:

• split that string in segments of 6 characters: cdemvt, ——, ——, cdemvt, cdemvt.
• each segment means, in order: base permissions, everyone permissions, group permissions, next owner permissions, owner permissions.
• each character means, in order: c (copy), d (damage), e (export), m (modify), v (move), t (transfer).
  • if any of the previously mentioned characters are missing and have a dash (-) instead, that means that the permissions is missing.

Suppose that we wanted to change the permissions for the next owner and remove the modify permissions. We would then issue the following command:

llInstantMessage(CORRADE, 
    wasKeyValueEncode(
        [
            // show current directory.
            "command", "inventory",
            "group", wasURLEscape(GROUP),
            "password", wasURLEscape(PASSWORD),
            "action", "chmod",
            "path", wasURLEscape("/My Inventory/Notecards/test"),
            "permissions", wasURLEscape("c--mvt------------c---vtc--mvt"),
            "callback", wasURLEscape(URL)
        ]
    )
);

The original permissions for the test notecard were:

c--mvt------------c--mvtc--mvt

and the new permissions are now:

c--mvt------------c---vtc--mvt

As you can see, the 4th segment which refers to the next owner permissions is missing the m component, meaning that it cannot be modified.