When the Discord bot logging channel is configured, moderation actions are sent to Discord through the bot instead of webhooks. Webhook notifications are disabled while bot logging is active.
Configuring the Logging Channel
- In Discord, right-click the channel where you want logs sent and select Copy Channel ID.
- Add the channel ID to your
server.cfg:
set ea_botLogChannel "123456789012345678" |
All moderation actions (bans, kicks, warns, mutes, etc.) are sent to this channel as embed messages.
Log Forwarding
Every log type goes to the main logging channel by default. To send one log type to a different channel, use the ea_addBotLogForwarding command:
ea_addBotLogForwarding joinleave 123456789012345678 ea_addBotLogForwarding ban 123456789012345678 |
Give the log type first, then the channel ID. Both are required — the command does nothing if either is missing.
Run it from the server console, or in-game with the easyadmin.server permission. Forwarding only works while the bot is running and ea_botLogChannel is set. Forwarding rules are not saved, so set them again after the bot restarts.
Available log types:
kick— Player kick notificationsban— Player ban notificationsslap— Slap action notificationswarn— Warning notificationsteleport— Teleport notificationsfreeze— Freeze and unfreeze notificationsspectate— Spectate notificationssettings— Server setting changes, resource start/stop, announcementscalladmin— Player calladmin reportsreport— Player report notificationsreports— Report claim and close notificationsscreenshot— Screenshot capture notificationsmute— Mute, unmute and Emergency Mode notificationscleanup— Cleanup notificationsjoinleave— Player join and leave notificationsstartup— Bot startup messages
Webhook Fallback
When bot logging is not configured (ea_botLogChannel is empty), EasyAdmin falls back to webhook notifications as described in the Webhooks guide.
