Well. Hey all, it's Para. I would like to reiterate, I don't | Grey Wolf Development

Well. Hey all, it's Para. I would like to reiterate, I don't own / work on Werewolf anymore, but that being said I did step in on this one.

We haven't yet figured out the actual issue, it's a doozy (seriously, I've been at this for years, and I'm scratching my head here). From the server, we are getting response times up to 14 seconds from Telegram. With all of the messages Werewolf gets (seriously, if you don't need it, please remove Werewolf as an admin in your group), what happens is that in those 14 seconds, 1000's more updates come in, but we can only receive 100 at a time. Obviously, this isn't ideal, as the messages in the queue just.. grow exponentially.

We tried doing a ping to Telegram from the server, and we were getting 10ms response times, awesome... so why the slow response to getUpdates? So we tried doing a getUpdates request (to get your startgame calls :P) in Firefox, and that worked fine as well. So is there something wrong with the code? Shouldn't be, there haven't been any changes recently. We have contacted Telegram bot support about the issue, hopefully they can help us out, but in the meantime, I did something I didn't want to do, but... hey, people want to play right?

For the moment, @werewolfbot is now running on my personal machine, at home. Proving it isn't the code, it's running perfectly now, feel free to play. I'll have to set up a script to restart it once in awhile, but you should be able to play while we figure out this issue.

Sorry about the inconveniences, we hope to have this resolved for you soon, in a more permanent manner (if I lose power or internet, you lose werewolf)