SAC Stats Bot Setup Guide — Backup Configuration

Prerequisites

Before setting up SAC Stats Bot, ensure you have:

Administrator permissions on your Discord server
SAC Bot already added to your server (recommended but not required)
A dedicated channel for bot alerts and notifications
Basic understanding of Discord bot permissions

🚀 Step 1: Add SAC Stats Bot

Click the Invite Link

Use the official invite link to add SAC Stats Bot to your server:

            https://discord.com/oauth2/authorize?client_id=1522192055177318443&permissions=8&scope=bot%20applications.commands
          

Select Your Server

Choose the server where you want to add SAC Stats Bot from the dropdown menu.

Authorize the Bot

Review the permissions requested and authorize the bot. The required permissions include:

Read Messages/View Channels
Send Messages
Embed Links
Attach Files
Read Message History
Add Reactions
Use Slash Commands

Complete Authorization

Complete the CAPTCHA verification if prompted, and SAC Stats Bot will join your server.

Step 2: Initial Setup

Run Setup Command

In any channel where SAC Stats Bot has access, run the setup command:

/stats_setup

Follow the Setup Wizard

The bot will guide you through the initial configuration:

Select your preferred language
Choose alert notification channels
Set monitoring frequency
Configure basic alert thresholds

Verify Setup

Once setup is complete, verify the configuration:

/stats_config view

🔔 Step 3: Configure Alerts

Create Alert Channels

Create dedicated channels for different types of alerts:

#bot-alerts - General bot status alerts
#security-alerts - Security-related notifications
#admin-updates - Administrative notifications

Configure Alert Channels

Set up which channels receive specific alert types:

            /stats_alerts channel #bot-alerts

            /stats_config alerts #bot-alerts

Test Alert System

Send a test alert to verify notifications are working:

/stats_test

Step 4: Link with SAC Bot (Optional)

If you have SAC Bot on your server, you can link the two bots for coordinated operation:

Get SAC Bot ID

The main SAC Bot ID is: 1509876788875231242

Link the Bots

Use the link command to connect SAC Stats Bot with the main bot:

/stats_link 1509876788875231242

Verify Connection

Check the connection status:

/stats_status

💡 Note

Linking with SAC Bot is optional but recommended for better coordination and status monitoring.

🔍 Step 5: Configure Monitoring

Set Check Interval

Configure how often the Stats Bot checks SAC Bot status:

/stats_monitor interval 30

This sets the check interval to 30 seconds (recommended: 30-60 seconds).

Set Timeout Values

Configure timeout and retry settings:

            /stats_monitor timeout 10

            /stats_monitor retries 3

Test Monitoring

Trigger a manual status check to verify monitoring is working:

/stats_check

Verification

After completing the setup, verify everything is working correctly:

Final Checks

Run /stats_status to confirm the bot is operational
Run /stats_test to verify alerts are working
Check that alert channels are receiving notifications
Verify monitoring intervals are appropriate for your server
Test the manual check command: /stats_check

Status Check

/stats_status --detailed

🔧 Common Issues

Bot not responding to commands

Ensure the bot has proper permissions and try re-inviting if necessary.

Alerts not being sent

Check that alert channels are properly configured and the bot has permission to send messages there.

Connection to SAC Bot failing

Verify SAC Bot is online and that both bots are on the same server. Try unlinking and relinking.

Monitoring not working

Check your monitoring interval settings and ensure the bot can reach SAC Bot's API.

Next Steps

After successful setup, consider these additional configurations:

Set up custom alert thresholds for your specific needs
Configure additional alert channels for different types of notifications
Set up integration with external monitoring tools if needed
Create a response plan for when SAC Bot goes offline
Train your moderation team on how to respond to alerts