geas-bot/TODO.md

To Do

• Testing
• Dockerise
• Infer/Transfer data from old bot
• Deploy

Bot Architecture

• Simplify directory tree
• Split event listeners into individual cogs.
• Update with re-organised data and config structure

• Correct references to data in existing cogs.

• Setup minimally functioning configs of guild on startup
• Synchronise core configuration /commands on startup
• Synchronise secondary /commands on complete configuration (see below)

Bot Functionality and Processes

• 'Delete Commands' Function
• 'Register Commands' Function
• Infer Permissions from Config
• Dynamic Command Prefixes
• Infer current games from Server Structure Create a separate cog to do this instead of having a migrate command, install the cog temporarily and remove the cog once migration is done.
• Re-enable logging
• Delete Dev/Test Functions
• Error handlers
• Debug Features

• Command Installer/Uninstaller

• Help Channel Event Listener

• Add Config key for Help Channel

• Slash Command Buttons or This kind of got subsumed into other features.
• Reaction listener selectors So did this.
• Member Verification

• Add Config key membership signup channels
• Add config keys: Membership Category Roles
• Message Receive listener
• Message React listener or buttons Used buttons waiting within the same command thread. Possibly update to global listener if performance is affected.

• Membership Restriction

• Message Receive Listener
• Membership Validation Listener

• Re-synchronise commands after any relevant config changes (See from above)

• Role Delete (member, admin, game) Admin role missing won't cause any issues as server role will still remain in control

Deleting membership roles will also trigger a mess. Event listener will trigger and attempt to execute simultaneously with the command to delete the role, which will cascade into several errors. In order to make this work, it is best to have the commands interact solely with the roles, and then subsequently the listeners to sync with the data.

• Channel delete (notifications, logs, game text channel) There aren't any critical settings that depend on this just yet, and it is hard to set this up without circularity
• Category delete (games) Circularity problem: if the category delete event listener is set up, it will react to the bot deleting categories when managing games.

• Flag for checking completeness of configuration for a guild.

• Function for checking configs for completeness

• Synchronise game channel on role updates

• Exception to event listener to prevent circularity unsure what this means

I remember what this is now: if you have a listener for when roles get deleted, and if the bot deletes a role, then it triggers the listener. It might be worth restructuring this such that the Bot command only deletes the role, which then triggers the listener that deletes the categories and synchronises data. That way, the roles can be deleted manually or via the command. Otherwise, it is not possible in the Discord API to have this exception, as the Bot only responds to the 'Guild' deleting the role, not the user or bot or admin that issued the command.

Event Listeners

Review Configs When

• Guild Changing Ownership
• Roles Modified
• Mod Channel Deleted

Commands

• Configure Bot function and sub commands

• botrole (role group)
• committeerole (role group)
• modchannel (channel group)
• help channel (channel group)
• signup channel (channel group)
• newcomer role (role group)
• returning player role (role group)
• student role (role group)
• help notifications (notification group)
• signup notifications (notification group)

• Set up timeslots
• Delete timeslots

• Base command
• Delete all games with the timeslot Do the opposite: block deleting timeslots with existing games.

• List timeslots
• Set up command permissions

• Slash Commands

• Admin Commands
• Game Management Commands

• Native Bot Commands

• Migrate existing bot commands

• setupgame
• definebotrole config
• deletegame
• reset purge
• migrate See above
• kickplayer /player remove
• addplayer /player add
• leavegame /player leave
• Pitch command and sub-commands

• run Combined both sub-commands into single command and prompt response.
• clear

Misc

• Review documentation

• Finalise README.md
• CHANGELOG.md
• COMMANDS.md
• resources.md

• Make sure to document not using discord_components and staying with discord-py-slash-commands library alone.