Server Log¶
The server log is a dedicated channel where NabBot announces important events related to your server and the features it manages.
It works as a lightweight operational history for your server, helping admins understand what changed and why.
Server Log vs Watchlist Feeds
The server log is meant for moderation and identity tracking inside your server.
It helps you keep track of the people in your server, such as who they are, which characters they register, and whether those characters were renamed or transferred in a way that changes what is visible in your tracked world.
It is not meant for tracking unrelated external characters.
For that, use watchlists and watchlist feeds instead. Those are better suited for keeping an eye on other characters outside your server.
Setup¶
You can choose any channel to act as the server log with /settings server-log set.
You can also decide which event types are announced with /settings server-log-filters.
Filters
Each filter controls a group of related announcements.
New event types are enabled by default unless you disable them.
Event Types¶
Audit Logs
For some moderation and server-management events, NabBot can only show who performed the action, and any audit log reason, if it has the View Audit Logs permission.
Member Joined¶
Sends a message when a member joins your server with basic information about them, like their Discord account age (to detect potential spam accounts). If you have a tracked world configured, it will also display the characters registered to that user.
If the member is a Discord bot and the bot has audit log permissions, it will also display who added it to the server.
Member Left¶
Sends a message when a member leaves your server. If you have a tracked world configured, it will also display the characters registered to that user.
If the bot has audit log permission, NabBot will be able to tell if the member left on their own or was kicked, as well as who kicked them.
Member Updated¶
Sends a message when relevant information about a member changes, such as their nickname or avatar. This can be helpful to detect possible impersonation attempts.
Member Banned¶
Shows a message when a member is banned from the server. Discord only sends NabBot this event if it has the Ban Members permission.
Member Unbanned¶
Shows a message when a member is unbanned from the server. Discord only sends NabBot this event if it has the Ban Members permission.
Characters Registered¶
Shows a message when a user registers a new character in the same world the server is tracking.
Character Unregistered¶
Shows a message when a user unregisters a character in the same world the server is tracking. Ownership changes can also generate unregister messages for the previous owner.
Character Renamed¶
Shows a message when a character registered by a server member is renamed.
Character Transferred¶
Shows a message when a character registered by a server member is transferred into or out of the tracked world.
Server Updated¶
Shows a message when some server-related settings change.
Premium¶
Shows messages related to the premium status of a server.
Autoroles¶
Shows a message when NabBot adds or removes roles from a member based on autorole rules.
Filtering¶
Server log filters use an opt-out model:
- existing event types are enabled by default
- newly added event types are also enabled automatically unless you disable them
Always-on notices
Some operational notices are currently always announced and are not part of the filter list.
These include things like:
- deletion of Discord roles that were being used by NabBot features, such as joinable roles or autoroles
- watchlist feed removal
- watchlist-related update errors and permission issues
These notices help explain why a NabBot feature may have stopped working after something changed directly in Discord.
Best Results¶
For the most useful server log experience:
- choose a channel that only moderators and admins can read
- give NabBot View Audit Logs if you want actor and reason details when available
- keep the tracked world configured if you want registered-character context in member and character events
The server log works best as a lightweight operational history for your server: not every action, but the events that help moderators and admins understand what changed and why.