Changelog

Every action a rule can take is now on every plan, the free one included. That covers timeouts, kicks, bans, deleting a message, giving or taking a role, DMs, and the newer ones: lifting a timeout or ban, nicknames, voice, slowmode, locking, a channel's name, topic or status, and pinning. Alerts, notices, copies, replies, reactions and holding a log back were already free.

The one exception is changing a log's colour, which needs Pro Lite or Quark Pro, the same as it does on the Logging page.

What each plan gets

	Free	Pro Lite	Quark Pro
Rules running	1	3	25
Every action except a log's colour	Yes	Yes	Yes
Changing a log's colour	No	Yes	Yes
Advanced conditions	No	No	Yes
Trying a rule on your own recent logs	No	No	Yes

• A rule that was Parked because one of its actions needed Quark Pro now runs, as long as it fits in your plan's number of rules.
• The safety rails are the same on every plan. A rule never acts on the server owner or anyone whose highest role is level with or above Quark's, each rule and each server has an hourly limit on moderation, and only someone with the matching Discord permission, such as Ban Members, can save a rule that bans.
• Action buttons on log formats are separate, and stay on Quark Pro.

Open Automations in the dashboard sidebar, or read the guide to automations.

Automations can now check a log against a list, read every part of it, and do much more when one matches. Open Automations in the dashboard sidebar.

Lists of words

A new condition, It's on a list of words, asks whether some text of the log is one of, isn't one of, contains a word from or doesn't contain a word from a list.

• Your own words. Type a word or phrase and press Enter, or paste several at once. Up to 200.
• One of Quark's lists, on every plan: swear words in English, German, Spanish, French, Polish, Portuguese and Turkish, known scam and phishing links, link shorteners, Discord invite links, and risky file types such as .exe and .scr. The builder shows what each has and where it comes from.
• Case is ignored, and so are full-width letters and extra spaces. Words are matched whole, so ass is not found in "class". A web address matches the addresses in the message, and a file ending such as .zip matches only the end of a file name. That is how Risky file types is checked, so IMG_1234.jpg is not caught by .img.

More on lists of words.

Every part of a log

• The message says something and lists can read the message, the text before an edit, the reason, the name, a voice channel's new status, the names of the files, and the username or ID of either person.
• A number is more or less than, a new condition, compares how many files a message had, how many messages or members a bulk log covers, a message's age, or an account's age in days.

15 new actions

Action	Plan
Reply to the message, without pinging anybody	Every plan
React to the message	Every plan
Pin or unpin the message	Quark Pro
Remove a timeout, unban someone, change someone's nickname	Quark Pro
Move, disconnect, mute or deafen someone in voice	Quark Pro
Set a voice channel's status, slowmode, a channel's name or its topic	Quark Pro
Lock or unlock a channel	Quark Pro

• Actions are grouped in the menu under The message, People, Voice and Channels, and only the ones that fit the logs a rule watches are offered.
• A channel action can change a channel you choose, or this log's channel.
• Locking takes Send Messages, threads and reactions away from @everyone in the channel, and Connect and Speak in voice. Unlocking takes those back off and changes nothing else. Locking or unlocking needs Manage Roles in that channel, for you when you save the rule and for Quark.
• A channel's name and topic can each be changed by rules once every 5 minutes, because of Discord's own limit.

New ideas

• Flag deleted messages that swear, from Quark's English list.
• A message with a known scam link is edited or deleted. With Quark Pro it also times the poster out for an hour.
• 10 members join in a minute. With Quark Pro it also locks a channel you choose.
• A voice channel's status is set to one of your words: clear it, or set it back. Quark Pro.

Careful by design

• A rule never acts on the person a Thread Member Joined or Thread Member Left log happened to, because a member can be added to a thread by somebody else mentioning them.
• Each new Quark Pro action needs the Discord permission for it, held by whoever last saved the rule, and counts towards the rule's hourly limit. Replies and reactions count as alerts.
• Quark needs a few permissions that are not in its invite link for some of these: Manage Channels, Manage Nicknames, and Move, Mute and Deafen Members. See permissions.

What each plan gets

	Free	Pro Lite	Quark Pro
Lists of words, including Quark's lists	Yes	Yes	Yes
Alerts, notices, copies, replies, reactions, holding back	Yes	Yes	Yes
Changing a log's colour	No	Yes	Yes
Moderation actions, the new ones included	No	No	Yes

Logs have always been posted under Quark, Quark Pro Lite or Quark Pro, with Quark's picture. With Pro Lite or Quark Pro you can now choose a name and avatar of your own. In the dashboard, go to Logging → Other and scroll to Log name and avatar at the bottom.

• A name. Up to 80 characters. Leave it empty to keep Quark's. The field says as you type if Discord would refuse it, for example a name with "discord" in it, and a name like that is not saved.
• An avatar. Quark's picture, your server's icon, one of Quark's 14 pictures (its logo in six colours, a shield, gavel, eye, bell, scroll, message, members and voice symbol), any of your server's custom emojis, or the icon of a role. Pictures can't be uploaded.
• Per log channel. Each of your log channels is listed with what is sent there. Give any of them a name or avatar of its own, such as "Mod Log" with the gavel in your modlog channel. One left on Same as server uses the setting above.
• Saved as you go. An avatar saves when you choose it, and a name when you stop typing. The preview shows how a log will look.

A change is used from the next log, and is recorded as a Logging Options Updated log in your Quark Events channel. If an emoji or role icon you chose is deleted, logs go back to Quark's picture, and no log is lost over it. When a plan ends, the setting is kept and logs go back to Quark's name until the plan is back.

Import settings copies the name and avatar to a server with a plan, and matches a role icon to the role you pair it with.

More in the guide to name and avatar.

Alongside log name and avatar and more for automations, this release adds new logs, says more in existing ones, and gives two commands more to do.

New logs

Log	When it is sent
AutoMod Blocked a Message	Discord's AutoMod stopped a message. Names the member, the channel and the AutoMod rule, but not what the message said
Thread Member Joined, Thread Member Left	Someone joins or leaves a thread. Several at the same moment are sent together as one log
Channels Reordered	Channels are dragged into a new order: which channel moved, and where to
Server Banner Updated	The server's banner changes, with the old and new banner
Reactions Cleared	All the reactions on a message, or all of one emoji, are removed at once
Server Plan Changed	A server moves between Pro Lite and Quark Pro. Server Upgraded now also says who gave the plan

Each can be switched on or off under Logging → Individual Log Config. See every log type.

Logs that say more

• Deleted forwards. When a forwarded message is deleted, the log shows what it carried: its text, files, stickers and embeds, where it was forwarded from, and a link to the original.
• Command answers. When a bot's answer to a slash command is deleted, the log says who ran the command, such as "Command run by @mara (/ban)".
• Pins without the audit log. A pin or unpin is logged even when Discord's audit log doesn't say who did it, for example without View Audit Log.
• Joined without an invite. When Quark is an Administrator and no invite was used, the join log says so, for a member added by a bot or through server discovery.
• The time on a log is when it happened. A log that waited for the audit log, or was sent again after a delay, now shows when the event happened rather than when it was posted. The Log Viewer places a log that arrives late by its time, not at the top.

Show Edits

• Word by word. Show Edits marks what was added in bold and what was removed struck through, with long unchanged stretches cut short. Nobody mentioned in the message is pinged.
• On every edit log that holds both versions of the message. It used to be only on edits of more than one line.
• Show edits in a log's Apps menu does the same for edit logs posted before this.

More on Show Edits.

/purge filters

/purge can now delete only the messages that match:

• user: one member's messages.
• from: bots and webhooks, or people.
• contains: some text, in any case.
• has: files, links, embeds or mentions.
• keep_pinned: leave pinned messages alone.

With a filter, count is how many matching messages to delete. Quark looks back through up to 500 messages, and the reply says how many it found if that was fewer. /purge now needs Manage Messages in the channel you run it in: a channel that takes the permission away from your role stops it there. More on /purge.

Fixed

• The Log Viewer said a log was delivered when Quark had no record of its delivery yet. It now says Not yet confirmed.
• Signing in to the dashboard could show an error page instead of your servers when Discord asked Quark to wait a moment. It now waits and tries again.
• Someone whose first payment was declined on the checkout page, and who then paid with another card, could be told an hour later that their payment had failed.
• /troubleshoot worked out a thread log channel's permissions as if the channel it is in allowed everything. It now checks that channel.
• On a server that ignores both actions by bots and actions done to bots, pressing Fix this on one in the troubleshooter marked both as being fixed.
• The icon for Multiple Reactions Removed was the one for a single removed reaction.

A log tells you what happened. Until now, doing something about it meant leaving the log for a command or Discord's menus. With Quark Pro, a log format can put action buttons under a log: press one and Quark does what the button says.

Open a format on Log Formats in the dashboard, pick a log, press Change something, then Change the buttons and Action button. Pick All logs at once first to put the button on every log.

• What it does. Up to 4 actions, in order: tell a channel, time someone out or remove a timeout, kick, ban or unban, delete the message, give or take a role, or send someone a DM. "Someone" is the person it happened to or the person who did it.
• Which logs carry it. Up to 8 conditions, the same blocks as in Automations: someone has a role, a bot did it, it happened in a certain channel, the account is new, and more. With none, the button is on every log of that kind.
• Who can press it. Quark checks the person pressing every time. They need the Discord permission for each action, and a highest role above the member's. Only certain roles narrows it to the roles you choose.
• Asked first. A button that moderates opens a confirmation box, written by Quark, that lists exactly what will happen, with an optional reason for the audit log and the modlog. A button that only sends a message acts straight away.
• Recorded. A ban, kick or timeout is logged as usual and names the person who pressed. The press itself is a Rule Action log, "Button Pressed", and the Log Viewer reads it as "mara pressed the “Ban” button about nova".

A log can have up to 5 action buttons, beside its link buttons and Quark's own.

Careful by design

• The moderation actions and Give or take a role can't be used on the person pressing.
• Tell a channel needs the person pressing to be able to post in that channel themselves.
• A server's buttons send one member at most 3 DMs an hour, and 60 messages an hour in all.
• A log where Quark is not sure who did it never gets a button that acts on the person who did it.
• Adding or changing an action button needs Manage automations under Dashboard Access, as well as Manage log settings, and the Discord permission for each action it takes.
• A format shared by link never carries action buttons, because they name your server's channels and roles.

More in the guide to action buttons.

Alongside action buttons, this release adds two new ways for a log to look and changes where a log's format and colour are set.

Components and pictures

Two more of Quark's own formats are on the Log Formats page in the dashboard:

Format	What it looks like
Components	Laid out with Discord's newer components: a box in the log's colour, the avatar beside the title, the buttons inside it
Image cards	Each log drawn as a picture card: the log's colour and icon, who it was about, and what happened. Needs Quark Pro

Components is free on every plan. In a format of your own, Components and Image are two more layouts, and with Quark Pro, Advanced has an editor for each:

• The Components editor. Drag in boxes, text, text with a picture, galleries, files, dividers, rows of buttons and a menu of action buttons. Any part can be shown only when a condition is true.
• The image editor. Layers of text, avatars, icons and shapes, including a shape you draw yourself, on a picture of the size you choose. Alt text is written from the log unless you write your own.

A log that comes to more than Discord allows, or a picture that is too big or too slow to draw, is posted as Standard. No log is lost to a layout. Every log, a picture included, can be searched in the Log Viewer. Discord's own search cannot read the words drawn in a picture.

Basic is just the facts

Basic and Basic (no embed) now keep each log's facts and nothing else: who, what, where and why. There is no name line above the title, the small print is the ID alone, and a few fields that are not facts of what happened, such as Roles on User Left, are left out. A picture of what changed, such as a new avatar, is kept. Edit Reason still works on a Basic modlog.

A log's format and colour are set in Log Formats

Individual Log Config no longer has a Format option or an Embed Color picker. How a log looks, for every log or for one log on its own, is set in Log Formats, or by an automation that changes its colour.

• On Pro Lite and Quark Pro, a log already given its own format or colour keeps it. Individual Log Config says so where the option was, with Follow the server's format or Use the log's own colour to go back.
• Each log's page ends with Formats and Automations: the format the log is posted in, every rule that watches it, and links to both. New for this log opens a new rule already watching it.
• Import settings no longer copies a log's own format or colour, and lists them as skipped.

Forum posts

• Ignoring a forum or media channel now ignores its posts too, whether it is on the Channels list or the Categories list. Messages, edits, pins, reactions and bulk deletes in a post are left out. A thread in a text channel is not affected.
• An automation about a forum matches the logs from its posts. A rule like "it happened in #help-forum" now runs on a message deleted in any of its posts, so check rules like that which moderate. Try it matches posts the same way.
• A forum on the Channels list of Ignore Rules can be removed again.

More on ignoring forums and forums in automations.

Also new

• Share your vote link. The Pro Lite card on the Logging page has a Share button beside Vote on Top.gg. It copies this server's vote link, to post for your members. A vote through it unlocks Pro Lite here if the server has under 1,000 members, like /vote.
• A gift can replace a failed renewal. If your subscription's last renewal did not go through, the gift page offers End subscription and redeem. The subscription ends, you are not charged for that renewal, and the gift starts the same day.
• On a phone, the server's name sits in the middle of the top bar once the page heading has scrolled away.

Fixed

• The troubleshooter said a thread used as a log channel "no longer exists". Threads are supported log channels: the troubleshooter now checks the channel the thread is in, which is where its webhook and permissions come from. See a thread as a log channel.
• On a server with a channel for deleted files, the format preview drew a deleted message's file on the Message Deleted log. It now says the file is posted as a Delete Attachment log, as Quark does.

A run of fixes for using the dashboard on a phone, and for searching for members.

On a phone

• Tapping a text field no longer zooms the page in and leaves it zoomed.
• The rule builder, the format builder and other sheets stay where they are when the keyboard opens. Before, the top of the sheet went off the screen, with the field you had just tapped.
• The list of results under a member or channel field opens where it can be seen, instead of behind the keyboard.
• The ignore rules' fields no longer correct or capitalise what you type.
• The top bar with the menu button stays at the top of the screen as you scroll, and shows the server's name once the page heading has scrolled away.
• The "live updates" notice sits under the top bar instead of behind it.
• On a narrow phone, a long server name no longer makes the page wider than the screen.

Member search

• On the Quark Pro tab, searching for a member in Ignore Rules searched the main bot's members. It now searches Quark Pro's.
• A search that fails now says so, instead of saying nobody was found.

Until now a thread being closed, reopened, locked or unlocked was a Thread Updated log with a different first line. Each is now a log type of its own, with its own title, icon and colour:

• Thread Closed
• Thread Reopened
• Thread Locked
• Thread Unlocked

They cover forum posts as well, and each one says one thing only.

• Discord's Close and lock sends two logs: Thread Closed, then Thread Locked. Switch either off and you still get the other.
• A thread Discord closes by itself for inactivity, or reopens because someone posted in it, is not logged.
• Thread Updated still covers a thread's name, slowmode, auto-archive, tags, pin and whether members can invite. A change like that made at the same time as a close or a lock is sent as its own Thread Updated log.
• An automation rule that names Thread Updated no longer runs for closes and locks. Add the new log types to the rule. A rule that watches the whole Messages category is not affected.

More in the guide to closed and locked threads.

Also new

• Two ideas in Automations that change a log's colour: turn the log red when an account newer than 7 days joins, and turn it purple when a deleted message contains a word you choose. Changing a colour needs Pro Lite or Quark Pro, and both ideas are marked so.

Fixed

• Edit Reason on a modlog Quark cannot read now says so when you press it, instead of after you have typed the new reason.

Quark's own formats are on every plan, and there are four more of them on the Log Formats page in the dashboard.

Format	What it looks like
Basic	Standard without Quark's icons: the same words, nothing drawn beside them
Basic (no embed)	Standard (no embed) without Quark's icons
Detailed	Standard with every extra detail a log has: IDs, account ages, when a message was sent, the exact time
JSON	Each log as JSON in a code block, for another bot to read

Basic only takes off the icons Quark draws, on the title, the field names and the buttons. Emoji somebody used in a message, a reason or a name stay. Edit Reason still works on a Basic modlog, in both kinds.

A format you build can start from Basic, Basic (no embed) or Detailed, as well as from the first four.

JSON for other bots

Each log is one JSON object in a code block, with the same keys every time:

{
  "v": 1,
  "type": 39,
  "log": "Ban",
  "time": 1791495600,
  "guild": "…",
  "executor": {
    "id": "…",
    "name": "mara.k",
    "bot": false,
    "created": 1684356000
  },
  "target": {
    "id": "…",
    "name": "novastar",
    "bot": false,
    "created": 1791405600
  },
  "channel": null,
  "role": null,
  "message": null,
  "content": null,
  "contentBefore": null,
  "reason": "Spamming invite links",
  "name": null,
  "amount": null,
  "attachments": null,
  "fields": [{ "name": "Reason", "value": "Spamming invite links" }],
  "truncated": false
}

• v is the version of this shape. A key a log has nothing for is null.
• Times are Unix seconds. IDs are strings.
• A log too long for one Discord message has its longest text shortened, and truncated is true. IDs, times and the type are never cut.
• JSON logs have no buttons.

More in the guide to log formats.

Until now every Quark log looked the same on every server: an embed, with the fields Quark chose. Log Formats is a new page in the dashboard sidebar where you decide how your logs look.

Four formats from Quark

Format	What it looks like
Standard	Quark's own embed, with a colour for each kind of log. Every server starts on this
Standard (no embed)	The same information as a plain message
Compact	A small embed with one or two lines for each log, for busy channels
Compact (no embed)	One or two lines of plain text, and no buttons

All four are free on every server. Each one is drawn on a real log before you choose it. Use this format applies at once, with Undo, and See every log shows a format on every kind of log Quark sends.

Build your own

Create a format starts from one of Quark's. Pick a log and change what you like about it; a log you leave alone keeps looking the way it does now.

• Show extra information. Add something the log knows but leaves out: the message ID, how old an account is, the exact time.
• Hide or spoiler something. Leave a field out, or put the message text behind a spoiler.
• Write your own text. Change the title or the footer, or add up to four lines of your own, with {{target}}, {{executor}}, {{channel}} and {{reason}} filled in from the log.
• Change the buttons. Choose which buttons a log has and their order, and add link buttons: Jump to message, or a link to your own tools with the member's ID in it.
• Change the colour or layout. Any colour, as an embed, plain text or compact.

The builder shows what Quark posts now beside what your format posts, and lists each change as a sentence you can edit or remove. All logs at once is for the few things you want everywhere. Nothing is saved until you press Save format.

Advanced, with Quark Pro

Write a log as a template, with tokens, filters and conditions:

{{#if reason}}{{reason}}{{else}}No reason given{{/if}}

Advanced starts from what the log looks like now, and Checks says what is wrong before you save. If a template has a mistake, or what it makes is too big for Discord, Quark posts that log as Standard instead, so no log is ever lost to a format.

Share a format with a link

Share gives a format a link, like quark.bot/f/staff-room-7kq2m9x4. The link carries how the format changes logs and nothing from your server: no names, channels, roles, members or logs.

Add from a link shows what a format looks like, and where any link buttons in it lead, before you add it. You get your own copy, and your logs do not switch over until you choose it.

What each plan gets

	Free	Pro Lite	Quark Pro
Quark's four formats	Yes	Yes	Yes
Build, share and add formats, and see them on every log	Yes	Yes	Yes
Post logs in a format you made	No	Yes	Yes
Logs a format can change one by one	None	10	All
Advanced	No	No	Yes

Nothing is deleted when a plan ends. Changes the plan does not run are parked, and the page says which.

Also new

• Individual Log Config can set Compact or Compact (no embed) for a single log.
• Creating, editing, sharing and choosing a format is recorded as a Logging Options Updated log in your Quark Events channel.
• Save is switched off while there is nothing to save, in the format builder, the rule builder in Automations and Dashboard Access.

More in the guide to log formats, and on the Log Formats page.

Fixed

• Turning a category off and on again was listed under the bell as the channel being "disabled" and then "unset". It now reads "turned off logging for the Voice category" and "turned logging back on for the Voice category".
• On a server with both bots, the Log Viewer opened on whichever bot had logged most recently. It now opens on the bot you were looking at in the dashboard.
• The Log Viewer no longer shows a full-screen "Connecting..." screen each time it is opened.
• Requests in progress are no longer cut off when the website restarts for an update.
• Dashboard pages all start the same distance under the header, and loading placeholders sit where the page lands.

Alongside Log Formats, this release changes how plans are offered and fixes a run of things that got in the way of setting Quark up.

Plans

• Yearly, monthly or lifetime. The plan card on the dashboard, and the plan step when you add Quark, used to open a monthly checkout only. You can now choose yearly, which shows what it saves, or monthly, and on the dashboard Quark Pro Lifetime. Each option says exactly what you pay and when.
• What Quark Pro did for your servers. On a server with Quark Pro, the Logging page shows what the plan kept in the last 30 days: deleted and edited messages logged with content the free plan would no longer have had, files kept, and server mutes and deafens with the moderator named. The same counts are in the renewal message and on the page for cancelling.
• One reminder for an unfinished checkout. If you open checkout and leave before paying, Quark may send you one message on Discord an hour later, with a link back to it and a link to stop these messages. Nothing is charged until you finish checkout.
• Stripe's checkout page no longer asks for your Discord ID. The plan always goes to the account you were signed in with.

Setting up logging

• Channel lists open at once on servers with hundreds of channels. They used to take seconds, which looked as if the page had frozen.
• The troubleshooter says what is wrong and how to fix it. The warning on the Logging page names the problem it found and what clears it, and See details opens the troubleshooter at that problem. A new server with no log channel is told to choose one.
• A server that has just added Quark is no longer warned that "no log has ever arrived" before it has had the chance to.
• Turning a category on or off on a server with no main channel no longer says "Something went wrong" after it has saved.
• When a change cannot be saved, the message now says why, for example that Quark needs the Manage Webhooks permission in that channel.

Fixed

• The setup screen after adding Quark could show an error page when one of Quark's services dropped a connection. It now tries again, and a reload is not needed.
• When Discord no longer accepts your sign-in, the dashboard and the Log Viewer ask you to sign in again instead of showing an error.

Limits and the API

• An ignore list holds up to 500 entries of each kind, and adding something already on it no longer adds it twice.
• Changes to ignore lists and tags are limited to 60 a minute, and log exports to 6 a minute. A large import pauses for up to a minute when it reaches the limit, then carries on.
• People given part of the dashboard under Dashboard Access see a read-only bell, without changes to access itself.
• API tokens must be sent as Bearer. A token that is not valid is answered with 401 straight away, where it could take a long time or answer 500 before. Tokens can no longer change who has dashboard access. See the API reference.

Quark has always told you what happened. Now it can do something about it. An automation is a rule that watches the logs Quark already sends and acts when one matches. Open Automations in the dashboard sidebar.

A rule is one sentence in three parts:

• When a log is produced: any log type, or anything in a category.
• And only if something is true: someone has a certain role, it is a particular person, a bot did it, it happened in a certain channel, the message says something, it keeps happening, or the account is new.
• Then do this: tell a channel and ping a role, add a notice to the log, or don't send the log.

With Quark Pro a rule can also time someone out, kick or ban them, delete the message, give or take a role, or send them a DM.

• Start from an idea. Five ready-made rules, such as "Tell a channel when someone with a role is banned" and "Alert a channel when one member has 5 messages deleted in 10 minutes". Each opens with its blanks left for you to fill in.
• See it before it runs. The builder reads the rule back in plain English and draws the log, and the alert, as they will look in Discord. Try it runs the rule against sample logs and marks which would set it off.
• Dry run. A rule in dry run counts how often it would have run and does nothing else. Good for a first day.
• Careful by design. A rule never acts on the server owner, or on a member whose highest role is level with or above Quark's. An alert pings only the one role you choose, never @everyone, and every rule has an hourly limit.

What each plan gets

	Free	Pro Lite	Quark Pro
Rules	1	3	25
Alerts, notices and holding a log back	Yes	Yes	Yes
Moderation actions	No	No	Yes
Advanced conditions	No	No	Yes

Alerts and moderation actions are recorded as a Rule Action log in your Quark Events channel, and a log that a rule held back is still in the Log Viewer, marked with the rule's name.

More in the guide to automations.

Several logs now carry more of what you would otherwise have to work out yourself.

• Time in voice. A Left Channel or Disconnected log lists each channel of the session with the time spent in it. Changed Channel and Moved say how long the member was in the channel they came from.
• Stream length. Stream Ended says how long the stream ran. So does a leave, switch or move that ends one.
• The moderator behind a bot. When a moderator acts through Wick, YAGPDB, Sapphire or ProBot, Discord records the bot as the one who did it. Quark's modlogs already showed the moderator. Role, channel, member and server logs now do too, and say which bot was used: "using Sapphire#8184". Because the action counts as the moderator's, these logs are sent on the free plan as well.
• Boosts. Server Boosted and Server Boost Removed are sent once for each boost and name the member, where Discord says who it was.
• Role colours. Role Modified shows gradient and holographic colours.
• Bulk deletes. The text file of deleted messages writes out what each embed said, for messages from bots and webhooks.
• Dashboard Access Changed names the preset and the permissions that were given.

More on time in voice and bot integrations.

Fixed

• The Log Viewer said a moderator "left the server" when they kicked or banned someone. It now reads "jet was banned by mara.k", with "using Sapphire" when a bot was used.
• The Log Viewer showed an edited message's new text under "Before". Edits logged from now on are the right way round.
• Embeds re-posted beside a deleted message were dated January 1970.
• A modlog showed "???" as the moderator when a bot's reason named nobody Quark could find. It now shows the bot.
• Active Ignore, which lets your own bot ask Quark not to log something it is about to do, works again.

If you run more than one server, you can set one up and copy it to the others. Under Settings → Import settings, press Import from another server.

• Pick another server you manage in Discord where Quark is set up.
• Tick what to copy: logging options and log types, where logs go, ignore rules, tags and language.
• Channels are not shared between servers, so for each channel the other server sends logs to, choose the channel here to use for the same logs, or leave it as it is.
• Every change is listed before anything is changed. A channel this server already uses is only ever replaced by one you choose, and the other server is not changed.

More in the guide.

Also new

• Status updates. Settings → Status updates shows which channel Quark's announcements about releases and downtime are posted in, and lets you move them or switch them off.
• Image-only tags. A tag can be an image with no text.
• This changelog, with an RSS feed.

Fixed

• The home page does less work as it loads and when you move to another page, which was slowest in Safari.
• Opening a tag with no image no longer leaves the previous tag's image frame in the preview.

A deleted or edited message is logged with what it said and its files. Until now, when the message came from an age-restricted channel, that content was re-posted in your ordinary log channel.

Under Logging → Channels → Special categories, set an Age-restricted channel. Deleted and edited messages, deleted files and polls, bulk deletes and removed reactions from your age-restricted channels then go there instead.

• The channel you choose has to be age-restricted itself.
• A thread counts as age-restricted when its parent channel is.
• Other logs about an age-restricted channel, such as a change to its permissions, go where they always did.
• With no channel set, nothing changes.
• Free on every plan.

Files has moved into the same Special categories section, and both rows now say which channel they follow when they have none of their own.

More in the guide to where logs go.

Edit Reason lets a moderator correct the reason on a ban, kick or timeout. Until now nothing on the modlog said it had been changed, and nothing stopped it being changed again months later.

• Edited by. An edited modlog says who edited it and when, under the reason.
• Lock. Press Lock on a modlog and its reason is final. Edit Reason and Lock are removed from it, and it cannot be unlocked.
• History. After the first change, a History button shows who edited or locked the modlog. With Quark Pro it shows the last ten changes, with the reason before and after each edit. On other plans it shows the latest change.
• A time limit for every modlog. Under Logging → Other → Modlog reasons, choose Always editable, Lock after 1 hour, 24 hours, 7 days or 30 days, or Never editable.

Locking, by hand or after a set time, is free on every plan. Modlogs posted before this release gain the new buttons the first time their reason is edited.

More in the guide to modlog reasons.

Fixed

• Edit Reason did not work on a modlog type that had been given a channel of its own.
• Editing the reason of a modlog in the no-embed format could drop its timeout line.

Every page of the dashboard has been rearranged so that things are where you look for them. Your settings were not changed, and each one does what it did before.

• Logging has a status column beside your settings, with a Health card that says whether your logs are being delivered.
• Channels shows each category on one line, with the log types it covers. A category with no channel of its own now says "Uses main channel".
• Ignore Rules, formerly Ignore Options, are grouped by people, roles, channels, messages and bots.
• Individual Log Config has a search box, and marks the log types you have switched off or changed.
• A change is confirmed in one place, beside the page's tabs, instead of with a pop-up each time.
• The troubleshooter is a checklist in the order a log travels, and shows what passed as well as what did not.
• The bell lists recent changes to your settings and who made them.
• The sidebar stays open on wide screens.
• The Analytics page has been removed.

Fixed

• Entries under the bell no longer read "Notification Error".

Until now, opening a server's dashboard took Manage Server or a similar permission in Discord. That is more than a moderator who only needs to read logs should have.

Under Settings → Dashboard Access you can now give a role or one person part of the dashboard:

Preset	What it allows
Log viewer	Read the log viewer, including history
Log analyst	Read and export logs
Moderator	The above, plus the ignore rules and switching log types on and off
Log configurator	A moderator, plus which channel each log goes to
Full access	Everything except managing access, API tokens and billing

Or choose Custom and tick the individual permissions.

• Pages someone can see but not change are marked read-only for them.
• Access never unlocks a paid feature: log history and export still follow the server's plan.
• Take the role away from a member in Discord and their access goes with it.

More in the guide to sharing access.

When logs stop arriving, the cause is usually a deleted channel, a missing permission or an ignore rule that covers more than was meant. Quark can now find those itself.

Press the stethoscope button at the top of the dashboard, or run /troubleshoot in your server. The troubleshooter checks your configuration, Quark's permissions in each log channel and the path a log takes to reach Discord, then lists what it found with the most serious first.

• Where a problem needs no decision from you, there is a button that fixes it.
• Send a test log sends one real log through the whole delivery path and tells you whether it arrived, or where it stopped.
• If Quark has already found a problem, the Logging page says so before you ask.

The troubleshooting guide explains each finding.

Your logs have always lived in a Discord channel, which is a good place to see them arrive and a poor place to find one again. The Log Viewer puts the same logs on the web. Open it from Log Viewer in the dashboard sidebar.

• Live. New logs appear at the top as they happen.
• Details. Click an entry to see who did it, who it was done to, the channel, the reason and the message. Edits show the text before and after.
• Filters. By time, category, log type, channel, member and role. Your filters are part of the page address, so a filtered view can be sent to another moderator as a link.
• Ask in plain words. Type "messages deleted by @someone this week" or "who was banned yesterday" and Quark turns it into filters. Your question is handled on Quark's own servers and is not sent to an outside AI service.

What each plan gets

	Free	Pro Lite	Quark Pro
Live feed	Yes	Yes	Yes
History	Last hour	Last hour	30 days
Export CSV	No	No	Yes

The last hour of history on Free and Pro Lite was added in September; at launch those plans had the live feed only.

Logs keep being posted to your Discord channels as before. The plan only changes how far back you can look on the web.

The website and the dashboard were redesigned from the ground up.

• Home page. Rebuilt, with a live preview of what Quark's logs look like.
• Choosing a server. A cleaner list with search, and you can pin the servers you open most. Pins follow your account from device to device.
• Dashboard. A reorganised sidebar, clearer headings and one consistent look across the settings pages.
• Walkthrough. The first time you open a server's dashboard, a short tour takes you through setting a log channel and the settings that matter most.
• Light mode has been reworked rather than left as an afterthought.

The full story is on the blog: Quark Logger's 2026 Website Refresh.