CasperVend 2/Customisation

Offline / Back Soon Textures

Inside each vendor are two textures: "BACK_SOON" and "VENDOR_OFFLINE"

Simply create two replacement textures, name the appropriate one with the appropriate name, Delete the old ones out of the vendor, and replace with the new. It's that easy!

Touch Vendor

The touch vendor allows the customer to interact with it by way of a touch menu instead of buttons on one of the faces. This means that the vendor can be in a standard" box shape, with customers being able to interact with all sides of the vendor instead of only one or two sides of it.

The touch vendor is only designed to vend ONE product - so don't use a profile that has multiple items in it, because only one of them will be displayed. It has no way to scroll between items.

Customising the Headless Vendor

The "Headless" vendor allows you to take the contents and drop them into one of your own objects - you can essentially turn one of your products into a vendor this way.

If you ONLY want your objects to accept the "PAY" function without having menu or button options, simply drop the script in the object without a MAPPING notecard.

It is NOT recommended to use the "headless" vendor for furniture that gets sat on - the avatar's action of sitting will force the vendor to reset. Instead, consider a holovendor system for furniture that people will sit on (which will also allow you save on prims by packing up separate displays in the holovendor), OR set up single-item static vendors or a "touch" vendor next to the furniture.

Remember that "Headless" vendors can ONLY vend ONE product. Link them to products the same as you would as if you were using the 1-prim STATIC vendor.

Using the "Headless" to Cutomise a Box

1. Drop the Mapping Helper script into the box.
2. Set up your customized mapping (see the sections below for details) for any buttons you're using. You WILL need an "admin" button even if you don't need any other buttons, but for anything with a face that you're expecting people pay (and not other faces) you should also map a "MAIN PANEL".
3. Remove the mapping script when done.
4. Create the MAPPING notecard, drop in your customised "VENDOR_OFFLINE" and "BACK_SOON" textures, and a copy of the vending script.
5. Set up your box to vend a product, the same as you would for a standard "static" vendor.

Using the "Headless" to Vend Objects (With Admin Button)

1. Drop the Mapping Helper script into the object
2. Set up your customized mapping for the Admin button. (Since you are using this on an actual object in this case, other buttons will be fairly useless.)
3. 3) Remove the mapping script when done
4. 4) Create the MAPPING notecard, drop in the "offline" and "back soon" textures if applicable, and a copy of the latest vending script.
5. 5) Set up your object to vend the product - use the Admin button area to get a configuration URL.

Example Vendor - "EasyMod"

This is an example vendor set up just so that you can see the maximum possible buttons. Each prim in the vendor is labeled with the appropriate button name the script is looking for.

Included inside the EASYMOD vendor example are all the default button textures, as individual textures.

The "EasyMod" is NOT intended to actually be used AS a vendor - only as an example of the complete setup.

Using the "CasperVend Mapping Helper" Script

Drop this script into a vendor prim or linked vendor object.

Click and it will give you a popup menu with the options:

Reset

This wipes any configuration you've done up to that point

Textures

There are 13 possible texture displays on a vendor, and this option walks you through selecting which display is which. If you're having trouble visualising the usual order of these buttons, rez out the "EasyMod" from the Customisation box and look at how the prims are named. (use Edit > Linked Parts if necessary).

You do not need to be in "edit" mode to do this step - being in edit mode means you have to right-click, THEN "touch" as opposed to just clicking the prim.

The script wants you to tell it the faces of the display panels. It is looking for this information in the following order:

1. Left panel six
2. Left panel five
3. Left panel four
4. Left panel three
5. Left panel two
6. Left panel one
7. Main texture panel
8. Right panel 1
9. Right panel 2
10. Right panel 3
11. Right panel 4
12. Right panel 5
13. Right panel 6

If you want to use all sides of a prim for one or more of those faces, then click "ALL SIDES" on the popup menu, BEFORE clicking the prim. It will give you another popup once it's processed the "ALL SIDES" selection and is ready for you to click the prim.

You WILL be having popup dialogues for each step. The one for the current step will always be on top - ignore the ones that are left up from earlier. It is NOT required to click "ok" or "ignoree" on the popups menus before proceeding to the next step but you can if you want to. (LSL doesn't allow self-closing of popup menus.)

Just click "skip" for the display panels you're not using. If you're using a simple one-prim, one-item vendor, then just use "skip" on everything BUT the "Main Texture Panel".

Buttons

This maps the clickable button areas from TOP LEFT to BOTTOM RIGHT, in the following order:

1. Page Left
2. Scroll Left
3. Admin Button
4. Search Button
5. Help Button
6. Demo Button
7. Gift Button
8. Scroll Right
9. Page Right
10. Rez

As with the texture panels above, just click "skip" on the options you're not using. (For example, not everyone uses the demo button.)

Yes, this can be used to customize buttons for a v2.x HoloVendor!

Finish

This does two things: (1) Sends the configuration to a code pasting site, and (2) gives you the link to the page it went to so you can copy it. Remember this link is valid for just one hour so if you get distracted and it expires, you'll have to do the configuration all over again.

Copy the configuration file from pastebin into a notecard and drop it in your vendor.

NOTE:

MAPPING notecards should have 37 lines for a normal vendor, and 38 lines for a holovendor. If you generated one that is longer or shorter than this, tell the mapping helper script to "reset" and go through the process again.

Delete the mapping helper script from the vendor once everything else is complete

Copy the MAPPING list from the pastebin site into a notecard and drop it in the vendor.

All done!