Reading your logs¶
LogDog posts VRChat activity as Discord messages called embeds. Each shows the event, who was involved, and when it happened. To search recorded history, use VRChat Audit Logs on the dashboard.
Requirements¶
| Requirement | Details |
|---|---|
| Your access | Channel access to read Discord logs. Manage Server or higher to browse dashboard logs. Editing reasons needs Administrator on the dashboard; Discord also accepts the Add/edit moderation reasons feature grant. |
| LogDog in Discord | View Channel, Send Messages, Embed Links, Attach Files, and Read Message History in log channels. |
| LogDog in VRChat | View Audit Log. |
| Plan | Free; Premium adds custom colors and more reason presets. |
Anatomy of a log embed¶
- Author: the group's name, short code, icon, and link to VRChat.
- Title: the event name, such as Group Member Join or Group User Ban.
- Color: the configured event level. Defaults are blue for informational events, yellow for warnings, red for negative actions, green for positive actions, and gray for neutral actions. For example, unbans use yellow by default. See the event catalog for each event's level.
- Fields: users, moderator, roles, world, or other details relevant to the event.
- Footer: user IDs and the audit Log ID. The timestamp shows when the event happened.
User and world names link to their VRChat pages when LogDog has an ID. Premium color customization can override the default colors.
What the user embeds add¶
When available, user events include avatar, trust rank, age-verification status, account creation date, linked Discord account, and history in your group. Joins, requests, and invites also show the bio. Member since may read Before LogDog was added when the join date is unknown.
Moderation History or User History opens the user's dashboard page. The viewer still needs dashboard access; seeing the Discord message does not grant it.
What the instance embeds add¶
Instance-open logs show the world, access type, region, capacity, and previous visits when recorded. Instance-close logs can include duration, peak players, and average players. View Instance Stats opens the recorded session; it may be unavailable until LogDog has recorded the instance. See Instance statistics.
Adding a moderation reason¶
On the dashboard¶
Open VRChat Audit Logs, select a moderation event, then choose Add reason or Edit reason. This requires Administrator. The saved reason also updates the Discord log message when that message is available.
In Discord¶
Select Add reason or Edit reason on the moderation log. Choose a preset or enter custom text. The log records who added the reason and who last edited it.
To allow a staff role to edit reasons in Discord, use Settings → Feature Permissions
or /permissions add reasons <role…>. This grant does not permit dashboard editing.
Reason presets¶
Edit presets under Settings → Reason presets on the dashboard, or
/config → Moderation → Edit reason presets in Discord. Enter one per line. Add
(requests) or (moderation) after a preset to limit where it appears. Restore defaults
restores LogDog's starter list.
Free servers can save 10 presets; Premium allows 25. When entering a reason, Custom lets staff type their own text. Text entered alongside a preset adds detail beneath it.
Act on a log¶
- Warn and kick logs offer Ban; ban logs offer Unban. See Banning users.
- Request logs offer Approve, Deny, and Deny & Block. See Join requests.
/getmodhistoryshows recorded history about one user. See Moderation history.
Each action has its own staff and VRChat permission requirements. Use the permissions matrix to check them.
Pings and destinations¶
Change channels under Log Routing, or with /events → Channel in Discord.
Choose event pings in Log Routing → Pings or with /notify.
See Log routing and Event pings.