On a server with an automation rule that moderates, a change here that lets more be logged needs a Discord permission as well. See changes that let more logs reach a rule.
Ignore rules
Logging → Ignore Rules. Anything you add here is left out of your logs. To do something when a log matches, instead of leaving it out, use automations. Two words matter. An executor is whoever did something. A target is whoever, or whatever, it was done to. If a moderator deletes a member’s message, the moderator is the executor and the member is the target.- Add members by searching for them or pasting a user ID.
- A forum channel is ignored together with all its posts.
- Exact content only matches the whole message, exactly. It is meant for things like bot commands.
- Each entry can be up to 100 characters.
If Quark cannot tell who did something, because it has no access to the audit log, Who did it and Roles that did it cannot apply to that log. See permissions.
Bots
Two switches in the Bots group at the bottom of the same tab decide whether actions involving bots are logged.
Both are on by default. Turning them off needs Quark Pro or Pro Lite. On the free plan they stay on. Some log types ignore these switches and are always sent. See actions by bots.
Switch log types on and off
- A whole category: turn its switch off under Logging → Channels.
- One log type: choose it under Logging → Individual Log Config and turn Enabled off.
/logging.
Other options
Logging → Other.Modlog reasons
- The time is counted from when the modlog was posted. Once it has passed, Edit Reason replies that the modlog is locked.
- A timed lock is not written on the modlog. If you choose a longer time, or Always editable, older modlogs can be edited again.
- Never editable is different. Modlogs posted while it is set have no Edit Reason button, and do not gain one if you change the setting later.
- A moderator can also lock a single modlog with its Lock button. Unlike a timed lock, that one is permanent: no setting here makes the modlog editable again. See buttons on logs.
- Changing the setting produces a Logging Options Updated log.
Active Ignore
Active Ignore is for servers that run a bot of their own. It lets the bot ask Quark not to log something the bot is about to do, or has just done, such as a message it deletes as part of a command.- Switch Active Ignore on for the log type under Logging → Individual Log Config.
- Have your bot send a request to the API, naming who will do it or what it will be done to. Quark leaves out the next matching log.
- A request covers one log unless it asks for more, and lasts 10 seconds unless it asks for longer. The most is 100 logs and five minutes.
- While Active Ignore is on for a log type, every log of that type is held for about three seconds before it is sent, so that a request made just after the action still counts. Leave it off unless your bot uses it.
- When many logs arrive at once, some are sent without that wait, and only a request made before the action leaves those out. Where you can, send the request before your bot acts.
- A request is not used up by a log your ignore rules leave out anyway.
- To switch it on for every log type at once, set
active_ignorethrough the API. - A request that names no log type never leaves out a modlog (Ban, Unban, Kick, Timeout, Timeout Removed), a Quark Events log, Member Leave or Bot Removed. To leave one of those out, the request has to name the log type and be made with an Admin token. A Basic token is refused.
- Quark records requests in Quark Events, as an Ignore Options Updated log that names the token by its ID and says what was asked for. A request that names one of those log types is recorded every time. Any other request is recorded once an hour for each token, and that log shows the token’s first request of the hour, not the ones that followed.
- The record is posted even when Ignore Options Updated is switched off. Nothing is posted if Quark Events is switched off or has no channel to go to.