Buh-bye floating text

Did you know that SL prims have properties that you can’t see/edit in your viewer’s edit window? Sho’nuff, they do. For example, particle emission is a prim property. That means if a script that emits particles is placed into a prim, and then deleted, the prim will continue to emit particles.

Floating text (i.e. hover text) is another such property. Here’s a quick script that will erase floating text from any prim (as long as the prim doesn’t have scripts in it that are setting the text any more), and then delete itself. I have this in my inventory as “EraseTextOnce” and so I can quickly filter for the word “erase” and drag and drop the script from my inventory on top of any prim, and bingo, it’s done.

So, if you want to use this yourself, here’s how:

  1. Right-click in your Inventory and select New Script.
  2. Name the script whatever you’d like
  3. Double-click the script to open the script editor.
  4. Erase the contents of the default script, and replace it with the text below.
  5. Press Ctrl+S (or click the Save button)
    llSetText("", ZERO_VECTOR, 1.0);

Want to know when your region restarts?

Here’s a small script you can create and place into any prim on your region, and it will send you an IM every time the region finishes a restart. This can be a lot more convenient than repeatedly trying to TP home!

  1. Edit any prim and press the “New Script” button on the Content tab.
  2. Double click the script to open the script editor.
  3. Erase all the text inside the new script
  4. Copy/paste the text below into the script editor
  5. Press Ctrl+S (or the save button)
  6. Make sure that you see the text “Save complete” in the bottom of the script editor!

Here’s the script:

  changed(integer change)
    if ( change & CHANGED_REGION_START )
      llInstantMessage( llGetOwner(), "Region just restarted." );

Rolling Restarts

For most regions the standard LL rolling restarts happen on Tuesday mornings (SLT), and on Wednesday for the remaining regions. Certain configurations of the E2V system can be affected by these restarts, and this article explains those situations.

Please see this article to be sure which version of the system you have, as it makes a big difference when it comes to rolling restarts!

To understand the impact rolling restarts can have on the E2V system in your store, it’s important to first understand how your store is (or can be) configured when it comes to product delivery. The list of rules is:

  • If your vendor is using 2.9 or earlier, product is always delivered from the Inventor Server as a box.
  • If your vendor is using 2.13 or later, you have the option of product being delivered as a box from the vendor itself, or as a box from the Inventory Server.
  • If your vendor is using any version 3 script, you have the 3 options. Product is either delivered from the vendor prim as a box, from the vendor prim as a folder, or from the Inventory Server as a box.

(“Box” in this context means a single object, which might be a box, or a bag, or a duck, or whatever.)

If your store is configured to deliver product from the Inventory Server, and your Inventory Server is not on the same region as your store, then it’s possible for product delivery to be affected by a rolling restart, as the Inventory Server basically ceases to exist while that region is being restarted.

With version 2, there’s only one way to avoid delivery problems during the time the Inventory Server’s region is being restarted, and that is to Take A Copy of the server, and rez it on the store region.

For version 3 users, you have more choices.

First, you can do nothing. This is because the Delivery Relay will queue up purchases while the server is unavailable, and will then process them once the server (i.e. region) comes back online.

Second, you also put a copy of the server on the store region.

Third, you can use a backup Inventory Server. The backup server would only be used during the time that the primary Inventory Server is unreachable. Soon after the primary server region comes back online, the Delivery Relay will automatically switch back to the primary server.


What version of the E2V system do I have?

As of this writing, there are two live, active versions of the E2V system in use. They are called “version 2” and “version 3.”

You can tell which version you have in two very simple ways:

  1. If your Inventory Server is white, you’re on version 2. If it’s black, you’re on version 3.
  2. If your vendor scripts are called “[E2V] Vendor 2.x” then you’re on version 2. If they’re called “[E2V-3] Vendor 3.x” then you’re on version 3. (Note that the “x” in both cases will actually be a number)

About Version Numbers

Version numbers in software operate a little differently than normal numbers. For example, you might think that version “2.9” is greater than version “2.16” if you view the numbers as traditional fractions. However, version numbers are typically presented in the format “major.minor” where 2.16 is a later version than 2.9, because the number “16” comes after the number “9.” In other words, don’t view them as decimals/fractions, view each number as a whole number, separated by a “.” character.

Admin Website URLS

If you’re on version 2, your admin site is located here: http://www.e2-designs.com/e2v/owners/

If you’re on version 3, your admin site is here:  http://www.e2-designs.com/e2v-3/owners/

There are a few things to note about these versions and sites:

  • All your sales data, whether you’re on 2 or 3, goes to the same place. if you upgrade to 3 from 2, you’re still accessing the same sales data.
  • Since both websites access the same sales data, many functions can be performed on either site. However, due to changes in version 3, some of the version 2 site’s functions will have no effect. Specifically, the store-wide sale feature, and anything having to do with split proceeds has moved in-world.