Because most ctfs use ctfd, I believe it is conceivable to have the bot establish an account for that ctf (assuming it uses ctfd).

This will also necessitate the addition of configuration for the email address that will be used in the registration process, as well as any other information that may be required (depends on what the registration requires). 

Currently the bot sends CTF reminders to the channel defined as REMINDER_CHANNEL in the configuration variables, and if the variable is not set, it looks up a channel named #general or the first world-readable channel it can write to. It would be good to have a command to set the reminder channel manually.

Bug fixes

• /ctf takenote wasn't taking attachments into consideration (fixed in 6bd9cba)
• /ctf status wasn't displaying all challenges because of Discord's fields limit of 25 per embed (fixed in 6bd9cba)
• After adding a challenge, the command issuer shouldn't be able to see its channel automatically, otherwise it will cause a lot of pain if /ctf pull is run, as a lot of challenges will be added (fixed in 6bd9cba)
• Periodic puller wasn't working properly (fixed in 6bd9cba)
• Truncate event information (description and prizes) which can be larger than Discord's allowed field value length of 1024 (fixed in 54a2497)
• /ctftime upcoming can be used in DM now (fixed in 23d9b01)

Optimization

• Session cookies are now cached (fixed in 70ccbbc)

Features

• Add /ctf scoreboard command to display the scoreboard at any time, in addition to posting the scoreboard periodically in its dedicated channel (introduced in 79f276c)
• Add /request and /report commands to send a feature request or a bug report to the developer (introduced in 22f4755)
• Post solves summary after archiving the CTF (introduced in 718c3a3)

Enhancements

• Add ability to feed a numerical ID into /ctf workon instead of going through the pain of typing a long challenge name (introduced in 7decf6e)
• Format scoreboard to easily spot our team position (introduced in 5e22987)

1. Added the possibility to manage multiple guilds simultaneously, every guild has its own separate database.
2. Updated installation instructions in README.md, there are 2 methods now, either by inviting the bot or self hosting it.
3. Added a new slash command /config which enables setting per guild configuration variables easily.

• [x] Add docstrings according to the docstring convention in PEP 257
• [x] Add CONTRIBUTING.md
• [x] Revisit README.md (I've written it in hurry)
• [x] Integrate Github workflows to check pull requests mergeability (check that they conform to our coding style)
• [ ] Add a new cog for generating reverse shell payloads, shellcodes, gopher payloads, etc

Major changes

• Switched to Slash commands that Discord introduced in late 2020
• Structured the project files

Minor changes

• Setup proper logging of errors
• Moved the configuration from docker-compose.yml to config.py

New features

• Retrieve challenges from the CTFd platform periodically by invoking the ctf pull command, create the challenge and send a pinned message in its channel containing the challenge information (name, description, points, etc).
• Announce an upcoming event when it approaches and enable voting using reactions.
• If the announced event gets a certain amount of positive votes, the CTF is automatically created and members are given instructions on how to join.
• When the CTF starts, a reminder will be sent in its general channel by mentioning the CTF role, also, the clock emoji in the category name will change to a red dot.
• Announce added challenges in the CTF's announcements channel and a lot more features.

The bot lacks a key command, namely /ctf intro. This will be simple; once executed, the bot replies with a series of messages and images describing its usage (from joining a CTF, pulling challenges, solving challenges, etc). It will be useful for members who never used the bot before.