PSA:
Just to explain how things work a little bit. When the bot sends you a menu, the Telegram API returns a response with the message ID. I then store that message ID so I can later send the "Time's Up" message if I need to. Until I get the response from the Telegram server with the info I need to store, the question is not registered. So when you click the menu button and get the "q was null" error - it means the bot hasn't gotten the reply yet. Wait a couple seconds, and try again.
TL;DR: Please, do not hit your vote menu choice 15 times in a second. It's really not necessary, and isn't going to "magically" make anything work.
I saw comments in support about it's "fun to force the bot"..... you aren't forcing anything, it's not magic, you just have to let it do it's thing.
Just to explain how things work a little bit. When the bot sends you a menu, the Telegram API returns a response with the message ID. I then store that message ID so I can later send the "Time's Up" message if I need to. Until I get the response from the Telegram server with the info I need to store, the question is not registered. So when you click the menu button and get the "q was null" error - it means the bot hasn't gotten the reply yet. Wait a couple seconds, and try again.
TL;DR: Please, do not hit your vote menu choice 15 times in a second. It's really not necessary, and isn't going to "magically" make anything work.
I saw comments in support about it's "fun to force the bot"..... you aren't forcing anything, it's not magic, you just have to let it do it's thing.
Node Version 2.1.6008.20133
Patched a bug in fool
Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
Few other minor bug fixes
Last 2 players alive = lovers now correctly shows lovers end, rather than SK / Wolf win
Patched a bug in fool
Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
Few other minor bug fixes
Last 2 players alive = lovers now correctly shows lovers end, rather than SK / Wolf win
Node Version 2.1.6008.21455
If the game has cupid / DG / WC, the first night voting time will be extended to 120 seconds. This is to allow special roles extra time to make their choices (especially cupid). Subsequent nights after that will have the normal night voting time as configured by admins.
If the game has cupid / DG / WC, the first night voting time will be extended to 120 seconds. This is to allow special roles extra time to make their choices (especially cupid). Subsequent nights after that will have the normal night voting time as configured by admins.
Node version 2.1.6008.23895
Cupid can now choose themself as one of the lovers
(remember, use /version to check what version you are on. Updates will happen automatically next game if you are mid game)
Cupid can now choose themself as one of the lovers
(remember, use /version to check what version you are on. Updates will happen automatically next game if you are mid game)
Node 2.1.6008.25878
Fixed issue where cult attempting to convert hunter -> gets killed by hunter displays Cult Hunter message, not Hunter message.
Also, in same instance, Cult death will be sent to the group as well
Fixed issue where cult attempting to convert hunter -> gets killed by hunter displays Cult Hunter message, not Hunter message.
Also, in same instance, Cult death will be sent to the group as well
I've gotten requests about how to donate, as not everyone can use paypal. So, I have set up a Patreon account. If you'd like to support @werewolfbot / make a contribution towards an upgraded server, head over to https://www.patreon.com/werewolf
Update:
Control version 2.1.6009.23299
New command added!
/nextgame
Using this command, the bot will PM you next time someone starts a game in that group :)
Note - that's when someone STARTS a game, not when the current game has ended
Control version 2.1.6009.23299
New command added!
/nextgame
Using this command, the bot will PM you next time someone starts a game in that group :)
Note - that's when someone STARTS a game, not when the current game has ended
Update:
Control Version 2.1.6010.27874
Node Version 2.1.6010.28148
New game endings for SK + Hunter, SK + <anyone else>, and no one left alive
Fixed an issue where hunter survives a solo wolf attack, but it still told they were killed
Made a lot of changes to the backend. SQL usage and CPU usage have been lowered dramatically, which will result in less lag
Control Version 2.1.6010.27874
Node Version 2.1.6010.28148
New game endings for SK + Hunter, SK + <anyone else>, and no one left alive
Fixed an issue where hunter survives a solo wolf attack, but it still told they were killed
Made a lot of changes to the backend. SQL usage and CPU usage have been lowered dramatically, which will result in less lag
Update:
Node Version 2.1.6011.22599
Players lists are now sorted:
In vote menus (PM) players will be sorted by name
In /players, they will be sorted in the order they died
Node Version 2.1.6011.22599
Players lists are now sorted:
In vote menus (PM) players will be sorted by name
In /players, they will be sorted in the order they died
There currently appears to be a major issue going around Telegram where some users appear as "Unknown" to some, but normal to others. Because of this, the bot sees some people as "Unknown" and cannot PM you or even respond to you. There's is nothing I can do about this - this is on Telegram side. I apologize for the issues, but you will need to wait for Telegram to sort it out
There is a possible fix. If you cannot talk to the bot, please try changing your username (@name) - you can even set it to the same thing you were using before.
Update
Node Version 2.1.6011.26352
Player list sorting has been updated to put "Skip" back at the bottom, as it should be
Node Version 2.1.6011.26352
Player list sorting has been updated to put "Skip" back at the bottom, as it should be
If you enjoy playing Werewolf, please take a moment to rate us on the bot store!
P.S. I'm sorry Jubs, I can't give you your life back. I don't intend to shut down @werewolfbot ;)
https://storebot.me/bot/werewolfbot
P.S. I'm sorry Jubs, I can't give you your life back. I don't intend to shut down @werewolfbot ;)
https://storebot.me/bot/werewolfbot
One of our players, Ajax, has written a really cool short story / fan fiction, inspired by @werewolfbot. I really enjoyed it, give it a read!
https://goo.gl/eVGV95
https://goo.gl/eVGV95
Yeah, Right!
The Game is Afoot
It was pouring outside and the wind was howling menacingly. In the dark cover of the moonless night, the only radiance seemed to peek through the stained glass windows of the Church. Inside, the ca…
Node Version 2.1.6015.24387
Fixed a bug when DG becomes harlot, they are unable to get a response from visiting someone.
Consolidated functions for App Seer, DG, and Wild Child. This should solve issues like seer dead because lover -> App seer does not become seer
Also consolidated Hunter death function. If Hunter died, DG becomes hunter, hunter then shoots hunter... new hunter should get to shoot as well
use /version to find out what version you are on
Fixed a bug when DG becomes harlot, they are unable to get a response from visiting someone.
Consolidated functions for App Seer, DG, and Wild Child. This should solve issues like seer dead because lover -> App seer does not become seer
Also consolidated Hunter death function. If Hunter died, DG becomes hunter, hunter then shoots hunter... new hunter should get to shoot as well
use /version to find out what version you are on
In case anyone was curious ;)
Werewolf database now includes 52,731 players in 8,224 groups.
In the past month, there have been 264,285 games which resulted in 662,879 player kills, and 493,624 survivors
Werewolf database now includes 52,731 players in 8,224 groups.
In the past month, there have been 264,285 games which resulted in 662,879 player kills, and 493,624 survivors