The SML Compendium Diamond – Three Girls in SL

All-in-one gym spotter and sitter solution by the SML Compendium, a product of The Fitness Factory.

The reason we made this newer sitter system is two-fold. Firstly, Starry (the creator of the old Calculator Hud, and the spotter system) seems to have left, or is on an extended break, and we needed a calc hud for the Fitness Factory. When I had finished making it, Fen said, “Why don’t we just make a new spotting system as well?”…so we did.

The second reason is scripting. The original sitter system was made over half a decade ago, RLV and Linden Scripting has had some advances since then, our new system takes advantage of those changes. With these new advances, more scripting could be packed into the sitter and spotter system to make life a little easier for gym owners. Here’s what the SML Compendium Diamond has to offer.

All in one solution

This is a full spotter system for the normal and power equipment and also a Power Crossover Sitter system rolled into one, working under one single attachment. The new v1.33 system also separates the sitters from the spotters. Sitter and Spotter parking areas are not viewable by each other.

Spotter and sitter “Auto-Return”

Configured in the config file. You can set a time limit for spotters and sitters to remain dormant (not being used) before the system automatically returns them to their waiting area. No more abandoned spotters and sitters dotted around your gym!

Triple PCO sitter RLV sit requests & Radegast Ready Multi Sitter

The Radegast viewer, which is the preferred viewer for running Sitters due to it being a text viewer, does not handle RLV all that well. The sitter system in the diamond hits the PCO weight with 3 sit requests on 5 seperate sit positions in an eight-second timespan if the previous sit request has failed to “force” Radegast to find a sit spot. From V1.33 there is now a remote caller which cycles through PCO sitters until all seats requested by the user is filled, finally negating the issues with Radegast refusing seats.

Full character menu

No more having to come up with weird short character names for the button menus. We decided to use full character menus for the diamond.

Anyway, enough with the intros…here’s the full instructions on how to set one up at your gym

Gym Owner Setup Guide

Editing the Configuration Notecard

All system settings are stored in the included Config notecard.

To edit the system:

Right-click the Main Control Diamond.
Select Edit.
Open the Contents tab.
Open the Config notecard.
Make your changes.
Save the notecard.

The system will automatically reload the configuration.

Configuration Notecard Rundown

Here’s all the settings in the config notecard before we move on to the main instructions…

CFG_MAX_RANGE | 150 – Configures the max range of the diamond
CFG_DROP_DELAY | 2.0 – The main delay timer between PCO sitter calls
CFG_SECOND_SIT_DELAY | 1.5 – The main delay timer for PCO sitter seat calls

CFG_DEBUG | 0 – Set to 0 for no debug messages or 1 for debug messages

CFG_SPOTTER_PARK_SEAT | UUID-OF-PARKING-SEAT-GOES-HERE | Spotter Park Area 1 – The parking seats for your human spotters goes here. Copy multiple lines over for multiple seating spots.

CFG_SITTER_PARK_SEAT | UUID-OF-SITTER-SEAT-GOES-HERE | Sitter Park Area 1 – The parking seats for your PCO sitter bots goes here. Copy multiple lines over for multiple seating spots.

CFG_AUTO_DEPLOY_DELAY | 10.0 – Deploy timer for the PCO sitters between diamond rezzes
CFG_AUTO_DEPLOY_RANGE | 96.0 – Max range of the diamond for deployment
CFG_SITTER_POLL_SECONDS | 1.5 – “Poll” timer for the activation calls for the PCO sitters

SITTER_BOT_KEY | UUID-OF-SITTER-BOT-GOES-HERE | – Sitter bot UUIDs are listed here so the autoreturn systems for both the postters and the sitters do not clash with each other.

CFG_RETURN_IGNORE_AVATAR | avatar_uuid | optional label – The same for your human spotters. All avatars listed here, when wearing a diamond, will be ignored by nearby spotters and sitters on the initial radar scan on the run up to an auto return. If the avatars listed here do NOT have a diamond on, a second “ping2 to confirm the missing diamond will be sent to BLOCK an autoreturn, this way your spotters can use the equipment with no danger of having the spotter or sitter being returned by accident.

CFG_SPOTTER_AUTO_RETURN | 1 – Timer between return pings
CFG_SPOTTER_IDLE_SCAN_RANGE | 8.0 – Radar scan range of the attached diamond before a return call is sent
CFG_SPOTTER_IDLE_SCAN_SECONDS | 160.0 – Number of seconds between a radar scan to see if the spotter is abandoned.

CFG_SITTER_STILL_RETURN | 1 – Timer bewteen return pings
CFG_STILL_CHECK_INTERVAL | 7.0 – Active “Mobile” timer to check if the PCO sitter is sitting still…in other words not moving. If the sitter is NOT moving (in other words the sitter is abandoned), the main timer starts for the auto return.)
CFG_STILL_DISTANCE | 0.15 – Total distance maximum range for the stalling of the main timer.
CFG_STILL_LIMIT_SECONDS | 300 – Maximum number of seconds for the main timer to down down until a full auto return of the sitter.

CFG_DEPLOY_TIMEOUT | 60.0 – Main timeout of failed remote deply of PCO sitter.

CFG_PCO_USER_SCAN_RANGE | 15.0 – Max scan range of PCO sitter to check for avatars in distance before an auto return. If the stillness timer has triggered the return timer, and the return timer triggers a return, this final radar scan checks to see if theres a gym users within this range, if there is…the auto return is cancelled.

DEPLOY_USER | UUID-OF-GYM-MANAGER-GOES-HERE | Gym Manager – Deploy managers…UUID of gym managers added here will have access to the “Deploy” button.

TARGET | UUID-OF-EQUIPMENT | NAME LABEL – Main UUID listings of your spotter gym equipment.

TARGET_DROP_HELPER | PCOSITTER-UUID-HERE | HELPER-UUID-HERE | LABEL NAME HERE – Main UUID listings of your PowerCrossovers for the SINGLE pco seats.

PCO_REMOTE_CALLER | UUID-OF-REMOTE-CALL-PRIM-HERE – UUID of PCO remote call prims here

Setting Up The Diamond – Initial Setup & Human Spotter Setup

First of all rez out your main diamond. Generally speaking, you want the main diamond out where your human spotters will be parked to make things easier for your spotters so they don’t need to search for the diamond.

Once you have the main diamond rezzed out, you need to add all the “parking” seats for your human spoitters, these are the seats that your spotters will go to when either sent there, or when the system automatically sends them back if they have been abandoned by the user.

CFG_SPOTTER_PARK_SEAT | UUID-OF-PARKING-SEAT-GOES-HERE | Spotter Park Area 1 is the demonstration line for the park. Grab the UUID of the seat(s) via the “Copy Key” button in the dit panel of Firestoem and paste it into the relevant spot. Copy the entire CFG_SPOTTER_PARK_SEAT | UUID-OF-PARKING-SEAT-GOES-HERE | Spotter Park Area 1 line for new parking seats. Once you have done this, save the config file.

Next it’s time to set up all your spotter equipment. Rez out the object named Auto Config Diamond. Give it a few seconds to set up the script, then click on it and select “Auto All”. This auto diamond will now run through your gym, scan all of the spotter pads and at the end park itself where it was originally rezzed and give you a full chat rundown of all your spotter equipment PLUS the UUID’s…it will look a bit like this…

Find the line in the main diamond config file that says TARGET | UUID-OF-EQUIPMENT | NAME LABEL. Paste your auto diamond block into that, overwriting the original line.

It is advisable to rename the labels to make a little more sense when people see them in the menu.

Next you want to add ALL of your regular human spotter to the CFG_RETURN_IGNORE_AVATAR | avatar_uuid | optional label line. This is for the auto return system, for instance, the Power LegPress. If there are two spotters side by side, and they are NOT listed in the config file, they will scan each other as active gym users instead of spotters and they will not be auto returned if the gym user has abandoned them.

Your diamond is now set up to have spotters spotting for your main equipment!

Setting Up The Diamond – PCO Sitter System

The PCO’s (Power Crossovers) work a little differently. Originally, they were produced with no spotter system, it was a member of the community who found out that if an avatar actually sits on the physical weight, the weight calculations of the PCO actually increase. As such, “PCO Sitters” actually sit on the physical weight itself…this is where things get a little complicated.

TARGET_DROP_HELPER | PCOSITTER-UUID-HERE | HELPER-UUID-HERE | LABEL NAME HERE

There are two “Sitter” objects in the package. One is “Multiple” which is a random sitter incase you are having RLV sitting issues with your bots. The other is Single. The config line above is for the single sitter. Rez out whichever sitting system you want to use and place it directly above the weight you want the sitters to drop down on. Next, rez out the PCO Helper, and place it UNDERNEATH the sitter prim. The Helper scans for weight names and then directs the sitter bot to the UUID of the weight to sit on.

The multi random sitter is for users of Radegast or other text or low graphics viewers who are having issues with the sitter bots not sitting on the weight after the drop down. Above is the config line, like the normal Power equipment, treat each of the 5 squares as “spotter” pads that are all linked together. Copy and paste all of the UUIDS for the 5 spotter pads, inlcuding the UUID of the helper under it into the config file.

So, the order in which to do this…

1: Rez out whichever sitter prim you are going to use…single or multiple. Place it directly above the main bar “holding” the weight.

2: Rez out the helper prim, place it below the sitter prim

3: Set up the configs in the config file. MAKE SURE you fill in all the UUIDS. If the UUID for the helper isnt pasted correctly, the entire sitter system will not work.

4: Once you have confirmed everything is working, edit the help and sitter objects, and turn them 98% transparent.

Now you need to rez out the Remote Sitter Caller object. Edit the config file inside this object and add the UUID of the main diamond. Then, copy this prim out to every PCO you have in your gym.

Next, find the PCO_REMOTE_CALLER | UUID-OF-REMOTE-CALL-PRIM-HERE in the main diamond config file. Add the UUID’s of each of the remote callers to new lines so the diamond knows what it is scanning.

Lastly, add the UUIDS of all your PCO sitter bots to the SITTER_BOT_KEY | UUID-OF-SITTER-BOT-GOES-HERE | a new line for each bot. This lets the diamond know to ignore all sitter bots when an auto return is triggered to return abandoned sitter bot and return abandoned spotter.

Once all your PCO sitter bots are logged in, click on the main diamond and select “Deploy Sitter” to let the diamond send out diamond attachments to all of your PCO sitters. After 300 seconds, your relogged sitters will automatically sit on their designated parking spots.

Setting up the PCO system is tricky, but it only needs to be done once.

Adding PCO Bot Parking Areas

Parking areas are locations where spotters and sitters are automatically returned when no longer needed.

Parking areas also appear as menu options so users can manually park a spotter.

Configuration format:

CFG_SPOTTER_PARK_SEAT | UUID-OF-PARKING-SEAT-GOES-HERE | Spotter Park Area 1

CFG_SITTER_PARK_SEAT | UUID-OF-SITTER-SEAT-GOES-HERE | Sitter Park Area 1

You may create as many parking locations as desired.

Group Access

To restrict usage to a specific group:

CFG_GROUP_ONLY | 1

To allow all users:

CFG_GROUP_ONLY | 0

Custom group warning message:

CFG_GROUP_MSG | You must be a member of this gym group.

Auto Return Settings

Spotter auto-return:

CFG_SPOTTER_AUTO_RETURN | 1
CFG_SPOTTER_IDLE_SCAN_RANGE | 6.0
CFG_SPOTTER_IDLE_SCAN_SECONDS | 60.0

Example:

System is on
Looks for nearby avatars within 6 metres.
Returns abandoned spotters to a parking location after 60 seconds.

PCO Sitter Recovery Settings

CFG_SITTER_STILL_RETURN | 1
CFG_STILL_CHECK_INTERVAL | 10.0
CFG_STILL_DISTANCE | 0.15
CFG_STILL_LIMIT_SECONDS | 180

Example:

Checks every 10 seconds.
Requires at least 0.15 metres movement.
Returns the sitter after 3 minutes of inactivity.

Customising Floating Text

Text displayed above the Main Control Ball:

CFG_FLOAT_TEXT_COLOR | <1,1,1>

CFG_FLOAT_TEXT | Force Sit System\nFor Spotting\nClick Here

Use:

\n

to create a new line.

Customising Spotter Text

Text displayed above attached spotter balls:

CFG_HALO_COLOR | <0.8,1.0,0.8>

CFG_HALO_TEXT | Fitness Factory Spotter

Final Checklist

Before opening the system to customers:

✓ Standard equipment tested

✓ Power Crossover stations tested

✓ Helper objects placed correctly

✓ Parking locations configured

✓ Group permissions verified

✓ RLVa/RLV compatibility tested

✓ Config notecard saved

✓ Main Control Ball reloaded

Your Fitness Factory Spotter System is now ready for use.

If you need help setting the system up, contact liandra.aries inworld