Profiles
What Modbot stores about a VRChat user, how and how often it is refreshed, and how the 18+ verified mark works.
Modbot keeps a copy of the public VRChat profile of everyone it comes across, so moderators can see who somebody is without leaving Modbot, and so there is a record of what a profile said before it changed. You see it at the top of the person popup.
Reading profiles needs See profiles.
Who gets a profile
Anyone Modbot sees, including:
- everyone on the member list and the ban list;
- anyone who joins, leaves, is banned, kicked, warned, given a role or turned away, and the moderator who did it;
- anyone a moderator's companion sees in an instance.
What is stored
The profile as VRChat returns it. The left side of the popup shows:
- banner, picture, display name and pronouns;
- a row of badges read from VRChat's tags and the platform they last used (see Badges);
- the group they represent, with its icon;
- how old the stored profile is;
- the 18+ verified mark, and what VRChat shows about age verification.
The Profile section at the top of the popup's Overview tab shows the rest:
- status line and bio;
- Joined VRChat;
- Last seen by Modbot: the latest time Modbot saw this person in anything it recorded;
- the tags that have no badge, behind 12 more tags (or however many). Press it to see them as VRChat sent them; Hide tags puts them away.
Badges
VRChat marks an account with tags, and Modbot turns the ones that mean something into a badge rather than making you read the tag:
| Badge | From |
|---|---|
| The trust rank (see Trust ranks) | the system_trust_* tags |
| VRC+, in gold | system_supporter: an active VRChat Plus subscription |
| PC, Android or iOS | the platform they last used. Anything else VRChat sends is shown as sent. |
| VRChat staff | the admin_* tags |
| Nuisance | system_troll or system_probable_troll. When the trust rank already says Nuisance, the badge is not shown twice. |
| Early adopter | system_early_adopter |
| One badge per language, such as English or Japanese | the language_* tags. A language Modbot has no name for shows its code. |
The 18+ mark is a badge of its own beside the name, so the age tags are not repeated here. Every tag not in this table is behind the more tags control on the Overview tab.
Modbot keeps everything else VRChat returns too, except these, which are dropped before anything is saved:
- where the person is right now and where they are travelling to, because that can contain the secret part of an instance address;
- the private note Modbot's own VRChat account may have on them;
- the friend key.
Pictures, banners and icons are fetched from VRChat's servers by Modbot's own server each time they are shown, because VRChat refuses a browser that asks for them directly. Modbot does not keep a copy of the image.
When a watched part of the profile changes (name, bio, status, pronouns, pictures, tags, trust rank, join date or age verification), Modbot writes an entry to the audit log. The person's Activity tab shows those entries, so you can see what a bio said last week.
Trust ranks
VRChat gives every account a trust rank, and Modbot reads it from the tags. It is shown as a small coloured dot and the rank's name beside a person wherever one is listed: the member list, the ban list, the person popup, the Live page, the audit log and the companion overlay.
| Rank | Colour |
|---|---|
| Visitor | grey |
| New User | blue |
| User | green |
| Known User | orange |
| Trusted User | purple |
| Legend | gold. A rank VRChat retired in 2018; a few old accounts may still carry it |
| Nuisance | dark red. VRChat has marked the account as a troll, or as probably one |
| VRChat Team | red. VRChat staff |
The colours are VRChat's own, the ones its nameplates use. Nuisance and VRChat Team take the place of whatever rank the account also holds, because that is the word a moderator needs to see.
The rank comes from the user details read, so it is as fresh as the tags: read once when Modbot first meets someone, then once a week. A person Modbot has not read yet shows no rank rather than a guessed one. A change of rank is written to the audit log like any other profile change.
How profiles are refreshed
VRChat answers two different questions about a person, and they do not return the same things:
| Public profile | User details | |
|---|---|---|
| What it gives | Name, bio, pronouns, age verification | Status line, pictures, Joined VRChat, tags, Last platform |
| How often | On the queue below | Once when Modbot first meets someone, then once a week |
The public profile is the one Modbot reads often, because it carries what moderators look at. The user details barely change, so reading them once a week is enough.
VRChat hands out profiles one person per request, so Modbot works through a queue. At most 3.5 requests a second go to VRChat for each of the two, and the queue is ordered like this:
- People a companion has just seen in an instance.
- People a moderator has just opened in Modbot.
- People who just did something Modbot recorded (in the last 30 minutes).
- The oldest profiles, once they are more than 6 hours old.
- People Modbot has never fetched.
These are the defaults. Some other rules protect the queue:
- A profile fetched in the last 30 seconds is not fetched again just because somebody opened it.
- If a refresh failed, that person is left alone for 30 minutes.
- If VRChat says the account does not exist, Modbot waits a week before asking again.
Who is refreshed on a schedule
Steps 4 and 5 — the two that go by the clock rather than by something that just happened — cover your group's members, and anybody else Modbot has seen in the last 30 days. Nobody else.
Modbot keeps a record of everyone it has ever come across, and most of them are strangers who stood in one of your instances once and never came back. Refreshing all of them every six hours would spend most of what VRChat allows Modbot on people nobody is looking at, instead of on your own members.
Nobody is unreachable, and nothing is deleted. Steps 1 and 2 are unchanged: the moment a companion sees somebody in an instance, or a moderator opens them in Modbot, they are fetched — however many years it has been. And somebody who comes back has been seen again, so they are back inside the 30 days.
What you give up is that the stored profile of somebody nobody has looked at for a long time is old, and says so. Open them and it is refreshed while you look at it. See People.
Every profile says how old it is
The line under the badges always says Last refreshed and how long ago. When the profile is older than 6 hours it adds stale — older than 6 hours. A bio from an hour ago and a bio from last week are different claims, and the popup never shows one without saying which it is.
When you open a person, Modbot shows what it has straight away and asks for a fresh copy. refreshing… appears while it waits, and the profile updates when the new copy arrives. If the refresh cannot happen, the line says Couldn't refresh: and the reason (for example, VRChat is limiting Modbot's requests) and keeps showing what it has. After a minute of waiting it says Refresh still waiting.
Other lines you may see:
| Line | Meaning |
|---|---|
| Never refreshed | Modbot knows the id but has not fetched the profile yet. |
| Profile not fetched yet. | The same, in place of the profile. |
| Not seen before. | Modbot has no record of this id at all. |
| No VRChat account with this id as of a date | VRChat said the account does not exist. Modbot keeps the last profile it saw, and the person's history still mentions them. |
This line only appears when both of VRChat's answers say the account does not exist. If one of them still knows the person, Modbot goes on showing them normally.
The 18+ verified mark
VRChat lets people choose whether their age verification is visible. Somebody who showed as 18+ yesterday can hide it today, and to anyone who looks them up they then appear unverified.
In the person popup the mark is a badge beside the name: 18+ verified in green, or Not seen as 18+ verified in grey. The two are different states and not the same claim, so they always read as different words.
The rest of what Modbot knows about the mark is in a card beside the badge. Hover the badge to open
it, tap it on a touch screen, or press Enter or Space with the badge selected — which also moves
you into the card, so Tab reaches Clear flag and Esc closes the card and puts you back on
the badge.
Modbot treats verification as something it has seen, not something it checks again:
- A refresh can set the mark and can never clear it. The first time any refresh sees the person as 18+ verified, the mark is set and the card says First seen on VRChat and the date. Hiding the badge in VRChat later changes nothing.
- The card shows both sides. VRChat shows this person as gives what VRChat said at the last
refresh (for example
18+orhidden). When the two disagree, that is the point: hidden is not the same as unverified. - Only a moderator can clear it. Anyone with Edit 18+ verified sees a Clear flag button in the card on a marked person, and Mark 18+ verified on an unmarked one. Mark 18+ verified asks Badge or Photo ID and runs the whole 18+ check: the mark, the roles you chose and a log of the method, the date and who did it. Clear flag asks for a reason and changes no roles.
The 18+ mark on the People page, its Members view included, and in case files is this same mark. 18+ verified is also a filter there.
Changing the mark by hand
Open the person
Click their name anywhere to open the person popup.
Open the 18+ badge, and press Clear flag or Mark 18+ verified
Hover the badge beside their name, tap it, or select it and press Enter. The button is in the
card. You need Edit 18+ verified.
Pick how, or say why
To mark someone, press Badge or Photo ID: that runs the 18+ check at once. To clear the mark, type a Reason (up to 500 characters) and press Clear flag again. The reason is optional but worth writing: it is kept with the change.
The card then says Set by or Cleared by your username and the date, and after a check, what it did and what it could not do. The change is written to the audit log against your account, with the reason.
If you clear the mark and a later refresh sees the person as 18+ verified again, the mark is set again. A new sighting is new evidence.
Common problems
The card keeps saying Couldn't refresh. Modbot's VRChat account may be rate limited or not signed in. Check the Health page. The stored profile stays usable in the meantime.
A big group has many ids without names. After Modbot is first set up, it has to fetch every profile one at a time. At 3.5 a second, a group of 8,000 takes about 40 minutes, and larger groups take hours.