Kaktushose
commented
1 month ago Wow, I didn't expect that anyone besides from me is still using this messy und unfinished framework 😅
jda-commands only acknowledges events just before a reply or edit get's send. I can't remember for sure why I've implemented it this way, but I believe there was a reason to it.
When your function calls take longer than 3 seconds, the interaction expires resulting in an unknown interaction error.
There are two possible solutions:
Acknowledge the component event by sending a reply before you do the heavy lifting:
@Button(value = "Random", emoji = "\uD83D\uDD27", ephemeral = true, style = ButtonStyle.PRIMARY)
public void onRandButton(ComponentEvent event) {
event.reply("Working on it...");
//time intense method call
event.reply("Second message, we are done!");
}Acknowledge the event manually
@Button(value = "Random", emoji = "\uD83D\uDD27", ephemeral = true, style = ButtonStyle.PRIMARY)
public void onRandButton(ComponentEvent event) {
((IMessageEditCallback) event.getContext().getEvent()).deferEdit().queue();
//time intense method call
event.reply("Second message, we are done!");
}P.S.: Remember that all these method run on the main WS thread. I don't know what your function calls exactly do, but be sure to not block the event thread.
stijnb1234
I have a slash command, which sends a reply with a button. When the user clicks on the button, I want to do some function calls (which takes some time) and then reply to the original interaction (replacing the original message).
However, when I do this, (sometimes) I get:
How can I do this correctly?
Example code: