You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 26, 2023. It is now read-only.
When registering the commands, the command handler won't delete a command if the command file was deleted, it will leave the command in the application because it was not marked as deleted, but the entire file was deleted. I think it could be fixed with a check if the ApplicationCommands all exist locally, and if one doesn't it should get deleted.
The text was updated successfully, but these errors were encountered:
If your commands are Guild Commands, sometimes discord will cache your commands and will take some time to remove them from the application.
A way around this is to remove the bot form the guild and adding it back as it will reset the cache discord might have of the bot or you can take the bot offline for some time.
I don't believe this is a djs-commander issue as this also happens to be using other languages like Java to build bots.
Another option would be adding the deleted: true to the command file and restart the bot, after that leave it as is or delete the file and restart again if needed.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When registering the commands, the command handler won't delete a command if the command file was deleted, it will leave the command in the application because it was not marked as deleted, but the entire file was deleted. I think it could be fixed with a check if the ApplicationCommands all exist locally, and if one doesn't it should get deleted.
The text was updated successfully, but these errors were encountered: