hippoSECURE User Guide
Welcome to hippoSECURE, a powerful yet easy to use security system that can help to keep unwanted visitors from your land. Among its many features:
- Maintain a list of banned avatars (the black list) and friendly people who you’re happy to see (the white list).
- Four operational modes (off entirely, list nearby avatars, remove anybody on the black list, remove anybody not on the white list).
- Customise the scan range, scan frequency, the way people are moved, the warning time and many other settings.
- Network several hippoSECURE units together so that you can control larger areas (Second Life limits mean one prim can only scan a 96m radius).
- If you own our hippoRENT system, you can connect a hippoSECURE unit to a rental box to allow tenants access or, if you wish, allow them to manage their own white and black lists.
Enough of the features, let’s look at what this document describes for you ...
1. Setting up your hippoSECURE system
2. Managing your white list, black list and managers list
3. Setting other options
4. Connecting multiple hippoSECURE systems together in a network
5. Connecting a hippoSECURE system to a hippoRENT rental box
6. Using a hippoSECURE system on group land
7. Configuring via notecard rather than via menu
8. Logging visitors
9. Connecting a hippoSECURE unit to a door system
1. Setting up your hippoSECURE system
Your hippoSECURE folder contains three objects: a hippoSECURE unit, a hippoSECURE Ejector (for use on group land, see below) and an affiliate vendor that lets you resell hippoSECURE for 20% commission.
Begin by rezzing a hippoSECURE unit on the parcel of land that you wish to protect. Click the unit and the main menu will appear.
The buttons on this menu are, from left to right and top to bottom ...
|White List ||Allows you to control your white list. People on your white list are always allowed access. |
|Black List ||Allows you to control your black list. People on your black list will be automatically booted in the two active modes (more on modes below). |
|Managers ||Allows you to maintain a list of other people who can control your security system. |
|Mode ||Click this then pick a mode to run your hippoSECURE unit in: |
Off -> it will ignore everybody
Black List -> people on the black list will get removed immediately; anybody else will be ignored
All -> black list targets will get removed immediately; strangers will be asked to leave and if they have not done so in the warning time you have specified (see below), they will be removed.
Scan Only -> Nobody will be removed, the unit will simply report the names and distances of people it detects.
Tip for Advanced Users of Version 1.5 or higher If you’ve networked several hippoSECURE version 1.5 units together (see section 4 below) then when changing the mode (off/scan only/black list/all) via the menu on any unit you’ll be offered the opportunity to switch the mode on every connected hippoSECURE unit as well. This makes it very quick to change security levels on every unit in a sim at once, for example. (You can turn this feature off via a configuration notecard setting, should you wish).
|Options ||Configure various system settings, including the scan range, scan frequency and warning time. |
|Status ||Report the status of your hippoSECURE unit. |
|Networking ||Set up networking, either between hippoSECURE units or between a hippoSECURE unit and a hippoRENT box. |
|Logs ||Opens the logs sub-menu which has some options that are useful if you’re logging visitors and activity. |
- List Logs
Prints out the current logs (date, time, visitor name, visitor key and what action, if any, was taken against them).
Wipes the current logs (you’ll be asked to confirm this).
- Email Logs (version 1.6 or higher only)
If you’ve specified an email address in the hippoSECURE unit’s configuration notecard, this will email the current logs to that address.
|Tools ||Opens the tools menu. In here, you’ll find several options ... |
- Test On
Test mode allows you to easily check that you’ve set up your scan area up correctly. Simply pop the hippoSECURE unit into “Scan Only” mode then then select “Test On”. Every time it scans you, the unit will send you an instant message. This allows you to simply wander around your land and check it’s detecting in the right places.
- Test Off
When you’re finished testing, “Test Off” will cancel test mode.
- Ejectors (version 1.6 or higher only)
If networking is turned on, this option will appear. Its sub-menu allows you to find (or automatically delete) any functioning Ejectors of yours in the sim (provided they’re set to network on the same channel as this hippoSECURE unit).
|Reset ||Resets the hippoSECURE unit and its settings to the default. If a “_config” notecard is contained in the unit (see below) it will read the settings from this. |
|Help ||Directs you to this web page. |
Please note that when you click the hippoSECURE unit it will listen for menu commands for five minutes then stop listening, to cut down on sim lag. Simply click it again to get it listening for menus again.
1.1 Determining an area to protect
To determine the area your hippoSECURE unit protects click it, pick “Options” from the menu, then choose ”Scan Range” and type the range in metres to scan (minimum 1m, maximum 96m (this is a Second Life limit)). Remember that Second Life limits also mean the unit will only detect the 16 closest avatars at any one time. The range you input here will determine the radius that the unit scans.
There are two more advanced ways to determine what area the hippoSECURE unit scans ...
1.1.1 Protecting just the land parcel
To protect just the same parcel as the hippoSECURE unit is sitting on, add -p to the range. So, for example, to scan 50m but just check the current parcel, click the unit, choose “Options” then “Scan Range” and type 50-p then press enter. This is a good way to avoid annoying your neighbours (and getting Abuse Reports filed against you). We recommend you use the -p setting most of the time.
1.1.2 Protecting a rectangular area
By default, hippoSECURE uses the standard Second Life scanning tools which scan a circular area. If you want to be clever, you can scan a rectangular area. This takes a little more work but with practice is very simple ...
- Move your avatar to the bottom left corner of the rectangular area you want to protect and note the x,y,z coordinates of that position (the Second Life menu bar has them, after the current sim name, for example it may read “Hippo Technologies 14, 200, 37 (PG)”. It’s the 14, 200, 37 you would want here.
- Move your avatar to the top right corner of the rectangular area you want to protect and note those coordinates; let’s for this example use 25, 190, 52.
- Click the hippoSECURE unit, choose “Options” then “Scan Range” and type <14, 200, 27>|<25, 190, 52> then press enter. (Note the | is the bar character, not a lower case L or capital i.).
- Clever users may like to know you can combine rectangular scanning and parcel only scanning, so you could use, for example, <14, 200, 27>|<25, 190, 52>-p.
- Version 1.5 and above of hippoSECURE can use relative coordinates if you prefer. For example, to set up a bounding box that extends 10 metres around and 5 metres above and below a hippoSECURE unit, you’d use <-10, -10, -5>|<+10, +10, +5> ... if a + or - sign occurs before a number, hippoSECURE will take it as a relative value: if there isn’t, it will take it as an actual coordinate. You can mix the two coordinate types, e.g. <-10, 190, -15>|145, +15, 530>.
1.2 Setting the scan rate
To determine how frequently your hippoSECURE unit scans for avatars click it, pick “Options” from the menu, then choose ”Scan Rate” and type the frequency in metres to scan (minimum 1 second, maximum 3600 (one hour)). The more frequently your unit scans, the greater the sim resources it will use; we’d recommend between 3 and 5 seconds.
1.3 Determining how people are removed
If you click on the “Removal Button” in the options menu, you will see that a hippoSECURE unit offers four ways to remove people from your land.
|Teleport ||The offending avatar is teleported to their home location. Note, you have must have the right to manually eject people from he land parcel if the hippoSECURE unit is to be able to do teleport people home. (If the unit is on group owned land, you will need have deeded it to use this (see below)). |
|Eject ||The offending avatar is ejected from the land (same as right-clicking them and choosing “Eject” manually). Note, you have must personally have the right to manually eject people from the land parcel if the hippoSECURE unit is to be able to do it. |
|Ban ||The offending avatar is added to the land ban list. (Note, you have must have ‘Ban These Avatars’ ticked in the ban tab of your land, or Second Life may fail to add names properly). People on the black list will be permanantly added when they are removed, strangers will be banned for two hours at a time if they are removed this way. Note, you have must have the right to edit the land ban list on the land parcel manually if the hippoSECURE unit is to be able to do it. (If the unit is on group owned land, you will need have deeded it to use this (see below)). |
|Advanced Tip! |
If you’re using version 1.5 or higher of hippoSECURE then you can control how long the ban will last by adding the BAN LENGTH: <time in hours> command to your hippoSECURE unit’s “_config” notecard to govern how long that ban will last. Use BAN LENGTH: 0 to set a permanent ban (the default setting, if you don’t specify another).
|Orbit ||The offending avatar is thrown off the land in an amusing way. Note, despite the comedy value, orbit is actually not that reliable; some shield devices offer some help against this and some land settings do not allow pushing. |
1.4 Turn your unit on
Finally, click your hippoSECURE unit then choose “Mode” and pick the mode you wish the unit to operate in (see above for a list of what the four modes do).
2. Managing your white list, black list and managers list
Your hippoSECURE unit can hold three lists inside it; up to 500 people on the white list (people who you consider friendly and wish to have access to the land); up to 500 on your black list (nasty folks who you want to remove on sight); and up to 100 managers, people who can control your security system. (Note: for versions of hippoSECURE earlier than 1.5, these limits are 80 for the white list, 80 for the black list, and 14 for the managers list).
To add somebody to the white list, click your hippoSECURE unit and choose “White List” from the menu. Then click “Add” and their name (or several names, separated by commas). The name must be their exact Second Life name. A hippoSECURE unit is case-sensitive, so “Kermit Frog” is not considered the same as “kermit frog”. The unit will report that each name has been added.
|Advanced Tip (v1.6 or higher only) |
You can add people to your white list for a limited time, if you wish. When typing their name, as above, simply add :<time in minutes> to their name. For example, you might type David Dimpleknees:12 to add David to your white list for 12 minutes. After this time, he’d automatically be removed.
If you’ve added somebody in this way, listing your white list will also tell you how much time they have left. For example:
hippoSECURE v1.6 whispers: WHITE LIST:
hippoSECURE v1.6 whispers: fred flintstone (will expire in 8 minutes)
hippoSECURE v1.6 whispers: david dimpleknees (will expire in 10 minutes)
Once you have done that, you could explore the other “White List” menu settings. You can remove people in much the same way from a list, wipe the list entirely clean or click “Group” and “Allow” to allow anybody wearing the same group tag as the group tag on the unit (assigning prims to a group is a Second Life topic, beyond the scope of these notes) to have access.
Managing the black list and the managers list is almost identical and very simple.
|Time Saving Tip! |
If the person you wish to add to a white, black or manager list is standing within scan range, simply use the “Add Nearby” button on the white, black or manager list menus. You’ll be given a list of nearby people to choose from to add. This can save lots of typing! (Note: if more than 12 people are in scan range, only the first 12 will be shown, due to the limit on Second Life menu sizes).
|Advanced Tip! |
You can also include managers’ names in the description field of the hippoSECURE object if you wish.
Welcoming or Banning by Age or Payment Status (Version 1.5 and above)
- You can add an age check to your white or black list. Here are some examples ...
- To consider people older than 30 days white listed, add AGE>30 to the white list (don’t put a space between “AGE”, “>” and “30”).
- To consider people younger than 60 days white listed, add AGE<60 to your white list.
- To bar people younger than 100 days, add AGE<100 to your black list.
- To bar people older than 365 days, add AGE>365 to your black list.
- You can also check people’s payment status and allow (or bar) them accordingly. Use the tags PAYMENT_NONE (to filter people with no payment information on file with Second Life), PAYMENT_ON_FILE (people with payment information on file) or PAYMENT_USED (people who both have payment information on file and who have used it). Here are some examples ...
- To consider people with payment information on file as white listed, add PAYMENT_ON_FILE to your white list.
- To bar people with no payment information on file, add PAYMENT_NONE to your white list.
- To remove a white list or black list filter of this type, just treat it as a normal name (e.g. use the “Remove” button on the black list menu and type PAYMENT_NONE to remove black-listing-by-no-payment). You can simply type AGE at the removal prompt to remove any age type filter.
- If you add competing criteria, e.g. AGE<100 to your black list and AGE>50 to your white list, the black list takes precedence. So in this example, somebody aged 75 days old would be removed.
3. Setting other options
There are some other useful options in your hippoSECURE unit’s options menu that are worth exploring. To control what information the unit displays above it, click “Options” then “Hovertext” then “Status” to determine whether the unit’s operational mode is displayed above it and “Names” to decide whether to show the list of avatars it has scanned above it in every mode (they are always displayed in ”Scan Only” mode.
The “Update” button will check to see if there are any updates available for your hippoSECURE system. Hippo Technologies offers free updates, for life, on all of our products. If you join the Hippo Technologies Users Group inworld you will also get announcements when products or updates are available.
4. Connecting multiple hippoSECURE systems together in a network
Second Life limitations mean that one hippoSECURE unit cannot scan more than 96 metres away from itself (so the maximum scan area is a circle, with a 96m radius). However, you can network two or more hippoSECURE units to cover a wide area. Networking means that the connected hippoSECURE units will share their white lists, black lists and manager lists. Hence you can easily protect a wide area by rezzing multiple units, configuring their scan ranges and ejection types, then connecting them together.
The process is very simple. On your first hippoSECURE unit, click it and choosse “Networking” from the menu and then “Security”.
Click “Channel” and then type in chat a channel number for the boxes to communicate on. We recommend a large negative number, for example -57361. (It does not matter if other objects in the sim are communicating on the same channel, as data sent between hippoSECURE units is encrypted).
Now choose “Start’” from the menu.
Finally, rez a second hippoSECURE unit and repeat the procedure (pick the same channel number, then “Start”).
Once both units have networking turned on and the same channel number set, any changes you make to a black list, white list, or manager list on one unit will be copied to the other.
You can network any number of hippoSECURE units but networking will only work within sims, not across sim borders.
|Time Saving Tip! |
You can easily copy the entire white, black and managers lists from one hippoSECURE unit to all the other units on the same network. Once you’ve set up networking as described above, simply click the hippoSECURE unit that you wish to copy the lists from. Choose “Networking”, then “Security” and finally choose “Copy Lists”.
5. Connecting a hippoSECURE system to a hippoRENT rental box
If you use the hippoRENT rental system, you can connect a hippoSECURE unit (or several units) to a rental box. This allows several possibilities ...
- Tenants and their partners will automatically be allowed safe passage by the hippoSECURE unit.
- Rental box managers will be able to control the hippoSECURE unit and will also not be removed.
- If you wish, you can allow tenants and partners to control some aspects of the hippoSECURE unit’s functionality; for example, you might let them add or remove friends to the white list.
5.1 Connecting a rental box
The procedure is straightforward. Begin by adding the ‘PLUGIN_security’ script that can be found in your hippoSECURE folder to the rental box. (Right click the rental box, choose “Edit” from the Second Life menu, then More>>> if it is showing, then click on the contents tab, then drag the script to the box’s inventory.) Double click on the script in the box’s inventory to edit it (it comes with full permissions) and change the network_channel and passphrase variables at the top to a channel number of your choice (a large negative number is good) and a passphrase to protect communications (I use a random jumble of letters myself). So, for example:
Save the script and ensure that “Running” is checked at the bottom of the script window before you close it.
If everything is okay, the rental box will say “Plugin Active” when you save it.
Once you’ve done that, click on the hippoSECURE unit, pick “Networking” from the menu and then “Boxes”. Pick “Channel” and type in chat the same channel number you used in the box script, then do the same for the passphrase. Finally you can click “Turn On” to start box networking. It is probably then a good idea to either reset the box (or use the PING SERVER voice command) to force it to send an initial update to the hippoSECURE unit. If the box has tenants, you’ll see their names listed when you use the hippoSECURE unit’s status command from the main menu.
Once you have successfully set this up, any changes made to the rental box (tenants renting or leaving) will be transmitted to the hippoSECURE unit.
5.2 Determining what functions a tenant can control
The hippoSECURE system allows you to quite carefully control what a tenant can do with any hippoSECURE unit connected to a box that they are renting. This is done using the “Permissions” menu option (under “Networking” -> “Boxes”). Pick that command and you will be asked to type the permissions you wish to assign. Use the codes below, separated by commas if you wish to assign more than one.
|X ||Tenant cannot use any hippoSECURE functions. |
|F ||Tenant has full access to the white list, black list and options menus. |
|W+ ||Tenant can add people to the white list. |
|W- ||Tenant can remove people from the white list. |
|B+ ||Tenant can add people to the black list. |
|B- ||Tenant can remove people from the black list. |
|M ||Tenant can set the mode (off, scan only, eject black list, eject any stranger) |
|H ||Tenant can set hovertext options |
|R ||Tenant can change the removal method (ban, eject, orbit, teleport home) |
So, for example, to let a tenant manage the white list and hovertext settings only, you would use w+, w-, h .
5.3 Useful tricks
If you’re using hippoSECURE v1.6 or higher and are configuring it with a configuration notecard, you can easily configure your system to load a different configuration card when the connected rental box is rented. This offers the ability to offer a “default” setup to new tenants, for example. See here for more information.
6. Using a hippoSECURE system unit on group land
The hippoSECURE unit can be used easily on group owned land, using the included hippoSECURE Ejector unit. The Ejector unit will be deeded to your group (it comes with both copy and transfer rights) so that it has the necessary permissions to eject, teleport home or ban people.
The steps are very simple:
- Turn on networking on your hippoSECURE unit and make a note of the channel number you choose. More information on this can be found above.
- Rez a hippoSECURE Ejector Unit on the piece of group land you’re securing; next to the hippoSECURE unit itself is probably easiest, but an Ejector can be anywhere in the same sim as the secure unit.
- Right-click the Ejector unit and choose Edit (and then More>>> if only the mini Second Life build dialog window has opened).
- Click on the ‘Contents’ tab, then double-click the ‘_config’ notecard to open it. Change CHANNEL: 0 to the networking channel you are using (e.g. CHANNEL: -3420) and close and save the notecard. The Ejector unit will reload it and report readiness.
- Once you’re happy, tick ‘Share with Group’ and then click ‘Deed’. Please note, once you’ve done this, you will not be able to edit the _config notecard again. So ensure the channel is set correctly. (Although you can always simple rez a new Ejector unit at any time and start again).
- That’s it. Anytime the hippoSECURE unit needs to eject somebody from the land, it will contact the Ejector unit which, because it is group-deeded, will be able to eject, teleport home or ban them.
- Having problems with an Ejector? Just change its prim description to ‘debug mode’ and click it. It’ll now be in “debug mode” and will chat information on what it’s doing (e.g. trying to eject somebody) whenever a hippoSECURE unit talks to it. (version 1.6 and higher only).
- If you accidentally lose or misplace an Ejector in a sim, you may be able to use the functions in the Tools->Ejectors sub-menu to help find or delete it. (version 1.6 and higher only)
7. Configuring via Notecard Rather Than Menu
Finally, it is possible to configure your hippoSECURE unit using a configuration notecard, if you prefer. This can be useful if you wish to use the same settings in several units, for example.
To do this, replace the “_config” notecard in your hippoSECURE unit with the one you’ll find in your hippoSECURE inventory folder. Then open the hippoSECURE unit’s inventory and double-click on the notecard to edit it and make any changes that you wish.. After making any changes, click your hippoSECURE unit and choose "Reset" from the menu that appears to load the “_config” notecard. (Older versions of hippoSECURE will load any changes as soon as you save the notecard).
|Important Note! |
If turning on networking (either between units or between a unit and a rental box) in the _config card, please ensure the command to turn networking on comes after you’ve defined the channel and any passphrase.
|Power Tip: Separate Configuration Cards When A Connected Rental Box Is Rented (v1.6 and higher only) |
You can choose to have a hippoSECURE unit load a separate configuration notecard when its connected rental box becomes vacant. Simply add a notecard called “_config_rented” to its contents ... it’s as easy that. Useful tip: you may also want to use this feature along with the the RESET AND RELOAD WHEN TENANT LEAVES: Yes configuration command; that would the allow you to have the regular “_config” card automatically load when a tenant leaves, too. (If using the Network Menu -> Security -> Copy Notecards option, you’ll be offered the change to also copy the “_config_rented” card, if one exists.)
Do remember that if you deed your hippoSECURE unit to a group, you may not be able to edit any _config notecard inside it afterwards, so do be careful. Even with a _config notecard inside, you can still use the menus to make configuration changes in the normal way.
There are some special advanced settings you can add to a “_config” notecard ...
- MODE WHEN OWNER IS IN RANGE: <off/black list/all/scan only> (Version 1.5 and higher only)
e.g. MODE WHEN OWNER IS IN RANGE: Scan Only
If you include this command in your hippoSECURE unit’s “_config” notecard, then when you are in scan range of the unit, it will switch from its normal mode to whatever you specify here. This can be very useful for example, you might choose to use a combination of MODE: All and MODE WHEN OWNER IS IN RANGE: Black List to eject everybody when you’re away from home and only named enemies when you’re back at home.
- RESET AND RELOAD WHEN TENANT LEAVES: <Yes/No>
e.g. RESET AND RELOAD WHEN TENANT LEAVES: No
If you’re using your hippoSECURE system in conjunction with a hippoRENT box and have given your tenants full access over the system, you may wish your hippoSECURE unit to reset and reload its _config card settings when a tenant leaves. To do this, turn use RESET AND RELOAD WHEN TENANT LEAVES: Yes. Any settings that the tenant has changed (including white and black lists) will be wiped and the defaults you have specified in the _config card reloaded.
- SWITCH TO MODE ON NEW TENANT: <off/black list/all/scan only> (Version 1.5 and higher only)
e.g. SWITCH TO MODE ON NEW TENANT: Black List
Tells hippoSECURE to change to this mode when a new tenancy is detected on the connected hippoRENT box. This allows for a number of interesting possibilities. For example, if you also added MODE: Off and RESET AND RELOAD WHEN TENANT LEAVES: Yes to the “_config” notecard, then hippoSECURE would power down when there was no tenant and turn itself active when somebody rents useful if you want to have potential customers free to wander around and explore before they rent, if the box is vacant.
- MODE WHEN TENANT LEAVES: <off/black list/all/scan only> (Version 1.6 and higher only)
e.g. MODE WHEN TENANT LEAVES: Scan Only
Use this option to have the hippoSECURE unit’s mode when the connected rental box’s tenancy ends. For example, this might be very useful if you would like prospective tenants to be able to look round an empty property in that scenario, simply use MODE WHEN TENANT LEAVES: Off.
- SENSOR TYPE: <SensorRepeat/Timer>
e.g. SENSOR TYPE: SensorRepeat
This advanced setting governs how your hippoSECURE unit scans. By default, it will use the Second Life llSensorRepeat() command. However, there is a known bug in this Second Life function if the scan area crosses a sim border. Should you find problems on a sim border (e.g. the unit reporting non-existent avatars, or people wildly outside the scan range), use SENSOR TYPE: Timer instead (which, for those who like to know about these things, simply uses llSensor() along with a timer() event to perform its scanning.)
- GENERAL WARNING: <message> (Version 1.5 and higher only)
e.g. GENERAL WARNING: Sorry, <NAME>, but <SIM> <COORDINATES> is a restricted area. Please leave!
Allows you to customize the contents of the warning dialog box shown to people who stray into a protected area. You can use “smart tags” as part of your messages ...
- <NAME> will be replaced with the trespasser’s name
- <SIM> with the name of the sim
- <PARCEL NAME> with the name of the land parcel
- <COORDINATES> with the Second Life map coordinates of the hippoSECURE unit
- <WARNING TIME> with the number of seconds before they are ejected
- BLACKLIST WARNING: <message> (Version 1.5 and higher only)
e.g. BLACKLIST WARNING: <NAME>, you are banned from <SIM> <COORDINATES> and have therefore been removed!
Similar to the above, this command allows you to customize the warning dialog box shown to people on your black list when they are removed from your land.
- AGE WARNING: <message> (Version 1.5 and higher only)
e.g. PAYMENT TYPE WARNING: Sorry, <NAME> but only people who are <AGE LIMIT>. You will be removed in <WARNING TIME> seconds!
Similar to the above, this customizes the warning dialog box shown to people who are removed because you’ve set up a black-list-by-age-filter. You can use the tag <AGE LIMIT> to insert the age limit if you wish (it will be replaced with “less than X days old” or “more than X days old”, depending upon what criteria you have in your black list).
- PAYMENT TYPE WARNING: <message>
e.g. PAYMENT TYPE WARNING: Sorry, <NAME> but you do not have sufficient payment information on file with Second Life to be allowed here. You will be removed in <WARNING TIME> seconds!
Similar to the above, this customizes the warning dialog box shown to people who are removed because you’ve set up a black-list-by-payment-status filter.
- GROUP ACCESS: <Yes/No>
e.g. GROUP ACCESS: Yes
If you set this to “Yes“, then anybody who is a member of the same group that the hippoSECURE unit is set to (and who has that group active) will be allowed access.
- GROUP USE: <Yes/No>
e.g. GROUP USE: Yes
If you set this to “Yes“, then anybody who is a member of the same group that the hippoSECURE unit is set to (and who has that group active) will be able to click the hippoSECURE unit and gain access to its menu functions.
- LOG PEOPLE IGNORED WHEN RUNNING IN BLACK LIST MODE: <Yes/No>
(Version 1.6 and higher only)e.g. LOG PEOPLE IGNORED WHEN RUNNING IN BLACK LIST MODE: Yes
Turn this option on and if you’re logging activity and the mode is set to only eject people on the black list, then casual visitors will also be logged for you, enabling you to see who has visited, even if no action was taken against them
- OFFER GLOBAL MODE CHANGES: <Yes/No>
(Version 1.6 and higher only)e.g. OFFER GLOBAL MODE CHANGES: Yes
When a hippoSECURE unit is networking, you can change the mode (e.g. from “Off” to “Scan Only”) across the whole network at once simply change the mode and hippoSECURE will ask if you wish to apply that change to other units. If you find this feature a distraction, simply add OFFER GLOBAL MODE CHANGES: No to a hippoSECURE unit’s “_config” notecard. (To switch it back on, use OFFER GLOBAL MODE CHANGES: Yes).
- EMAIL ADDRESS: <email address>
(Version 1.6 and higher only)e.g. EMAIL ADDRESS: email@example.com
If you’re using hippoSECURE’s ability to log activity on your land, then you can also have those logs emailed to you. Simply specify your email address in the configuration notecard using this command. You’ll then be able to use the “Email Logs” button under the logs sub-menu. Please note that a large log may take a while to email: it will split across several emails and due to the way Second Life functions, only one email can be sent by the logs script every 20 seconds. The data in a log email is exactly the same as that printed via chat when you use the “List” option in the logs menu you’ll get the SL date and time, the visitor’s name, Second Life key, and what action was taken against them, if any.
- EMAIL LOGS EVERY: <time in hours>
(Version 1.6 and higher only)e.g. EMAIL LOGS EVERY: 24
Further to the command above, you can also tell a hippoSECURE unit to
xYou can easily email the contents of your hippoSECURE unit’s logs, if keeping them, to an email address; simply add EMAIL ADDRESS: <address> to its configuration notecard (e.g. EMAIL ADDRESS: firstname.lastname@example.org send logs every so often by using this command.
|Power User Tip! |
You can instantly copy a ‘_config’ notecard from one hippoSECURE unit to any other units on its network. Simply use the “Copy Notecard” button which will appear on the Network/Security menu once you have intra-unit networking set up correctly and turned on (and a ‘_config’ notecard in the unit!)
8. Logging Visitors
If you’re using version 1.5 or higher of hippoSECURE you can turn on visitor logging. This will cause your unit to record every unique visitor, along with what action was taken were they permitted to pass or removed? Were they on the white list or black list? Visitor logging is turned off by default, as if you’re in a high traffic area and scanning very rapidly, it can be quite laggy. To turn it on, add the following command to your hippoSECURE unit’s “_config” notecard ...
LOG VISITORS: Yes
... then reset the unit. You can now use the “Logs” menu (click your unit, choose “Logs”) to see the contents of your visitor log (as well as to erase it at any point if you wish).
Useful things to note ...
- Your log can hold up to 100 entries. Then earlier records will begin to be deleted.
- If somebody visits more than once on the same day, only one log entry will be recorded for them. If they were permitted to pass, the first time they visited that day will be reported; if they were removed, the latest removal time will be logged.
- Your own visits won’t be recorded in your log. (If you can’t remember when you visited your own land, that needs more caffeine, not a scripted gadget).
- If using hippoSECURE v1.6 or higher, you can also email these logs to yourself, either on demand, or at regular intervals. See the information above on the email configuration notecard commands.
9. Connecting a hippoSECURE unit to a door system
If you’re using v1.5 or higher of hippoSECURE and the door plugin module for hippoRENT (doors must be version 5.2 or higher), you can network the doors to hippoSECURE so that the two systems share a common access list. Any names added to the door’s access list will be copied to hippoSECURE’s white list (and vice versa). To set this up ...
- Turn on hippoSECURE networking as described in section 4 above.
- Add the following command to the door’s “_config” notecard ...
HIPPOSECURE NETWORKING CHANNEL: <channel>
... substituting whatever channel number you chose when turning networking on ...
e.g. HIPPOSECURE NETWORKING CHANNEL: 123456
- Any names you or a tenant now add to the door’s access list will be transmitted to the hippoSECURE unit. Any names added to the hippoSECURE unit’s white list will be transmitted to the door. If you black list anybody who happens to be on the door’s access list, they will be removed.
- A further trick allows you to synchronize not merely additions but removals. Add this command to the door’s “_config” notecard ...
HIPPOSECURE SYNC REMOVALS: Yes
... and anybody you or a tenant remove from the door’s access list will be removed from the hippoSECURE unit’s whitelist and vice versa.
We hope that you enjoy using your hippoSECURE unit and it helps you manage your land security better, whether you’re a private individual or a landlord.
We recommend to all customers that they join the Hippo Technologies Users Group in Second Life. It’s a friendly community and lots of advice, tips and support can often be found by asking nicely!