Prerequisites
Before adding Celestia to your server, ensure you have the following:1
Required Permissions
You need Administrator permission or equivalent permissions to add bots to your server.
2
Role Hierarchy
Celestia’s bot role should be placed in the top 5 roles of your server for optimal functionality.
3
Essential Permissions
- Manage Channels — For voice features and channel management
- Manage Roles — For moderation and role features
- Ban Members — For antinuke and moderation
- Kick Members — For moderation features
- Manage Messages — For automod and purge commands
Add Celestia to Your Server
Invite Celestia
Click here to add Celestia to your Discord server with all recommended permissions
The invite link includes all recommended permissions. You can customize these during the authorization process if needed.
Initial Setup
After adding Celestia to your server, follow these steps to get started:1
Verify Bot Status
Check that Celestia is online and responsive by running:
2
Configure Prefix (Optional)
Celestia’s default prefix is Example:
~. To change it:3
Set Up Antinuke
Protect your server with the antinuke system:Enable the protections you need from the interactive panel.
4
Configure Logging (Recommended)
Set up a logging channel to track all bot actions:
5
Add Trusted Users
Whitelist your staff to prevent false antinuke triggers:
Essential Commands
Get familiar with these core commands:Help & Information
Help & Information
Antinuke Setup
Antinuke Setup
Moderation
Moderation
Configuration
Configuration
Next Steps
Antinuke Protection
Learn how to set up comprehensive server protection
Whitelist System
Configure trusted users and roles
Moderation Guide
Explore all moderation features
Full Command List
Browse all 400+ commands
Support & Resources
Support Server
Join our Discord for help and community support
Documentation
Browse the complete documentation
GitHub
View our GitHub repositories
Report Issues
Report bugs or request features
Troubleshooting
Bot not responding to commands
Bot not responding to commands
Possible causes:
- Bot doesn’t have permission to read/send messages in the channel
- Wrong prefix being used
- Bot is offline or restarting
- Check bot’s role permissions
- Verify prefix with
@Celestia prefix - Check bot status in support server
Commands not working properly
Commands not working properly
Possible causes:
- Insufficient bot permissions
- Bot role is positioned too low in hierarchy
- Missing required permissions
- Grant Administrator or required permissions
- Move bot role higher in server settings
- Check permission requirements in command help
Antinuke triggering on staff
Antinuke triggering on staff
Possible causes:
- Staff members not whitelisted
- Whitelist not configured properly
- Use
~whitelist add @stafffor each trusted user - Whitelist staff roles with
~whitelist add @Staff Role - Verify with
~whitelist check @user
Legal Information
Terms of Service
Terms of Service
By using Celestia, you agree to our Terms of Service.Read Terms of Service →
Privacy Policy
Privacy Policy
Learn how we collect, use, and protect your data.Read Privacy Policy →
Need help? Join our support server for assistance from our team and community!