You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the bot restarts due to an update, a crash, or heroku's restart functionality (I believe this is a thing?) the bot currently does not cache the latest x amount of messages per channel. This means the delete or update events on recent messages posted before the restart won't be fired and thus won't be captured by the bot. This is definitely not ideal for the ghost ping functionality and the logging of message edits/deletes.
Expected Behaviour
When the bot is restarted it will cache the latest x amount of messages per channel so that events will trigger on those messages
Actual Behaviour
No messages are cached which means no events are fired on messages that were sent before the bot was restarted
The text was updated successfully, but these errors were encountered:
Overview
When the bot restarts due to an update, a crash, or heroku's restart functionality (I believe this is a thing?) the bot currently does not cache the latest x amount of messages per channel. This means the delete or update events on recent messages posted before the restart won't be fired and thus won't be captured by the bot. This is definitely not ideal for the ghost ping functionality and the logging of message edits/deletes.
Expected Behaviour
When the bot is restarted it will cache the latest x amount of messages per channel so that events will trigger on those messages
Actual Behaviour
No messages are cached which means no events are fired on messages that were sent before the bot was restarted
The text was updated successfully, but these errors were encountered: