This would probably be helpful to have in a util file, but might be nice for some of the more complex queries we end up having

Quotes currently can't have linebreaks in them

image
The blank lines represent images sent

Continuous Integration 👍

Per Elmer, /votekick

When Aquarius is added to a server, only a select few modules should be enabled automatically. The rest will need to be enabled by the server admin.

As part of the settings, Aquarius should also allow the restriction of modules, perhaps using the following states:

1. ON: Anyone can use this module
2. RESTRICTED: Only the Aquarius Mod role and server admin can use this module
3. ADMIN: Only the server admin can use this module
4. OFF: The module won't run on the server

Further, additional configuration values should be allowable (things like API access keys and the like)

This is for you, @Mechdriver.

Allow the user to pass in an id or name and grab information about the corresponding Pokémon

Using GitHub Webhooks, the bot should respond to certain events from configurable repositories and broadcast them in configurable rooms. This will be a good initial test of #43

Add support for custom replies

• .command syntax is not working
  • .quotes add new "quote"
• keyword "new" is not working
  • @bot new quote "quote"

Per Zane, we should have a quotes module

Things like Karma won't trigger

If the bot owner gives a broadcast message, Aquarius should put it in all the general rooms for each server it's in. This will help alert people it's going down

It'd be nice to have bin scripts to automate some of these processes, especially when we end up needing a database.

Why not ¯_(ツ)_/¯

When new commands are added, Aquarius should alert server admins via DM so they can add the command if they wish.

When a user joins a server, Aquarius should message them with a configurable rules command. This will be a good initial test of #43

Perhaps allow it to be triggered in a room as well.

This should output all the commands the bot can run

This allows the bot to be a little customized for each server it's added to.

Lia suggested something like this: https://github.com/Donohue/karmabot/blob/master/scripts/example.coffee

Add the following commands to karma

@bot karma @user - shows user's karma level
@bot karma shitlist - shows users with the lowest karma level

The bot should respond to new deploys and broadcast them in configurable rooms. This will be a good initial test of #43

When Aquarius is added to a server, it should send a greeting to the admin explaining certain things about the bot. It should probably cover:

1. What it does
2. How to trigger it
3. Common modules and how to use them
4. How to configure bot settings for the server
5. How to contact me / find this repository

The server admins should be able to set certain settings for the server they are running here. (The bot will need to check for multiple servers run by the admin, and require specification if it's ambiguous).

It should disable the bot for X minutes in the server

This command should set an alarm for a certain time. It can be a single alarm, or repeated alarm and displays a set message when triggered.

Things like @ian ++ can get through, which breaks regex

Track when and where users were last active in a server

The bot should respond to passing and failing tests and broadcast them in configurable rooms. This will be a good initial test of #43

Module might be the wrong word, but in additional to one-off commands a broader scope should exist (system?) - but regardless, Dan wants the bot to be able to run a Mafia game.

As much as I'd hate to lose that in my code, there's a lot of duplication - it might be better to have message return false if it isn't triggered and a string on trigger, and then have Aquarius put it in a variable and run an if(var) { aq.sendMsg() } check

Currently the bot is in dire need of doing something exclusive to myself whenever I say a certain thing. That needs to be changed. I personally think it should be "dang" although I am open to other options.

Command Tests

• 8ball Tests
• Choose Tests
• Karma Tests
• Order Tests
• Overwatch Tests
• Pokédex Tests
• Quotes Tests
• Reply Tests
• Same Tests
• Seen Tests

Core Command Tests

• Broadcast Tests
• Info Tests
• Nickname Tests
• Stats Tests

Framework Tests

• Command Tests
• Link Util Tests
• Messaging Util Tests
• Permission Util Tests
• String Util Tests
• Trigger Util Tests
• User Util Tests

Config Tests

• ServerSetting Tests
• Default Key Tests
• Config Tests

Bot Tests

• Help Tests
• Message Tests
• Core Message Tests
• Query Tests
• Admin Tests

Poor @Fyurie can't use it since he's EU :(.

pls

We need to use the Procfile to set an env flag to read from dotenv or the Heroku env - right now, it throws an error when the bot starts in production.

I think it fits discord better to have to tag the bot. So @aquarius help instead of .help

Skiddiks has requested a @bot seen @user command, which outputs the time since the user has been offline for.

It'd be cool to see what replies get used most often. A simple usage counter + an "active" flag that is toggled on removal would do it (that way we don't lose data on reply deletion)

Adding requires quotes; removing doesn't allow them. They should be optional for removing a reply.

It'd be fun to integrate with Twitch and YouTube Gaming and post alerts / allow stream modifications (think title updates, donation alerts).

I'd probably have to create a permission system as part of this. Maybe a custom "Aquarius-Mod" role?

• Choose
• Order
• Reply
• Same
• Showtimes

The rest of the commands duplicate existing functionality

Since a lot of the regex follows a general pattern, might be worth trying to create some helper methods for it. The bot mention for instance would be a lot cleaner if it wasn't duplicated in each command

Allow the user to query for a card by name, and return information about the card

Ideally they should return a Promise that resolves to the response string

For large servers, it'd be nice to add a pickup group command where the bot automatically creates a voice channel and adds players to it, and then deletes channels as they become unused.

As mentioned here, we might want to add a general info command

https://github.com/meew0/discord-bot-best-practices