Automations

​

Create a rule

​

What a rule is made of

​

When

​

And only if

• 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.
• It keeps happening counts every log the rule watches for that member or channel, not only the ones that meet the other conditions. A rule can have two of these. A rule that counts cannot also add a notice or hold the log back.
• 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

​

Starters

​

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 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 permission has to come from one of the person’s own roles. One that only @everyone has does not count.
• 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.
• Notices 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.
• A rule’s timeout never shortens a longer timeout.
• Rules only see logs that pass your ignore rules and have a log channel. A rule never moves a log to another channel.

​

What is logged

• Moderation actions are logged even when the Rule Action log type is switched off. Alerts 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 and held-back logs do not produce a Rule Action log.

​

Advanced conditions

executor.bot && content matches "discord.gift/*"
@Staff in target.roles || target.accountAgeDays < 7
count(10m, target) >= 5
reason contains executor.id

• Join with &&, ||, ! and brackets. Compare with ==, !=, <, <=, >, >=.
• Text has contains, startsWith and matches. Put text in double quotes.
• 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.
• An expression can be up to 500 characters.

​

The API