FlaroCity WatchTower

Feature System

A complete owner-control system for Second Life stores, clubs, parcels, rentals, communities, and private regions that unites reliable live awareness, owner tools, subscription coverage, and permission-safe security workflows.

Device

WatchTower Terminal

The main in-world device connects each protected location to the dashboard.

Data

Live Owner Signals

Signals are designed for owner awareness: machines, locations, visitors, events, and health.

Safety

Permission-Safe

Actions and logs respect Second Life permissions and owner land powers.

Roles

Dashboard + Roles

Owner accounts can unlock dashboard tools, staff workflows, and location-scoped access.

Core Features
Core

WatchTower Terminal

The main in-world device for each protected location. It registers with the website and sends supported land, visitor, health, and event data.

Setup

Turn On Registration

A new terminal starts offline, uses a private setup key, connects to the correct account, and unlocks after heartbeat.

Queue

Safe HTTP Queue

Events are queued and sent on a safe 5-7 second target without spamming Second Life HTTP.

Health

Script + Lag Health

Reports script version, online state, region FPS, time dilation, lag score, capacity, and last-seen timestamps.

Land

Land Snapshot

Reports region, parcel, avatar counts, maturity, SLURL, and map tile details where available.

Map

Live Region Map

Shows the newest scanner window with parcel-present and region-only avatar dots.

Owner Dashboard
Dashboard

Owner Command Center

Live overview with freshness labels, machine count, locations, avatar counts, live signal, and map panel.

Ops

Ops Center

Fast operations view for machine count, avatar count, refresh rate, queue target, and live avatar signal.

People

People Online

Display name, username, parcel or region presence, position, distance, and last-seen information.

Machines

Machine Table

Tracks terminal and payment station status, script version, location, type, and last-seen time.

Locations

Location Intelligence

View each registered place, parcel, region, traffic counts, and land snapshot data.

Tickets

Support Tickets

Logged-in customers can open private tickets and staff can manage requests from the dashboard.

Security & Control
Security

WatchTower Block List

Store a UUID on the website as Block Here or Block Everywhere. A fresh protected-land detection queues the verified eject path, with deduplication and audit history.

Safety

Verified Warn & Kick

Warn sends a private message; Kick uses the verified land-eject action. Both require a fresh eligible WatchTower and the necessary Second Life land authority.

Gate

Access Gate

Optional Second Life account-age policy with 15- to 360-day thresholds, a configurable warning, owner/manager exemptions, audit logging, and eject after the warning window.

Staff

Staff Role Manager

Optional staff tools for role organization and staff-aware workflows.

Tags

Tags + Avatar Watch

Tag avatars as staff, VIP, friend, watchlist, blocked, customer, vendor, or custom labels.

Friends

Friends Tracking

Track approved Second Life UUIDs, current online state, and server-calculated daily, weekly, and monthly online history.

History

Extended History

Optional longer-history views for searchable operational records.

Discord

Discord Alerts

Optional webhook alert routing for selected WatchTower events. Webhooks must remain private.

Relay

Chat Relay

Optional chat and event relay for selected messages with owner-approved filters and throttles.

Branding

Custom Branding

Optional branding controls for larger locations, venues, estates, and networks.

Owner Workflow

Setup Flow

  1. Place the WatchTower Terminal on the correct parcel.
  2. Use Turn On and connect the terminal to the dashboard account.
  3. Confirm online status and last heartbeat.
  4. Run Land Now and Scan Now for the first live data check.
  5. Review token safety before sharing screenshots.

Daily Use Flow

  1. Open the dashboard and confirm freshness labels.
  2. Review land, region, and visitor signals.
  3. Check machine status, payment records, and support tickets.
  4. Use Warn/Kick for an immediate response or add a local/global WatchTower Block rule for future detections.
  5. Open a private support ticket for billing or terminal issues.