About Ormi-Bot

Your all-in-one Discord moderation and community management solution

Why Choose Ormi-Bot?

Ormi-Bot combines powerful moderation tools with engaging community features to help you build and maintain a thriving Discord server.

Advanced Moderation

  • Multi-level warning system
  • Automated moderation logs

Community Tools

  • Reaction roles
  • Welcome messages
  • Giveaway system

Easy Configuration

  • Step-by-step setup
  • Detailed documentation

Technical Specifications

Discord.py 2.5.2

99.9% Uptime

Secure API

Setup Guide

Get Ormi-Bot in 4 Simple Steps

Requires all choosen by me permission

2. Configure Permissions

After inviting, verify the bot has these critical permissions:

  • Moderation: Kick, Ban, Manage Messages
  • Utility: Manage Roles, Manage Channels
  • General: Read Messages, Send Messages

3. Basic Configuration

Run these essential commands to set up your server:

;prefix ! - Change command prefix
;slc #mod-logs - Set moderation log channel
;swc #welcome - Set welcome channel

4. Test the Bot

Verify everything works with these test commands:

;help - View all commands
;ping - Check bot latency
;serverinfo - View server details

5. Advanced Setup (Optional to use)

Customize further with these features:

  • Reaction roles (;rr)
  • Ticket system (;st)

Features

Moderation Tools

Keep your server safe with powerful moderation commands like kick, ban and mute.

Fun & Games

Engage your community with fun commands like 8ball, meme, and rps.

Utility

Make server management easier with utility commands like poll and remindme.

Fun Commands

;ship

No permissions required

Full Syntax:

;ship @user1 @user2

Description:

Calculates compatibility between two users with a fun percentage score. Perfect for lighthearted community interactions and relationship jokes.

Parameters:

  • @user1: First user to compare
  • @user2: Second user to compare

Example Usage:

;ship @UserA @UserB
;ship @BestFriend @Crush

Required Permissions:

  • None - works for all users

Notes:

  • Results are randomly generated for entertainment
  • Includes fun ship names based on usernames
  • Works with user mentions or IDs
  • Great for community bonding and fun activities

;8ball

No permissions required

Full Syntax:

;8ball [question]

Description:

Provides mysterious answers to your yes/no questions. Great for decision-making games and fun interactions.

Parameters:

  • [question]: Your yes/no question (must end with ?)

Example Usage:

;8ball Will I win the lottery?
;8ball Should I order pizza tonight?

Required Permissions:

  • None - works for all users

Notes:

  • Has 20+ different possible responses
  • Questions must end with a question mark
  • Answers range from positive to negative to neutral
  • Pure fun - not meant for serious decisions

;hug

No permissions required

Full Syntax:

;hug @user

Description:

Sends a warm virtual hug with cute animations. Boosts server positivity and creates friendly interactions between members.

Parameters:

  • @user: The member to hug (mention or ID)

Example Usage:

;hug @BestFriend
;hug @NewMember (welcome gesture)

Required Permissions:

  • None - works for all users

Notes:

  • Includes 5+ different hug animations
  • Great for welcoming new members or comforting friends
  • Works in both servers and DMs
  • Cannot hug yourself (bot will playfully refuse)

;rate

No permissions required

Full Syntax:

;rate [thing]

Description:

Gives a completely arbitrary 1-10 rating to anything. Pure fun with no logic - perfect for silly debates and laughs.

Parameters:

  • [thing]: What you want rated (text only)

Example Usage:

;rate my outfit
;rate pineapple on pizza

Required Permissions:

  • None - works for all users

Notes:

  • Ratings are completely random
  • Includes funny commentary with each rating
  • Accepts any text input (within Discord limits)
  • Great for breaking the ice or starting conversations

;rps

No permissions required

Full Syntax:

;rps [rock/paper/scissors]

Description:

Classic rock-paper-scissors game against the bot. Supports standard choices and custom variants for fun competitions.

Parameters:

  • [choice]: Your move (rock, paper, or scissors)

Example Usage:

;rps rock
;rps paper
;rps scissors

Required Permissions:

  • None - works for all users

Notes:

  • Standard rules: rock beats scissors, scissors beat paper, paper beats rock
  • Includes fun reaction animations for wins/losses
  • Track your win/loss streak with the bot
  • Great for quick games and server interactions

;random

No permissions required

Full Syntax:

;random [min] [max]

Description:

Generates random numbers for decisions, games, or giveaways. Customize your range for different use cases.

Parameters:

  • [min]: Lowest possible number (default: 1)
  • [max]: Highest possible number (default: 10)

Example Usage:

;random 1 10 (basic range)
;random 100 1000 (custom range)
;random (default 1-10)

Required Permissions:

  • None - works for all users

Notes:

  • Supports negative numbers and decimals
  • Maximum range: -1,000,000 to 1,000,000
  • Great for deciding turns, picking winners, or RPG games
  • Combine with ;giveaway for random selections

;slap

No permissions required

Delivers a virtual slap with fun animations. For joking interactions between friends.

Usage:

;slap @user

Examples:

;slap @Friend (playful joke)
;slap @Rival (friendly competition)

;simprate

No permissions required

Measures someone's 'simp' level with a humorous percentage. All in good fun.

Usage:

;simprate @user

Examples:

;simprate @Friend
;simprate @Yourself (self-roast)

;howgay

No permissions required

Generates a random 'gay percentage' score for fun. Not scientifically accurate.

Usage:

;howgay @user

Examples:

;howgay @Friend
;howgay @RainbowUser

Note:

This is purely for entertainment. Always use respectfully.

Moderation Commands

;kick

Required Permissions: Kick Members

Full Syntax:

;kick @user [reason]

Description:

Removes a member from the server temporarily. The user can rejoin with a valid invite link. Ideal for rule violations that don't require permanent removal.

Parameters:

  • @user: The member to kick (mention or ID)
  • [reason]: Optional reason for the kick (visible in audit logs)

Example Usage:

;kick @Spammer Flooding general chat
;kick @Troll Repeated off-topic posts

Required Permissions:

  • Bot needs Kick Members permission
  • Bot's highest role must be above the target user's highest role

Notes:

  • Kicked users can rejoin with an invite
  • Always provide a clear reason for transparency
  • Use ;ban for more severe cases
  • Action is logged in server audit logs

;ban

Required Permissions: Ban Members

Full Syntax:

;ban @user [reason]

Description:

Permanently removes a user from the server. This action should be reserved for serious violations like harassment, scams, or malicious behavior.

Parameters:

  • @user: The member to ban (mention or ID)
  • [reason]: Optional reason for the ban (visible in audit logs)

Example Usage:

;ban @Scammer Attempted phishing
;ban @Hacker Exploiting server vulnerabilities

Required Permissions:

  • Bot needs Ban Members permission
  • Bot's highest role must be above the target user's highest role

Notes:

  • Banned users cannot rejoin unless unbanned
  • Always document the reason in your moderation logs
  • Bans can be reversed with ;unban UserID
  • Consider temporary mutes/kicks for less severe cases
  • Action is logged in server audit logs

;mute

Required Permissions: Moderate Members

Full Syntax:

;mute @user [duration] [reason]

Description:

Temporarily restricts a user's ability to send messages. Useful for de-escalating conflicts or preventing spam during heated discussions.

Parameters:

  • @user: The member to mute (mention or ID)
  • [duration]: Mute length (e.g., 30m, 2h, 1d)
  • [reason]: Optional reason for the mute

Example Usage:

;mute @NoisyUser 30m Excessive caps usage
;mute @Flamer 2h Personal attacks in #general

Required Permissions:

  • Bot needs Moderate Members permission
  • Bot's highest role must be above the target user's highest role

Notes:

  • Duration defaults to 1 hour if not specified
  • Maximum mute duration is 28 days
  • Combine with a private message explaining the mute
  • Use ;unmute @user to remove restrictions early
  • Action is logged in server audit logs

;warn

Required Permissions: Kick Members

Full Syntax:

;warn @user [reason]

Description:

Issues a formal warning that's tracked in the user's record. Warnings help document patterns of behavior and can trigger automatic actions at certain thresholds.

Parameters:

  • @user: The member to warn (mention or ID)
  • [reason]: Detailed explanation of the violation

Example Usage:

;warn @NewUser Minor language violation
;warn @Roleplayer NSFW content in SFW channels

Required Permissions:

  • Bot needs Kick Members permission
  • Bot's highest role must be above the target user's highest role

Notes:

  • Warnings are permanently stored until manually cleared
  • View warning history with ;warnings @user
  • Manage warnings using ;delwarn or ;clearwarns
  • Consider setting up automatic actions for repeated warnings
  • Always include specific details in the reason

;purge

Required Permissions: Manage Messages

Full Syntax:

;purge [amount]

Description:

Bulk deletes messages from a channel. Perfect for cleaning up spam, off-topic discussions, or bot command clutter.

Parameters:

  • [amount]: Number of messages to delete (1-100)

Example Usage:

;purge 20
;purge 100

Required Permissions:

  • Bot needs Manage Messages permission
  • Must be used in a text channel

Notes:

  • Can only delete messages up to 14 days old
  • For complete channel cleanup, use ;nuke
  • Doesn't work on pinned messages
  • Action is logged in server audit logs

Utility Commands

;remindme

No permissions required

Full Syntax:

;remindme [time] [message]

Description:

Sets personalized reminders that ping you after a specified time. Works in both DMs and servers.

Parameters:

  • [time]: Duration (e.g., 30m, 2h, 1d)
  • [message]: Reminder content

Example Usage:

;remindme 2h Check the laundry
;remindme 30m Meeting starts soon

Required Permissions:

  • None - works for all users

Notes:

  • Supports minutes (m), hours (h), and days (d)
  • Maximum reminder duration: 1 year
  • Reminder pings you in the channel/DM where it was set
  • Use ;rmdm for DM-only reminders

;poll

No permissions required

Full Syntax:

;poll "Question" "Option1" "Option2" ...

Description:

Creates a simple poll with up to 10 options. Users can vote by reacting to the message.

Parameters:

  • "Question": The poll question (e.g., "Best programming language?").
  • "Option1", "Option2", etc.: The choices for the poll (minimum 2).

Example Usage:

;poll "Favorite Color?" "Red" "Blue" "Green"

Notes:

  • Supports up to 10 options.
  • Results are visible in real-time via reactions.

;avatar

No permissions required

Full Syntax:

;avatar [@user]

Description:

Displays the avatar (profile picture) of a user in high resolution. If no user is specified, shows the avatar of the command executor.

Parameters:

  • [@user]: Optional user mention or ID (e.g., @User or 123456789012345678).

Example Usage:

;avatar @User
;avatar (shows your avatar)

Notes:

  • Supports animated avatars (GIFs).
  • Click the image to view it in full size.

;unban

Required Permissions: Ban Members

Full Syntax:

;unban UserID [reason]

Description:

Reverses a permanent ban, allowing the user to rejoin the server. Essential for correcting mistakes or welcoming reformed community members.

Parameters:

  • UserID: The Discord ID of the banned user (not username).
  • [reason]: Optional explanation for the unban (visible in audit logs).

Example Usage:

;unban 123456789012345678 Mistaken identity
;unban 987654321098765432 After appeal review

Required Permissions:

  • Bot needs Ban Members permission.

Notes:

  • Find user IDs in your server's ban list or audit logs.
  • Always document the reason for transparency.
  • Consider sending a welcome message to the returning user.

;unmute

Required Permissions: Moderate Members

Full Syntax:

;unmute @user [reason]

Description:

Removes message restrictions from a muted user before their timeout expires. Use when a user demonstrates improved behavior.

Parameters:

  • @user: The member to unmute (mention or ID).
  • [reason]: Optional explanation for the unmute.

Example Usage:

;unmute @NoisyUser Apology accepted
;unmute @Flamer Mediation successful

Required Permissions:

  • Bot needs Moderate Members permission.

Notes:

  • Consider sending a DM explaining why the mute was lifted.
  • Use ;mute to reapply restrictions if needed.

;warnings

Required Permissions: Kick Members

Full Syntax:

;warnings @user

Description:

Displays all active warnings for a member, including dates and reasons. Essential for tracking behavior patterns.

Parameters:

  • @user: The member to check (mention or ID).

Example Usage:

;warnings @RuleBreaker
;warnings 123456789012345678

Required Permissions:

  • Bot needs Kick Members permission.

Notes:

  • Warnings are stored until manually cleared.
  • Use ;clearwarns to reset a user's warning count.

;clearwarns

Required Permissions: Kick Members

Full Syntax:

;clearwarns @user

Description:

Resets all warnings for a member, effectively giving them a clean slate. Useful for reformed users or administrative corrections.

Parameters:

  • @user: The member to clear warnings for (mention or ID).

Example Usage:

;clearwarns @ReformedUser
;clearwarns 123456789012345678

Required Permissions:

  • Bot needs Kick Members permission.

Notes:

  • This action cannot be undone.
  • Consider documenting the reason for clearing warnings in your moderation logs.

;delwarn

Required Permissions: Kick Members

Full Syntax:

;delwarn @user [warningID]

Description:

Removes a specific warning from a user's record. Use to correct errors or outdated warnings.

Parameters:

  • @user: The member to remove a warning from (mention or ID).
  • [warningID]: The ID of the warning to delete (found in ;warnings output).

Example Usage:

;delwarn @User 3
;delwarn 123456789012345678 5

Required Permissions:

  • Bot needs Kick Members permission.

Notes:

  • Warning IDs are sequential and unique per user.
  • Use ;warnings @user to find the correct ID.

;nuke

Required Permissions: Manage Channels

Full Syntax:

;nuke

Description:

Completely resets a channel by deleting all messages and creating a clean slate. Automatically creates a backup of deleted content for moderation review.

Parameters:

  • None - operates on the current channel.

Example Usage:

;nuke (after major spam attack)
;nuke (to reset off-topic discussions)

Required Permissions:

  • Bot needs Manage Channels permission.

Notes:

  • This action is irreversible.
  • Consider using ;purge for partial cleanups.

;lock

Required Permissions: Manage Channels

Full Syntax:

;lock [reason]

Description:

Temporarily prevents all users from sending messages in a channel. Ideal for emergency situations or scheduled maintenance.

Parameters:

  • [reason]: Optional explanation for the lock (visible in channel).

Example Usage:

;lock Server maintenance in progress
;lock Pausing discussion during investigation

Required Permissions:

  • Bot needs Manage Channels permission.

Notes:

  • Always pair with an explanatory pinned message.
  • Use ;unlock to restore access.

;unlock

Required Permissions: Manage Channels

Full Syntax:

;unlock

Description:

Restores message permissions in a previously locked channel.

Parameters:

  • None - operates on the current channel.

Example Usage:

;unlock (after maintenance is complete)

Required Permissions:

  • Bot needs Manage Channels permission.

Notes:

  • Consider announcing the unlock to users.

;slowmode

Required Permissions: Manage Channels

Full Syntax:

;slowmode [seconds]

Description:

Controls how frequently users can send messages in a channel. Helps prevent spam during active events or discussions.

Parameters:

  • [seconds]: Delay between messages (0-21600, where 0 disables slowmode).

Example Usage:

;slowmode 5 (for active Q&A)
;slowmode 30 (for event channels)
;slowmode 0 (to disable)

Required Permissions:

  • Bot needs Manage Channels permission.

Notes:

  • Combine with ;lock for complete conversation control during crises.

;fg

Required Permissions: Ban Members

Full Syntax:

;fg @user

Description:

Simulates a ban with a dramatic fake kick message. Designed for harmless pranks with trusted community members.

Parameters:

  • @user: The member to prank (mention or ID).

Example Usage:

;fg @BestFriend (April Fools' joke)
;fg @RegularUser (with prior consent)

Required Permissions:

  • Bot needs Ban Members permission.

Notes:

  • Never use this command during actual moderation actions - it undermines trust.

;nick

Required Permissions: Manage Nicknames

Full Syntax:

;nick @user [newNickname]

Description:

Modifies a user's server-specific nickname. Useful for enforcing naming conventions or playful community events.

Parameters:

  • @user: The member to rename (mention or ID).
  • [newNickname]: The new nickname (leave empty to reset).

Example Usage:

;nick @User123 ProperName (enforcing rules)
;nick @Streamer [LIVE] StreamerName (event tagging)

Required Permissions:

  • Bot needs Manage Nicknames permission.

Notes:

  • Always respect identity - avoid forced nicknames that might offend.
  • Nicknames are server-specific and don't affect global usernames.

;case

Required Permissions: Kick Members

Full Syntax:

;case [caseID]

Description:

Displays detailed information about a specific moderation action from your server's logs. Essential for reviewing past incidents and maintaining transparency.

Parameters:

  • [caseID]: The unique identifier of the moderation case.

Example Usage:

;case 42 (view standard moderation case)
;case DM-15 (view DM-related incident)

Required Permissions:

  • Bot needs Kick Members permission.

Notes:

  • Case IDs are automatically generated and can be found in audit logs or warning messages.
  • Use ;editcase to update details.

;editcase

Required Permissions: Kick Members

Full Syntax:

;editcase [caseID] [newReason]

Description:

Modifies the details of an existing moderation record. Use to correct errors or add additional context to past actions.

Parameters:

  • [caseID]: The unique identifier of the case to edit.
  • [newReason]: Updated explanation for the moderation action.

Example Usage:

;editcase 42 Updated evidence link
;editcase DM-15 Added user apology transcript

Required Permissions:

  • Bot needs Kick Members permission.

Notes:

  • All edits are logged with the moderator's name and timestamp.
  • Avoid changing the original reason without documentation.

;afk

No permissions required

Full Syntax:

;afk [reason]

Description:

Sets your status as AFK (Away From Keyboard) with an optional reason. Automatically removes when you send a message.

Parameters:

  • [reason]: Optional explanation for your absence.

Example Usage:

;afk Taking a break
;afk Sleeping

Required Permissions:

  • None - works for all users.

Notes:

  • AFK status is server-specific.
  • Others will see your AFK status when mentioning you.

;snipe

No permissions required

Full Syntax:

;snipe

Description:

Displays the most recently deleted message in the current channel. Useful for moderation and tracking deleted content.

Parameters:

  • None - operates in the current channel.

Example Usage:

;snipe (after a message is deleted)

Required Permissions:

  • None - works for all users.

Notes:

  • Only works for messages deleted within the last 5 minutes.
  • Does not show messages deleted by bots or users with admin permissions.

;invite

No permissions required

Full Syntax:

;invite

Description:

Generates a permanent invite link to your server with default permissions.

Parameters:

  • None - generates a standard invite.

Example Usage:

;invite (to share your server)

Required Permissions:

  • None - works for all users.

Notes:

  • Admins can create custom invite links with specific permissions in Discord settings.
  • Invite links can be revoked in server settings.

;embed

Required Permissions: Manage Messages

Full Syntax:

;embed "Title" | "Description" | #HEXColor | [imageURL] | [channel]

Description:

Creates rich embedded messages with custom titles, descriptions, colors and images.

Parameters:

  • "Title": The embed's header text.
  • "Description": The main content of the embed.
  • #HEXColor: The sidebar color (e.g., #FF0000 for red).
  • [imageURL]: Optional image to include in the embed.
  • [channel]: Optional channel to send the embed to.

Example Usage:

;embed "Rules" | "1. Be respectful" | #FF0000 | #announcements

Required Permissions:

  • Bot needs Manage Messages permission.

Notes:

  • Use the pipe character (|) to separate parameters.
  • Image URLs must be direct links to image files.

;vote

No permissions required

Full Syntax:

;vote [question]

Description:

Creates a simple yes/no poll with reactions for quick community feedback.

Parameters:

  • [question]: The poll question to ask.

Example Usage:

;vote Should we add more game channels?

Required Permissions:

  • None - works for all users.

Notes:

  • For multiple-choice polls, use ;poll instead.
  • Results are visible to everyone in the channel.

;lastfm

No permissions required

Full Syntax:

;lastfm [username]

Description:

Displays music statistics from Last.fm including recent tracks and top artists.

Parameters:

  • [username]: Optional Last.fm username (uses linked account if omitted).

Example Usage:

;lastfm DJOrmi
;lastfm (for linked accounts)

Required Permissions:

  • None - works for all users.

Notes:

  • Users must link their Last.fm account first with ;lastfm set [username].
  • Shows listening history and musical preferences.

;rmdm

No permissions required

Full Syntax:

;rmdm [time] [message]

Description:

Sets a reminder that will be sent to you via DM after the specified time.

Parameters:

  • [time]: Duration until reminder (e.g., 30m, 2h, 1d).
  • [message]: The reminder content.

Example Usage:

;rmdm 2h Check the oven
;rmdm 30m Take medication

Required Permissions:

  • None - works for all users.

Notes:

  • Supports minutes (m), hours (h), and days (d).
  • Maximum reminder duration: 1 year.

;ascii

No permissions required

Full Syntax:

;ascii [text]

Description:

Converts text to stylized ASCII art for decorative messages.

Parameters:

  • [text]: The text to convert (max 20 characters).

Example Usage:

;ascii Hello

Required Permissions:

  • None - works for all users.

Notes:

  • Best results with short words or initials.
  • Supports A-Z, 0-9, and basic punctuation.

;color

No permissions required

Full Syntax:

;color [HEX/name]

Description:

Displays a visual sample of a color from its HEX code or name.

Parameters:

  • [HEX/name]: Color in HEX format (e.g., #FF5733) or CSS color name (e.g., "royalblue").

Example Usage:

;color #FF5733
;color royalblue

Required Permissions:

  • None - works for all users.

Notes:

  • Supports all standard CSS color names.
  • HEX codes must include the # symbol.

Configuration Commands

;prefix

Required Permissions: Administrator

Full Syntax:

;prefix [new_prefix]

Description:

Changes the bot's command prefix for this server. The prefix must be 1-3 characters long.

Parameters:

  • [new_prefix]: The new prefix to use (e.g., !, ?, $).

Example Usage:

;prefix !
;prefix ?

Required Permissions:

  • Bot needs Administrator permission.

Notes:

  • Prefix changes don't affect the ;help command's prefix.
  • Reset to default with ;prefix ;

;slc

Required Permissions: Administrator

Full Syntax:

;slc #channel

Description:

Sets the channel where moderation logs will be recorded. Essential for server administration.

Parameters:

  • #channel: The text channel for logs (mention required).

Example Usage:

;slc #mod-logs

Required Permissions:

  • Bot needs Administrator permission.

Notes:

  • Logs include kicks, bans, mutes, and warnings.
  • Disable with ;slc disable

;sdlc

Required Permissions: Administrator

Full Syntax:

;sdlc #channel

Description:

Configures where deleted message logs will be archived. Helps track rule violations.

Parameters:

  • #channel: The text channel for deleted message logs.

Example Usage:

;sdlc #deleted-logs

Required Permissions:

  • Bot needs Administrator permission.

Notes:

  • Requires Manage Messages permission to track deletions.
  • Disable with ;sdlc disable

;swc

Required Permissions: Administrator

Full Syntax:

;swc #channel

Description:

Designates the channel where welcome messages will be posted for new members.

Parameters:

  • #channel: The text channel for welcome messages (mention required).

Example Usage:

;swc #welcome

Required Permissions:

  • Bot needs Administrator permission.

Notes:

  • Combine with ;swm to customize the welcome message.
  • Disable with ;swc disable

;swm

Required Permissions: Administrator

Full Syntax:

;swm [message]

Description:

Customizes the welcome message template. Supports variables like {user} and {server}.

Parameters:

  • [message]: The welcome message template.

Example Usage:

;swm Welcome {user} to {server}!
;swm Enjoy your stay, {user}! Read rules in #rules

Required Permissions:

  • Bot needs Send Messages permission.

Notes:

  • Available variables: {user}, {server}, {memberCount}
  • Reset to default with ;swm reset

;say

Required Permissions: Administrator

Full Syntax:

;say [message]

Description:

Makes the bot send a message as if it wrote it. Supports embeds and formatting.

Parameters:

  • [message]: The content to send (supports Markdown).

Example Usage:

;say Hello everyone!
;say **Announcement:** Server maintenance tonight

Required Permissions:

  • Bot needs Administrator permission.

Notes:

  • Use responsibly - all messages are logged with the executor's name.
  • For embeds, use ;embed instead.

;autorole

Required Permissions: Administrator

Full Syntax:

;autorole @role

Description:

Sets a role to be automatically assigned to new members. The bot must have Manage Roles permission.

Parameters:

  • @role: The role to automatically assign (mention or ID).

Example Usage:

;autorole @Member
;autorole 123456789012345678 (using role ID)

Required Permissions:

  • Bot needs Administrator and Manage Roles permissions.

Notes:

  • The bot's role must be higher than the target role in the hierarchy.
  • Disable with ;autorole disable

Role Management Commands

;addrole

Required Permissions: Manage Roles

Adds a specified role to a user. The bot's highest role must be above the target role.

Usage:

;addrole @user @role

Examples:

;addrole @User @VIP
;addrole 123456789012345678 987654321098765432 (using IDs)

;rmrole

Required Permissions: Manage Roles

Removes a specified role from a user. Cannot remove roles higher than bot's highest role.

Usage:

;rmrole @user @role

Examples:

;rmrole @User @Muted
;rmrole 123456789012345678 987654321098765432 (using IDs)

;createrole

Required Permissions: Manage Roles

Creates a new role with optional color (hex format). The new role will be at the bottom of hierarchy.

Usage:

;createrole "Role Name" [#color]

Examples:

;createrole "VIP"
;createrole "Moderator" #FF0000

;delrole

Required Permissions: Manage Roles

Permanently deletes a role from the server. This action cannot be undone.

Usage:

;delrole @role

Examples:

;delrole @OldRole
;delrole 123456789012345678 (using role ID)

Warning:

All role permissions and assignments will be permanently lost.

;editrole

Required Permissions: Manage Roles

Modifies role properties including name, color, and icon. At least one parameter must be specified.

Usage:

;editrole @role "New Name" [#color] [iconURL]

Examples:

;editrole @Role "Updated Name"
;editrole @Role "" #00FF00 (changes only color)
;editrole @Role "" "" https://example.com/icon.png (changes only icon)

;rr

Required Permissions: Manage Roles

Full Syntax:

;rr "Title" "Description" @role1 :emoji1: @role2 :emoji2: ...

Description:

Creates a reaction role panel where users can self-assign roles by clicking reactions. Perfect for interest groups, notifications, or channel access management.

Parameters:

  • "Title": Panel header (e.g., "Get Roles").
  • "Description": Brief explanation of the roles (e.g., "React to gain access").
  • @role: Role to be assigned when reacted.
  • :emoji:: Emoji associated with the role (e.g., :game_die: for @Gamers).

Example Usage:

;rr "Channel Access" "Select your interests:" @Gamers :game_die: @Music :musical_note: @Movies :film_frames:

Required Permissions:

  • Bot needs Manage Roles and Manage Messages permissions.
  • Bot's role must be higher in hierarchy than assigned roles.

Notes:

  • Panel can be manually edited/deleted. (so normal moderator/administrator or owner can't do this)
  • Users can remove reactions to lose roles.
  • Emojis must be available on the server (standard Discord or custom server emojis).

;giveaway

Requires: Administrator

Full Syntax:

;giveaway <duration> <prize>

Description:

Starts a new giveaway.

Parameters:

  • <duration>: The duration of the giveaway (e.g., 1d, 2h).
  • <prize>: The prize for the giveaway.

Example Usage:

;giveaway 1d Discord Nitro

Notes:

  • Only administrators can use this command.

;endgiveaway

Requires: Administrator

Full Syntax:

;endgiveaway <giveaway-id>

Description:

Ends a giveaway early and selects a winner.

Parameters:

  • <giveaway-id>: The ID of the giveaway to end.

Example Usage:

;endgiveaway 123456789

Notes:

  • Only administrators can use this command.

;greroll

Requires: Administrator

Full Syntax:

;greroll <giveaway-id>

Description:

Rerolls the winner of a giveaway.

Parameters:

  • <giveaway-id>: The ID of the giveaway to reroll.

Example Usage:

;greroll 123456789

Notes:

  • Only administrators can use this command.

Ticket Commands

;st

Requires: Administrator

Full Syntax:

;st <channel>

Description:

Sets the channel where tickets will be created.

Parameters:

  • <channel>: The channel to set for ticket creation (mention or ID).

Example Usage:

;st #create-ticket

Notes:

  • Only administrators can use this command.

;addstaff

Requires: Administrator

Full Syntax:

;addstaff <user>

Description:

Adds a user to the ticket support team.

Parameters:

  • <user>: The user to add (mention or ID).

Example Usage:

;addstaff @Helper

Notes:

  • Only administrators can use this command.

;rmstaff

Requires: Administrator

Full Syntax:

;rmstaff <user>

Description:

Removes a user from the ticket support team.

Parameters:

  • <user>: The user to remove (mention or ID).

Example Usage:

;rmstaff @Helper

Notes:

  • Only administrators can use this command.

;tlog

Requires: Send Messages

Full Syntax:

;tlog <channel>

Description:

Sets the channel where ticket logs will be recorded.

Parameters:

  • <channel>: The channel to set for ticket logs (mention or ID).

Example Usage:

;tlog #ticket-logs

Notes:

  • Only administrators can use this command.

;serverinfo

No permissions required

Full Syntax:

;serverinfo

Description:

Displays detailed information about the server, including member count, creation date, and roles.

Parameters:

  • None - operates in the current server.

Example Usage:

;serverinfo

Notes:

  • Includes statistics like channels, boosts, and emojis.
  • Embed is updated in real-time.

;ping

No permissions required

Full Syntax:

;ping

Description:

Checks the bot's latency and response time. Useful for testing if the bot is online.

Parameters:

  • None - returns the bot's ping in milliseconds.

Example Usage:

;ping

Notes:

  • Latency under 100ms is excellent.
  • Includes API and websocket ping.

Information Commands

;userinfo

No permissions required

Full Syntax:

;userinfo [member]

Description:

Displays detailed information about a user including join date, roles, and status.

Parameters:

  • [member]: Optional user mention or ID (defaults to command user)

Example Usage:

;userinfo @User

;serverinfo

No permissions required

Full Syntax:

;serverinfo

Description:

Displays server statistics including member count, channels, and creation date.

Example Usage:

;serverinfo

;avatar

No permissions required

Full Syntax:

;avatar [member]

Description:

Shows high-resolution user avatar with download option.

Parameters:

  • [member]: Optional user mention or ID

Example Usage:

;avatar @User

;roleinfo

No permissions required

Full Syntax:

;roleinfo <role>

Description:

Displays role information including permissions, color, and member count.

Parameters:

  • <role>: Role mention or name

Example Usage:

;roleinfo @Moderator

;ping

No permissions required

Full Syntax:

;ping

Description:

Shows bot latency and API response times.

Example Usage:

;ping

;emojiinfo

No permissions required

Full Syntax:

;emojiinfo :emoji:

Description:

Displays emoji metadata including ID, creation date, and uploader.

Parameters:

  • :emoji:: Server emoji (must be from current server)

Example Usage:

;emojiinfo :pepe:

;uptime

No permissions required

Full Syntax:

;uptime

Description:

Shows how long the bot has been continuously online.

Example Usage:

;uptime

;recentjoins

No permissions required

Full Syntax:

;recentjoins [limit]

Description:

Lists most recently joined members (default: last 10).

Parameters:

  • [limit]: Optional number of members to show (1-25)

Example Usage:

;recentjoins 5

;hierarchy

No permissions required

Full Syntax:

;hierarchy

Description:

Displays server role hierarchy with permission highlights.

Example Usage:

;hierarchy