Modbot Docs
AI

Unusual activity

Alerts when a figure Modbot watches runs far outside your own normal - a burst of joins or flags, a busy instance nobody is watching, a drop in active members.

Insights arrive on a schedule. An alert arrives when something happens: a burst of joins, a run of flags, an instance filling up with nobody watching it, a week with far fewer active members than usual.

An alert is figures, not prose. It says what the figure was, what normal looks like, which stretch of time it covers, and where in Modbot to go and look. If your AI is on, it can also carry one sentence from the model about those figures — but the alert goes out either way.

Like an insight, an alert never names anybody. It counts things. The one alert that suggests an action is Open a second instance, which says an instance is full and has a button to open another.

You set alerts up under Settings → AI → Alerts, which needs the Change settings permission. Everything is off until you turn it on.

What Modbot can watch

WatcherWhat it noticesOver
People joining the groupVRChat group joinsan hour
People joining DiscordDiscord server joinsan hour
New accounts joiningof those joiners, the ones whose VRChat account is less than a month oldan hour
AI flagsflags raised by your AutoMod rulesan hour
Moderation actionsbans, removals, instance kicks, warnings, rejections, and Discord bans, kicks and timeoutsan hour
People leavinggroup and Discord leavesan hour
Instances openinggroup instances being createdan hour
An instance filling upan open instance far busier than your instances usually getnow
Nobody watching a busy instancea busy open instance with no moderator's client in itnow
Fewer active membersthe week just ended against the four weeks beforea week

Group joins and Discord joins are watched separately, because they are different doors.

Active member here means the same as it does on the Discord analytics page: somebody who sent a message or spent time in voice.

How Modbot decides something is unusual

Never against a fixed number. A group of fifty and a group of five thousand have nothing in common except that each knows what its own Tuesday evening looks like.

Modbot compares the stretch just ended with the matching earlier stretches — the same hour of the day on each of the last 14 days, or the four weeks before this one. Normal is the middle of those, and the spread is how far they usually sat from the middle.

A spike has to clear three bars at once:

  • it has to be big enough on its own — five joins, three flags — so a quiet group never alerts on two of anything;
  • it has to be several spreads above normal, and how many is the sensitivity you chose;
  • it has to be at least half again normal, so a big steady number does not alert on a wobble.

A drop works the other way: Fewer active members alerts when the week comes in below a share of normal — half at Low, about two thirds at Normal, three quarters at High.

Modbot says nothing at all until it has enough history to know what normal is: five matching stretches, or three weeks for the weekly watcher.

Nobody watching a busy instance is the one that is not a comparison. It fires on an instance at or above your own normal busiest instance — twice that at Low, half again at Normal, level with it at High — with no moderator's client in it.

Open a second instance

A separate alert, set by two numbers instead of a sensitivity. It tells you an instance is full enough that it is time to open another, and gives staff a button to do it.

Under Settings → AI → Alerts, the Second instance card has two boxes. Leave one empty to leave it off.

  • Alert at people — alert when one open instance of your group holds this many people.
  • Alert at percent of capacity — alert when one holds this share of its world's capacity, as VRChat reports it. A world whose capacity Modbot does not know never reaches a percent; use Alert at people for it.

If you fill in both, whichever line is reached first raises the alert.

An instance alerts once, for its whole life. If it empties and fills again, there is no second alert about the same instance. Nothing here needs AI, and the alert carries no sentence.

In Discord the alert has an Open second instance button. Pressing it opens one more group instance of the same world, with the same group access and region as the full one, and answers you with a Join link. It needs a Modbot account linked to your Discord account and VRChat, with the Manage calendar permission — the one that lets you open an event's instance from Modbot. It uses the same VRChat limit as opening an event's instance: one instance every 5 seconds. If VRChat says to slow down, press the button again a few seconds later; Modbot does not retry on its own.

Only one second instance is opened per alert. A second press, by you or anyone else, gives the same Join link back. Each instance opened this way is written to the event log as Second instance opened, with who pressed.

The alert shows in Modbot with the others, under Unusual activity.

Sensitivity

Each watcher is Off, Low, Normal or High.

  • Low is the quietest: it takes a big, obvious spike.
  • Normal is the middle.
  • High notices more, and will sometimes notice a busy evening.

If a watcher is saying too much, move it down one. If something happened and it said nothing, move it up one.

Quiet time

After an alert, that watcher stays quiet for the quiet time — 6 hours by default — so one busy evening does not fill your channel.

The exception is when it gets much worse: twice as far from normal as the alert that was posted. Then it speaks up again, because a burst that keeps growing is worth hearing about more than once.

The second instance alert has no quiet time: it alerts once per instance.

Where alerts appear

  • In Modbot, as a card at the top of the VRChat analytics page and of Health, showing alerts from the last 24 hours. Each row has Open, which takes you to the thing it is about — the member list filtered to the people who joined in that hour, the Flags page, the Live page, and so on. Reading them needs See analytics.
  • In Discord, if you pick an alerts channel. This can be a different, noisier channel from your insights channel. The bot needs View Channels, Send Messages and Embed Links in it. The card is amber, and shows the figure, what normal is for that hour or day, the stretch of time, and a link to the page the alert came from. The second instance alert shows Alert at in place of the stretch of time, and has the Open second instance button.
  • Anywhere else, through event routes: every alert also writes an Unusual activity event, which a route can send wherever you like.

× on a card hides it. The alert itself is kept, and you can still find it through the event log.

Settings

The Alerts card:

  • Discord channel — where alerts go. Leave it empty to keep them in Modbot only.
  • Quiet time — how long a watcher stays quiet after an alert.
  • AI sentence — whether the model writes one sentence on each alert. Turning it off does not turn alerts off.

The What is watched card has one control per watcher. The Second instance card has the two boxes described above.

Alert sentences are real AI requests and count towards spend under Insights on Limits and spend. They are made like every other AI call: with the feature's time limit, the fallback model when the first one fails, and a row in the call log under Insights, with nobody in Asked by because nobody pressed anything. If AI is off, or that limit is reached, or the model does not answer, alerts still go out — with their figures and no sentence, and the call log says why.

When the checks run

Every 15 minutes. An hour-long stretch ends on the quarter-hour, so an alert reaches you within about 15 minutes of the thing it is about.

Open a second instance is checked every minute, against head counts Modbot updates every 30 seconds.

Fewer active members is checked once a day, because it counts whole days and cannot change inside one.

Modbot is not endorsed by or affiliated with VRChat Inc. or Discord Inc. VRChat is a trademark of VRChat Inc. Discord is a trademark of Discord Inc. SteamVR is a trademark of Valve Corporation. Windows is a trademark of Microsoft Corporation. Docker is a trademark of Docker, Inc. PostgreSQL is a trademark of the PostgreSQL Community Association of Canada. Railway is a trademark of Railway Corp. Other names are trademarks of their respective owners; see Legal. Modbot and its logo are trademarks of the Modbot project. Open source under AGPL-3.0.

On this page