Members and bans
The member list and the Bans page, how fresh the lists are, and kicking, banning and unbanning.
Modbot keeps its own copy of your group's member list and ban list, read from VRChat. The Members view of the People page and the Bans page show those copies. Nothing on either is typed in by hand or guessed. When Modbot does not know something yet, the page says so.
What Modbot can do from these pages
Modbot can kick, ban and unban, each behind its own permission. See Kicking, banning and unbanning. It cannot warn anybody: the Warn permission is on the Roles page but nothing reads it yet, and neither does Act on many at once. Moderation done in VRChat itself still arrives here, because Modbot reads VRChat's group audit log.
What "synced" means
Both lists start with a line like 4,790 members · Synced 12m ago. Syncing is Modbot reading a whole list from VRChat, one page of up to 100 people at a time, from start to finish. When it gets to the end, it rests, then starts again from the top. While it is reading, the line says Syncing... in place of the time.
So the lists show what the last complete read found, and so does the count. Synced 12m ago means the last complete read finished 12 minutes ago. Anything that changed in VRChat after that shows up after the next read.
These are the default timings. You can see the ones your Modbot uses under Settings, Server, Sync timings, on the Member list and Ban list cards. They cannot be changed from the app.
| List | Time between pages | Rest between rounds |
|---|---|---|
| Member list | 2 seconds | 15 minutes |
| Ban list | 3.5 seconds | 30 minutes |
For example, a group of 5,000 members is 50 pages, which takes about 100 seconds to read. With the 15-minute rest, a change on VRChat's side normally shows in the Members view within about 17 minutes.
The pages do not refresh by themselves. To fetch the list again, change a filter, move to another page, or reload the browser tab.
The first read. Until Modbot has read a list all the way through once, the page shows a warning: Reading the member list for the first time. (or The member list has not been read yet.). What you see until then is only the pages read so far, not the whole group.
Members
Members is the People page with the Membership filter set to
Members. Open it from the Members tab on the VRChat page, with g then m, or by searching
for Members (Ctrl+K). The sidebar lights People while it is open. Set Membership to
People who left for the people a complete read no longer listed.
It needs See profiles, or See members on its own. With only See members you see members and people who left, without the Discord column.
Above the list: how many members the last complete read found, and when it was synced (or Syncing... while a read is running).
The columns are Person, Discord, Roles, Joined, Last seen by Modbot and First seen, with Left in place of First seen for people who left. The last column on each row opens a menu with Kick and Ban; see Kicking, banning and unbanning. The search, the filters, the sorting and the keyboard are People's: see People.
The Members page was a page of its own until September 2026. Its old address, /members, and every
link to it still work: they open this view, with the filters the link carried.
Bans
The Bans page needs See the audit log.
There are three tabs: the two ban lists, VRChat and Discord, and People acted on more than once.
VRChat
Everyone VRChat says is banned from your group right now, however long ago the ban was issued. This is the list to check before deciding somebody is not banned in VRChat.
Above it: how many bans the last complete read found, and when it was synced.
| Control | Options |
|---|---|
| Search by name or id | As on People. |
| Status | Still banned, Bans that were lifted or Both. |
Bans that were lifted are bans a complete read no longer listed.
The columns are Person, Banned on, Seen by Modbot, Lifted (when you are looking at lifted bans), and Case file (with See profiles). 50 bans a page, with the page numbers at the bottom and the page you are on in the address. With Unban, each standing ban also has an Unban button.
Discord
Everyone banned from your Discord server. The Bans link under the Discord page's header opens this tab, with the server's header above it.
The bot reads the whole list from Discord when it signs in and again once a day. A ban or unban in Discord changes the list straight away. Reading the list needs the Ban Members or View Audit Log permission for the bot's role in Discord; without either the tab says Cannot read the Discord ban list: the bot needs Ban Members or View Audit Log. and shows only the bans the bot saw happen.
Search and Status work as on the VRChat tab. The columns are Person, Reason (the reason given in Discord, when there was one), Banned on, Seen by Modbot and Lifted (when you are looking at lifted bans). Discord's list has no dates, so a ban that was already there when the bot first read the list has no Banned on. Click a row to open the person popup.
People acted on more than once
Everyone who has been kicked, warned, banned, removed from the group or turned away more than once. See Reviews and repeat offenders.
Kicking, banning and unbanning
Modbot can do three things to a person in your VRChat group, each behind its own permission:
| Action | Needs | Where |
|---|---|---|
| Kick | Kick | The person popup, and the row menu in the Members view. |
| Ban | Ban | The person popup, wherever it is opened from, and the row menu in the Members and People who left views. |
| Unban | Unban | The person popup, and the Bans page. |
Somebody who is already banned is offered Unban instead of Ban.
Kick and Ban are also buttons under the bot's cards in Discord and on Look up in Modbot, with the same permissions, reasons and confirmation. See Acting from Discord.
Who each action works on
Ban works on anybody, whether or not they are in your group. You do not have to wait for somebody to join before you can keep them out. If you have heard about a person from another group, from a Discord message or from a flag, open them and ban them: VRChat bans an account, not a membership. Somebody Modbot has never seen before is added to its records by the ban, and their name and picture appear once the profile refresh reaches them.
The other two only make sense in one direction:
- Kick is offered only to somebody the member list says is in the group. There is nothing to remove anybody else from, and VRChat answers a kick of somebody who is not in the group with They are not in the group.
- Unban is offered only against a ban that stands. VRChat answers an unban of somebody who is not banned with They are not banned.
Every action opens a confirmation naming the person, with the reasons from the group's reason list that are ticked for that action, and a note. A ban offers the ban reasons; an unban asks Why lift the ban? and offers its own reasons, such as Mistake, Appeal upheld and Time served.
A reason is required on a ban. On a kick or an unban it is optional, unless your group has switched on Require a reason on kicks, unbans and rejected join requests in Settings, Moderation. A reason that needs a written reason, such as Other, needs the note filled in whichever action it is picked on.
Modbot asks VRChat, waits, and then tells you what happened. If VRChat refuses, the screen says what VRChat said and nothing is recorded as done — there is no case where Modbot shows a ban that did not happen. A kick or a ban marks the person as gone from the member list straight away, and a ban adds them to the ban list; the next sweep confirms it.
A ban also writes its case file from the reason and the note, so the ban is written up at the moment it is made rather than chased up afterwards. Once the ban is done, the confirmation offers Open the case file, to add screenshots or more detail straight away.
An unban shows the person's case file above the reasons, when there is one for the ban being lifted, so you can read why they were banned before you lift it. Once the unban is done, the case file records that the ban was lifted, when, by whom and why: its page gets a Why the ban was lifted section beside Why they were banned, and nothing it said about the ban changes. If the case file could not be updated, the confirmation says so; the unban stands either way.
Only the person's newest case file is marked, and only while its ban stands. A ban that was lifted in VRChat itself is not tied to its case file, because VRChat does not say which ban an unban was for.
When Discord is set up and the person has linked their accounts, a ban or unban made here is made on their Discord account too, without any ban sync switch. The confirmation says Also banned in Discord., or says what Discord refused. The group ban stands either way. An unban that VRChat answers with They are not banned still lifts the ban on their Discord account.
Pressing the button twice does one thing. Each confirmation carries a key, and Modbot refuses a second action under the same key and shows you the first one's answer.
Modbot will not act on the VRChat account it signs in as.
Who banned somebody, and why
- The Ban list knows who is banned, but not who banned them.
- A ban made from Modbot knows who decided it: VRChat records every action Modbot takes as Modbot's own account, so the moderator's name lives in Modbot's audit log and nowhere else.
- The audit log knows who banned them, for every ban Modbot saw happen. It reaches back only as far as VRChat's own audit log went when Modbot first synced.
- None of them knows why. VRChat's audit log has nowhere to put a reason, so your group writes one itself in a case file.
How joins, leaves and bans are recorded
When somebody joins, leaves, gets a role, or is banned or unbanned, Modbot adds it to the audit log. Most of the time that entry comes from VRChat's own audit log, which says exactly who did it and when, and shows VRChat as its source.
The sweeps are a backup. If VRChat's audit log missed a change, the next sweep notices the difference and records it with Sync as its source and no "who", because a list cannot say who changed it. A sweep waits a couple of minutes for the audit log first, so the same change is not recorded twice.