skrytt / catnip Goto Github PK

The env file supports settings STREAM_NOTIFY_CHANNEL_ID and STREAM_NOTIFY_COOLDOWN. These settings must be made to be configurable in a per-guild fashion (via an admin command) instead, as the owners of different values will wish to choose different values.

We implemented this as an env setting initially for convenience, since the bot is used in one server only for now. A design goal is to have the bot be able to run in multiple servers safely, so this is considered a bug.

I would like to be able to roll N M-sided dice. For example:

• !roll 2d20 rolls two 20-sided dice
• !roll d10 or !roll 1d10 rolls one ten-sided die
• !roll 4d100 rolls four 100-sided dice

We will need to be able to modify the database schema in order to store additional data. To do this, we will need to find a workable approach to database versioning and upgrades/downgrades of the schema. This ticket is to track those efforts.

Ticket to track documentation issues.

• Need to document that SQLite3 development libraries are a linker dependency of this bot
• Improve documentation of mount/env variables (ideally also provide a template file)

We need to figure out how we can unit test commands we add to the bot, to give ourselves confidence we won't break them during refactoring.

Many users of this bot are roleplayers (for example, dungeons and dragons players). As a fun tool for the creative folks, I'd like to introduce a way to create and use simple character/creature/monster cards.

What I'm imagining is that users will be able to invoke some commands to build a card describing a character, and then use a command to display that card as a Discord embed.

When I say card, here is an example of the sort of thing I have in mind:
https://cdn.discordapp.com/attachments/515853207847567369/616396622389313548/unknown.png

I'd like to introduce better tools to be able to monitor the bot service and its performance. This ticket exists as a tracker for those initiatives.

Perhaps this will involve using something like Prometheus and Grafana to produce simple timeseries data, then introducing alerting tools to draw attention to service issues.

As a user, I want to be able to type !hedgehog
and see a picture of an adorable spiny hedgehog in my Discord channel.

As someone who is terrible at remembering birthdays, it would be handy if users could optionally register their birthday with the bot in a particular guild. If they did this, the bot could shout out their birthday in that guild on the right day, saving me the embarassment of forgetting.

Need to verify we're using rusqlite and SQLite in a way that isn't going to cause problems like thread races or data corruption.

Research best practices and make changes as required to ensure this is the case.

I'd like users to be able to choose their own title to be associated with their account, for example:

Scheming Skrytt

When a title is available for a user at the time a stream will be shouted out, the title should be used as a prefix for the display name of the user.

Goal is to have a pipeline automatically building, testing and deploying the bot.