Grey Wolf Development
Ir al canal en Telegram
Channel for developer updates / notices on what's going on with our bots. Support: @greywolfsupport.
Mostrar más📈 Análisis del canal de Telegram Grey Wolf Development
El canal Grey Wolf Development (@greywolfdev) en el segmento lingüístico de Inglés es un actor destacado. Actualmente la comunidad reúne a 11 732 suscriptores, ocupando la posición 7 605 en la categoría Juegos y el puesto 1 111 en la región Internacional.
📊 Métricas de audiencia y dinámica
Desde su creación el невідомо, el proyecto ha mostrado un crecimiento acelerado, reuniendo a 11 732 suscriptores.
Según los últimos datos del 08 noviembre, 2026, el canal mantiene una actividad estable. En los últimos 30 días la variación de miembros fue de -113, y en las últimas 24 horas de -3, conservando un alto alcance.
- Estado de verificación: No verificado
- Tasa de interacción (ER): El promedio de interacción de la audiencia es 17.96%. Durante las primeras 24 horas tras publicar, el contenido suele obtener N/A% de reacciones respecto al total de suscriptores.
- Alcance de las publicaciones: Cada publicación recibe en promedio 2 107 visualizaciones. En el primer día suele acumular 0 visualizaciones.
- Reacciones e interacción: La audiencia responde de forma activa: el promedio de reacciones por publicación es 17.
- Intereses temáticos: El contenido se centra en temas clave como donation, developer, executrix, hunter, achievement.
📝 Descripción y política de contenido
El autor describe el recurso como un espacio para expresar opiniones subjetivas:
“Channel for developer updates / notices on what's going on with our bots.
Support: @greywolfsupport.”
Gracias a la alta frecuencia de actualizaciones (últimos datos recibidos el 09 noviembre, 2026), el canal mantiene la vigencia y un amplio alcance. La analítica demuestra que la audiencia interactúa activamente con el contenido, lo que lo convierte en un punto de referencia dentro de la categoría Juegos.
11 732
Suscriptores
-324 horas
-147 días
-11330 días
Archivo de publicaciones
11 729
![[Executrix: Support for new Spoiler entities] As of the new telegram update, you can now use a new type of entity, spoilers,](https://cdn.tlmtr.io/_next/static/media/empty-channel.35ed232f.svg)
[Executrix: Support for new Spoiler entities]
As of the new telegram update, you can now use a new type of entity, spoilers, in your messages. Now that the bot api was updated as well, Trixy supports these out of the box. You can use
<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 :)11 729
Bots should be back online now, sorry for the wait, we had some major server issues. Happy wuffing!
11 729
[Known Issues]
Hey everyone, since Telegram's 64-Bit-ID Update which broke this and that, most issues are fixed now. However, there remain a few issues which I want to list here, so you all are aware.
Werewolf: 🐺
- [RESOLVED ✅] Custom GIFs:
While displaying custom GIFs is working again on both bots, the code that downloads the GIFs to our server appears not working. In consequence, the beta bot currently doesn't display your GIFs if you changed them after the update. We're investigating how to fix this.
- Getstatus
The
/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!11 729
[Website / Stats]
The website has been fixed, and the
/stats command will now work again.
Happy Wuffing!11 729
[Patches]
Main bot should now show captions for gifs
Inline stats is fixed
That stupid Int32 error is gone
/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 patches11 729
[Christmas Event!] ❄️
Even though the bots are still a bit dizzy, we're starting this year's christmas event!
Come to our official Main and Vets groups to check it out :) 🎅🐺
11 729
[Bots back]
After a while of being unstable, the werewolf bots appear to be working now after a lot of messing with the code!
Please note: If you have a custom GIF pack, you will currently not be able to change your GIFs. We will fix that as soon as we can. Also, if you encounter any bugs or unusual behavior, please stop by @werewolfsupport. Happy Wuffing! 🐺
11 729
[Downtime over]
Hey everyone, the bots have come back to life! Enjoy playing and nomming your friends again (are you hungry already?) 🐺
11 729
[Bots back!]
The server is back up and the bots are running again!
Happy wuffing! 🐺
11 729
[Bots Down]
Hey everyone, we are aware that all our bots are down at the time being.
We suspect that this is our server provider's fault, its own website was down right now as well.
Maybe it's already coming back, we are trying to bring the bots back to you! We will let you know when anything happens!
11 729
[Executrix: Welcome Bug]
Not sure if anybody noticed, but there has been a bug in Executrix that made it send a welcome message for people who were only being unbanned but not actually joining the group. Worry not: said bug is being fixed these seconds :)
Happy Wuffing!
11 729
[New Chat Member - Update]
Because Telegram stopped sending "User has joined the group (via invite link)" service messages in large groups, we had to change the way that Executrix detects new chat members to welcome them. Welcome messages should now work perfectly fine in groups of all sizes. However, note the following changes:
- The welcome message is no longer sent in reply to telegram's service message, even if present.
- Telegram's service message is no longer deleted if "DeleteSpamWelcomes" is enabled and a user joins and instantly leaves. Enabled "DeleteSpamWelcomes" will still stop Executrix from sending a welcome message for such spam joins, though.
- Executrix being a group administrator is now mandatory for it to send welcome messages.
Have a great day! :)
11 729
[Status Update]
We will inform you about the current status in this posting.
[12:48 UTC]
Executrix is down for the time being. We are changing the database model.
[13:32 UTC]
Making final needed changes to the code...
[16:03 UTC]
Seems completed!
11 729
[Bot API Update]
Since the number of users joining telegram has become insane, the Bot API has announced that user IDs will soon exceed the magical number
2147483647 - 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 :)11 729
[Server Reboot]
Server reboot has been completed, bots should be happy now. Enjoy snacking on your neighbors tonight!
11 729
[Ugh....]
The reboot somehow failed.
All that is to be seen on the server currently is this text. No moving icon, nothing else. The bots can't be started again currently.
And since sleep is a thing even among admins and developers, you can probably expect some hours of downtime now... Sorry.
11 729
[Server Reboot]
Due to the recurring issues which our bots currently face, we are going to restart the server. For this reason you can't start games now. In about 30 minutes, we will terminate all running games and reboot the server. Afterwards, you can hopefully continue lynching each other peacefully :)
11 729
Hey everyone, we have noticed that our bots are currently down. We are working on getting them back, sorry for the inconvenience. We will of course let you know when you can start wuffing again! 🐺
In the meantime, please refrain from flooding messages / commands to the bots :)
