Closed FusionBrah closed 2 months ago
This error can for the moment be safely ignored and doesn't break or affect anything in the bot, however I will take a look at correcting this as it is probably just a quick thing to add to my code. I'll check it out
Will this affect if the bot can @ reply to someones message?
Will this affect if the bot can @ reply to someones message?
No all of that has been working fine. (Edit: I deliberately set the bot to either not ping for replies or to just not reply at all because it got confused with it in the past, replying to someone 2 messages ago but hitting reply on the last person to type)
I've just put in a line that fixes this by adding the GuildMembers intent at initialisation. I'm not sure if anything actually uses it, but it might. I had a think about it and it might have affected its ability to see name changes like if you change the bot's name on discord for example it may not update in the program, but I'm not sure as I haven't tested it.
In either case it will all be fixed now, but nothing really should have changed for the most part.
G'day, When I am running the bot I am getting the following output in the console:
I have confirmed that the correct intent's are enabled on the application on the Discord Dev portal.
Cheers mate.