MD Visitors Tracker User Manual

Quick summary:

 

Initial notes

! IMPORTANT: The following user manual applies to:

  • MD Visitor Tracker & Greeter version 2.0.0
  • MD Visitor Tracker & Greeter (Bulb) version 2.0.0
  • MD Visitor Tracker & Greeter (Notepad) version 2.0.0
  • MD Visitor Tracker Board & Greeter version 2.0.0

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

 


 

Chapter #1: initial setup

The setup of MD Visitor Tracker is very easy and quick: owner will have to simply rez the tracker in-world and wait a few seconds for the automatic setup to complete.

Once done, when the owner clicks on the tracker, a dialog menu will appear, called “owner menu”: this dialog is visible only by the owner and allow to enter the visitor tracker’s settings.

The basic setup for the visitor tracker is now done, but some additional steps are required.

 


 

Chapter #2: owner menu

When the owner clicks the visitor tracker, the configuration menu is displayed. This particular menu – accessible by the owner only – contains all the settings and options of the tracker.

md visitors tracker - 01

MD Visitor Tracker – Owner Menu

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

  • Active: this button turns the tracker on/off, enabling or disabling the scan of the area specified.
  • Report: if enable, this option make the tracker send a daily IM to the owner, containing the visitors list for the current day.
  • Notify: if enable, this option will send an IM to the owner every time a new visitor is found.
  • Options: this sub menu groups together some advanced features, such as the greeter & giver module, scan time and scan range configuration, hover text and more. The detail of each features will be explained in the options chapter.
  • Appearance: this sub menu interact with the appearance of the visitor tracker, prodiving serveral options. These features will be described in details in the appearance section of this user guide. Please note: different features in the appearance menu are available with different versions of MD Visitor Tracker, as will be described.
  • List Visitors: this button will list to the owner the daily visitors list, with date & time.
  • Online Services: opens the MD Labs Online Services website, where the owner can interact with all the trackers. 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 visitor tracker, wiping all the data, including options and visitor list.

 


 

Chapter #3: basic usage

The basic usage of the MD Visitor Tracker is very simple: once rezzed it’s immediately ready to work and clicking on the ‘Active’ button will start the scan of the area for visitors. By default, the tracker will work with these settings, that can be customized anytime:

  • scan time: 45 seconds. This value can be changed through the ‘Options’ menu, more details in the corresponding chapter.
  • scan range: 20 meters. This value can be changed through  the ‘Options’ menu, more details in the corresponding chapter.
  • timezone: UTC. This value can be changed through  the MD Labs Online Services website, more details in the corresponding chapter.

With these values, the tracker will scan every 45 seconds an area of 20 meters; if new avatars are found, an IM will be sent to the owner, reporting the name of the visitor and the visit date-time, in UTC format. Also, every 24 hours from the tracker’s activation the daily visitors list will be sent to the owner as IM.

Please note: by default, no greet message nor item (landmark, notecard, object) is sent to the visitors. You can change this behavior through the corresponding features in the ‘Options’ sub menu.

 


 

Chapter #4: options

In the option sub menu is possible to find some additional features aimed to enrich the experience with the visitor tracker.

md visitors tracker - user manual - 02

MD Visitor Tracker – Options Menu

  • Greeter: through this button the owner can enable the greeter module for MD Visitor Tracker; the owner will be asked to provide a text message that will be sent to each avatar found. Once the feature is active, clicking on the greeter button again will disable it.
  • Giver: through this button the giver module of MD Visitor Tracker can be configured; by clicking, the owner will be prompted to a submenu where will be asked to choose which type of item give to each new visitor found. There are 3 main item’s type that can be chosen: landmark, notecard, object; the owner can choose one or multiple types of items. Please note: to activate this feature, one item of the chosen type must be present into the MD Visitor Tracker’s content.
  • Visible: this option toggle the tracker’s visibility. Please note: this option is available only for
    • MD Visitor Tracker & Greeter
    • MD Visitor Tracker & Greeter (Notepad)
  • Hover Text: through this option the owner can set a custom text to be displayed on the MD Visitor Tracker as hover text; after clicking, the owner will be asked to submit a valid text. Once the hover text is set, clicking on the button again will disable it.
  • Scantime: scan time represents how often the tracker will scan around for new visitors; by default this value is set to 45 seconds, this means MD Visitor Tracker will perform a scan of the area every 45 seconds. This value can be changed through this button: the owner will be asked to provide the new scan time value, submitting a value between 5 and 900 seconds.
  • Scanrange: scan range represents how far the tracker will scan for new visitors; by default this value is set to 20 meters, this means MD Visitor Tracker will perform a scan of a 20 meters wide area. This value can be changed through this button: the owner will be asked to provide a new value for scan range: any value between 1 and 96 meters is valid; by submitting ‘0’ (zero), the owner will enable the parcel-wide scan.
  • Show Range: once enabled, this option will show the scan range as a semi-transparent sphere around the MD Visitor Tracker; this is useful to get a visual idea of the area under the tracker’s control.

 


 

Chapter #5: appearance

This sub menu groups together all the features aimed to change the MD Visitor Tracker’s appearance.

Please note: depending on the version of MD Visitor Tracker, different options will be available inside this menu.

md visitors tracker - user manual - 03

MD Visitor Tracker – Apperarance Menu

 

  • Hover Text Color: through this button the owner can change the color for the hover text, if displayed.
  • Text Color: through this button the owner can change the color for the board’s main face. Please note: this setting is available ONLY for MD Visitor Tracker Board.
  • Show Logo: through this button the owner can show/hide the logo space on the tracker board. Please note: this setting is available ONLY for MD Visitor Tracker Board.

 


 

Chapter #6: 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 Visitor Tracker owner will be able to do:

  • Get a quick overview of all the trackers, with locations where they are rezzed, total number of visit;
  • View detailed graphs by tracker, date (day/month/year) , region or by visitor;
  • Change tracker’s default timezone from here;
  • Rename a specific tracker;
  • Delete all data about a specific tracker;
  • See the visitors list for any tracker, including visitor name and visit date-time;
  • Archive unused trackers;
  • Delete a specific visit from a tracker;

 


 

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

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 #6.2: MD Visitors Tracker homepage

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

MD Visitors Tracker – homepage

 

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

  • My Trackers: it’s the main tab, from here is possible to access the store’s data as well as to a list of all rezzed trackers and the detailed visitors list of each of them.
  • Archived: this tab lists all the archived trackers, the ones that are not used and/or not rezzed anymore in-world. Archiving the trackers 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 tracker” and the graph will show a pie chart with all the trackers and their total visit counted.

 

MD Visitors Tracker – homepage

 

The Tools panels groups together some useful tools to analyze and manipulate the tracker’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 tracker: this is the default view, useful to analyze the number of visitors counted by each tracker;
  • 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 visitors counted by the trackers;
  • by month: this view is useful to analyze the monthly visitors counted by the trackers;
  • by year: this view is useful to analyze the yearly visitors counted by the trackers;
  • by visitor: through this view is possible to analyze the visits from each visitor;

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

 


 

Chapter #6.3: Basic operations

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

  • Turn on/off: this switch toggles the tracker’s status in-world between on and off.
  • Calculate profit: this toggle enables or disables the integration of MD Visitors Tracker with MD Vendor System – the vendor solution from MD Labs. When this option is enabled, if MD Visitors Tracker is used along with MD Vendor System in the same area (i.e. an in-world store), then the tracker will calculate the amount in L$ earned from each visitor through the vendors running MD Vendor System. PLEASE NOTE: this option appears only if MD Vendor System is regularly purchased.
  • Quick Peek: this feature allows the user to retrieve a list of the visitors currently present in the tracker’s area. As the name of this feature says, it is a quick peek of what is going on in-world, without actually needing to be logged in.

 

MD Visitors Tracker – basic operations

 


 

Chapter #6.4: Additional operations

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

  • Rename: rename the corresponding tracker in-world and on MD Labs Online Services;
  • Reset: reset the corresponding tracker in-world;
  • Merge: merge the corresponding tracker with another one, associating all the visitors to the new tracker and removing the old one from in-world and from MD Labs Online Services;
  • Archive: archive the corresponding tracker, removing it from in-world (if present);
  • Delete all visits: delete the complete tracker’s visitors list;
  • Delete: delete the corresponding tracker in-world and from MD Labs Online Services, removing also all the visitors list and settings;

 

MD Visitors Tracker – additional operations

 


 

Chapter #6.5: Tracker’s details: visitors 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 tracker‘, which is also the default one. When this data view is selected, a list of all trackers rezzed is presented along with the region and total visitors for each tracker. By clicking on the tracker’s name the details page for that specific item will load, and will look like this one:

MD Visitors Tracker – details

 

The first part of the page contains an useful graph showing the daily visitors for the selected tracker; below this graph two other panels are present, containing the tools and the visitors list.

MD Visitors Tracker – details

 

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

The visits panel is the main panel of this page and presents a complete list of all the visitors tracked; for each visit the following data is displayed:

  • Visitor’s name;
  • Visit date & time;
  • Visit duration;

 

MD Vendor System Plugin – Store Credit & Gift Card User Manual

Quick summary:

 


 

Chapter #1: overview & setup

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

  • MD Vendor System Plugin – Store Credit & Gift Card version 1.1.0

 

Store Credit & Gift Card plugin add the following features to MD Vendor System:

  • Enable store credit’s payment on the vendors;
  • Enable gift card’s payment on the vendors;
  • Create store’s gift card to sell and use;
  • Create promo codes, with specific discount % and validity rules, to be used as payment options on the vendors;

PLEASE NOTE: the store credit & gift card plugin is sold separately and it’s included only inside the MD Vendor System (full pack).

The plugin’s installation is very quick and simple: just drop the script inside the vendor along with the MD Vendor System ‘core’ plugin: the plugin will be automatically detected and installed. A message sent on chat will notify the owner of the successful installation.

At this point, to access the plugin’s specific settings the owner will have to go to the owner menu > plugin sub menu, where all installed plugins are listed.

md_vendor_system_14

Owner Menu – Plugin sub menu

 

By clicking on the corresponding ‘Credits’ button, the plugin’s specific menu will load, presenting all the available options:

Store Credit & Gift Card Plugin – Menu

Store Credit & Gift Card Plugin – Menu

 

  • Store Credit: toggles on/off the store credit payment method for the selected vendor; the owner will be asked to provide a % of the purchase earning that will be converted as store credits. More details about this feature in the corresponding chapter.
  • Gift Card: toggles on/off the gift card payment method for the selected vendor. More details about this feature in the corresponding chapter.
  • Promo Code: toggles on/off the promo code payment method for the selected vendor. More details about this feature in the corresponding chapter.
  • Update: this button will search online for plugin’s update and deliver it to the owner, if found.
  • Back: this button navigate back to the plugin sub menu.
  • Main Menu: this button navigate back to the owner menu.

 

Once installed the Store Credit & Gift Card plugin, on MD Labs Online Services website two tabs will appear:

  • the ‘Store Credit & Gift Card‘ tab will list all users having store credits and/or gift card credit; the owner is able to add credits to a specific user’s balance – if already listed – or add a new user from scratch, with a custom balance assigned.
  • the ‘Promo Codes‘ tab will list all the promo codes – active and not – with detailed info about their validity and settings; the owner is able to add or remove codes that users will use to get discounts.

 

Store Credit & Gift Card Plugin @ MD Labs Online Services

 

When a credit payment option is enabled, once the user click on the vendor and select among pay or gift, will be prompted to a window where is asked to choose the payment method among:

  • L$: complete the purchase using the L$ balance as payment method (this option is ALWAYS present);
  • Store Credit: complete the purchase using the store credit’s balance as payment method (this option is present ONLY if enabled through the plugin);
  • Gift Card: complete the purchase using the gift card credit’s balance as payment method (this option is present ONLY if enabled through the plugin);
  • Promo Code: use a promo code and benefit of the associated discount (this option is present ONLY if enabled through the plugin);

 

md_vendor_system_credits_03

User Menu – Payment method selection

 

As the user chooses the payment method and pay, the transaction will be complete and the purchased item delivered.

On MD Labs Online Services website, for every transaction is reported the payment method, as shown below:

md_vendor_system_27

MD Labs Online Services – Payment Method

 

To uninstall the plugin simply remove it from the vendor’s content and the vendor will automatically update, removing the additional features.

 


 

Chapter #2: store credit

To enable the store credits as payment option, the owner has to hit the corresponding “Store Credit” toggle inside the plugin’s menu; at this point a window will pop up, asking the owner to submit the % of the product’s cost that will be converted into store credits and added to the user’s balance.

! IMPORTANT: by default, 1 store credit = 1 L$.

Once the requested value is submitted, the store credit feature will be immediately activated, adding the payment option in the user’s menu. From now, for every purchase made (entirely or partially) with L$, an amount of store credits are added to the user’s balance; the number of store credit to add is calculated as the submitted conversion percentage of the item’s total price.

For example, if the cost of the purchased item is 300L$ and the store credit percentage is 10%, 30 store credits will be added to the user’s balance.

The store credits are added immediately after the purchase and the users are able to check their current balance anytime, by clicking on the “View Balance” button in the vendor’s users menu.

MD Vendor System supports also ‘mixed’ payments: a mixed payment (in this case) is made partially by store credits and partially by L$. This scenario can occur if the user selects store credits as payment option but doesn’t have enough credits to purchase the item. In this specific case, MD Vendor System will prompt the user a window asking if abort the purchase process or complete it using L$ to pay the remaining cost of the item.

md_vendor_system_28

User Menu – Mixed Payment with store credits

If the user decides to complete the purchase using the L$ for the remaining amount, the vendor will set itself in ‘pay mode’, waiting for the payment; once it’s correctly performed, the product will be delivered and the purchase correctly finalized. In this case, the payment method for this transaction on MD Labs Online Services will be “Store Credit & L$“.

PLEASE NOTE: in case of mixed payment with store credits and L$, the amount of store credits to add to the user’s balance is calculated ONLY on the part paid using the L$ balance.

 


 

Chapter #3: gift card

As for store credit, gift card payment option can be activated by the owner clicking on the corresponding toggle “Gift Card” in the plugin’s menu. No particular setup is required to activate this feature.

! IMPORTANT: by default, 1 gift card credit = 1 L$.

Once the requested value is submitted, the gift card feature will be immediately activated, adding the payment option in the user’s menu; users are able to check their current balance anytime, by clicking on the “View Balance” button in the vendor’s users menu.

As for store credit, MD Vendor System supports ‘mixed’ payments also or gift cards: if the user selects gift card as payment option but doesn’t have enough credits to purchase the item, MD Vendor System will prompt the user a window asking if abort the purchase process or complete it using L$ to pay the remaining cost of the item.

md_vendor_system_29

User Menu – Mixed Payment with gift card

 

If the user decides to complete the purchase using the L$ for the remaining amount, the vendor will set itself in ‘pay mode’, waiting for the payment; once it’s correctly performed, the product will be delivered and the purchase correctly finalized. In this case, the payment method for this transaction on MD Labs Online Services will be “Gift Card & L$“.

PLEASE NOTE: in case of mixed payment with gift card and L$ (if the store credit feature is active) the amount of store credits to add to the user’s balance is calculated ONLY on the part paid using the L$ balance.

Along with the Store Credit & Gift Card Plugin, a pack is included: MD Gift Card Creator Kit. This particular pack contains the script & tools required to create the gift cards that will be sold and used by customers.

! IMPORTANT: the only gift cards compatible with MD Vendor System are the ones using MD Gift Card Creator Kit, other gift cards using different systems will NOT work!

In the next chapter is described how to setup a gift card step by step, using MD Gift Card Creator Kit.

 


 

Chapter #4: setup a generic gift card

The MD Gift Card Creator Kit contains the script & tools to required to create gift cards to use along with MD Vendor System. This pack is provided with Store Credit & Gift Card Plugin and comes boxed as reported below:

MD Gift Card Creator Kit

MD Gift Card Creator Kit

 

Once unpacked, the content of the creator kit will look like this:

MD Gift Card Creator Kit – Content

The two important item on this creator kit are:

  • MD Gift Card Script: this is the script required by any gift card to work. It comes with copy&transf permissions and can be dropped either on a prim or inside a HUD.
  • MD Gift Card Template HUD (Full Perm): this HUD comes with full permissions and represents a template HUD for creating MD Gift Cards.

 

PLEASE NOTE: this chapter will explain the step-to-step guide for creating generic gift cards using ONLY the MD Gift Card Script. This means the gift cards created can be either object to rez/attach or third-party HUD; if you want to read how to create gift cards using the template HUD included, please refer to the next chapter.

The setup of a generic gift card is simple and quick and can be divided into 3 main steps:

  1. Change MD Gift Card Script’s next owner permissions;
  2. Drop MD Gift Card Script inside an object that will work as gift card;
  3. Configure MD Gift Card Script’s amount and additional features;

As first step, a change on the next owner’s permissions is required: as mentioned before, MD Gift Card Script comes with copy&transf permissions, but in order to be used, the next owner’s permissions MUST be set to transfer only. This because a single gift card will be transfer only, so a user can gift and pass it to another, but not take a copy of it.

md_vendor_system_31

MD Gift Card Script – Change of next owner’s permissions

 

Once done with this first step, the MD Gift Card Script can be dropped inside the object/prim that will work as gift card; if the script is dropped with the wrong permissions will automatically delete itself and another copy (with the right permissions) will have to be dropped.

In order to configure the gift card in the best way, the owner should rez the object on the ground and drop the MD Gift Card Script inside. Once the script is inside the object and rezzed on the ground, the step 2 is complete and only the last step is left.

Clicking on the object/gift card rezzed on the ground a configuration menu will be presented to the owner, containing only a few options:

md_vendor_system_32

MD Gift Card Script – Gift card configuration

  • Set amount: this button will ask the owner to submit the gift card’s amount in L$. This is the only value required during this configuration step.
  • Help: this button loads the MD Vendor System plugin user manual.

By clicking “set amount” and providing a valid number greater than 0, the gift card’s value will be set to that corresponding amount in L$. At this point the gift card’s setup is complete and the object can be picked up in inventory, ready to be sold. Clicking “set amount” again, the owner can change the gift card’s amount any time before selling it.

! IMPORTANT: after setting or changing the gift card’s amount, the owner MUST NOT change the object/prims’s description, as some relevant information are stored that – if changed – could lead to the gift card break.

Customers purchasing the gift card will be able to either wear or rez the gift card on the ground to get a menu where they will be asked if ‘use’ the gift card, adding the amount to their balance and making the gift card unusable. As additional feature, an animation or pose can be dropped inside the gift card along with the MD Gift Card Script: this animation will be played automatically every time the user will wear the gift card.

The gift card is now ready to be sold.

TIP: MD Vendor System can be easily used also to sell gift cards, handling them as ‘normal’ items (1 per vendor). This way owner will have a complete track of the income made by gift cards, integrated with MD Labs Online Services as well.

 


 

Chapter #5: setup a gift card with the template HUD

This chapter explain how to create a gift card HUD (Heads-up displays) using the template included inside the MD Gift Card Creator Kit.

Once unpacked, the content of the creator kit will look like this:

MD Gift Card Creator Kit - Content

MD Gift Card Creator Kit – Content

 

The object called ‘MD Gift Card Template HUD (Full Perm) is the HUD itself that will be used to create the gift cards. This HUD comes empty and with full permissions so to be highly customizable: it will only require the MD Gift Card Script to work.

The setup of the MD Gift Card Template HUD can be divided into few main steps:

  1. Rez the MD Gift Card Template HUD (Full Perm) on the ground;
  2. Change the MD Gift Card Template HUD (Full Perm) next owner permissions to transfer-only;
  3. Change the MD Gift Card Script next owner permissions to transfer-only;
  4. Drop the  MD Gift Card Script inside the MD Gift Card Template HUD (Full Perm);
  5. Click the ‘Set Amount’ button on the MD Gift Card Template HUD (Full Perm) to setup the gift card;
  6. Customize the MD Gift Card Template HUD (Full Perm) with personal texture and logo;
  7. Take the MD Gift Card Template HUD (Full Perm) in inventory and rename it.

 

(1) As first step, the MD Gift Card Template HUD (Full Perm) has to be rezzed on the ground; once done it will look like this:

md_vendor_system_credits_06

MD Gift Card Template HUD (Full Perm)

 

(2) Once rezzed, the first thing to do is change the gift card template next owner permissions to transfer-only:

MD Gift Card Template HUD (Full Perm) - change of next owner's permissions

MD Gift Card Template HUD (Full Perm) – change of next owner’s permissions

 

(3) The MD Gift Card Script – included inside the MD Gift Card Creator Kit – needs to have its next owner permissions changed to transfer-only as well:

MD Gift Card Script – Change of next owner’s permissions

 

(4) Once both MD Gift Card Template HUD (Full Perm) and MD Gift Card Script next owner permissions are set to transfer-only, the MD Gift Card Script has to be dropped inside the MD Gift Card Template HUD (Full Perm). At this point, the MD Gift Card Script will perform a permissions check over itself and on the HUD; if wrong permissions are found, the script will print a warning message on the local chat before deleting itself.

(5) As both MD Gift Card Template HUD (Full Perm) and MD Gift Card Script next owner permissions are set up correctly, it will be possible to setup the gift card’s amount clicking on the ‘Set Amount’ button and providing a value greater than 0 (zero): the gift card’s value will be set to that corresponding amount in L$.

! IMPORTANT: the gift card setup has to be done with the MD Gift Card Template HUD (Full Perm) rezzed on the ground and not attached. Moreover, after setting or changing the gift card’s amount, the owner MUST NOT change the HUD’s description, as some relevant information are stored that – if changed – could lead to the gift card break.

(6) It’s now possible to customize the MD Gift Card Template HUD (Full Perm)’s appearance by dropping a texture for the background and for the store logo:

md_vendor_system_credits_08

MD Gift Card Template HUD (Full Perm) textured

 

PLEASE NOTE: the ‘Set Amount’/’Use Card’ and ‘Help’ button’s texture cannot be changed.

(7) At this point the MD Gift Card Template HUD (Full Perm) is setup and ready to be sold; it can be taken in inventory now and renamed.

Customers purchasing the gift card will be able to wear the HUD and be able to ‘use’ the gift card, adding the amount to their balance and making the gift card unusable. As additional feature, an animation or pose can be dropped inside the gift card along with the MD Gift Card Script: this animation will be played automatically every time the user will wear the gift card.

TIP: MD Vendor System can be easily used also to sell gift cards, handling them as ‘normal’ items (1 per vendor). This way owner will have a complete track of the income made by gift cards, integrated with MD Labs Online Services as well.

 


 

Chapter #6: use a gift card

These few lines will explain you how to use a gift card, received as gift or bought.

As first thing wear the gift card by double clicking on it from the inventory, or right clicking and select ‘Add’: a menu will appear, like the one reported below:

md_vendor_system_33

MD Gift Card – User Menu

In the dialog it is reported gift card’s amount in L$ and there are two main buttons:

  • Use Card: this button will start the gift card’s utilization process, which will add the gift card’s amount to your balance.
  • Help: this button loads this user manual.

By clicking on “Use Card”, a second dialog will open asking for confirmation:

md_vendor_system_34

MD Gift Card – Use card confirmation

 

By clicking on “use”, the gift card’s amount will be added to your current balance and the gift card will not be valid anymore; you can now detach the gift card and delete it.

You can now use your credit simply by clicking on a vendor which supports gift card credit as payment, selecting if buy or gift the product and using “gift card” as payment method. The product’s cost will be subtracted from your gift card’s credit balance. You can check your balance anytime by clicking on a vendor which supports gift card credit as payment and selecting “View Balance”.

 


 

Chapter #7: promo codes

A promo code is a special code which is associated to a discount, whether in a percentage or a specific amount in L$. MD Vendor System – Store Credit & Gift Card Plugin allow the owner to create as many promo codes as wanted, each one associated to a specific discount, that can be distributed and utilized during the purchase process. When purchasing from a vendor having the promo code feature enabled, in fact, the user will be asked to submit a promo code which – if valid – will apply the specific discount on the current transaction.

When creating a promo code, there are some basic settings to setup:

  • The promo code MUST be 3 to 8 characters long;
  • The promo code MUST contain only alphanumeric characters (a-z, A-Z, 0-9);
  • The promo code MUST be associated to a discount:
    • Using a percentage (%), between 1 and 99;
    • Using a fixed amount (L$);
  • The promo code’s utilization MUST be associated to one of the following:
    • Everyone: everyone having the promo code can use it and benefit of the discount;
    • Group members: only members of a specific group are able to use the promo code and benefit of the discount;
    • Specific avatar: only one defined avatar is able to use the promo code and benefit of the discount;

Along with these basic settings there are also several optional ones, aimed to customize even more the promo code. Those settings aren’t mandatory for the promo code to be created and used, but can enrich the whole experience.

  • Promo code utilization limit: define how many times a single avatar can use a specific promo code;
  • Promo code validity period: a validity start time and end time (in SLT) defining a period when the promo code is accepted by the vendors;
  • Promo code vendor: associate the promo code to a specific vendor, which will be the only one accepting the code;
  • Promo code region: similar to the previous one, associate the promo code to a specific region. Only the vendors in the region will accept the code;

 

Promo Codes are managed through the MD Labs Online Services website, inside the MD Vendor System product page. A tab called ‘Promo Codes’ is present, containing a list of all the codes with all the features and the button to create a new one.

MD Vendor System - Promo Codes

MD Vendor System – Promo Codes

 

To create a new promo code, simply click on the ‘Add Code’ button, a wizard window will appear:

Promo Codes - Create new code

Promo Codes – Create new code / basic setup settings

 

The code creation wizard is divided into two main parts: basic setup and advanced settings. The first contains the basic aspects of the promo code, mandatory for the creation: code name, discount type and amount, promo code’s utilization. The second one – accessible by clicking on the gears icon – contains a set of advanced settings, which are optional: code utilization limit, code’s validity period, code’s vendor or region association.

 

Promo Codes - Create new code / advanced settings

Promo Codes – Create new code / advanced settings

TIP: by placing the mouse on the many question marks in the creation wizard, a popup window will be displayed, containing useful suggestions.

Once filled the basic setup section and the desired features from the advanced settings, clicking on the red ‘Add Code’ button will immediately create the promo code, adding it to the code’s list; the promo code is ready to be distributed and used by the customers.

When the customers click a vendor having the promo code feature enable, a ‘Promo Code’ button will appear among the payment methods; by clicking they will be asked to submit the promo code and – if the code is valid and compliant to all the restrictions – the associated discount will be applied to the product’s cost.

MD Vendor System - Promo code as payment method

MD Vendor System – Promo code as payment method

 

MD Vendor System Plugin – Remote Control User Manual

Quick summary:

 


 

Chapter #1: overview & setup

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

  • MD Vendor System Plugin – Remote Control version 1.1.0

Remote Control plugin add some very interesting features to MD Vendor System:

  • Configure and control the vendor from MD Labs Online Services website;
  • Change vendor’s role from server to client (‘satellite’ vendor);

PLEASE NOTE: the remote control plugin is sold separately and it’s included only inside the MD Vendor System (full pack).

The plugin’s installation is very quick and simple: just drop the script inside the vendor along with the MD Vendor System ‘core’ plugin: the plugin will be automatically detected and installed. A message sent on chat will notify the owner of the successful installation.

At this point, to access the plugin’s specific settings the owner will have to go to the owner menu > plugin sub menu, where all installed plugins are listed.

md_vendor_system_14

Owner Menu – Plugin sub menu

 

By clicking on the corresponding ‘Remote Ctrl’ button, the plugin’s specific menu will load, presenting all the available options:

  • Client Mode: this buttons is a switch to enable/disable the client mode; by turning it on, the vendor will become a ‘client’, connected to another vendor or product server which will act as ‘server’, hosting the products in its content. More details about this feature in the corresponding chapter.
  • Online Setup: this button will load the vendor’s settings page at MD Labs Online Services website, allowing the owner to configure and control the vendor remotely. More details about this feature in the corresponding chapter.
  • Update: this button will search online for plugin’s update and deliver it to the owner, if found.
  • Back: this button navigate back to the plugin sub menu.
  • Main Menu: this button navigate back to the owner menu.

To uninstall the plugin simply remove it from the vendor’s content and the vendor will automatically update, removing the additional features.

 


 

Chapter #2: remote control

The first feature added by the remote control plugin is the ability to configure and control every vendor remotely, from the MD Labs Online Services website.

To reach the vendor’s settings webpage the owner can either click the “Online Setup” button inside the plugin’s menu or hit the cog icon directly on MD Labs Online Services website.

md_vendor_system_19

Vendor’s list @ MD Labs Online Services

 

Either way will take the owner to the vendor’s settings page, that will look like this:

md_vendor_system_20

Vendor’s settings page @ MD Labs Online Services

 

Every aspect of the vendor, from price to for sale status, from mode to split, discount and stock quantity can be controlled; the changes will be instantly applied to the corresponding vendor in-world. It is also possible to toggle on/off the client mode, connecting the vendor to another one which will act as server.

Lastly, if the Store Credits & Gift Card plugin is installed, the owner will also be able to toggle on/off the store credit, gift card and promo code as payment method.

 


 

Chapter #3: client mode

Client mode is a vendor’s particular working mode where the vendor doesn’t holds the products to sell in its content, but connects to another vendor or terminal (‘server’) to retrieve the products. The advantages of this setup are obvious: keeping only one copy of your products inside the ‘server’ vendor will reduce the confusion of multiple copies and simplify the maintenance of your products, while reducing also the time required to setup your vendors; also one ‘server’ vendor can be connected to multiple ‘clients’.

A vendor setup as client can be connected to two different type of server:

  • Vendor as Server: the client is connected to another vendor running MD Vendor System (‘core’) script and the remote control plugin.
  • Terminal as Server: the client is connected to terminal acting as product server and running the MD Redelivery Terminal & Product Server Script.

! IMPORTANT: version 2.0.0 or above of MD Redelivery Terminal & Product Server Script is required for using the features described below.

The main difference between these two server type is that while the vendor to use as server can be in any region, the terminal to use as server must be in the same region as the client. On the other hand, there are some pro in using a terminal as product server:

  • Being in the same region, the communication between server and client is faster and more reliable;
  • The same terminal running the MD Redelivery Terminal & Product Server Script can be used both as redelivery terminal and as product server, keeping all the products stored in one place and offering both redelivery and product delivery at the same time;

! IMPORTANT: any client – independently by the type of server which is connected to – will be able to manage only one normal item and/or one fatpack item from the server’s content; demo and multiple items will not be considered.

To setup a vendor in client mode, the owner will have to click on the corresponding ‘Client Mode’ button inside the remote control plugin’s menu: this will start the connection wizard. The first step of the setup is picking the type of server to connect to among vendor or terminal. As described above a terminal, to be used as product server, must be in the same region as the client vendor; conversely a vendor, to be used as server, can be in any region, as long as it’s set for sale and not already set as client.

Remote Control - Client connection

Client connection – Server type selection

When this first selection is made (and depending by the choice), the owner will be asked to pick among a list of vendors or terminals to use as server:

  • If trying to connect to a vendor, a complete list of vendors is displayed: the owner is also able to search the desired vendor by region or by name;
  • if trying to connect to a terminal, a list of all terminal rezzed in the same region as the client is displayed;

 

Vendor as Server - Vendor Selection

Vendor as Server – Vendor Selection

Once selected the vendor or the terminal to use as server, the client vendor will try to connect and, if no errors occurs, proceed to complete the connection.

At this point:

  • if the client is connected to a vendor, it will retrieve automatically the item and/or the fatpack;
  • if the client is connected to a terminal, the owner will be asked to pick an item among the ones present in the terminal’s content;

Once this last step is done, the connection is complete and a message will be displayed in the local chat; from that moment the vendor will use the item inside the server’s content as products to sell. As users will buy or gift a product from a ‘client’ vendor, the connected server will be contacted and will deliver the product purchased to the receiver.

Please note: this connection process can be performed also through the MD Labs Online Services, using the ‘client mode’ toggle in the vendor’s settings page.

The changes are reflected automatically on MD Labs Online Services website, where a column called ‘Role’ will display, for every vendor, if it is setup as client or server.

md_vendor_system_22

MD Labs Online Services – Vendor’s list

 

When a vendor is set as client, the remote control plugin’s menu will present two additional buttons:

  • Refresh: using this button will trigger a refresh of the product list from the server to the client; this is an useful feature especially when the content of the server has changed;
  • Ping Server: this button will trigger a connection test to check if the vendor server is up and reachable. An IM is sent to the owner, with the result of the test.
Remote Control Plugin - Menu (Client)

Remote Control Plugin – Menu (Client)

 

To better improve the user experience, an effective delivery method has been implemented: as the user purchases the product the transaction is stored, but the item is flagged as ‘delivered’ only once the server successfully receives the deliver request and the product is sent to the receiver. With this method, if some communication issue arises during the connection to the server or during the product’s delivery, the transaction is stored anyway – giving the user the chance to use the redelivery feature – but will stay flagged as ‘not delivered’; the owner is able to check the delivery status of every transaction on the detail page of the corresponding vendor.

md_vendor_system_21

MD Labs Online Services – MD Vendor System (Detail page)

 

To disable the client mode from a vendor simply click the ‘Client Mode’ button (or toggle the feature from the website): the vendor will be disconnected from the server and will start acting like a ‘normal’ vendor.

 

MD Vendor System User Manual

Quick summary:


 

Chapter #0: Initial notes & basic informations

MD Vendor System is a complete vending solution, built with a module (or plugin) architecture, easy to use and full of features. Its specific modular design lets the owner add or remove additional functions very quickly and easily, while making the whole system able to adapt to every situation and need.

MD Vendor System is composed by one main ‘core’ script and several different plugin scripts, each of them adding different features:

  • Demo & Multiple Items: this plugin adds the ability to manage one or more demo items, one fatpack item and multiple products, which customers will be able to buy or gift.
  • Remote Control: this plugin adds the ability to set a vendor as ‘client’ (‘satellite vendor’) connected to another vendor (server) or to a product server.
  • Store Credit & Gift Card: this plugin adds the store credit, gift card and promo codes option as payment method.
  • Poses: this plugin turns any compatible pose displayer into a pose vendor with advanced features.

The main (‘core’) script alone is able to manage and sell one product item, with its specific price.

Also, the main script alone provides all the most common options such as:

  • buy and gift features;
  • profit split;
  • stock quantity limit;
  • group mode;
  • discounts;
  • direct pay;
  • and much more

PLEASE NOTE: the main script is always required for the vendor to work.

The basic version of MD Vendor System sold consist of the ‘core’ script and the demo & multiple items plugin, while the other plugins are sold separately or present inside the full pack version sold.

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

  • MD Vendor System (‘core’) version 4.0.2
  • Demo & Multiple Items Plugin version 2.0.0

The other plugins have dedicated user manual pages:

  • The Remote Control plugin user manual is available here;
  • The Store Credit & Gift Card plugin user manual is available here;
  • The Poses plugin user manual is available here;

 


 

Chapter #1: what’s inside the pack – MD Vendor System components

Depending on which version of MD Vendor System is purchased (standard version vs Full Pack version), the system will be composed by several parts.

MD Vendor System presents the following components:

  • MD Vendor System 4.x.x: this is the main ‘core’ vendor system script;
  • MD Vendor System Plugin – Demo & Multiple Items 2.x.x: this is the plugin enabling demo, fatpack and multiple items selling;
  • [READ ME FIRST] MD Vendor System – Quick Start: a notecard, containing some basic information about the product, as well as F.A.Q. and links to user manuals;
  • [ADD ON] MD Vendor System Online Services HUD 0.8: this HUD allows the owner to register an account to MD Labs Online Services, a companion website where it is possible to organize, manage and interact with all the rezzed vendors;
  • [Auto Updater] MD Vendor System 4.x.x: this tool is an auto updater for previous installations of MD Vendor System. The auto updater simply runs through all the rezzed vendors containing an older version of MD Vendor System and automatically updates them, replacing the old script with the new ones;

MD Vendor System (Full Pack) presents the following components:

  • MD Vendor System 4.x.x: this is the main ‘core’ vendor system script;
  • MD Vendor System Plugin – Demo & Multiple Items 2.x.x: this is the plugin enabling demo, fatpack and multiple items selling;
  • MD Vendor System Plugin – Remote Control 2.x.x: this plugin allows the vendors to connect as clients (satellites) to another vendor or product server;
  • MD Vendor System Plugin – Store Credit & Gift Card 2.x.x: this plugins allows store credits and gift card as payment option. It also includes the gift card script and a full perm template HUD for creating custom gift cards;
  • MD Vendor System Plugin – Poses 2.x.x: this plugin turns any compatible pose displayer into a pose vendor, able to preview the poses and let customers buy them directly. It comes also with a full perm pose stand;
  • MD Redelivery Terminal & Product Server Script 3.x.x: this content is not a plugin for MD Vendor System, but a separate device working as redelivery terminal and also as product server for client vendors. It includes some advanced features such as mass redelivery.
  • [READ ME FIRST] MD Vendor System – Quick Start: a notecard, containing some basic information about the product, as well as F.A.Q. and links to user manuals;
  • [ADD ON] MD Vendor System Online Services HUD 0.8: this HUD allows the owner to register an account to MD Labs Online Services, a companion website where it is possible to organize, manage and interact with all the rezzed vendors;
  • [Auto Updater] MD Vendor System 4.x.x: this tool is an auto updater for previous installations of MD Vendor System. The auto updater simply runs through all the rezzed vendors containing an older version of MD Vendor System and automatically updates them, replacing the old script with the new ones;

 


 

Chapter #2: first setup

Once received the MD Vendor System – boxed or just as folder – inside there will be two main scripts:

  • MD Vendor System
  • MD Vendor System Plugin – Demo & Multiple Items

The first one is the ‘core’ script, the vendor itself while the second one is a plugin for handling demo and multiple items; while the first is necessary for the vendor to work correctly, the plugin can be added and removed anytime, without compromising the vendor’s functionality.

As first step, the MD Vendor System script must be dropped inside the object/prim used as vendor; if this is the first setup for that specific vendor (and not a simple vendor reset), it’s highly recommended to rename the vendor with it’s final name in order to avoid having multiple vendors with the same name, which could lead to malfunctions. Also, it is important to remember to never setup a new vendor starting from a copy of an existing one created via drag&copy.

The second step is a simple click on the vendor, that will prompt the debit permission request, required by the script in order to handle the split system and the refund one. Clicking on “next” and granting the permission will complete this step.

Once granted the debit permission, the vendor will automatically connect to MD Labs’s server and try to restore the existing settings; this feature – which won’t be useful during a first setup – becomes very handy in case of a vendor reset, when the settings are saved and the whole vendor’s status will be automatically restored.

During a first setup, at this point the vendor is ready to be configured and not yet ready to be used. If a normal user – different from the owner – clicks on the vendor now, a message will be sent 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’s configuration menus.

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

 


 

Chapter #3: owner menu

When the owner enters the owner menu a dialog will appear: from this window the most important options are accessible and ready to be customized.

MD Vendor System – Owner Menu

MD Vendor System – Owner Menu

This owner menu – accessible by the vendor system owner only – is divided in many sections, some of them leading into other sub menus:

  • Price: this first feature is used to set the item price in L$; clicking on the “Price” button will open a textbox where the owner will have 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;
    • The item’s price must be set;

If 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 a primary set of options – the most useful ones – that aim to make this product as flexible as possible. The feature present in this menu are:
    • direct pay;
    • profit split;
    • discount;
    • group mode;
    • limited stock quantity;
    • notifications;
    • hover text;

The detail of each feature will be explained in the options chapter.

  • Plugins: this button leads to the plugins sub menu, where all the installed plugins are listed; for each plugin there is a dedicated menu where the owner can configure the additional features. The details for configuring and using each plugin can be found in the corresponding chapters.
  • Online Services: opens the MD Labs Online Services website, where the owner can interact with all the rezzed vendors. 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 vendor.
  • Archive: this button triggers a specific feature for vendors which are not used anymore; by archiving, the vendor will be removed from in-world keeping all the it’s statistics and transactions accessible via the MD Labs Online Services web page. This will allow customers to request redeliveries, while helping store owner to keep their data sorted and organized deleting unused vendors.

 


 

Chapter #4: basic usage – setup a simple vendor

This chapter is meant to explain the basic steps to setup a simple vendor in its most basic configuration: a single product vendor allowing both buy and gift options for users.

The basic usage of a vendor using MD Vendor System is very simple and easy to achieve: once rezzed and granted the debit permission, owner will have to drop inside the vendor’s content one “normal” item and/or one fatpack item 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;
  • 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 at least one valid item is dropped inside the vendor’s content, a second step is required: owner in fact will have to assign the item a price. By clicking the “Price” button the owner will be asked to choose the type of item to assign the price to, among “normal” item or a fatpack. Once this choice is made, submitting a value will automatically associate the price to the chosen item.

Price – Item’s price selection

Price – Item’s price selection

 

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

By default, users can click the vendor and get the users menu to buy or gift. Based on the action chosen among the listed ones, different scenario will take place:

  • in case of a normal purchase (“Buy” option), 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 user 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 in fact be asked to 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.

 

User Menu

User Menu

 

In both scenarios, if the timeout is reached the operation will be canceled and the user will have to start the process again.

 


 

Chapter #5: fatpack

As mentioned in the initial notes of this user manual, the basic (“core”) version of MD Vendor System can manage up to:

  • 1 normal item, with a specific price;
  • 1 fatpack item, with a specific price;

This means that the default vendor is able to handle one of these following setup:

  • 1 item, 0 fatpack;
  • 0 item, 1 fatpack;
  • 1 item, 1 fatpack;

While there aren’t any constraints for the “normal” item, the fatpack item will have to contain the keyword ‘FATPACK‘ in its name in order to be automatically identified by the MD Vendor System and used properly.

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

For reference, here’s a couple of examples for correct fatpack item:

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

Once the fatpack item is detected and the corresponding price is set correctly, new options appear in the user menu, like shown below:

User Menu with fatpack options

User Menu with fatpack options

 

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.

HINT: To disable the fatpack feature owner will have to remove the corresponding item from the vendor’s content and the MD Vendor System will automatically do the rest.

 


 

Chapter #6: multiple vendor setup

MD Vendor System introduces a very useful feature that aims to save time while setting up the vendors. This feature, called ‘multiple setup’, allows the owner to decide whether to apply a specific setting to the current vendor or to all vendors belonging to the owner and present within the same region at once. 

It’s possible to take advantage of this great feature with almost all the settings available, included all the options described in the next chapter. Once a feature is chosen, the owner will be prompted to a dialog asking if apply the setting to the single vendor or to all vendors; once the selection is made and the specific setting configured, the value will be applied to the single vendor or all vendors.

multiple setup menu

multiple setup menu


 

Chapter #7: options

In the options sub menu is possible to find a lot of additional features aimed to enrich the experience with MD Vendor System by 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 personal vendors.

Owner Menu - Options

Owner Menu – Options

 

  • 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 100%. 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 and/or fatpack’s cost. 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: 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, in fact, 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. 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.
  • 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.
  • MP Link: by enabling this option, the owner will be asked to provide the SL Marketplace’s link (URL) to the product inside the vendor. Once submitted the link, the users will see an additional “View on MP” button on the users menu; clicking on it, they will be taken to the corresponding page on the SL Marketplace.
  • 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 in fact 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.

 


 

Chapter #8: vendor’s pay buttons

Once the vendor is set for sale, it will set its pay button accordingly with the item’s price provided; the users will be able to right click on the vendor and select ‘Pay’ to make the default SL payment window appear, like shown below:

default SL payment window

default SL payment window

 

! IMPORTANT: By paying the vendor directly, the script will consider the purchase as a “Buy” and the item will be delivered directly to the avatar whom paid the vendor.

HINT: when both the discount and the group mode features are active, the vendor’s default payment window will still present the full price but, if the avatar paying has the right group tag active, the discounted price is calculated according to the discount % provided and the difference is refunded to the avatar whom paid the vendor.

If – for example – the item’s price is set to 100L$ and there is a 25% discount for avatars wearing a specific group’s tag, right clicking on the vendor and selecting ‘Pay’ the 100L$ pay button is presented but, once paid the 100L$ amount, the avatar will be refunded of 25L (25% of 100L$) if having the right group tag active.

! IMPORTANT: this behavior is achieved only having both the discount and group options enabled and only if the users right click on the vendor and select “Pay”; when purchasing through the vendor’s menu infact the discounted price (if due) is calculated and the SL default payment window will already contain either the full price or the discounted one.

There is one scenario although, where the MD Vendor System will disable this option to avoid wrong payments and mistakes: when both item and fatpack are present inside the vendor, the right amount to pay vary depending on the item type (normal item or fatpack). For this reason – only in this specific case – , the payment method via right click is disabled, like shown in the image below:

SL payment window disabled

SL payment window disabled

 

In this situation, the users will have to use the vendor’s menu to purchase the products.

 


 

Chapter #9: 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 Vendor System is designed to interface with MD Labs Online Services, giving the owner incredible possibilities, such as:

  • Get a quick overview of all the vendors, with locations where they are rezzed and total profit;
  • Analyze selling statistics grouped by vendor, region, date (day/month/year), customer, product or by event;
  • See the transaction list for every vendor, including buyer, item bought, item cost, net profit, purchase type, purchase date-time;
  • Delete one or more specific transaction from a vendor;
  • Add/remove any vendor assignment to an event or fair;
  • View selling statistics for both In-World sales and SL Marketplace sales (SL Marketplace integration is required);
  • Configure any vendor remotely, also client ‘satellite’ vendors (remote control plugin is required);
  • Delete completely one or more vendor, including all its transactions (remote control plugin is required);
  • Redeliver contents from all your vendors to customers (redelivery terminal required);
  • Keep track of your store credits and gift cards, adding credits to specific users (store credit & gift card plugin required);

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 Vendor System pack.

md_vendor_system_08

MD Vendor System – 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 Vendor System for the Online Services. (Please note: this step is required only if MD Vendor System is purchased from in-world store)

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

The main page is divided in three different tabs: ‘My Vendors’ , ‘Redelivery Terminal’ , ‘Store Credit & Gift Cards’; inside the My Vendors tab a full list of all the vendors rezzed in-world is displayed, reporting also the region where the vendor is rezzed, the total number of item sold 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. If SL Marketplace data is integrated, all the MP Listing will be reported here as well, assigned to a special region called “Marketplace”.

 

md_vendor_system_09

MD Labs Online Services – MD Vendor System

 

In the ‘My Vendors’ tab a pie chart graph is also displayed, reporting for each vendor the total profit made:

md_vendor_system_10

MD Labs Online Services – MD Vendor System (Graph)

 

By clicking on a specific vendor in the ‘My Vendors’ tab it’s possible to check the full transactions list of the vendor, with detailed info about the payer, the receiver, the amount paid and much more.

md_vendor_system_11

MD Labs Online Services – MD Vendor System (Detail page)

 

The second tab, called ‘Redelivery Terminal’, presents a list of all redelivery terminals rezzed: for each of them it’s possible to check the redelivery list and also interact directly with the corresponding terminal in-world, triggering a normal or mass redelivery, changing the role from server to client and deleting the terminal. More information about the MD Redelivery Terminal can be found here.

md_vendor_system_12

MD Labs Online Services – MD Vendor System (Redelivery Terminal tab)

Please note: MD Redelivery Terminal is sold separately.

 


 

Chapter #10: 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.

There are several benefits in integrating the SL Marketplace inside MD Labs Online Services website, the most important are:

  • Having both SL Marketplace sales and in-world sales grouped in only one place, with statistics and tools to analyze them;
  • Through MD Redelivery Terminal, being able to offer redelivery for both product purchased from in-world and on SL Marketplace;

 


 

Chapter #11: 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 all the times.

User Menu

User Menu

 

  • Buy: this option allow the user to purchase the item inside the vendor. 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 submit the name or the key (UUID) of the avatar receiving the gift. If the submitted value is correct  the process will proceed and 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.
  • Get demo: clicking on this button the user will receive for free a folder containing all the demo items inside the vendor.
    • Please note: in order to use this feature, Demo & Multiple Items plugin must be installed on the vendor.
  • View on MP: clicking on this button, the user will be taken to the SL Marketplace’s page of the corresponding product.
  • View Balance: with this option the user will receive an IM containing the personal credit’s balance, divided in store credits and gift cards.
    • Please note: in order to use this feature, Store Credit & Gift Card plugin must be installed on the vendor.

 


 

Chapter #12: plugin – demo & multiple item

Demo & Multiple Item is the first plugin for MD Vendor System and it’s always included in any version provided. This plugin allows the owner to:

  • Handle one or more demo items, that will be given for free to users clicking on the “Get Demo” button in the vendor;
  • Handle multiple “normal” items, that users will be able to buy or gift;

Please note: by LL limitation, an object can contain up to 255 items inside; this means MD Vendor System can handle up to (255-the number of scripts) items in a single vendor.

The plugin’s installation is very quick and simple: just drop the script inside the vendor along with the MD Vendor System ‘core’ plugin: the plugin will be automatically detected and installed. A message sent on chat will notify the owner of the successful installation.

At this point, to access the plugin’s specific settings the owner will have to go to the owner menu > plugin sub menu, where all installed plugins are listed.

md_vendor_system_14

Owner Menu – Plugin sub menu

 

By clicking on the corresponding ‘Demo & Items’ button, the plugin’s specific menu will load, presenting all the available options:

md_vendor_system_15

Demo & Multiple Item Plugin – Menu

  • Store Demo: when this option is enabled, MD Vendor System will store on MD Labs Online Services website also transactions for demo items.
  • Help: this button loads the MD Vendor System user manual.
  • Back: this button navigate back to the plugin sub menu.
  • Main Menu: this button navigate back to the owner menu.

Similarly to the fatpack’s handling, also for demo items there is a naming convention to respect: a demo item will have to contain the keyword ‘DEMO‘ in its name in order to be automatically identified by the MD Vendor System and used properly.

As reference, 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;

Once one or more valid demo items are dropped inside the vendor, an additional button named ‘Get Demo’ will appear inside the user menu; by clicking it, the user will receive a folder containing all the demo items.

User Menu - Demo

User Menu – Demo

This plugin also allow to sell multiple “normal” products within the same vendor: once the user clicks the vendor and selects among buy or gift, a list of all the products is displayed for the user to choose, in order to complete the process.

md_vendor_system_17

User Menu – Product selection

 

To uninstall the plugin simply remove it from the vendor’s content and the vendor will automatically update, removing the additional features.

 


 

Chapter #13: plugin – remote control

Remote Control plugin allows to interact remotely with the vendors and enabling the client mode. This plugin has a dedicated user manual, which can be found here.

 


 

Chapter #14: plugin – store credit & gift card

Store Credit & Gift Card plugin adds to vendors the store credit and credit card payment options. This plugin has a dedicated user manual, which can be found here.

MD Gacha Machine for Events – User Manual

Quick summary:

 


 

Chapter #1: what’s inside the pack

Once you receive your purchased copy of MD Gacha Machine Script for Events and unpack it, you will find:

  • MD Gacha Machine Script, with copy-only permissions   (for hoster)
  • MD Gacha Machine Online Services HUD   (for hoster)
  • MD Gacha Machine Script [for participants], with transf & copy permissions    (for participants)

 

MD Gacha Machine Script For Event – Pack’s content

 

The first script, called MD Gacha Machine Script, is meant to be used by event’s hosters whom wants to participate to their own events or just have a standalone gacha machine. While the MD Gacha Machine Script is the script itself for gachas, the Online Services HUD is necessary to register and login the MD Labs Online Services website which will be used to create and manage the hosted events.

A complete user manual which covers details about standalone gacha machine’s script and basic usage of Online Services HUD can be found here

 


 

Chapter #2: Participant’s script

The MD Gacha Machine Script for participants comes will transf & copy permissions because it’s designed to be the one sent and used by event’s participants.

The MD Gacha Machine Online Services HUD is not included but can be retrieved by any participants through the ‘Get HUD’ button present inside the gacha’s menu. The usage of the HUD is optional for event’s participants: having an account at MD Labs Online Services website will allow them to view all the stats of their gachas and events they are participating, as well as manage some aspects of their machines.

Event’s hoster should provide (by sending or selling) the MD Gacha Machine Script [for participants] to all event’s participants, but before doing so a permission’s change is requested: in order to work, infact, the MD Gacha Machine Script’s next owner permission MUST be changed to copy-only.

If an event’s participant receives the script with a different permission set other than copy-only, the script will send out an alert message and will not work.

MD Gacha Machine Script for Events - 04

Next Owner permission’s change before sending the script to participants

 

Once the participants receive/purchase the MD Gacha Machine Script (configured with the right permissions), they can drop the script into the machines and perform the setup. At this point, an hosted event must be created.

 


 

Chapter #3: Creating an hosted event

In order for the partecipants to be able to use their copy of MD Gacha Machine Script, a valid event must be created by the hoster through the Online Services website. Hoster should log in the Online Services website and select “MD Gacha Machine” from the drop down list on called ‘Products’. At this point the page will load, composed by two main tabs:

  • ‘My Gachas’ tab, containing all the data regarding gacha machines owned by the hoster.
  • ‘My Events’ tab, containing all the event created and hosted.
MD Gacha Machine Script for Events - 05

MD Gacha Machine page @ Online Services website

 

Clicking on the ‘My Events’ tab will present the list of all hosted events, with name, region, start/end date, profit and status; also in this page it’s possible to find a link to create a new hosted event.

MD Gacha Machine Script for Events - 06

‘My Event’s page

 

In order to create a valid hosted event, there are some rules and constraints that need to be satisfied:

  • A specific event can occur only at one region
  • A region can run only one event during a specific period
  • An event must have a valid start and end date
  • An event duration must be between 1 to 60 days

This means only one event per time can be created and run in a specific region, during a specific period. Clicking on the ‘Create Hosted Event’ link will start the wizard, where some data will have to be provided:

  1. Event’s name: the name that will be used for the hosted event;
  2. Event’s region: the region where the event will occur;
  3. Event start date/time (SLT): the date & time when the event’s participants will be able to setup their machines, in Second Life Time (SLT). All the transactions made from this moment and before the event effective start date/time will be considered as test transaction and not counted on the event’s total sales. Here some additional constraints are applied:
    1. It’s not possible to set a start date in the past from the moment the event is being created;
    2. It’s not possible to set a start date more than 30 days in advance from the moment the event is being created;
  4. Event effective start date/time (SLT): the date & time when the event will effectively start, in Second Life Time (SLT). All the transactions made from this moment and before the event end date/time will be considered as valid transaction and counted on the event’s total sales. Here some additional constraints are applied:
    1. It’s not possible to set a start date in the past from the event start date;
  5. Event end date/time (SLT): the date & time when the event will end, in Second Life Time (SLT). Here some additional constraints are applied:
    1. It’s not possible to set an end date more than 60 days after the start date;

 

Hosted event creation wizard

 

When all data are provided correctly, the new event will be created and all the gacha machines present in the specified region and running the MD Gacha Machine Script for participants will be automatically associated to it.

Please note: the participant’s gacha machine will not work if:

  • No hosted event exists on the region where the partecipant’s machines are rezzed;
  • The hosted event’s start date/time is not reached yet;
  • The hosted event’s end date/time is surpassed;

 


 

Chapter #4: Event’s statistics

Once the hosted event is successfully created, it will be listed into the ‘My Events’ tab along with all the past events occurred. For each event it’s possible to see some basic information:

  • Event name: the name associated to the event;
  • Region: the region where the event is run;
  • Start date/time (SLT): the time when the event start, in SLT format;
  • End date/time (SLT): the time when the event end, in SLT format;
  • Total sales (L$): total profit made during the event by all partecipants through their gachas;
  • Status: the event’s status (open/close);

 

Hosted events list

 

Clicking on the event’s name will load the corresponding sales summary page; this page contains all the sales data regarding the event grouped by partecipants or gacha machines and also a graph to display the values in a more effective way.

Hosted Event's Sales Summary - Graph

Hosted Event’s Sales Summary – Graph

 

Right below the graph, the sales data are presented into a table, reporting the store/owner, the profit made in L$ and the % of total sales represented by that profit.

Hosted Event's Sales Summary - Table

Hosted Event’s Sales Summary – Table

 

Using this tool, the event’s hoster can check anytime during the event or once the event has ended which stores or gacha are selling the most, being able to get a detailed view of the event.

Please note: while the graph is always shown for the hoster to get an idea of the event’s trend, by default the detailed partecipants’s profit and % of total sales are hidden. This is made for a privacy reason, since not all partecipants may be willing to share their sales data; the partecipants will have to explicitly decide to share their data with the hoster of the event they are partecipating. When data is hidden and not shared, the values are replaced with a dash ( ).

In order to share their data, partecipants will have to log in the MD Labs Online Services website and go to MD Gacha Machine page; selecting the ‘view by event‘ they will be able to see a complete list of all events – hosted or not – they are partecipating. By clicking the checkbox they will enable or disable the sales’s data sharing with the hoster for the corresponding event.

Partecipants’s sales data sharing with hoster

 

 


 

Chapter #5: End an hosted event

Once an event is running, the hoster can decide to close it before time. Inside the tab called ‘my events’, a button is displayed at the end of each running (open) event’s row: by clicking on it the hoster will be asked to confirm the event end.

Important: as an event is closed all the gacha machines (belonging to participants and/or to the hoster) associated to the event will stop working immediately.

End event

End event

 

Even after an event is closed all the statistics and sellings data will be preserved and the hoster will always be able to access them.