genericnerd / reaper Goto Github PK

• Message count
• Optional by user

Logging will require a refactor to reduce code duplication. It is imperative that when logging message edits or deletions, the entirety of the message (including attachments) is kept and carried over. A method to do this may be required.

Prevent this behaviour

• Moderator
• Admin
• Owner

Redis database will keep the last minute of the following:

• A user typing in a channel
• A user being in a voice channel unmuted

On every message and while a user is connected to a voice channel (will need to keep storage), we will compare to this cache. If they are in it, stop execution. Otherwise, give them XP per the guild's instructions.

Add Wendigo (role recovery) functionality to Reaper. The requirements are as follows:

• Each time a role is added, add it to a database
• Each time a role is removed, add it to a database
• On mute expiry, remove the muted role from this database. If the user is not on the server, remove it anyways.
• When a user rejoins, apply all their roles

The requirements are like current Reaper, which is as follows:

• Await a message reaction
• Check if we are in an ignored channel
• Check if the message is already on that board
• Check if it is a reaction we care about
• Check if the reaction count is over the threshold
• Copy the entire message, including attachments
• Add the message and board ID to a database to avoid duplicate log
• Send the message

Add settings command to allow an admin to adjust all guild settings

Add Giveaway Bot-like functionality. Requirements are as follows:

• Restart resistant
• Must be able to initially provide a giveaway name, duration, reward, optional channel, and optional role requirements
• Each entry must be checked if they meet the optional role requirement
• Each entry must be kept in a separate database table and no duplicates should be permitted (composite primary key)

as the title says

On /info, we send a message and delete it to figure out the latency. There must be a way to do this better

• Cooldown per user, configurable
• Once a message is reported, it cannot be reported again for 24 hours
• Allow roles to be mentioned
• Jump to message