Log Forwarding
Forward game events to Discord channels
Active development
Log forwarding is under active development. New event types and formatting improvements are added regularly. If you notice inaccuracies or incorrect data in forwarded logs, please report it to the developer.
WardenCore can automatically forward game events to Discord channels in real time. Every time a player kills another player, logs in, opens a chest, or triggers any tracked event, the bot posts a formatted embed in the designated Discord channel.
Setting Up Log Forwarding
Open log forwarding settings
In the WardenCore panel, go to Settings > Discord > Log Channels.
Select channels
For each event type, select the Discord channel from the dropdown list. Leave unselected to disable forwarding for that event type.
Use a separate channel for each event type. Sending multiple event types to the same channel hits Discord rate limits and can cause the bot to become unstable.
Save
Click Save. Events will start forwarding immediately. The bot batches embeds to stay within Discord's rate limits (up to 10 embeds per message, flushed every 5 seconds).
Tip: use separate channels
Create dedicated Discord channels for different log types -- for example, #pvp-kills, #admin-log, #chat-log, #login-log. This keeps things organized and makes it easy to find specific events.
Available Event Types
Core
| Channel | Description |
|---|---|
| Chat (Public) | Global chat messages |
| Chat (All) | All chat messages (Global, Local, Squad, Admin) |
| Kills (PvP) | Player vs player kills |
| Kills (PvE) | Deaths from environment and AI |
| Login | Player join and leave events |
| Admin | Admin command executions |
| Admin (Public) | Public admin announcements |
| Admin Alerts | Suspicious activity alerts |
| New Player | First-time player join notifications |
| Bot Commands | Channel for bot command input and responses |
Economy
| Channel | Description |
|---|---|
| Trade | Player trading activity |
| Bank | ATM and banking transactions |
Events
| Channel | Description |
|---|---|
| Chest | Chest interactions |
| Raid | Base raid activity |
| Vehicle | Vehicle claim and usage |
| Squad | Squad create, join, leave |
| Quest | Mission and quest activity |
| Name Change | Player name changes |
| Violations | Flying vehicle violations (kicks and bans appear in the Login channel) |
| Fame Points | Fame point changes |
| Sentry | Sentry turret events |
Gameplay
| Channel | Description |
|---|---|
| Lockpicking | Player-owned lock picks |
| Lockpicking (World) | World object lock picks |
| Dialpad | Dialpad code attempts |
| Dial Lock | Dial lock interactions |
| Lock Bomb | Lock bomb detonations |
| Bomb Defusal | Bomb defusal attempts |
| Bunker | Bunker puzzle minigame |
| Puzzle | Puzzle solving logs |
| Trap | Trap placement and triggers |
| Explosive | Explosive usage logs |
| Chest Bury | Buried chest activity |
| Base Flag | Base flag interactions |
| Bunker Lock | Bunker activation status |
How Log Embeds Look
Each event type generates a formatted Discord embed with relevant details. For example:
- PvP Kill embeds include the killer, victim, weapon, distance, and a map thumbnail showing the location
- Login embeds show the player name, Steam ID, and IP address
Privacy
Login embeds contain player IP addresses (personal data). It is recommended to restrict the login log channel to administrators and moderators only.
- Trade embeds group multiple items from the same trade session into a single embed with a summary
Log Forwarding Performance
WardenCore batches log embeds to respect Discord's rate limits:
- Embeds are grouped per channel and flushed every 5 seconds
- Up to 10 embeds are sent per message (Discord's maximum)
- A buffer of 500 entries prevents memory issues during high-activity periods
- If the buffer fills up, the oldest entries are dropped
This means during intense activity (e.g., a large PvP battle), there may be a short delay before all events appear in Discord. Under normal conditions, events appear within a few seconds.
Common Issues
Logs not appearing in Discord
- Make sure a channel is selected for the event type in the panel
- Verify the bot has permissions to send messages in the target channel
Delayed logs
Some delay is normal. Embeds are batched every 5 seconds and Discord has rate limits. During very high activity, delays may be slightly longer. This is by design to avoid hitting Discord's API limits.
Too many messages
If a channel is getting flooded, consider disabling less important event types or splitting events across more channels. For example, PvE kills on a busy server can generate a lot of traffic -- you may want to disable PvE forwarding or send it to a low-priority channel.
Missing events after server restart
Events that occurred while the bot was offline are not retroactively forwarded. Log forwarding only captures live events. Historical data is always available in the WardenCore panel's log viewer.