CasperVend 2/Event Vendor Script

Where do I find the Event Vendor?

Originally, the Event Vendor script was loose in the vendor crate. If you haven't redelivered your vendor pack in a while (for example, if your dropboxes are still at 2.2x....) then it might still be a standalone loose script.

Currently, the Event Vendor script is now in its own sub-box within the vendor crate:

Click for larger image	1) Rez the Vendor shipping crate on the ground. 2) Click to unpack contents to your inventory. 3) Drag the Event Vendor crate from your inventory to the ground.
Click for larger image	4) Click to unpack the Event Vendor crate to your inventory. 5) Locate the Event Vendor script itself. 6) Follow the "how to" instructions in the next section.

How To Use The Event Script

Set up your vendor(s) with the regular vendor script on your "home" sim/region.
Edit the vendor
Click to the Contents tab
Delete the "CasperVend2" script from the contents
Drag the CasperVend2 Event Vendor replacement script from your inventory, into the contents of the vendor.
Once the vendor reboots, grant debit perms.
Pick up your newly modified event vendors, and rez them on the event sim/region.
MAKE SURE you continue have regular vendors rezzed elsewhere in Second Life, on a quieter sim/region. The more the merrier.
You CAN make changes to a vendor using the event script, you just have to click the vendor in-world, get the popup menu, and choose "Reset" for it to pick up the changes.

Continue Having Regular Vendors Rezzed

You need SOME regular vendors on a quiet sim in order for transactions to go through. It does not need to be a 1:1 ratio, you should only need about 6-10 regular vendors elsewhere in order to ensure the event vendors function properly.

Info for Event/Mall Organizers

You MUST allow time for merchants in your event or mall adequate time to clean up their own vendors after an event!

Cleaning Up Your Event Vendors

Because there are no incoming communications, event vendors will NEVER respond to a website scan - this also means you are unable to delete an inworld vendor via the website either.

You MUST remember to clean up your event vendors from an event before the sim goes away (either by click > menu > delete OR edit > delete > then run a bee on "Check All") otherwise you will be unable to later.

Caveats & Limitations

You must have at least one normal vendor rezzed elsewhere, on a non-overloaded region - and ideally several more. If you don't, your transactions will stall and fail!
If you make a change to the configuration on the website, the vendor will not automatically update. You have to touch it inworld and choose Reset to get it to pull the latest config.
License notecards will be delivered, but we can't wait for them to be accepted - the transaction will just go through regardless.
Same for gift deliveries - we can't wait for the customer to confirm their gift selection, it just goes through as a direct gift.
The vendor won't automatically reload if the linkset changes. So if you link the vendor to something, be sure to touch -> reset.
The event vendor script is no-transfer, because it can't be used in affiliate vendors - it can't transfer money

All these features depend on the website being able to communicate with the vendor (HTTP-IN), which is why they are not fully available with the Event Vendor replacement script.

Profit sharing DOES work.

Background - Why Is There An Event Script?

CasperVend2 is a very efficient vendor system, and as such has always been in popular use at events, many of which consisted of packed sims of 60+ avatars. Recently, though, there have been two reported instances of CasperVend vendors not working well at two particular events - Collabor88 and Uber.

While it has been very hard to diagnose these issues (none of our team have been able to gain access to the regions while the vendors were malfunctioning), we were able to get hold of some data from our side which has helped us identify the cause.

So, what's the problem?

It appears that the issue lies with the "HTTP-IN" function.

CasperVend is a very sophisticated system, which depends on complex algorithms and processes running on our servers. This is because there is simply not enough script space in the vendor itself to perform all the extensive functionality that CasperVend provides.

As part of this process, the server needs to "dial in" to the sim/region, in order to reach the vendor - this is done to send notifications, confirm option choices and license agreements, or make affiliate payments. Unfortunately, it seems that once region load gets beyond a certain point, HTTP-IN just completely falls apart and can no longer be used, with every request failing with a message like so:

  <lsl>   Proxy Error
  
  The proxy server received an invalid response from an upstream server.
  The proxy server could not handle the request POST http://10.9.4.70:13020/web/task/8f493d26-de0b-19f1-74c6-5d199f02a8df/script/b48999ce-5e27-5fe8-0c22-e0c03b34babc/http.

  Reason: Error reading from remote server</lsl>

Once such an error has been encountered, the system automatically tries to "self-heal". This causes the vendor to reset and re-establish itself in the network. Unfortunately, in such a broken region, the vendor will take a long time to get back online.

I can't stress enough that this is an issue with Second Life and the Lab's architecture (notice the internal IP address; 10.9.4.70 is a machine on LL's internal network), and NOT a problem with CasperVend or our servers.

Why has this never been addressed before 2015?

Quite frankly, it's never been an issue before. CasperVend has been used in huge events for many years, and while it's experienced some lag, there have never been such wide-scale issues before the summer of 2015.

Our best bet is that something has changed recently in the LL server-side code which makes HTTP-IN more vulnerable to lag.

The CasperVend2 Event Vendor replacement script

We've now released a special "Event Vendor" replacement script.

This is a special version of the vendor which has all inbound communications ripped out and disabled. This means it's reliable enough to function in heavily overloaded/broken regions.