Moderation Features

Quo provides several moderation tools to help you manage your Discord server effectively. These tools include message management, member management, role management, and channel management features.

Commands

Message Management

/clear (Aliases: purge)

Purge messages from a channel with various filtering options.

Subcommands:

• /clear [amount] - Remove a specific number of messages
• /clear [member] [amount] - Remove messages from a specific member
• /clear embeds [amount=100] - Remove messages containing embeds
• /clear files [amount=100] - Remove messages with file attachments
• /clear images [amount=100] - Remove messages with embeds or attachments
• /clear all [amount=100] - Remove all messages (except pinned)
• /clear user [member] [amount=100] - Remove messages from a specific user
• /clear contains [text] - Remove messages containing specific text
• /clear bot [prefix] [amount=100] - Remove bot messages and messages with prefix
• /clear emoji [amount=100] - Remove messages containing custom emoji
• /clear reactions [amount=100] - Remove all reactions from messages

Traditional Commands:

• qclear 10 - Delete 10 messages
• qclear @user 25 - Delete 25 messages from user
• qpurge embeds - Delete messages with embeds
• qclear bot q - Delete bot messages and messages starting with q

Required Permissions:

• User: Manage Messages
• Bot: Manage Messages

Examples:

/clear 50
/clear embeds 100
/clear contains spam
qclear bot q 50

/selfclean

Remove Quo’s messages from a channel.

Traditional Command: qselfclean [amount=100]

Notes:

• If Quo has Manage Messages permission, it will also delete command messages
• Maximum search limit: 1000 messages

Member Management

/kick

Kick a member from the server.

Options:

• member: The member to kick
• reason: Reason for kicking (optional)

Traditional Command: qkick @user [reason]

Required Permissions:

• User: Kick Members
• Bot: Kick Members

Cooldown: 3 uses per 1 second per user

Example:

/kick member: @Troublemaker reason: Spamming in channels
qkick @Troublemaker Violating server rules

/ban

Ban a member from the server.

Options:

• member: The member to ban (can be ID for users not in server)
• reason: Reason for banning (optional)

Traditional Command: qban @user [reason]

Required Permissions:

• User: Ban Members
• Bot: Ban Members

Cooldown: 3 uses per 1 second per user

Example:

/ban member: @Troublemaker reason: Repeated rule violations
qban 123456789012345678 Raiding

/unban

Unban a user from the server.

Options:

• user: The user to unban (ID or Name#Discriminator)
• reason: Reason for unbanning (optional)

Traditional Command: qunban UserID [reason]

Required Permissions:

• User: Ban Members
• Bot: Ban Members

Cooldown: 3 uses per 1 second per user

Example:

/unban user: 123456789012345678 reason: Appeal approved
qunban 123456789012345678

Role Management

/role

Add a role to one or multiple users.

Options:

• role: The role to add
• users: The users to add the role to

Traditional Command: qrole @role @user1 @user2 ...

Required Permissions:

• User: Manage Roles
• Bot: Manage Roles

Notes:

• If no users are specified, you’ll be prompted to add the role to all members
• Includes a revert button to undo the action

/rrole (Aliases: removerole, takerole)

Remove a role from one or multiple users.

Options:

• role: The role to remove
• users: The users to remove the role from

Traditional Command: qrrole @role @user1 @user2 ...

Required Permissions:

• User: Manage Roles
• Bot: Manage Roles

Notes:

• If no users are specified, you’ll be prompted to remove the role from all members who have it
• Includes a revert button to undo the action

Channel Management

/lock (Alias: lockdown)

Lock a channel, category, or the entire server to prevent messages.

Subcommands:

• /lock [channel] [duration] - Lock a specific channel
• /lock server [duration] - Lock the entire server

Traditional Commands:

• qlock [channel] [duration]
• qlock server [duration]

Required Permissions:

• User: Manage Channels
• Bot: Manage Channels (for server lock: Manage Guild)

Examples:

/lock channel: #general duration: 1h
/lock server duration: 30m
qlock #announcements 2h

/unlock (Alias: unlockdown)

Unlock a previously locked channel, category, or server.

Subcommands:

• /unlock [channel] - Unlock a specific channel
• /unlock server - Unlock the entire server

Traditional Commands:

• qunlock [channel]
• qunlock server

Required Permissions:

• User: Manage Channels
• Bot: Manage Channels (for server unlock: Manage Guild)

/maintenance

Enable or disable maintenance mode for the server.

Subcommands:

• /maintenance on [role] - Enable maintenance mode
• /maintenance off [role] - Disable maintenance mode

Traditional Commands:

• qmaintenance on [role]
• qmaintenance off [role]

Required Permissions:

• User: Administrator
• Bot: Manage Channels

Notes:

• Creates special maintenance channels that remain accessible
• Can be applied to specific roles or the entire server
• Automatically creates maintenance-chat and maintenance-vc channels

Button Interactions

• Confirm Action - Confirms moderation actions when prompted
• Cancel Action - Cancels moderation actions when prompted
• Lock All - Locks all channels in a category
• Unlock All - Unlocks all channels in a category
• Role Revert - Reverts role addition/removal actions
• Maintenance Toggle - Quickly toggles maintenance mode

Tips for Effective Moderation

1. Message Cleanup:

   • Use specific clear subcommands to target only necessary messages
   • For large cleanups, use multiple smaller clear commands rather than one large one
   • Use clear contains to quickly remove spam with common phrases

2. Role Management:

   • Set up proper permission hierarchies before using role commands
   • Use the revert buttons if you accidentally add/remove roles incorrectly
   • For mass role changes, test on a single user first

3. Server Security:

   • Always provide a reason for moderation actions for transparency and audit logs
   • Use maintenance mode during server updates or configuration changes
   • Set up timed locks for temporary situations (e.g., raid prevention)

4. Command Efficiency:

   • Learn the traditional command syntax for faster moderation
   • Use command aliases like purge instead of clear when preferred
   • Combine filters (like clear bot q) for more precise message removal