Telegram RegisterThe public register of Telegram

Channel

Ирландский Лесоруб в Геймдеве

@Vaniagramming

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

451subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002052525268
TypeChannel
Username@Vaniagramming
DescriptionМеня зовут Иван (@JazzyJohn), 10 лет работаю в игровой индустрии. Я старший с++ геймплей программист. Это мой маленький канал о геймдеве и программировании.
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/Vaniagramming

Growth

4517 Aug 2026, 17:26 — 451 subscribers8 Aug 2026, 05:01 — 451 subscribers7 Aug 2026, 17:268 Aug 2026, 05:01
2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 450–452 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 05:01451no change
7 Aug 2026, 17:26451first reading

Engagement

15 posts held, back to 19 February 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 15 posts for this entry, the most recent from 12 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
57
Videos
6
Links
108

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

171 reactions across 15 posts, in 10 distinct kinds. The most used accounts for 29.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍5129.8%
🔥3922.8%
custom 54115807319294117682615.2%
👀2514.6%
105.85%
❤‍🔥95.26%
42.34%
💯31.75%
🗿31.75%
🫡10.585%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it isTelegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 15 of the 15 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 171reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 15 most recent posts we hold, published 19 February 2026 to 12 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

12 Jul 2026, 14:22 UTC140 views7 reactionsread 8 August 2026
Forwarded from @alphynariumPhoto

чтение на сегодня: ситуация в MTG, где у обоих игроков бесконечное комбо, и кто победит, зависит от того, верна ли гипотеза о существовании бесконечного количества чисел-близнецов (пар простых чисел, отличающихся на 2). и с одной стороны, да, эта гипотеза доказана «многим кажется что правдива» (но не доказана), так что теоретическая победа могла бы быть за Элис. но с другой, если Боб придумает действительно большое

👍3custom 54115807319294117683👀1

17 Jun 2026, 14:47 UTC498 views7 reactionsread 8 August 2026

И вдогонку релиз Unreal Engine 5.8. В новой версии мы получили: новый экспериментальный меш для ландшафта, новый экспериментальный редактор растений, куча улучшений для анимации и Control Rig (в частности экспериментальная возможность контролировать поверхность скелетал меша и анимировать её), плагин для внедрения LLM и куча всего еще. Как всегда ждем пары патчей, прежде чем внедрять в свои проекты

👍3custom 54115807319294117683🔥1

17 Jun 2026, 14:21 UTC216 views4 reactionsread 8 August 2026

Смотрим State of Unreal. Обещают оптимизацию, и много нового📱

👀1👍1🔥1🫡1

26 May 2026, 18:22 UTC326 views7 reactionsread 8 August 2026
Forwarded from @t3dpesecPhoto

ПОЕХАЛИ! Сидим в режиме общения думаем про ИИ. Обсуждаем с точки зрения 3Дэ, геймдизайна, программирования и т.п. Гости Иван - мега-программист и Жека просто крутой чел... узнаете на стриме. Смотреть тут live.vkvideo.ru/3dpesec www.youtube.com/@3Dpesec www.twitch.tv/3dpesec kick.com/3dpesec Лайк. Подписка. Репост.

👍4👀21

13 May 2026, 06:47 UTC412 views8 reactionsread 8 August 2026

Вышло превью Unreal Engine 5.8. Из интересного: улучшение производительности Lumen, еще больше улучшений для PCG, и основная фича Mesh Terrain. Полную roadmap смотрим тут

👍6custom 54115807319294117682

12 May 2026, 06:55 UTC715 views20 reactionsread 8 August 2026

На днях коллега попросил меня сделать ему экскурс по анимационной системе Unreal. Я решил записать небольшую заметку из того, что ему рассказал. Теперь делюсь ею с вами.

❤‍🔥95👍4👀2

9 May 2026, 06:01 UTC380 views18 reactionsread 8 August 2026

С праздником Победы! Никто не забыт и ничто не забыто!

🔥12💯3🗿3

21 Apr 2026, 12:41 UTC705 views9 reactionsread 8 August 2026

Havok navigation для Unreal Engine. Интересная альтернатива базовой навигации Unreal для крупных студий, ибо цена в 50к$ за игру, отсекает сразу всё инди. Хотя возможно скоро увидим некие изменения в ценовой политики. А пока можно только с интересом наблюдать и завидовать быстрой много-поточной навигации по стенам 👀

👀5👍4

7 Apr 2026, 08:13 UTC498 views17 reactionsread 8 August 2026

Я достаточно оптимистичен по поводу ИИ в разработке и в геймдеве. Я делился с вами опытом кодинга с помощью ИИ и часто пользуюсь ИИ в разных частях разработки. Но иногда полезно взглянуть на прогресс с другого, немного депрессивного угла. Хочу поделиться с вами эссе про влияние ИИ на инновации🚀

🔥8custom 54115807319294117686👍3

30 Mar 2026, 05:43 UTC≈1,020 views19 reactionsread 8 August 2026

Делюсь с Вами огромной библиотекой ресурсов для геймдева. В ней куча всего полезного: от гайдов и ассетов до полноценных движков и исходников игр. Определенно пригодится разработчику любого уровня и проекта!

👍9🔥6custom 54115807319294117684

24 Mar 2026, 07:56 UTC721 views12 reactionsread 8 August 2026

Продолжаю рассказывать как устроено StateTree в UnrealEngine. В этот раз рассмотрим технические тонкости передачи данных между частями дерева.

🔥6custom 54115807319294117684👍2

10 Mar 2026, 09:28 UTC761 views12 reactionsread 8 August 2026

Хочу поделиться докладом от разработчиков игры 2025 года Clair Obscur: Expedition 33. Sandfall Interactive рассказывает как покоряли Unreal, как использовали блюпринты и много чего интересного.

👀7🔥3custom 54115807319294117682

Showing the 12 most recent of 15 posts we hold for @Vaniagramming. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 8 August 2026 — this entry's latest reading, not the date you are reading this.

“Ирландский Лесоруб в Геймдеве” (@Vaniagramming), 451 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Vaniagramming.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.