2 measurements spanning 4 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 14–16 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
11 Aug 2026, 23:45
15
no change
7 Aug 2026, 21:12
15
first reading
Engagement
20 posts held, back to 11 August 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 20 posts for this entry, the most recent from 4 September 2022. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Photos
7
Videos
1
Links
3
Lifetime counters from Telegram’s own channel header, read 11 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
41s
Average length
41s
Measured directly from 1 video 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
66 reactions across 13 posts, in 5 distinct kinds. The most used accounts for 71.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
47
71.2%
👍
14
21.2%
🤬
3
4.55%
❤
1
1.52%
👎
1
1.52%
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 13 of the 20 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 66 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 11 August 2022 to 4 September 2022, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
те, кто сидит в чате, наверное, знают, что я в августе ушел и заморозил разработку этой игры по некоторым причинам, в которые входила нехватка времени.
сейчас времени не хватает для полноценной разработки большого проекта, но хватает для неспешной разработки без особого вклада в пиар, поэтому я начинаю новый проект, подробнее про него сейчас напишу в t.me/heavyDrift
делал генерацию карты, начал с платформ, и как всегда, все сработало с первого раза...
зато проверил, какой фпс выдает при тысяче светящихся объектов, фпс адекватный(1000 fps)
импортировал ветки в движок, накидал их, сделал им свечение, сделал их подбор, реализовал высвечивание их количества, безопасное(то есть сделал античит на изменение дерева) хранение значения дерева на устройстве, сделал вечное удаление веток после сбора(после перезахода в игру или смерти ветки не появятся заново)
оценку свечения дерева и реализации вышеперечисленного в чат
так будет высвечиваться количество дерева(в правом верхнем углу, количество камня будет высвечиваться аналогично, только чуть левее панелька будет)
и так нормально или что-нить уменьшить/увеличить/шрифт поменять/переставить?
под прошлым постом вы набрали 10 🔥 и я, как и обещал, выкладываю первую альфу игры
сейчас там сделаны только механики из платформера, полный список того, что будет сделано в следующих версиях можно почитать в t.me/gamedev_channel/5
оценку передвижения и реализации механик платформера в чат
сделал:
1)настройки
2)сохранение выбора настроек в память устройства(даже если приложение удалить и снова установить, настройки останутся)
3)прыжок кнопкой
4)прыжок джойстиком
5)прилипание к стенам(на видосе забыл показать, но если к краю стены в прыжке прислониться, то можно будет зависнуть в воздухе, эту фичу логично будет использовать при сражении с мобами ближнего боя, имея оружия дальнего боя)
5)оптимизировал св…
сделал анимацию ходьбы
в чат оценку и совет быстрее или медленнее сделать
🔥3
Showing the 12 most recent of 20 posts we hold for @gamedev_channel. 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.
Polls
The 3 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 11 August 2022 to 4 September 2022. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
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 11 August 2026 — this
entry's latest reading, not the date you are reading this.
“💊GAMEDEV💊” (@gamedev_channel), 15 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/gamedev_channel.
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.