Reply to a message with this phrase to generate a styled quote image preserving the original author and message.

• How It Works
  Reply to any message and send @auralis quote this The bot will generate an image containing the quoted message and author.


• Message Requirements
  The quoted message must:
  • Contain text (empty messages are rejected)
  • Not include links http:// or https://
  • Be 200 characters or fewer


• Formatting Rules
  The following formatting is automatically cleaned:
  • Markdown (bold, underline, strikethrough)
  • User mentions are converted to display names
  • Emojis (Unicode and custom) are fully supported


• Image Layout
  The generated quote image includes:
  • The original author’s avatar
  • The quoted message, wrapped to fit the image
  • The author’s display name and username
  • A subtle watermark crediting Auralis


• Overflow Protection
  Text is wrapped and clipped to ensure it always fits within the quote image without breaking layout.


• Output
  The result is sent as a PNG image directly in the channel as a reply.

Displays a user's avatar in full resolution, including server-specific avatars when available.

• Usage
  /avatar — Displays your own avatar.
  /avatar <user> — Displays the selected user’s avatar.


• Avatar Sources
  The command supports multiple avatar types:
  • Server-specific avatar (if the user has one)
  • Global avatar (Discord profile avatar)
  • Default avatar (fallback if no custom avatar exists)


• Display Behavior
  If a server-specific avatar exists, it is shown as a thumbnail while the global avatar is displayed in full resolution.


• Module Control
  This command can be enabled or disabled via the dashboard. If disabled, users will be notified with an error message.


• Output
  The avatar is displayed in an embed with the user’s display name as the title.

Displays a user's profile banner or their accent color if no banner is set.

• Usage
  /banner — Displays your own banner.
  /banner <user> — Displays the selected user’s banner.


• Banner Priority
  The command follows this priority order:
  • Profile banner image (if available)
  • Accent color image (generated dynamically)
  • Error message if neither exists


• Accent Color Handling
  If the user has no banner but does have an accent color:
  • A solid-color image is generated dynamically
  • The color’s hex value is displayed in the embed description


• Module Control
  This command can be toggled on or off through the dashboard. If disabled, an error message is shown explaining how to re-enable it.


• Output
  The banner or generated color image is sent as an embed image attachment.

Displays detailed information about the current server, including statistics, moderation data, and roles.

• Module Requirement
  This command requires the Server Information module to be enabled via the dashboard. If disabled, an error message with a dashboard link is shown.


• Displayed Information
  The main embed includes:
  • Server name and icon
  • Server owner ID
  • Total number of channels
  • Total number of categories
  • Boost level and boost count
  • Number of members currently timed out
  • Total ban count (if permissions allow)


• Permission Handling
  If the bot lacks permission to view bans, the ban count is skipped silently without error.


• Server Icon Fallback
  If the server has no icon:
  • A placeholder image is dynamically generated using the server name
  • The generated image is attached and used as the embed thumbnail


• Roles Overview
  A Show Roles button is included below the embed.
  • Displays all roles except @everyone
  • Roles are sorted by hierarchy (highest first)
  • Roles are paginated in groups of 10
  • Role list is shown as an ephemeral message


• Footer Information
  The server ID is displayed in the embed footer.

Generates a visual profile card image for a user, displaying their avatar, banner, and current activity.

• Usage
  /profile — Displays your own profile.
  /profile <user> — Displays the selected user’s profile.


• Module Requirement
  This command requires the Profile module to be enabled via the dashboard. If disabled, an error message with a dashboard link is shown.


• Profile Image Contents
  The generated profile image includes:
  • User avatar (displayed in a circular frame)
  • User display name and username
  • Profile banner or accent color background
  • A dedicated activity display panel


• Banner Handling
  The banner background follows this priority:
  • User profile banner image (if available)
  • Dynamically generated image using the user’s accent color
  • Neutral fallback color if neither is available


• Activity Detection
  The activity panel displays one of the following states:
  • Spotify Listening — Song title, artist, and album artwork
  • Game Activity — Game name, icon, and elapsed playtime
  • Idle — Displays a placeholder message when no activity is detected


• Activity Priority
  If multiple activities are present:
  • Spotify listening takes priority over game activity
  • Only one activity is shown at a time


• Output
  The profile card is generated as a PNG image and sent directly in the channel.

Displays a visual rank card showing a user’s level, XP progress, and server rank.

• Usage
  /rank — Displays your own rank.
  /rank <user> — Displays the selected user’s rank.


• Module Requirement
  This command requires the Leveling module to be enabled via the dashboard. If disabled, an error message with a dashboard link is shown.


• Displayed Information
  The generated rank card includes:
  • User display name and avatar
  • Current server level
  • Server rank position
  • Total XP and XP required for the next level
  • A visual progress bar representing level progress


• Card Styling
  The background follows this priority:
  • User profile banner (if available)
  • Generated background using the user’s accent color
  • Dark fallback background if neither exists


• Status Indicator
  The user’s current Discord status (online, idle, dnd, offline) is displayed as an icon on the rank card.


• XP Progress Calculation
  XP required for the next level increases non-linearly based on the current level.


• Output
  The rank card is generated as a PNG image and sent directly in the channel.

Displays the server-wide top-10 leaderboard ranked by total XP.

• Module Requirement
  This command requires the Leveling module to be enabled via the dashboard. If disabled, an error message with a dashboard link is shown.


• Ranking Criteria
  Users are ranked by their total accumulated XP in the current server.


• Leaderboard Composition
  The leaderboard displays:
  • The top 10 users by XP
  • User display name and avatar
  • Current level and total XP


• Fallback Handling
  If fewer than 10 eligible users exist:
  • Remaining slots are filled with random server members
  • Fallback users display level 0 and 0 XP


• Card Generation
  The leaderboard is generated as a single image containing:
  • One row per ranked user
  • Banner or accent-color background per user
  • Rank number, avatar, level, and XP


• Output
  The leaderboard is sent as a PNG image directly in the channel.

Set a custom AFK status and automatically notify users who mention you while you are away.

• Usage
  /afk set <status> — Sets a custom AFK status message.


• Module Requirement
  This command requires the AFK module to be enabled via the dashboard. If disabled, an error message with a dashboard link is shown.


• AFK Activation
  When the command is used:
  • Your AFK status and timestamp are saved in the database
  • You are marked as AFK until you send a message
  • Only one AFK status can exist at a time


• Mention Notifications
  If another user mentions you while AFK:
  • The bot replies with an AFK embed
  • The embed shows how long you have been AFK <t:...>
  • Your custom AFK status message is displayed


• Automatic AFK Removal
  Your AFK status is automatically removed when:
  • You send a message in the server
  • The message does not start with a hyphen "-"


• AFK Removal Feedback
  When your AFK is removed:
  • A confirmation embed is sent as a reply
  • The message auto-deletes after 10 seconds


• Restrictions
  
  • Bot messages are ignored
  • AFK checks only run in servers (not DMs)
  • Messages starting with "-" do not clear AFK

Display the most recently deleted message in the server.

• How It Works
  Whenever a message is deleted, the bot stores the message data in the database. The /snipe command retrieves the latest deleted message for the server.


• Stored Information
  For each deleted message, the following data is saved:
  • Author username
  • Author avatar (if available)
  • Message content
  • Original creation timestamp
  • Attachment URLs (if present)


• Single-Message Limit
  Only one deleted message per server is stored. Each new deleted message overwrites the previous one.


• Bot Message Handling
  Messages sent by bots are ignored and are never stored or retrievable using this command.


• Attachments
  If the deleted message contained attachments:
  • The attachment URLs are displayed in a separate embed field
  • Multiple attachments are shown as a newline-separated list


• Empty State
  If no deleted message exists for the server, the bot responds with an error message stating that there is nothing to snipe.


• Output
  The sniped message is displayed in an embed with:
  • The original author’s name and avatar
  • The original message content
  • Any associated attachment URLs

Displays the current state of the counting game, including the last valid number and last counting user.

• Availability
  This command can be used in any channel.


• Configuration Check
  If no counting channel has been set up, the bot will notify that the counting game is not yet configured.


• Displayed Information
  The status embed includes:
  • The current valid number in the counting sequence
  • The user who last counted correctly


• Formatting
  The current number is displayed in a monospace format to improve readability.


• Fallback Handling
  If no valid user has counted yet, the last user field displays None.

Set a channel as the official counting game channel and enable advanced number validation.

• Usage
  /setcounting <channel> — Select the channel where counting should take place.


• Permission Requirement
  You must have the Manage Channels permission to use this command.


• Channel Configuration
  When a channel is set:
  • The selected channel becomes the only valid counting channel
  • The current counting progress is reset
  • The last counted number is set back to 0
  • The last counting user is cleared


• Number Validation
  Messages sent in the counting channel are evaluated using a safe mathematical parser:
  • Allowed operators: +, -, *, //, %, **
  • Parentheses and unary minus (-5) are supported
  • All expressions are evaluated as integers


• Supported Number Formats
  
  • Decimal: 1, 42
  • Hexadecimal: A, FF, 10, 0xFF
  • Binary: 0b1010
  • Octal: 0o77


• Mathematical Functions
  
  • sqrt(x) — square root
  • pow(x, y) or x ** y — exponentiation
  • abs(x)
  • round(x)
  • floor(x), ceil(x)
  • min(a, b), max(a, b)


• Trigonometry & Constants
  
  • Functions: sin(), cos(), tan()
  • Constants: pi, e
  • Example: sin(pi / 2) → 1


• Counting Rules
  
  • Each number must increase by exactly 1
  • The same user may not count twice in a row
  • Incorrect numbers reset the count back to 1


• Feedback
  
  • Correct numbers receive a ✅ reaction
  • Incorrect counts trigger a warning embed and reset the game

Claim your daily Lumina reward.
Resets daily at 00:00 GMT.

• Reward
  Lumina received: 200–400 Lumina

Displays the Lumina balance overview for yourself or another user.

• Usage
  /balance — Shows your own balance.
  /balance <user> — Shows the selected user's balance.


• Displayed Values
  The balance overview is split into three categories:
  • 💰 Wallet: Spendable Lumina, used for economy and robbery actions.
  • 🔒 Bank: Stored Lumina that is safe from robberies.
  • 🪙 Casino: Chips used for gambling and casino games.


• Security
  Lumina stored in the bank cannot be stolen using robbery-related commands.


• Embed Information
  The embed author dynamically displays the selected user's name and avatar when a target user is provided.

Displays all items currently stored in your inventory.

• Contents
  Shows every item you currently own, including their name, rarity, and value.


• Empty Inventory
  If your inventory is empty, a warning embed is shown indicating that no items are stored.


• Interactive View
  When items are present, the inventory is displayed using an interactive menu.
  • Allows browsing through all items
  • Supports pagination for large inventories
  • Updates dynamically without re-running the command


• Scope
  This command only displays your own inventory. Viewing other users’ inventories is not supported.

Sell an item from your inventory in exchange for Lumina.

• Usage
  /sell <item number>
  Items are referenced using a 1-based index as shown in your inventory list.


• Item Validation
  If the selected item number does not exist in your inventory, the action is cancelled and an error message is shown.


• Sell Price
  Items are sold for 60% of their original Lumina value.


• Inventory Update
  The sold item is permanently removed from your inventory once the transaction is completed.


• Result
  After selling an item:
  • The calculated Lumina is added to your wallet
  • Your updated balance is displayed
  • The sold item’s name and rarity are shown in the confirmation embed

Explore a random zone to find either Lumina or an item.
Usable once every 30 minutes.

• Zones
  A random zone is selected on each use:
  • Forest
  • Ruins
  • Volcano
  • Sea Caves


• Direct Lumina Find
  Chance: 15%
  Reward: 50–250 Lumina
  Replaces item rewards when triggered.


• Item Find (85%)
  If Lumina is not found, an item is awarded based on zone-specific rarity chances.


• Item Rarity Chances per Zone
  
  • Forest: ⭐ 60% • ⭐⭐ 30% • ⭐⭐⭐ 10%
  • Ruins: ⭐⭐ 50% • ⭐⭐⭐ 30% • ⭐⭐⭐⭐ 15% • ⭐⭐⭐⭐⭐ 5%
  • Volcano: ⭐⭐⭐ 50% • ⭐⭐⭐⭐ 35% • ⭐⭐⭐⭐⭐ 15%
  • Sea Caves: ⭐⭐ 55% • ⭐⭐⭐ 30% • ⭐⭐⭐⭐ 10% • ⭐⭐⭐⭐⭐ 5%


• Item Rewards
  Items are added to your inventory and have a Lumina value:
  • ⭐ Common: 20–60 Lumina
  • ⭐⭐ Uncommon: 120–180 Lumina
  • ⭐⭐⭐ Rare: 350–420 Lumina
  • ⭐⭐⭐⭐ Epic: 900–1100 Lumina
  • ⭐⭐⭐⭐⭐ Legendary: 2200–3500 Lumina

Open a crate for a chance to obtain rare or valuable items.
Cost: 150 Lumina

• Cost & Validation
  Opening a crate costs 150 Lumina.
  If your balance is too low, the crate cannot be opened and no Lumina is deducted.


• Crate Upgrade System
  Crates start at 1⭐ rarity and can upgrade up to 5⭐.
  • Up to 4 upgrade rolls are performed
  • Each roll has a 50% chance to increase the star level
  • Upgrading stops immediately on a failed roll


• Final Rarity
  The final star count determines the rarity tier of the item received.


• Item Reward
  One random item is selected from the final rarity tier and added to your inventory.
  • Item rarity ranges from ⭐ Common to ⭐⭐⭐⭐⭐ Legendary
  • Each item has a fixed Lumina value based on rarity


• Lumina Bonus
  In addition to the item, you receive a bonus equal to 20% of the item’s value, added directly to your wallet.


• Result Summary
  After opening a crate, the result embed displays:
  • The final crate rarity
  • The item name and rarity
  • The item’s Lumina value
  • The Lumina bonus received
  • Your updated balance

Combine two items together for a chance to create a higher-rarity item.

• Usage
  /craft <item1> <item2>
  Both items must be selected using their 1-based inventory index.


• Item Validation
  Crafting requires two different valid items from your inventory. Selecting the same item twice or an invalid index will cancel the action.


• Success Chance
  Crafting success is based on item rarity:
  • Base chance: 40%
  • +10% success chance per average rarity above ⭐
  • Maximum success chance capped at 90%


• Successful Craft
  On success:
  • Both original items are consumed
  • A new item is created with rarity = highest rarity + 1
  • Maximum possible rarity is ⭐⭐⭐⭐⭐ (5)
  • The new item is added to your inventory


• Failed Craft
  On failure:
  • Both items are permanently consumed
  • You receive a small Lumina salvage reward
  • Salvage reward ranges from 10–60 Lumina


• Result Display
  The result embed shows:
  • Crafting success or failure
  • The resulting item and rarity (on success)
  • Lumina salvage and updated balance (on failure)

Displays the Lumina value of a selected item from your inventory.

• Usage
  /worth <item number>
  The item number corresponds to its 1-based position in your inventory.


• Inventory Validation
  The command performs several checks before displaying a result:
  • If you do not yet have an inventory, the command stops
  • If your inventory is empty, a warning message is shown
  • If the item index is invalid, the request is rejected


• Displayed Information
  When a valid item is selected, the embed displays:
  • Item name
  • Lumina value of the item
  • Rarity, represented using star icons (⭐)


• Rarity & Styling
  The embed color is dynamically selected based on the item’s rarity tier.


• Scope
  This command can only be used to view the worth of your own items. Viewing other users’ inventories or items is not supported.

Earn Lumina by working.
Usable once every 60 minutes.

• Cooldown
  This command can be used once every 60 minutes per user.


• Reward
  Completing work grants a random Lumina payout:
  • Minimum reward: 75 Lumina
  • Maximum reward: 200 Lumina


• Process
  A short working animation is displayed before the reward is granted.


• Result
  After completion:
  • The earned Lumina amount is shown
  • Your updated balance is displayed

Attempt to rob another user by selecting a risk level. Higher risk increases potential rewards, but drastically lowers success chance and increases fines on failure.

• Low Risk
  Success chance: 85%
  Steal: 40–150 Lumina
  Fine on failure: 50–120 Lumina


• Normal Risk
  Success chance: 75%
  Steal: 80–350 Lumina
  Fine on failure: 100–300 Lumina


• High Risk
  Success chance: 30%
  Steal: 200–700 Lumina
  Fine on failure: 300–700 Lumina


• Ultra Risk
  Success chance: 10%
  Steal: 500–1500 Lumina
  Fine on failure: 800–2000 Lumina

Mine underground for Lumina crystals and other resources.
Usable once every 10 minutes.

• Cooldown
  This command can be used once every 10 minutes per user.


• Possible Outcomes
  Mining can result in one of the following outcomes:
  • 💎 Rare Lumina Crystal: Gain 300–600 Lumina
  • 🪨 Lumina Shards: Gain 50–150 Lumina
  • 💥 Pickaxe Failure: Lose 30–70 Lumina


• Risk Factor
  Mining is not always profitable — there is a chance to lose Lumina if the expedition fails.


• Process
  A short mining animation is shown before the outcome is revealed.


• Result
  The result embed displays:
  • The mining outcome description
  • The Lumina gained or lost
  • Your updated balance

Go hunting in the wilds to earn Lumina rewards.
Usable once every 20 minutes.

• Cooldown
  This command can be used once every 20 minutes per user.


• Hunting Reward
  Each successful hunt grants a random Lumina payout:
  • Minimum reward: 100 Lumina
  • Maximum reward: 300 Lumina


• Flavor Outcome
  A random creature is selected to flavor the hunt result:
  • 🦌 Deer
  • 🐉 Dragon
  • 🐗 Boar
  • 🦅 Eagle
  • 🕷️ Spider
  • 🐍 Snake


• Process
  A short hunting animation is displayed before rewards are granted.


• Result
  After completion, the result embed displays:
  • The hunted creature
  • The Lumina gained
  • Your updated balance

Gamble a chosen amount of Lumina for a chance to win more.

• Usage
  /gamble <amount>


• Win Chance
  You have a 45% chance to win the gamble.


• Winning Outcome
  On a win:
  • Winnings range from 150% to 220% of your bet
  • Winnings are added directly to your wallet


• Losing Outcome
  On a loss, the full bet amount is deducted from your wallet.


• Restrictions
  Bet amount must be positive and you must have sufficient Lumina in your wallet.

Spin the slot machine and test your luck.

• Usage
  /slots <amount>


• Slot Symbols
  Symbols have different rarity weights: 🍒 🍋 🍉 ⭐ 💎 🔥


• Outcomes
  
  • 3 matching symbols: JACKPOT — win 5× your bet
  • 2 matching symbols: Small win — net +50% of your bet
  • No matches: Lose the full bet


• Result
  The final result shows the symbols rolled and your updated balance.

Play a full interactive blackjack game against the dealer using casino chips.
Optional voice channel sound effects supported.

• Currency
  Blackjack is played using casino chips, not Lumina.


• Gameplay
  
  • Hit or Stand using interactive buttons
  • Dealer draws until reaching at least 17
  • Aces dynamically adjust between 1 and 11


• Payout Rules
  
  • Blackjack: +150% profit
  • Win: +100% profit
  • Push: No gain or loss
  • Loss / Bust: Lose full bet


• Audio
  Card, win, and loss sounds play automatically if you are in a voice channel.

Convert Lumina into casino chips for gambling games.

• Exchange Rate
  1 Lumina → 5 Chips


• High Amount Fee
  A 3% fee is applied when converting 10,000 Lumina or more.


• Validation
  Amount must be positive and available in your wallet.


• Result
  The embed displays Lumina spent, chips received, and any fee applied.

Convert casino chips back into Lumina.

• Exchange Rate
  5 Chips → 1 Lumina (0.2 Lumina per chip)


• High Amount Fee
  A 3% fee is applied when converted Lumina reaches 10,000 or more.


• Validation
  You must own the specified number of chips.


• Result
  The embed displays chips spent, Lumina received, and any conversion fee.

Displays a list of contributors who have helped develop Auralis and its features.

• Command Behavior
  When used, the bot sends an embed listing contributors and their respective contributions to Auralis.


• Displayed Information
  The credits embed includes:
  • Contributor display names
  • Associated roles or features they worked on
  • Clickable references to specific commands or systems


• Interactive References
  Some credit entries include:
  • Slash command references
  • External links such as the Auralis website and dashboard


• Contribution Requests
  The embed description encourages contributors to reach out if their contribution is missing from the list.


• Version Information
  The current bot version is displayed in the embed footer.


• Output
  The credits are displayed in a standard embed visible to everyone in the channel.

Displays detailed technical and general information about the Auralis bot.

• Displayed Information
  The embed includes a full system overview:
  • Total registered commands
  • Bot memory usage (RAM)
  • Bot uptime since last restart
  • Total users, servers, and channels
  • Discord.py version
  • Python version
  • CPU core count
  • Total system RAM
  • Operating system


• Bot Metadata
  The embed also displays:
  • Bot name and ID
  • Creator information with profile link
  • Bot creation timestamp
  • Current bot version


• Formatting
  System statistics are displayed in a formatted "asciidoc" code block for readability.


• Footer Information
  The embed footer displays the requesting user’s name and avatar, along with a timestamp.


• Output
  The information is sent as a public embed in the channel.

Displays the current Discord API latency for the bot.

• Latency Measurement
  The displayed ping represents the bot’s current WebSocket latency to Discord.


• Unit
  Latency is displayed in milliseconds (ms).


• Accuracy
  The value is calculated at the moment the command is executed and may fluctuate over time.


• Output
  The bot responds with a simple embed displaying the current ping value.

Sends an interactive invitation link to the official Auralis Discord support server.

• Availability
  This command can be used in:
  • Servers
  • Direct Messages (DMs)
  • Private channels


• Command Behavior
  When executed, the bot sends an embed containing a clickable button linking to the official Auralis Discord server.


• Invite Button
  The embed includes a Discord link button:
  • Button label: Auralis | Discord
  • Opens the official Auralis support server invite


• Embed Details
  The embed contains:
  • A short title encouraging users to join the server
  • The current bot version displayed in the footer


• Message Visibility
  The response is sent as an ephemeral message, meaning:
  • Only the command executor can see the invite
  • The message does not clutter public channels


• Logging
  Each use of the command is logged for analytics and usage tracking.

Report a bug directly to the Auralis development team for review and fixing.

• Usage
  /bug <feature> <description>


• Parameters
  The command requires two inputs:
  • feature — The command, event, or feature where the bug occurs, example: /rank <user>
  • description — A detailed explanation of what went wrong


• Bug Identification
  Each bug report is assigned a unique Bug ID:
  • Generated using a random seed and user metadata
  • Displayed as a short hash, example: af3c1


• Developer Submission
  When submitted:
  • The report is sent to a public bug-report channel
  • The embed includes the feature name and formatted description
  • The reporting user’s name and avatar are attached


• User Confirmation
  After submission, you receive a confirmation embed containing:
  • Your generated Bug ID
  • A direct link to the developer-side report message


• Visibility
  The confirmation message is visible in the channel where the command was used.


• Logging
  Each bug report is logged for analytics and usage tracking.

Submit a feature or improvement suggestion for the Auralis bot or dashboard.

• Command Type
  This command opens an interactive modal form instead of using inline text arguments.


• Suggestion Form
  When executed, a modal appears with two required fields:
  • Suggestion Name — Short title or command name
    Max length: 20 characters
  • Description — Detailed explanation of the suggestion
    Max length: 600 characters


• User Confirmation
  After submission:
  • You receive a confirmation embed thanking you for the suggestion
  • The confirmation message is sent as an ephemeral response


• Developer Review System
  Each suggestion is forwarded to the internal suggestion channel and includes:
  • The suggestion title and full description
  • The submitter’s name and avatar
  • Two interactive buttons: Accept (✅) and Reject (❌)


• Suggestion Thread
  For every submission:
  • A dedicated discussion thread is automatically created
  • The thread title includes the suggestion name
  • Developers can discuss and review the idea inside the thread


• Acceptance Handling
  If a suggestion is accepted:
  • The user receives a DM notification
  • An Upcoming Update embed is posted in the updates channel
  • A unique Suggestion ID is generated and displayed


• Rejection Handling
  If a suggestion is rejected:
  • The user receives a DM notification
  • The suggestion buttons are permanently disabled


• Button Safety
  Once a decision is made:
  • All buttons are disabled to prevent double actions
  • The decision cannot be changed afterward

Submit a 1–5 star review for Auralis that may be displayed publicly.

• Command Type
  This command opens an interactive modal form instead of using inline text arguments.


• Review Form
  When executed, a modal appears with two required fields:
  • Stars — A numeric rating between 1 and 5
    Exactly 1 character
  • Review — Written feedback about Auralis
    Minimum 20 characters, maximum 200 characters


• Validation
  Before submission:
  • The star rating is validated to ensure it is between 1 and 5
  • Invalid ratings are rejected with an error message


• One Review Per User
  Each user may have only one active review:
  • If a previous review exists, it is deleted
  • The old review message is removed from the review channel
  • The new review replaces it in the database


• Public Review Posting
  After submission:
  • The review is posted in the designated public review channel
  • The embed displays the user’s name and avatar
  • The star rating is shown using 🌟 icons
  • The written review is shown as the embed description


• User Confirmation
  Once the review is successfully saved:
  • You receive an ephemeral confirmation message
  • The message confirms your selected star rating


• Failure Handling
  If an error occurs during processing:
  • The review is not saved
  • You receive an ephemeral error message


• Administrative Removal
  A special Remove Review context menu is available:
  • Only usable by an authorized administrator
  • Deletes both the database entry and the message
  • Confirms removal with an ephemeral response

Play an uploaded audio file directly in a voice channel.

• Requirements
  You must be connected to a voice channel.


• Supported Formats
  .mp3, .wav, .ogg, .flac, .m4a, .aac


• Playback Behavior
  The file plays immediately and does not enter the queue system.


• Auto Join
  If the bot is not already in a voice channel, it will join yours automatically.

Play music using a YouTube or Spotify link, or a search query.

• Accepted Inputs
  YouTube links, Spotify tracks/albums/playlists, or plain text searches.


• Queue Handling
  If music is already playing, the requested track is added to the queue.


• Spotify Conversion
  Spotify links are automatically converted to playable audio sources.


• Queue Limit
  The music queue supports a limited number of tracks to prevent overload.

Displays the current playback volume.

• Volume Range
  1% – 100%


• Scope
  Volume is stored per server, not per user.

Adjust the playback volume.

• Usage
  /volume alter <1–100>


• Smooth Adjustment
  Volume changes are applied gradually to prevent audio spikes.


• Limit
  Volume cannot exceed 100%.

Skip the currently playing track.

• Behavior
  Skips to the next song in the queue.


• Fallback
  If the queue is empty, playback may stop or continue with recommendations.

Displays all songs currently queued.

• Pagination
  Songs are displayed in pages when the queue is long.


• Queue Types
  Displays both the main queue and any recommendation queue.

Shuffle all queued songs.

• Requirement
  At least two songs must be in the queue.


• Scope
  Only affects the main queue, not recommendations.

Remove a specific song from the queue.

• Usage
  /queue cancel <position>


• Indexing
  Song positions start at 1.

Pause the currently playing track.

• Requirement
  Audio must currently be playing.

Resume paused playback.

• Restriction
  Cannot be used if playback is already active.

Stop playback and clear the entire queue.

• Effect
  Stops playback, clears all queues, disables repeat, and disconnects from voice chat.

Toggle repeat mode for the currently playing track.

• Enabled
  The current song loops indefinitely.


• Disabled
  Playback continues normally through the queue.

Advanced message purge system with optional filters for precise cleanup.

• Usage
  /channel clear [amount]


• Optional Filters
  
  • user — only delete messages from a specific member
  • bots — remove bot messages only
  • contains — delete messages containing specific text
  • attachments — remove messages with files
  • minutes — limit deletion to the last X minutes


• Module Requirement
  Requires the Channels module to be enabled from the dashboard. If disabled, the command returns an error with a dashboard link.


• Permission Requirement
  You must have the Manage Messages permission to execute this command.


• Limits
  
  • Default amount: 25 messages
  • Maximum deletable messages: 250
  • Pinned messages are skipped automatically
  • Messages older than 14 days are deleted individually


• Behavior
  When executed successfully:
  • Messages are filtered before deletion
  • Recent messages are bulk-deleted when possible
  • Older messages are removed individually
  • A private confirmation embed is returned to the user


• Result Embed Includes
  
  • Total deleted message count
  • Number of skipped pinned messages
  • Applied filters (user, bots, text, attachments)
  • Selected time window, if used


• Error Handling
  
  • No permission ? command is blocked
  • No matching messages ? warning message shown
  • Deletion errors are safely ignored per-message

Prevents users from sending messages in the current channel by modifying channel permissions.

• Module Requirement
  This command requires the Channels module to be enabled via the dashboard. If disabled, an error message with a dashboard link is shown.


• Permission Requirement
  You must have the Manage Roles permission to use this command.


• Lock Behavior
  When locking a channel:
  • "send_messages" is disabled for "@everyone"
  • Roles with channel permission overwrites are also updated
  • Existing permission overwrites are preserved where possible


• Already Locked Handling
  If the channel is already locked:
  • The command exits early
  • An error embed stating the channel is already locked is shown


• Success Feedback
  Upon success, an embed confirms the locked channel by mentioning it.


• Failure Handling
  If the bot lacks sufficient permissions, an error embed is displayed.

Restores message sending permissions in a previously locked channel.

• Module Requirement
  This command requires the Channels module to be enabled via the dashboard. If disabled, an error message with a dashboard link is shown.


• Permission Requirement
  You must have the Manage Roles permission to use this command.


• Unlock Behavior
  When unlocking a channel:
  • "send_messages" permissions are reset to default
  • Role-specific overwrites are cleared where applicable
  • Normal message flow is restored


• Already Unlocked Handling
  If the channel is already unlocked:
  • The command exits early
  • An error embed states the channel is already unlocked


• Success Feedback
  Upon success, an embed confirms the unlocked channel by mentioning it.


• Error Handling
  Permission or Discord API errors are caught and displayed to the user.

Applies a Discord timeout to a selected user for a predefined duration.

• Module Requirement
  This command requires the Mute / Unmute module to be enabled via the dashboard. If disabled, an error message with a dashboard link is shown.


• Permission Requirement
  You must have the Moderate Members permission to use this command.


• Usage
  /mute <user> <time> [reason]


• Available Durations
  The timeout duration is selected from a fixed list:
  • 60 Seconds
  • 5 Minutes
  • 10 Minutes
  • 1 Hour
  • 7 Days


• Reason Handling
  The reason field is optional. If omitted, the reason defaults to No reason provided.


• Mute Behavior
  When executed successfully:
  • The selected user is timed out using Discord’s native timeout system
  • The timeout automatically expires after the selected duration
  • The user is prevented from sending messages or interacting


• Feedback
  A success embed is sent containing:
  • Muted user mention
  • Timeout duration
  • Reason (if provided)
  • User ID


• Error Handling
  
  • If you lack permissions, a permissions error embed is shown
  • If the bot lacks permissions, a Discord error is displayed

Removes an active timeout from a user and restores normal interaction permissions.

• Module Requirement
  This command requires the Mute / Unmute module to be enabled via the dashboard. If disabled, an error message with a dashboard link is shown.


• Permission Requirement
  You must have the Moderate Members permission to use this command.


• Usage
  /unmute <user>


• Unmute Behavior
  When executed successfully:
  • The user’s timeout is immediately removed
  • Normal messaging and interaction is restored


• Feedback
  A success embed is sent containing:
  • Unmuted user mention
  • Confirmation that the timeout duration is now None
  • User ID


• Error Handling
  
  • Permission errors are shown if you lack Moderate Members
  • Bot permission issues are displayed if Discord rejects the action

Create a moderation note attached to a specific user.

• Module Requirement
  This command requires the Notes module to be enabled via the dashboard. If disabled, an error message with a dashboard link is shown.


• Permission Requirement
  You must have the Manage Server permission to use this command.


• Usage
  /note create <user> <note>


• Note Limits
  The maximum number of notes allowed in a server is:
  • ⌈Member Count ÷ 10⌉ (one note per ten members, rounded up)


• Note ID
  Each note is assigned a unique 3-character alphanumeric ID used for identification and deletion.


• Behavior
  When successfully created:
  • The note is stored in the database
  • The note ID and content are displayed in a confirmation embed
  • The note is permanently attached to the selected user

Display all moderation notes associated with a selected user.

• Module Requirement
  This command requires the Notes module to be enabled via the dashboard. If disabled, an error message with a dashboard link is shown.


• Permission Requirement
  You must have the Manage Server permission to use this command.


• Usage
  /note get <user>


• Displayed Information
  For each stored note, the embed shows:
  • Note ID
  • Note content


• No Notes Handling
  If the user has no stored notes:
  • An embed is shown stating that no notes exist

Delete a specific moderation note from a user.

• Module Requirement
  This command requires the Notes module to be enabled via the dashboard. If disabled, an error message with a dashboard link is shown.


• Permission Requirement
  You must have the Manage Server permission to use this command.


• Usage
  /note delete <user> <note_id>


• Note Identification
  The "note_id" must match the ID shown in /note get


• Deletion Behavior
  When a valid note ID is provided:
  • The note is permanently removed from the database
  • A confirmation embed is sent


• Invalid ID Handling
  If no matching note is found:
  • The bot replies that no note exists with that ID

Start a customizable giveaway with timed entry, optional role requirements, and automatic winner selection.

• Permission Requirement
  You must have the Manage Roles permission to start a giveaway.


• Usage
  /giveaway <duration> <winners> <prize> [required_role]


• Duration Format
  The duration must include a time unit: - s > seconds - m > minutes - h > hours - d > days
  Examples:
  - 30m - 2h - 1d


• Winner Count
  
  • The number of winners must be a positive integer
  • Values lower than 1 are automatically corrected to 1
  • If fewer users join than winners, all participants may win


• Optional Role Requirement
  If a role is provided:
  • Only members with the specified role can join
  • Users without the role receive an error message when clicking join


• Giveaway Embed
  The giveaway message displays:
  • 🎁 Prize description
  • 👥 Number of winners
  • ⏳ Remaining time (live countdown)
  • 📊 Current number of participants


• Joining the Giveaway
  Users join by clicking the 🎉 Join Giveaway button:
  • Duplicate entries are prevented
  • Each successful entry updates the joined counter
  • Users receive an ephemeral confirmation message


• Automatic Ending
  When the timer expires:
  • Winners are randomly selected
  • Winning users are mentioned in the channel
  • The giveaway button is disabled


• No Participants Handling
  If nobody joins:
  • A message is sent stating that no one entered
  • No winners are selected


• Persistence & Restart Safety
  
  • Active giveaways are stored in the database
  • Giveaways automatically resume after a bot restart
  • Remaining time is preserved accurately

Embed creation has been moved to the dashboard interface.

Reactrole creation has been moved to the dashboard interface.

Set up the ticket system by creating a support channel with an interactive ticket button.

• Module Requirement
  This command requires the Ticket module to be enabled via the dashboard. If disabled, an error message with a dashboard link is shown.


• Permission Requirement
  You must have the Manage Channels permission to use this command.


• Usage
  /ticket tool <channel_name> <message>


• Setup Behavior
  When executed successfully:
  • A new text channel is created using the provided name
  • @everyone can view the channel but cannot send messages
  • Bot permissions are automatically configured


• Ticket Button
  The created channel contains:
  • An embed showing the provided description
  • An Open Ticket button for users to create tickets


• Post-Setup Note
  You are advised to move the ticket channel into an appropriate category.

Export the full message history of a ticket as an HTML or text transcript.

• Ticket-Only Command
  This command can only be used inside channels starting with:
  ticket-


• Transcript Format
  The exported transcript includes:
  • All messages in chronological order
  • Embeds, attachments, replies, and reactions
  • Author names, avatars, timestamps, and roles


• HTML Output
  The transcript is generated as a standalone HTML file using Discord-style components.


• Delivery
  The transcript file is sent directly into the ticket channel.

Add a user to an existing ticket, granting them access to view and send messages.

• Module Requirement
  This command requires the Ticket module to be enabled via the dashboard.


• Usage
  /add user <member>


• Ticket Channel Restriction
  This command only functions inside channels starting with:
  ticket-


• Permission Behavior
  When executed:
  • The selected user gains read and send permissions
  • The change applies only to the current ticket


• Confirmation
  A success embed confirms the added user and ticket channel.

Remove a user from an existing ticket, revoking their access.

• Module Requirement
  This command requires the Ticket module to be enabled via the dashboard.


• Usage
  /remove user <member>


• Ticket Channel Restriction
  This command only functions inside channels starting with:
  ticket-


• Permission Behavior
  When executed:
  • The user’s permission overwrite is removed
  • They immediately lose access to the ticket


• Confirmation
  A confirmation embed states that the user has been removed.

Sets up a complete server verification system using a math-based captcha and role-based access control.

• Module Requirement
  This command requires the Verification module to be enabled via the dashboard. If disabled, an error message with a dashboard link is shown.


• Permission Requirement
  You must have the Manage Server permission to run this command.


• Usage
  /verification setup <color>


• Verified Role Creation
  During setup:
  • A role named Verified is created if it does not already exist
  • The role color can be customized using a hex value
  • If an invalid color is provided, a default embed color is used


• Channel & Category Setup
  The setup process automatically creates or reuses:
  • A category named Verification
  • A channel named ✅┃verify
  • A channel named ❌┃unverified


• Permission Overhaul
  Once setup starts:
  • All channels are locked for @everyone
  • All channels are unlocked for the Verified role
  • Verification channels are excluded from the mass lock
  • Any channels that fail permission changes are listed in the result embed


• Verification Button
  The verify channel contains:
  • An embed instructing users to verify
  • A persistent Verify! button (survives bot restarts)


• Captcha System
  When clicking the verify button:
  • A math captcha modal is shown: a + b × c
  • The answer must be entered as a number
  • Incorrect answers result in verification failure


• Account Age Check
  Users must meet the minimum account age:
  • Accounts must be at least 2 days old
  • Younger accounts are rejected automatically


• Verification Completion
  Upon successful captcha completion:
  • The Verified role is added to the user
  • An ephemeral success message is shown


• Already Verified Handling
  Users who already have the Verified role receive a warning message and cannot verify again.


• Setup Result Summary
  After setup completes:
  • A private summary embed is sent to the executor
  • The embed lists created roles and channels
  • Any permission failures are clearly reported

TempVC creation will be moved to the dashboard interface.

Create an interactive event with sign-ups, automatic countdown, optional role pings, and timed start handling.

• Command Type
  This command opens an interactive modal instead of using slash arguments.


• Event Creation Modal
  When executed, you are prompted to enter:
  • Event Title — Short title (max 100 characters)
  • Description — Full event details (max 1000 characters)
  • Image URL — Optional image displayed in the embed
  • Your Current Local Time — Used for timezone calculation
  • Event Time (Local) — When the event should start


• Timezone Handling
  The system automatically:
  • Calculates your timezone offset based on input
  • Normalizes offsets to realistic ranges
  • Rounds the final event time to the nearest 10 minutes
  • Converts everything to UTC internally


• Role Mention Selection
  After submitting the modal:
  • You can select a role to mention when posting the event
  • Up to 24 roles are selectable
  • A No role option is always available


• Event Embed
  The posted event message contains:
  • Event title and description
  • Absolute and relative Discord timestamps
  • An optional image
  • A dynamic list of joined users


• Signup System
  The event message includes interactive buttons:
  • Join — Adds the user to the participant list
  • Leave — Removes the user from the list
  • Duplicate joins are prevented
  • All feedback is sent ephemerally


• Automatic Countdown
  Once created:
  • The bot continuously tracks remaining time
  • Checks run automatically until the event starts
  • The system survives bot restarts


• Event Start Handling
  When the countdown reaches zero:
  • A new thread is created under the event message
  • All joined users are mentioned
  • Joined users are automatically added to the thread
  • A start notification is posted


• Persistence & Cleanup
  
  • Active events are stored in the database
  • Timers resume automatically on bot restart
  • The event entry is removed once the event starts


• Error Handling
  
  • Invalid date formats result in an error response
  • Internal errors are handled with safe fallbacks

The Auralis Dashboard is a full-featured web control panel designed to replace traditional Discord-only configuration. It provides real-time management, visual feedback, and deep server customization — all secured through Discord OAuth.

• Server Selection & Authentication
  Secure Discord-based access control
  • Login using Discord OAuth2
  • Access limited to servers you manage
  • Automatic permission and ownership verification


• Overview Dashboard
  A centralized analytics overview displaying real-time server information:
  • Total members and online users
  • Prefix configuration with instant saving
  • Moderation statistics (bans & timeouts)
  • Boost tracking and member goals
  • Command, music, and item analytics
  • Ticket activity overview


• Module Management System
  Every major bot feature is modular and can be toggled independently:
  • AFK system
  • Music playback
  • Notes
  • Channel moderation tools
  • Mute and unmute commands
  • Ticket system
  • Verification system
  • Temporary voice channels (Join-to-Create)
  • Utility commands (avatar, banner, profile, server info)
  Disabled modules immediately block related Discord commands.


• Music Queue Management
  View and control the server’s music activity directly from the dashboard:
  • Live regular queue display
  • Recommended song generation
  • Queue capacity visualization


• Leveling System
  Complete leveling configuration without commands:
  • Enable or disable XP tracking
  • Interactive leaderboard display
  • Automatic top-level role assignment
  • User exclusions from top-role eligibility
  • MEE6 leaderboard import with reset confirmation


• Application Builder
  Design application systems visually:
  • Application and manager channel selection
  • Required and reward role configuration
  • Custom embed introduction text
  • Dynamic question creation
  • Live resend and delete controls


• Embed Generator
  Create Discord-style embeds with live preview:
  • Title and description editor
  • Author display with avatar support
  • Inline and stacked fields
  • Thumbnail and image support
  • Footer text, icon, and timestamp toggles
  • Direct channel delivery


• Memberstream System
  Automated join and leave messaging:
  • Custom embeds for member events
  • Dynamic placeholders ({member}, {server}, {membercount})
  • Image uploads and color pickers
  • Automatic role assignment


• Server Member Management
  Administrative control directly from the web panel:
  • View all server members
  • Kick or ban users instantly
  • Permission-checked execution


• User Warning System
  Clear moderation visibility for staff:
  • Users grouped by warning level
  • Live updates from moderation actions
  • Improved staff awareness


• Advanced Logging
  Granular event logging with channel binding:
  • Member, message, role and channel events
  • Thread lifecycle logging
  • Voice activity tracking
  • Prefix and slash command usage


• Emberwatch Anti-Spam
  Honeypot-based automated spam detection:
  • Dedicated detection channel
  • Kick, mute and failure tracking
  • 24-hour activity statistics
  • 7-day visual heatmap


• Instant Configuration Sync
  All changes apply immediately:
  • No bot restarts
  • No command reloads
  • Live backend updates


• Security & Permissions
  Built with strict access control:
  • Discord OAuth2 authentication
  • Role-based permission mirroring
  • No sensitive data exposure
  • Server-isolated configuration storage