Guide Revision Suggestions

[JavascriptLearner815]

1. [VERY LOW PRIORITY] Usage data in the help command doesn't surround itself in `s.
2. [MEDIUM PRIORITY] Guild-only data is absent in the help command.
3. [LOW PRIORITY] Args is absent in the help command.
4. [LOW PRIORITY] Cooldown-message feature is absent in the additional features page. (e.g. <@!12345678910111213>, ${cooldownMessage}, please wait ${timeLeft.toFixed(1)} more second(s).)
5. [VERY LOW PRIORITY] Help command specific info showcase div doesn't process the two asterisks as bold and just displays them as a fallback, as well as the backticks.
6. [LOW PRIORITY] DotENV should be another option in Configuration Files and the name of the page Configuration Files changes to Configuration.
7. [LOW PRIORITY] Command permissions should be above the dynamic help command section and the dynamic help command section include it.
8. [VERY LOW PRIORITY] "Can not" in command permissions should be "cannot" and the Y should be lowercase as it's a reply.
9. [LOW PRIORITY] Nodemon should be listed along with PM2's page.
10. [HIGH PRIORITY] Add more comments to complicated pages, such as Keyv, OAuth2, etc.
11. [HIGH PRIORITY] Detailed information and auxiliary support for each of the steps for Canvas.
12. [VERY HIGH PRIORITY] Add rankings that'll reduce the cooldown (especially one manually for the bot owner and moderators for no cooldowns) either in Making a Currency System or in Configuration Files, e.g. add ranks to the currency system or add ranks manually in the config.json (with, perhaps, another page explaining how to make a command that gives someone a rank).
13. [MEDIUM PRIORITY] read and write commands writing to a file named write.txt, with read showing the file's contents USING SPLIT, and write adding a new line followed by the required argument, followed by its new content USING SPLIT.
14. [MEDIUM PRIORITY] Command permissions should also check if the BOT has the permission, then display a different message if it already knows the USER has the permission.
15. [MEDIUM PRIORITY] Command permissions should be an array and LOOP through them, checking if ALL permissions are possessed, possibly even displaying what you have and what you need. Same with checking if the BOT has the permission from the aforementioned suggestion (14).
16. [MEDIUM PRIORITY] Owner-only command property.
17. [HIGH PRIORITY] The reload command section should explain how to make it also work with commands organized into folders.

...and more to be possibly bethought of.

I know some (or a lot) of these won't be added into the guide, but, obviously, that isn't everything, and plus, I want to see any thoughts or even additional revisions. Of course, discussing tweaks just makes the suggestions better!

(The CAPITALIZED PRIORITIES are somewhat just for show.)

Suggested Code to be Added to the Guide (Tweak These)

if (command.permissions) {
      const authorPerms = message.channel.permissionsFor(message.author);

      if (!authorPerms) return message.reply('you cannot do this!');

      for (const permission of command.permissions) {
        if (!authorPerms.has(permission)) return message.reply('you cannot do this!');
      }

      const myPerms = message.channel.permissionsFor(message.client.user);

      for (const permission of command.permissions) {
        if (!myPerms.has(permission)) return message.reply('*I* cannot do this myself!');
      }
}

[Danktuary]

1. Will add
2. Will fix
3. Will fix
4. Will add
5. Partially fixed in 2be792e but I missed one, will fix
6. Eventually
7. Okay
8. I think style(*): grammar, spelling, punctuation #539 fixes this, will verify later
9. Maybe eventually; PM2 suffices imo
10. Eventually
11. Could you elaborate?
12. This seems quite specific and out of the guide's scope. There are a few different existing pages that would provide you the information you'd need to build that yourself
13. Also specific, don't think so
14. Maybe
15. Maybe, I'll look into these
16. It's a one-liner, sometimes it's good to leave something for the reader to think up. I think it's mentioned on the FAQ page as well. But maybe.

Thanks for the suggestions. 😄 I'll take care of these as I see fit.

[JavascriptLearner815]

I made a fork on this project for a rough idea of some of the suggestions, as well.

[JavascriptLearner815]

Also, added a 17th suggestion.