Skip to content

Server Owner Quick Setup

Baytae Tistear edited this page Jul 12, 2026 · 1 revision

Server Owner Quick Setup

Parent section: Installation and Setup

Use this page when adding SDAC to a Discord server for the first time or after a major update.

1. Invite The Bot

Invite SDAC with both required scopes:

  • bot
  • applications.commands

The public dashboard invite page can generate the invite link when the host has SDAC_BOT_CLIENT_ID or DISCORD_CLIENT_ID configured.

2. Open The Control Center

In Discord, run:

/sdac

/sdac is always the fallback command. The bot keeps the public command list small by default:

/sdac
/submit
/guess
/hint

Most admin tools are behind the /sdac buttons and submenus.

3. Run Setup

From /sdac, open Setup and use the setup wizard.

Configure at minimum:

  • SDAC admin role.
  • Submission channel.
  • At least one category repost channel.
  • Optional approval queue channel.
  • Optional weekly top-post channel.
  • Optional game summary and error notification channels.

4. Optional Custom Command Name

Server owners can set a server-specific launcher such as /pepo:

/sdac -> Setup -> Command Name

The custom command does not replace /sdac. It adds a server-only alias that opens the same control center. /sdac remains available as the stable fallback.

5. Sync Commands

After changing the command name, or if Discord shows duplicate/old commands, run:

/sdac -> Setup -> Sync Commands

This refreshes the server command list and clears copied guild commands. Discord may take a minute to update the command picker.

6. Run Checks

From /sdac -> Setup, use:

  • Setup Status for a quick readiness view.
  • Run Setup Test for database, folder, channel, permission, and command visibility checks.
  • Diagnostics for runtime checks.

The setup test shows:

  • Global commands active.
  • Server alias.
  • Guild-specific commands.
  • Whether duplicate guild command copies are cleared.

7. After Updates

After installing an update, restart the services on the server:

sudo systemctl restart sdac-bot
sudo systemctl restart sdac-dashboard

Then check Bot Owner Home. If it says the dashboard is newer than the bot heartbeat release, restart the bot again or inspect the bot service logs.

8. Useful Links

Clone this wiki locally