Paginated Message Bug
Default paginated message
code:
Solution:Jump to solution
could they have any interaction handlers that ended up having the same name as something in a paginated message component?
12 Replies
Have you tried just doing
return paginatedMessage.run
instead of return interaction
havent used paginated messages in a while but that's all i used to return when i used it last
oh nvm, i looked in the example repo and they did it the same way as youThis is the default one, I didn't intend on using it but it's like that
like that from the CLI
To be more specific this happens when clicking the next page button
I honestly have no idea :\
Solution
could they have any interaction handlers that ended up having the same name as something in a paginated message component?
its pretty unlikely but
or maybe even ended up with another instance of the bot running
Those could both be possibilities. Maybe they have a general interaction handler where they already acknowledge the button press.
@./Ticker
Yes?
Have you looked at KaydaFox' suggestions?
I did, I just reinstalled sapphire and it worked as usual
IDK what happened
:kekw:
Putting his answer as the solution though
Cause it is a good possibility
Sure