Settings Menu
Ahh the settings menu. Here’s where I get all option-y 🙂
 |
This sets who can access the Silo’s main menus. It can be set to Public, Group, or Private. Note, this does not grant access to the Settings menu. That can be managed using the Admins notecard (see below). |
 |
The Silo stores information on the most recent 15 captives. It uses this to recapture them when they log back in or come within range of the Silo following a non-release un-sit. This button will clear the current list of captives. |
 |
This button opens a secondary menu that allows you to set the maximum amount of time someone using the Self-Bondage system will be held. |
 |
Increase the scan range the Silo will use when looking for potential captives. The range can… Err, range from 10 to 90 meters and increases in 10 meter increments. |
 |
These buttons let you set the Silo ID number which is displayed on the front of the Silo. It’s also used by the optional (and yet to come) Silo Console and Silo Status Board. |
 |
The Silo has two isolation levels; Comms – which prevents IMs and local chat, and Total – which blocks all outside interaction. This button allows you to set the default isolation level imposed when someone is captured. |
 |
Since the Silo might be used in locations where there isn’t a handy hole in the floor, I added a shadow that will hide the unhelpfully hole-less area. Clicking the Shadow button will toggle the shadow prim on or off to help obscure the holelessness. What? It’s a perfectly good word 🙂 |
 |
Saves the current prim adjustments as the default, so the Silo will reset to these positions. |
 |
Performs a complete script and resizer reset on the Silo. |
And that’s the Settings Menu.
Admin Access
Now let’s talk about access, specifically who can access the settings menu. Assuming that you’re the owner of the Silo, if you were to edit it and take a look in the contents tab you’d see this:
The scripts are no mod so you can’t edit them – it turns out that much like laws and sausages, you really don’t want to see how scripts are made 🙂 – but the Admins note card is full perm, so edit away! By default it looks like this:
Anyone named in the note card is given admin access to the Silo meaning that they can access the settings menu. The Silo is “shipped” with me and my building alt’s names in there as examples and also so we can trouble shoot things if someone is having problems with their own Silo, but you can delete both names and add your own, or simply add your own. You can even delete the note card entirely if you want to eliminate secondary admins.
Oh and it has to be the user name not the display name. That’s why my building alt is in there as DiabolicalSuperScience Resident rather than Winifred Hinchcliffe which is the name she goes by in person.
Demo Mode
Lastly is something that most people probably won’t bother with – that’s why it’s “lastly” – demo mode. When a Silo is in demo mode it treats everyone – including a current captive – like an admin, so they have access to the settings menu and can release captives, including themselves. It’s mainly in there so I can put demo versions out for people to test without getting stuck on it for hours at a time.
To put a Silo into demo mode simply edit the Silo and add a space and the word demo to the object name of the Silo – so it looks like this “Silo 42 v1.0.0 DEMO” – and do a script reset. To take it out of demo mode delete the demo from the object name field and do another script reset.