Instance notices¶
Post a message when a group instance opens, optionally mention staff or members, and update that message with player counts and closure details.
Requirements¶
| Requirement | Details |
|---|---|
| Your access | Administrator to configure; Manage Server or higher to view dashboard settings. |
| LogDog in Discord | View Channel, Send Messages, and Embed Links in the notice channel. Ping roles must be mentionable, or LogDog needs Mention @everyone, @here, and All Roles. |
| LogDog in VRChat | View Audit Log for opening events. Instance visibility affects player counts and closure checks; review Join Group Instances in Diagnostics. |
| Plan | Notices, pings, and display toggles are free. Premium adds customization and a minimum-player threshold. |
Set up on the dashboard¶
- Open Settings → Instance notices.
- Choose a channel and enable Post a notice when an instance opens.
- Choose any roles to ping and which instances to announce.
- Set the display options. These controls save as you change them.
Set up in Discord¶
Run /config → Instance Notices for the same settings.
| Setting | What it does |
|---|---|
| Channel | Where LogDog posts notices; required before enabling. |
| Roles to ping | Up to five roles mentioned with a notice. |
| Announce | All group instances, or only Public and Group+ instances. |
| Join links | Show the Open in VRChat button. |
| Live player count | Update the player count while the instance is open. |
| Mark closed | Update the message when the instance closes. |
What members see¶
The notice shows the world image, opener, access type, and age restriction when available. The player count starts as Just opened until an instance check provides a count. Open in VRChat opens the instance's launch page; members still need permission to join.
With Mark closed enabled, the same message changes to Instance closed, loses its join button, and shows duration and peak players instead of the live count.
Timing and limits¶
Opening notices depend on the VRChat audit check, normally about every ten minutes. Closure updates depend on instance checks and may take another ten to twenty minutes. Platform errors or lost access can delay either.
- The same world is not announced again within ten minutes.
- If an instance briefly disappears from a check and returns, LogDog can reopen its original message instead of posting another.
- Opening events more than 30 minutes old are skipped. A recent event recovered after a short delay may still produce a notice.
Premium options¶
Premium adds a title template ({world} inserts the world name), custom blurb, color,
and image. Use Save notice appearance after editing these fields on the dashboard.
Post once N players are in waits until LogDog observes the chosen player
count before posting. The threshold uses the counts available to LogDog, which can be
limited by instance visibility.
For a single message listing all currently visible instances, use the open-instances panel. For recorded history, see Instance activity and turnout.