This is a bug!
Please report the problem with "!<feedback>" command :)

in other words if you saw that when someone joined your group contact support

All the bots will now reply to / commands normally.

We will continue to support ! commands

A FRIENDLY REMINDER TO ALL WW PLAYERS:

A few people are getting banned for flooding the bot. Let me explain a few things here:

Spamming a command is not some kind of magic. Hitting a command 40 times will not make anything magical happen. It's like the button on an elevator - pressing it multiple times is not a secret passcode or anything.

The spam detection is actually quite lenient. If you hit it, you were seriously spamming it. The bot also warns you before it bans you.

Here's the bigger reason why this happens though -
Everytime you hit a command, it's meant to get a response from the bot. Each time the bot has to send a command, it counts towards the API limit. So spamming a command reaches the bot towards API limits, and lags the bot for EVERYONE. This is why we are very strict about spamming the bot - if you do it enough for the bot to auto-ban you, that's on you. You were given a warning and continued to spam the bot.

For those that haven't seen the news yet, @werewolfbot was entered into a contest awhile back. Telegram announced earlier today the first set of winners, and @werewolfbot was selected!
Thank you to all of the players and the community that really made this game what it is today! We still have more new features planned of course, so stay tuned :)
https://telegram.org/blog/botprize1

Current issue with creating balanced game has been (hopefully) fixed.

Those getting the Sunday Bloody Sunday achievement, this is a bug, it will be removed

We saw that people were having problems with inserting bot commands without sending them.

You can use tab on desktop to complete the command without sending it.

We are currently testing a new @admin system. Please hold one while we work out a few bugs

The new @admin system is finished. Thank you to everyone for there patience.

The buttons do the action on the forwarded message. The group will be notified of the action.

@werewolfbutlerbot has hit its API limit. We will be sorting this out today

This is what it looked like when I solved the problem.

Time to recieve ping message: 00:07
Average Messages per second in: 361.66666666667
Messages recieved in the last minute: 21700

We seem to of sorted the problem out. Thank you for everyone's patience

The @admin system has been disabled for now. It needs a redesign because it is slowing the bot down a lot

Werewolf Enforcer is back.

The new flagged system is back

Most of the latest Enforcer as been restored. If you discover a feature that is missing please contact @werewolfsupport so that we can bring it back

For anyone who is wondering what happened to Enforcer today. The server decided to kill itself meaning it wouldnt start the bot, nor would it allow the bot to run at full speed when it did start it. I had to revert back to snapshot (like a save) that was from july and then rebuild from there which is why it took so long. Everything seems perfect now though and all updates made between july and now appear to be restored, if you find a missing one please contact support.

Thank you for everyones understanding

Whoever has added @werewolfbot or @werewolfIIbot to a channel (not a group, a CHANNEL) - please remove it.

All bots are back online. There was an update to the bot api dealing with how bots receive messages from channels. We had to modify the code to handle these new update types. Though really, I have no idea why werewolf would be in a channel....

Problem with Lynch voting has been found and patched. Deploying new code shortly.

It's amazing how much a single missing ? can break things