Skip to content
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

Counting game bug #266

Open
Anonyyymous opened this issue Dec 15, 2024 · 3 comments
Open

Counting game bug #266

Anonyyymous opened this issue Dec 15, 2024 · 3 comments

Comments

@Anonyyymous
Copy link

Anonyyymous commented Dec 15, 2024

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.

@ericthelemur
Copy link
Contributor

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.

@Anonyyymous
Copy link
Author

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 ...'.

@ericthelemur
Copy link
Contributor

Pretty sure you can get away with fetching the message, and if it doesn't exist, then it has been deleted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants