MD Redelivery Terminal & Product Server User Manual

Quick summary:

 


 

Chapter #0: Initial notes & basic informations

MD Redelivery Terminal & Product Server is a tool designed for stores, a 2-in-1 solution that offers both redelivery terminal and product server features; this product is completely integrated with MD Vendor System, the vendor solution released by MD Labs (available here).

! IMPORTANT: All other vendors systems are not compatible with this product, therefore the following instructions does not apply.

MD Redelivery Terminal & Product Server is available as separate purchase here or included into MD Vendor System (Full Pack).

! IMPORTANT: The following user manual presents and explains the usage and detailed features of:

  • MD Redelivery Terminal & Product Server Script version 3.0.3
  • MD Redelivery Terminal / Mass Redelivery Plugin version 3.0.0

 


 

Chapter #1: What’s inside the pack

Once purchased and received the product, MD Redelivery Terminal & Product Server Script is composed by two script:

  • MD Redelivery Terminal & Product Server Script: it is the main script, offering both redelivery and product server features. This script must always be present inside the device.
  • MD Redelivery Terminal / Mass Redelivery Plugin: is an optional plugin that enables the mass redelivery feature (more details in the corresponding chapter).

 


 

Chapter #2: First setup

Whether the owner wants to setup a redelivery terminal or a product server, the few steps required are exactly the same.

PLEASE NOTE: MD Redelivery Terminal & Product Server Script is designed to work with MD Vendor System but it is not a plugin. This means the script has to be installed in a separate prim, being a different device. Do not drop the MD Redelivery Terminal & Product Server Script inside vendors running MD Vendor System.

As first thing, the MD Redelivery Terminal & Product Server Script must be dropped inside the object/prim used as terminal/server; if this is the first setup for that specific device (and not a simple vendor reset), it’s highly recommended to rename the terminal or server with it’s final name in order to avoid having multiple devices with the same name, which could lead to malfunctions. Also, it is important to remember to avoid setup a new device starting from a copy of an existing one created via drag&copy.

The basic setup for the terminal is now done, but the configuration is not over yet.

 


 

Chapter #3: Redelivery Terminal vs Product Server

As mentioned in the previous chapters, MD Redelivery Terminal & Product Server Script is a 2-in-1 solution which offers both redelivery terminal and product server features; this means the same script can be used to setup either a redelivery terminal or product server and in general, a device running MD Redelivery Terminal & Product Server Script can works as both at the same time. Since a single device can work as both redelivery terminal and product server at the same time, the difference between the two is more ‘logical’ then ‘physical’.

In general a redelivery terminal is a device hosting one or more items in its content and serving customers redeliveries for product they have already purchased. A redelivery terminal can then have two roles:

  • server: is the terminal itself, hosting the items and delivering the products upon customer’s request.
  • client: is an empty device – not containing any item – that works as satellite terminal. Customers can click on it and request a redelivery just as with any other terminal, but the client relies on a redelivery server for the product delivery.

 

A product server is a device that holds one or more items inside its content and have one or more vendors connected to it as clients, relying on the product server to deliver the products that are purchased. Differently from the redelivery terminal, the product server can only have the server role.

 

Redelivery Terminal Product Server
main purpose offer redelivery to customers, send out product updates via mass redelivery deliver products purchased through client (satellite) vendors
possible roles server and client server only
max # of items hosted per device 250 250
max # of devices manageable 999 999
devices connectable redelivery terminal as client vendor as client

 


 

Chapter #4: Products naming, constraints & limitations

Along with the script, the owner will have to drop inside the terminal all the products used to offer redelivery and/or sold via the vendors, if setting up a product server.

! IMPORTANT: Keep in mind that MD Redelivery Terminal & Product Server can work either as redelivery terminal or product server, or even as both at the same time.

Whether for a redelivery terminal, a product server, or both, the products inside the terminal has to comply some specific rules:

  • Products must be objects.
  • Each product must be only one item. (If your products are composed by several items, this means you will have to box them into one single pack)
  • To offer redelivery for products sold in-world, the troduct’s name must match EXACTLY the one inside the in-world vendor.
  • To offer redelivery for products sold from SL Marketplace, the product’s name must match EXACTLY the item’s name on the SL Marketplace page.

The following picture is an example of a correct product’s name matching between in-world vendor, MP listing and redelivery terminal/product server:

Product's name matching (Click to enlarge)

Product’s name matching (Click to enlarge)

 

As shown in the picture above, for this specific example the product called ‘MD Gacha Machine Script’ is present inside the in-world vendor, marketplace listing and redelivery terminal with the same name; thanks to this matching it is possible to offer redeliver for both products purchased in-world and from the SL Marketplace.

! IMPORTANT: when writing the product’s info on the SL Marketplace page, the item’s name reported in the item’s title field may vary depending on the language selected (English, Japanese, German, French, Portoguese, Spanish): it is very important to always make sure the item’s name reported in the item’s title field corresponds to the one desired in all the languages.

 


 

Chapter #4.1 Constraints & limitations

When setting up a  redelivery terminal or a product server there are some constraints and limitation to take in account:

  • For redelivery terminal, the item’s name must match exactly between the ones sold inside the vendor and the ones inside the redelivery terminal;
  • To offer redeliver also for products sold through SL Marketplace:
    • the item’s name in the SL Marketplace page must match exactly with the ones inside the redelivery terminal;
    • SL Marketplace sales must be integrated with the MD Labs Online Services website. Detailed instructions here.
  • Each redelivery terminal or product server can contain up to 250 items and more cannot be added. However there is no limit on how many terminals to use: if a redelivery request involves a product that cannot be found on the terminal #1, the request is automatically forwarded to the terminal #2, and so on until the product is found or there are no more terminals to query;

 


 

Chapter #5: Owner Menu

Once the owner has dropped the MD Redelivery Terminal & Product Server Script along with one or more products, a simple click will make the ‘Owner Menu’ appear: this specific dialog – accessible by the owner only – contains all the terminal’s settings and features.

MD Redelivery Terminal & Product Server – Owner Menu

 

Here’s an overview of the main features present in this menu, some of them will be explained more in detail in the corresponding chapters:

PLEASE NOTE: some features listed below are utilizable only when using the terminal as redelivery terminal.

  • Active: when this option is enabled, the redelivery terminal is active and users can click on it to access their redelivery page.
  • Mass Redelivery: clicking on this button will start the ‘Mass Redelivery’ wizard, allowing the user to redeliver a specific product to everyone whom purchased it. (redelivery terminal only feature).
  • Manual Redelivery: this feature will let the owner redeliver a specific product contained inside the redelivery terminal to a specific avatar. (redelivery terminal only feature).
  • List Products: this button will list all the products stored inside the redelivery terminal.
  • Online Services: opens the MD Labs Online Services website, where the owner can interact with all the redelivery terminals. More details about this feature can be found in the corresponding chapter.
  • Update: this button starts the update module, which will look online for a new update of the product and – if found – deliver it to the owner.
  • Reset: this button will reset the redelivery terminal, wiping all the data and settings.

 


 

Chapter #6: Basic Usage – Setup a simple server device

This chapter is meant to explain the basic steps to setup a simple redelivery terminal or product server in its most basic configuration: a single terminal working as server. The setup procedure consists in just a few and easy steps:

  1. Rez the object to use as terminal and make sure to have mod permissions for it;
  2. Drop the MD Redelivery Terminal & Product Server Script inside the rezzed terminal object;
  3. A “not active” hover text will appear over the device. At this time is a best practice to rename the terminal with an unique name;
  4. Drop one or more item product that users will be able to have redelivered inside the terminal’s content, keeping in mind the following criteria:
    • the name matching is very important for the redelivery to work;
    • the product must be an object;
    • if the owner does not have transfer permission on an item it will be ignored and users won’t be able to obtain it;
    • if the owner does not have copy permission on an item it will be ignored and users won’t be able to obtain it;Drop one or more item product that users will be able to have redelivered inside the terminal’s content, keeping in mind the following criteria:
  5. Once the items are dropped click on the terminal to access the owner menu, then select “Active” to enable the device;
  6. The redelivery terminal or product server is now setup and working correctly;

 

Once a device is setup correctly and enabled – if working as redelivery terminal – customers touching it will be taken to a webpage with their purchases made at the store: this page – hosted as part of MD Labs Online Services – is personal for each user and contains all the items purchased by the current user – or received as gift. Depending on the specific setup, the list of purchases will contain both products sold from in-world vendors and SL Marketplace, or just one of the two. The customer will have to click the ‘Redeliver’ button of the selected product to immediately receive a redelivery.

 


 

Chapter #7: Redelivery Terminal – Client vs Server

! IMPORTANT: the Client role is a specific feature applicable to redelivery terminals only.

While standard redelivery terminals (server) holds in their content all the product that will be redelivered, a terminal set as client will not contain any item, but will instead connect to another terminal set as server to retrieve the requested product and redeliver it.

This behavior is better explained in the picture below:

Server redelivery terminal vs Client redelivery terminal

 

When a terminal works as server, it will behave as shown in the upper side of the picture: each redelivery request (1) from users is made directly on the redelivery terminal which is set as server, holding all the products in its content. If the request is accepted, the redelivery server will directly send the requested product to the avatar (2).

On the contrary, when a terminal works as client, each redelivery request from users is made on the redelivery client (1) and immediately forwarded from this last one to the server (1). If the request is accepted, the redelivery server will directly send the requested product to the avatar (2). This behavior is shown in the lower side of the picture above.

The redelivery terminal client doesn’t store any product in its content, but rely on the server for it.

Client terminals become extremely useful when the owner wants to offer a redelivery point at satellite stores or at events: in this case it will be necessary only to setup a redelivery terminal without placing any product inside, saving time and avoiding to have several copies of the same products inside each terminal. The terminal will automatically set itself in client mode and work as already described.

Another import point to consider which favors client terminals is related to the fact that they are region-independent; this means that no matter where in the grid the client terminals are located, they will always be able to contact the redelivery server and process the request. Again, this feature becomes very useful in case of satellite stores or redelivery point at temporary events, where multiple redelivery clients – one per each satellite store and/or event –  will connect to the redelivery server which will be the only one holding the products in its content. This setup will reduce the efforts needed by the owner to maintain a product list up-to-date, since these products will be stored only in one terminal and not mirrored into every terminal.

 


 

Chapter #8: Redelivery Terminal – Auto linking between terminals

As explained in the previous chapters, each terminal can store up to 250 items in its content; those items are the product that can be redelivered upon request. This limit is imposed by a Second Life constrain and cannot be changed. Even tho the maximum number of 250 products can be considered elevated, it is often not enough for a medium-big store, which has to manage even thousands of different products. MD Redelivery Terminal & Product Server Script solves this problem by allowing the redelivery terminal to link each other virtually, as if they were only one large terminal.

The linking between a terminal and another is made when the new one is rezzed and it is completely automatic and invisible to the owner.

Since there is no limit on how many redelivery terminal a store can use, this solution allows the owner to manage a virtually unlimited number of products. When a customer request a redelivery for a specific product the request is sent to the first redelivery terminal but, if the requested item cannot be found in the terminal’s content, the request is then forwarded from the first terminal to the second, and so on until the product is found or there are no more terminals to query.

All this process is automatic and invisible both to the owner and the user, working independently if the initial request is made directly to a server terminal or a client one

 

Redelivery request on multiple servers

 

PLEASE NOTE: the same auto linking technology is used for product servers.

 


 

Chapter #9: Redelivery Terminal – Mass Redelivery

! IMPORTANT: the Mass Redelivery is a specific feature applicable to redelivery terminals only.

This particular feature has been created to simplify and automate the redelivery of products; with Mass Redelivery, the owner can automatically redeliver a specific product to all avatars whom purchased it. Depending by the particular setup, the redelivery list can include both in-world and MP purchases or one of the two. The Mass Redelivery becomes really useful for distributing product updates, where a new version of a specific product has to be sent to all users who purchased it.

In order to enable this feature the owner will have to drop a second script inside the redelivery terminal; this script – called MD Redelivery Terminal Script / Mass Redelivery – is included inside the MD Redelivery Terminal & Product Server Script pack. After dropping this second script, clicking on the corresponding “Mass Redelivery” button in the owner menu will start a wizard composed by 4 different steps:

Step 1 – product selection: in this first step, owner will be prompted to a list of all products sold through in-world vendors and/or MP and will be asked to choose the product to redeliver; an useful ‘Search‘ button is present to simplify this step and make it faster.

md redelivery terminal script - 09

Mass Redelivery – Step 1 – Product selection

 

Step 2 – object selection: once chosen the product to mass redeliver, an object (if present) matching the name of the product is picked automatically from the terminal’s content and selected as object to redeliver. However, in order to allow even more flexibility, the owner is asked if proceeding with the object selected automatically (‘Continue‘) or choose another object picking it from inside the terminal’s content (‘Change‘).

md redelivery terminal script - 10

Mass Redelivery – Step 2 – Object selection

 

Step 3 – custom message: in this third step – optional – the owner is asked to submit a custom message that every customer will receive along with the product redelivery.

Step 4 – confirm: this last step consist in a recap of the chosen settings – product, object and custom message – in order to start with the mass redelivery process.

md redelivery terminal script - 11

Mass Redelivery – Step 4 – Confirmation

 

Once the owner confirms all the settings, the mass redelivery starts and one by one, every customer whom purchased the selected product is offered a new copy of the chosen object, along with the (optional) custom message.

PLEASE NOTE: this procedure could take up to several minutes depending by the number of customers to redeliver the products to.

 


 

Chapter #10: Redelivery Terminal – Manual Redelivery

! IMPORTANT: the Manual Redelivery is a specific feature applicable to redelivery terminals only.

This feature is very similar to the Mass Redelivery, except that is applied to a specific avatar, instead of to all avatars whom purchased a selected product. Once clicked the corresponding button in the menu, the owner will be asked to follow a simple wizard to submit all the requested parameters:

Step 1 – avatar selection: owner will be first asked to provide the name or the key (UUID) of the avatar whom will receive the redelivered product.

Step 2 – product selection: in this step, owner will be prompted to a list of all products inside the terminal and will be asked to choose the product to redeliver.

Step 3 – custom message: in this third step – optional – the owner is asked to submit a custom message that the customer will receive along with the product redelivery.

Step 4 – confirm: this last step consist in a recap of the setting chosen – product and custom message – in order to start with the manual redelivery process.

Once the owner confirms all the settings, the redelivery starts and the selected product will be sent to the desired avatar, along with the custom message (if provided).

 


 

Chapter #11: Product Server

A product server is a particular device holding one or more product in its content and having one or more client vendor connected to it, relying on it for the product’s delivery.

MD Redelivery Terminal & Product Server Script is able to work as redelivery terminal and product server, as well as product server only. The client vendors connected to the product server need to run the latest version of MD Vendor System as well as the Remote Control Plugin.

A product server – like the redelivery terminal – is subject to some limitations:

  • each product server can contain up to 250 items. However there is no limit on how many servers to use: if a product delivery request involves a product that cannot be found on the server #1, the request is automatically forwarded to the server #2, and so on until the product is found or there are no more servers to query;
  • each client vendor connected to a product server can retrieve only one item among all the products inside the product server’s content;

! IMPORTANT: a terminal running the MD Redelivery Terminal & Product Server Script can be both a redelivery terminal and a product server at the same time.

The setup of a product server is identical as the one required for a redelivery terminal: both script and products have to be dropped inside the object used as server. The connection of the client to the product server has to be done from the client vendor through the remote control plugin, as explained here. Once connected, the client vendor will be associated to one item chosen among the ones present inside the server’s content and every time a purchase is made from the client vendor the server is contacted to deliver the product to the receiver avatar.

Below are reported some real user case as example:

Terminal set as Product Server only

 

Terminal set as Product Server & Redelivery Terminal

 


 

Chapter #12: User Menu

Once the redelivery terminal is setup correctly, with the products dropped in the content and set to active, if a user touch the terminal is prompted to its personal webpage hosted at MD Labs Online Services.

This webpage is private and contains a list of all products purchased by the current user from the store.

Redelivery page @ Online Services

 

The page is divided into two main tabs:

  • Purchased: this tab contains the list of all products purchased from the user for himself, or gifted to someone else;
  • Received as Gift: this tab contains the list of all products that have been gifted to the user from another avatar.

Additional information such as region, date and cost are stated for each transaction listed, so users can better identify the products; a click on the ‘redeliver this item‘ link of the corresponding entry will start the redelivery process and within few seconds the the user will receive a new copy of the selected product.

IMPORTANT: products not having copy permission are excluded from the redelivery and not displayed on the redelivery page.

MD Teleport System – User Manual

Quick summary:

 

Initial notes

The following user manual applies to:

  • MD Teleport System
  • MD Teleport System – Super Mario Pipe Edition

When some of the features are available only for a specific version, will be clearly stated.

 

Chapter #1: initial setup

To get started using your MD Teleport System, first rez a copy and click on it to perform the quick setup; the owner will be asked to name the teleporter in order to idenfity it.

Please note: this step is very important and mandatory for the teleporter to work correctly; moreover, the name provided should be unique in order to avoid confusion between multiple teleporters belonging to the same owner.

Once the teleporter have been named, the initial setup is complete. At this point, the teleporter will start scanning the area around for other teleporters belonging to same owner and will automatically link to them if they are found; this procedure can take up to 60 seconds the first time.

Important: for the teleporter to work properly, there is a parcel setting called ‘object entry’ that must be set correctly; this specific setting allows the telporter to move around the parcel, infact teleporting the avatar itself. Usually this setting is enabled by default but in case it isn’t, the MD Teleport System will send the owner  a warning during the setup process, requesting to enable the option. To enable this option go to World > Parcel Details > Options tab and set the Object entry checkbox to Everyone.

md teleport system 01

Parcel’s object entry setting

 

Once the initial setup is complete if owner clicks on the teleporter will be propted to a menu called ‘choice menu’; this menu can be accessed by the owner only and will show 2 different buttons:

  • Owner menu: using this button the owner can access to the teleporter’s configuration menu, where several options can be set in order to customize the teleporter.
  • Teleport: this button starts the normal teleport procedure.
Choice Menu

Choice Menu

 

Chapter #1: Owner Menu

When the owner clicks the teleporter and selects ‘Owner Menu’, the configuration menu is displayed. This particular menu – accessible by the owner only – contains all the settings and options needed to setup the MD Teleport System in a quick and flexible way.

Owner Menu

Owner Menu

This menu is divided in many section, some of them leading into other sub menus

  • Active: this button enables or disables the teleporter. When enabled, the teleporter will be usable by the owner and other users whom comply the optional access list configuration; if disabled, the teleporter will be unusable for everyone, including the owner.
  • Privacy: this button leads the owner to a submenu where it’s possible to configure the teleporter’s access list, defining who can use (leave and reach) the teleporter.
  • Options: this button takes the owner to a submenu where some additional settings are present, in order to customize even more the teleporter.
  • List TP: this button will list to the owner the complete list of all teleporters connected to the actual one.
  • Update: this button starts the update module, which will look online for a new update of the product and – if found – deliver it to the owner.
  • Reset: this button will reset the teleporter, wiping all the data, including options and access list.

 

Chapter #3: Basic Usage

For a basic usage – suitable to most users – the owner will have to rez at least 2 teleporters. Once named them correctly (using different names!), the teleporters will start scanning the area around and within 60 seconds they will link to each others; a message will be sent to the owner, stating the teleporter have found each others and connected. At this point, simply right clicking on one teleporter and selecting ‘Teleport’ will teleport the user from one teleporter to another. Alternatively, the owner can also left-click on the teleporter and select “Teleport” from the Choice Menu to teleport.

If more than 2 teleporter are rezzed and setup, once an user clicks to teleport will be propted to a menu where its asked to choose the destination among the possible ones; a 30 seconds timeout is applied at this step and the user will be unsit from the teleporter if the timeout occurrs.

Destination selection menu

Destination selection menu

 

Chapter #4: Privacy

This section is one of the most important present into the MD Teleport System, because allows the owner to define who can use each teleporter. Using this feature and its many options, the owner can have the total control on who is able to use the teleporter to reach some specific areas. The Privacy menu is divided itself into 3 sections:

  • Leave: this button takes the owner to another menu where it’s possible to define who can leave using the teleporter. In other words, the ‘leave’ setting define who can sit on the teleporter and teleport to a specific destination.
  • Arrive: this button takes the owner to another menu where it’s possible to define who can reach the teleporter. In other words, the ‘arrive’ setting define if the corresponding teleporter will appear inside the list of possible destinations.
  • Access list: this button takes the owner to the access list submenu, where it’s possible to create, edit and remove a group of avatars whom will have specific permissions on the teleporters.
Privacy Menu

Privacy Menu

NOTE: By default, the teleporter is set to ‘public’: this means everyone can use the teleporter to leave (teleport) and everyone can arrive to the teleporter (teleport present in destination list).

 

Chapter #4.1: Leave

Leave

Leave Menu

When defining who can sit and use the teleporter, different options are present:

  • Owner Only: if this option is enabled, only the owner will be able to teleport from this device.
    • Note: while other users cannot sit and teleport, they will still be able to see and reach this teleport as a destination when using from another teleport. The restriction of this behavior has to be done inside the ‘Arrive’ submenu.
  • Access List: with this option active, only the owner and the users present in the access list will be able to sit and teleport from this device.
    • Note: while other users not present into the access list cannot sit and teleport, they will still be able to see and reach this teleport as a destination when using from another teleport. The restriction of this behavior has to be done inside the ‘Arrive’ submenu.
  • Group Only: this option let only users wearing a specific group’s tag to be able to teleport from this device. In order to use this feature, owner will be asked to assign the teleporter to the desired group using the group tool that can be found under right-click > Edit >General tab. Once selected the right group, clicking on the “Group Only” button will enable the feature.
    • Note: while other users not having the right group tag cannot sit and teleport, they will still be able to see and reach this teleport as a destination when using from another teleport. The restriction of this behavior has to be done inside the ‘Arrive’ submenu.

 

Chapter #4.2: Arrive

Arrive Menu

Arrive Menu

When defining who can see a specific teleporter in the destination list and reach it, different options are present:

  • Owner Only: if this option is enabled only the owner will be able to see this teleporter in the destination list and select it, making the teleporter perfect for a private area where no one – except the owner – have access.
    • Note: while other users cannot reach this teleporter selecting it from the destination list, they can still use it if they somehow reach (or are teleported) to the area where the teleporter is rezzed. The restriction of this behavior has to be done inside the ‘Leave’ submenu.
  • Access List: with this option active, only the owner and the users present in the access list will be able to see this teleporter in the destination list and teleport to the area where its rezzed.
    • Note: while other users cannot reach this teleporter selecting it from the destination list, they can still use it if they somehow reach (or are teleported) to the area where the teleporter is rezzed. The restriction of this behavior has to be done inside the ‘Leave’ submenu.

 

Chapter #4.3: Access List

Access List Menu

Access List Menu

This section is designed to manage the access list, used to define both who can leave (sit and teleport) and who can arrive (select the teleporter from the destination list).

There are 3 main action to perform in this area:

  • Add user: by clicking, owner will be asked to provide the name or key (UUID) of the avatar to add to the access list. If the value submitted is valid, the corresponding avatar will be immediately added and will be able to leave and/or arrive to the teleporter, depending by the privacy settings.
  • Remove user: this button will popup a menu containing all the avatar present inside the access list and owner will be asked to pick the one to remove.
  • List user: this button will list to the owner all the avatars present in the access list.

Important: the access list is shared and synced between ALL the teleporters present in the parcel: this is mandatory for all the privacy settings to work properly. This means that when adding or removing a user on one teleporter, the change will be reflected to all teleporters linked during the next sync.

 

Chapter #5: Options

In the option sub menu is possible to find some additional features aimed to enrich even more the experience with the MD Teleport System.

Options Menu

Options Menu

 

  • Notify: when this option is enabled, the owner will receive a notification IM from the teleporter once one of its connections changes; this means either when a new teleporter is found and connected or when an existing teleporter is removed from the linked ones.
  • Scan Time: each teleporter – when active – will keep scanning the area around at a given rate; this rate, called scan time, can be adjusted to define how often the scan will occurr. At each scan the teleporter will update the list of connected teleporters, removing the deleted ones and adding the new ones.
  • Hover Text: this option will display a custom text – submitted by the owner – on the teleporter.

MD Group Gift Giver Script – User Manual

 Quick summary:

 

 


 

Initial notes

! IMPORTANT: The following user manual presents and explains the usage and detailed features of:

  • MD Group Gift Giver Script version 3.3.0

 


 

Chapter #1: initial setup

The first setup of MD Group Gift Giver Script is very easy and quick: simply drag the MD Group Gift Giver Script provided in the pack and drop it inside the prim that will work as group gift giver. Once done, simply clicking on the prim will make a the choice menu appear. This special menu is visible only to the owner and contains two main action:

  • Owner Menu: by clicking, the owner will access to the owner menu, where its possible to configure the group gift giver.
  • Get gift: this button simulate the behavior of the group gift giver as if the owner was a ‘normal’ user.
Choice Menu

Choice Menu

 


 

Chapter #2: Owner Menu

When the owner clicks the group gift giver, the configuration menu is displayed. This particular menu – accessible by the owner only – contains all the settings and options needed to setup the group gift giver in a quick and flexible way.

md-group-gift-giver-script-02

Owner Menu

This menu is divided in many section, some of them leading into other sub menus:

  • Active: by toggling this option on, the group gift giver will be enabled and it will be possible for users to click the board and get the gifts.
  • Group Only: by enabling this feature only the users wearing a specific group’s tag will be able to get the gifts. Owner will be asked to assign the group gift giver to the desired group using the group tool that can be found under right-click > Edit >General tab. Once selected the right group, clicking on the “Group Only” button will enable the feature. When the group only mode is active clicking on the button again will disable it.
    • NOTE: leaving this option disabled, will not restrict the gift giver to a specific group’s members; however, several other options are present to manage how can access the group gift giver.
  • Gift Limit: this option will apply a maximum number of gifts that will be given out to users. Owner will be asked to submit the maximum amount of gifts and once reached that number, no more gifts will be given out. This feature can be compared to a “limited stock quantity”.
  • Reserve Gift: this button will open a submenu dedicated to configure and manage the group gift giver’s access list. It is possible, infact, to add up to 10 different avatars that will be the only ones able to get the gifts. More about this feature can be found at the dedicated chapter.
  • Manager: this button will open a submenu dedicated to configure and manage the group gift giver’s manager list. It is possible, infact, to add up to 5 different avatars that will be able to manage the group gift giver’s settings. More about this feature can be found at the dedicated chapter.
  • Blacklist: this button will open a submenu dedicated to configure and manage the group gift giver’s blacklist. It is possible, infact, to add up to 10 different avatars that will be forbidden to use the group gift giver. More about this feature can be found at the dedicated chapter.
  • Options: this sub menu groups together some optional features, such as ‘1 per avi’ mode, the minimum avatar age required, hover text and notifications. The detail of each features will be explained in the options chapter.
  • Update: this button starts the update module, which will look online for a new update of the product and – if found – deliver it to the owner.
  • Reset: this button will reset the group gift giver, wiping all the data, including options and access list.

 


 

Chapter #3: Basic Usage

The basic usage for MD Group Gitft Giver Script is very easy and quick to get: simply drop the script into the prim that will work as group gift giver along with one or more items that will be used as gifts. The usage that will suit the most cases is simply restricting the access to gifts only to members of a specific group. In order to achieve that, it’s mandatory to assign the prim’s group to the desired one:

  1. right click on the prim and select ‘Edit’.
  2. navigate to the first tab, called ‘General’
  3. At the middle of the panel, there is a ‘Group’ entry: clicking on the wrench icon next to it will popup a window containing all the available groups to choose among.
Group assignment

Group assignment

 

Once done this, click the group gift giver in order to access the Owner Menu, where the ‘Group Only’ option needs to be enabled.

The basic setup is now complete: users clicking the group gift giver will be required to wear the corresponding group’s tag active in order to get the gifts contained.

 


 

Chapter #4: Reserve Gift

MD Group Gift Giver Script allows owner to compile a list of avatar that will be the only ones able to get the gifts; this list can contain up to 10 different avatar and this feature can be used in combination with other options – such as the ‘Group Only’ – or as main working mode.

Reserve Gift

Reserve Gift Menu

From this submenu many actions can be performed:

  • Add: by clicking, owner will be asked to provide the name or key (UUID) of the avatar to add to the reserve gift list. If the value submitted is valid, the corresponding avatar will be immediately added and will be able to click and access the group gift giver script in order to get the gifts contained.
  • Remove: this button will popup a menu containing all the avatar present inside the reserve gift list and owner will be asked to pick the one to remove.
  • Remove all: this option will remove all avatars, wiping the access list.
  • List: this button will list to the owner all the avatars present in the reserve gift list.

As mentioned before, the ‘Reserve Gift’ feature can be used alone or combined with other options: infact this feature represents another filtering level to better define who can access the gifts.

For example, combining the ‘Reserve Gift’ feature with ‘Group Only’ will let only users present into the access list and wearing the correct group’s tag to receive the gifts. Similarly, other options can be added or combined to customize even more the group gift giver.

 


 

Chapter #5: Manager

Similarly to the Reserve Gift feature, MD Group Gift Giver Script allows the owner to compile a list of avatar that will be considered “manager”: this list can contain up to 5 different avatar. The managers will be able to control the group giver script in all it’s aspects just as the owner would.

Manager Menu

Manager Menu

 

From this submenu many actions can be performed:

  • Add: by clicking, owner will be asked to provide the name or key (UUID) of the avatar to add as manager. If the value submitted is valid, the corresponding avatar will be immediately added and will be able to click and access the group gift giver script’s owner menu.
  • Remove: this button will popup a menu containing all the avatar present inside the manager list and owner will be asked to pick the one to remove.
  • List: this button will list to the owner all the avatars present in the manager list.

 


 

Chapter #6: Blacklist

Another important feature of MD Group Gift Giver Script is the blacklist one; this feature allows the owner to compile a list of avatar that will be considered “blacklisted”: the avatars present in this list will not be able to get the gift contained inside the group gift giver.

Blacklist Menu

Blacklist Menu

 

From this submenu many actions can be performed:

  • Add: by clicking, owner will be asked to provide the name or key (UUID) of the avatar to add to the blacklist. If the value submitted is valid, the corresponding avatar will be immediately added and from that moment will not be able to click and get the gifts.
  • Remove: this button will popup a menu containing all the avatar present inside the blacklist and owner will be asked to pick the one to remove.
  • Remove all: this option will remove all avatars, wiping the blacklist.
  • List: this button will list to the owner all the avatars present in the blacklist.

 


 

Chapter #7: Options

In the option sub menu is possible to find some additional features aimed to enrich even more the experience with the group gift giver script.

Options Menu

Options Menu

  • 1 per avi: this option will limit the users to get the gifts only once; this feature is useful when working with no-copy items or when a gift limit is set or in general when users can’t get multiple copies of the gifts. If users will try to get gifts for a second time, a warning message will be sent to them, informing they already had the gift once.
  • Avatar age: this option will give the gifts only to avatars whose age (in days) doesn’t exceed a specific value provided. In order to enable this option, owner will be asked to submit the maximum avatar’s age – expressed in days – for the avatars to get the gifts. Avatar exceeding the value will receive a warning message.
  • Hover text: this option will display a custom text – submitted by the owner – on the group gift giver.
  • Notify: if this option is enabled, an IM will be sent to the owner every time a gift is given to someone.

 


 

Chapter #8: MD Labs Online Services

MD Labs Online Services is a responsive website, accessible from any platform from mobile devices to desktop computers, which allow to interact with the products released by MD Labs. Here’s a quick overview of what the the MD Group Gift Giver owner will be able to do:

  • Get a quick overview of all the gift givers, with locations where they are rezzed, total number of gift given;
  • View detailed graphs by giver, date (day/month/year) , region or by customer;
  • Rename a specific giver;
  • Delete all data about a specific gift giver;
  • See the transactions list for any giver;
  • Archive unused givers;
  • Delete a specific transaction from a gift giver;

 


 

Chapter #8.1: Register an account and activate the product

Before accessing the website for the first time, the owner must register an account and activate the service. In order to do so, an Online Services HUD is provided inside the MD Visitor Tracker pack.

MD Labs Online Services HUD

MD Labs Online Services HUD

Once attached the HUD, there are 2 simple steps to follow:

  1. Click on the user icon register of the HUD, and type a password  for the Online Services login.
  2. Click on the check icon activateto activate the MD Visitor Tracker for the Online Services.

At this point it’s possible to open the  MD Labs Online Services website and simply log in.

 


 

Chapter #8.2: MD Group Gift Giver homepage

Once logged in the MD Labs Online Services website, it is possible to access the MD Group Gift Giver section from the ‘Products’ dropdown list on the top of the page. The page that will load is the MD Group Gift Giver homepage and will look similar to this one:

MD Group Gift Giver – homepage

 

The webpage is divided into 2 different tabs (right under the top bar), each one containing specific features:

  • My Givers: it’s the main tab, from here is possible to access the store’s data as well as to a list of all rezzed gift givers and the detailed transactions list of each of them.
  • Archived: this tab lists all the archived givers, the ones that are not used and/or not rezzed anymore in-world. Archiving the givers help keeping data sorted and consistent.

 

The first element in the homepage is the graph panel: the data represented here will vary based on the current view selected. The default view is “by giver” and the graph will show a pie chart with all the givers and their total gift given count.

MD Group Gift Giver – homepage

MD Group Gift Giver – homepage

 

The Tools panels groups together some useful tools to analyze and manipulate the giver’s data. The most important tool of this section is the ‘view‘ drop down list which allow to group, sort and view the data in several ways:

  • by giver: this is the default view, useful to analyze the number of gifts given by each giver;
  • by region: through this view is possible to analyze which regions generate the most traffic;
  • by day: this view is useful to analyze the daily gifts given by the givers;
  • by month: this view is useful to analyze the monthly gifts given by the givers;
  • by year: this view is useful to analyze the yearly gifts given by the givers;
  • by avatar: through this view is possible to analyze the gifts given to each avatar;
  • by gift: through this view is possible to analyze the gift given by each specific gift;

Other useful tools are the ‘delete selected‘ button, which allow the deletion of multiple givers at once, and the ‘export‘ button, which allow to export the data from the current view.

 


 

Chapter #8.3: Basic operations

When the data view is set to ‘by giver‘ some basic operations will be accessible, to perform over every giver listed. These operations are:

  • Turn on/off: this switch toggles the group gift giver’s status in-world between on and off.
  • Gift limit: through this switch it is possible to toggle the gift limit feature on the gift givers in-world. When enabling it, the feature will require to provide the maximum number of gifts that will be given before deactivating the gift giver.
  • 1 per avi: through this switch it is possible to toggle the 1 per avi feature, that limit each customers to get the gifts only once.

 

MD Group Gift Giver – basic operations

 


 

Chapter #8.4: Additional operations

While the data view is set to ‘by giver‘, is possible to perform some additional operations to the group gift givers; all these features are accessible by clicking the 3-dot icon (…) on the right of the giver’s list. A drop down window will appear with the following options:

  • Rename: rename the corresponding giver in-world and on MD Labs Online Services;
  • Reset: reset the corresponding giver in-world;
  • Archive: archive the corresponding giver, removing it from in-world (if present);
  • Delete all given: delete the complete giver’s complete transactions list;
  • Delete: delete the corresponding giver in-world and from MD Labs Online Services, removing also all the transactions and settings;

 

MD Group Gift Giver – additional operations

 


 

Chapter #8.5: Giver’s details: transactions list

As said in the previous chapters, depending on the data view chosen it will be possible to view and analyze different kind of data; the most important is the data view ‘by giver‘, which is also the default one. When this data view is selected, a list of all gift givers rezzed is presented along with the region and total gifts given for each giver. By clicking on the giver’s name the details page for that specific item will load, and will look like this one:

 

MD Group Gift Giver – details

 

The ‘tools‘ panels provides some useful instruments to filter, manage and analyze the giver’s data; it is possible in fact to filter and see only the gifts given during a specific period, delete multiple transactions at the same time and export the transactions list.

The transactions panel is the main panel of this page and presents a complete list of all the gifts given; for each transaction the following data is displayed:

  • Customer’s name;
  • Gift’s name;
  • Transaction’s date & time;

MD Security System User Manual

Quick summary:

 


Initial notes

! IMPORTANT: The following user manual presents and explains the usage and detailed features of:

  • MD Security System version 2.5.0

 

Chapter #1: initial setup & deeding

The setup process for MD Security System is divided into two main steps: the owner registration and the security system’s deeding; while the first step is mandatory and must be done, the second is not always required depeding on the owner’s permission over the land where the MD Security System is rezzed.

Once rezzed the MD Security System, the owner will be asked to touch on it in order to start the registering procedure; a simple touch will do the work and take the owner to the next setup step.

After the first touch to register, the MD Security System will analyze the land where its rezzed on, the owner’s permissions on the land and eventually require for an additional step: the deeding. This is because for the eject feature to work correctly, the MD Security System owner must be the land owner as well, as reqired by Linden Lab.

However, as it happens for many private estates, the land may be owned by a group; in this case, to have complete protection, it’s necessary to deed the MD Security System to the same group that own the land.

In order to do so, simply:

  1. Right click the MD Security System and go to “Edit”and go to the tab called “General”;
  2. Under creator, owner and last owner there is an entry called “Group”, be sure the current group is set to the one owning the land, and if not use the wrench icon to change it;
  3. Click on the checkbox called “Share” to select it;
  4. Click on the “Deed” button;
MD Security System - 01

MD Security System – steps to follow to deed

 

At this point the security system is deeded and the owner will receive a message confirming the operation: the initial setup is now complete.

IMPORTANT: deeding the MD Security System to the land group will force the ‘Group Mode’ feature – once enabled – to work only with the land group the orb is deeded to.


 

Chapter #2: owner menu

Once the MD Security System’s setup is complete, a click of the owner on it will open a menu called ‘owner menu’; this dialog is accessible only by the owner, administrators and managers. Through this menu is possible to configure and manage every aspect of the security system:

  • Active: activate or deactivate the MD Security System;
  • Mode: choose a default behavior for the MD Security System to have toward new avatars found;
  • Access List: define and manage who can interact with the MD Security System, who is allowed in the land and who is banned;
  • Options: customize how the MD Security System protect the area and enable some advanced scan features such as minimum age required, max ARC and more;
  • Advanced: customize the MD Security System behavior and appearance, such as its visibility, hover text, eject message and the notifications;
  • Online Services: access the MD Security System webpage through the MD Labs Online Services website;
  • Update: search for a new product update;
  • Reset: reset the MD Security System;

 

MD Security System – Owner menu

MD Security System – Owner menu

 


 

Chapter #3: basic usage

To start using MD Security System simply rez it on the ground and proceed with the deed, if required. Once done a click will bring up the owner menu; before clicking on the ‘Active’ button it’s necessary to pick a working ‘mode’ from the ‘Mode’ sub-menu. Once done, clicking on ‘Active’ will turn the security system on; the MD Security System’s notification bar will switch from red to green and the orb will scanning the area around.

For more details on the orb’s working mode, please refer to the next chapter of this manual.

MD Security System - 03

Active MD Security System

 

IMPORTANT: By default, the orb will scan a 30 meters spherical area every 30 seconds.

 


 

Chapter #4: mode

Modes define how the security system should behave when one or more avatars are found in the area.

The mode submenu can be reached from the owner menu and is used to set the “default” mode . The owner is asked to choose among several different options:

  • Allow: all the unknown avatars found will be automatically allowed in the area and added to the allow list.
  • Eject: all the unknown avatars found – who are not on the access list – will be automatically ejected.
  • Ban & Eject: all the unknown avatars found – who are not on the access list – will be automatically added to the ban list and ejected.
  • Scan & Eject: all the unknown avatars found not matching the scan options will be automatically ejected; the other ones will be allowed.

 

Mode menu

Mode menu

 

There is one last option in this submenu, called ‘silent’:

  • if ‘silent’ is enabled: once unknown avatars are found, the security system will use the chosen mode automatically, without asking the intervention from the owner or administrators.
  • if ‘silent’ is disabled: once unknown avatars are found, the security system will look for the owner or administrators in the area and (if found), prompt a dialog to them asking to manually pick a specific action toward the avatars found. If no action is taken before the timeout, the orb will use the “default” mode.

 

MD Security System - 05

Owner’s manual action picking when ‘silent’ mode is disabled

 


 

Chapter #5: access list

The access list submenu is the core of MD Security System and allows the owner to define lists of avatars with specific roles and permissions upon the area under control.

The security system’s access list can be divided in two major categories:

  • Control list: define who can control the security system;
  • Access list: define who is allowed or banned from the security system’s area;

The control list is made on a 3-level structure, where each level is a different role:

  • Owner: the highest role, assigned only to one avatar, the security system’s owner; this role has full permissions on the security system;
  • Admin: the second-level role after the owner; admin has a complete control on the security system, with some few exceptions.
    • In general, one admin can:
      • Activate/deactive the security system
      • Set security system’s auto action
      • Add admin, allowed and banned avatars
      • Remove allowed and banned avatars
      • List all avatars in access list
      • Set security system’s scan time and scan range
      • Toggle security system’s visbility, hover text, notifications
    • At the same time, one admin can’t:
      • Remove other admin from security system’s access list
      • Activate/deactive security system’s lock mode
      • Restore security system’s access list
      • Delete the security system
  • Manager: the third-level role after owner and admin; manager has a limited control on the security system.
    • In general, one manager can:
      • Add allowed and banned avatars
      • Remove allowed and banned avatars
      • List all avatars in access list
    • At the same time, one manager can’t:
      • Activate/deactive the security system
      • Set security system’s auto action
      • Remove admin from security system’s access list
      • Remove other manager from security system’s access list
      • Activate/deactive security system’s lock mode
      • Restore security system’s access list
      • Set security system’s scan time and scan range
      • Toggle security system’s visbility, hover text, notifications
      • Delete the security system

Similarly to the control list, the access list is made on a 2-role structure:

  • Allow: avatars with allow role can freely enter the area under the security system’s protection.
  • Ban: avatars with ban role cannot enter the area under the security system’s protection and they will be immediately ejected out if found.

 

access list menu

 

For each role (admin, manager, allow, ban) a list is kept by the MD Security System: users of each list can be added, removed or listed anytime.

The access list submenu presents 3 main buttons corresponding to the main actions that can be performed:

  • Add: the user (owner/admin/manager) will be asked to submit the name or key (uuid) of the avatar to add. If the data submitted is correct, the user will be asked to choose a role for the avatar, among the following: admin (this role is present only if the user adding is the owner or an admin), manager, allow, ban, temp allow, temp ban. In case temp allow or temp ban is chosen, the user will be also asked to submit the timeout period (in hours), among 1 and 244. If the process concludes correctly, the selected avatar will be added to the security system’s list corresponding to the chosen role.
  • Remove: the user (owner/admin/manager) will be asked to choose a list based on the corresponding role where to remove the avatar from; once the role is chosen, the user will be prompted to a list of all the avatars assigned to the selected role. At this point the user will have to choose the desired avatar to remove from the security system’s list.
  • List: list all users present in security system, grouped by role.

 

access list - add menu

access list – add menu

 

Other than role’s lists, the access list menu contains also some additional useful features aimed to enrich and simplify the access lists managing:

  • Auto Sync: when this option is enabled all avatars added or removed from any list (admin, allow, ban) will be automatically added or removed from the access lists of all the security systems belonging to the same owner and present in the same region.
  • Restore NC: clicking on this button will make the MD Security System look in its content for a specific notecard which will contain the access list. If the notcard is found and it’s correctly formatted as required (avatar name or uuid | avatar role), the data will be loaded and the entries in the notecard will be added to the access list.
  • Restore: this feature is similar to the previous but instead of restoring the access list from a notecard, it’s restored from an online backup, automatically stored and mantained by each security system. The owner will be prompted to a list of all the MD Security System owned and will be asked to choose one to use as source for the restore; the access list of the selected security system (source) will be copied (restored) to the requesting one.

 


 

Chapter #6: options

The options submenu contains several specific options and features related to how the MD Security System analyzes and protects the area.

IMPORTANT: Most of the options presented are made to work at their best with the ‘Scan&Eject’ mode.

options menu

options menu

 

  • Pay info: when this option is enabled unknown avatars found in the area without payment info are automatically ejected, without intervention from the owner or administrators.
  • Min age: when this option is enabled unknown avatars found in the area having an age below the minimum allowed are automatically ejected, without intervention from the owner or administrators. Once clicking to enable the feature, the owner is asked to provide a specific age – in days – that will be the limit below which avatars will be ejected.
  • Max ARC: when this option is enabled unknown avatars found in the area having a rendering cost higher than the maximum allowed are automatically ejected, without intervention from the owner or administrators. Once clicking to enable the feature, the owner is prompted to a second dialog window when is mandatory to provide a specific ARC limit that will be used to eject avatars. More details about this feature are at the end of this chapter.
  • Max stay: when this option is enabled the unknown avatars will be allowed into the orb’s area for a specific time, after which they will be ejected automatically without intervention from the owner or administrators. Once clicking to enable the feature, the owner is asked to provide a specific period in minutes (5 to 240) that will be the maximum period the avatars will be allowed.
  • Group mode: by enabling this feature only the avatars member of a specific group and wearing the corresponding tag will be allowed in the area. Owner will be asked to assign the security system to the desired group using the group tool that can be found under right-click > Edit >General tab. Once selected the right group, clicking on the “Group Mode” button will enable the feature. When the group mode is active clicking on the button again will disable it. Please note: once the MD Security System is deeded, this feature will work ONLY with the group the orb is deeded to.
  • Eject home: when this option is enabled banned or unknown avatars will be automatically teleported home when ejected, instead of out the area’s boundaries.
  • Scan time: the scan time defines how often the MD Security System will scan the area under protection; by default, the scan time is set to 60 seconds. Using this button the owner can change the scan time to any value between 20 and 300 seconds.
  • Scan range: the scan range defines the dimension of the area under protection; by default the scan range is 30 meters. Using this button the owner can change the scan range to any value between 1 and 96 meters. Please note: since the security system’s scan sensor uses a spheric shape, 96 meters is the maximum diameter of the protected area, having center in the orb; the effective forward protection distance consist of the radius, which is at max 96/2= 48 meters.
    • MD Security System can also scan the whole parcel: to enable this feauture the owner will have to submit ‘0’ (zero) as scan range value.
  • Show range: clicking this button will display the security system’s protection area, using a corresponding spheric shape. This feature is useful to check if the chosen scan range (1-96) covers the desired area.

 

IMPORTANT: The ARC (“Avatar Rendering Cost”), is a tool to help you understand more about sources of Viewer-side lag. ARC is represented as a point score and shows how each avatar affects the rendering performance of the viewer; the higher the score, the more the avatar affects the rendering performances.

MD Security System, through the ‘Max ARC’ feature, can automatically eject avatars having an higher rendering cost. When the owner setup the feature, will be asked to provide a value for ARC that will act as the limit. Any value between 0 and 500’000 are accepted, but for convenience, 5 different levels are provided as preset corresponding to 5 different ARC limits. In addition i also possible for the owner to provide a custom value for the ARC. Below is shown the ‘Max ARC’ setup dialog:

'Max ARC' setup dialog

‘Max ARC’ setup dialog

 

More details about the ARC can be found here.


 

Chapter #7: advanced

This last submenu groups together some additional features and options related to increase the overall experience with the MD Security System.

Advanced menu

Advanced menu

 

  • Show Orb: toggles the security system visibility, switching it from visible to invisible.
  • Show Info: toggles the hover text shown above the security system.
  • Notify: enables or disables the notification messages sent by the security system to the owner and administrators on relevant events.
  • Eject Msg: with this feature, the owner can change the message sent to the avatars on eject with a custom text.
  • Get Copy: clicking this button will request for another copy of MD Security System, which will be sent to the owner. Please note: this feature is available only in the copy version of MD Security System, since due to deed reasons the orb iteself must have transfer permissions.
  • Delete: this button appears only once the MD Security System is deeded and it’s made to delete the orb when normally not having land permissions to do so.

 


 

Chapter #8: MD Labs online services

MD Labs Online Services is a responsive website, accessible from any platform from mobile devices to desktop computers, which allow to interact with the products released by MD Labs.

MD Security System - 08

MD Security System @ MD Labs Online Services

 

Here’s a quick overview of what the the MD Security System owner will be able to do from the website:

  • Have a complete list of all MD Security System rezzed in-world.
  • Change the MD Security System protection mode (eject/ban/allow/scan)
  • Toggle MD Security System status (on/off) and visibility, rename and delete the security system from in-world.
  • View the access list of a specific security system, sorted by role (admin/allow/ban).
  • View all the warnings and events logged by each security system.
  • Add a specific avatar to the MD Security System’s access list, as admin, allow or banned user, providing the name or uuid.
  • Remove a specific avatar from the MD Security System’s access list.

MD Buy / Buy as Gift User Manual

Quick summary:

Initial notes

The following user manual applies to:

  • MD Buy / Buy as Gift Script
  • MD Buy / Buy as Gift Vendor

When some of the features are available only for a specific version, will be clearly stated.


Chapter #1: initial setup

Depending on the version, the owner will have to either drag the MD Buy / Buy as Gift Script in any object to be used as vendor or just rez the MD Buy / Buy as Gift Vendor. Then, a simple click will prompt the debit permission request. This step is mandatory for the vendor system setup and it’s required to activate the refund system. Clicking on “next” and granting the permission will complete this step.

Once granted the debit permission, the vendor is not already setup for working and some other steps are necessary. If a normal user – different from the owner – clicks on the vendor at this point, will get a message saying the vendor is not yet ready for work. When the owner clicks on the vendor, a dialog menu will appear called “owner menu”: this dialog is visible only by the owner and allow to enter script settings.

The basic setup for the vendor is now done, but to make it working a couple of more additional steps are required.


 

Chapter #2: owner menu

When the owner enters the owner menu, a dialog will appear. From this window, all the script options are accessible to be customized.

owner menu

This menu is divided in many section, some of them leading into other sub menus:

  • Price: this first feature is used to set item and fatpack (if present) price in L$; clicking on the “Price” button will open a submenu where the owner is asked if the price to set is for the item’or the fatpack. Once made the choice, the owner is asked to submit the price in L$. Only integer values bigger than zero are allowed.
  • For Sale: this button acts like a switch, setting the vendor and all its content for sale or not. Setting the vendor for sale is a mandatory step to complete the setup; in order to be set for sale, the vendor should match some criteria:
    • Must contain at least one item to be sold;
    • The item’s price must be set;
    • If a fatpack item is present, the fatpack’s price must be set;

If all the above conditions are verified, clicking the “For Sale” button will set the vendor for sale, giving users the chance to purchase the products. Clicking another time the button will set the vendor to not for sale state and users won’t be able to interact with the vendor.

  • Options: this sub menu groups together all the options present that aim to make this product as flexible as possible. The feature present in this menu are vendor mode, profit split, discount and group mode, notifications, redelivery system, hover text, vendor’s time and limited stock quantity.  The detail of each feature will be explained in the options chapter.
  • Online Services: opens the MD Labs Online Services website, where the owner can interact with all the rezzed vendors. Details about this feauture can be found in the corresponding chapter.
  • Update: this button starts the update module, which will look online for a new update of the product and – if found – deliver it to the owner.
  • Reset: this button will reset the vendor, wiping all the data, including options and price.

Chapter #3: basic usage

The basic usage of a vendor containing the MD Buy / Buy as Gift script is very simple: once rezzed and granted the debit permission, owner will have to drop inside the vendor’s content one or more items that users will be able to purchase. For this step owner’s permission on the selected items are very important: if the owner does not have transfer permission on an item it will be ignored and users won’t be able to purchase it. Morevoer, if owner does not have copy permission on an item it will be considered, but a warning message is sent to remind the owner the only available copy of the item will be given to the first user purchasing it.

Once one or more valid item are dropped inside the vendor’s content, a second step is required: owner infact will have to click the “Price” button and input the item’s price in L$.

At this point, clicking the “For Sale” button will set the vendor for sale, terminating the setup and allowing users to purchase the product inside the vendor.

Users can click the vendor and open the users menu to buy, gift or use the redelivery system. Based on the action choosed among the listed ones, different scenario will take place.

user menu with basic options

user menu with basic options

In case of a normal purchase (“Buy” option), user will be asked to select which item to process – if more than one item is present – from a multi page menu; once the selection is made, the vendor will enter the “pay mode” and user will have to pay the vendor the defined amount – either via right click > pay or simply clicking to make the default Second Life payment window show – within a certain time, defined by the vendor’s timeout. If the timeout is reached the operation will be canceled; on the opposite, if users pays correctly the vendor the selected item will be immediately sent as inventory offer, completing the transaction.

In case of gift (“Gift” option), user will be asked to first submit the name or the key (UUID) of the avatar whom will receive the item. After a valid name or key is passed, the process will run similarly to the normal purchase one; user will infact be asked to select the item to gift and then pay the vendor within the defined time to complete the transaction. The purchased item will be immediately sent to the receiver avatar as inventory offer along with an instant message notifying the gift just received.

In case of redelivery (“Redelivery” option), user will be prompted to a list of item contained inside the vendor and available for redelivery; selecting one of them will trigger a verification request to check if the item has been actually purchased by the requesting avatar. In case a transaction record is found the verification ends with success and the item is sent again to the user as inventory offer.


Chapter #4: demo & fatpack

Other than normal items, MD Buy / Buy as Gift can handle a virtually unlimited number of demo items and one fatpack item. To enable these two features, owner will have drop the demo/fatpack item in the vendor first; in order for the script to correctly identify those special items a reserved keyword in their name is needed:

  • Demo items must contain the keyword ‘DEMO‘ in their name;
  • Fatpack item must contain the keyword ‘FATPACK‘ in its name;

Please note: the keyword can be in any part of the item’s name, but it mandatory to write it with capital letters and without quotes.

Here’s a couple of examples for correct demo items:

  • DEMO Mesh rigged hair;
  • Mesh rigged hair DEMO;
  • (DEMO) Mesh rigged hair;
  • Mesh rigged hair [DEMO];
  • DEMO! MESH RIGGED HAIR;
  • Mesh hair DEMO rigged;

Here’s a couple of examples for correct fatpack items:

  • FATPACK Mesh rigged hair;
  • Mesh rigged hair FATPACK;
  • (FATPACK) Mesh rigged hair;
  • Mesh rigged hair [FATPACK];
  • FATPACK! MESH RIGGED HAIR;
  • Mesh hair FATPACK rigged;

All above examples are correct, since the keyword its written in capital letters and appear in different point of the item name.

Once a new item is dropped inside the vendor, the MD Buy / Buy as Gift Script will scan each item’s name and – using the above keywords – automatically understand if it’s a demo, a fatpack or a normal item. When a demo or a fatpack is found the corresponding feature is automatically enabled, making new options appear in the user menu, like shown below:

user menu with demo and fatpack options

user menu with demo and fatpack options

Important: when a fatpack item is dropped inside a vendor, the MD Buy/Buy as Gift Script will automatically set the vendor not for sale, until the owner will set a price for the fatpack item through the “Set Price” button in the owner menu. Once the fatpack’s price is choosen, clicking the “For Sale” button will set the vendor for sale again.

When a user selects the “Get Demo” option will automatically receive an inventory folder containing all the demo items present inside the vendor; by default, demo items costs 0L$ and this option cannot be changed.

When a user selects “Buy Fatpack” or “Gift Fatpack” options, the normal buy / gift workflow as described in the previous chapter is activated, but applied on the fatpack item.

To disable the demo/fatpack feature owner will just have to remove the corresponding item from the vendor’s content and the MD Buy / Buy As Gift Script will automatically do the rest.


Chapter #5: multiple Setup

MD Buy / Buy as Gift introduces a very useful feature that aims to save time while preparing the vendors. This feature, called ‘multiple setup’, allow the owner to decide whether  apply a specific setting to the current vendor or to all vendors present within the same region at the same time. 

It’s possible to take advantge of this great feature with all options described in the next chapter. Once a feature is chosen from the option sub menu, the owner will be propted to a dialog asking if apply the setting to the single vendor or to all vendors; once the selection is made and the specific option configured, the settings will be applied to the single vendor or all vendors.

 

multiple setup menu

multiple setup menu


Chapter #6: options

In the options sub menu is possible to find a vastity of additional features aimed to enrich the experience with the buy / buy as gift script, adding some specific functions. These features may not be useful to everyone all the times, but will allow the owner to setup more flexible and customized vendors.

options menu

  • Vendor mode: this first button acts like a switch, changing the vendor’s operating mode through Buy&Gift, Buy Only and Gift Only. While the Buy&Gift mode allow users to either buy or gift the items in the vendor, the Buy Only mode removes all the gift options from the user menu, allowing users to only purchase the items for themselves. Similarly, the Gift Only mode allow users to only gift the products, removing every buy options.
  • Split L$: this option allow the owner to split the profit from the vendor with another avatar. Once clicked on this button, the owner will be asked to type the name or UUID (avatar key) of the avatar whom is going to split the profit with, and pick a split percentage between 1% and 99%. If both steps are done correctly, each time a user makes a purchase, the profit is splitted with the avatar declared and the L$ immediately payed out. When this option is active a “check” sign will appear in the corresponding button of the menu and details will be listed in the menu’s header; hitting another time the ‘Split L$’ button will disable the feature.
  • Discount: this option let owner apply a custom discount % to the items present inside the vendor. The owner will be asked to submit a custom discount percentage between 1% and 99%. Once this step is complete, the discounted price is calculated based on the percentage chosen and applied to the item’s cost and to the fatpack too, if present. When this option is active a “check” sign will appear in the corresponding button of the menu and details will be listed in the menu’s header; hitting another time the ‘Discount’ button will disable the feature.
  • Group mode: by enabling this feature only the users wearing a specific group’s tag will be able to interact with the vendor. First, the owner will have to assign the vendor the desired group using the group tool that can be found under right-click > Edit >General tab. Once selected the right group, clicking on the “Group Only” button will enable the feature. When the group only mode is active clicking on the button again will disable it. The basic usage of the group mode will allow only users wearing a specific group tag to be able to use the vendor; however, this feature becomes even more useful when used in combination with the discount. Enabling both the discount and group mode, infact, will allow users having the right group tag to purchase item and fatpack at the discounted price, while the others will have the choice to join the group and pay the discounted price, or proceeding without the right group tag and purchasing at the full price.
  • QTY Limit: this option – if enabled – lets the owner decide a maximum number of items to be sold, after which the vendor will be set sold out. When clicked on the corresponding button, the owner will be asked to submit the number of items available in stock. Once submitted the value, the feature will be immediately activated and for each sale (“buy” or “gift”) the number of available items in stock is decreased by one unit. When no more items are available the vendor is automatically set on sold out and the owner will receive a notification IM.
  • Notify: this option – if enabled – sends the owner an IM each time a users pays the vendor to purchase a product. The IM contains reports the name of the user, the product purchased and the amount payed. If the split L$ option is active, a second IM is sent to the avatar the owner is splitting the income with. When this option is active a “check” sign will appear in the corresponding button of the menu and details will be listed in the menu’s header; hitting another time the ‘Notify via IM’ button will disable the feature.
  • Redeliver: when this option is enabled the “Redelivery” button appears in the users menu, allowing the redelivery system. On the other hand, when this option is disabled, the item redelivery is not possible, since no “Redelivery” button will be present in the users menu. When this option is active a “check” sign will appear in the corresponding button of the menu and details will be listed in the menu’s header; hitting another time the ‘Redelivery’ button will disable the feature.
  • Hover Text: this option when active displays the hover text over the vendor; this text contains useful suggestion and shows the vendor’s status. When this option is active a “check” sign will appear in the corresponding button of the menu and details will be listed in the menu’s header; hitting another time the ‘Hover Text’ button will disable the feature.
  • Vendor Time: this last options represent the amount of time available for the users to interact with the vendor at any step of the purchase process. User infact clicking on the vendor will reserve it for a limited amount of time; if no actions are taken before the timeout, the vendor is set available for the other users. By default the vendor time is 45 seconds, but any value between 30 and 300 seconds is allowed. Clicking on this option owner will have to submit the new vendor time in seconds which will be immediately applied.

A quick side note on Second Life default pay mode & MD Buy / Buy as Gift:

It is normally possible for an avatar to right click on a vendor and select the ‘pay’ option, to directly pay that item without using the vendor’s menu. In this case, the script will consider the purchase as a “Buy” and the item will be delivered directly to the avatar whom paid the vendor.

There are some scenario although, where the MD Buy / Buy as Gift will disable this option to avoid wrong payments and mistakes. This because the right amount to pay may vary depending on group mode, discount and item type (normal item or fatpack). Due to all these reasons and for error preventing, the payment method via right click may be disabled, like shown in the image below:

payment window disabled

payment window disabled

However, there is a particular scenario that represent an exception:

  • No fatpack item present inside the vendor;
  • No discount feature active;

If these conditions are matched, the MD Buy / Buy as Gift will automatically create a button with the corresponding amount in the payment window, like shown in the next image:

payment window enabled

payment window enabled


Chapter #7: MD Labs Online Services

MD Labs Online Services is a responsive website, accessible from any platform from mobile devices to desktop computers, which allow to interact with the products released by MD Labs. Here’s a quick overview of what the the MD Buy / Buy as Gift owner will be able to do:

  • Get a quick overview of all the vendors, with locations where they are rezzed and total profit;
  • Rename a specific vendor (on the website only);
  • Delete all data about a specific vendor (from the website only);
  • See the transaction list for any vendor, including buyer, item bought, item cost, net profit, purchase type, purchase date-time;
  • Delete a specific transaction from a vendor;
  • Display, for each vendor, all the successfull redeliveris;

Before accessing the website for the first time, the owner must register an account and activate the service. In order to do so, an Online Services HUD is provided inside the MD Buy / Buy as Gift pack.

MD Buy_Buy as Gift - MD Labs Online Services HUD

Once attached the HUD, there are 2 simple steps to follow:

  1. Click on the user icon register of the HUD, and type a password  for the Online Services login.
  2. Click on the check icon activateto activate the MD Buy / Buy as Gift for the Online Services.

At this point it’s possible to open the  MD Labs Online Services website and simply log in; once successfully logged in, select ‘MD Buy / Buy as Gift’ from the product drop down list on top and the main page will load.

The main page is divided in two different tabs, the first one is called ‘Data’ and the second one is called ‘Graph’; inside the Data tab a full list of all the vendors rezzed in-world is displayed, reporting also the region where the vendor is rezzed and the total profit in L$ made by the single vendor. A box named ‘Tools’ allows to change view and data source in order to lead multiple data analysis, other than exporting the data.

 

md labs online services for md buy / buy as gift - main page

md labs online services for md buy / buy as gift – main page

 

Once selected a specific view and a data source, the ‘Graph’ tab will show an accurate graphic rapresentation of it, like shown in the image below:

md labs online services for md buy / buy as gift - main page (graph tab)

md labs online services for md buy / buy as gift – main page (graph tab)

 

By clicking on a specific vendor in the ‘Data’ tab its possible to check the full transactions list of the vendor, with detailed infos about the payer, the receiver, the amount paid and such.

 

md labs online services for md buy / buy as gift - detail page

md labs online services for md buy / buy as gift – detail page


Chapter #8: SL Marketplace integration

MD Labs Online Services also offer the opportunity to integrate SL Marketplace data inside the Online Services website. This means all the sales made through the SL Marketplace will be listed inside the Online Services website, giving a complete and detailed view of both in-world and Marketplace.

In order to integrate SL Marketplace with MD Labs Online Services a quick and easy setup is required. The procedure can be summarized in these few steps:

  1. Open your SL Marketplace webpage and select ‘Merchant home‘ from the ‘My Marketplace‘ drop down list on the top.
SL Marketplace Integration - Step 1

SL Marketplace Integration – Step 1

 

2.  Select  “Automatic Notifications (ANS)” from the left drawer.

SL Marketplace Integration – Step 2

 

3. Add ‘http://mattiahost.altervista.org/Generic/ans.php’ (without quotes) in the ‘Notification URL‘ field.

SL Marketplace Integration - Step 3

SL Marketplace Integration – Step 3

 

At this point, the integration is complete and all the future sales on SL Marketplace will be automatically listed inside the MD Labs Online Services website.


Chapter #9: user menu

Depending on the setup chosen by the owner, once a user click on the vendor a menu is shown containing many options; this guide will cover all the possible features, but not all of them may be present at any time.

user menu

user menu

  • Get demo: clicking on this button the user will receive a folder containing all the demo items inside the vendor. The cost of this operation is always 0L$.
  • Buy: this option allow the user to purchase one of the item inside the vendor. If more than one item is present, the user will be promtped to a multi page menu, where the desired product must be selected. Once the selection is made the vendor will set itself in pay mode, waiting for the user to pay the amount requested; a timer is started at this point and if no actions are taken before the timeout the operation is canceled and the vendor is set available again. A simple click on the vendor will open the default Second Life payment window and once the user pays the vendor, the item selected will automatically be sent as inventory offer.
  • Gift: this option let users gift an item from the vendor to another avatar. As first thing, user will be asked to subit the name or the key (UUID) of the avatar receiving the gift. If the submitted value is correct  the process will proceed and if more than one item is present, the user will be promtped to a multi page menu, where the desired product must be selected. After this step the vendor will set itself in pay mode, waiting for the user to pay the amount requested; at this point the work flow is the same as for the buy option; once user pays the vendor the requested amount the item purchased is sent to the receiving avatar as inventory offer, and an instant message is sent as well, notifying the receiver about the gift.
  • Buy Fatpack: this option allow user to purchase the fatpack from the vendor. The process is exactly the same as the “Buy” one described above, just applied to the fatpack.
  • Gift Fatpack: this option allow user to gift the fatpack from the vendor to another avatar. The process is exactly the same as the “Gift” one described above, just applied to the fatpack.
  • Redeliver: this last option let user request for the redelivery of a product already purchased. User will be prompted to a list of item contained inside the vendor and available for redelivery; selecting one of them will trigger a verification request to check if the item has been actually purchased by the requesting avatar. In case a transaction record is found the verification ends with success and the item is sent again to the user as inventory offer.

MD Labs Online Services

Overwiew

MD Labs Online Services represents an effort to provide the perfect companion to the products released by MD Labs.

This companion comes in the shape of a responsive website, that will collect and display data from in-world products, allowing user to interact with them as well. MD Labs Online Services is totally free and without any hidden costs, available for anyone who purchased one of the compatible products listed below:

Depending on the product, different features, data and interaction will be available. In many cases user will be able not only to view the data collected in-world, but also interact with the product directly from the website, without any intervention in-world.

Last, the website have been designed to be easy to use, light and flexbile, being able to adapt automatically to every kind of displays, from desktop to laptops, from smartphones to tablets; this way user will always be able to login indipendently from the device used and enjoy the experience.

 

Initial setup

In order to be able to login and enjoy the features provided by MD Labs Online Services, user is asked to complete the setup process, which is divided into two main steps:

  1. Account registration
  2. Product activation

Both these steps are very quick and easy to perfom and the only tool required is the Online Service HUD that is provided with the product purchased.

MD Labs Online Services Manager - HUD version

MD Labs Online Services HUD

 

Once wear the HUD the menu will drive the user through the two simple steps required.

 

1. Account registration

The first step is the account registration, which will create a user profile to log in the MD Labs Online Services website.

! IMPORTANT: the user account is unique for all products working with the MD Labs Online Services website. This means the registration process is only required at the first time; if other products compatible with the MD Labs Online Services are purchased, user will be asked directly to activate the product, and will be able to login using the account created.

In order to proceed, user will have click on the the user icon register of the HUD, or on the corresponding “Register” button in the display version. User will then be asked to choose and submit a password for the account: this password can’t be blank and it will be used – along with the avatar name – to login the Online Services website. Submitting a valid password will create the account and finish this first setup step.

Please note: password can be changed anytime using the “change password” feature available on the Online Service Manager.

 

2. Product activation

The second step is the product activation, which will add the current purchased product to the ones available for the user. User will have to click on the check icon activate of the HUD or on the corresponding “Activate” button in the display version. The Online Services Manager will communicate with the website and do the rest, activating the corresponding product.

At this point, the setup process is completed, and the user can log in the MD Labs Online Services website.

 

Login and utilization

To login, user will have to go to the page of MD Labs Online Services and provide the Second Life avatar name or key (UUID) and the password chosen in the account registration step.

MD Labs Online Services login page

MD Labs Online Services login page

 

Once successfully log in, the Online Services home page will open and the user will find the products activated for Online Services under the “Product” drop down list, on the top of the home page, like shown below:

MD Labs Online Services home page

MD Labs Online Services home page

 

Change/reset password

To change or reset the MD Labs Online Services’s password, the user has two different options: from the Online Services website or through the MD Labs Online Services HUD.

To change password from the MD Labs Online Services website, the user has to perform the login and reach the ‘Preferences’ panel on the right side of the Home. A ‘change password’ link is present to start the procedure.

If for some reason the  user is unable to login the MD Labs Online Services website, a second option to change or reset the password consist in wearing the MD Labs Online Services HUD that is included with the product purchased. Once the HUD is on, simply clicking to the key icon password will lead the user to the password change procedure.

 

MD Labs Online Services HUD

MD Labs Online Services HUD – Key icon to change/reset the user’s password