katreque / bottotherobot Goto Github PK

Start the implementation of the Getting Started.

• Installing Botto the Robot. (Wait until our Package is published)
• Creating a Discord bot.
• Configuring Botto.
• Adding Botto to a Discord Server.
• Choosing a template and executing it.
• Link to a tutorial for hosting the bot on AWS. (Issue to create a tutorial here)

Create a command handler to the bot.

• Check the bot prefix in the .env.
• Detect the bot commands.
• Only execute commands if the user has admin privileges.

Create a Permission handler where we can map Discord permissions (the most important and used) into a JSON. And we can use it on our config file and the template generation.

• Get User's Discord bot id and token (secret) and how to store it.
• Command to start the bot.
• Generate link to add the bot to the Discord Server.

Bunch of new stuff to add and refactor.

https://discordjs.guide/additional-info/changes-in-v13.html#before-you-start

Create a command to call the template generation function and handle the size and the language for that template.

The size should be a Enum based on the small, medium, big and giant options.
The language should be a Enum based on the EN and pt_BR options.

Time to implement the template execution on the user's command. It should get the template structure and replicate it on the Discord server.

Link to Discord Developers: https://discord.com/developers
Post the id and secret on the private discord team's channel.

What Modules should be added to each Template and it's respective Size (small, medium, big or giant)?

Actual Templates:

• Default
• Tech
• Gaming

Members without a role can see and access all channels created by Botto. They should have only basic access depending on what each template offers.

Create a command list to the docs and add the template command with all it's parameters (#18).

Get the language parameters from the generation command (as described on #10) or use the default language of the User that sent the command (using the Discord API). This info needs to be stored and will be used in the future.

On the eslint, remove the console logs from the warning list. It should be accepted because we use it to show some important info to the user.