Reading your logs¶
Every event LogDog delivers is a Discord embed. Once you know the layout, each one tells you who did what, to whom, and when — at a glance.
Anatomy of a log embed¶
- Author line (top) — your group's name, short code, and icon. Click it to open the group on VRChat.
- Title — the event, in plain language (e.g. Group Member Join, Group User Ban).
- Color — the event's severity:
Informational — routine activity.
Warning.
Negative action — bans, kicks, removals.
Positive action — joins, accepts, unbans.
Gray action — neutral/administrative.
- Fields — the details for that event: the user(s) involved (linked to their VRChat profiles), who performed the action, roles, instance/world info, and so on.
- World image — instance events include the world's picture when LogDog has it cached.
- Footer — the VRChat user IDs involved and the audit Log ID, plus the timestamp.
User and world names are clickable links to their VRChat pages wherever LogDog has an ID.
Adding a moderation reason¶
For moderation events (bans, kicks, removals, and similar), each embed carries an 📝 Add reason button. Any server admin can click it, type a reason, and it's recorded on the embed — showing who added it (and who last edited it). It's a lightweight way to keep your "why" attached to the "what," right in the channel.
Where events land¶
Which channel an event appears in depends on the layout you picked in /setup:
- Express — requests, instance activity, and everything else split across three channels.
- Prebuilt / Custom — routed by category to the channels you chose.
Want to change routing or what's delivered? See /events and Managing your configuration.