This chapter is the install guide for a normal WatchTower owner. The goal is to get one terminal rezzed, registered, online, and visible in the dashboard without overwhelming the owner with technical details.
Before you rez the terminal
You need a Second Life location where scripts are allowed to run. The location may be a store, club, rental office, event area, community hub, or managed parcel. If the parcel is group-owned, decide whether the WatchTower object will remain owned by you, owned by the land group, or deeded to the group. Some security and access features require land powers, so installation should match how the land is controlled.
Before setup, confirm these items:
| Requirement | Why it matters |
|---|---|
| You can rez objects | The terminal must be placed in-world. |
| Scripts are allowed | The terminal cannot report data if scripts are disabled. |
| HTTP is allowed | The terminal must contact the FlaroCity API. |
| The object is not set to temp-on-rez | It must remain in-world. |
| The object description is available | The private token is saved as `WTTOKEN:...`. |
| The parcel has the needed land powers | Eject/ban/access features depend on land permissions. |
Recommended object name
Name the terminal after the location it protects. Good names make dashboard review easier.
Examples:
- `WatchTower - Main Store`
- `WatchTower - Club Floor`
- `WatchTower - Rental Region 1`
- `WatchTower - Event Landing Point`
- `WatchTower - Demo Parcel`
Avoid names like Object, Box, New Scripted Prim, or WatchTower Copy 7. Those names make support harder when several terminals exist.
Basic setup steps
- Rez the WatchTower Terminal at the location you want to protect.
- Wait a few seconds for all scripts to initialize.
- Touch the terminal.
- Choose **Turn On** from the menu.
- Wait for the owner message confirming registration.
- Confirm the object description now contains `WTTOKEN:...`.
- Open the dashboard and confirm the location appears.
- Use **Land Now**, **Scan Now**, and **Health** from the menu to test the basic workers.
A successful setup usually shows the terminal as online, sends a heartbeat, sends a land snapshot, sends a small scanner batch, and records health information.
What the token does
The WatchTower token is the private key that connects the in-world object to the correct dashboard account/location. It is stored in the object description as:
WTTOKEN:your-private-token-hereThe token should not be posted in public chat, sent to customers, displayed on signs, or included in screenshots. If the token is copied into another object, that object may try to report as the same terminal. If the token is lost, reset, or cleared, worker scripts should stop until the terminal is registered again.
What happens when Turn On is clicked
When **Turn On** is clicked, the Register HTTP script sends a small registration payload. That payload identifies the object, owner, region, parcel, position, and script version. The FlaroCity API returns a private token. The Token Reader saves it into the object description and broadcasts it to all worker scripts by link message.
After that, the workers begin sending safe updates through bounded queues. The workers do not need the owner to paste a setup code unless the dashboard chooses to require manual claiming.
First-hour checklist
During the first hour after installation, check these items:
| Check | Good result |
|---|---|
| Hover text | Shows WatchTower online or healthy status. |
| Dashboard location | Shows the right region and parcel. |
| Land snapshot | Shows parcel name, region name, SLURL, region FPS, time dilation, and counts. |
| Scanner | Shows a few avatars at a time instead of trying to send everyone at once. |
| Health | Shows free memory and script health messages. |
| Billing status | Shows current plan, add-ons, and location count. |
| Duplicate locations | No unwanted duplicate from old test tokens. |
Safe reset procedure
Use **Reset Token** only when the terminal needs to be re-registered or moved to a new owner/account. Resetting clears the local token, empties queues, stops worker scripts, and requires **Turn On** again.
Recommended reset steps:
- Open the dashboard and note the old terminal/location name.
- Touch the terminal and choose **Reset Token**.
- Confirm hover status changes to offline.
- Touch again and choose **Turn On**.
- Confirm the dashboard either updates the existing location or creates a new pending location for review.
- Remove stale duplicates from the dashboard if needed.
Moving the terminal
If the terminal is moved within the same parcel, the next land snapshot should update the position. If it is moved to another region or parcel, the dashboard may treat it as a new location or require review depending on billing and matching rules. Owners with limited plans should verify they are not accidentally over the location limit.
Common setup mistakes
**The object says offline after Turn On.** The API may not have returned a token, HTTP may be blocked, the site may be down, or the object may have lost script state. Check owner chat for the exact error.
**The dashboard shows the wrong parcel.** Move the terminal to the intended parcel and request **Land Now**. In Second Life, parcel boundaries can be close together, so the exact terminal position matters.
**The scanner seems slow.** This is intentional. The safe scanner sends only a small batch per cycle so the object does not build huge lists or crash under busy-region conditions.
**Eject/ban does not work.** The object may not have land powers. Confirm parcel ownership, group role powers, object ownership, and whether the action is allowed on that land.