Automations

​

Create a rule

​

What a rule is made of

​

When

​

A message is sent, a reaction is added

• They are named on their own. No Anything in category includes them, so a rule on all of Messages does not start running on every message.
• Quark’s own messages and reactions never set them off, and neither does anything sent through a webhook, which is how every log is posted. Messages Discord posts itself, such as a join or a boost notice, do not count as sent. A reaction on one of Quark’s messages or on a webhook message does not set off Reaction Added.
• Your ignore rules and log channels play no part: there is no log to leave out or send.
• The person who did it is the one who sent the message or added the reaction. Discord says who that is, so it is never a guess. There is nobody it happened to, so a rule that only watches these two cannot ask about or act on “the person it happened to”.
• With no log, a rule on either cannot add a notice, hold a log back, change a log’s colour or send a copy of a log. Use an alert or forward the message instead.
• The message is still there, so a rule can delete, pin, react to, reply to or forward it, and set slowmode in its channel.
• On Reaction Added, the name is the emoji: 🚩 itself, or the name of one of your server’s own emoji. The number is how many of that emoji the message has, this reaction included. A starboard is “the number of reactions is at least 5”. If Quark could not read the message, the number is not known, and a condition on it is not met.
• On Reaction Added, a rule alerts or forwards about the same message once. A starboard that alerts at 5 stars does not alert again at 6. The rule’s other steps, such as a reaction or a timeout, are not held back by this.
• Try your last 50 logs has nothing to try a rule on these against, because Quark keeps no log of them. Try it works.

​

A tag is sent, a button is pressed

• The person who did it is whoever sent the tag or pressed the button. The person it happened to is the person the tag was sent to with user:. On Tag Sent, the rule runs once for each person the tag was sent to, up to 5. A tag sent to nobody has nobody it happened to.
• The name is the tag’s name. On Tag Button Pressed, the message is the button’s label.
• Like Message Sent and Reaction Added, these are not logs: ignore rules and log channels play no part, and a rule on them cannot add a notice, hold a log back, change a log’s colour or send a copy. The press itself is still recorded as a Rule Action log.
• A tag’s Automations section lists the rules about it, and New automation there starts a rule with the tag already chosen.

​

And only if

• And: this one and the one above both have to be true.
• Or: this one starts another set of conditions. Every condition in a set has to be true, and any one set being true is enough.

• A condition about something the log does not say is not met. Its opposite is not met either. A rule about “the person who did it” does not run on a log that names nobody. They did it to themselves needs a log that names both people, No reason was given needs one of the five logs above, and The message is new, or old needs a log about one message. The builder warns when none of the logs a rule watches can answer a condition.
• It keeps happening counts only the logs the rule’s other conditions are true for. With “the message contains a link” beside it, 3 times means 3 messages with a link, not 3 messages of any kind. A log one of the other conditions cannot be answered for, such as a deleted message Quark never saw the text of, is not counted. A rule can have two counts. A rule that counts cannot also add a notice, hold the log back or change its colour.
• It’s a certain time of day is read on the clock of the time zone you choose, daylight saving included. The window starts at the first time and stops just before the second.
• A message’s age is measured from when it was posted to when the log is made.

​

Text a rule can read

​

Lists of words

• Your own words: type a word or phrase and press Enter. Pasting several at once splits them. A list holds up to 200, each up to 100 characters.
• One of Quark’s lists: choose one in the menu. The builder shows what it has, roughly how many entries, and where it comes from.

• Case is ignored, and so are the different ways of writing the same letter, such as full-width letters, and extra spaces.
• Words are matched whole: ass is not found in “class”. A phrase such as bad word is found in “a BAD, word”.
• An entry with no letters or digits, such as an emoji or :), is looked for anywhere in the text.
• An entry that is a web address, such as bit.ly or discord.com/invite, is matched against the web addresses in the text, including the ones it is part of: bit.ly catches go.bit.ly/x.
• An entry written as a file ending, such as .zip, matches the end of a file name. .img does not catch IMG_1234.jpg, and archive.tar.gz ends in .gz. Use it with the names of the files.

​

Forums and their posts

• It applies to forum and media channels only. A rule about a text channel does not match logs from threads in it.
• If Quark cannot find out which forum a post is in when the log is made, the rule compares the post alone.
• Try your last 50 logs matches a forum’s posts the same way.
• When a log names a moderator only because a bot put their ID at the start of its audit log reason, a rule treats the bot as the person who did it. Conditions, counts and {executor} all read the bot. Wick, YAGPDB, Sapphire, ProBot and Quark’s own commands are the exception. See your own bot.

​

Then

• The message. Forward, Reply, React, Delete and Pin act on the message the log is about, so they are only offered on a rule that watches nothing but message edits, pins, Message Sent and Reaction Added, where the message still exists.
• People. Each acts on the person who did it or the person it happened to, whichever you choose.
• Voice. Moving, disconnecting, muting and deafening are only offered when at least one log the rule watches has someone in voice, such as Joined Channel. They are skipped, at no cost, for someone who is not in voice when the rule acts.
• Channels. Each changes a channel you choose, or this log’s channel. This log’s channel is only offered when every log the rule watches happens in a channel of that kind: a voice channel for its status, a text channel for its topic, and not a thread for a lock, a new name or a topic. A slowmode, name or topic the channel already has is left alone, and costs nothing.
• A channel’s name and topic can each be changed by rules once every 5 minutes, because Discord allows only two renames of a channel in 10 minutes.
• An alert or a forward can’t be sent to a category, a forum, a media channel or a directory: those take no messages of their own.
• An action the logs a rule watches can’t take is not offered. If a rule already has one, the block says why and the rule can’t be saved until it is changed.

​

Locking a channel

​

Text from the log

​

Alerts as embeds

• The alert’s text is the embed’s text.
• The embed’s title is optional, up to 200 characters as you write it, on one line. It can use the tokens above.
• The colour is a hex code such as #C336C3, or left empty for Discord’s own.
• The role it pings is mentioned outside the embed, where a ping works.

​

Copies

• A copy never carries the log’s files, and leaves out any picture that was one of them, such as a new emoji or an old avatar.
• A copy has none of the log’s own buttons, such as Edit Reason and Lock on a ban or Ban on a join. Those act on the log or on a member, and stay in your log channel. A copy has no action buttons either.
• A rule can send copies to up to 3 channels. One log is copied to at most 3 channels, whatever the rules say, and to each channel once.
• A copy is never posted in the log’s own channel: the channel the log went to, or the one it was held back from.
• A log that was sent to your Age-restricted channel is only copied to a channel that is age-restricted too.
• With Don’t send this log in the same rule, the log goes to the copy’s channel instead of your log channel. That is how a rule sends some logs somewhere else.
• When one event produces two logs, such as a role given and another taken in one change, each log is copied. Anything else the rule does, it does once for the event.
• When voice events or reaction removals are bundled into one log, the events in the bundle are not copied.
• Saving a rule that sends a copy, or switching one on, also needs View logs under dashboard access. See who can view and edit rules.
• A copy is the log. To post the message itself, forward the message.

​

Forwarding the message

• It is only offered when the message is still there: on message edits, pins, Message Sent and Reaction Added.
• The channel has to take messages. A category, a forum, a media channel or a directory cannot be chosen.
• A message in an age-restricted channel is only forwarded to a channel that is age-restricted too. If Quark cannot tell whether either channel is, the message is not forwarded.
• A forward counts as an alert towards the hourly limits.
• A forward shows the message to whoever reads that channel. Saving the rule needs View logs, and the person who last changed the rule must be able to read the channel the message came from each time it runs. See who can view and edit rules.
• If Quark cannot post in the channel, the forward is skipped and the rule’s row says so.

​

Starters

• These starters work on every plan, the free one included. To only be told, remove the moderation action under Then before saving.
• “Roles members give themselves” are role changes where Discord’s audit log names the member as the one who made the change. A role a bot hands out when someone reacts or presses a button was given by the bot. Use the verification bot starter for those.
• A ghost ping, for the starter, is a message that mentions a member or a role and that its author deletes within 10 seconds of posting it. It does not catch @everyone or @here.
• The starter for someone with a role leaving watches one role. To watch two, such as Staff and Booster, make a second rule for the other role, or use an advanced condition.

​

Dry run and Try it

• Dry run is a switch on the rule. A rule in dry run counts how often it would have run and does nothing else: no post, no ping, no action. Its row shows the count for the week.
• Try it runs the rule you are editing against sample logs and marks which would set it off. Nothing is posted.
• Try your last 50 logs, on Quark Pro, does the same against the last 50 logs of the types the rule watches. Someone with dashboard access needs View logs and View log history to use it.

​

What each plan gets

​

Who can view and edit rules

• The dashboard’s messages call Timeout Members “Moderate Members”. It is the same permission.
• The permissions that act in a channel are read in that channel: deleting or pinning a message in the message’s channel, and the channel actions in the channel they change. A channel that takes a permission away from your roles stops you saving a rule that uses it there.
• The server owner can save any rule. Administrator covers the permissions, but not the rule about your highest role.
• Only the server owner can save a rule that gives a role with a moderation or management permission, or switch it on, rename it or take it out of dry run. Those permissions are Administrator, Manage Server, Manage Channels, Manage Roles, Manage Messages, Manage Webhooks, Manage Expressions, Manage Threads, Kick Members, Ban Members and Timeout Members. Only the role’s own permissions are read, not what a channel allows it. Anyone who can edit rules can still switch such a rule off or put it into dry run, and a rule that takes such a role is not restricted this way.
• Quark asks Discord for your permissions each time you save a rule with a moderation action, switch it on, take it out of dry run or rename it. If Discord does not answer, the change is refused.
• The rule then acts for you. See who a rule acts for.
• If Quark is missing a permission, the step is skipped and the rule’s row says why. See permissions.

​

Changes that let more logs reach a rule

• Changing the order of the rules.
• Deleting, switching off, putting into dry run or editing a rule that holds logs back.
• Under Logging: removing an ignore rule, switching a log type or a category on, switching Actions by bots, Actions on bots or PluralKit Compatibility off, giving logs a channel where they had nowhere to go, and setting or clearing the Files channel.

• If one of the server’s rules gives a role with a moderation or management permission, only the server owner can make these changes.
• Changes that leave more out, such as adding an ignore rule or switching a log type off, are never checked. Neither is switching Active Ignore on or off.
• Quark asks Discord for your permissions when you make the change. If Discord does not answer, the change is refused.
• The Logging pages do not say which permission is missing. They say “You don’t have permission to do that.”
• This is checked on the dashboard. The /logging and /troubleshoot commands in Discord go by their own permissions.

​

Who a rule acts for

• The server owner passes every check. Administrator covers the permissions, but not the two rows about the highest role.
• The forward and quote check stops a rule copying messages out of a channel its author cannot read into one they, or others, can. A timeout does not stop it, because a member who is timed out can still read.
• For the moderation rows, the permission has to come from one of the person’s own roles. One that only @everyone has does not count. For reading a channel, @everyone’s View Channel and Read Message History do count.
• A message from an age-restricted channel is only forwarded or quoted into a channel that is age-restricted too, and is never quoted in a direct message. If Quark cannot tell whether a channel is age-restricted, the step is skipped.
• When a check fails, that step is skipped and uses nothing from the hourly limits. Alerts, notices and held-back logs are not affected.

​

If a rule stops acting

​

Safety rules

• the server owner
• Quark itself
• a member whose highest role is level with or above Quark’s highest role
• someone who is no longer in the server

• On these logs Quark cannot be certain who did it, so a rule that acts on the person who did it cannot be saved: deleted messages, bulk deletes, attachments and polls, Moved, Disconnected, server mutes and deafens, pins, and removed reactions. For a removed reaction, Discord says whose reaction it was and not who removed it. For the others, Quark matches the event to the audit log and can be wrong.
• When the moderator was found through another bot, as in “using Sapphire”, the step is skipped.

• Moderation is counted in members, not actions. Everything one rule does to the same member in an hour counts once.
• One rule acts on the same member at most 20 times an hour.
• A member that two rules act on counts once for each rule towards the server’s 30.
• Each member a rule moderates also uses one of the alerts in the first column. Moderation does not stop when the alerts run out.
• A channel action counts once for each channel, and pinning once for each message, in the second column.
• A copy of a log, a forward, a reply and a reaction count as alerts. Notices, colours and held-back logs are not counted, and neither is an action that was skipped.
• Past a limit, actions are skipped until the next hour. The rule’s row says so.

• Sent only to people who are in the server, and never to a bot.
• Not sent to the person a User Left, Kick, Ban or Bot Removed log is about. They have left.
• One rule messages one member at most once every 10 minutes.
• Quark adds a last line that the rule cannot remove: “Sent automatically by a rule in” and the server’s name.
• Members with DMs closed do not get the message.

• A rule acts once on each event, however many times Discord reports it.
• What Quark does itself never sets a rule off. A rule that bans does not trigger a rule that watches bans, and a rule that sets a voice channel’s status when a status is set does it once.
• A rule’s timeout never shortens a longer timeout.
• Rules only see logs that pass your ignore rules and have a log channel. A log only goes to another channel when a rule sends a copy there. Message Sent and Reaction Added are not logs, so neither applies to them.

​

What is logged

• Moderation actions are logged even when the Rule Action log type is switched off. Alerts, forwards, replies, reactions and the other two follow the switch.
• A rule reaching its limit, or failing to act, is logged at most once an hour for each rule and reason.
• Notices, colours, copies and held-back logs do not produce a Rule Action log. A copy that cannot be posted, because Quark cannot post in the channel or the channel is gone, is said on the rule’s row.

​

Advanced conditions

executor.bot && content matches "discord.gift/*"
@Staff in target.roles || target.accountAgeDays < 7
count(10m, target) >= 5
content containsAny list("scam-links")
status in ["free nitro", "join my server"]
fileNames containsAny [".exe", ".scr"]
attachments > 3
reason contains executor.id
executor == target
!reasonGiven && timeBetween("22:00", "06:00", "Europe/London")
messageAgeSecs < 10 && content contains "<@"

• Join with &&, ||, ! and brackets. Compare with ==, !=, <, <=, >, >=.
• Text has contains, startsWith and matches. Put text in double quotes.
• A list is written ["a", "b"], or list("profanity-en") for one of Quark’s. in asks whether the text is one of the entries, and containsAny whether it has one as a whole word, as in lists of words. Quark’s lists are profanity-en, profanity-de, profanity-es, profanity-fr, profanity-pl, profanity-pt, profanity-tr, scam-links, link-shorteners, discord-invites and risky-files.
• Write a role or member as @name and a channel as #name. Test a role with in, as in @Staff in executor.roles.
• count(10m) is how many times the rule’s logs have happened in the window for the same member doing it. Add target or channel to count for those instead, or server to count for the whole server.
• timeBetween("22:00", "06:00", "Europe/London") is whether it happened between two times of day. Times are 24-hour, and the zone is an IANA name such as Europe/London, America/New_York or UTC.
• An expression can be up to 500 characters.

​

The API