Modules
Logging
Per-category event and audit logs.
A log that says a message was deleted is half an answer. Dispresso reads the server audit log alongside the event, so a delete says who deleted it, a ban carries the reason the moderator typed, and a role change names the person who made it. Where it genuinely cannot tell, it says that instead of leaving the field blank.
Or just tell the bot#
set up logging
log server events in #server-log
make the member logs go to #joins
make the alert role @Staffset up logging asks for member logs and then server logs; same reuses the first channel. Start with dispresso or mention it. It asks for anything it still needs, writes the same settings the dashboard writes, and the whole list of sentences is on Talk to Dispresso.
Three destinations#
Events about members go to one channel: joins and leaves, nickname, role and avatar changes, timeouts, bans and unbans, message edits and deletes, bulk purges with the content that was removed, and voice joins, leaves and moves. Events about the server go to another: channels, roles, emojis, invites, webhooks and integrations created, deleted or changed. Anything a staff member does through the bot goes to the Moderation module's own log channel, so mod actions and audit cases stay together.
You can point all three at one channel, or give member events a channel of their own separate from the rest.
Setting it up#
/logging takes four actions. Quick setup channels is the fast road: it makes a Logging category with the three channels in it, reuses anything already there, and switches the module on. Setup panel is the same settings by hand, Status prints where each log is pointed, and Disable module turns it off. /server logging is the same command, and the Logging page in /botdashboard has all of it.
Turning the noise down#
Sixteen switches, one per kind of event, so a server that only wants deletes and bans can have exactly that. Bot messages are never logged as edits or deletes. Naming roles as ignored keeps role changes involving them out of the log, which is how you stop a self-roles channel filling it up.
A bypassed channel writes nothing
Channels on the bypass list are never written to by logging. That is there so a log cannot be sent into a channel you never wanted it in, but it also means that if you put your own log channel on the list, the log goes quiet and nothing tells you why.
Joins carry where they came from#
A member joined entry names the invite code, whoever made it, and the channel it came from. When two invites were used in the same moment it says it could not tell them apart, which is a different fact from having nothing to report.
Every system#
The rest of Dispresso writes to the same log. A ticket opened, claimed, closed or given a transcript; a giveaway created, ended or rerolled; a wallet or bank transfer, a shop purchase, a big daily or work claim, a balance edited by staff; a level up and a change to the level roles; a role menu posted and a role taken or dropped through one; a welcome or goodbye posted and the welcome settings changed; channel locks, AutoMod hits, voice rooms created, claimed and locked, form submissions, counters made, bumps, partner ads, events, and everything the assistant builds by talking. Each line says who, what and where, carries its system in the footer, and shows on the site's log viewer with a system tag and a System filter.
| System | Slug | What gets a line |
|---|---|---|
| Tickets | tickets | opened, claimed, closed, transcript saved, panel built by talking |
| Giveaways | giveaways | created, ended, rerolled |
| Economy | economy | transfers, daily and work claims of 1,000 or more, balance edits by staff |
| Shop | shop | every purchase |
| Leveling | leveling | level ups, level roles set or removed |
| Self roles | self_roles | menu posted, role taken or dropped, colour pack added |
| Welcome | welcome | welcome and goodbye posted, settings changed |
| Moderation | moderation | every case, channel locks and unlocks |
| AutoMod | automod | every rule hit and the action taken |
| Voice rooms | voice_rooms | created, claimed, locked, unlocked |
| Forms | forms | every submission |
| Counters | counters | a counter channel made |
| Directory | directory | every bump |
| Partners | partners | a partner ad or spotlight posted |
| Events | events | an event created |
| Assistant, templates, sales | assistant templates sales | a server built, a sales desk built, the rules changed |
| Also known | music zoo gangs birthday id_verification rooms | reserved for those systems as they join the log |
Or just tell the bot#
log everything
log tickets to #ticket-logs
log giveaways and shop purchases in #staff-logs
send all logs to #logs
stop logging the economy
what are you loggingEvery system is on the moment the logging module is, and writes to the server log channel unless you give it one of its own. A #channel that does not exist yet is made, private to staff. Start with dispresso or mention it. It asks for anything it still needs, writes the same settings the dashboard writes, and the whole list of sentences is on Talk to Dispresso.
- /loggingAdmin logging setup and status. Server staff only.