Logging Redefined

Per-event audit trail for 22 server events, each with its own toggle and optional log target.

Overview

Each event type can log to a text channel or a forum thread. Toggle only what you need to avoid noise.

Forum channels require the thread snowflake, not the parent forum channel ID.

Setup

  1. Enable Logging.
  2. Set default log channel (text/announcement).
  3. For forum logging: create a thread, copy its ID, paste into Thread ID field.
  4. Enable individual event types (message edit/delete, voice join/leave, etc.).

Forum thread logging

Right-click the forum thread → Copy Thread ID. Paste into the module field labeled for forum/thread targets.

The bot validates channel type on save. Wrong IDs show an error in the dashboard.

Tip

Use one thread per log category (mod log, voice log) for readability.

Event toggles

  • Member join/leave: enable the module and set the right channels.
  • Message edit/delete: module enabled; bot needs read access in that channel.
  • Voice join/leave/move: voice channel permissions for bot.
  • Moderation cases: enable when using Moderation module for unified audit.

Usage

Logging is passive: no member commands. Events appear as embeds or compact messages depending on event type.

Troubleshooting

  • Nothing logs → module enabled? event toggle on? channel/thread ID valid?
  • Forum errors → paste thread ID, not forum channel ID.
  • Missing message content → check the module is enabled and the bot has permission to read/send in that channel.
  • Duplicate logs → disable overlapping event types you do not need.