Every event that Burger Bot logs is delivered as a rich Discord embed — a structured, color-coded message that makes it easy to scan your audit log channel at a glance. Each embed type is purpose-built for its event category, surfacing the metadata that matters most for that specific action.
Embed Structure
All Burger Bot audit log embeds share a consistent structure:
| Embed Element | Content |
|---|
| Color | Color-coded by event category (e.g., green for joins, red for bans, yellow for edits) |
| Title | Short label describing the event (e.g., “Member Banned”) |
| Description | The main event details — see examples below |
| Footer | Event ID and exact UTC timestamp |
| Thumbnail | The relevant user’s avatar, where applicable |
| Author | The moderator or actor responsible for the action, where applicable |
Example Embeds
The following examples show the description field content for three common log types.
Member Join
👤 User: @NewUser#1234 (ID: 392847561029384)
📅 Account Age: 14 days old
📆 Joined At: June 12, 2025 at 03:42 PM UTC
⚠️ New Account: Yes — account is less than 30 days old
The “New Account” warning flag is automatically added when a joining member’s account was created less than 30 days ago. This is a helpful signal for spotting potential alt accounts or raiders.
Member Ban
🔨 Banned User: @TroubleUser#5678 (ID: 847392016284739)
🛡️ Moderator: @AdminSarah#0001
📝 Reason: Repeated rule violations after two prior warnings.
📆 Banned At: June 12, 2025 at 04:15 PM UTC
🔗 Case ID: #BAN-00142
Message Delete
🗑️ Deleted In: #general (ID: 102938475610293)
👤 Author: @ChatUser#9012 (ID: 918273645019283)
📝 Content: "hey everyone check out this totally legit link..."
📆 Deleted At: June 12, 2025 at 04:22 PM UTC
👮 Deleted By: @Moderator_Jake#3344 (if detectable)
Color Coding Reference
Burger Bot uses a consistent color system across all audit log embeds:
| Color | Event Category |
|---|
| 🟢 Green | Member join, role granted, channel created |
| 🔴 Red | Member ban, member kick, channel deleted, role deleted |
| 🟡 Yellow | Message edit, nickname change, role update, channel update |
| 🟠 Orange | Message delete, bulk delete |
| 🔵 Blue | Voice events, member unban |
| ⚪ Grey | Member leave (voluntary) |
| Field | Always Available | Notes |
|---|
| User ID | ✅ Yes | Always present |
| User tag/mention | ✅ Yes | Always present |
| Timestamp | ✅ Yes | Always present |
| Message content | ⚠️ Sometimes | Only if message was cached |
| Moderator/actor | ⚠️ Sometimes | Requires View Audit Log permission |
| Reason | ⚠️ Sometimes | Only if moderator provided one |
Consider setting up separate channels for different log categories — for example, #member-logs, #message-logs, and #mod-action-logs. This prevents high-volume events like message deletes from burying critical entries like bans and role changes, and makes it much easier to search for specific incidents.
