Event categories
Your own labels for events, such as Karaoke or Movie night, and the alerts members can sign up for.
VRChat gives an event one category from a fixed list. Event categories, under Community in the sidebar, are your own: Karaoke, Open mic, Movie night, whatever your events are. An event can carry any number of them.
| To do this | Use |
|---|---|
| Make one | New category, a name of up to 40 characters. Two categories cannot have the same name, whatever the letter case. |
| Rename one | Rename. Every event that carries it shows the new name, and Discord's posts follow on their next update. |
| Set its Bluesky tag | Bluesky tag, in the same form. It starts as the name's words joined, so Dance night is DanceNight. Type another to use that instead, or empty it for no tag. A tag keeps to letters and digits (a # or a space you type is dropped), up to 64 characters, and cannot be only digits. Until you type one, a rename changes the tag with the name. |
| Delete one | Delete. Events that carried it keep everything else, and Discord's posts drop its name on their next update. |
The tags end the Bluesky posts of events that carry the category; see Tags on the calendar page.
Each category shows how many events carry it, not counting events that were deleted. With none made the page says No categories. Making, renaming and deleting are in the operational log. Categories are picked on the event form, under Categories.
The page's address is /event-categories, and the command palette finds it as Event categories,
or by words such as karaoke or labels. With See calendar the page lists the categories and
nothing more; New category, Rename, Delete and the Alerts card below appear only with
Manage calendar. Deleting asks you to confirm and says how many events carry the category.
Nothing on this page asks VRChat or Discord anything. The places an event goes pick up a new or changed name the next time they update the event.
Event alerts
Members of your Discord server can sign up for a category and be told shortly before an event that carries it starts. Alerts are off until someone with Manage calendar turns them on, in the Alerts card at the top of the Event categories page.
| Setting | What it does |
|---|---|
| On | The master switch. Off (the default), nothing is queued or sent, the Notify me button comes off the channel posts and /notify is not registered in Discord. |
| Direct message | Members can be told by direct message. On by default. |
| Ping | Members can be told by a post in a channel that mentions them. Off by default. Turning it on needs a channel; Ping channel appears when it is on. |
| Minutes before | How long before the start an alert goes: 5 to 1,440. 60 by default. |
Save alerts saves all five together. Each setting that changed is in the operational log.
How members sign up
/notifyopens a form with the categories to tick. The ones a member already ticked stay ticked. When both ways are on, the form also asks how to be told: Direct message or Ping in a channel. Sending it replaces the member's sign-ups with what is ticked; nothing ticked takes them all off. The form lists up to 25 categories, the first 25 by name.- Notify me is a button under each event's channel post, there only while alerts are on. Pressed, it signs the member up for the categories the event carries, or for that one event when it has none. Pressed again by a member who is already signed up for all of that, it takes the sign-ups off.
Both answer only the member who used them. Nobody needs a Modbot account.
What goes out
- One alert per member per event date. A member signed up through several categories of one event is told once. A repeating event alerts for each date, once.
- Direct message: Title starts, the time in the member's own time zone and how long until
it starts, with a Join link where
/eventswould show one. - Ping: one post in the channel you picked with the same words, mentioning the members who chose ping. A long list is split into several posts.
- A member whose way is switched off in the settings is told the other way when that is on, and otherwise not at all.
- Cancelled and deleted events send nothing, and an alert still waiting for one is dropped. A date cancelled on its own sends nothing either.
- Moving an event. An event that happens once alerts once, even if its start moves after the alert went. A date that moves before the alert is queued is alerted at its new time.
- Members who left the server are skipped.
- A closed direct message is not tried again. Nothing else is retried either: an alert that Discord refuses is counted as failed.
- Turning alerts off leaves the waiting ones where they are. They go if alerts are turned on again before the event starts, and are dropped after.
Each finished alert is one entry, Event alert sent, in the operational log. It names the event and the date and counts what happened: how many went by direct message, how many by ping, how many had direct messages closed, how many failed and how many were skipped. Closed and failed are counted separately. It names no member. Privacy says what is kept.
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.
Google Calendar
Connecting Modbot to a Google calendar your group owns, putting your events on it, and handing out the calendar's public links.