Self-explanatory

No idea what happened, all of a sudden registering commands with the script now takes a long time.

It seems to be the PUT request that is taking so long, so I don't know if there's anything I can do.
I'll look into debugging a bit further, but for now I'll mark this as "wontfix".

It would be better if it recursively searched every directory, instead of needing to specify.

It's definitely working as it is, but it's more of a bandaid thing.

Perhaps adding more emojis would add some color, or research other ways to make READMEs stand out.

It's just very grey at the moment.

Instead of taking specific variables, it should take an object and just pass that object into the insertOne function.

Every other event is handled in the correct way besides this.

Implementation would probably be best if I make a new class for the updater, to maintain uniformity with the other events. Then just make an event file. This also would allow me to extend the updater with other CSGO events, or perhaps even make it an agnostic RSS updater.

As referenced in #12, README really does not need a lot of that text. It'd be much more succinct and just overall better to remove a lot of it.

Some parts that could be removed:

Right now, it tracks updates for a game called CS:GO, and tracks YouTube uploads for a YouTuber named EthosLab. Very random things, but they're what I want at the moment!

Not very configurable at the moment!!! I'm working on it next :D

^ Needs to be updated with a feature list, and the final paragraph is outdated.

Also, some parts should be rewritten in my opinion. Cut down on exclamation points perhaps?

Currently the loop is only reading inside the /commands/config folder, but eventually there will most likely be other commands that aren't related to config.

Recursively gathering the files in a folder would probably be the solution, I'll have to look into how to do that. Perhaps fs has a native way?

Right now if I add more config options, they won't be added to each server in the database.

Maybe make a script that goes through each document and generates new keys?

Right now it doesn't actually say much. Well, correction, it has a lot of words, but not many of them are important or necessary.

Listing features and cutting down on some of that would probably help.

Have a channel where you can type a message with a prefix, and the bot will automatically copy your message into the channel corresponding to that prefix.

Could work like this:

/notes auto prefix <prefix> <channel> | This would set a specific prefix to a specific channel

&Mi "make cow farm" | usage example, showing a prefix and a message. Generic version below:

&<prefix> <message>

Right now it's very easy for the program to crash. Try catch should make it safer at least.

It's really not needed, although it does serve as a good test for error messages. However, unit tests would probably be a much better way to check that, since the file seems to cause some issues rarely.