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
An idea I had to solve this is to record the message id on a successful count, then on the next count message, check that message still exists. If it has been deleted, reply with a warning message stating that and where the count is continuing from.
I had a quick look at the docs so may not have looked hard enough, but I couldnt find a way to tell if a specific message was deleted. The closest thing was an on_message_delete event. If we store the most recent count message, if that event is triggered and the messages match, we could then just say 'message was deleted, current count is ...'.
If the most recent message in the counting game is deleted and the next player has no way of knowing, someone can anonymously stop the game.
The text was updated successfully, but these errors were encountered: