Skip to main content

​
Moderation commands

The moderation commands that act on a member check the same things before they act:
  1. You need the matching Discord permission.
  2. Quark needs the same permission. See permissions.
  3. The member must be in the server. /ban, /kick, /mute and /unmute do not work on someone who has left.
  4. Your highest role must be above the member’s highest role, unless you own the server.
  5. Quark’s highest role must also be above the member’s.
/unban and /purge only check the first two. Reasons can be up to 480 characters. The action is recorded in Discord’s audit log with your user ID in front of the reason, so Quark’s modlog shows you as the moderator and not Quark.

​
/ban

Bans a member. delete removes their messages from the last 1 to 7 days. Leave it out to delete nothing.

​
/unban

Takes a user ID, not a mention, because a banned user is not in the server to be mentioned.

​
/kick

Removes a member from the server. They can rejoin with an invite.

​
/mute and /unmute

/mute applies a Discord timeout. It does not use a “Muted” role.
  • time is a number. type is the unit: minutes, hours or days. If you leave type out, the unit is days.
  • Decimals work. time: 1.5 with type: hours is 90 minutes.
  • The longest timeout is 28 days. That is Discord’s limit.
  • Members with Administrator and the server owner cannot be timed out.
/unmute removes the timeout.

​
/purge

Deletes the most recent messages in the channel where you run it. count is 2 to 100.
  • Messages older than 14 days are skipped. Discord does not allow them to be deleted in bulk.
  • It deletes everything in range, including pinned messages. There is no filter by member.
  • The reply tells you how many messages were actually deleted.

​
Buttons on logs

Buttons are not restricted the way commands are. Anyone who can see the log can press one, so Quark checks permissions itself where it matters.

​
Modlog reasons

Edit Reason changes the reason shown on Quark’s log. It does not change Discord’s audit log. It edits the modlog it is pressed on, whichever channel that is in, including a modlog type that has been given a channel of its own.
  • Each edit adds a line under the reason: “Edited by”, the moderator and the time. From the second edit the line counts the edits and names the last editor.
  • Lock stops the reason being edited, permanently. Edit Reason and Lock are removed from the modlog, leaving History. Nobody can unlock it, whatever their permissions.
  • History appears after the first edit, lock or change to the modlog’s images.
  • Your server can also lock every reason after a set time, or switch editing off. See modlog reasons. When that setting is what stops an edit, Lock does nothing and the reply says why.
  • Modlogs posted before these buttons existed have only Edit Reason. They gain the others the first time their reason is edited.
  • On a busy channel, a modlog can be posted in the same message as other logs. See rate limits. It is then posted without Edit Reason and Lock. On an older message that holds several logs and still has the buttons, Edit Reason replies that the modlog shares its message with other logs and its reason can’t be edited. Lock and History still work there, and apply to the whole message.
Every edit, lock and change to the images is recorded on every plan. The plan only decides how much of the record History shows. See data for how long it is kept.

​
Modlog images

Edit Reason is also where a moderator adds images to a modlog, such as a screenshot of what the member did. The form it opens has the reason, an Images field and, once the modlog has images, a Remove the images already attached tick box.
  • A modlog can hold up to 4 images. Each can be up to 6 MB and has to be a PNG, JPEG, GIF or WebP.
  • The images are attached to the modlog’s message in your channel. Quark does not keep a copy of them. See data.
  • To add images without changing the reason, leave the reason as it is. If you empty the reason box, the reason becomes “[no reason provided]”.
  • Removing takes off every image on the modlog. To replace them, tick the box and add the new ones in the same form.
  • If an image is too large, is not an image, or would take the modlog past 4, nothing is changed, the reason included. The reply says which it was.
  • Adding images takes a few seconds. Quark replies once the modlog has been updated.
  • Changing the images does not add an “Edited by” line. It is recorded in History.
Images follow the same rules as the reason. The same members can change them, and they cannot be added or removed once the modlog is locked, once your server’s modlog reasons setting has stopped edits, or on a modlog that shares its message with other logs. A locked modlog keeps the images it has. Images are on every plan.

​
See initial reactors

Right-click a message, or long-press it on a phone, then choose Apps → See initial reactors. Quark tells you who added each reaction first. It only works while Quark still has the message stored. See message age.

​
Get IDs

Right-click a log, or long-press it on a phone, then choose Apps → Get IDs. Quark replies, only to you, with every ID in that log: the members, roles and channels it mentions, the ID in its footer, and each author on a Multiple Messages Deleted log.
  • Each ID is listed next to a mention, so you can see whose it is. Nobody is notified.
  • Under the list is a numbered button for each ID. Press one and Quark replies with that ID alone, which is easy to copy on a phone.
  • A log with a single ID gets that ID as the whole reply.
  • On a modlog, the member and the moderator are labelled User and Moderator. On other logs the IDs are not labelled, so go by the mention.
  • Up to 20 IDs are listed. Any beyond that are counted at the end.
It works whether or not the User ID button is switched on for your logs, and it also gives you the IDs the button does not, such as the moderator’s. It only works on a log posted by the bot whose command you chose. On any other message Quark replies that it is not a valid Quark log.

​
Report log issue

For a log that looks wrong: the wrong moderator, a missing detail, a layout that broke. Right-click the log, or long-press it on a phone, choose Apps → Report log issue, and say what is wrong in up to 1,000 characters. Quark sends its developers:
  • What you wrote.
  • A copy of the log: its text, its embeds and buttons, and the names and sizes of any files on it. The files themselves, and the addresses of images and avatars, are left out.
  • Your server’s ID, language and plan, your user ID, and the IDs of the log’s channel, its message and the webhook that posted it.
The copy includes everything written in the log, such as the content of a deleted message. Only report a log you are happy for Quark’s developers to read.
  • The reply gives you a reference. Mention it in the support server to follow the report up.
  • Each person can send one report a minute in a server.
  • The form can be sent for up to an hour after you open it. After that, start again from the log’s menu.
  • Quark holds the copy of the log while the form is open, and removes it once the report is sent or the hour is up.
Like Get IDs, it only works on a log posted by the bot whose command you chose.

​
/language

Sets the language Quark uses for everything in your server, including logs. See languages.

​
/debug

Sends a report to Quark’s developers containing your server ID, which permissions Quark has, your plan, and Quark’s configuration for your server. Only run it when support asks you to.

​
/vote

Shows the link to vote for Quark on Top.gg and what your votes have unlocked. See voting.

​
/premium

On a server without a plan, explains Quark Pro. On a server with one, links to getting started with a subscription.