Pyre Bot has one main goal: Create an easy-to-use way to manage a maintain dedicated game servers from within Discord. From sending commands to the game console to allowing players to initiate a restart vote, Pyre was created to make it as easy as possible.
Feel free to join our Discord if you want to discuss the bot or hang out!
These instructions will help make sure your system is ready to run the bot and help you get started using it for your needs.
The bot can be ran without everything listed below, but this is what we recommend:
Pyre Bot is meant to be ran within Docker; we use AWS ECS but you can use whatever container service you like. If you prefer not to use containers, install the requirements and it can be ran locally.
The latest pre-built Docker images can be found here.
You need to get an API token from the Discord Developer Portal. The token will be used later in the environment variables. Invite the bot you create on the developer portal to your server and create the following for each RoR2 server you plan on running:
- Admin commands channel
- Public commands channel
- In-game chat channel
- Role for linked members
Also create a channel for all servers to post updates to.
Set up a Seq server to ingest the logs from the game, we use Twiner's GotSeq plugin to send our logs there. Seq needs te be set up with an API key for each server you plan to host.
Pyre Bot uses Amazon DynamoDB to store player stats from the servers and link Discord IDs to SteamIDs. You will need to setup an AWS account an add some tables to DynamoDB for this to work. Create the following tables:
- BotCommands_Stats - Primary key: DiscordID (String)
- Players - Primary key: DiscordID (String)
Since we host our Seq server in AWS as well as the bot, it is recommended to use EFS to enable your files to be shared between these services.
Several variables need to be configured in the environment to make the bot run correctly, without these it will fail to run:
- ADMIN_CHANNELS
- ADMIN_ROLE
- AWS_ACCESS_KEY_ID
- AWS_SECRET_KEY_ID
- CHAT_CHANNELS
- COMMANDS_CHANNELS
- DISCORD_TOKEN
- LINKED_ID
- LOG_LEVEL
- LOG_PATH
- PLAYERS_TABLE
- SEQ_API
- SERVER_ADDRESSES
- SERVER_CHANNEL
- STATS_ENDPOINT
- STATS_REGION
- STATS_TABLE
- TRACK_STATS
Never upload online or share your configuration to anyone you do not trust. These API keys are private and can result in your access from the services being removed if they get out.
The bot requires that you are using the following mods in your RoR2 server. Not having all of these mods installed and updated to their latest builds can result in certain features not working properly.
Required Mods
- BepInEx
- Change redirectOutputLog to true in your doorstop_config.ini to prevent double messages being sent to BepInEx terminal.
- BotCommands
- Used to send commands to the server from Discord
- R2DSE
- Outputs steam player names and IDs
- DebugToolkit
- Outputs run time and stages cleared
- Enables additional commands to be sent to the server (i.e. give_item, give_equip)
If running in Docker, launch the bot using the following example command; consult your hosting server if using another container platform.
docker build -f Dockerfile -t pyre-bot:latest .
&& docker run
-v path/to/your/log/folder:/data
--env ADMIN_CHANNELS=list,of,channels
--env ADMIN_ROLE=Admin
--env AWS_ACCESS_KEY_ID=
--env AWS_SECRET_ACCESS_KEY=
--env CHAT_CHANNELS=list,of,channels
--env COMMANDS_CHANNELS=list,of,channels
--env DISCORD_TOKEN=
--env LINKED_ID=
--env LOG_PATH=/data/
--env SEQ_API=
--env SERVER_ADDRESSES=list_of_server_address:with_ports
--env SERVER_CHANNEL=
--env STATS_ENDPOINT=https://dynamodb.us-east-2.amazonaws.com
--env STATS_REGION=us-east-2
--env STATS_TABLE=BotCommands_Stats
--env TRACK_STATS=yes
--env LOG_LEVEL=info
--name pyre-bot
--rm
pyre-bot:latest- restart : Initiates a vote to restart the server
- Requires a majority vote (at least 75% of in-game player count)
- votekick {player}: Initiates a 30-second vote to kick {player} from the Risk of Rain 2 server
- Requires a majority vote (at least 75% of in-game player count)
- endrun : Initiates a 30-second vote to end the current run in the Risk of Rain 2 server
- Requires a majority vote (at least 75% of in-game player count)
- info : Lists the game server status via Steamworks API
- Listed info includes server name, current stage, player count, player names, and ping
- link {SteamID} : Allows players to see their play stats for the Risk of Rain 2 server
- Assigns the "Linked" role (NOTE: requires further config to not be hardcoded)
- stats : Outputs your player stats to chat
- Currently supported stats are Time Played, Stages Cleared, and Runs Completed
- help : Displays all commands
- start : Starts the Risk of Rain 2 server
- stop : Stops the Risk of Rain 2 server
- delete {number} : Deletes the given amount of messages in the channel
- say {message} : Sends an in-game message from the perspective of the server
- cmd {command with args} : Passes on a command to execute by the server
- Very experimental as of now, only use when you are sure of the results, as passing commands in certain contexts can cause unhandled exceptions with BotCommands
- giveitem {player} {item} {quantity (default - 1)} : Gives a player a specified quantity of an item
- giveequip {player} {equip} : Gives a player a specified equipment
- restart_admin : Restarts the server without votes
- help_admin : Displays information on how to use admin commands
By default the bot is configured to manage a Risk of Rain 2 server. This can be changed by calling the executables for other servers and pointing the checks at their respective logs.
- Discord.py - Discord API wrapper for Python
- Python-A2S - Steamworks API wrapper for Python
Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.
To add functionality for other games or servers, add a new file in the cogs folder.
See also the list of contributors who participated in this project.
This project is licensed under the GPL-3.0 License - see the LICENSE file for details
- Moved chat to its on cog
- Server now posts updates to server update channel
- Created Server class
- Finally updated the README?
- These updates got lost somewhere :)
- Moved all stat tracking to Amazon DynamoDB for a better experience
- Custom version of the Pygtail module is now packaged with the bot
- Fixed an exception that occurred when the bot reconnected to Discord servers.
- Complete rewrite of setup.py
- Updated all requirements to newest versions
- Various fixes, improvements, and optimizations that makes everyone's lives better
- Added player stat tracking
- Improved integration with DebugToolkit
- Gets run time and stage number from the server log output directly
- Other things I've likely just forgotten about ... it's been a while
- Added configuration options for admin and command channels
- This allows running multiple bot instances to manage more than one server
- New global check makes sure the bot only listens to commands in these channels
- Added dictionaries for items, equipment, and stages
- Commands check dictionaries for values before issuing to the server
- Added basic logging
- Log can be found in the bot.log file in the bot's directory.
- New delete command allows simpler delete or testing messages
- Improved error handling
- Steam query is now used to check if the server is running
- Added giveequip command
- status command now shows current stage name
- Added say, endrun, giveitem, and votekick commands
- Requires BotCommands
- Added a setup script to create config.ini on first launch
- Added option to output game chat to Discord channel
- Enabled by default, change in config.ini
- Added automatic server restarts
- Enabled by default, change in config.ini
- Using new Steamworks API