Grey Wolf Development
Open in Telegram
Channel for developer updates / notices on what's going on with our bots. Support: @greywolfsupport.
Show more📈 Analytical overview of Telegram channel Grey Wolf Development
Channel Grey Wolf Development (@greywolfdev) in the English language segment is an active participant. Currently, the community unites 11 727 subscribers, ranking 7 599 in the Games category and 1 120 in the International region.
📊 Audience metrics and dynamics
Since its creation on невідомо, the project has demonstrated rapid growth, gathering an audience of 11 727 subscribers.
According to the latest data from 10 November, 2026, the channel demonstrates stable activity. Although there has been a change in the number of participants by -120 over the last 30 days and by -2 over the last 24 hours, overall reach remains high.
- Verification status: Not verified
- Engagement rate (ER): The average audience engagement rate is 18.80%. Within the first 24 hours after publication, content typically collects N/A% reactions from the total number of subscribers.
- Post reach: On average, each post receives 2 205 views. Within the first day, a publication typically gains 0 views.
- Reactions and interaction: The audience actively supports content: the average number of reactions per post is 17.
- Thematic interests: Content is focused on key topics such as donation, developer, executrix, hunter, achievement.
📝 Description and content policy
The author describes the resource as a platform for expressing subjective opinions:
“Channel for developer updates / notices on what's going on with our bots.
Support: @greywolfsupport.”
Thanks to the high frequency of updates (latest data received on 11 November, 2026), the channel maintains relevance and a high level of publication reach. Analytics show that the audience actively interacts with content, making it an important point of influence in the Games category.
11 727
Subscribers
-224 hours
-207 days
-12030 days
Posts Archive
11 727
[Enforcer Update]
* Can now delete the forwarded message that was sent with @admin
* Fixed the issue setting welcomes
11 727
[Werewolf reminder]
Another thing I've heard from lots of players is that they don't know if they successfully joined the game, or that they don't appear on the player list as soon as they click the Start button, and so they think they have not joined and click the Join button again.
It is way simpler than that. When you click the Start button, if the bot says that you successfully joined, you successfully joined. Period. Please don't click the Join button again if you received the confirmation message from the bot: that is just being spammy.
The player list does not update too often, and sometimes fails to update, that's why you might not see your name on it. Anyway, that is not the way you see if you joined - again, if the bot tells you, it is right.
PS: The bot will now notify the group every 30 seconds with the name of the new players - but again, this is not for confirmation! Rather, it tells everyone else who is taking part to the game.
TL;DR: If you receive the "You successfully joined" message, you have joined. Don't try to join again
11 727
[Werewolf reminder]
Another little reminder. Ask your group's admin to set the link of the group (e.g.
/setlink@werewolfbot https://t.me/joinchat/AAAAAD1l2naRUp0HvOwBhA). This way the bot will know the link of your group, and, among the other advantages, the joining message will contain a link, so you can go back easily to the group chat after having joined.
Also, if you don't want to scroll up to find a join button, you can use /join to make one.11 727
[Werewolf]
You can now stop waiting by clicking a button which will appear under the bot's response to /nextgame. The command /stopwaiting is still working anyway.
11 727
[Werewolf]
As someone suggested, a new command /stopwaiting has been added to remove you from the waitlist. This way, if you ran /nextgame, you won't be notified anymore.
You can use it in the same group where you ran /nextgame, or in PM with the bot specifying link, id, or username of the group.
Examples:
/stopwaiting -1001077134233
/stopwaiting
https://t.me/joinchat/AAAAAD1l2naRUp0HvOwBhA
/stopwaiting @username11 727
[Werewolf]
The issue with new groups seems to be fixed. If you find any other error, go to @werewolfsupport. Happy wuffing!
11 727
We can't let @telegram have ALL the glory! Werewolf 4.2 has been released! NEW MODE! Read about the updates here: https://t.co/mHJ2JjQOkz
http://twitter.com/greywolfdev/status/865379045273481217
11 727
.... something... something is happening behind the curtains... what is that???!?
11 727
This project is proving harder than I expected to get working the way I want it to work. It might be a few more weeks before I can bring it back online.
FYI: I am trying to get it to a point where the bot does not need to be in the group for months to function, ideally you should just be able to add it, give it admin and send it a command.
11 727
[Werewolf]
Just a little reminder, as I noticed that 2/3 of the games are still Chaos.
If you play always Chaos games, and you ever thought "I could never win this game! The enemies were too strong", or vice versa "This game was too easy to win", then you might want to give normal games a try.
The old system where the roles appeared only after x people joined was completely removed quite a bit ago. Instead, now normal games are balanced, so that it is (more or less) equally likely for any team to win.
PS: No, we're not dead, a lot of new features are coming! Stay tuned 😉
11 727
[Supercleanupbot Alpha]
Please note supercleanupbot is still in alpha so please be patient while we work out the bugs, it is far from finished
11 727
[Supercleanupbot]
For everyone who missed it @supercleanupbot is back online rewritten in c#, it is currently catching up the last few months of messages.
It will now be scalable across many many groups.
11 727
[Werewolf]
Just to let everyone know, we are currently experimenting with various "join" methods, in an effort to reduce group spam and load on the bot. For those using Beta, please just hang tight with us while we simplify this and make it better. We have been watching the beta groups (somewhat quietly) to gauge reactions and usability, then making further adjustments.
Once everything is good, easy, etc, we will release to production (@werewolfbot)
11 727
If you were one of the original nsfw image detection system users, the like 5 or 10 of you i personally let use it, you are going to need to add your clientID and clientSecret again as well using /setnsfw for the service to continue to function
11 727
Yeah so i dun made a bit of a goof and forgot to push the settings to everyones groups for nsfw image detection so it just didnt think it was turned on.
That has since been fixed and the system works as designed. Enjoy automatically banning porn spammers
11 727
[NFSW Image detection release]
So nsfw image detection is now live on @enforcerbot. It uses computer vision to look at the content of images posted in the group and bans/kicks the user automatically. The action is logged in the log channel so if you havent set one of those up yet then you should.
The bot will soon be able to delete the image as well.
Please look at our set up guide for nsfw image detection here: http://telegra.ph/Enforcer-NSFW-Image-Detection-Guide-05-15
The system in its current state has not been throughly tested so if it does not work for you please contact our support group with /support
11 727
[Enforcer update 15 May 2017]
- Warning by Username or ID with reason behind now working.
- Log channel messages now show the exact text of the admin's message and the user who the admin replied to.
- Elevate and Deelevate commands will now be logged as well
- Some small bugfixes
—--@Enforcedbot---—
I have introduced nsfw image detection using computer vision to enforced bot. It will soon make its way to @enforcerbot. In a couple of hours/days. Stay tuned for when it comes.
You can access its settings in /menu -> nsfw detection
To see how to set it up look at: http://telegra.ph/Enforcer-NSFW-Image-Detection-Guide-05-15
11 727
If anyone is wondering what exactly we are patching against it is this:
https://en.wikipedia.org/wiki/WannaCry_ransomware_attack
