Skip to main content

​
How logs are delivered

Quark posts logs through a webhook that it creates in each log channel. That is why it needs Manage Webhooks there. Logs appear under the name Quark, Quark Pro Lite or Quark Pro, depending on your server’s plan. If the webhook or the log channel is deleted, logs to that channel stop. After five failed attempts in a row, Quark clears the channel from your configuration, so the setting looks empty. Choose a channel again on the dashboard, or run /troubleshoot and press Register webhook. A channel set for a single log type is not cleared automatically. If Quark only loses a permission, nothing is cleared. Logs resume when the permission is back.

​
Message age

To show what a deleted or edited message said, Quark has to have stored the message when it was sent. What happens with an older message:
  • Deleted: the log is sent without the content or the author. On the free plan and Pro Lite, the log says the content is available with Quark Pro. You can turn that notice off under Logging → Other → Pro upsell logs. With it off, a deleted message that is too old produces no log at all.
  • Edited: the log shows the author and the new text, but not what the message said before.
  • Older than 30 days: a deletion is not logged on any plan.
How long a message is kept is decided when it is sent. Upgrading does not bring back messages that were stored under the 12-hour limit. Quark cannot show messages that were sent before it joined, or in channels it could not see.

​
Actions by bots

These log types are always sent, on every plan, whoever did them: member joins and leaves, bots added and removed, bulk message deletes, and bans, unbans, kicks, timeouts and timeouts removed. An action a moderator takes through Wick, YAGPDB, Sapphire or ProBot counts as the moderator’s, not the bot’s. It is logged on the free plan, and on a paid plan it is logged even when Actions by bots is on. An action taken through any other bot, apart from Quark’s own commands, counts as the bot’s, even when that bot’s audit log reason puts a moderator’s name on the log. See bot integrations.

​
Who did it

Discord does not tell a bot who performed most actions. Quark finds out from the server’s audit log, which needs the View Audit Log permission. Without it, many log types are not sent at all and others lose the moderator. See permissions.
  • When a moderator acted through Wick, YAGPDB, Sapphire or ProBot, the log names the moderator and adds which bot was used, for example “using Sapphire#8184”. This applies to every log built from the audit log, apart from single deleted messages and voice moves, disconnects, mutes and deafens. See bot integrations.
  • A deleted message shows Deleted by when someone other than the author deleted it. If a bot deleted it for a moderator, this shows the bot.
  • Soundboard and AutoMod rule logs are sent either way, but only say who made the change if Quark can read the audit log.
  • A voice move or disconnect done by a moderator is logged as Moved or Disconnected. If the member did it themselves, it is Changed Channel or Left Channel. If a bot did it for a moderator, these show the bot.
  • Server mutes and deafens show the moderator on Quark Pro only.

​
Bundling

Voice events and reaction removals often come in bursts. When several happen close together, Quark sends one log instead of many: Multiple Voice Channel Events or Multiple Reactions Removed. A single event on its own is logged as normal. Automation rules that watch the individual log types run for each event in a bundle.

​
Time in voice

Some voice logs say how long something lasted.
  • A session spent in one channel has no list. The Joined line already says how long it lasted.
  • A leave log lists up to ten channels. With more, some are replaced by a count, such as ”… +3”, and the last channel is always shown.
  • A list that starts with ”…” is partial: Quark did not see the start of the session, or a channel was left out.
  • Channels on your ignore rules, and channels in ignored categories, are left out of the list.
  • Stays shorter than two seconds are not listed.
  • If Quark did not see the stream start, there is no Streamed for line.
  • In a bundled log, each event shows its most recent channels on one line, where there is room.

​
Boosts

Server Boosted and Server Boost Removed are sent once for each boost and name the member. The log says “Someone” when Discord does not say who it was: a member who is already boosting adds another boost while the server’s boost messages are switched off, or a member removes one of several boosts.

​
Deleted files

Quark keeps a copy of each file posted in your server for a short time, so that it can re-post the file if the message is deleted. See data for how long.
  • Very large files cannot be re-posted. The cut-off rises with your server’s boost level.
  • With Spoilers switched on, re-posted files are marked as spoilers.
  • Bulk deletes attach a text file listing the deleted messages. For a message from a bot or a webhook, and any message with no text of its own, the file writes out what each embed said.

​
Rate limits

Discord limits how many messages can be posted to one channel in a given time. If your server produces logs faster than that:
  • The dashboard’s Channels tab shows a warning naming the channel.
  • If it goes on, Quark pauses the busiest log type in that channel so the others keep arriving. It resumes on its own when the channel is quieter.
The limit is per channel. Moving one or two categories to their own channels is the fix. On a busy channel, logs that arrive at almost the same moment can be posted together as one message. A modlog that shares its message with another log is posted without its Edit Reason and Lock buttons, so its reason cannot be edited or locked. See modlog reasons.

​
Language

Logs are written in your server’s language. See languages.

​
Your settings changes are logged too

Changing a log channel, the ignore rules, a logging option, an automation rule, a tag, an API token or dashboard access produces a log in the Quark Events category, with who made the change. A Dashboard Access Changed log names the preset and each permission that was given. Changes to one log type produce a Log Updated log: switching it on or off, setting its format or a channel of its own, changing its colour, and its bot and Active Ignore switches. Three things are not logged: taking a log type’s own channel away, going back to the server’s format, and any of these changes while Log Updated itself is switched off, which includes switching it off. A change made by someone on your Who did it ignore list is not logged either. Active Ignore requests are recorded there too.