Calendar
Plan your group's events once in Modbot, and let it put them on VRChat's group calendar, in Discord and in a calendar feed, and open the instance on time.
The Calendar page is where you plan your group's events. You fill in an event once, and Modbot does the rest:
- puts it on your group's VRChat calendar;
- makes a Discord event in your server;
- posts it in a Discord channel, with a Join button once the instance is open;
- lists it in a calendar feed, a link people can add to Google Calendar, Outlook or Apple Calendar;
- puts it on your group's own Google calendar, once one is connected;
- posts it on your group's Bluesky account, one post for each date, once one is connected;
- opens the group instance a few minutes before the start, if you ask it to.
Each of these has a tab in the event form. An event made from nothing goes nowhere until you change something on a place's tab; then Modbot sends it there. A place you never touch is left alone. The calendar feed is always on.
Events made on VRChat itself, on vrchat.com or in the game, show up on the page too, and you can edit them from Modbot. See Events made on VRChat.
Who can use it
| To do this | You need |
|---|---|
| See the Calendar page, every event, where each one is published and any errors | See calendar |
| Plan, edit, cancel and delete events | Manage calendar and See calendar |
| See, copy or replace the calendar feed link | Manage calendar and See calendar |
| See the templates | See calendar and Manage calendar or Manage templates |
| Make, edit and delete templates, with every part of the template form | Manage templates and See calendar |
| Turn the public feed on or off, and copy its address | Manage calendar and See calendar |
| See what each event did and Past events | See calendar and See analytics |
| See who a moderator's client saw at an event | Those two and See the audit log |
| See the Event categories page | See calendar |
| Make, rename and delete event categories | Manage calendar and See calendar |
| Change the event alerts settings | Manage calendar and See calendar |
| See calendar problems on Health | See the operational log |
Without See calendar, Calendar does not appear in the sidebar. Manage calendar on its own is not enough to open the page. Without Manage calendar, the page is read-only: there is no New event button, no feed link or Public feed switch, an event shows no Edit, Duplicate, Cancel event or Delete buttons, and nothing can be dragged or drawn on the calendar.
None of these permissions is in the built-in Moderator or Viewer roles. Administrator holds all of them. Give them on purpose: an event can open an instance by itself, and it posts to VRChat and Discord in your group's name.
The page
The page works like Google Calendar. At the top are Today, the arrows for back and forward, the dates on screen (for example September 2026 or Sep 21 – 27, 2026), and a switch between four views:
- Day and Week show the hours down the side, in your own clock, and one column a day, Monday first. The page opens scrolled to an hour before the first event on screen, or to 8 AM when there is none. A red line marks the time it is now. Events that overlap sit side by side. An event that lasts a day or longer is shown in a row across the top instead. Click a date at the top of a column to see that day on its own.
- Month shows six weeks. Each day lists the events that start on it, with the start time, up to three; +2 more (or however many) opens that day. Click a date to see that day.
- Schedule is a list from the day on screen to about two months ahead. Each row shows the time, the title, the event's status, the world, and a badge for each place it is published, such as VRChat calendar: Published or Discord event: Failed.
Week is the view the page opens on. On a phone it opens on Day.
Refresh, beside the views, reads your group's VRChat calendar again straight away. See Events made on VRChat.
On a wide screen a small month sits beside the calendar. Click a date in it to jump there; its own arrows page through months without moving the calendar. It is hidden on phones.
A repeating event appears once for every time it happens.
Times on the page are in your browser's time zone. Each event also has its own time zone, which you set in the form (see When).
Below the calendar, Possible duplicates in Discord lists Discord events that look like copies of each other, when there are any (see Duplicate Discord events). Under it, a Drafts box lists events saved as drafts, when there are any. Under that, Past events lists every time an event ran in the last 90 days, the busiest first. See Past events.
The page updates by itself when an event changes, so a place changing from Sending… to Published shows up without reloading. While an open event still has something being sent, it is also read again every few seconds.
Colours
An event's colour says where it stands:
| Colour | Meaning |
|---|---|
| The accent colour | Scheduled, and nothing has failed. |
| Green | Open right now. |
| Red edge | Scheduled or Open, and at least one place it is published has Failed, or its instance did not open. Open the event to see the error. |
| Dashed outline | A Draft. |
| Faded | Finished. |
Keyboard shortcuts
| Key | Does |
|---|---|
| D, W, M, A | Day, Week, Month, Schedule |
| T | Today |
| J or → | Forward a day, a week or a month |
| K or ← | Back a day, a week or a month |
| C | New event (with Manage calendar) |
They are also listed under Calendar when you press ?.
An event's status
| Status | Meaning |
|---|---|
| Draft | Saved, but published nowhere and never opened. |
| Scheduled | The next time it happens has not started yet. |
| Open | It has started, or its instance has opened early, and it has not ended. |
| Finished | It does not happen again. |
| Cancelled | Someone cancelled it. |
A repeating event goes from Scheduled to Open and back to Scheduled each time, and only becomes Finished after the last one.
Opening an event
Click an event in any view. It opens in a small box beside it, showing:
- when it starts and ends (the time you clicked, for a repeating event), and how it repeats;
- Moved from … when that one date was moved on its own;
- the description (that date's own, if it was given one);
- World, which opens the world popup. For an event that picks from a world list, the world picked for its next date, and under it the World list, with Pick again while that date is scheduled; other dates show the list's name;
- Next game, while an event that picks from a list is open. See Next game;
- Instance, once Modbot has tried to open one: Opening while it waits for VRChat, Open or Closed (click it for the instance popup), and a Join link while it is open. If VRChat refused, VRChat's error is shown here instead, in red, and Open now tries again while the instance can still be opened;
- one line per place it is published, with its state: Sending… (with a turning mark) from the moment you save until it is done, then Published, or Failed with what went wrong and a Try again button. See Try again;
- How it went, once the time you clicked has started. See What an event did.
With Manage calendar you also get Edit, Duplicate, Cancel event and Delete, and Open now from two hours before a time starts until it ends, while no instance of it is open. See Opening the instance. Duplicate opens the form for a new event filled in with this one's details; nothing is saved until you save it. With Manage templates you also get Save as template.
A link to one event (for example from a Chat answer) opens it in the middle of the page instead.
Streamed on Twitch
With Twitch set up, an event shows Streamed on Twitch, with the time and Open for the channel, for each stream that started while it was on (from an hour before it starts to its end). When two events overlap, Modbot leaves the stream unlinked. With Manage calendar you can click Remove on a stream, or Link a Twitch stream to choose another from the channel's recent streams; what you choose Modbot never changes.
What an event did
Open a time an event has already run, or one that is running now, and How it went shows what it did. You need See analytics as well as See calendar for it.
| Figure | What it counts |
|---|---|
| Most at once | The most people in the event's instance at one moment, over the instance's whole life. The same number as Most at once in the instance popup. |
| Ran for | How long the instance was open. Open for while it still is. |
| New members | People who joined your group from when the event opened (its instance's Minutes early included) until a day after it ended. |
| Join requests | Requests to join your group over the same stretch. |
New members and join requests count until a day after the end because people often join a group the day after an event they liked. Two times of a daily event share some of that day, and both count it.
Which instance. The one Modbot opened for that time, when it opened one. Otherwise, your Managed group's instance in the event's world that was open for most of the event, which covers an event someone opened by hand in VRChat. An event with no world, and no instance opened by Modbot, has no instance: Most at once and Ran for show —. When the instance is not the one the Instance line above already shows (that line is about the time Modbot is dealing with now), it is named under How it went; click it for the instance popup.
For a repeating event, a Usually column shows the middle value of its last six times before this one. Times with no instance leave out Most at once and Ran for.
Seen by a moderator's client shows how many people a moderator's desktop client saw in the instance, their total time there (People-time), and the people seen longest, each with their time. Everybody opens the instance popup's People tab when there are more. This needs See the audit log too, and counts only while a moderator's client was in the instance: Nobody seen. means no client saw anyone, not that nobody came. For Usually, times nobody was seen are left out.
The numbers show on this page and in the event's dates over time. The only place they are posted is the optional monthly event summary, and only as averages.
An event's dates over time
Every date of this event, under How it went, opens the event's page at /calendar/series/ and its
id. It shows how the event did over time, one row for each date, newest first, and the same figures as a line chart.
You need See analytics as well as See calendar. One page covers all the dates of one event, so a
repeating event is one page and two separate events are two.
| Figure | What it counts |
|---|---|
| Interested on Discord | The number Discord shows as interested in the event's Discord event when the date started, read while the date runs. |
| Interested on VRChat | The number VRChat shows as interested in the event on the group calendar when the date started, read while the date runs. |
| Came | The people a moderator's desktop client saw arrive in the date's instance. |
| Most at once | The most people in the date's instance at one moment. |
Above the chart, the page gives the average of each figure over the dates that have it.
- The interested numbers are read once, when the date starts, and kept. This needs no switch, and it happens for every date of an event that is on Discord's events or on VRChat's calendar. If Modbot was not running at the start, the number is read later in the date and shows a muted late beside it. A date from before Modbot kept them, or one VRChat did not list, shows —.
- Came counts only the people seen where a moderator's Modbot app was. It can be lower than the real turnout, and a date nobody was seen at shows —.
- A date missing one figure is skipped on that line of the chart, and the line carries on.
- The page lists at most the latest 100 dates.
- Nothing warns you when a number drops.
Staff can also get the averages for the month before posted in a channel, as a monthly event summary.
Past events
Past events, under the calendar, lists every time an event ran in the last 90 days: the event, when, Most at once, Ran for, New members and Join requests. The busiest come first, and times with no instance come last. It shows at most 50, and only when there is at least one. Click a row to open that time of the event with How it went. On a phone each row shows the event, when it started and its new members, with the most at once on the right.
Drafts and deleted events are never listed. A cancelled event's times before the cancel are. A date cancelled on its own is not listed, and a date moved on its own is listed at the time it ran.
A time counts as one the event ran when the event's dates say so, or when Modbot opened an instance for it. If you move a repeating event, its earlier times are worked out from the new dates, except those Modbot opened an instance for, which stay at the time they ran.
Moving events by dragging
With Manage calendar you can change the calendar by dragging, the way you would in Google Calendar. Without it, events open when clicked, but nothing can be dragged and no new event can be drawn.
- Move an event: drag it to another time, or to another day in Week. In Month, drag it to another day; it keeps its time of day. An event in the row across the top of Week can be dragged to another day the same way.
- Change when it ends: drag its bottom edge.
- Draw a new event: press on empty time and drag down. A single click on empty time draws one hour. In Month, click empty space in a day. A small form opens with the time filled in: type a title and click Save draft, or click More options for the full form. The small form only saves drafts, so nothing is published until you open the draft and click Schedule. Closing the small form after typing a title asks Discard changes? first.
Everything snaps to 15 minutes. On a phone, hold your finger on an event (or on empty time) for a moment until it picks up, then drag. A finger that moves straight away scrolls the page instead.
A drag is saved once, when you let go. It is the same as opening the event, changing its times in the form and clicking Save: the change reaches VRChat's calendar, the Discord event and the channel post the same way, and the audit log records it, for example moved the event “Movie night” from Sat 26 Sep, 08:00 PM–10:00 PM to Sun 27 Sep, 09:00 PM–11:00 PM.
After a drag, Event moved · Undo shows at the bottom of the screen for a few seconds. Undo puts the event back where it was, through the same save. Because Modbot waits 20 seconds without a change before writing to VRChat's calendar, an undo straight away usually means VRChat is never sent the move at all. If the save fails, the bottom of the screen says why instead, for example That event has already ended.
Repeating events
When you drag one date of a repeating event, Modbot asks Move “…”? and shows the date you dragged and where it is going:
- This date moves only that date. The other dates stay where they are. After it saves, Date moved · Undo shows at the bottom of the screen. See Changing one date of a repeating event.
- All dates moves every date by the same amount, the same as editing the whole event. The days of the week and the Last date move with it: a Monday and Wednesday event dragged one day later becomes Tuesday and Thursday.
Close the box to leave the event where it was.
Planning an event
Open the form
Click New event (or press C). The form starts with the next whole hour, two hours long, in your browser's time zone. You can also draw the event on the calendar and click More options (see Moving events by dragging); the form then starts with the time you drew.
Fill it in
Open the tab of each place the event should go to (see where it goes), type its title and description straight into the picture of how that place shows the event, and set the rest on the Shared info tab. Every field is described below. To schedule it, an event needs a title, typed on any place's tab, plus a world if the instance should open by itself, and a channel if the Discord post is on.
Save it
- Schedule saves it and starts publishing it everywhere that is on.
- Save draft saves it without publishing or opening anything. You can come back to it from Drafts and click Schedule later.
- Cancel leaves without saving. Closing the form any other way (the X, Esc or a click outside it) does the same. If you changed anything since it opened, Modbot first asks Discard changes?: Keep editing goes back to the form, Discard closes it. A form you did not touch closes at once.
Save draft needs nothing filled in, not even a title or a world. A draft with no title shows as Untitled event in the Drafts box, on the calendar and in its details, and Schedule refuses it until it has one. Schedule asks for a world list to be picked only when VRChat is on: it opens the VRChat tab and says Pick a list.
The buttons stay at the bottom of the form while you scroll, and are the same on every tab, on a phone too. When you edit an event that is already scheduled, Save takes the place of Schedule and Save draft.
Schedule and Save first look the event over. If something looks off, the form stays open and says what, above the buttons, and the button becomes Schedule anyway or Save anyway. Click it to save as it is, or change the form first. Save draft is not looked over.
When you turned a place on by changing its tab, Schedule also says once where the event is going, for example Goes to VRChat calendar, Discord event. Click Schedule anyway to go ahead.
| Warning | When |
|---|---|
| No VRChat tags | The event goes to the VRChat calendar and Tags is empty |
| No VRChat language | The event goes to the VRChat calendar and Languages is empty |
| The title differs from the template's | The event was made with Use template and its title is no longer the one the template gave it |
| "Title" already starts … | Another event has the same title and starts within 15 minutes of this one, in Modbot or on VRChat's group calendar. "On VRChat" is added when it was made there |
Titles are compared the way Duplicate Discord events compares them. A repeating event is checked by its first start. The check looks only at the events Modbot has stored, which include your group's VRChat calendar as of the last time the calendar page was opened or refreshed. It never asks VRChat, so saving never waits on it; press Refresh first to be sure an event just made on vrchat.com or in the game is counted. If the check is slow, the save goes ahead without the duplicate lines.
Modbot does not publish while you wait on the form. It saves the event, then publishes it in the background within a minute or so. Watch the place badges change on the event; they change without reloading the page.
Where it goes
Every place that is set up has a tab in the form, after Shared info. An event made from nothing goes nowhere until something on a place's tab is changed; that turns the place on and puts a dot on its tab. Typing in the title or description in its picture counts. An event made from a template or a copy keeps the places it had. Schedule names the places once, as described under Save it.
| Tab | What it does | Its own settings |
|---|---|---|
| VRChat | Puts the event on your group's VRChat calendar. | VRChat calendar, and Open the instance |
| Discord, the event | Makes a Discord event in your server. | The Discord picture |
| Discord, the post | Posts a card in a channel. | Discord channel post |
| Google Calendar | Puts the event on your group's Google calendar. | The Google Calendar colour and Show as, and Visible to, under Where |
| Bluesky | Posts each date on Bluesky a set time before it starts. | Bluesky |
The calendar feed always lists the event and has no tab. Opening the instance is part of the VRChat tab: changing Minutes early or who is invited turns it on.
Not set up. A place that is on but cannot work yet says Not set up on its tab. Click it to open the setting that is missing, in a new browser tab, so what you typed stays. A place that is not set up has no tab unless the event already goes there; if you may change settings, the + after the tabs lists what is missing and links to Settings:
| Place | Needs |
|---|---|
| VRChat calendar, Open the instance | A Managed group and a VRChat account, in Settings, Modbot's VRChat login. |
| Discord event, Discord channel post | A Server id and the bot connected, in Settings, Discord. While the bot is connecting or reconnecting, these say Not set up too, because nothing is sent until it is back. |
| Google Calendar | A key and a calendar that Check found Modbot may change, and Keep Google updated on, in Settings, Google Calendar. See Google Calendar. |
| Bluesky | An account that passed Check and Posting on, in Settings, Bluesky. See Bluesky. |
The Discord post also says Not set up until you pick a channel on the Discord tab.
Members only. The Google Calendar tab says Members only for an event only your members may see: Visible to is Group, or VRChat shows the event only to some of your group's roles. Set Visible to to Everyone to send it. An event that was on Google keeps its place, and goes to Google again once everyone may see it.
You can still save an event with a place that is not set up. Nothing is sent there until it is set up; then Modbot catches up by itself. The event shows the same Not set up where that place would be, and so does Health.
The tabs
The form has a Shared info tab, then one tab for each place that is set up: VRChat, Discord, Google Calendar and Bluesky. The Discord event and the Discord post share the Discord tab, one above the other; clicking in one makes it the one you are working on. A tab with a dot is a place the event goes to. The calendar feed has no tab; it uses the event's words. On a phone the row of tabs scrolls sideways. Saving works from any tab. When a save is stopped by a field on another tab (the world list, or a picture that did not upload), the form jumps to the tab with that field.
| Tab | What is on it |
|---|---|
| Shared info | The fill-ins and links, Categories, When, Where, and Name in a template. No title or description: each place has its own. |
| VRChat | The event as VRChat shows it, then the VRChat calendar settings and Open the instance. |
| Discord | The Discord event and the Discord post, each the way Discord shows it, with the Discord picture and the Discord channel post settings. |
| Google Calendar | The event as Google's own event popup shows it, then the Google Calendar settings. |
| Bluesky | The post, then Bluesky's Post it. |
Typing into the picture. A place's tab draws the event the way that place shows it, and the title, the description and the picture are boxes you type in or click on, in the place of the real thing. The VRChat tab has nine views: five in game (group events, calendar, event page, live now, notification) and four on vrchat.com (group events tab, event page, calendar, calendar popup). The Discord tab has the Events list, Event page and Link in chat views of the Discord event, and In the channel for the post. Click the names above a picture to show or hide a view; what you type shows in every view that is open. The Link in chat view has not been measured against Discord yet, so it may be a little off. The Bluesky tab has no views: it is Bluesky's New post box, and nothing else.
A place's card is read when its tab opens, and drawn again a moment after the form changes. The lines the place adds around your words (the time, the world, the join link) come from the server, by the same code that sends the event, so they match what goes out. Beside each description a count, such as 12 / 1000, turns red when it is over the place's limit. Copy and Paste buttons sit beside a box, and a description also has the links button. The fill-ins (in a template) and the links are under the card too, and go where you last clicked.
- Discord event: the cover, the time, the title, the location and the description, cut to Discord's 100 and 1,000 characters. The location is the world's name (or VRChat with no world); the join address only appears while an instance Modbot opened is open.
- Discord post: the card as it will be posted, with the times in your own time, and the role it mentions above it, if you picked one. Click the bar down its left side to pick the colour it has while the event is Scheduled. See The channel post.
- VRChat: what is sent to VRChat: the title, time, repeat, category, who can see it, languages, platforms, tags, picture id, whether members are notified, and the description. VRChat may change some characters after it gets them.
- Google Calendar: what goes on your Google calendar, drawn like Google's own event popup, in the event's colour: the title and the description are boxes you type in, with the time in the event's own time zone, the repeat in words, the location, the calendar's name and the world's name and page under the description. Links typed in Google's own description show as plain words here. A padlock line means only the people the calendar is shared with will see it, because Check found the calendar is not public, or shows the public only free or busy.
- Bluesky: the post for the event's next date in Bluesky's New post box: the text, the post's pictures, the video or the GIF with their alt text (or the link card when it has none of them), who can reply and the language, and a ring that counts down Bluesky's 300 characters.
A card does not save anything or send anything to VRChat, Discord or Google. It can draw an event that is not finished yet, with no title or no channel, but shows the error instead if something would be refused, such as a title that is too long.
Title and description
There is no title or description on the Shared info tab. Each place has its own, typed on its tab.
| Field | Notes |
|---|---|
| Title | Required to schedule: an event needs a title from at least one place. A draft needs none. Up to 100 characters. The count beside it, such as 12 / 100, turns red when it is too long. |
| Description | Optional, except for the VRChat calendar. Up to 1,000 characters, counted the same way. Line breaks are kept. The Discord event and the Discord post share one title and description. |
What each place is sent. A place with a title of its own is sent that. A place with none is sent the event's title, which is the first title typed: the places the event goes to first, in the order of the tabs (VRChat, Discord, Google Calendar, Bluesky), then the others. The same goes for the description. An empty box shows those words muted, so you can see what that place will say. An event made before the form changed keeps its title and description; they show muted in any box that has no words of its own.
An event with no title anywhere is refused with An event needs a title. when you Schedule or Save it. A draft may have none, and shows as Untitled event. An event that goes to the VRChat calendar needs a description, from the VRChat tab or from any other place's.
Each place shows its own text the way that place reads it:
- Discord: Discord's own markup, such as
[words](https://address)for a link. - Google Calendar:
[words](https://address)and barehttp://orhttps://addresses become clickable links. Nothing else typed there is treated as markup, and other kinds of address are left as text. The event's description, sent where a place has none of its own, is still plain text. - VRChat: plain text.
- Bluesky: plain text. Its description is cut to 300 characters, counted the way Bluesky counts (a letter with an accent, or an emoji, is one), and the count beside it turns red when it is over.
Each place's words count against the same limits (100 and 1,000 characters; Bluesky's description 300). A date that was given its own title or description (see Changing one date of a repeating event) shows those words on every place, instead of the place's own text. Modbot's own pages, the calendar feed, reminders and invites always use the event's title, the one described above.
Categories
Shown once at least one event category exists. Tick any number of them, or none. They belong to Modbot: VRChat and Google never hear of them, and VRChat's own VRChat category stays as it was, under VRChat calendar. They show on the Discord event and the channel post.
When
| Field | Notes |
|---|---|
| Starts | The date and time of the first time it happens. |
| Ends | Must be after the start. An event can last at most 7 days. |
| Time zone | The time zone Starts and Ends are in. |
| Repeat | Does not repeat, Daily, Weekly or Monthly. |
| Days of the week | Only for Weekly: tick Mon to Sun. The day of the first start is always included, even if you leave it unticked. |
| Every | Only for repeating events. How many days, weeks or months apart it happens, from 1 to 52: Weekly with Every 2 weeks is every other week. |
| Ends | Only for repeating events. Never, On a date or After a number of times. |
| Last date | For Ends: On a date. The last day it may start on. It cannot be before the start. |
| Times | For Ends: After a number of times. How many times it happens, from 1 to 500, the first one included. After the last one the event is finished. |
The time zone matters for repeating events. A weekly event at 20:00 in Europe/London stays at
20:00 London time in both summer and winter, even though that is a different time for someone in
another country.
A Monthly event happens on the same day of the month as its first start. An event on the 31st skips months that have no 31st.
Every 2 weeks counts weeks from Monday to Sunday, starting with the week of the first start. A Monday and Thursday event that starts on a Thursday happens that Thursday, skips the next week, then happens on the Monday and Thursday of the week after. A skipped month still counts for Every 2 months.
After a number of times counts every time the repeat gives, including a date you cancelled on its own: cancel one of six and five are left.
Where
| Field | Notes |
|---|---|
| World | None, World id (type the world's id; an event that already has a world shows it here), or Pick from a list. None is allowed, unless the instance opens by itself. Pick from a list takes the world from a world list instead, a new one for each date. |
| World list | Shown for Pick from a list. The list to pick from; Seen comes first. See When the world is picked. |
| Who can join | Group members, Members and their friends or Anyone. Used for the instance Modbot opens, and shown on the channel post. |
| Visible to | Group or Everyone, always shown. Who sees the event on VRChat's calendar, and whether it may go to Google Calendar, the public feed and the weekly line-up on Bluesky. A new event starts as Group. |
| Region | US West, US East, Europe or Japan. Used for the instance Modbot opens. |
| Picture link | Optional. Must start with https:// and point at a public website. Used as the Discord event's cover and the channel post's picture, unless a Discord picture is set. When empty, Discord gets the world's picture instead. It can be a link to the picture itself, a link to a page that shows it, or a VRChat file link: see Picture links. |
VRChat calendar
On the VRChat tab.
| Field | Notes |
|---|---|
| VRChat category | One of VRChat's categories: Arts, Avatars, Dance, Education, Exploration, Film & media, Gaming, Hangout (the default), Music, Other, Performance, Roleplaying or Wellness. |
| Languages | Edited in the picture of VRChat's page on this tab, under Languages: type a code such as eng or jpn in Add a language and press Enter or a comma; remove one with its ✕. At most 20, each up to 64 characters. |
| Tags | Edited in the same picture, under Tags: type a tag in Add a tag and press Enter or a comma; remove one with its ✕. At most 20, each up to 64 characters. |
| VRChat picture | Optional. The picture on VRChat's calendar. See The VRChat picture. |
| PC, Android, iOS | The platforms the event is for. They sit beside Choose picture, because their icons are drawn into the VRChat picture. See The VRChat picture. |
| Notify group members | Asks VRChat to tell your group members about the event. VRChat is only asked this when the event is first put on its calendar, not when you edit it later. |
| Featured | Asks VRChat to show the event as featured. Off for a new event. Not every VRChat account may feature events. If VRChat refuses Featured, Modbot sends the event again straight away without it, so the event still goes onto VRChat's calendar, and leaves Featured out of everything it sends for the next 7 days; after that the next change asks again. The box stays ticked in Modbot while VRChat's copy is not featured. |
Some of VRChat's own event settings are not in the form: how early hosts and guests may join, closing the instance after the end, instance overflow and which group roles see the event. For an event made on VRChat, Modbot keeps what VRChat has for them and sends them back with every change.
Picture links
The Picture link can be more than a link that ends in .png or .jpg:
- A link to a page that shows the picture (a gallery page, a post): Modbot uses the picture the page names for link previews, the same one Discord or a chat app would show.
- A link that does not end in a picture name, like a CDN link with
?ex=…after it, or a picture in another format such as WebP: Modbot looks at what the link sends back, not at its name. - A VRChat file link, like
https://api.vrchat.cloud/api/1/file/file_…/1/file, from a picture you uploaded to VRChat: the VRChat picture fills itself in from it, so you do not have to copy thefile_part across. Change or clear the link and a VRChat picture that came from it follows. A VRChat picture you chose yourself stays.
To use a link, Modbot's server fetches it. It only fetches https:// links on public websites, never
an address on your own network, follows at most three redirects, stops after 10 MB or 15 seconds, and
keeps nothing. A VRChat file link is fetched with Modbot's VRChat login, and only while Settings,
VRChat proxy, Proxy VRChat images through Modbot is on.
Discord takes PNG, JPEG, GIF and WebP for an event cover. A link to a picture in another format still works for the VRChat picture, which is turned into a PNG in your browser, but Discord's event gets no cover from it.
A Discord attachment link (cdn.discordapp.com/attachments/…?ex=…) stops working after about a
day. Modbot fetches the link again each time it updates the Discord event, so use a link that lasts.
The Discord picture
On the Discord tab, with the Discord event, or with the post when only the post is on. Discord shows an event's cover in a wide 2.5:1 strip, so a picture made for VRChat's calendar loses its top and bottom there. Discord picture lets you choose which part shows.
- Choose picture, or give a Picture link: the picture opens in a crop box in Discord's shape. A picture chosen here or under VRChat picture opens in both crop boxes, each in its own shape.
- Drag the box, and use Size. The pictures on the Discord tab show the crop, before anything is uploaded.
- Upload keeps the cropped picture in Modbot. From then on Discord gets it as the event's cover and on the channel post, instead of the picture link. Pressing Save or Schedule with a crop still open uploads it first.
- Remove goes back to the picture link. Crop opens the picture link again to crop it anew.
- Modbot keeps the picture (at most 8 MB) until the event is deleted or given another one. A picture uploaded but never saved with an event is deleted once it is a day old, within the hour after.
The VRChat picture
VRChat's calendar does not take a picture link, so its picture is a separate field from Picture link. A VRChat file link in Picture link fills it in (see Picture links).
Uploading a picture is off until you turn it on, and it needs VRChat+. VRChat takes the upload only from an account that has VRChat+, and the account that has to have it is the VRChat account Modbot signs in as for your group. Without it VRChat refuses the upload with You don't have permission to use tag: gallery. Modbot shows that sentence under the field with a Get VRChat+ link, and nothing is uploaded.
There is no box to type or paste a VRChat picture id. A picture belongs to the VRChat account that uploaded it, and Modbot publishes as its own account, so VRChat refuses an id taken from your own account. The VRChat picture field shows one of these:
| What you see | When |
|---|---|
| Choose picture | Uploads are on. |
| Choose picture turned off, with Needs VRChat+ on it | Modbot's VRChat account has no VRChat+. A Get VRChat+ link sits beside it. |
| Choose picture turned off, with Uploads off on it | The upload switch is off. |
| Picture set and Remove | The event already has a picture, whatever the switches say. |
The PC, Android and iOS boxes sit beside Choose picture. They are turned off with it, and for the same reason: Needs VRChat+ or Uploads off shows when you hover over a box that is turned off.
The platform icons are part of the picture. VRChat's own event form has no platform setting, so Modbot draws the icons of the ticked platforms into the top right corner of the picture before it sends it, the way the card on the VRChat tab shows them. Ticking or unticking a box does not upload anything. If a picture Modbot uploaded from this form is already set when you change the boxes, it opens in the crop box again, where you cropped it, and Save or Schedule uploads it again with the new icons. A picture the event had before you opened the form is not drawn again; to change its icons, Remove it and choose a picture again.
The boxes start from the world. Pick a world, or one world from a world list, and the boxes tick themselves for the platforms the world has a build for, once Modbot has read them. You can change them. A world list picked as a whole has no world to tick from, and a saved event keeps its own boxes until you pick another world.
Without a picture, the world's picture is used. When an event goes to VRChat with a world picked and no VRChat picture, no crop open and no Picture link, Save or Schedule uploads the world's own picture, cropped to 16:9 and with the icons, as the event's picture. It uses the world's full-size picture, and its small one if the full-size one cannot be fetched. It needs the same things as Choose picture: uploads on and VRChat+, and Modbot has to be able to fetch the world's picture (Settings, VRChat proxy, Proxy VRChat images through Modbot on). If any step fails the event is saved with no picture, as before. A draft and a template upload nothing. An event that already has a picture keeps it.
Remove means no picture. If you Remove the picture, no world picture is used in its place while the form is open. Choosing a picture, or picking another world, turns it back on.
Modbot also checks for itself. It reads whether its VRChat account has VRChat+ from the account's own tags each time it signs in to VRChat, and Settings, Modbot's VRChat login, Pictures shows the answer as VRChat+: Yes, No or Not checked. Check again reads it again right away, with one request to VRChat; use it after you buy VRChat+ for that account. While the answer is No, the Upload VRChat pictures switch can be turned off but not on, and Choose picture in the form is turned off, with Needs VRChat+ on it and a Get VRChat+ link beside it. The server answers Modbot's VRChat account needs VRChat+ to use pictures. to anyone who asks it to upload, and refuses to turn the switch on. The moment Modbot learns the account has no VRChat+ (when it signs in, or when you press Check again), it turns Upload VRChat pictures off by itself and writes a Settings changed entry in the audit log with nobody named and marked automatic. An event that already has a VRChat picture keeps it and still sends it. Not checked (an account Modbot has not signed in with since this check was added, or one VRChat sent no tags for) is treated as before: nothing is turned off.
To turn it on, go to Settings, Modbot's VRChat login, Pictures, and turn on Upload VRChat pictures. A Get VRChat+ link sits beside the switch. While it is off, Choose picture in the form is turned off with Uploads off on it. A VRChat file link in Picture link still fills the VRChat picture in (see Picture links).
With it on:
- Choose picture and pick any picture your browser can open (PNG, JPEG, WebP, AVIF, GIF, and more). Or give a Picture link in this form: its picture opens the same way.
- The picture opens in a crop box in the shape VRChat's calendar uses, 16:9. Drag the box to choose the part to keep, and use Size to make it larger or smaller. The card on the VRChat tab shows the cropped picture before anything is uploaded.
- Upload sends the cropped picture to VRChat, as a PNG (or a JPEG if a PNG would be over 10 MB), and a small copy of it shows in the form once VRChat has it. Pressing Save or Schedule with a crop still open uploads it first. While it uploads, Save and Schedule wait.
- Crop on a VRChat picture that came from a VRChat file link opens that picture in the crop box, to upload a cropped copy in its place.
- The picture is uploaded to VRChat, to the VRChat account Modbot signs in as for your group. It is a file on that account from then on, like a picture uploaded on vrchat.com. Modbot does not keep a copy; it keeps only the id VRChat gives the picture, and sends that id with the event.
- Remove takes the picture off the event. The file stays on VRChat.
- An event saved with a picture, opened again later, shows Picture set instead of the small copy, because Modbot keeps only the id. So does an event made on VRChat with a picture.
- Modbot uploads one picture a minute at most, the same pace as its VRChat calendar changes. A second picture chosen within the minute waits for its turn.
- To turn the upload off again, turn off Upload VRChat pictures. Modbot then never sends a picture to VRChat: Choose picture in the form is turned off (an event that already has a picture keeps it, and still shows Picture set and Remove), and the server answers Picture uploads are off. to anyone who asks it to upload. Turning it on or off is in the audit log as a settings change.
If the upload fails, the reason shows under the field:
- Could not open the picture. Your browser cannot read that kind of picture (some browsers cannot read HEIC, for example). Save it as a PNG or JPEG and choose it again.
- The picture is larger than 10 MB.
- The link is not a picture., Could not fetch the picture link. or The link took too long to answer. The picture link gave Modbot nothing it could use.
- VRChat is not taking uploads right now. Try again in a few minutes. VRChat asked Modbot to slow down. Modbot does not try again by itself; choose the picture again later.
- You don't have permission to use tag: gallery. The account Modbot signs in as does not have VRChat+. The Get VRChat+ link is beside it.
- Anything else VRChat says, in VRChat's own words.
Who uploaded which picture, and for which event, is in the audit log.
Discord channel post
On the Discord tab, with the Discord post.
| Field | Notes |
|---|---|
| Channel | Pick None and the channel post is turned off; a post the event already had is taken down when you save. A channel where the bot is missing View Channels, Send Messages or Embed Links is marked Missing followed by what it lacks. |
| Mention role | Optional, None to start with. A role to ping when the post goes up, such as @GameNight. See Mentioning a role. |
| Colour | Click the bar down the left side of the post to pick the colour it has while the event is Scheduled. Modbot's violet to start with. Saved with the event, and kept in a template. |
The Discord event has no settings of its own besides the Discord picture.
Open the instance
On the VRChat tab, under Open the instance. The Open the instance switch at the top turns opening the instance on and off; changing a field below it turns the switch on. It needs a world, or a world list.
| Field | Notes |
|---|---|
| Minutes early | How long before the start the instance opens: 0 to 120. The default is 10. |
| Host | A staff account Modbot invites first once the instance is open. See Inviting people. |
| Invite list | A saved list whose people Modbot invites last. Picking one needs See members and See profiles. |
| Staff | Staff accounts Modbot invites after the host. |
| Announce in Discord when the first person joins | Posts once in the Channel when the first person is in the instance. Can only be ticked with Post to channel and a channel. |
| Announce in VRChat when the first person joins | Posts once in your VRChat group's posts when the first person is in the instance. |
| Announce on Bluesky when the first person joins | Replies once under the date's Bluesky post when the first person is in the instance. Can only be ticked with Bluesky on. |
When the instance opens early, the event counts as Open from that moment, not from the start time.
When saving fails
The form lists everything that is wrong at once, one line each, so one fix-and-save round is enough. For example:
- Modbot's VRChat account needs Manage Group Calendar in this group. Shown first, when VRChat calendar is on and Modbot's last look at your group says its account lacks that permission. On its own it does not stop the save: the event is saved, and the VRChat calendar place waits for the permission.
- An event needs a title.
- VRChat's calendar needs a description.
- The VRChat image id is not a VRChat file id. Only a program using the API can get this one, because the form has no box to type an id into. It has a space in it, or it is a link to somewhere other than VRChat. See The VRChat picture.
- The end must be after the start.
- An event can last at most 7 days.
- The last date is before the start.
- Pick a last date or a number of times, not both.
- Repeat every must be between 1 and 52. or The number of times must be between 1 and 500.
- The picture link must start with https://. or The picture link points at a private address.
- Pick a channel to post to.
- Pick a world to open the instance in.
- That world list has no worlds. Add worlds to it on the World lists page first, or save the event as a draft.
- That event has already ended. You tried to schedule an event whose last time is already over.
VRChat's group calendar
When the event goes to the VRChat calendar, Modbot adds the event to the calendar of the group chosen as Managed group (Settings, Modbot's VRChat login). With no managed group chosen, nothing is sent.
- A repeating event is one entry on VRChat, using VRChat's own repeat, in the event's time zone, with Every, and the last date or the number of times when there is one. It is not one entry per week. Once some of its times have passed, VRChat's entry starts at the next one, so VRChat is sent only the number of times that are left: six times with two over shows as four on VRChat.
- One date cancelled or changed on its own is sent to that one date on VRChat. Modbot reads that month of your calendar (up to three pages) before each change to find VRChat's id for the date, then removes it (a cancel) or changes its time, title and description. If Modbot cannot find that date on its own, the date shows VRChat calendar: Failed when you open it, and the rest of the event is left alone; check the date on VRChat yourself. Cancelling an event's last date finishes the event, and that date is still taken off VRChat. See Changing one date of a repeating event.
- Edits are sent as one. Modbot waits until an event has gone 20 seconds without a change, then sends what it says at that moment. Fixing a typo three times in a row costs one change on VRChat.
- Modbot sends one VRChat calendar change a minute at most, across all events. VRChat is strict about its calendar, so this is kept slow on purpose. If you plan several events at once, they reach VRChat one after another.
- Cancelling or deleting the event, or turning off VRChat calendar, removes it from VRChat's calendar.
- A finished event stays on VRChat's calendar as a past event.
- Changes made on VRChat are read back. See Events made on VRChat.
Events made on VRChat
Modbot reads your group's VRChat calendar, so events someone made on vrchat.com or in the game show up on the Calendar page, in the Upcoming event box on the VRChat page's Overview, and in the calendar feed.
When Modbot reads it. Only when someone is looking:
- when the Calendar page opens, and when you move to dates it has not read yet: one request for each month on screen (a Month view can touch three);
- when the VRChat page's Overview opens: one request for this month, and one for next month when nothing on VRChat is left this month;
- when you click Refresh on the Calendar page.
A month read in the last five minutes is not asked for again, by anyone, unless you click Refresh. Nothing is read on a timer, so the calendar feed only learns about an event made on VRChat after someone has opened one of these pages. A repeating event costs one more request the first time Modbot sees it, and again after it is changed on VRChat, to read how it repeats.
How they show. An event made on VRChat has a VRChat badge next to its status. It is an ordinary Modbot event: with Manage calendar you can open, edit, drag, cancel and delete it, and your change is sent to that same event on VRChat, never as a second copy. It arrives with VRChat calendar and Discord event on, and Discord channel post and Open the instance off; turn them on if you want them. Featured and the picture are copied in with the rest. While you leave them as they came, Modbot does not send Featured or the picture back to VRChat, so an event VRChat features, or one with a picture another person uploaded, is not refused when you edit it; changing the box or the picture sends it. VRChat settings the Modbot form does not have, such as how early hosts may join, are kept as they are when you edit it.
Changed on VRChat. The newest change wins. Modbot copies in a change made on VRChat, for any event, including ones planned in Modbot. If you changed the event in Modbot more recently and Modbot has not sent it yet, your change wins and is sent to VRChat. One exception: for an event planned in Modbot, the title and description are always Modbot's. VRChat changes some characters in the text it is given (for example it drops an en dash), so its copy of the words is not taken as an edit; change them in Modbot. For an event made on VRChat, a change to its words goes into VRChat's own text when the event has one, so the shared words Discord and Google show are not replaced.
Deleted on VRChat. When an event is missing from a month Modbot read, Modbot asks VRChat about that one event. If VRChat says it is gone, Modbot deletes it too, which also ends its Discord event and post. A failed or partial read never deletes anything, and an event that was only moved to another month is updated, not deleted. One exception: if the event was edited in Modbot and that edit had not reached VRChat yet, the edit is newer, so Modbot puts the event back on VRChat. If VRChat answers that it cannot find the picture, that is shown on the event as a refusal and the event is not put back. An event made on VRChat is looked for on VRChat's calendar before Modbot makes it again.
What Modbot cannot hold. Modbot keeps one rule per repeating event, so:
- a change on VRChat to one date only of a repeating event is left on VRChat, and Modbot keeps the series as it was;
- an event repeating every year, or more than 52 days, weeks or months apart, or more than 500 times, is not brought in.
An event that repeats every second week (or every third, and so on) or a number of times on VRChat is brought in with the same Every and Times.
If the read fails, a red line under the page's controls says why, for example VRChat's calendar is waiting on its rate limit. Modbot's own events still show.
When VRChat says no
The VRChat calendar place on the event shows one of:
| State | What is happening |
|---|---|
| Sending… | Being sent: waiting for your edits to settle, for its turn, or for a rate limit to pass. |
| Published | VRChat has the latest version. |
| Failed | Something stopped it. What went wrong is shown beside it, with Try again. |
| Removed | Taken off VRChat after a cancel, a delete, or turning it off. |
Before sending, Modbot checks what it can, and lists every problem it finds together, so you can fix them all at once:
- that Modbot's VRChat account has Manage Group Calendar in your group, with a link to your group's roles on VRChat. Modbot looks at your group every few minutes; when its last look says the permission is missing, Modbot looks once more before saying so, so a permission you just gave is not missed;
- a title and a description;
- that the VRChat image id could be one (see The VRChat picture); only an event saved through the API can fail this, since the form has no box to type an id into.
When any of these is wrong, nothing is sent to VRChat, so none of its strict limit is spent.
What Modbot does next depends on why it failed:
- Modbot's VRChat account lacks Manage Group Calendar. Give the permission to a role Modbot's account has in VRChat (Group settings, Roles). Modbot sends the event by itself the next time it looks at your group, within a few minutes, with no edit. Press Try again to have it look straight away.
- VRChat said "too many requests". Modbot never retries straight away. It pauses all VRChat calendar changes for a while and the place shows Sending…, not Failed. It carries on by itself. You can see the pause under VRChat request limits on Health.
- VRChat refused the event (for example, a field it does not accept). Modbot does not send the same thing again by itself. Fix the event in Modbot and save, and it is sent. Saving with nothing changed, or pressing Try again, sends it again as it is.
- VRChat did not answer, or had a problem on its side. For a change to an event already on VRChat, Modbot tries again after 15 minutes. For a new event, VRChat sometimes adds it anyway, so Modbot looks on VRChat's calendar instead of sending it again: if it is there, the place shows Published; if not, it shows Failed with VRChat did not add the event. and a Try again button, and Modbot sends nothing until you press it, not even after an edit. Try again looks once more first, in case VRChat added it late.
Try again
Every place that failed has a Try again button, for people with Manage calendar: the VRChat calendar, the Discord event, the channel post, the post saying the event is cancelled, and one date's own change on VRChat. It sends it again as it is, without editing the event, and the place shows Sending… until it is done. Use it after fixing the cause outside Modbot, such as a permission in VRChat or Discord.
- One press is enough. The button is off while it sends, and a second press finds the place already being sent.
- Saving the event, even with nothing changed, does the same for every failed place at once: the old failure goes away as soon as you save, and the place shows Sending…. The one exception is VRChat did not add the event., which only its own Try again sends.
- An instance that did not open is tried again with Open now.
Discord
Discord needs the bot to be set up and connected. See Setting up the bot. While the bot is not connected, nothing is sent to Discord, and it catches up once it is.
Modbot checks every 20 seconds and makes at most 5 Discord changes each time, so with many events it can take a little longer.
The Discord event
When the event goes to the Discord event, Modbot makes an event in the server set as Server id (Settings, Discord, Bot). The bot needs the Create Events and Manage Events permissions in that server.
- It has the title, description, start and end, and the picture link (or the world's picture) as its cover. When the event has categories, its description starts with a line such as Categories: Karaoke, Movie night. If the picture cannot be fetched, the event is made without a cover.
- Before the instance opens, its location is the world's name.
- When the event opens, Modbot starts the Discord event. If Modbot opened the instance for it,
the join link goes in it until the instance closes. If it did not (Open the instance
is off, or VRChat refused), the location stays the world's name. Discord only
allows 100 characters for a location, and VRChat's join links are longer. So, while there is a join
link:
- if your Public address is set (Settings, Server), the location is a short Modbot address that sends people on to the instance;
- otherwise the location stays the world's name, and the join link goes at the top of the description.
- When it finishes, Modbot ends the Discord event. When you cancel or delete it, or turn off Discord event, the Discord event is ended too, and disappears from your server.
- A repeating event gets a new Discord event each time it happens. Discord cannot move an event back from started to scheduled, so after each time, the old one is ended and a new one is made for the next time.
- One date cancelled on its own ends that date's Discord event, and the next date gets its own. One date moved, or given its own title or description, has its Discord event changed to match.
- If you schedule an event after its start time, Discord refuses a start in the past, so the Discord event starts one minute from when Modbot makes it.
- If someone deletes or ends the Discord event in Discord, Modbot makes it again the next time the event needs a change there (an edit, or the instance opening).
The short address works without signing in. It only sends people on while the instance Modbot opened is still open; at any other time it answers "not found".
The channel post
When the event goes to the Discord post, Modbot posts a card in the channel you picked, in the same style as instance announcements.
- The card shows your group's name, the title, the description, When and Ends (as Discord times, so everyone sees their own time zone), World, Who can join, Region, and the picture link or the world's picture.
- With categories, a Category or Categories field lists them, in alphabetical order.
- World opens the world's page on vrchat.com, which anyone can open. (Modbot's own world page needs a Modbot sign-in, which your members do not have.)
- The line at the bottom says Scheduled, then Open now with a Join button once the instance is open.
- The side bar is the Colour you picked while the event is Scheduled. Once the date is open it is green, when it finishes it is dark, and when it is cancelled it is red, whatever was picked, so the colour still tells you where the post stands.
- The card is edited whenever the event changes.
- When it finishes, the card says Finished. When you cancel or delete the event, it says Cancelled. The Join button is removed either way.
- A repeating event gets a new post each time it happens. The old post keeps its last word (Finished, or Cancelled for a date cancelled on its own) and a new one is posted for the next time.
- Old posts are deleted a day after the event, or that date, was due to end. That covers every card, whether it says Finished or Cancelled, and the short Cancelled messages from cancelling. Modbot only deletes messages it posted for the calendar. It never touches anyone else's messages, or its own instance announcements and giveaway posts.
- Turning off Discord channel post, or picking a different channel, deletes the post.
- If someone deletes the post in Discord, Modbot does not post it again until the event changes.
Cards from before October 2026 are not deleted, because Modbot did not keep track of them once they said Finished or Cancelled. Delete those by hand. Older Cancelled messages are deleted, a couple at a time.
The bot needs View Channels, Send Messages and Embed Links in the channel.
Mentioning a role
An event can ping one role when its channel post goes up, for example @GameNight for the people who asked to hear about game nights. It is off until you pick a role in Mention role.
- The post shows the role above the card, and pings it once for each date: when that date's post first goes up. A repeating event pings again for each new date.
- Edits never ping. When the event changes, opens or finishes, the post is edited and keeps showing the role, but nobody is notified. If someone deletes the post and Modbot posts it again, or you turn Discord channel post off and on, or you move the event to another date and back, that date is not pinged a second time.
- Only roles the bot may ping. That is a role with Allow anyone to @mention this role turned on (Discord, Server Settings, Roles, the role, Display), or any role if the bot has the Mention @everyone, @here and All Roles permission. Other roles are marked Bot cannot mention in the list, and saving with one says The bot may not mention that role.
- @everyone and @here are never offered, and an event cannot ping them.
- Nothing else Modbot posts pings the role: not the cancel message, and not the post when the first person joins.
The role list is the one Modbot keeps for Settings, Discord. Like the channel list, it needs Change settings to open.
Duplicate Discord events
When several tools make Discord events (another bot that copies VRChat's calendar, a bot of your own, Modbot's calendar, or people by hand), your server's event list can show the same event twice. Modbot looks for this in every Discord event in your server, whoever made it, and lists what it finds under the calendar as Possible duplicates in Discord, and on Health.
Two events count as possible duplicates when:
- their titles match, ignoring capitals, spaces, punctuation, emoji and a bracketed tag at the front (so [VRChat, Group Public] Movie night matches Movie night 🎬, but Game Night (Among Us) does not match Game Night (Minecraft)), or one title contains the whole of the other and the shorter one has at least six letters; and
- they start at most 15 minutes apart.
Each set shows the title and time, then every copy with who made it: the bot's or app's name, Modbot's calendar for the Discord event of one of your Modbot events (with Open to open it), Modbot for another event Modbot's bot made, or A person. People are never named.
Modbot does not delete or change anything. Decide which tool should make your Discord events, turn the others off, and delete the extra events in Discord. To stop Modbot making one, turn off Discord event on that Modbot event.
Modbot reads your server's event list when you open the Calendar page or Health, at most once every five minutes, so a duplicate you just deleted can stay listed for a few minutes. The list needs the bot to be connected; while it is not, nothing is listed.
When Discord says no
The Discord event and Channel post places use the same states as VRChat: Sending…, Published, Failed and Removed, with Discord's error beside a failure. Common errors:
| Error | Fix |
|---|---|
| The bot needs Create Events. (or Manage Events, or both) | The error names the bot's role. Turn the permission named on for that role in Server Settings, Roles. |
| The bot is not in that server. | Check Server id in Settings, Discord, and that the bot has been invited. |
| Discord is rate limiting the bot. | Nothing. Modbot tries again on its next check. |
A refusal that will not fix itself, such as a missing permission, is not sent again by itself. After fixing the permission, press Try again on the place, or save the event; nothing has to change. See Try again. Other failures are tried again on the next check.
Opening the instance
When the event opens the instance, Modbot opens a group instance Minutes early before each start:
- in the event's world, with its Who can join and Region;
- owned by your Managed group.
A date cancelled on its own gets no instance. A date moved on its own opens Minutes early before its new start.
Modbot opens one instance each time the event happens, and never more. It notes the attempt before asking VRChat, so a restart cannot open a second one. If Modbot was down at the opening time, it still opens the instance when it comes back, as long as that time has not ended yet.
Once the instance is open, its join link goes onto the Discord event and the channel post, and the event shows it under Instance. When the instance closes, the link is taken off.
If VRChat refuses, Modbot does not try again for that time by itself. The error shows on the event under Instance, with Open now to try again while the time has not ended, and on Health, and the event turns red. The next time the event happens gets its own attempt.
If the request never reached VRChat, Modbot sends it again while the time has not ended: when it was waiting out a VRChat request limit or signing in, when Cloudflare stopped it, or when VRChat asked Modbot to slow down (only once the limit allows). The event shows Opening meanwhile.
If VRChat failed on its side or did not answer, it may have opened the instance anyway, so Modbot does not send the request again. The event shows Checking… while Modbot looks for a new instance of the event's world in your group. If one shows up, it becomes the event's instance. If none does, the event shows the error, turns red, and it is up to you to press Open now.
Open now
Open now, on the event, opens the instance straight away, through the same path and the same limit. It appears for people with Manage calendar from two hours before a time starts until it ends, while no instance of that time is open: before the opening time, after VRChat refused, or after the instance closed. It does not appear while an earlier attempt is under way or Checking…. It works whether or not Open the instance automatically is ticked. The audit log names who pressed it. Invites and the posts for the first person then follow as usual; after a closed instance, the people not invited yet are invited to the new one.
Modbot opens at most one instance every 5 seconds, which is well within what an event needs.
Inviting people
Once Modbot has opened an event's instance, it can invite people to it, in this order:
- the Host;
- the Staff;
- the people on the Invite list, as the list holds them at the moment the instance opens.
Not every group member: only who you picked. Somebody who is host, staff and on the list is invited once.
Only people who asked get an invite. Nothing is sent to anybody else:
| Who | Gets invites when | How to stop |
|---|---|---|
| The Host and Staff | Their Get event invites switch is on, on their Account page. It is on for every staff account until they turn it off. | Untick Get event invites on the Account page. |
| People on the Invite list | They pressed Get event invites under /me in your Discord server. | Press Stop event invites under /me. |
Turning invites off stops them at once, even for an event whose invites are already going out. While /me is off on the Commands card in your server, members have no way to ask or to stop, so no member counts as having asked, even one who asked before: an invite list reaches its staff only. A member is matched by their Discord account, or by the VRChat account linked to it now. People who did not ask count as Didn't ask for invites.
What is sent, and from where. Everything is sent from your group's own accounts:
- a VRChat invite to the instance, from your group's Modbot VRChat account (the one under Settings → VRChat). VRChat only lets an account invite its friends, so somebody who is not a friend of that account cannot get one;
- otherwise, a Discord direct message from your server's Modbot bot, to people whose Discord account Modbot knows (linked to their VRChat account, or proven on their staff account). It holds the event's title and a Join button, nothing else.
Somebody with neither counts as No way to reach. Somebody whose direct messages are closed counts as Couldn't reach, and is not asked again.
Who is left out: people banned from the group or from the Discord server, and people a moderator's client already sees in the instance.
Who is a friend. VRChat does not give Modbot the whole friends list, so Modbot remembers what it learns: an invite VRChat accepts means a friend, a refused one means not, and the friends VRChat lists when Modbot signs in count as friends. Somebody Modbot knows is not a friend gets the Discord message straight away; after a week, Modbot tries a VRChat invite once more in case they added the account. Somebody Modbot knows nothing about gets one VRChat invite first.
How fast. One VRChat invite every 30 seconds, and a direct message every few seconds. Sending stops when the instance closes or the event ends, so a long list may not get through in time. If VRChat asks Modbot to slow down, Modbot does not ask again for that person: it sends the direct message instead, and waits before the next VRChat invite. If VRChat fails on its side, the invite may have arrived anyway, so that person counts as Couldn't reach and gets no direct message on top.
Nobody is invited twice. Modbot notes each person before it sends, so a restart picks up where it stopped and never sends the same invite again.
The event shows Invited N of M, and under it how many by VRChat invite, by Discord message, Couldn't reach, No way to reach and Didn't ask for invites.
Announce when the first person joins
As soon as VRChat counts somebody in the instance, Modbot posts once each time the event happens:
- with Announce in Discord when the first person joins, in the event's Channel: the event's title and a Join button, from your server's Modbot bot;
- with Announce in VRChat when the first person joins, in your VRChat group's posts, from your group's Modbot VRChat account: the event's title, … has started. and the join link. It is visible to the group, and VRChat does not notify members about it;
- with Announce on Bluesky when the first person joins, as a reply under that date's Bluesky post: We're live in and the world's name, then a link. The link joins the instance when Who can join is Anyone, and goes to your VRChat group's page otherwise. A date with no Bluesky post gets no reply. The reply is sent like any Bluesky post, so Posting, Pause all posting and Bluesky's rate limit apply to it.
For a draft a host approves, or for instances that are not an event's, see Live posts in Settings, Posts.
If Discord, VRChat or Bluesky refuses, or there was no Bluesky post to reply to, the event shows what it said under Instance, and Modbot does not try again for that time.
The calendar feed
The calendar feed is a link people add to their own calendar app (Google Calendar, Outlook, Apple Calendar and others) to see your group's events there. It is only on the page for people with Manage calendar, in the Calendar feed row below the calendar.
- Make link creates the link the first time.
- Copy copies it.
- Add to Google Calendar opens Google Calendar's own page for adding a calendar by its address, with the feed filled in, in a new tab. It adds the feed to the Google account you are signed in to in that browser, for your own use. Google then holds the feed's secret address and reads the feed from its own servers, so the address must be one the internet can reach. It works on a computer, not in Google's phone app, and Google checks the feed on its own schedule, so a change can take a while to show there. To put events on a Google calendar your members follow, use Google Calendar instead.
- New link replaces it. The old link stops working at once, for everyone who added it. Use this if the link got shared somewhere it should not be. Modbot asks Make a new feed link? first; click Make new link to go ahead.
The address
The link looks like this:
https://modbot.example.com/api/calendar/feed/<secret>.icsIt starts with your Public address (Settings, Server). If that is not set, the page uses the address you have open in your browser instead, which only works for others if they can reach that address too.
Who can see it
Anyone who has the link. Opening it needs no Modbot account and no sign-in: the secret part of the address is the key. Share it where you would share your event list, and make a New link if it leaks.
What it contains
The feed lists:
- every event that is Scheduled or Open;
- every Finished event for 30 days after its last time ended, so it stays in people's calendars as something that happened;
- every Cancelled event for 30 days after it was cancelled, marked as cancelled, so calendar apps can show it as cancelled instead of it quietly disappearing.
For each one:
- the title and description;
- the start and end, in the event's time zone;
- the repeat and last date, so calendar apps show every time it happens;
- dates cancelled on their own left out, and dates moved or reworded on their own at their new time and with their own title and description;
- the world's name as the location. A repeating event is one entry in the feed, so for one that picks from a world list, the location is the world of its next date;
- a link to the event on your Modbot calendar page, when your Public address is set (Settings, Server). The link needs a Modbot sign-in, like the page itself.
The calendar is named after your managed group, or Modbot if none is set.
It does not contain drafts, deleted events, the join link, the picture, anything about Discord or VRChat, or anything about your members. When you delete an event, it drops out of the feed. How a calendar app shows a cancelled event is up to the app: some strike it through, some leave it out. Calendar apps check a feed on their own schedule, so a change can take a while to show up there.
Reading the feed asks VRChat nothing, so it does not use any of your group's VRChat requests.
The public feed
The public feed is a second feed that lists only your public events, at an address with no secret in it. Hand it to event directories, put it on your website, or add it in Google Calendar with From URL. Directories that only read VRChat's group calendar, or that want a form filled in, do not need it.
It is off until someone with Manage calendar turns it on, with the Public feed switch below the Calendar feed row. While it is on, its address is beside the switch, with Copy:
https://modbot.example.com/api/calendar/public.icsLike the calendar feed's link, it starts with your Public address (Settings, Server), or the address you have open in your browser when that is not set.
Who can see it
Anyone. Opening it needs no Modbot account, no sign-in and no secret. There is no link to replace: to stop it, turn the switch off. The address then answers "not found" at once, and calendar apps that read it stop getting updates. Turning it on or off is in the audit log, like any other setting.
What it contains
Only events that go to your group's VRChat calendar (the VRChat tab is on) with Visible to set to Everyone, in the form's Where section. Turn it off and the event leaves the public feed, whatever Visible to said. An event that goes only to Google Calendar is not in the public feed; it is on the Google calendar's own public links instead. An event that VRChat shows only to some of your group's roles is left out too.
Of those, it lists the same events as the calendar feed: Scheduled and Open ones, Finished ones for 30 days after their last time, and Cancelled ones for 30 days after the cancel, marked as cancelled. Never drafts or deleted events.
Each entry has the same title, description, times, repeat, changed and cancelled dates, world name and calendar name as in the calendar feed, with two differences:
- No link to your Modbot calendar page. Nobody reading a public feed can sign in to it.
- The join link, only for an event anyone can join (Who can join set to Anyone). It is
your Public address followed by
/api/calendar/join/and the event, the same link a Discord event shows. It leads to the instance while one Modbot opened is open, and to "not found" the rest of the time. An event for Group members or Members and their friends has no link.
It does not contain events visible only to your group, drafts, deleted events, the picture, anything about Discord, or anything about your members.
A change you make in Modbot is in the public feed at once. A change made on VRChat, or an event finishing, can take up to a minute. Calendar apps check a feed on their own schedule, so it can take longer to show there. Reading the feed asks VRChat nothing.
Google Calendar
When the event goes to Google Calendar, Modbot puts the event on the Google calendar named in Settings, Google Calendar, and keeps it in line with the event. Setting it up, and the calendar's own public links, are on the Google Calendar page.
What goes
- The title and description, with a blank line and the world's name and its page on vrchat.com under the description.
- The start and end, in the event's own time zone.
- The repeat and its last date, as one Google event that repeats.
- The world's name as the location, or VRChat with no world.
- The event's colour, when you picked one, and whether it shows as Busy or Free. See Google Calendar settings on the form.
No picture, no join link, nothing about Discord and nothing about your members. Nobody is invited or emailed, and no reminders are set: each person's own Google settings decide those.
An edit reaches Google about twenty seconds after your last change, so several quick fixes are one change there.
Google Calendar settings on the form
The Google Calendar tab draws the event like Google's own event popup. The title and the description are typed straight into it, as described under Title and description. Under it are the event's own Google settings:
| Setting | What it does |
|---|---|
| Calendar | The Google calendar the event goes to. It links to Settings, Google Calendar, in a new browser tab, if you may change settings. |
| Colour | Calendar default, or one of Google's eleven event colours. The colour shows on the preview. |
| Show as | Busy or Free. Free is the default: it is what Modbot has always sent, so an event you do not change stays as it is. A Busy event blocks the time for the people who can see the calendar's free or busy times. |
A change reaches Google at the next sync, like any other edit. Whether people who follow the calendar see the colour is up to their Google settings.
Members only
An event only your members may see never goes to Google, whether Google is on or not: Visible to is Group, or VRChat shows the event only to some of your group's roles. A public Google calendar would show it to anyone. The Google Calendar tab says Members only. Change an event that is on Google to Group, and Modbot takes it off Google.
Cancel, delete and finished events
| In Modbot | On Google |
|---|---|
| Cancel event | Kept, with Cancelled: in front of its title, until a day after the date it was cancelled on; then removed. A repeating event stops at that date. |
| Delete | Removed at once. |
| Finished | Kept, as something that happened. |
| The place turned off | Removed. Turned on again later, the event is added again. |
One date of a repeating event
What happens on Google when you change one date:
| Change | On Google |
|---|---|
| Cancelled | Left out of the repeat. |
| Moved or reworded | That date is changed on its own, to the new time and words. |
| Put back as planned | That date goes back to the repeat's time and the event's own words. |
When you then edit the whole event, Modbot writes the whole repeat again and sends every changed date again after it, so they stay as you left them.
Changes made on Google
Modbot does not read anything back from Google. A change made to the event on Google itself is replaced the next time the event changes in Modbot, and an event deleted on Google is added again then. Edit your events in Modbot.
On the event
Each event says how it went on Google: Google Calendar: Sending…, Published with Open, which opens the event on Google, Failed with Google's own words and Try again, or Removed. A changed date Google refused shows under the date, with Try again.
Bluesky
When the event goes to Bluesky, Modbot posts the event on the Bluesky account in Settings, Bluesky. Setting that up is on the Bluesky page. This is different from the other places: Bluesky gets one post for each date of the event, not one entry that repeats.
When it posts
Post it sets how long before a date starts its post goes: 1 hour before, 1 day before, 3 days before or 1 week before. A new event starts on 1 day before. A one-off event gets one post. A repeating event gets one post for every date, each sent that long before its own start. Modbot makes a date's post when its time comes, so a long series does not fill Marketing with posts weeks ahead.
The posts are ordinary Marketing posts. They go through the same checks as any Bluesky post: the Posting switch, Pause all posting, Bluesky's hourly limit and its rate limit.
An event made or changed after a date's post time has already passed is posted right away, as long as that date has not started. An event made tomorrow with 1 day before is posted as soon as it is saved (after a short moment, so quick edits count as one). A date that has already started gets no post.
What the post says
The title, the time of the date in the event's own time zone, the world's name when the event has one, the description and one link. The link is the event's page on Google Calendar when the event is on Google, else the group's page on vrchat.com. A post holds 300 characters in all: Modbot cuts the description (with an ellipsis) until the post fits, and never cuts the title, time, world or link. Typing in the title or the description on the Bluesky tab's card gives the post words of its own, and a date that was given its own title or description (see Changing one date of a repeating event) shows those words instead.
The post's pictures go with it as full pictures, in place of the link card: up to four, in the order they have in the box, each with its alt text. A picture with no alt text of its own is described by the post's title. Until the pictures of the post are changed in the Bluesky tab, the post goes with the event's cover picture alone. Modbot sends a small copy made when a picture is chosen. A cover chosen before that gets its copy the next time someone who can manage the calendar or templates opens the Calendar page, made in their browser without a word on screen. Until then it goes as it is when it is 1 MB or smaller; otherwise the post has no picture.
The post can carry one video instead of the pictures (see Bluesky settings on the form). It goes up to Bluesky as the post goes out. If it cannot go, the post is made without it, and the post's line in Marketing says why.
Tags
A post ends with a last line of tags. First come the tags of the event's
categories, in the order of the categories' names, then the tags set for
every post in Settings, Bluesky, under Tags on every post (up to five, such as #VRChat; empty
to start). A category's tag is made from its name by default (Dance night gives #DanceNight) and can be
changed on the Event categories page. A tag is never written twice in one post.
A post holds 300 characters. Tags are added after the words, and the words are never cut for them: a tag that does not fit is left out, and so is every tag after it. A post whose description was cut to fit may have little or no room, so it gets few or no tags. The Bluesky tab's preview shows the tags the post will have.
A tag that changes what a date's post would say is a change like any other (see below): when you change a category's tag, rename a category, change a category on an event, or change Tags on every post, the posts of dates that have not started and are already up are deleted and posted again. Anyone who saw, liked or replied to the old ones loses them.
Pin the next event
With Pin the next event on in Settings, Bluesky, the post of the next date that has a post on Bluesky is pinned on the account's profile. When that date ends the pin moves to the next date's post, and with none left it comes off. A post you pinned by hand is left alone. A post that is deleted or made again because the date changed loses the pin, and the next date's post (or the new one, once it is up) takes it. See Pin the next event.
Weekly line-up
With Weekly line-up on in Settings, Bluesky, one post a week lists the next seven days: a line for each date with its day, time and title. It is set by Day, time and Time zone (Monday 12:00 in UTC to start) and takes every date of an event whose Visible to is Everyone, whichever places it goes to and whether or not it goes to Bluesky. A members-only event and a cancelled date are left out. Over 300 characters it lists as many as fit, then +N more, and ends with the public page of the group's Google calendar as the link card when there is one. A week with no dates gets no post, a time more than an hour past is skipped, and the post is left as it is when a date changes or is cancelled afterwards. See Weekly line-up.
Bluesky settings on the form
The Bluesky tab is Bluesky's New post box, with Post it below it. The title and the description are typed straight into the box, as described under Title and description.
- Pictures. The picture button, or dropping pictures on the box, adds up to four. The event's cover is the first picture by default. ALT on a picture opens its alt text, which is up to 2,000 characters and falls back to the post's title while empty. The cross on a picture takes it out. A picture is kept by Modbot as soon as it is added, so Save waits for one that is still uploading.
- Video. The film button under the box adds one video, from a file (an MP4, MPEG, WebM or QuickTime file
of at most 50 MB) or a link (it must start with
https://). It replaces the pictures: with a video the picture button is off, and with pictures the film button is off. ALT on the video opens its alt text, up to 2,000 characters, falling back to the post's title while empty, and the cross takes the video out. A file is kept by Modbot as soon as it is chosen, so Save waits for one that is still uploading, and stays kept until no event, template or post still to be sent uses it. A link is kept only as an address; Modbot downloads the video when the post goes out, and the post goes up without it if that fails. Templates keep the video too. - GIF. The GIF button under the box searches Klipy and adds the GIF you click, in the order Klipy lists them. It is there only once the Klipy key is set under Settings, Bluesky, GIF search, Klipy key. A GIF replaces the pictures or the video: with a GIF the picture and film buttons are off, and with pictures or a video the GIF button is off. Its title is the alt text to start with; ALT opens it to change, and the cross takes the GIF out. Modbot keeps only the GIF's Klipy address, never a copy, and posts it as a link card the way Bluesky's own app does. Templates keep the GIF too.
- Emoji. The smiley button opens a full emoji picker. The emoji goes in at the caret of the title or description you last clicked into, or at the end of the description when you have clicked into neither.
- Anyone can interact. The chip under the post opens Bluesky's own choices for who can reply: Anyone, Nobody, or any mix of Your followers, People you follow and People you mention. Allow quote posts is a tick; clear it to stop other people quoting the post. The chip says what is picked. Anyone with quote posts allowed is the usual, and makes no extra record on Bluesky.
- Language. The button at the bottom of the box opens a list of common languages, up to three, as Bluesky allows. It says Language until one is picked, and then the names. The languages are sent as the post's language, which Bluesky uses to show it to people who read those languages. With none picked the post carries none.
- The ring shows how many of the post's 300 characters are left, and turns red once it is over.
Who can reply and quote posts are sent as two records Bluesky keeps next to the post, made right after it. If Bluesky refuses one, the post stays up and Modbot tries the records again on its next passes; the post's line in Marketing says why until they are made. A sign-in made with Sign in with Bluesky before these choices existed cannot make them: a post that limits replies or quotes waits, and Marketing says Sign in with Bluesky again to let Modbot set who can reply. Click Sign in with Bluesky again once (see Bluesky). An app password already allows it. Posts that anyone can reply to and quote are not held up.
The choices are saved on the event, kept by templates and sent with every date's post. Changing one is a change like any other, so the date's post is deleted and posted again (see below).
Changes, cancelling and deleting
Bluesky cannot edit a post. So when you change what a date's post would say, Modbot waits for about 30 seconds after your last change, then:
- a post not sent yet is simply rewritten;
- a post that already went out is deleted on Bluesky and posted again, as a new post, with the new words. Anyone who saw, liked or replied to the old one loses it.
| In Modbot | On Bluesky |
|---|---|
| A date's time changes | The old date's post is deleted; the new date gets its own. |
| Cancel event, or This date of a repeating event | The post is deleted, and none is made. Nothing says it was cancelled. |
| Delete | The posts are deleted. |
| The place turned off | The posts are deleted. Turned on again, they are made again. |
| A date has started or passed | Its post stays as it is. |
A post you delete or cancel yourself in Marketing is not made again until the event changes.
Modbot deletes at most three posts from Bluesky in one pass. A delete Bluesky refuses is tried again after two minutes. While Bluesky is limiting Modbot, nothing is deleted, and a delete is never sent again for that.
While Posting is off, nothing happens. With Posting off in Settings, Bluesky, or Pause all posting on, Modbot makes no post and takes none down. That includes a cancelled event: its post stays up on Bluesky until Posting is on again, and is then deleted. Delete it from Marketing, or on Bluesky, if it cannot wait.
Event categories
See Event categories, which also covers the alerts members sign up for.
Templates
A template is a name and everything the event form holds, except when the event happens: the title and description, the text each site says for itself, the places it goes, the category, tags, languages and platforms, the world or world list, who can join, the picture, the Bluesky post's pictures and their alt text, who can reply to it, quote posts and its languages, the repeat pattern, the channel post, and the instance settings. In place of a start, an end and a time zone it has a Length, from 1 minute to 7 days. A repeat keeps its pattern but no last date.
The Templates card sits under the calendar, below Drafts. It lists each template by name, with its title and length. Anyone with Manage calendar or Manage templates sees the list. Only Manage templates shows New template, Edit and Delete.
New template and Edit open the event form with a Name above the title, Length under When, and Save and Cancel at the bottom. It has the same tabs as the event form, with the cards drawn for a made-up start. There is no Schedule or Save draft, and a repeat can end Never or After a number of times. A template can be saved half filled in: the title, the channel and the world may stay empty (Save does not ask for a world list, even with VRChat on), and an event made from it is refused for them instead. The rest is checked as it is for an event. Modbot asks Delete “…”? before it deletes a template. Events already made from a template do not change when it does.
Manage templates is enough to pick an Invite list on a template, without See members and See profiles; the list's name is all the form shows, never who is on it. Picking a list on an event still needs See members and See profiles. So when somebody without them uses a template that has a list, the new event opens with Invite list empty.
Each change is in the audit log.
Fill-ins
A template's text can hold blanks that you fill in each time you use it, such as Host or What. In the template form, the Fill-ins row lists them: click a name to put it where the cursor was last, or type a name in New fill-in and click Add. A blank shows as a box with its name in the title, the description and each site's own text, and you delete it like a letter. The same blank may stand in as many texts as you like. Names do not mind capitals or extra spaces, and are at most 40 characters.
The template form also shows the Categories you made in Modbot, so a template keeps them. A category deleted since is left out when the template is used.
Automatic links
The Links row, in the template form and in the event form, puts a link where the cursor was last. There are four, each shown as a box with its name:
| Link | What Modbot puts in its place |
|---|---|
| Google event | This event on the Google calendar. |
| Discord event | This event's Discord event. On a repeating event it is the current date's event. |
| Add our Google calendar | The page that adds the server's Google calendar, once Settings names a calendar that is public. |
| VRChat group page | The group's page on vrchat.com, once a group is set up. |
You never type these in when you use a template: Modbot fills them when the event is sent. They work in descriptions only (the main description and each site's own description), not in titles: a title is shown as it is in lists, reminders and posts, so the Links row does not put a link in one, and a link name typed or pasted into a title stays plain words. A fill-in such as Host still works in a title. Links show on VRChat, Discord, Google, Bluesky and in the calendar feed. Discord's own text leaves out only the Discord event link, which would point at itself there. Bluesky leaves it out too: that link is the current date's, not the date the post is about.
An event is not on Google or Discord until its first publish, so Google event and Discord event are left out of what is sent first; once the address is known the texts are sent again by themselves, the way an edit is. A link that cannot exist (no public Google calendar, no group) is left out the same way: Modbot also removes the spaces before it, and a line with nothing else on it, so no half-written sentence is sent. The link to a group's own invite page, or to its instances, is not automatic: type it into the text.
On a repeating event, Discord event is the Discord event of the current date. Each time the date moves on, VRChat and Google are updated once, with the new address; until the new date's Discord event exists they keep the address they have, so there is no update without the link in between. A date you changed on its own (its own times or words) does not hold the Discord event's address, so it is not sent again every time the date moves on.
Add our Google calendar follows the Public line from the last Check in Settings. A Check that cannot tell (Google would not list who the calendar is shared with) keeps the answer from before, so the link does not disappear and every event is not sent again.
Use a template
With Manage calendar, Use template sits beside New event once there is a template. Pick the template and type a value into the box for each fill-in; every place that blank stands is filled in, in the title, the description and each site's own text. Click Use and the form for a new event opens, filled in from the template, with the next whole hour as its start and the end set by the template's length. Nothing is saved until you save it. A fill-in left empty is not accepted: Modbot tells you which ones to fill in.
Save an event as a template
With Manage templates, Save as template in an event's details opens the template form filled in with that event's details and its length, with no dates. Give it a name and click Save. It is a copy: the event does not change.
Editing, cancelling and deleting
Edit
Open the event and click Edit. The form opens with Save (and Save draft too, while it is still a draft). Changes reach every place by themselves: VRChat after 20 seconds without further changes, Discord on its next check. A place that had failed shows Sending… as soon as you save, and is sent again even if nothing it shows changed.
For a repeating event, Edit first asks This date or All dates. All dates opens the form for the whole event. This date opens a smaller form for the date you clicked; see Changing one date of a repeating event.
- A published event cannot go back to being a draft.
- A cancelled event cannot be edited.
- To run a Finished event again, edit it and give it new dates.
Cancel
Cancel event is shown for a Scheduled or Open event. Cancelling it:
- removes it from VRChat's calendar;
- ends the Discord event, which then disappears from your server;
- changes the channel post to Cancelled;
- marks it cancelled in the calendar feed, where it stays for 30 days;
- puts Cancelled: in front of its title on Google Calendar, until a day after its date;
- stops any future instance from opening.
Modbot asks Cancel “…”? first; click Cancel event to go ahead.
Telling members. Changing the old channel post does not notify anyone. When the event has a channel, the question has a tick, Post that it's cancelled in the channel. It starts ticked when the event has Discord channel post on. Leave it ticked, and Modbot posts a short message in that channel: the event's title, its date and time (in each reader's own time zone), and Cancelled. It is posted once, within about 20 seconds, and never again for that event. On the event it shows as Cancelled post: Published. A day after the event was due to end, Modbot deletes it, together with the old card, and it shows as Cancelled post: Removed. Untick it to cancel without a message.
A cancelled event no longer appears on the calendar, and cannot be un-cancelled. To run it again, plan a new event.
For a repeating event, Modbot asks Cancel “…”? with This date and All dates. All dates cancels the whole event, as above. This date cancels only the date you clicked; see Changing one date of a repeating event. The Post that it's cancelled in the channel tick is there too, for either choice: with This date, the message gives that date's time.
Changing one date of a repeating event
You can cancel, move or reword one date of a repeating event and leave every other date as it is: for example, skip the week of a holiday, or start one week an hour later.
- Cancel one date: open the date, click Cancel event, then This date.
- Move one date: drag it and choose This date, or open it, click Edit, then This date, and change Starts and Ends.
- Give one date its own title or description: open it, click Edit, then This date. Leave a field as the event's own to keep following the event when you change the event later.
These choices show only for a date that has not ended yet, of an event that is Scheduled or Open. A date cannot be moved to start at the same time as another date of the same event. Once a date has started (or its instance has opened early), only its end can change: That date has already started. For an event on VRChat's calendar, a date cannot move to or past the date before or after it: Can't move a date past the next date on VRChat. Cancel the date and plan a separate event instead.
What happens to that one date:
| Place | Cancelled | Moved or reworded |
|---|---|---|
| Calendar page | Shown struck through, with a Cancelled badge when opened. | Shown at its new time; opening it shows Moved from …. |
| VRChat calendar | That date is removed. | That date is changed. |
| Discord event | Ended; the next date gets its own. | Changed to the new time and words. |
| Channel post | Its last word is Cancelled. Deleted a day after the date was due to end, with the short Cancelled message. | Edited to match. |
| Opening the instance | No instance opens. | Opens Minutes early before the new start. |
| Calendar feed | Left out. | Shown at the new time, with its own title and description. |
| Google Calendar | Left out of the repeat. | That date is changed on its own. |
| Past events | Not listed. | Listed at the time it ran. |
Undo. After dragging one date, Date moved · Undo shows at the bottom of the screen; Undo puts that date back. A date you move back to exactly its planned time, with the event's own title and description, is a normal date again.
Cancelling a date cannot be undone from the page. Its other dates are not affected.
Then editing the whole event. If you later change the whole event's times (with All dates or Edit), each changed date follows the event to the same day: cancel one Sunday, then move the event from 8 PM to 9 PM, and that Sunday stays cancelled. A changed date on a day the event no longer has (for example, the event moves from Sundays to Mondays) is dropped. Dates that are over are left as they ran.
Delete
Delete is shown for every event, including drafts. For an event that is still Scheduled or Open, deleting does everything cancelling does, and also hides it from the Calendar page and takes it out of the calendar feed at once. Its channel post changes to Cancelled straight away, and is deleted a day after the event was due to end, like any other old post. A deleted Finished event is also removed from VRChat's calendar.
Modbot asks Delete “…”? first; click Delete to go ahead. There is no way to bring a deleted event back from the page. Its history stays in the audit log.
On Health
The Health page (See the operational log) shows calendar problems for events that are Scheduled or Open:
- A Calendar card appears when something failed. Each line reads: the event's title, the place (VRChat calendar, Discord event, Channel post, Google Calendar or Instance), the error, and how long ago. An Instance line means the instance for the current time did not open.
- Not set up lines in the same Calendar card name each place an event wants that cannot work yet (see Where it goes): for example Discord event · Not set up, linking to the setting that is missing. Google Calendar · Not set up shows while events are ticked for it and Google Calendar is not set up, or Keep Google updated is off. Bluesky · Not set up shows while events are ticked for it and Bluesky is not set up, or Posting is off.
- Google Calendar · limited until … in the same card means Google asked Modbot to slow down. Nothing is sent to Google until then; the events wait and go after.
- Possible duplicates in Discord lines in the same Calendar card name each set of duplicate Discord events, its time and who made the copies, and lead to the Calendar page. These show even when Modbot has no events of its own.
- Missing Create Events, Missing Manage Events or Missing Create Events and Manage Events appears in the Discord bot card when an event has Discord event on and the bot does not have that permission, or those permissions, in your server.
A place that is only Sending… because of a VRChat rate limit is not a problem and is not listed here. Look at VRChat request limits on the same page instead.
In the audit log
Every change to the calendar is recorded in the audit log, with the operational entries (you need See the operational log to see them):
| Entry | When |
|---|---|
| Event planned | Someone created an event, as a draft or scheduled. |
| Planned event changed | Someone edited or dragged it. Shows what changed; a change of time alone reads as moved the event … from … to …. |
| Planned event cancelled | Someone cancelled it. Says whether it was posted in the channel. |
| One date of an event cancelled | Someone cancelled one date of a repeating event. Shows which date. |
| One date of an event changed | Someone moved one date of a repeating event, or gave it its own title or description. |
| Planned event deleted | Someone deleted it. |
| Planned event opened | One of its times started (or its instance opening time came). |
| Planned event finished | Its last time ended. |
| Instance opened for an event | Modbot opened the instance. |
| Instance for an event failed to open | VRChat refused to open it. Shows VRChat's error. |
| Event failed to publish | A place failed. Shows which place and the error. |
| Event published | A place has the event now: VRChat's calendar, the Discord event, the channel post, Google Calendar, or the message that it is cancelled. Written once when it first gets there, not for every edit after. |
| Event taken down | A place that had the event no longer has it, after a cancel, a delete or turning it off. Not written for a place the event never reached. |
| Event picture uploaded to VRChat | Someone uploaded a VRChat picture. Names the event when it was already saved; for a new event, the event's own Event planned entry carries the same picture. |
| Calendar feed link replaced | Someone made a feed link, or a new one. |
| Event template made, Event template changed, Event template deleted | Someone made, edited or deleted a template. |
| World picked for an event | A world was picked from the event's world list: by Modbot for a date, with Pick again, or with Next game. |
| Event category made | Someone made an event category. |
| Event category renamed | Someone renamed one. Shows the name before. |
| Event category deleted | Someone deleted one. Shows how many events carried it. |
| Event alert sent | Members were told before an event. Shows how many by direct message and by ping, how many direct messages were closed, how many failed and how many were skipped, never who. |
Each invite is recorded too, about the person who was invited, with the moderation entries (you need See the audit log):
| Entry | When |
|---|---|
| Invited to an event | Modbot sent a VRChat invite or a Discord message. |
| Event invite failed | Neither got through. Shows what VRChat or Discord said. |
For events read from VRChat, the entries say so instead of naming a person: Modbot added the event “…” from VRChat's calendar, The event “…” was changed on VRChat: … and The event “…” was deleted on VRChat.
Common problems
The VRChat calendar place stays on Sending…. Modbot sends at most one VRChat calendar change a minute, and waits 20 seconds after your last edit. With several events queued, give it a few minutes. If it still waits, VRChat may have asked Modbot to slow down; check VRChat request limits on Health. Also check that a Managed group is chosen.
Nothing happens in Discord. Check that the bot is connected on Health, that Server id is set, and, for the Discord event, that the bot has Create Events and Manage Events. After fixing a permission, press Try again on the place.
VRChat calendar still says Modbot needs Manage Group Calendar after you gave it. Check that the role you changed is one Modbot's VRChat account has: the message names the account's roles. Then press Try again, which looks at your group's roles again before sending.
The same event shows twice in Discord's event list. More than one tool is making Discord events. Check Possible duplicates in Discord under the calendar to see which ones, then see Duplicate Discord events.
The role was not pinged. Check that the role is open to mentions, or that the bot has Mention @everyone, @here and All Roles (see Mentioning a role). A date is pinged only once: an edit, or a post made again for the same date, does not ping.
The Discord event shows the world's name instead of a link. The instance is not open yet, or Modbot's Public address is not set. Without it, the join link is at the top of the Discord event's description instead.
The instance did not open. Check Instance on the event for VRChat's error. Modbot does not try again for that time by itself; fix the cause and press Open now, or open it yourself in VRChat. The next time the event happens, Modbot tries again.
An event made on vrchat.com is not on the page. Click Refresh. If it repeats every second week or every year, Modbot cannot hold it (see What Modbot cannot hold). Check also that a Managed group is chosen.
My edit on VRChat's website disappeared. Someone changed the same event in Modbot more recently, and the newest change wins.
The feed link stopped working. Someone clicked New link. Copy the new link from the Calendar page and add it to your calendar app again.