Reviews and repeat offenders
The list of people acted on more than once, the Past actions block on a person, and the Reviews page that asks the team to look when a moderator's pattern seems unusual or a moderation rule flags somebody.
Modbot reads your group's audit log from VRChat, so it knows every kick, warn, ban and removal any moderator has done in VRChat. Two features count what is in that record:
- People acted on more than once, on the Bans page and on each person's popup.
- Reviews, which ask the team to look when one moderator's recent actions seem unusual.
Neither does anything to anybody. They count, and they ask.
What counts as an action
Both features count the same things done to a person:
- kicked from an instance;
- warned;
- banned;
- removed from the group;
- a join request turned away (rejected or blocked).
Unbans are shown but never counted as an action against somebody: lifting a ban is not another strike. Invites, accepted join requests and role changes are not counted either.
A moderator acting on their own account is never counted.
You can change which of those kinds count — see Changing the rules.
One decision counts once
Some single decisions are recorded more than once. Banning somebody who is in one of your group's instances makes VRChat record a ban and an instance kick, a second apart; a ban pressed in Modbot is recorded by Modbot and by VRChat.
Modbot counts that as one action, by the moderator who made it, against the person it was made against. The heavier record is the one that counts, so a ban with a kick beside it counts as a ban and the kick is not counted again. Both are still in the audit log, as one row that opens into both.
Two decisions stay two. A ban, an unban, and a second ban ten minutes later is two actions.
People acted on more than once
On the Bans page, the People acted on more than once tab lists everyone who has been acted on at least twice, by any moderator, most recent action first. Opening the Bans page needs See the audit log; the list itself needs See profiles.
At the top, the rule that decides the status is written out, for example Repeat: 3 or more actions in the last 30d., and when the counts were last rebuilt.
Switch between Everyone and Repeat only. Up to 200 people are listed.
| Column | What it shows |
|---|---|
| Person | Click to open their popup. |
| Status | Once, More than once or Repeat (see below). |
| Actions | All actions against them, ever. |
| Last 30 days | Actions in the last 30 days. |
| Kicks, Warns, Bans, Removed, Turned away | The count of each kind. Kicks are kicks from an instance; Removed is removal from the group. |
| Moderators | How many different moderators acted on them. |
| Last action | What it was, who did it and how long ago. |
The statuses:
- Once: one action, ever.
- More than once: two or more, but not enough recently to count as repeat.
- Repeat: 3 or more actions in the last 30d. The 3 is the default, and can be changed.
Changing the rules
Settings, Moderation, Repeat offenders, for anyone with Change settings.
- Repeat offender after — how many actions in the last 30 days make somebody a repeat offender. Between 2 and 100.
- What counts — which kinds of action count towards it. Every kind counts unless you turn one off. At least one has to stay on.
Turning a kind off does not hide it. Its column still shows what happened; it just does not count towards the status, and the Actions column no longer includes it.
Pressing Save rebuilds every person's counts before it answers, so the Bans page matches the new rule straight away.
VRChat's group audit log does not record instance mutes — instance kicks and instance warns are the two it records — so there is no mute to separate from a kick yet.
Past actions on a person's popup
The same numbers appear as a Past actions block on the Overview tab of a person popup, for anyone with See profiles. For example: Acted on 4 times by 3 different moderators, 2 in the last 30d. followed by the last and first action, a count of each kind, the status and its rule.
If nobody has ever acted on them it says No actions recorded.
How fresh the counts are
The counts are rebuilt from Modbot's records every 15 minutes, and each screen says when that last happened (Counted and a time). Before the first run they say Not counted yet.
They only cover what Modbot has recorded, which starts when Modbot first read VRChat's audit log. Nothing before that is counted.
Reviews
The Reviews page is in the sidebar right after Flags. It needs the Review tickets permission. The number beside Reviews is how many are waiting. While anything is waiting, the browser tab's title starts with the open reviews and open flags you can see added together, as (3) Modbot.
A review is a question, not a finding. Modbot never judges a moderator, never limits what they can do, and never messages them. It writes a plain sentence with the numbers in it, and waits for a person to look.
Review tickets is a separate permission from the moderation ones on purpose: the people being reviewed should not be the people closing their own reviews.
What opens a review
The same run that rebuilds the counts, every 15 minutes, looks for two patterns. The moderator in a review is the VRChat account VRChat's audit log names as having done the action.
Keeps acting on one person. One moderator has acted on the same person 3 or more times in the last 30 days, in at least 2 different places, and no other moderator has ever acted on that person. A "place" is an instance when Modbot knows it, otherwise the world, otherwise the day. Two kicks in one evening in one instance are one place.
If other moderators have acted on the same person, the bar is much higher: 8 or more. That is what keeps the persistent troll everybody removes from looking like a grudge.
Far more actions than the rest of the team. One moderator did 10 or more actions in one day (counted in UTC), and that is at least 4 times the larger of:
- what the next busiest moderator did that day, and
- the team's usual number of actions per moderator per day.
Comparing against the next busiest moderator stops a raid night, when everybody is busy, from opening a review on whoever happened to be busiest. This check does not run at all until the team has at least 7 days with recorded actions, because before that there is no "usual".
"Usual" is actions over the last 90 days, up to yesterday, divided by the days a moderator did anything. Today is left out, so a busy day cannot raise the usual it is compared to.
The numbers in this section are the defaults. There is no screen for changing them yet.
Flagged by a moderation rule. A third kind does not come from detection at all: a flag sent here, either by a rule set to open a review for each flag or by a moderator pressing Open a review on one. The "moderator" in that review is the rule. It shows the rule and version, what was checked, the language, the words or picture that matched and the model's reason.
Reading a review
Switch between Waiting (with a count) and Closed. At the top right: Last checked and a time, or Not checked yet.
Each review shows:
- what kind it is (Keeps acting on one person or Far more actions than the rest of the team), the moderator, and the person when there is one; all click through to popups;
- when it opened, and when its numbers were last updated;
- the sentence, for example Acted on the same person 4 times in the last 30 days, across 3 different instances or days (3 instance kicks, 1 ban). No other moderator has acted on this person.;
- the numbers behind it: Actions, Of which, Different instances or days, Other moderators who acted on them, Looking back, Day (UTC), Next busiest that day, Team's usual per moderator-day, Their usual, and Rule applied;
- Covers and the dates, and a button such as Show the 4 fact ids, which lists the ids of the audit log entries behind the numbers.
If you disagree with the question, you can see exactly how it came to be asked.
Closing a review
Find out what happened
Open the moderator and the person, read their Activity, and ask the moderator if you need to.
Write what you concluded
In What did you conclude?, for example "Asked her; a crasher kept coming back on new accounts." A note is required, up to 2,000 characters.
Press Close review
The review moves to Closed, showing who closed it, when, and the note.
A review that came from a moderation flag has two buttons instead: The rule was right and The rule was wrong. Wrong dismisses the flag, which stops that rule and term flagging that person ever again; right confirms it. Both feed the rule's numbers under Settings, AutoMod.
The note and who closed it are kept with the review and recorded in the audit log. "This was looked at and found fine" is worth keeping as much as the pattern was.
If somebody else closed the same review a moment before you, Modbot says so.
What happens after
- A closed review is never reopened by the same actions. Only actions that happen after it was closed can open a new review about the same moderator and person.
- While a review is open, its numbers keep updating. The same pattern does not open a second review.
What these features cannot see
- Anything VRChat's audit log does not record. Everything here comes from actions done in VRChat.
- Why an action was taken. Kicks and warns have no reason in VRChat's audit log. Bans can have a case file, but the checks do not read case file reasons yet.
Evidence
Attach screenshots and video to a case file, view them, take them off, destroy them, what the audit log records about them, the three evidence permissions, and the upload limits in Settings.
Reports
What members tell the mods with /report or the Report to mods menu in Discord, the Reports page where staff read and close them, who sees who reported, and how long the words are kept.