Open hdorer opened 2 years ago
Moved to medium priority because it seems to be a rare occurrence
Band-aid fix would be to try/catch the interaction.reply() calls (especially since this seems to be a relatively rare occurrence) so that the bot doesn't doesn't die whenever this happens
This would not be as effective as I originally thought, since the catch for any error with the command still replies to the interaction. If I went this route I would have to add an additional try/catch for that which could just output to the log. But I might as well just learn how to defer the reply
This would not be as effective as I originally thought, since the catch for any error with the command still replies to the interaction.
or I could just not attempt to reply to the interaction in that catch clause...
So far I believe this has only happened with the quest mod commands
Band-aid fix would be to try/catch the interaction.reply() calls (especially since this seems to be a relatively rare occurrence) so that the bot doesn't doesn't die whenever this happens
More permanent fix would be to defer the reply, but that requires learning how to do a new thing