Setting up the bot
Create a Discord bot, switch on the intents it needs, invite it to your server and connect it to Modbot.
Modbot can run a Discord bot for your community's server. Once it is connected it:
- posts events to the Discord channels you choose (Event channels);
- announces your group's open instances in a channel (Instance announcements);
- lets members link their Discord and VRChat accounts, and gives linked members a role (Account linking);
- keeps a copy of the server's messages, members and voice time, for the Discord members list and the Discord analytics page (Messages and analytics);
- answers five slash commands, and a sixth for members when you switch it on (see Slash commands);
- lets moderators look people up, write notes, and kick, ban or answer join requests from right-click menus and buttons under cards (Acting from Discord).
The bot is optional. Until you give Modbot a token and a server id, the bot does not start and the rest of Modbot works as normal.
You need the Change settings permission to set the bot up.
Create the application
- Open the Discord Developer Portal and click New Application. Any name works; "Modbot" is fine.
- Open Bot and click Reset Token. Copy the token and keep it somewhere safe for a moment. Discord shows it only once.
Switch on the privileged intents
An intent is a kind of update the bot asks Discord to send it. Most are open to every bot. Two of the ones Modbot asks for are privileged, which means you have to switch them on yourself.
Still under Bot, find Privileged Gateway Intents and switch on:
- Server Members Intent
- Message Content Intent
Leave Presence Intent off. Modbot does not ask for it.
Invite the bot to your server
The easiest way is the Bot invite link Modbot builds for you. It appears on the Account linking card under Settings → Discord once you have saved the Client id there (the Developer Portal shows the client id under OAuth2). It asks for exactly the permissions the features you have set up need. See Account linking if you want to fill in that card now.
You can also build the link yourself under OAuth2 → URL Generator:
- Scopes: bot and applications.commands. Without applications.commands the bot connects, but no slash commands appear.
- Bot permissions: see Permissions the bot needs below.
Open the link, pick your server and confirm. Do not give the bot Administrator.
Find your server id
In Discord, turn on Developer Mode (User Settings → Advanced). Then right-click your server's icon and choose Copy Server ID.
Enter the token and server id in Modbot
You can do this in the setup wizard or later in Settings.
- In the setup wizard, the step Public address, Discord and email has a Discord bot section with Bot token and Server ID.
- In Settings, open Settings → Discord. On the Bot card, fill in Bot token and Server id, then press Save.
The token is stored encrypted and is never shown again. Once one is saved, the Bot line on the card says Token stored. When you change something else later, leave Bot token empty: an empty field keeps the token you already have.
Also set a Public address under Settings → Server. Modbot builds every link it sends to Discord from that address and nothing else. Without it, event posts have no link back to Modbot, and account linking cannot work.
Modbot looks at its Discord settings every ten seconds, so the bot connects within a few seconds of saving. Nothing needs restarting, now or when you change these settings later.
Intents the bot asks for
These are all the intents Modbot requests, and what each one is for.
| Intent | Switch in the Developer Portal | What Modbot uses it for |
|---|---|---|
| Servers | none | The server's name, channels and roles, and slash commands. |
| Server messages | none | Messages as they are sent, edited and deleted. |
| Message Content Intent | yes | The text of those messages. |
| Server Members Intent | yes | The member list, joins and leaves, nickname and role changes, timeouts, and the message that asks new joiners to link their accounts. |
| Voice states | none | Who joins, leaves or moves between voice channels, for voice time. |
| Bans and moderation | none | Bans and unbans, and new entries in the server's audit log as they happen. |
| Server invites | none | Which invite each new member used, and invites being made or deleted (Invites). |
If a privileged intent is off
Discord refuses the whole connection when a bot asks for a privileged intent that is switched off, without saying which one. Modbot works out which ones are off, then connects again without them, so posting events and the slash commands keep working.
While that is happening, the Discord bot card on the Health page shows Intents off in the Developer Portal: followed by the switches to turn on.
What you lose without each one:
- Without Message Content Intent, messages are still stored, but with no text.
- Without Server Members Intent, Modbot does not read the member list or see people join and leave, and new joiners are not asked to link their accounts.
After you switch an intent on, Modbot asks for it again the next time Modbot restarts, or when you change the Bot token, the Server id, or the Prompt new joiners to link their VRChat account switch.
Permissions the bot needs
These are Discord permissions. You give them when you invite the bot, or later in your server's role and channel settings.
| Permission | Needed for |
|---|---|
| View Channels | Everything the bot reads or posts. |
| Send Messages | Event posts, instance announcements, calendar posts, insights, member milestone posts, new staff reminders, and the backup channel for account linking. |
| Embed Links | Event posts, instance announcements, insights, member milestone posts and new staff reminders, which are sent as cards. |
| Attach Files | Pictures on cards (when Modbot fetches VRChat pictures) and on Marketing posts, which are sent as files. |
| Read Message History | Reading back each channel's older messages, and updating instance announcement cards. |
| View Audit Log | Knowing who banned, kicked, timed out or changed somebody's roles, and catching up on what happened while the bot was offline. |
| Manage Roles | Only if you turn on Ko-fi or Patreon supporters, set a Linked role or an 18+ role for account linking, turn on role sync or lists that give roles, choose a Regular role for member milestones, or turn on the join gate. The bot's own role must also sit above the roles it gives or changes, and the gate's Member role. Also to put a role's permissions, or a channel's settings for roles, back from a server snapshot (Allow restore is on). |
| Ban Members | Only if you copy group bans into Discord (ban sync), or ban a Discord member from Modbot (Ban in the web app, or /ban). Reading the server's ban list needs this or View Audit Log. The invite link asks for it only when ban sync copies bans as bans. |
| Kick Members | Only if ban sync copies bans as removals, you remove a Discord member from Modbot (Remove from Discord, or /kick), or the join gate removes people who do not finish (Remove after is not Never). |
| Manage Server | Only if you turn on invite tracking, which reads the server's invites and how often each was used; and if the join gate may pause your server's invites (Allow pausing invites), pausing them. The invite link Modbot builds asks for it once either is on. |
| Create Invite | Only to make invites from a list of names on the Invites tab, which needs invite tracking on. The invite link Modbot builds asks for it once invite tracking is on. |
| Manage Channels | Only to delete a ticket after an 18+ check (Delete the ticket after is on). The invite link Modbot builds does not ask for it. |
| Create Events and Manage Events | Both, only if a calendar event has Discord event ticked. The invite link Modbot builds does not ask for them. |
| Create Public Threads | Only if you turn on event recaps, which start a photo thread on each recap. The invite link Modbot builds asks for it once they are on. |
| Add Reactions | Only for a giveaway people react to. The invite link Modbot builds does not ask for it. |
| Manage Messages and Timeout Members | Only if you set AutoMod rules to delete messages or time people out. The invite link Modbot builds does not ask for these. |
The Bot invite link asks for View Channels, Send Messages, Embed Links, Attach Files, Read Message History and View Audit Log. It adds Manage Roles once Ko-fi or Patreon supporters is on, a linked role, 18+ role or member milestones Regular role is saved, role sync is on, the join gate is turned on or Allow restore is on for server snapshots, Ban Members or Kick Members once ban sync copies bans into Discord, Kick Members once the join gate removes people, Manage Server once invite tracking is on or the gate may pause invites, Create Invite once invite tracking is on, and Create Public Threads once event recaps are on. If you turn on a feature later that needs more, open the link again to give the bot the new permission.
Whenever you pick a channel in Settings → Discord, a channel where the bot lacks a permission
that setting needs is marked with what is missing, for example Missing Send Messages, Embed Links.
Fix it in Discord's channel settings, or pick another channel. The channel and role lists come from
the bot, so they are empty until it has connected once.
Checking that it is connected
Open Health from the Discord row at the bottom of the sidebar. It needs See the operational log. The Discord bot card shows one of these:
| State | Meaning |
|---|---|
| not set up | No token or no server id is saved. This is not a fault. |
| connecting | Signing in to Discord. |
| working | Connected. It also shows how long it has been connected and how many commands were registered: the slash commands and the right-click menus. |
| reconnecting | The connection dropped and Modbot is getting it back. This usually clears within a minute. |
| stopped — needs you | Discord refused to let the bot sign in, usually because the token is wrong. The bot waits until you change the settings. |
The card also shows how many posts have gone to Discord since Modbot last started, each event channel with a problem, how far reading back message history has got, and the last problem the bot ran into. See Checking a deployment for the rest of that page.
You can also run /modbot in Discord.
Slash commands
The bot registers its commands on your server only. Every reply is visible only to the person who
ran the command, except /events, which answers in public unless the member asks otherwise. One
Discord bot can serve several Modbots: each one answers only in its own server.
| Command | What it does | Who can use it |
|---|---|---|
/lookup user: discord: | Looks up one person in what Modbot has stored. Fill in one of the two: user takes a VRChat display name or id, and suggests names from Modbot's records as you type; discord takes a member picked from Discord's list. If the person linked their accounts, the reply covers both. It shows their VRChat profile as VRChat shows it — their name, their picture, their banner, and the group they represent — with whether they have been seen as 18+ verified and when the profile was last refreshed; their Discord account; whether they are banned in the group and on Discord (with the reason Discord holds), or timed out on Discord; how many bans, kicks and warns in the group; how many bans, kicks and timeouts on Discord; how many times Modbot's rules flagged them; and their latest moderation events, with the reason where there is one. Notes are included for people with See the audit log, and join requests for people with See join requests. Somebody known only on Discord gets a reply headed by their Discord name and picture. Nothing is fetched from VRChat or Discord. If several VRChat names match, it lists them with their ids so you can run it again with one. | See profiles |
/recent count: | The latest moderation events, in the group and on Discord, newest first. Every name opens that person in Modbot. count is 1 to 25; 10 if you leave it out. | See the audit log |
/modbot | Whether the bot is connected, whether any channel is set to receive events, and the web app's address. | Anyone who connected Discord to their Modbot account |
/note text: member: vrchat: | Writes a note about one person, the same note as in the web app. text is 1 to 2,000 characters. Fill in one of the other two: member takes a member picked from Discord's list, and vrchat takes a VRChat display name or id and suggests names from Modbot's records as you type. The reply, seen only by you, is "Note saved." with an Open in Modbot button on their profile. If several VRChat names match, it lists them with their ids so you can run it again with one. Without See profiles, vrchat takes an exact id only: no names are suggested or searched, and no reply names the person. | Write notes, and a VRChat account linked to your Modbot account |
/watch reason: for: member: vrchat: follow-up: | Starts watching one person, the same watch as the Watch button in the web app. reason is 1 to 200 characters. for is 1 day, 1 week, 30 days or Until stopped. follow-up is None, Tomorrow or In a week, and is optional. Fill in one of member and vrchat, as for /note. The reply, seen only by you, says who you are watching and until when, with an Open in Modbot button. If somebody is already watching that person it says so. Names work as for /note. | Write notes, and a VRChat account linked to your Modbot account |
/live | The group's open instances right now, one card each: the world, how many people are in (such as 12/40), and when it opened. Names, up to 20 and then "and N more", appear only while a moderator's Companion App is watching that instance, the same rule as the Live page; otherwise you see the count only. No flags and no watched tags. An Open Live button opens the Live page. Seen only by you. | See live instances |
/ban member: vrchat: | Bans one person, with the same meaning as Ban in the web app. Fill in one of the two: member takes a member picked from Discord's list, and vrchat takes a VRChat display name or id and suggests names from Modbot's records as you type. A VRChat person, or a member who has linked their accounts, is banned from the VRChat group, and their linked Discord account is banned with them, as for any ban made in Modbot. A member with no VRChat link is banned from the Discord server only. Nothing is sent until you have sent the form (the group's reasons and a note for a group ban; a reason and Delete their messages from — None, 1 day or 7 days — for a Discord ban) and pressed the red button on the confirmation. Never the bot, the server's owner or a Discord account linked to a Modbot staff account. Without See profiles, vrchat takes an exact id only: no names are suggested or searched, and no reply names the person. See Ban and kick. | Ban for a VRChat person or a linked member; Ban on Discord for a member with no VRChat link; and a VRChat account linked to your Modbot account |
/kick member: vrchat: from: | Removes one person. Name them as for /ban. A Discord member is removed from the Discord server and a VRChat person is kicked from the group, unless from says otherwise: Discord server, VRChat group or Both, for a person with both accounts linked. The form and the confirmation work as for /ban; Both is one confirmation that acts in both places. Seen only by you. | Kick for the group; Remove from Discord for the Discord server; both for Both; and a VRChat account linked to your Modbot account |
/gate waiting, /gate let-in member:, /gate hold, /gate lift | The join gate from Discord. waiting lists up to 10 people at the gate, oldest first, with when they joined and a Let in button for each; if more are waiting it says "and N more". let-in takes a member picked from Discord's list and gives them the member role now, whatever steps they have left. hold holds new joiners at once, with nothing to confirm first, and the reply has a Lift hold button; lift lifts the hold. They do what the buttons on the join gate page and under a join spike alert do, and write the same entries to the audit log under the name of your Modbot account. Seen only by you. | Manage the join gate, and a VRChat account linked to your Modbot account; waiting also needs See members, as the page does |
/ageverified member: method: vrchat: | The 18+ check, typed in a ticket. member is picked from Discord's list; method is Badge or Photo ID; vrchat is the member's VRChat profile link, needed only when they have not linked their accounts. Marks the VRChat account 18+ verified, gives and takes away the Discord roles and the VRChat group role chosen in Settings → Discord → 18+ check, logs the method, the date and you as the checker (nothing else is kept, never the ID), and deletes the ticket if that is switched on. A role that fails is said in the answer and does not undo the check. Only there when /ageverified is on the Commands card, which is off to start. Seen only by you. | Edit 18+ verified, and a VRChat account linked to your Modbot account |
/event open event:, /event cancel-date event: date: say-so: | The calendar from Discord, for event hosts. event suggests your upcoming events as you type. open opens the event's instance now, with the same refusals as Open now on the calendar page (for example "It is too early to open the instance."). cancel-date suggests the event's next ten dates, asks "Cancel Title on time?" with Cancel this date and Keep it, and cancels only that date when you press the red button. For an event that does not repeat, its only date is the whole event, and the button says Cancel the event. say-so yes also posts, once, that it is cancelled in the event's channel, as the calendar page's tick does; an event with no channel refuses it. The date is cancelled once however many times the button is pressed, and the audit log has the same entries as for the calendar page, under the name of your Modbot account. Suggestions need See calendar as well, as the calendar page does. Seen only by you. | Manage calendar, and a VRChat account linked to your Modbot account |
/post new channel:, /post list | Marketing posts from Discord, for event hosts. new takes a channel picked from Discord's list and opens a form with a Title (optional) and the Text. You then see a private preview of the message exactly as it will be posted, with Post now and Cancel. Post now saves a post that is due now, the same as Post now on the Marketing tab, and Modbot's Discord sender posts it within about twenty seconds: it tries once, and a press, a second press or a restart can never make a second message. The post then shows on the Marketing tab like any other. It is refused, and nothing is saved, while posting is paused, Discord posts are switched off or Discord is not set up. list shows the next ten posts waiting to go out, soonest first, and the posts that failed, each with its time. Discord only; VRChat and Bluesky are chosen on the Marketing tab. Seen only by you. | new: Manage posts, and a VRChat account linked to your Modbot account. list: See posts |
/vote channel: only_for: show_counts: anonymous: | Asks the server to vote on a question, for event hosts. channel is picked from Discord's list; only_for is a role, and only people holding it can vote (leave it out for everybody); show_counts puts the count for each option on the message while the vote is open; anonymous is yes when left out, and no lets staff see who picked what on the Votes page. It opens a form with the Question and the Options, one on each line, and posts the vote at once. See Votes. Only there when /vote is on the Commands card, which is off to start. Seen only by you. | Manage posts, and a VRChat account linked to your Modbot account |
/events private: | The next five dates in the next 14 days, soonest first: the event's name, its time in each reader's own time zone, how long until it starts, the world's name, and Open now while its instance is open. Only events already published in this Discord, as a Discord event or a post in a channel; never a draft, a cancelled event or a deleted one. A Join button (at most five) opens VRChat for an event anyone can join whose instance is open; events only members can join have none. The answer is public unless private is yes. If a public /events was already posted in that channel in the last minute, the answer is private instead. Each person can ask five times a minute. Only there when /events is on the Commands card. | Anyone in the server |
/remindme event: before: | Sends you one direct message before an event, so you don't miss it. Pick the event from the list under event, which suggests only the events /events would show. before is 15 minutes, 1 hour (if you leave it out) or 1 day. Running it with an event is the whole opt-in: Modbot sends you a confirmation direct message at once, with a Stop button, and the reply you see says when the reminder will come. If your direct messages are closed, it tells you so and keeps nothing. Run it with no event to list your reminders, each with a Stop button. The reminder says "Title starts" and the time in your own time zone, and has a Join link only if anyone can join the event and its instance is open. A repeating event is reminded for its next date only. The reminder follows a date that moves, is dropped if the date or event is cancelled, and is not sent if it is more than 15 minutes late. You can have one waiting reminder per event date and ten in all. Only there when /remindme is on the Commands card; see What Modbot keeps for reminders. | Anyone in the server |
/report member: what: | Tells the mods about someone, privately. member is picked from Discord's list; what is 1 to 1,000 characters. The reply, seen only by you, is "Sent to the mods." You can't report yourself or Modbot. If you already have an open report on that person it says "The mods already have your report." You can make 3 reports in any 10 minutes and 10 in a day; after that it says "Slow down. Try again in a few minutes." Nobody else in the server sees that you reported, and the person reported is never told. The mods read it on the Reports page. Only there when /report is on the Commands card; see What Modbot keeps for reports. | Anyone in the server |
/profile member: | Your own profile card, seen only by you, with Edit, Who sees what, Findable and Spotlight buttons (the last two are your own on/off switches, off to start: Findable lets /find list you, Spotlight lets the weekly member spotlight feature you): the fields you fill in are the ones set up under Settings → Member profiles. A pick-list field is a select menu in the form and a free text field a text box. With member it shows that member's card: only the fields they let you see, or every answer if you are a moderator with a connected Modbot account who can see members. Only there when /profile is on the Commands card. | Anyone in the server |
/notify | Opens a form to sign up for event categories and be told before events that carry them. Tick the categories you want, none to take them all off; when both ways are on, also pick Direct message or Ping in a channel. The reply says what you will be told about. The same sign-up is on the Notify me button under each event's channel post. Not on the Commands card: it is there only while On is switched on in the Alerts card on the Event categories page, and is off until then. See Event alerts. | Anyone in the server |
/supporter-code | A short code, seen only by you, to paste into the message box when you pay on Ko-fi, so Modbot can match the payment to your Discord account. Asking again gives the same code. Needs no Modbot account. Not on the Commands card: it is there only while the Ko-fi switch in Settings is on. See Ko-fi. | Anyone in the server |
/find field: value: also-field: also-value: | Lists members by what their profiles say, for example the members whose Role is Singer and whose Time zone holds UTC-5. field and value are required; also-field and also-value add a second condition, and a member must match both. Fields and the options of a pick-list are suggested as you type; for a free text field, value is any words the answer holds, in any letter case. Only members who turned Findable on in /profile are listed, never you, bots or people who left. A member is matched only on an answer you may read: the ones they opened to members, or every answer if you are a moderator with a connected Modbot account who can see members, so a match never gives away a hidden answer. The reply, seen only by you, has a button for each of up to 25 members, labelled with their name, and says how many more there are. A button shows the card /profile member: would show you. Only there when /find is on the Commands card. | Anyone in the server |
/birthday set month: day:, /birthday show, /birthday remove | Your own birthday, a month and a day and never a year. set takes the month from a list and the day as a number, and refuses a date that does not exist. show tells you what is set and remove forgets it, taking the birthday role off at once if you hold it. Only you see the answers. You can run it five times a minute. Only there when /birthday is on the Commands card; see Birthdays. | Anyone in the server |
/term name: | What a word your community uses means. name is suggested as you type, from the terms and their other names staff typed on the Terms and rules page; you can also type the whole word, in any letter case. The answer, seen only by you, is the term, its other names and what it means. You can run it five times a minute. Needs no Modbot account. Only there when /term is on the Commands card. | Anyone in the server |
/rule rule: | One of your community's rules. rule is suggested as you type, by number and title; you can also type a number or the whole title. The answer, seen only by you, is the rule's number, its title and what it says. You can run it five times a minute. Needs no Modbot account. Only there when /rule is on the Commands card; see Terms and rules. | Anyone in the server |
/link | A Link VRChat account button that opens the account linking page. | Anyone in the server |
/me | What Modbot holds about the member who ran it, with What Modbot keeps and Ask to delete my data buttons. Only there when /me is on the Commands card; see What members can see: /me. | Anyone in the server |
/verifyaccount code: | Connects the Discord account that runs it to a Modbot account, with the code from Connect with a code on that account's Your account page. See Letting moderators use the commands. | Anyone in the server |
/help | The commands the person who ran it can use, and what each does. A member who has not connected Discord to a Modbot account sees /link, /me, /events, /remindme, /birthday, /term, /rule, /notify, /supporter-code, /report, /verifyaccount and /help only; a moderator also sees the commands their Modbot permissions let them run. | Anyone in the server |
Switching commands on and off
Settings → Discord → Commands has one switch for every command and right-click menu, labelled with its
name. A command that is off is not registered: nobody sees it in Discord. Press
Save commands; the bot registers the new list within a few seconds, without reconnecting.
Everything is on except /me, /events, /remindme, /report, /profile, /find, /birthday, /ageverified, /vote, /term, /rule and the Report to mods menu, which stay off until you turn them on. /notify is not on this card: it follows the On switch in the Alerts card on the Event categories page, off by default. The commands you never touched
keep following their default if a later version changes it. Nothing can be saved in the demo.
What Modbot keeps for reminders
/remindme is off until you turn it on. Each reminder is one row in Modbot's database: the member's Discord
id, the event, the date it is about, how long before it was asked for, when it is due and its state
(waiting, sending, sent, stopped, skipped or failed), with the times they changed. No name and no message text.
Every reminder is deleted in the end: sent, stopped, skipped and failed ones 30 days after they last changed,
one stuck while sending after a day, and one nobody handled (the command was off) 30 days after it was due.
Just before it sends, Modbot checks again that the event is still one /events would show, and skips the reminder
if it is not, so a message never names an event taken off Discord after you asked. Purging a person deletes all of theirs. What leaves your server is two direct messages
through Discord to that member: the confirmation, and the reminder. Turning /remindme off stops the
reminders being sent too; Stop keeps working. Reminders are separate from
event invites: asking for one signs nobody up for the other, and
stopping event invites under /me does not stop a reminder. Each member can run /remindme five times a minute.
What Modbot keeps for reports
/report and the Report to mods menu are off until you turn them on. Each report is one row in Modbot's
database, on the Reports page:
- the reporter's Discord id and name, as they were when they reported;
- the reported person's Discord id and name, and the VRChat account linked to them then, if any;
- what the reporter wrote;
- for a report made from the menu, a copy of the message: its id, the channel's id and name, when it was sent, its words, the names (only the names) of the files attached, and its link;
- whether it is open or closed, who closed it and when, the note they wrote, and when the text was removed.
The reporter is shown on the Reports page to everyone who can see reports, and nowhere else. Not in Discord,
not in a notification, not in the audit log. The audit log gets two entries, Member report made and Member
report closed, naming the person reported and the report's id, and nothing written or quoted; when the person
is a staff account, only people who also hold Review tickets see them. Running /report
or the menu is not recorded as Discord command used, because that entry would name the reporter.
A closed report keeps its text and the message copy for Closed reports days, 365 unless you change it under Settings → Server → Keep for (days); 0 keeps them forever. Then the text and the message copy are removed and the bare record stays: who, about whom, when, and who closed it with what note. An open report is never removed. Purging a person deletes every report they made and every report about them.
What leaves your server: nothing about a report goes to Modbot Cloud or to an AI chat tool in this version. Staff who can see reports are told "Modbot: new report" by email, Discord direct message or push, as each of them set up, with no names and no words, and at most one every 15 minutes.
Who sees the commands in Discord
/lookup, /recent, /modbot, /note, /watch, /live, /ban, /kick, /gate and /ageverified are shown only to members who may time others out (Discord's
Timeout Members permission). /event, /post and /vote are shown only to members who may manage events
(Manage Events), which event hosts usually have and moderators often do not. Everyone else does not see
them in the command list. /report, like /events, /remindme, /birthday, /term, /rule, /notify and /supporter-code, is shown to everyone while it is on. To change
who sees them, open Server Settings → Integrations → Modbot in Discord and pick roles or
members for each command. /verifyaccount is shown to everyone, because many moderators don't hold
Timeout Members; without a code from a Modbot account it does nothing.
Seeing a command does not let anyone use it: Modbot still checks the person's Modbot account and permissions every time, as described below.
Letting moderators use the commands
Every command except /link, /me, /events, /remindme, /birthday, /term, /rule, /notify, /supporter-code, /report, /verifyaccount and /help only answers people Modbot can match to
a Modbot account. Each moderator connects their own Discord account from their Your account
page in Modbot, under Your Discord account, in one of two ways. Either way, the card then says
Connected as and their Discord name. Nobody can do this for somebody else, and nobody can type
an id in: Modbot knows the Discord account is theirs because Discord told it.
- Connect with a code works once the bot is set up. The card shows a code such as
K7P-42Q, with Copy, and the command to run:/verifyaccount K7P-42Q. Run/verifyaccountin your Discord server and paste the code intocode. Discord tells Modbot which account ran the command, and the bot replies "Your Discord account is now connected to Modbot." The card changes by itself within a few seconds. A code works once, for 15 minutes; New code replaces it. A wrong or old code gets "That code isn't right or has expired." Each Discord account can try five codes a minute, and a code stops working after five wrong tries at it. - Connect Discord signs in to Discord: Discord asks them to sign in and allow Modbot to see who they are, then sends them back. It uses the same Discord application as Account linking, so it is only offered once the Account linking card's client id, client secret and redirect address are saved.
If the bot isn't set up either, Connect Discord stays, and pressing it says "Discord sign-in is not set up on this server."
A Discord account can be connected to one Modbot account. If it is already connected to another
one, nothing changes: the account page says so, or /verifyaccount replies "This Discord account is
connected to another Modbot account." Disconnect on the same card takes it off; the bot then
treats that Discord account as nobody.
If someone without a connected Modbot account runs a command, the bot replies "Connect Discord on your account page in Modbot first." If they lack the permission, the reply names the permission they need. Permissions come from the person's Modbot roles, the same as in the web app. See Roles and permissions.
Before connecting existed, moderators typed a Discord user id into their account, and an administrator could type one for them. Modbot never checked those. An account that still has one shows it as Not proven, with the day it stops working: the bot answers it, and sends direct messages to it, until 1 November 2026, and then never again. Connecting before then, with Connect with a code or Connect Discord, replaces it. Where two accounts typed the same id, the bot answers neither.
Every command run, answered or refused, is recorded in the audit log as Discord command used, except /report
and the Report to mods menu, which would name the reporter.
The names suggested while you type into /lookup user:, /note vrchat:, /watch vrchat:, /ban vrchat: and /kick vrchat: are not
recorded; the command you then run is, and so is every question you answer and every button you press under /event and /post. The events and dates suggested under /event are not recorded either, and neither are the fields and options suggested under /find. A /find is recorded as a command run, without the fields or words searched for and without who was found. A /term or /rule is recorded as a command run, without the word, number or title asked about, and the terms and rules suggested under them are not recorded. Names are only suggested to people that command would answer, and for every one but /lookup only to people who also have See profiles.
Right-click menus
The bot also registers two menus, under Apps when you right-click a member: Look up in Modbot and Add a note. They follow the same rules as the commands: a connected Modbot account and the matching permission. Only members with Discord's Timeout Members permission see them until a server admin changes that under Server Settings → Integrations. See Acting from Discord.
One more menu is for everyone, under Apps when you right-click a message: Report to mods. It opens a
form asking "What's wrong?" (1 to 1,000 characters) and tells the mods about the message's author, with a copy
of the message. It follows the rules of /report above, and it refuses a report on your own message, on
Modbot's, on a message you already reported, and on a person you already have an open report on. It is off until
you turn it on, and needs no Modbot account.
Turning the bot off
Clear Server id on the Bot card and press Save. The bot disconnects within a few seconds. Your channels and other Discord settings are kept for when you turn it back on.
If something is wrong
Start with the Discord bot card on Health.
| You see | What to do |
|---|---|
| stopped — needs you with "Discord rejected the bot token." | Reset the token in the Developer Portal and paste the new one into Bot token. |
| Intents off in the Developer Portal: … | Switch the named intents on under Bot → Privileged Gateway Intents. |
| reconnecting for a long time | Check whether Discord is having problems. After a few minutes Modbot signs in again from scratch by itself. |
| connected, but no slash commands appear in Discord | The bot was invited without the applications.commands scope. Invite it again with it. |
| A problem registering the slash commands | Check that Server id is your server's id and that the bot is in that server. |
A moderator does not see /lookup, /recent or /modbot | They lack Discord's Timeout Members permission. Show them the commands under Server Settings → Integrations → Modbot in Discord; see Who sees the commands in Discord. |
| A channel marked Missing … or Removed | Give the bot the named permissions in that channel, or pick a different channel. |
Discord
Every Discord page in Modbot, from setting up the bot to the features that run in your server.
Acting from Discord
Look people up, write notes, watch people, see who is live, and kick, ban or answer join requests from Discord, with the same permissions and records as the web app. Includes the /ban and /kick commands.