itsshunya / shuwy Goto Github PK

Currently the !help command shows the docstring for each command, some of them have information which is useless for the user.
e.g. Cog Members: !welcome channel : Subcommand for "welcome" function to set the welcome channel.

Functions which return a message should always return an embed style message.

After looking at other bots, it is clear people often do not like long command names. We might want to get new names for command names that are phrases or maybe unite them in a group

When you try to give somebody a role (for example welcome role) that is higher than the bot's role, it will display a message.

Since the update to the database library (from sqlite to aiosqlite) the functions related to favourite music have stopped working.

This might be due to some database writting/reading issue with the new library.

When using the !welcome text subcommand, the bot output an error Error in command: welcome text

name 'set_welcome_message' is not defined

When using the BATCH file to launch Shuwy, it displays Shuwy version as 10.0

EditorConfig helps maintain consistent coding styles for multiple developers working on the same project across various editors and IDEs. The EditorConfig project consists of a file format for defining coding styles and a collection of text editor plugins that enable editors to read the file format and adhere to defined styles.

The values for Guild ID and Guild Name are swapped out in the logs for the bot.

It might be useful to add another .md page showing a graphic tutorial to generate a Discord Bot Token for people who are new with Discord bots.

Feature requested

Migration to use Pipenv instead of Python virtual environments.

Reason

This will ease the creation of a virtual environment and it is increasing its popularity, a guide on how to configure it should be added as well.

Planning

Install the Pipenv package from pip, add a Pipfile and Piplock migrating from requirements.txt to Pipenv and replace the run.bat paths.

Expected behaviour

All the python modules should be installed in the pipenv virtual environment and it will be easier to work around it.

Actual behaviour

All the python modules are stored in the python installation or the virtual environment.

At the moment (v.0.0.7) when a user reacts with an emoji to the music player, he needs to remove the emoji by himself if he wants to press the same button again.

e.g. User wants to lower the volume a lot: He will need to add and remove the emoji to do it multiple times.

Feature: Remove emoji on use.

The current bot uses sqlite3 for database management, while this is not an asynchronous library.

Should migrate to aiosqlite (asynch).

We need more logs for different things happening within the bot, currently it is logging the commands used. Could log on_error as well.

Suggested: new command to assign roles (minimum 1, not maximum).
It should check if the user already has each one of those roles.

Recently a timestamp was added to the BATCH file to display the current date and time for each line command.
But for the call to the python Shuwy.py there is no timestamp displayed, so from that line onwards no timestamp is displayed.

In the main command line window for the bot, the python version is incorrect.

Nowadays many people use discord, but most discord communities are kept in a single language.
Not everyone speaks english fluently or likes to have a bot in english.

FEATURE REQUEST: Add more languages to the bot
IDEA: It is possible to work with a JSON for each language and store all the string data in them, loading the JSON depending on the language chosen. The one thing not possible would be to change the name of the commands (or maybe use alias...)

With the new discord version, it is mandatory the use of intents for certain things, which makes it mandatory to use at least the version 1.5.1 of discord.py

It might be useful to add another .md page showing a tutorial to set up a Lavalink server and edit its configuration.

When a member joins a server the database should get connected and retrieve the data for the welcome role/message from there. There is a problem here where it does not connect correctly to the database.

After using !help, an error is displayed regardless the conditions.

Possibly a TimeoutError.

When posting a bot message containing an embed, the thumbnail picture (bot's avatar) is displayed a bit blurry.

Subject of the issue

In the welcoming messages, the bot sets the thumbnail picture of the embed to the avatar of the user who joined. Sometimes this avatar is not displayed correctly, displaying only a loading screen.

Your environment

• ID: 737219824987406367
• Shuwy version: 0.2.4
• Discord.py version: 1.5.1
• Python version: 3.7.5

Steps to reproduce

Let a member join to a server that has configured the welcome message on member join and add an embed message. Most of the time it will be right, but it will display a loading image some times.

Expected behaviour

The thumbnail picture should be the avatar picture of the user.

Actual behaviour

Sometimes a loading picture gets displayed.

Subject of the issue

In some functionalities where the bot has to send an embedded message containing a tag to the specified user @User#0000, instead of displaying his tagged name such as @User, it displays his ID as <@02049239499202523>.

Your environment

• ID: 737219824987406367
• Shuwy version: 0.2.4
• Discord.py version: 1.5.1
• Python version: 3.7.5

Steps to reproduce

Let a member join to a server that has configured the welcome message on member join and add an embed message with a tag to the user in that message. Most of the time it will be right, but it will display some weird ID numbers at some point.

Expected behaviour

The user should get tagged (not notified because it is within an embed) in the format @User.

Actual behaviour

The user gets tagged displaying his ID in the format <@02049239499202523>.

The music cog has completely stopped working, with a log message displaying the error:
Failed to match ytInitialData JSON object

Possibily Lavalink/Wavelink failure.

Add .README to include the documentation for this project.