-
-
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
Message Sweep not for manually fetched messages #4599
Comments
I've also run into this issue, and it's not entirely explained in any guide or documentation that when using awaitReactionCollector and the related events that unwanted behaviour can occur when specific client options are set (removing an active message from cache when it should have events on it). It would be nice to be able to set message.stopSweepable() or some manual logic that stops a message from being swept, and after we're done with the message we can set it to be swept. Or otherwise logging a warning to console if the time for a reactionCollector set is longer than the message cache lifetime. |
I also think that something like Edit: #6013 is making some big changes to being able to customize cache, possibly a way to alternatively implement this could work with this new feature |
I have general conceptional question, no one could help me on the discord server.
You can specify the cache in the client options
{messageCacheMaxSize, messageCacheLifetime,messageSweepInterval }
so that ram usage doesn't climb indefinitely.
But if I set it to one message, does my manual fetched messages for e.g. reaction listeners get sweeped?
If yes, add an option to not sweep manually fetched messages.
Thanks!
The text was updated successfully, but these errors were encountered: