Commands
244 commandsEvery command Notoq registers, with what it does, which parameters it takes and which permission it needs.
244
Commands
22
Categories
217
Free
27
Premium
181
Also as text command
Most of it is set up on the dashboard
Commands are what you run in the moment. Welcome messages, level rewards, automations, tickets, security and the rest are configured on the web dashboard, with previews and without memorising a single option name.
Showing 20 of 244 commands
Bans a user from the server and records the case.
How it works
Works on people who already left, because it takes a user rather than a member. The reason field autocompletes from the reason templates configured for the server, and you can attach an image as evidence, and it is kept with the log entry, not just posted once. delete_message_days removes that user's messages from the last 0-7 days. The ban is written to the moderation log and the target is notified by DM before it takes effect.
Parameters
userUserrequiredThe user to ban.
reasonTextoptionalReason. Autocompletes from your reason templates.
delete_message_daysNumber 0-7optionalDelete that user's messages from the last X days. Default 0.
imageAttachmentoptionalEvidence image, kept with the log entry.
Removes a member from the server.
How it works
A kick is not a ban: the person can rejoin with a new invite. Same reason templates and same evidence image as /ban, and the same log entry. Requires the member to still be on the server. Someone who already left cannot be kicked.
Parameters
memberMemberrequiredThe member to kick.
reasonTextoptionalReason. Autocompletes from your reason templates.
imageAttachmentoptionalEvidence image, kept with the log entry.
Mutes a member for a set duration using Discord's own timeout.
How it works
The duration is written the way you would say it: 2h, 1d12h30m, 45m. Discord caps a timeout at 28 days. During it the member can read but cannot post, react, or speak in voice. Reason templates and evidence image work as with /ban.
Parameters
memberMemberrequiredThe member to time out.
durationTextrequiredFor example 2h, 45m, 1d12h30m. Discord's ceiling is 28 days.
reasonTextoptionalReason. Autocompletes from your reason templates.
imageAttachmentoptionalEvidence image, kept with the log entry.
Lifts an active timeout early.
How it works
Refuses if the member is not actually timed out, so you do not accidentally log a lift that never happened. The lift is written to the moderation log with your reason.
Parameters
memberMemberrequiredThe member whose timeout should end.
reasonTextoptionalWhy the timeout is being lifted.
imageAttachmentoptionalOptional image for the log entry.
Lifts a ban by user ID.
How it works
Takes an ID rather than a user picker, because a banned account cannot be picked from a member list. Copy it from the ban list or from the original log entry.
Parameters
user_idTextrequiredThe numeric ID of the banned account.
reasonTextoptionalWhy the ban is being lifted.
imageAttachmentoptionalOptional image for the log entry.
Stops members from posting in a channel.
How it works
Takes away Send Messages from @everyone on that one channel. Roles with an explicit allow still get through. That is deliberate, so your team can keep talking in a locked channel. Without an argument it locks the channel you are in.
Parameters
channelText channeloptionalWhich channel. Defaults to the current one.
Reverses a lock.
How it works
Puts Send Messages back to inherited rather than to an explicit allow, so the channel returns to whatever your category permissions say instead of gaining a new override.
Parameters
channelText channeloptionalWhich channel. Defaults to the current one.
Empties a channel by cloning and deleting it.
How it works
Every message is gone, permanently. There is no undo. The clone keeps the name, topic, permissions and position, but it is a new channel with a new ID, so pinned messages, webhooks and anything referencing the old ID break. A confirmation dialog stands in front of it and only the person who ran the command can confirm.
Parameters
channelText channeloptionalWhich channel. Defaults to the current one.
Bulk-deletes up to 100 messages with filters.
How it works
The filters stack: you can ask for the last 100 messages from one person that contain a word and carry no attachment. Bot messages are skipped unless you name a user explicitly. Discord itself refuses to bulk-delete anything older than 14 days, so old messages survive a purge no matter what you set.
Parameters
amountNumber 1-100requiredHow many messages to scan and delete.
userMemberoptionalOnly messages from this person.
containsTextoptionalOnly messages containing this text.
no_embedsYes/NooptionalOnly messages without embeds.
no_attachmentsYes/NooptionalOnly messages without attachments.
Warns a member and opens a numbered case.
How it works
Every warning gets a case ID that counts up per server, so /unwarn 14 always means the same thing. The member is told by DM. Warning yourself, a bot, or anyone who can time out members is refused. A moderator cannot warn another moderator through this command. The note is for your team only and never reaches the person warned. If warning escalation is configured in the dashboard, hitting the configured count triggers the action automatically.
Parameters
userUserrequiredWho is being warned.
reasonText, max 1000requiredThe reason. This is what the member sees.
noteText, max 500optionalInternal note. Moderators only, never shown to the member.
Withdraws a warning by case ID.
How it works
The case ID autocompletes from the warnings that are still active, so you cannot pick one that is already withdrawn. The case is not deleted: it is marked inactive and keeps who withdrew it, when, and why. It stops counting towards escalation but stays readable in the history.
Parameters
case_idNumberrequiredCase ID. Autocompletes from active warnings.
reasonText, max 500optionalWhy the warning is being withdrawn.
Shows the full warning history of one member.
How it works
Active and withdrawn warnings, newest first, five per page with buttons to page through. Withdrawn ones are shown with who withdrew them and when, so the record stays honest instead of just shrinking.
Parameters
userUserrequiredWhose history to show.
Shows your own active warnings on this server.
How it works
Needs no permission, anyone can look themselves up. Only active warnings, up to ten, with reason, date and the moderator who issued them. Internal notes are not part of it.
Withdraws every active warning of one member at once.
How it works
Administrator only, and behind a confirmation that names the count first. Like /unwarn, the cases survive as withdrawn entries rather than disappearing. If the member has no active warnings, nothing happens and you are told so.
Parameters
userUserrequiredWhose warnings to clear.
reasonText, max 500optionalWhy. Written to every affected case.
Opens one case in full.
How it works
Everything the case holds: reason, moderator, channel it was issued in, every note with its author and timestamp, and, if it was withdrawn, who did that and why. Autocompletes over all cases, active or not.
Parameters
case_idNumberrequiredCase ID. Autocompletes over all cases.
Appends an internal note to an existing case.
How it works
Notes are stacked with author and timestamp, so a case can carry a conversation between moderators. One note is capped at 500 characters and all notes on a case together at 1000. When the room runs out you are told how much is left rather than having the note silently truncated. The member never sees any of it.
Parameters
case_idNumberrequiredWhich case. Autocompletes over all cases.
noteText, max 500requiredThe note. Moderators only.
Runs a full security posture scan and returns a score out of 100.
How it works
Walks the server against the posture checks (role permissions, verification level, 2FA requirement, invite and webhook hygiene, log coverage) and returns a score with a letter grade plus a count per severity. The eight worst open findings are listed inline; the rest live in the Security Center on the dashboard. The scan is recorded, so drift against the last run is visible later.
Applies every fix that is safe to apply without asking.
How it works
Only the remediations classified as safe run, the ones that cannot lock anybody out or remove access someone is relying on. Anything with a real blast radius is left for you and named in the "still needs your attention" list. A fresh scan runs straight after, so the reply shows the new score rather than the old one.
A written audit of the security configuration with recommendations.
How it works
Different from /security scan: the scan grades the server, the audit reads the setup and says what is missing. It flags a security system that is off, a missing log channel, and an unusually large number of roles carrying Administrator, and pairs each finding with a recommendation.
Freezes the server for a set number of minutes.
How it works
Four switches, all on by default: text channels (including forums and threads), voice and stage channels, new joins, and existing invites. The lockdown ends by itself when the timer runs out, so a forgotten lockdown does not become permanent. /security unlock ends it early.
Parameters
duration_minutesNumber 1-1440optionalHow long. Default 10 minutes, ceiling 24 hours.
lock_channelsYes/NooptionalLock text channels, forums and threads. Default yes.
lock_voiceYes/NooptionalLock voice and stage channels. Default yes.
lock_joinsYes/NooptionalBlock new members from joining. Default yes.
lock_invitesYes/NooptionalDisable existing invites. Default yes.
reasonTextoptionalRecorded with the lockdown.
Text commands
Many commands also work as text commands with the prefix “.”, and a few exist only that way. Premium servers can change the prefix, in which case the text form follows it.
Permissions
The permission shown is the one Discord requires before the command even appears in the menu. Some commands check further inside. A ticket can also be closed by the person who opened it.