A common mistake people do is use event.thinking
with event.reply
, however, they always run into the Interaction has already been acknowledged.
error! The reason for this is because event.thinking
is a response to the interaction, meaning you have acknowledged it! You should use dpp::interaction_create_t::edit_original_response instead.
Below is an example, showing how you should properly use the thinking method.
#include <dpp/dpp.h>
int main() {
event.thinking(true, [event](const dpp::confirmation_callback_t& callback) {
event.edit_original_response(dpp::message("thonk"));
});
}
});
if (dpp::run_once<struct register_bot_commands>()) {
bot.global_command_create(newcommand);
}
});
return 0;
}
The cluster class represents a group of shards and a command queue for sending and receiving commands...
Definition: cluster.h:80
std::string get_command_name() const
Get the command name for a command interaction.
Represents an application command, created by your bot either globally, or on a guild.
Definition: appcommand.h:1397
std::function< void(const dpp::log_t &)> DPP_EXPORT cout_logger()
Get a default logger that outputs to std::cout. e.g.
@ st_wait
Wait forever on a condition variable. The cluster will spawn threads for each shard and start() will ...
Definition: cluster.h:63
interaction command
command interaction
Definition: dispatcher.h:678
Session ready.
Definition: dispatcher.h:961
User has issued a slash command.
Definition: dispatcher.h:695
This will make the bot think briefly, then change the response to "thonk"!