Forum log channels¶
Send logs to a Discord forum instead of a text channel. Each log becomes its own post, named after the event and the person it is about, and tagged so your staff can filter the forum by category or event. Forums work on any server; it doesn't need to be a Community server.
You can mix the two: send busy categories to a forum and keep the rest in text channels.
Requirements¶
| Requirement | Details |
|---|---|
| Your access | Administrator to route logs to a forum or add tags; Manage Server or higher to view routing. |
| LogDog in Discord | In the forum: View Channel, Send Messages (shown as Create Posts in a forum's settings), Embed Links, Attach Files, and Read Message History. Manage Channels to create forums during setup or to add tags. Manage Threads only to apply moderator-only tags. |
| LogDog in VRChat | View Audit Log. |
| Plan | Free. |
What a post looks like¶
| Part | What it shows |
|---|---|
| Title | The event and who it is about, such as Member Join · TurboTinyTwigg or Instance Kick · J4CK4L_. An event about nobody in particular names who did it, such as Group Update · Plaz5. |
| First line | VRChat's own sentence for the event, such as User TurboTinyTwigg has been added to the group by Plaz5. Discord shows this line as the post's preview in the forum list. |
| Embed | The same log message a text channel gets, with the same buttons: Add reason, Ban, Approve, and the rest. |
| Tags | The forum's tags named after the log's category or event, up to five. |
Event pings go above the first line, so pinged roles are notified the same way as in a text channel. Reasons and other later updates edit the post's message, as they do in a text channel.
A post archives after an hour without activity. Archived posts stay in the forum and in search, and pressing a button on one reopens it. Archiving keeps your server well below Discord's limit of 1,000 active posts.
Set it up¶
During setup¶
Under How should LogDog post your logs?, choose A forum. The layouts work like this:
| Layout | With a forum |
|---|---|
| Express | One #vrc-logs forum for every log, with a tag per category. |
| Prebuilt | One forum per category, each with a tag per event. Deselect any categories you don't want. |
| Custom | Route each category to a forum or a text channel you already have. |
LogDog creates its forums in a private LogDog category, as it does its text channels.
Forums can't hold LogDog's own messages, so setup also asks where those go; see
Set up LogDog.
/setup in Discord asks the same questions.
On a server that is already set up¶
Choose a forum as the channel for a category or an event in
Log routing or /events, the same way as a text channel. The channel
picker lists forums along with your text channels. Then add the tags (below).
Tags¶
LogDog tags each post with every forum tag named after its category or its event. Matching
ignores case, spaces and punctuation, so a tag called Group Admin, group-admin or
Group / Admin matches the Group / Admin category. An event matches its short name, such
as Instance Kick for Group Instance Kick.
- A post gets at most five tags, the most Discord allows.
- Moderator-only tags are applied only if LogDog has Manage Threads in the forum.
- A log with no matching tag is posted without tags, unless the forum requires one (see A forum that requires tags). Log Routing points out categories with no matching tag.
- LogDog only tags a post when it creates it. Tags your staff add later, such as Handled, are left alone.
Let LogDog add the tags¶
On the dashboard:
- Open Log Routing and find a category that is routed to a forum.
- Open Forum tags. LogDog lists a tag for each category routed to that forum and marks the ones that are already there.
- Optionally, under Give an event its own tag, tick the events that should get their own tag.
- Select Add tags.
In Discord, run /events, open a category that is routed to a forum, and press
Add forum tags. This adds a tag for each category routed to that forum.
A forum holds up to 20 tags, and each tag name can be up to 20 characters, so events with longer names can't have their own tag. LogDog needs Manage Channels in the forum to add tags.
How fast posts appear¶
Discord limits how quickly a bot can create posts in one forum: 10 every 10 seconds and 50 every 5 minutes, which is up to 600 posts an hour. When a group is busier than that, logs wait their turn and post shortly after, in order. Nothing is dropped. While logs are waiting, the dashboard's Overview says they are waiting behind Discord's post limit.
If one forum is often busy, give the busiest categories their own forums (Prebuilt does this for you), or keep them in text channels.
A forum that requires tags¶
A forum with Require tags turned on refuses posts without a tag. If none of its tags matches a log, LogDog applies one of the forum's tags it is allowed to use, preferring one that isn't moderator-only.
If the forum has no tag LogDog may use, every post would be refused, so LogDog won't route
logs there: Log Routing, /events and setup refuse that forum and say why. If the forum's
tags change later, Log Routing marks the route needs a tag and the Overview says the
forum requires a tag LogDog can't apply.
To fix it, add a tag to the forum that isn't moderator-only, or turn off Require tags in the forum's settings.
Troubleshooting¶
- Posts have no tags: add them from Forum tags, or name your own tags after the categories.
- Posts arrive late: check the Overview for the waiting notice; see How fast posts appear.
- Logs stopped arriving: check Log Routing for a route marked needs a tag or unpostable, then Diagnostics for LogDog's permissions in the forum. See No logs arriving.