Telegram RegisterThe public register of Telegram

Channel

GameDev HACK

@GameDevHACK

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

89subscribers

+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-1001508694754
TypeChannel
Username@GameDevHACK
DescriptionHACK — Helpful Advice, Code & Knowledge Blog by a developer sharing advice and coding tips to help you create better games. Уютный бложик в виде записок разработчика @AnikoV. Полезные советы, код и знания.
CreatedBetween 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
On Telegramt.me/GameDevHACK

Growth

897 August 2026 — 89 subscribers9 August 2026 — 89 subscribers7 August 20269 August 2026
2 measurements spanning 2 days. 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 88–90 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 14:4889no change
7 Aug 2026, 17:2289first reading

Engagement

15 posts held, back to 24 October 2025the 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 16 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
28
Videos
14
Links
99

Lifetime counters from Telegram’s own channel header, read 9 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.

Video runtime
2m 10s
Average length
1m 05s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

30 reactions across 12 posts, in 7 distinct kinds. The most used accounts for 43.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1343.3%
🤝516.7%
🫡413.3%
👍310.0%
26.67%
🤔26.67%
👎13.33%

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 12 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 30reactions 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 24 October 2025 to 16 June 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

16 Jun 2026, 13:22 UTC50 views2 reactionsread 9 August 2026
Forwarded from @NorlinGames

Реверс-инжиниринг Силксонг https://www.youtube.com/watch?v=eC9bIelizlw #gamedev #silksong #research

👎1🤔1

18 Mar 2026, 20:01 UTC131 views1 reactionsread 9 August 2026
Photo

best practices for character navigation architecting for ААА performance and robustness Неплохой обзорный доклад лучших практик для навигации персонажей с GDC 2026 от Tech lead, Havok Navigation Ben Sunshine-Hill #AI #navigation

🤝1

17 Mar 2026, 19:14 UTC109 views1 reactionsread 9 August 2026

https://gamedev.center/run-unity-tests-faster-dotnet/

1

9 Mar 2026, 19:04 UTC116 views3 reactionsread 9 August 2026

Procedural Grass в Ghost of Tsushima Здесь трава — это не набор расставленных мешей. По сути это GPU-driven procedural pipeline, который генерирует, фильтрует и рендерит растительность почти полностью на стороне GPU. Цели у системы довольно практичные: • минимальная нагрузка на CPU • масштабируемость для большого open world • высокая визуальная плотность • правдоподобное поведение на ветру 😡Procedural placement

1🔥1🤝1

4 Feb 2026, 20:34 UTC141 views2 reactionsread 9 August 2026

Вы когда Unity запускаете на исполнение, GameView ставьте на конкретное разрешение, а то кто его знает, сколько пикселей будет, когда вы ставите на Aspect. Часто бывает так что GameView с FullHD достаточно по визуалу и по производительности сильно лучше.

🤝2

4 Feb 2026, 17:47 UTC142 views5 reactionsread 9 August 2026
Video

Алгоритм Грэхема — алгоритм построения выпуклой оболочки в двумерном пространстве. В этом алгоритме задача о выпуклой оболочке решается с помощью стека, сформированного из точек-кандидатов. Все точки входного множества заносятся в стек, а потом точки, не являющиеся вершинами выпуклой оболочки, со временем удаляются из него. По завершении работы алгоритма в стеке остаются только вершины оболочки в порядке их обхода пр

🔥4🤔1

30 Jan 2026, 07:22 UTC202 views3 reactionsread 9 August 2026
Photo

Хочу Вам поподробнее рассказать про разработчика Бобби из предыдущего поста. Бобби многое повидал: занимался AI ещё в 2008 году, когда это ещё не было мейнстримом, а я ещё в школу под стол ходил. Так вот у этого мужика есть отличный набор стримов, где сосредоточена такая крутая кристаллизованная выжимка информации об архитектуре, которая, явно видно, прошла огонь, воду и медные трубы. Считаю это одними из лучших "до

👍3

22 Jan 2026, 07:55 UTC158 views4 reactionsread 9 August 2026
Photo

Когда-то около 8 лет назад я пристально следил за блогом разработки компании CampoSanto - разработчиков прекрасной Firewatch . По их проекту было много интересных докладов на GDC. Там явно собралась в то время очень талантливая команда из около 10 человек. - Аниматор James Benson (youtube, x.com), который делал также анимации и для серии игр Ori. - Matthew Wilde - vfx разработчик (https://x.com/skilful) уже автор ш

🔥3🤝1

20 Dec 2025, 14:05 UTC162 viewsread 9 August 2026
Video

Несколько видео с выдержками из "чистого кода", которые, в том числе, визуально показывают их влияние на общую работу в команде. Мне кажется, это всё про сокращение "времени координации" при обсуждениях и чтении кода и сокращение размера изменений в PR/MR. Я не приверженец безукоризненно соблюдать всё, что написано в "чистом коде", но многие вещи оттуда реально работают и проверены временем и работой в разного раз

Showing the 12 most recent of 15 posts we hold for @GameDevHACK. 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.

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 9 August 2026 — this entry's latest reading, not the date you are reading this.

“GameDev HACK” (@GameDevHACK), 89 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/GameDevHACK.

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.