Grey Wolf Development
Channel for developer updates / notices on what's going on with our bots. Support: @greywolfsupport.
Больше📈 Аналитический обзор Telegram-канала Grey Wolf Development
Канал Grey Wolf Development (@greywolfdev) языкового сегмента Английский является активным участником. Сейчас сообщество объединяет 11 729 подписчиков, занимая 7 605 место в категории Игры и 1 111 место в регионе Международный.
📊 Показатели аудитории и динамика
С момента создания невідомо проект демонстрирует стремительный рост, собрав аудиторию из 11 729 подписчиков.
Согласно последним данным от 09 ноября, 2026, канал показывает стабильную активность. За последние 30 дней изменение числа участников составило -118, а за последние 24 часа — -5, при этом общий охват остаётся высоким.
- Статус верификации: Не верифицирован
- Уровень вовлечённости (ER): Средний показатель вовлечённости аудитории составляет 18.36%. В первые 24 часа после публикации контент обычно набирает N/A% реакций от общего числа подписчиков.
- Охват публикаций: В среднем каждый пост получает 2 154 просмотров. В течение первых суток публикация набирает 0 просмотров.
- Реакции и взаимодействия: Аудитория активно поддерживает контент: среднее количество реакций на один пост — 17.
- Тематические интересы: Контент сосредоточен на ключевых темах, таких как donation, developer, executrix, hunter, achievement.
📝 Описание и контентная политика
Автор описывает ресурс как площадку для выражения субъективного мнения:
“Channel for developer updates / notices on what's going on with our bots.
Support: @greywolfsupport.”
Благодаря высокой частоте обновлений (последние данные получены 10 ноября, 2026) канал поддерживает актуальность и высокий уровень охвата публикаций. Аналитика показывает, что аудитория активно взаимодействует с контентом, что делает его важной точкой влияния в категории Игры.
<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 :)/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.
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!/stats command will now work again.
Happy Wuffing!/nextgame command should properly notify now
/customgif uploading should work now
Various other minor bug fixes
If you were in a game already when this was deployed, you may have to wait until the next game to see the patches2147483647 - that being 2 to the power of 31 minus 1. Since our bots are written in C#, it means that we have to switch from int to long type for User IDs. This also requires operations on the database that can't be performed while the bot is running.
Long story short: We are trying to update Executrix to stay in accordance with the newest Bot API. Some information that is saved starting now may be lost, including user warns, elevations, etc. We will also have a downtime later. Better remember the warns, etc. and issue them later when the operation is completed.
We will of course let you know about the progress. Cheers :)