Copy scripts

The E2V-3 box contains two scripts to help copy the contents of one prim to another prim. The scripts are:

Copy prim contents - FROM HERE
Copy prim contents - TO HERE

We’ll call these the “FROM” script and the “TO” script.

To use the scripts:

  1. Drop the “FROM” script into the prim that contains the contents you want to copy.
  2. Drop the “TO” script into the prim that you want to copy the above contents into.
  3. Wait for a moment. The contents will be copied, and then both scripts will automatically remove themselves.
  4. Always complete one copy before doing another copy – even if you’re copying to/from the same prim(s) multiple times.

If you’re using these scripts to copy items into your E2V Inventory Server, remember that you will need to use “Edit Linked Parts” and put the TO script into one specific Storage Box at a time. You can place the TO script into the same prim over and over, to copy from several different objects into the same Storage Box, or you can put the TO script into a different Storage Box each time.

Erase floating text

If you have some floating text over a prim and you want to get rid of it, follow these steps:

  1. Create a new script anywhere in your inventory.  The name doesn’t matter, but you might want to name it something other than New Script so that you can find it again later.
  2. Double click the script to open the script editor.
  3. Press Ctrl+A or select ALL the text in the script with the mouse, and press Backspace, or Delete, so that the script editor is completely empty.
  4. Copy/paste the script code that appears below into your script, and then click Save in the script editor. Make sure that no errors appear in the bottom of the script editor window.
  5. Drag this script from your inventory directly on top of any prim, and it will erase the floating text, and then delete itself automatically.
default
{
  state_entry()
  {
    llSetText("", ZERO_VECTOR, 0.0);
    llRemoveInventory(llGetScriptName());
  }
}

Why I dislike the term “RL”

A recent Plurk thread got me thinking again about my disdain for the term “RL” when used in contrast to SL. I do understand that most of the time, the term “RL” is used in relation to your privacy, and yeah, whatever. Do you, boo. But if you’re a content creator, and you feel like what you do in SL isn’t “real” then you’re doing yourself a disservice.

I sell a vendor system in SL, and it’s a combination of LSL (SL scripting), HTML5/CSS3, Javascript, PHP, and MySQL. Trust me when I say those are “real” technologies. And my recent job search proved that, when the interviewers were equally interested in my SL business as they were in my day job experience. You can bet that SL was listed on my resume as my own side business where I create an e-Commerce system for an MMORPG.

If you can texture, or you can do 3D models, then you’re using very advanced software and what you do is absolutely valid and valued in the “real” world. If you sell your creations in SL, and are generating income for yourself, then you own your own business. Your business is developing digital assets for an MMORPG.

I first heard about SL from an article talking about people quitting their day jobs and living off of SL income. The article was mostly about the Chung dynasty, but mentioned that many other people were doing it, too. So I never once thought of SL as a “game” for even a second. My whole purpose for starting was to see how people were able to make money. Regardless of why you first got into SL, I think the first step to truly valuing your own work is to get rid of the mindset that SL is a game that you play. You can play Halo all day and never make a cent. But if your Paypal account has seen money go in and out of it, then thinking SL is a game is just another mental block to appreciating the value of what you do in SL, and using the experience to bolster your value in the workforce.

 

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)
default
{
  state_entry()
  {
    llSetText("", ZERO_VECTOR, 1.0);
    llRemoveInventory(llGetScriptName());
  }
}

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:

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