Aiess not taking bot commands anymore

[STCapricorn]

I'm not sure what happened, but Aiess seems to have stopped responding to bot commands altogether. It still posts in text channels just fine.

[Naxesss]

Discord is adding message intents soon. This means bots won't be able to read message contents, which will make text commands as-is unfeasible. Because of that, I've removed text commands and instead added slash commands (+ping -> /ping).

To get these comamnds to work on the desktop version of Discord, you need to re-invite the bot with the applications.commands scope.

https://discord.com/api/oauth2/authorize?client_id=680467769573244928&permissions=0&scope=bot%20applications.commands

Feel like there should be an easier way to do this, but it is what it is I guess.

[Rekunan]

Instead of removing text commands altogether, why not keep them in and give warnings that they'll soon no longer work? Or at least keep them in and have it respond that the text commands are depreciated, similar to how Bathbot does with some commands:

The main issue I have with what you did was that this GitHub issue was the only way I was able to learn about this change.

[Naxesss]

That's a good idea, will definitely try doing that once I'm done with uni stuff.

[Sitoria]

it works now
can close this issue

[Rekunan]

slash commands were already working, but this issue is about text commands not working (like +filters)