Official Werewolf Group (English) - Moved to a "private" chat because Telegram does not allow all countries to join public groups
https://telegram.me/joinchat/B7EXdD1l2nZnyyHrsP0ZYw
https://telegram.me/joinchat/B7EXdD1l2nZnyyHrsP0ZYw
So, about the past couple hours -
The bot was running, everything on our end was perfect. However, Telegram almost completely stopped sending it ANY messages for over an hour (and I was still asleep, so I didn't notice). The bot was asking Telegram for updates, and Telegram was telling it that there were no messages for it. I.e. your commands to @werewolfbot were not reaching the bot, even though the bot was asking for them.
I've revoked the API token, replaced it with a new one, and started the bot back up. Everything should be good now.
If you'd like to see this mornings events for yourself, feel free to look at my log file. Check out 9:06:43 AM, which is when it went down.
Log file lines are as such:
Timestamp - Time for bot to run httprequest to get messages - how many messages Telegram sent the bot in that request.
The bot was running, everything on our end was perfect. However, Telegram almost completely stopped sending it ANY messages for over an hour (and I was still asleep, so I didn't notice). The bot was asking Telegram for updates, and Telegram was telling it that there were no messages for it. I.e. your commands to @werewolfbot were not reaching the bot, even though the bot was asking for them.
I've revoked the API token, replaced it with a new one, and started the bot back up. Everything should be good now.
If you'd like to see this mornings events for yourself, feel free to look at my log file. Check out 9:06:43 AM, which is when it went down.
Log file lines are as such:
Timestamp - Time for bot to run httprequest to get messages - how many messages Telegram sent the bot in that request.
Werewolf Enforcer Update:
Hello! As some of you might have noticed, the @admin cmand was unstable for the most part of the last 24 hours; this is because the team behind @werewolfbutlerbot has been tweaking and modifying the system to better suit the needs of the users and could only do it in a live environment so that we could test it properly.
As you know we used to have multiple reports coming in for just one item when different users report the same issue with the @admin tag. Enforcer will now recognise them as the same issue and only 1 report will be triggered to prevent multiple reports being logged for the same item.
Also on the @admin tag, we have added the /solved command which will enable the admins to recognise reports that have already been acted on. Usually when an issue is reported with the @admin tag, all the admins will receive the notification and be alerted, resulting in scenarios where multiple admins taking action for the same issue. This command essentially eliminates that possibility when the report has been marked as resolved and prevents the other admins from taking action on the same report. It also gives you piece or mind as to whether or not issues are being dealt with.
Please see below for a usage example and remember you have to reply to the message that contains @admin.
Note: This command does not work for admins in certain regions due to how telegram manages it's data.
As always, please go to @werewolfsupport for more information or if you need help; and you can look at our code at https://github.com/BladeZero/GroupButler
Hello! As some of you might have noticed, the @admin cmand was unstable for the most part of the last 24 hours; this is because the team behind @werewolfbutlerbot has been tweaking and modifying the system to better suit the needs of the users and could only do it in a live environment so that we could test it properly.
As you know we used to have multiple reports coming in for just one item when different users report the same issue with the @admin tag. Enforcer will now recognise them as the same issue and only 1 report will be triggered to prevent multiple reports being logged for the same item.
Also on the @admin tag, we have added the /solved command which will enable the admins to recognise reports that have already been acted on. Usually when an issue is reported with the @admin tag, all the admins will receive the notification and be alerted, resulting in scenarios where multiple admins taking action for the same issue. This command essentially eliminates that possibility when the report has been marked as resolved and prevents the other admins from taking action on the same report. It also gives you piece or mind as to whether or not issues are being dealt with.
Please see below for a usage example and remember you have to reply to the message that contains @admin.
Note: This command does not work for admins in certain regions due to how telegram manages it's data.
As always, please go to @werewolfsupport for more information or if you need help; and you can look at our code at https://github.com/BladeZero/GroupButler
GitHub
GitHub - dllz/GroupButler: A Lua Telegram based on Otouto
A Lua Telegram based on Otouto. Contribute to dllz/GroupButler development by creating an account on GitHub.
Werewolf Moderator Information
Seeing how many games are running on both @WerewolfBot and @WerewolfiiBot , it no longer makes sense to try to prevent bots from hitting api limits. (If a bot sends more than 30 messages per seconds, telegram delays all messages from the bot. Now realize that the bot is running enough games to have 3000 players at one time....) To solve that, we tried creating a clone of Werewolf Bot. @WerewolfiiBot, so now, we own two api-limits hitting bots. Lol, we're most certainly not going to make a third one.
Para spent a while writing a setup guide for devs who would like to offer their chatrooms a non api limited bot (If bot is in a small number of chats, it won't be delayed).
Now, if BIOS sounds to you like a Biological Vegetables brand, or compiler makes you thing of Wall-E, do not even bother to read on. This post is intended for devs, and people who know what they are doing. The software you use could break your computer if misused, and melt your brain if you get stuck on "Why the heck does it not want to work". Support WILL NOT be given on @werewolfsupport if you have no idea what compile or runtime or any of these things mean. If you are a serious developer, and we can tell you at least got most of it done, we can answer small questions (it is possible Para left something out of the setup guide) Cause if you try to set up a bot, you should have some basis (google IS a good place to start).
Check out the github readme for the setup if you are interested in creating your own clone. (Note that , yes, to run your werewolf clone, you do need windows.)
https://github.com/parabola949/Werewolf/blob/master/README.md
Note -
This does NOT mean development of @werewolfbot has stopped! Check the github regularly for updates that you can merge into your own fork
Another note - if you do spin up a clone, feel free to let us know!
Seeing how many games are running on both @WerewolfBot and @WerewolfiiBot , it no longer makes sense to try to prevent bots from hitting api limits. (If a bot sends more than 30 messages per seconds, telegram delays all messages from the bot. Now realize that the bot is running enough games to have 3000 players at one time....) To solve that, we tried creating a clone of Werewolf Bot. @WerewolfiiBot, so now, we own two api-limits hitting bots. Lol, we're most certainly not going to make a third one.
Para spent a while writing a setup guide for devs who would like to offer their chatrooms a non api limited bot (If bot is in a small number of chats, it won't be delayed).
Now, if BIOS sounds to you like a Biological Vegetables brand, or compiler makes you thing of Wall-E, do not even bother to read on. This post is intended for devs, and people who know what they are doing. The software you use could break your computer if misused, and melt your brain if you get stuck on "Why the heck does it not want to work". Support WILL NOT be given on @werewolfsupport if you have no idea what compile or runtime or any of these things mean. If you are a serious developer, and we can tell you at least got most of it done, we can answer small questions (it is possible Para left something out of the setup guide) Cause if you try to set up a bot, you should have some basis (google IS a good place to start).
Check out the github readme for the setup if you are interested in creating your own clone. (Note that , yes, to run your werewolf clone, you do need windows.)
https://github.com/parabola949/Werewolf/blob/master/README.md
Note -
This does NOT mean development of @werewolfbot has stopped! Check the github regularly for updates that you can merge into your own fork
Another note - if you do spin up a clone, feel free to let us know!
GitHub
GreyWolfDev/Werewolf
Werewolf for Telegram. Contribute to GreyWolfDev/Werewolf development by creating an account on GitHub.
Oh also.... good job everyone, we ran 33844 games yesterday, compared to 26973 the day before... @werewolfbot is growing fast!
Not sure what is happening, but @werewolfbot is receiving a 502 error from Telegram
Looks like the Telegram API is back online. @werewolfbot is running ok again
Remember, if you enjoy playing Werewolf, take a moment to rate us easily right here on Telegram!
telegram.me/storebot?start=werewolfbot
telegram.me/storebot?start=werewolfbot
Telegram
Telegram Store Bot
@Storebot helps you discover the best bots 👾 on Telegram. Explore charts, rate bots and enjoy updates! StoreBot.me
wow everyone! the main group for werewolfplay @werewolfgame has hit 4k members! This is a tremendous accomplishment
Grey Wolf Development
wow everyone! the main group for werewolfplay @werewolfgame has hit 4k members! This is a tremendous accomplishment
On that note, we are currently working on removing inactive members. The limit for supergroups is 5K.
For now everyone please refrain from using the /stats command for now. Thank you!
Hey everyone, theres a new inline bot that answers a lot of frequently asked questions, type @wwfaqbot and it will pop up a lot of different commonly asked questions you can get the quick answer for
Hey everyone, Para here. We are testing some new server stability stuffs, and need a little help.
We have a beta version of Werewolf Moderator up and running, and need a few groups to test it out.
Note:
- This is beta. While it will work, there may be times I need to do some CPU profiling on it, which means I'll have to "pause" the bot for a few minutes. When I do so, I'll broadcast a message to any groups playing a game to let you know
- Upside, there is no peak time!
- This is only temporary. I may leave it running for a few days, possibly even a couple weeks, not sure yet.
- Beta bot has no GIF support - it will only show the text
If you are an admin of your group (preferrably group owners!), and are interested, please swing by @werewolfsupport (the international / english group) and let us know
We have a beta version of Werewolf Moderator up and running, and need a few groups to test it out.
Note:
- This is beta. While it will work, there may be times I need to do some CPU profiling on it, which means I'll have to "pause" the bot for a few minutes. When I do so, I'll broadcast a message to any groups playing a game to let you know
- Upside, there is no peak time!
- This is only temporary. I may leave it running for a few days, possibly even a couple weeks, not sure yet.
- Beta bot has no GIF support - it will only show the text
If you are an admin of your group (preferrably group owners!), and are interested, please swing by @werewolfsupport (the international / english group) and let us know
Few updates:
Upon joining, if you haven't started the bot, you will now get a nice easy button to press. Should simplify things. If the game starts and you still haven't registered with the bot, you will be forced to "flee" the game.
Admins - if a player with no username leaves the chat mid game, you can still /smite them by using their userid. Just forward a message from them to @userinfobot and it will give you the id. then run
If you have Enforcer in your group: simply reply to the user with /id and Enforcer will tell you the id (that's @werewolfbutlerbot)
If the bot detects that the player has left the group, they will flee the game automatically as well. This doesn't work well in large groups due to the user left message not always being sent.
Guardian Angel can no longer save a lover from suicide - they will remain dead.
Upon joining, if you haven't started the bot, you will now get a nice easy button to press. Should simplify things. If the game starts and you still haven't registered with the bot, you will be forced to "flee" the game.
Admins - if a player with no username leaves the chat mid game, you can still /smite them by using their userid. Just forward a message from them to @userinfobot and it will give you the id. then run
/smite 000000000 (replace the 0's with the user id)If you have Enforcer in your group: simply reply to the user with /id and Enforcer will tell you the id (that's @werewolfbutlerbot)
If the bot detects that the player has left the group, they will flee the game automatically as well. This doesn't work well in large groups due to the user left message not always being sent.
Guardian Angel can no longer save a lover from suicide - they will remain dead.
Update for admins:
If you /setlink on your group, and it's now in the /grouplist, you can remove it by using /remlink in your group
If you /setlink on your group, and it's now in the /grouplist, you can remove it by using /remlink in your group
Just to let everyone know, @werewolfbot is currently being worked on. @werewolfIIbot is online.
@werewolfbot has been beta testing some new features of the Telegram Bot API (we are working directly with Telegram on this), and it appears there was a bug this morning. It is being fixed as we speak, please hold tight :)
@werewolfbot has been beta testing some new features of the Telegram Bot API (we are working directly with Telegram on this), and it appears there was a bug this morning. It is being fixed as we speak, please hold tight :)
Hi everyone. Just like yesterday @werewolfbot is offline due to some testing we are doing with Telegram. Please use @werewolfiibot until further notice. Thank you for your understanding.