Use the Add Stats Bot link above and review the requested permissions in Discord before authorizing. The current invite requests permission value 8 (Administrator). Only add bots you trust, and keep the bot's role below trusted staff roles.
Add the monitor and configure a status channel
Use the Add Stats Bot link above and review the requested permissions in Discord before authorizing. The current invite requests permission value 8 (Administrator). Only add bots you trust, and keep the bot's role below trusted staff roles.
Run /setup and select the text channel where the status message should appear. You may also choose an optional role or user to notify when the monitored bot changes status. The bot updates this message during its status checks.
/setup channel:#bot-status ping_role:@ModeratorsThe bot checks the monitored bot automatically and updates the configured embed. It synchronizes configuration, maintenance mode, and status history with the shared Supabase bot_documents table when SUPABASE_URL and a server-only SUPABASE_SERVICE_ROLE_KEY (or SUPABASE_SECRET_KEY) are configured. SQLite remains a local durable copy; on Railway set DB_PATH to a file on a mounted persistent volume so local data survives redeployments.
Copy the variable names from the Stats Bot .env.example into the hosting provider's secret/environment settings. Do not commit real credentials or put the Supabase key in browser code.
Run /remove to delete the status embed and stop tracking for this server. The server owner, an administrator, or an existing delegated manager can manage the tracker.