Changelog

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.