This is a script to play a looped sound on click, ideal for a door bell or similar. Supports access control (owner, group or everyone, with whitelist and blacklist support), and is supplied full perms (so also good for anyone learning to script).

XStreetSL: https://www.xstreetsl.com/modules.php?name=Marketplace&file=item&ItemID=1374178

inSL:  http://slurl.com/secondlife/Sunweaver%20Air/195/36/141

Script to notify the owner of a prim when it is clicked, and the identity of the avatar that clicked it. Includes a link to the avatar’s profile, so you can easily identify who they are. For example:

Click ‘n’ tell 1.0: I’ve just been clicked by Xugu Madison ( secondlife:///app/agent/c5ff894e-d6e4-48bb-b6fe-f143447d95a1/about ).

Due to how object -> avatar instant messages work in Second Life, while the message only goes to the owner it shows up in the local chat tab (instead of being a new tab as avatar instant messages do). Second Life also rate-limits messages from objects, so if the prim is clicked repeatedly (over about 15 times in 30 seconds) the script could lose some of the clicks.

This is an XStreetSL exclusive at the moment: https://www.xstreetsl.com/modules.php?name=Marketplace&file=item&ItemID=1491906

Again, not new, but first announcement here; notecard/speech reading script (inSL). Ideal for helping with presentations, SL-weddings, etc. this script allows you to select a notecard from inventory (by means of a paged dialog menu), and it will read it out, with configurable pacing. It can take an unlimited number of notecards to read (selection by dialog menu), and optionally can animate the avatar while a speech is read out. Speech rate and distance are configurable by notecard, as are the details of who exactly can use the script.

Instructions (Copied from the included notecard)

1. Open the box (I’m assuming you have if you’re reading this).
2. Copy the “Speech reader 1.2″ script out into your inventory, and the sample Configuration if you wish.
3. Drop the speech reader script into an object of your choice, along with any notecards for it to read.
4. If you wish to animate the avatar while the notecard is read, drop an animation in to prim inventory as well as the notecards (a full perm chicken dance is provided if you need a test anim).

To use, click the object the script is in, which will bring up a dialog menu. From there, select a notecard or press “Prev” or “Next” to move between pages of notecard names. Once a notecard is selected, it will request the notecard from the asset server (this may take a couple of seconds) and start reading it once the asset server responds. The script will attempt to animate the reading avatar with it if can find a suitable animation in inventory, and will not start reading until animation permissions are received.

To pause playback, put a line with just “[PAUSE]” on it in the notecard, as in:

The itsy bitsy spider went up the water spout.
Down came the rain, and washed the spider out.
[PAUSE]
Out came the sun, and dried up all the rain
And the itsy bitsy spider went up the spout again.

This will cause the script to pause on that line until clicked to indicate it should continue.

Configuration

Configuration is done by a special notecard called “Configuration”, such as:

access=owner
read_delay=1.0
whitelist=Gusher Castaignede
whitelist=Xugu Madison
blacklist=Doctor Evil
shout=false

All lines should be of the form “setting=value”. This example does the following:

1. Set the access permissions to “owner” (can also be “group” or “everyone”), allowing only the object’s owner and anyone in the white list to access it.
2. Sets the delay between reading lines of the notecard, to 1 second.
3. Add “Gusher Castaignede” to the white list.
4. Add “Xugu Madison” to the white list.
5. Add “Doctor Evil” to the black list.
6. Have all text from the notecard said (as opposed of shouted).

If access permissions were set to group instead (“access=group”), anyone with the same ACTIVE group as the one the object belongs to, would be able to access it (except for people in the blacklist). If access permissions were set to everyone (“access=everyone”), anyone except avatars in the black list would be able to access it.

Read delays are specified in seconds, and are a minimum of 0.1 seconds due to LSL limitations.

White/black list commands add to the list (rather than replace it). There is no way of adding multiple avatars from one line.

Shout can be set to “true” or “false”, and primarily affects the range at which the speech reader can be heard.

Not new products, but ones I’m seeing a lot of interest in, recently; prim counters for rental parcels.

First of all, we have the fairly standard multi-renter single parcel counter. This is intended to give avatars sharing a single lump of land, an idea of their prim usage compared to their prim quota. Produces output such as:

Single parcel multi-avatar prim counter 1.2: You are using 309 out of a quota of 1000 prims for this parcel.

Prim quotas are defined in an included notecard. Requires that the prim’s owner has “owner-like” access to the land; that means either be parcel owner, or be an officer in the group the land is deeded to (apparently; have to admit I’m trusting the documentation on that one).

Secondly, there’s the multi-parcel prim counter. Designed to sit in a rental office or similar on arented out sim, it takes in one or more landmarks (for parcels on the same sim). When clicked by its owner, it tells them the total prim allowance and usage for the parcel each landmark points to. Output example:

Demo prim counter: “Chess set at 400m” contains 35 out of a maximum of 351 prims.

Both scripts are L$50 each, and available from XStreetSL or directly from my in-world store.

Starting my new range of “core” scripts at value prices, we have a modifiable vendor. Nothing exciting; sits in a prim, takes money, hands out objects. Perfect if you’re just getting started, or have ever wanted to see what a vendor script looks like on the inside. Currently this is an XStreetSL only item, but it will be going into rotation through my shops over the next few days.

Configuration is done entirely by chat commands. All you have to do is drop the script and object (or objects to sell as a set) into a prim together, tell it the price (in chat), and it does the rest. A sample vendor is provided, if you get stuck. Full instructions included in the package. As always, free updates for life are just part of the standard customer service.

XStreetSL: https://www.xstreetsl.com/modules.php?name=Marketplace&file=item&ItemID=1478419

XStreetSL: https://www.xstreetsl.com/modules.php?name=Marketplace&file=item&ItemID=1476281

This is a texture cycling script, intended for use in building houses or similar. It changes the textures on one or more sides of some prims it  is linked to, cycling sequentially through a set of textures in prim inventory. Can be configured to only respond to prim owner, anyone whose ACTIVE group is the same as the prim, or everyone.

IMPORTANT:

1. The textures MUST be full perms, due to SL’s permission model.
2. This can only change linked prims.

Configuration (taken from included docs)

The prims which are changed, which sides are changed, and who the script responds to are configured by setting the description on the prim the script is in. This description should be of the form: Change “<prim name>” sides <sides> on <access> click

Prim name is the name of the prims that the script will change. For example, if you set it to “Window pane”, the script will affect all LINKED prims called “Window pane”.

Sides is a comma-separated list of sides of the prim. If you’re not sure what you’re doing, “2,4″ is a safe bet for this, and changes two opposites sides of a cube (rotate the prim if it’s not changing the sides you expect).

Access can be “owner”, “group” or “everyone”. Please note that group access requires the avatar’s ACTIVE group matches the prim’s group (not just that they are part of the group).

Examples:

Change “Window pane” sides 2,4 on owner click
Change “Window” sides 2 on everyone click

XStreetSL: https://www.xstreetsl.com/modules.php?name=Marketplace&file=item&ItemID=1471933

XStreetSL demo: https://www.xstreetsl.com/modules.php?name=Marketplace&file=item&ItemID=1474518

Second Life: http://slurl.com/secondlife/Sunweaver%20Air/203/45/141

Ever wanted to ship a HUD with your hair, eyes or fairly much anything else, so it can be re-textured or re-colored by the end user? This is the product for you. Full perms on all scripts, a complete HUD for setting textures, colors and glow on unlinked prims.  Comes with all the scripts you need to set up the HUD, plus a sample HUD. Script for putting in the target prims is also provided. Textures can be loaded from prim inventory or stored within the HUD script itself. Colors and glow can be configured by changing the button they’re on to the right values and using the included scripts to handle the HUD configuration for you.

Instructions

While a sample HUD is provided, you are strongly encouraged to make your own HUD to hold the scripts (particularly as mine is really ugly).

There are 3 scripts for the HUD, 1 script (change receiver) for the target prims, and 2 supporting tools (texture UUID dumper and face identifier).

HUD Setup

The HUD scripts are:

• Color reporting script
• Glow reporting script
• Texture changing HUD script

“Texture changing HUD script” goes in the ROOT of your HUD’s link set, and handles all clicks on the HUD. It identifies which button is being pressed by the prim’s name, which is where the two reporting scripts come in. While textures are managed by the HUD script, color and glow buttons must have pre-configured, and the two reporting scripts set name of the prim they are put in according to its color/glow.

There are 5 buttons supported by the HUD script (specified by name):

• “Texture preview” – these prims have textures set across their faces by the HUD script, to show the user textures they can choose.
• “Color <color>” – these prims trigger a color change when clicked. For example, a prim named “Color <0.00000, 0.00000, 0.00000>” would set the target to black when clicked.
• “Glow <glow>” – these prims trigger a glow (and optionally fullbright) change when clicked. For example a prim named “Glow 0.25″ would set a prim to quarter-glow when clicked.
• “Left arrow button” and “Right arrow button” – these allow paging through the texture preview.
• “Minimise button” – minimises the HUD by rotating it 90 degrees, and also de-minimises (but do make sure there’s a button on the face the user can see when the HUD is minimised!).

Any button is optional, and any button except left/right arrow can be duplicated across the HUD as many times as you can get to link.

Textures are loaded from two places; firstly, from a list stored inside the script, and secondly from prim inventory. While the first requires more work, it is required if you do not wish to ship full permission textures with your HUD due to SL’s security model. This is where the first supporting tool, “Texture UUID dumper” helps; if you put your textures (which MUST be full permission) into the Texture UUID dumper, then click it, it will produce a list or lists ready for insertion into the script.

If the texture UUID dumper produces more than one message (message length from LSL is limited, which makes this necessary), you’ll need to remove the “];” from the end, and “[" from the start, of between messages to create a single list for the LSL script.

The list should then be put into the script at the line (in place of "[]“:

list STORED_TEXTURES = [];

If you then ship the scripts (both HUD and change receiver) without modify permissions, the customer won’t be able to read the UUIDs out of the script. If you’re doing this, I’d recommend changing g_Channel in the HUD script and change receiving script, so they can’t listen for messages between the two scripts and extract the UUID that way. Remember that the channels MUST agree for the script to work.

Target Prim Setup

In each prim you wish to change you should put the script “Change receiver” into prim inventory. This script will attempt to load a configuration notecard and then listen for commands from the HUD. It can be configured to change only some sides of a prim, and to change full bright settings along with glow, by putting values into a notecard called “Configuration”, with the notecard placed in the same prim as the change script.

The configuration should look like:

sides=1,2,5
glow bright=false

In this case, that would change only sides 1, 2 and 5 of the prim, and would not change full bright settings. By default (if there is no sides entry in the configuration notecard), the script changes all sides of a prim at once.

For full bright settings; depending on use case, it can be beneficial to set full bright on prims when a prim is set glowing, in order to provide a glow boost, and also to disable full bright when glow is set to 0. This is where the “glow bright” option comes in; disabled by default, it sets a prim’s faces to full bright if glow is set to non-0 values, and sets full bright off if glow is set to 0. It can be configured with lines such as:

glow bright=true
or
glow bright=false

in the configuration notecard.

For identifying sides of a prim, a simple “Prim face identifier” script is provided which will say the number of the side clicked, when it is placed in a prim. Please note that the script is shipped not running; once you have added it to a prim, use Tools -> Set Scripts to Running in Selection to start the script.

Samples

A sample HUD, with a selection of random textures from a freebie box, is provided. Feel free to use it as a base for your own HUD (or ship it as is, if you like it, your choice).

A sample change receiving prim, “Change receiver”, is also supplied. It may provide particularly useful as it contains a sample configuration.

The first of my major releases this month is a tool for setting texture/color on prims in a link set. You can grab it from XStreetSL at https://www.xstreetsl.com/modules.php?name=Marketplace&file=item&ItemID=1471045.

Has three basic modes of operation:

• Bucket – sets all prim faces to one texture/color.
• Paint – sets an individual prim face on click.
• Replace – substitutes one texture/color with another.

Usage

There are three scripts, in two parts; a HUD which controls the texture tool, and the texture tool which performs the actual changes. The texture tool works by being linked to the target prim(s). For texture replacement to work, it needs to inject a script into every prim in the link set, and those scripts then need to be set running. Once finished, de-linking the texture tool from the link set will cause its client scripts to self-delete.

So, the procedure is, step by step (the texture tool will walk you through this, too):

1. Rez texture tool and target prim(s).
2. Link texture tool at root of target prim(s) linkset.
3. Click texture tool to start script injection.
4. Take link set to inventory.
5. Rezz link set from inventory.
6. While in build mode, select link set, then from the Tools menu pick “Set Scripts to
   Running in Selection”
7. Wear the HUD to control the texture tool.
8. Make changes.
9. De-link the texture tool from the target prims, to cause its supporting scripts to self-delete.
   You can do this by selecting the link set, then enabling “Edit Linked Parts” (from the Tools
   menu), click the tool prim to select only it, and then click “Unlink” in the Tools menu.

The HUD, when attached, contains 3 basic parts:

1. Mode buttons (far right); Bucket, Paint and Replace.
2. Texture preview buttons (centre).
3. Color buttons (bottom) – supplied in just black and white, but you can add more by
   duplicating the existing button and attaching them to the HUD.

Textures are loaded from prim inventory, and MUST be full perms for the HUD to operate correctly.

To set all prims to one color/texture, select Bucket (it should turn yellow), then click on a texture preview button, or color button.
To set individual prims, select Paint, then click a texture/color, then click prims in the target link set. The clicked face will change to match the selected texture/color.
To replace textures/colors, select Replace, then click the texture/color to be replaced, followed by the texture/color to replace it with. Clicking a texture after a color, or a color after a texture, will cause the initial choice to be cleared.

Somewhat in the theme of raffle balls or magic chairs, this is a rezz-day present giver. If an avatar clicks on the prim on the same day as the created their account (were “rezzed”), it gives them a random item from inventory. Otherwise, it tells them how many days until their rezz-day. Handles leap-birthdays (Feb 29) by handing out presents on March 1st instead (if the current year isn’t a leap year).

This script will only hand out objects (prims and prim sets), never notecards, landmarks, scripts or any other type of inventory.

XStreetSL: https://www.xstreetsl.com/modules.php?name=Marketplace&file=item&ItemID=1469303

Second Life: http://slurl.com/secondlife/Sunweaver%20Air/211/43/141

Looks up the age and height of any avatar that clicks it. Nothing more than a cute toy. Produces output such as:

Avatar age & height detector 1.0: Xugu Madison is 1791 days old, and 1.22 metres tall (without shoes).

XStreetSL: https://www.xstreetsl.com/modules.php?name=Marketplace&file=item&ItemID=1468356