Watch a region with the Region Monitor
Put the Region Monitor in one object in each region you look after, so Civitas knows who's there and how the region is running without a bot staying in it.
You need permission to manage in-world objects (objects.manage).
The Region Monitor watches one region for your community. It tells Civitas who's in the region, with people and bots told apart, how the region is running (time dilation and frames per second), each time the region restarts, and its parcels. It only sends what changed, and no bot has to stay in the region for it.
Get the script
- Go to In-world objects and press Send me the script on the Region Monitor card.
- A Civitas bot offers you the script in SL, named for your community. Accept it.
- Drop it into an object you own in the region. It starts working straight away.
The script is made for your community and for you. You can copy it into as many objects as you like, but not read it or give it away. Sending it doesn't count toward your community's daily limit.
Put one Region Monitor in each region. The object can be small and hidden anywhere in the region, and while the script is working it shows no hover text. Each object shows under Objects on In-world objects, marked Region Monitor.
One per region
If you put a second Region Monitor in a region that already has one, the second tells you in SL that another one watches the region and stays idle. Its hover text says so. It takes over if the first one stops: when that object is disabled or taken back to inventory, or it hasn't reported for 20 minutes.
What it reports
- Who's there: everyone in the region, looked at every 30 seconds. Avatars SL flags as scripted agents count as bots, apart from people.
- Performance: time dilation and frames per second, averaged over five minutes and sent when they change, and at least every 15 minutes.
- Restarts: when the region last started, which it sends after each restart.
- Parcels: each parcel's name, shape, owner, group, settings and prims. It reads them when it starts, after each restart, once a day, and when a manager asks, by checking which parcel is at each 4 m square of the region. A region with more than 300 parcels isn't read.
The region's estate, its place on the grid and how many avatars it lets in come with it too. Civitas keeps 90 days of performance and how busy each region was.
See what it sees
On In-world objects, click a Region Monitor's object under Objects to see its region: who's there, how it's running, when it last restarted and how many parcels it has. An object whose region hasn't heard from it for 20 minutes shows Not reporting. A second Region Monitor in the same region says that another one reports on it.
- Press Parcels on Estates to see the region's parcels on the Estates page's map, with each one's area, owner and prims (while Estates is on).
- Press Read parcels now after changing parcels (such as splitting or joining them), rather than waiting for the daily read. The parcels show a minute or so later.
If an object shows Not reporting although its Region Monitor is still there, open the object's contents in SL and check that the script is running. A script that runs out of memory stops and shows "Stack-Heap Collision" in SL; the Region Monitor warns you in SL before it gets close. Put a new copy in, from the Region Monitor card.
Keep it up to date
When a newer script is out, the object and its copy show Update available, the Region Monitor card counts the objects that need it, and the script tells its owner in SL. Get a new script and put it in the object instead of the old one.
Turn it off
- To turn off one object, click its name under Objects and press Disable…. Another Region Monitor in the region takes over, if there is one.
- To turn off a copy of the script and every object it's in, press Disable… beside it under Copies sent.
Updated