In general: Have some form of the CustomEmbedService but then for Delays, where every guild can specify its delays per command. Setting it to 0 wouldn't delete the command and setting it to 0.1 would basically be instant (+ it avoids the phone glitch where the messages stay). Also add a global delay which would automatically set all other delays to the same value. (defaults would be mostly 0 and 0.1)

Also write an extension for messages which would check if there is a delay and if it has to invoke the command.

• Role info

• change mentionable or not

• change name

• change colour

• give everyone in role x role y

• much more

Move all to a service

• Add 'message prefixes' that get denied.

• Add a cool thumbnail url

• Filter out purge command

• Ability to show people the deleted embed upon deletion

• Add message length checker

Adding a badges system that gives you badges upon reaching a certain level, achievement, or game related badge. Allow up to 18 badges on a user profile (image generated). Also have a few ideas summed up in a file already.

Redo it so I'd have multiple files in a folder per user (depending on the category so like let's say: general options - privacy related options - etc...)

Add a starboard system (with customizable reaction emote)

Add a blacklist system for Users & Guilds

Well the name says it all, a simple yet effective way of blacklisting all Users & Guilds. Shouldn't be too hard.

###Add/Fix storage system for CustomEmbeds.
Oh yeah. This has to be compatible for different languages.

Instead of just having it so people can customize the message sent in the current channel, they can also customize if the bot dms something, and if so, what.

###Add Cooldown precondition + a new class/struct to save all the precondition times from (guild-wise).

Every command will have a different Cooldown int (in seconds). Every guild will also have a global guild cooldown (int) and a PreferGlobalOverLocalCooldown (bool) value.

Then in the cooldown precondition, we would check if GlobalCooldown is 0, if it is, then we would use the LocalCooldown (even if it is 0, a 0 second cooldown is just no cooldown).
If GlobalCooldown isn't 0, then we would check if the guild PrefersGlobalOverLocal and decide which one to use based on that.

Also, idea: Make a command that shows all cooldowns for all commands.

This would be guild-wise, and ideally handled in MessageReceivedEvent.

This would include a blacklist and whitelist for both users & channels.

Plus, if possible, adding the ability to allow certain Discord permissions.
Like everyone with the "Add Reactions" permission would be able to access this command.

A lot wrong

###Add Possibility for custom 'languages'.
See #3, it has to be compatible with that too.
Basically what I mean, allow guilds to have a custom language, meaning they can customize any command with any output (one condition: It may and shall not break Discord's ToS, if it breaks the ToS, the entire Guild will be blacklisted from using the bot.)

This is a big part of the project, so it'll require some effort and time.

Achievements

I already had some great ideas. Listed them all in a file. Will continue working on it and post on here later.