EV-OldVersion

EasyVend is an expansion pack for CasperVend, which provides rapid setup of products and vendors in-world with no website access required.

It's designed as a drop-in replacement for E2V vendor scripts, however, E2V is not required - EasyVend can be used out of the box.

Features

• Drop-in replacement for E2V vendor scripts
• Drop-in replacement for E2V store controller to support profit splits, sales, price groups
• Drop-in replacement for E2V inventory server for remote delivery
• Obeys E2V naming rules for item matching
• Supports DropBox delivery, local vendor delivery and folder delivery
• Automatically creates products in the CasperVend system

Caveats

• NOT SUPPORTED: E2V's "partners" feature
• The EasyVend does not display textures - if you want automatic texture management use the full CasperVend
• You can't manage what displays on the vendor from the web
• You can't manage profit shares or store credit awards from the web
• If you use local vendor or folder deliveries, customers will be unable to claim redeliveries using the automatically created products. However, you can edit the product on the web interface and set an item for redelivery.

E2V Items Not Used by CasperVend EasyVend

• Delivery Relay
• Payments Object
• Transaction Relay

E2V Migration: Drop-N-Go

Where Are the Scripts?

• Redeliver your paid CasperVend pack
• If you have the FatPack, then unpack your FatPack > Unpack "Premium Vendors" > Look for the EasyVend box and unpack that
• If you have just the Premium Vendors box, then unpack that to get to the EasyVend box

Using the Scripts

1. If you use the E2V Inventory Server, drop the "CasperTech DropBox" script into each E2V Inventory Storage box (not the root prim)
2. Drop the "CasperVend2 EasyVend Store Controller" script into your E2V Store Controller
3. Remove the E2V scripts from each vendor you wish to convert, and replace them with the "CasperVend2 EasyVend".

That's it!

E2V Migration: Fresh Setup

This is intended ONLY for merchants migrating TO CasperVend who are used to E2V's way of doing things, and have a lot of vendors to get changed over to the CasperVend format. These instructions allow these merchants to continue adding products while they take the time to get the hang of how the normal CasperVend system works.

Create Your Settings Notecard

The Store Controller's settings note card contains the options for the vendors you have on THAT sim/region.

The note card is roughly divided up into 4 sections:

• Defaults
• Splits
• Sales
• Price Groups

For example:

# Defaults
N-Reward=2%
G-Reward=5%

# Splits
Split=

# Sales
Sale=
ExcludedGroups=
SpendCreditDuringSale=false
EarnCreditDuringSale=false

# Price Groups
PriceGroup=one,50
PriceGroup=two,100

Default Settings:

---

N-Reward
Specifies the default non-group buyer's reward value to be used for each vendor, if the value is not specified either on the vendor, or in the vendor's price group. This value can be either a percentage (if you include the % sign) or an absolute value. This value can be either a percentage (if you include the % sign) or an absolute value. Leave this blank, or use a 0, to prevent any default value from being used.

G-Reward
Specifies the default customer group's buyer reward value to be used for each vendor when the customer has the same group tag active that the vendor object is set to, if the value is not specified either on the vendor, or in the vendor's price group. This value can be either a percentage (if you include the % sign) or an absolute value.

Price Groups

---

Price groups allow you to define a single set of vendor options, in one place, then use those options on as many different vendors as you want. Changes to the price group only need to made to the group itself (in the settings notecard) and all vendors using THAT group will be updated automatically.

You can also put specific groups on sale simply by changing their prices, while the rest of your products remain unchanged.

Each group is defined on a new line that begins with:

  PriceGroup= 

and consists of at least two items: the name of the group, and the price of the group. You can also specify buyer's reward values on the group, by adding them after the group's price.

Omitting a Value vs Explicit Zeros

---

When you don't supply a value for buyer's rewards, you are indicating that you want to use the default values (if they exist elsewhere in the settings notecard).

This means that leaving them blank is NOT the same thing as using explict 0's. For example:

N-Reward=2%
G-Reward=10%

PriceGroup=socks,100
PriceGroup=shoes,100,,8%
PriceGroup=pants,100,0
PriceGroup=shirts,100,0,0

The above settings will result in the following values:

socks ... n-reward: L$2, g-reward: L$10
shoes ... n-reward: L$2, g-reward: L$8
pants ... n-reward: L$0, g-reward: L$10
shirts ... n-reward: L$0, g-reward: L$0

Sales

---

You can place the entire store on sale by putting either a percentage or a flat amount into the Sale field. Once the settings are saved and loaded, the controller will restart all the vendors, and they will take on the sale pricing.

You can exclude certain pricing group (see below) from the store-wide sale by adding their names, separated by commas, to the ExcludedGroups line.

The SpendCreditDuringSale option controls whether customers will be able to to buy on-sale items using their store credit or not. Put "true" or "false." Note that vendors in groups that are excluded from the sale are not affected by this setting.

The EarnCreditDuringSale options control how buyer's rewards behave during the sale. Use "false" to prevent on-sale vendors from issuing buyer's rewards.

Splits

---

Parts of a Split

---

There are 3 parts to a split. They are Split Name, Split Target, and Split Amount.

Split Name
You need a short, easy to remember name for what you're doing with this split. Are you paying rent? Are you paying your CSR? Paying your manager, or co-designer? Making a donation? Whatever it is you're doing with the split, you'll need to call this split something.

Split Target
Next you'll need the UUID of the avatar you want to pay. You can get an avatar's UUID from their profile.

Split Amount
Lastly, you'll need the amount you want to give this avatar on each sale. This is typically written as a percentage, like 25% or whatever amount you choose.

Adding Split to Controller

---

dit the settings note card inside the Store Controller, and find the section for Splits. This is where you'll add your split information.

Here's an example of a split definition. In this example we'll use "mgr" as the Split Name, and 50% as the Split Amount.

 Split=mgr,ad7b01b9-9b71-4beb-ba05-0c353ade5952,50%

As you can see, the split is written as "Split=" followed by Split Name, Split Target, Split Amount with no spaces between the values.

Pick Which Vendors Use the Split

---

Think of it like this: adding the split info to the Controller doesn't pick which vendors should use that split, it only makes that split available to use.

You can apply a split to any vendor by adding the Split Name to the vendor's description line as part of the vendor's pricing options.

Normally vendor's description line has 3 components to it, which are price, n-reward, and g-reward, written like this:

  [150,2%,5%]

You can add a fourth component, which is the Split Name, like this:

  [150,2%,5%,mgr]

A vendor with the above pricing options will pay 50% of its sale price of L$150 to the avatar specified in the split called "mgr" inside the Controller.

In this way, you can easily change the Split Target or Split Amount on many vendors at once, simply by changing the Store Controller, instead of editing every vendor using the split. Important!

You must have FOUR parts to the vendor pricing to use splits! They are price, n-reward, g-reward, and split name.

But what if you're not using Buyer's Rewards? The Split Name still needs to be the 4th item! Here's how to do this if you are not using Buyer's Rewards at all (or if you just want to use the default values from the Store Contoller):

In our example above, the Buyer's Rewards were included in the options:

  [150,2%,5%,mgr]

You can "skip" writing the Buyer's Rewards just by removing those numbers:

  [150,2%,5%,mgr]

But without spaces!

  [150,,,mgr]

Or, you can disable Buyer's Rewards by using 0's:

  [150,0,0,mgr]

Create Your Store Controller Object

This object will control the settings for your vendors on the region where THAT controller is located.

1. Rez a new prim
2. Drop in the "3) CasperVend2 EasyVend Store Controller" script
3. Add in your "settings" notecard (see instructions above for how to create this)

That's it!

Rez a DropBox

Rez the CasperVend DropBox out of the main Premium Vendors box.

Your packaged products - not folders - will go in here to be used for remote delivery.

Create Your Vendors

1. Rez your vendor object
2. The name of the vendor MUST MATCH the name of the inventory item, Except:
   • There may be additional text at the end
   • The word "vendor" at the end will be ignored
   • Inventory items may have multiple words
3. Edit the vendor's description field to indicate pricing and - if used - loyalty and/or splits

A vendor object may contain the word "vendor" at the very end of the name, separated by a space. This text will be ignored when matching the vendor to a product box. Thus "My Fancy Shoes Vendor" will actually deliver a product named "My Fancy Shoes" (your transactions will list this name, as well).

For example, all of your product boxes might carry the text "(Wear to unpack)" on the end of them. But this text isn't helpful on a vendor or transaction listing. For example, using the suffixes feature, you can name your vendor "My Fancy Pants" and name your product box "My Fancy Pants (Wear to unpack)". Note also that if you use folder delivery mode in this example, the customer's folder will be named the same as the vendor - without the unsightly "(Wear to unpack)" which doesn't make much sense in a folder name.

About The Vendor Description Field

The description field may contain:

1. Price (or name of price group, as defined in controller's settings notecard)
2. Pricing + loyalty rewards
3. Pricing + loyalty rewards + splits

Remember, any rewards that are not being used need to be explicitly defined instead of being left blank.