Skip to main content

​
Getting Started

Click the invite link provided on the website or documentation. Make sure you have Manage Server permission in the server you want to add the bot to. The bot will request necessary permissions during the invite process.
Essential Permissions:
  • View Channels
  • Send Messages
  • Embed Links
  • Attach Files
  • Read Message History
  • Add Reactions
For Specific Features:
  • Manage Roles — For role management commands
  • Manage Emojis and Stickers — For emoji/sticker stealing
  • Manage Webhooks — For webhook commands
  • Manage Channels — For channel info commands
The bot works right away with the default prefix ~. You can:
  1. Test it with ~ping to confirm it’s working
  2. Use ~help to see available commands
  3. Configure features like vanity tracking, embeds, or custom prefix as needed
The default prefix is ~ (tilde). All commands start with this prefix, for example: ~ping, ~userinfo, ~steal
Server administrators with Manage Server permission can change the prefix using the prefix management commands. You can also enable no-prefix mode if supported.

​
Common Issues

Check these common causes:
  • Verify the bot is online (green status)
  • Make sure you’re using the correct prefix (~)
  • Check if the bot has Send Messages permission in the channel
  • Ensure you’re not on cooldown for that command
  • Try the command in a different channel
Still not working? Contact support with details about the command you tried.
This means either you or the bot lacks required permissions:If you’re missing permissions:
  • Check if you have the required role/permission for that command
  • Most management commands need Manage Roles, Manage Channels, etc.
If the bot is missing permissions:
  • Check bot’s role permissions in Server Settings
  • Make sure bot’s role is high enough in the hierarchy
  • Grant the specific permission the error message mentions
Common causes:
  • Discord API slowdown (temporary)
  • Large server with many members/roles/channels
  • Complex operations (like mass role assignment)
Solutions:
  • Wait a moment and try again
  • For mass operations, be patient (they take time)
  • If persistent, check Discord status page
Bots occasionally restart for:
  • Updates and maintenance
  • Server reboots
  • Bug fixes
The bot should come back online within a few minutes. If it’s offline for more than 10 minutes, check the support server for announcements.
Remember: Vanity tracking requires Aurelia bot, not just Celestia.Steps to fix:
  1. Make sure Aurelia is invited to your server
  2. Verify Celestia is present (Aurelia requires it)
  3. Check vanity features are unlocked in Celestia
  4. Confirm vanity URL is set correctly with /vanity view
  5. Ensure Aurelia has Read Messages permission
See the Vanity Tracking guide for setup help.
Common reasons:
  • Discord CDN links expire after a few hours
  • Image file is too large (>256KB for emojis, >512KB for stickers)
  • Server has reached emoji/sticker limit
  • Unsupported format (WebP, Lottie)
Solutions:
  • Reply to the original message instead of using old links
  • Check server emoji/sticker limits
  • Convert WebP to PNG for emojis
  • Lottie stickers cannot be stolen (vector format)

​
Features & Limitations

Celestia — Main bot with all core features:
  • Moderation commands
  • Role management
  • Emoji/sticker management
  • User/server info
  • Utilities
  • Embed builder
Aurelia — Extension bot specifically for vanity tracking:
  • Vanity URL monitoring only
  • Requires Celestia to be present
  • Better performance for vanity features
  • Must be invited separately
The bot supports one custom prefix per server. However:
  • Slash commands (like /vanity) always work alongside prefix commands
  • No-prefix mode can be enabled per server
  • Self-prefix — Users can set their own personal prefix with ~selfprefix <prefix>
Your personal prefix will work only for you across all servers with the bot!
Single steal (~steal): 1 emoji or sticker at a time (with interactive selection)Multi steal (~stealemojimulti): Up to 15 emojis per commandNote: Stickers can only be stolen one at a time using ~steal.
Emojis:
  • ✅ PNG (static)
  • ✅ GIF (animated)
  • ❌ WebP (not supported)
  • ❌ APNG (use GIF for animation)
Stickers:
  • ✅ PNG (static)
  • ✅ APNG (animated)
  • ✅ GIF (animated)
  • ❌ Lottie (vector format, cannot be stolen)
Emoji Limits:
  • Tier 0: 50 static + 50 animated
  • Tier 1+: 100 static + 100 animated
Sticker Limits:
  • Tier 0: 5 stickers
  • Tier 1: 15 stickers
  • Tier 2: 30 stickers
  • Tier 3: 60 stickers
Other Benefits:
  • Higher bitrate for voice channels
  • Vanity URL (Tier 1+)
  • Server banner (Tier 2+)

​
Commands & Usage

Check out the full command list on the website:https://celestia-bot-chi.vercel.app/#commandsThe website provides:
  • Complete list of all commands
  • Detailed descriptions
  • Usage examples
  • Command categories
You can also use ~help in Discord for a quick overview.
Some servers may have no-prefix mode enabled, which allows commands to work without the prefix. This is a server-specific setting configured by administrators.Slash commands (like /vanity) always work regardless of prefix settings.
Variables are placeholders that get replaced with actual values. Use them in embeds, messages, and webhooks:Examples:
  • {user.mention} → @username
  • {guild.name} → Server name
  • {guild.count} → Member count
  • {timestamp} → Current date/time
See the full Variables guide for all available variables.
View all your saved embeds with:
/embed list
Your embeds are saved to your account and can be used in any server where the bot is present. Use /embed builder to create new embeds.

​
Permissions & Roles

Role Management: Manage RolesEmoji/Sticker Management: Manage Emojis and StickersChannel Management: Manage ChannelsWebhook Commands: Manage WebhooksServer Settings: Manage Server (for prefix changes, vanity, etc.)Most info commands (ping, userinfo, serverinfo, etc.) require no special permissions.
Discord uses role hierarchy — roles can only manage roles below them.Rules:
  • Bot’s highest role must be above the role it’s managing
  • Your highest role must be above the role you’re managing (unless you’re server owner)
  • Managed roles (bot roles, integrations) have special restrictions
Solution: Move the bot’s role higher in Server Settings → Roles.
Roles are ordered from top to bottom in Server Settings. A role can only manage (assign, remove, edit) roles that are positioned below it.Example:
@Owner (highest)
@Admin
@Moderator
@Bot Role  ← Bot can manage roles below this
@Member
@Everyone (lowest)
The bot cannot manage @Admin, @Moderator, or roles above @Bot Role.
Yes! You can designate certain roles as “bot roles” to prevent them from being mass-assigned to humans using commands like ~role humans.This is useful for:
  • Integration roles
  • Bot-specific roles
  • Special permission roles
Bot roles can still be assigned to actual bots, just not to human members in bulk operations.

​
Troubleshooting

This means the role you’re trying to manage is higher than the bot’s highest role in the hierarchy.Solution:
  1. Go to Server Settings → Roles
  2. Drag the bot’s role higher in the list
  3. Make sure it’s above all roles you want the bot to manage
  4. Try the command again
Causes:
  • Webhook was manually deleted from channel settings
  • Channel was deleted
  • Webhook URL is incorrect
Solutions:
  • Create a new webhook in channel settings
  • Copy the new webhook URL
  • Update your commands with the new URL
  • Keep webhook URLs secure (don’t share publicly)
Common issues:
  • Embed doesn’t exist (check with /embed list)
  • You’re not the owner of the embed
  • Bot missing Send Messages or Embed Links permission
  • Embed has no title or description (at least one required)
Solutions:
  • Verify embed exists and you own it
  • Check bot permissions in the channel
  • Edit embed to include at least title or description
AFK status automatically clears when you send any message in the server.If it’s not clearing:
  • Make sure you actually sent a message (reactions don’t count)
  • Bot must be online and running
  • Check if bot has Read Messages permission
Workaround: Run ~afk again to reset it manually.

​
Support & Updates

Report bugs using the ~report command:
~report [description of bug]
Include as much detail as possible:
  • What command you used
  • What you expected to happen
  • What actually happened
  • Any error messages
Submit feature suggestions using:
~suggest [your suggestion]
Be specific about:
  • What feature you want
  • Why it would be useful
  • How it would work
All suggestions are reviewed by the development team!
Multiple ways to get help:
  1. Documentation — Check this website for guides
  2. In-Discord — Use ~report or ~suggest commands
  3. Support Server — Join the support server (link on website)
  4. Bug Reports — Use ~report for technical issues
Most questions can be answered by browsing the documentation!
Update logs and changelogs are posted in:
  • Support server announcements
  • Bot status channel (if configured in your server)
  • Official website/documentation updates section
Major updates are announced across all channels.
Yes! Join the official support server:https://discord.gg/BCUaYVVN55Get help with:
  • Direct support from staff
  • Community discussions
  • Update announcements
  • Feature suggestions
  • Bug reports

​
Still Have Questions?

Browse Commands

Check out the full command list and documentation on the website

Join Support Server

Get direct help from staff and community members