> ## Documentation Index
> Fetch the complete documentation index at: https://docs.celestia.rest/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Start using Celestia in your Discord Server in just a few minutes.

## Prerequisites

Before adding Celestia to your server, ensure you have the following:

<Steps>
  <Step title="Required Permissions">
    You need **Administrator** permission or equivalent permissions to add bots to your server.
  </Step>

  <Step title="Role Hierarchy">
    Celestia's bot role should be placed in the **top 5 roles** of your server for optimal functionality.
  </Step>

  <Step title="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
  </Step>
</Steps>

<Warning>
  Ensure Celestia's role is positioned above roles it needs to manage. The bot cannot moderate users with roles higher than its own.
</Warning>

***

## Add Celestia to Your Server

<Card title="Invite Celestia" icon="plus" href="https://discord.com/oauth2/authorize?client_id=1372066291397169162&permissions=8&scope=bot+applications.commands">
  Click here to add Celestia to your Discord server with all recommended permissions
</Card>

<Info>
  The invite link includes all recommended permissions. You can customize these during the authorization process if needed.
</Info>

***

## Initial Setup

After adding Celestia to your server, follow these steps to get started:

<Steps>
  <Step title="Verify Bot Status">
    Check that Celestia is online and responsive by running:

    ```bash theme={null}
        ~help
    ```
  </Step>

  <Step title="Configure Prefix (Optional)">
    Celestia's default prefix is `~`. To change it:

    ```bash theme={null}
        ~prefix <new_prefix>
    ```

    Example:

    ```bash theme={null}
        ~prefix !
    ```
  </Step>

  <Step title="Set Up Antinuke">
    Protect your server with the antinuke system:

    ```bash theme={null}
        ~antinuke
    ```

    Enable the protections you need from the interactive panel.
  </Step>

  <Step title="Configure Logging (Recommended)">
    Set up a logging channel to track all bot actions:

    ```bash theme={null}
        ~log
    ```
  </Step>

  <Step title="Add Trusted Users">
    Whitelist your staff to prevent false antinuke triggers:

    ```bash theme={null}
        ~whitelist add @staff-member
        ~whitelist add @Admin Role
    ```
  </Step>
</Steps>

***

## Essential Commands

Get familiar with these core commands:

<AccordionGroup>
  <Accordion title="Help & Information" icon="circle-info">
    ```bash theme={null}
        ~help - View all available commands
        ~help [command] - Get detailed info about a specific command
        ~serverinfo - View server information
        ~botinfo - View bot statistics
    ```
  </Accordion>

  <Accordion title="Antinuke Setup" icon="shield-halved">
    ```bash theme={null}
        ~antinuke - Open antinuke control panel
        ~antinuke help - View antinuke help pages
        ~whitelist add @user - Add trusted users
        ~antinuke status - Check protection status
    ```
  </Accordion>

  <Accordion title="Moderation" icon="gavel">
    ```bash theme={null}
        ~ban @user [reason] - Ban a member
        ~kick @user [reason] - Kick a member
        ~timeout @user [duration] [reason] - Timeout a member
        ~warn @user [reason] - Warn a member
        ~purge [amount] - Delete messages
    ```
  </Accordion>

  <Accordion title="Configuration" icon="gear">
    ```bash theme={null}
        ~prefix <new_prefix> - Change bot prefix
        ~log  - Set logging channel
        ~welcome setup - Configure welcome messages
        ~autorole add humans @role - Add auto-role
    ```
  </Accordion>
</AccordionGroup>

***

## Next Steps

<CardGroup cols={2}>
  <Card title="Antinuke Protection" icon="shield-halved" href="/antinuke">
    Learn how to set up comprehensive server protection
  </Card>

  <Card title="Whitelist System" icon="shield-check" href="/whitelist">
    Configure trusted users and roles
  </Card>

  <Card title="Moderation Guide" icon="gavel" href="/moderation">
    Explore all moderation features
  </Card>

  <Card title="Full Command List" icon="terminal" href="https://celestia-bot-chi.vercel.app/#commands">
    Browse all 400+ commands
  </Card>
</CardGroup>

***

## Support & Resources

<CardGroup cols={2}>
  <Card title="Support Server" icon="discord" href="https://discord.gg/BCUaYVVN55">
    Join our Discord for help and community support
  </Card>

  <Card title="Documentation" icon="book" href="/">
    Browse the complete documentation
  </Card>

  <Card title="GitHub" icon="github" href="https://github.com/Zenith-Sosuke">
    View our GitHub repositories
  </Card>

  <Card title="Report Issues" icon="bug" href="https://discord.gg/BCUaYVVN55">
    Report bugs or request features
  </Card>
</CardGroup>

***

## Troubleshooting

<AccordionGroup>
  <Accordion title="Bot not responding to commands" icon="circle-exclamation">
    **Possible causes:**

    * Bot doesn't have permission to read/send messages in the channel
    * Wrong prefix being used
    * Bot is offline or restarting

    **Solutions:**

    * Check bot's role permissions
    * Verify prefix with `@Celestia prefix`
    * Check bot status in support server
  </Accordion>

  <Accordion title="Commands not working properly" icon="triangle-exclamation">
    **Possible causes:**

    * Insufficient bot permissions
    * Bot role is positioned too low in hierarchy
    * Missing required permissions

    **Solutions:**

    * Grant Administrator or required permissions
    * Move bot role higher in server settings
    * Check permission requirements in command help
  </Accordion>

  <Accordion title="Antinuke triggering on staff" icon="shield">
    **Possible causes:**

    * Staff members not whitelisted
    * Whitelist not configured properly

    **Solutions:**

    * Use `~whitelist add @staff` for each trusted user
    * Whitelist staff roles with `~whitelist add @Staff Role`
    * Verify with `~whitelist check @user`
  </Accordion>
</AccordionGroup>

***

## Legal Information

<AccordionGroup>
  <Accordion title="Terms of Service" icon="file-contract">
    By using Celestia, you agree to our Terms of Service.

    [Read Terms of Service →](https://celestia-bot-chi.vercel.app/terms)
  </Accordion>

  <Accordion title="Privacy Policy" icon="shield-halved">
    Learn how we collect, use, and protect your data.

    [Read Privacy Policy →](https://celestia-bot-chi.vercel.app/privacy)
  </Accordion>
</AccordionGroup>

<Note>
  Need help? Join our [support server](https://discord.gg/BCUaYVVN55) for assistance from our team and community!
</Note>