[Known Issues]
Hey everyone, since Telegram's 64-Bit-ID Update which broke this and that, most issues are fixed now. However, there remain a few issues which I want to list here, so you all are aware.

Werewolf: 🐺
- [RESOLVED ✅] Custom GIFs:
While displaying custom GIFs is working again on both bots, the code that downloads the GIFs to our server appears not working. In consequence, the beta bot currently doesn't display your GIFs if you changed them after the update. We're investigating how to fix this.

- Getstatus
The /getstatus command is out of order because the new version of the Telegram Bot library doesn't support handling connection errors in the way it did previously. We will think about how to implement this again.

Executrix: 🔨
- [RESOLVED ✅] Commands by username
Any commands that require a userhandle (/kick, /ban, /mute, /warn, /id, etc.) do not work with a username if the user's ID has more than 32 significant bits. This is due to an external API we use which in turn uses a library that is still not updated for 64-Bit-IDs properly. We will make it work as good as we can until that library is fixed. For now, using such commands by reply or with the numeric telegram ID should work perfectly fine.

- Using said banhammer commands by reply on people who post anonymously through a channel of theirs is not working yet.

[RESOLVED ✅] Donations: 💸
The donation options are currently broken. We're working on bringing them back up! If you still want to donate right now, ask us in the support group, we will work something out.

New Links 🔗
The new format for private group/channel links is not yet supported by our bots. Temporary workaround: Change the links to the old format manually. For example, if your group link is https://t.me/+abcABC123, use the link https://t.me/joinchat/abcABC123 instead.


If you know of any issues that we missed in this list, tell us in the support group! Sorry for all problems caused, and happy wuffing!

Bots should be back online now, sorry for the wait, we had some major server issues. Happy wuffing!

[Executrix: Support for new Spoiler entities]

As of the new telegram update, you can now use a new type of entity, spoilers, in your messages. Now that the bot api was updated as well, Trixy supports these out of the box. You can use <span class="tg-spoiler">Your spoiler text goes here</span> in extra commands, welcome messages, rules, etc. Just keep in mind that people who don't have an updated version of telegram will see the entire message as "unsupported" message if a spoiler entity is in it.

The message below this one is a spoiler, so you can see how it looks for you :)

[Custom GIFs on Beta Bot]
The source of the GIF download problem was found and hopefully fixed. If your gifs get approved from now on, they should work on beta bot again, hopefully.

If you submitted your GIFs in the last few days, we will approve them right now and you should be good.

If it was longer ago, and your GIFs are currently not working on beta bot, please re-submit your GIF pack, it should work again after we approve it again.

We will be working on getting the donation platforms back up :)

Happy Wuffing everyone! 🐺

The bots are currently having some trouble, this might be caused by Telegram itself. Give them some time to recover, we will let you know when they are back :)

The bots seem to be working now, enjoy! 🐺

Just a heads up, if anyone wants to help support Ukraine, you can send money directly to them here: https://savelife.in.ua/en/donate/

There are two options, help the army or support the fund
Supporting the fund helps the citizens directly, I'd suggest that (I'm sure the army has plenty of money.. I could be wrong though)

If you use Fondy to send, note that the currency is in UAH, so make sure you do a currency conversion and type in the UAH amount, not your local currency amount.

Also, if you feel like helping ddos the Russians, just open this page and leave it open :)
http://stop-russian-desinformation.near.page

Be careful with DDOS attacks, they are illegal. Consider using a VPN if you still wanna do it.

Make love (and wolf), not war! 🐺

Because of the bots not working properly (again :/), we are going to reboot the server. We don't know the exact cause sadly. As soon as the remaining games on beta bot ended, the server will restart and hopefully the bots will work again.

The reboot didn't bring the success we hoped for. Investigating further at the time being.

In an experiment to find out what causes the issue, we are opening beta bot for all groups temporarily. Feel free to add @werewolfbetabot to your chats and play with it — Beta at least seems to work.
We are shutting the @werewolfbot down temporarily. Sorry for the inconvenience caused.

The bots appear to be back for now!
You can switch back to @werewolfbot, thank you. 🐺 :)

So apparently we are back to daily recurring hiccups for the Werewolf Moderator.

Procedure as follows, until further notice:

- If @werewolfbot works, use it.

- If it doesn't work, use @werewolfbetabot. Once beta leaves your group, try to use @werewolfbot again.

- If it doesn't work and @werewolfbetabot is leaving your group upon starting a game, feel free to shoot us a message in @werewolfsupport, we'll review it.

Sorry for the inconvenient way, we'll look how we can get the bot fixed in the long term.

We are performing a force reboot right now. All current games will probably be killed.
Do NOT spam bot commands, we will let you know when there is further information.

For now, we are back to the previous state. You can all play with beta when the normal bot doesn't work (like currently)

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)

Oh... I hope this doesn't happen, but I should mention, my cat has a tendency to step on the reset button of my PC.... if the bot dies in the middle of the night (I'm UTC - 6), I apologize :P

Just a heads up: In an attempt to fix this problem in the long term, we are going to migrate to a new server. It's been ordered and is now up and running. We will migrate the bots in the next few days, and of course let you know about how it goes.

Thanks to Para (and his cat), who enable us to have the bots running now despite the trouble on the old server!

Happy Wuffing everyone! 🐺