-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Collector#end not firing off unless there's been another button pressed. #9922
Comments
You nested your listener, so it will not register until something reaches it. This is not a bug. Please don't dump your file and expect someone to comb through it to find your issue. You should provide a minimal reproducible code sample—whilst doing that, you may even find your issue. |
@Jiralite I think you conclusion is invalid. If user is getting response, then the parent scope was fulfilled and the collector should be registered. The code look pretty valid and looks like Discord.JS collector is actually not working well. I took his sample out and unnested it. Same behavior. |
Once again,
"A minimal reproducible code sample" means a one-file I can copy paste exactly as-provided (minus the token) and reproduce the issue. |
Which package is this bug report for?
discord.js
Issue description
Steps to reproduce:
Collection.stop() works perfectly fine provided there is pagination input. But if someone presses smash or pass without paginating then it does not fire off.
Code sample
Versions
discord.js 14.13.0
Node.js v21.0.0
WSL 1.2.5.0 // Ubuntu 22.04.3 LTS
Issue priority
Low (slightly annoying)
Which partials do you have configured?
Not applicable
Which gateway intents are you subscribing to?
Guilds
I have tested this issue on a development release
No response
The text was updated successfully, but these errors were encountered: