Setup

SirenBot is self-hosted, which means you must host it yourself, on your servers.

Setting up the bot itself

To begin, you must create a Discord bot and copy its token. For steps on how to do that, visit this guide. You'll be able to change the bot's profile picture, username, and about me there.

After you've copied its token, open token.env and replace the "insert_token_here" text with your token.

Do not give out your bot's token, as it will give anyone who has it full access to the bot.

The default prefix of SirenBot is sb!. If you'd like to change it, open up SirenBot.py, find TOKEN (near the top), change it to anything you'd like, then restart the bot.

Before you do anything else

As soon as you start the bot, go into any channel and run the sync command.

Setting up logging channels

To edit the logging channels (for the events), you'll need to add channel IDs to config.env. If you don't know how to copy channel IDs, visit this guide.

Open config.env and input 3 variables. Make sure to follow the following format:

GENERAL_LOGS = CHANNEL ID: INTEGER
CRITICAL_LOGS = CHANNEL ID: INTEGER
MEGA_ALERT_LOGS = CHANNEL ID: INTEGER

An example of this would be:

GENERAL_LOGS = 1067273085029453865
CRITICAL_LOGS = 1067526616948932698
MEGA_ALERT_LOGS = 1074873948803698688

Make sure the bot is able to view the channels you're putting into config.env.

After you've added your logging channels, run the setup command in your logging server.

If setup gives no response, make sure you have administrator permissions and try again.

If you wish to change your logging channels, update config.env, restart the bot, then run the setup command again.

Registering channels and roles

You can only register commands and roles once. To check if it has already been run, view config.

To register channels and roles into the config, run the register command, using the following format:

/register <@modrole> <@adminrole> <@teamrole> <@verifiedrole> <#generalchannel>

An example of this would be:

/register @moderator @administrator @staff @members #general-chat

Variable Information

• GENERAL_LOGS is for regular logs, such as command logging and other relatively harmless events.

• CRITICAL_LOGS is for critical events, such as a scary role being updated, a watched role being given, and more.

• MEGA_ALERT_LOGS is for the most important logs, such as general being locked, a scary role being created, and more.