xinthedark / mzbot-v2 Goto Github PK

.define now does not return anything, and instead reports an error. In the logs, it reports "List index out of range".

This problem should be specific to Repl.it

Automatically installing packages for the user with os.system should be avoided, as commands like pip install -r requirements.txt aren't guaranteed to work all the time (e.g. if there is more than one version of python installed or pip isn't in PATH). Just the requirements.txt file is enough to indicate the dependancies and you should tell the user how to install them instead of doing it for them.

bot token was leaked!

Title is self-explanatory.

When an invalid argument is supplied to the meme command it runs indefinitely, blocking the heartbeat.

Rewrite the storage such that information is not stored in temporary variables, but in the repl.it database: https://docs.replit.com/hosting/database-faq

Right now, the .play command only accepts a url (string).

Need to add a search song feature; input string and auto search video from YouTube.

Tidy up the code; for example: remove unnecessary code and comments, and clean up the code to make it more readable.

Also improve code formatting. Readability is important.

Sadly, Heroku (which we have been using since the launch of this bot) will no longer be offering free Dynos (https://blog.heroku.com/next-chapter).

Hence, we will have to move to other hosting platforms by the end of this year.

Currently looking for alternatives.

Current hosting link on replit: https://mzbot-v2-3.jmuzhen.repl.co

Current repl link: https://replit.com/@JMuzhen/mzbot-v2-3

Currently, the bot is restarting very frequently (~70-80+ times a day), and commands seem to work for a very short period of time before they break.

This should be due to the "OpenAI moderation" feature added in 942b55b.

If there are no possible fixes, I will revert that commit.

MZ Bot has been amazing. I have developed it for more than a year now, and all sorts of useful features have been added. I also thank the Discord community for actively using and providing feedback on my bot.

However, I now announce that I will no longer be actively developing the bot.

Not that there is anything in particular that I hate. I am stopping development for a variety of reasons, for example:

1. I do not have so much time to work on this bot now.
2. I believe that the bot is almost "complete", and there are not many new features to be added. Despite that, I recognise that there are many bugs to be fixed and features to be enhanced, but those are no longer a top priority for me.
3. I do not agree with the general direction of how Discord is developing the bot system (see this thread by Rapptz, the creator of discord.py). Discord is currently strongly encouraging every bot developer to switch to slash commands. In the future, it is highly probable that they will force everyone to use slash commands; However, it is clear to me that the slash commands system was not developed properly. For example, using a slash command is around 5 times slower than using normal text commands: you have to first type the command, wait a split second for all the commands to load, choose the command you want, then enter parameters, and finally wait for the bot to respond.
4. I do not have the time and patience to migrate to slash commands, and I think that it is useless to do so. Everyone on Discord is much more familiar with text commands.

To clarify: I don't think slash commands are a bad idea in general, but the way Discord has implemented slash commands shows that they have not put much thought and effort into it.

Open source projects are a great idea; I will probably be creating them and/or be contributing to them in the future. For now, it is more important that I learn some programming skills.

Bye.

TL;DR: I will no longer be a Discord bot developer. I still want to develop software though.

It is crucial that the bot knows how to handle unexpected errors.

Timeline:

• In 25caf75, basic error handling was mostly complete.
• Then, I realised that when hosting on Replit, many repls share the same IP address; hence it is common to be rate limited by discord.
  • In 36b4c0e, a small bypass was added.
  • In 3c516e8, the (mostly) complete bypass was added.

However, there are many other use scenarios and errors that are not handled properly as of now. It is important that we fix these errors, making the bot more stable, before adding new functionality.

Our goal for now is simple: to ensure that the bot can run automatically and completely on its own, without any human intervention or maintenance.

https://discordpy.readthedocs.io/en/latest/api.html#discord.Member.timeout