Nested message component collector not firing
Can anyone help me with this? Response from second button not firing
4 Replies
- What's your exact discord.js
npm list discord.js
and node node -v
version?
- Not a discord.js issue? Check out #other-js-ts.
- Consider reading #how-to-get-help to improve your question!
- Explain what exactly your issue is.
- Post the full error stack trace, not just the top part!
- Show your code!
- Issue solved? Press the button!switched back to an awaitMessageComponent but I'm running into the same issue for both:
that's the code for handleDemoteButton
0
and 1
log, and 2
correctly logs after 30 seconds
however pressing the button does not go through to 2
/ 3
I also tried logging the filter, nothing gets passed through to the filter
so am I listening to the wrong message or am I doing something stupid like that?
the first interaction is the slash command, /manage <@user>
the next interaction is involved when a user presses the Demote
button
lastly, as you can see here ^^, the final interaction involves a confirmation button saying Yes, demote them
thus this.handleComponentInteraction
is called from a collector
I know that the best way is to abstract it out into an event listener, however I was just wondering if there's a way to fix this as it is
type InitialInteraction = Command.ChatInputCommandInteraction | Command.ContextMenuCommandInteraction;
Command is from Sapphire
it is, but it is in a private repo at the moment
I can send a gist of the command fileYep
Yeah, that's true, that makes more sense
same, I'm a bit confused
I reckon I'll just refactor as that's probably part of what makes it so difficult to debug