请前往Patreon获取游戏本体。
❤5

Channel
@ddbhanhua
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
20,919subscribers
+1,317 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002576828752 |
|---|---|
| Type | Channel |
| Username | @ddbhanhua |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/ddbhanhua |
Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 95% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 07:18 | 20,919 | +76 |
| 16 Sept 2026, 03:01 | 20,843 | +41 |
| 14 Sept 2026, 10:18 | 20,802 | +37 |
| 12 Sept 2026, 19:40 | 20,765 | +45 |
| 10 Sept 2026, 19:42 | 20,720 | +55 |
| 7 Sept 2026, 16:19 | 20,665 | +102 |
| 4 Sept 2026, 17:41 | 20,563 | +63 |
| 2 Sept 2026, 23:55 | 20,500 | +18 |
| 1 Sept 2026, 21:54 | 20,482 | +22 |
| 1 Sept 2026, 00:55 | 20,460 | +27 |
| 31 Aug 2026, 01:52 | 20,433 | +19 |
| 30 Aug 2026, 03:08 | 20,414 | +38 |
| 29 Aug 2026, 01:48 | 20,376 | +17 |
| 28 Aug 2026, 04:34 | 20,359 | +29 |
| 27 Aug 2026, 03:34 | 20,330 | +21 |
| 26 Aug 2026, 00:44 | 20,309 | +29 |
| 25 Aug 2026, 01:42 | 20,280 | +34 |
| 23 Aug 2026, 16:49 | 20,246 | +65 |
| 22 Aug 2026, 02:08 | 20,181 | +30 |
| 20 Aug 2026, 22:11 | 20,151 | first reading |
113 posts held, back to 4 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 57 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 22 of 28 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 113 (4 August 2026 – 2 September 2026) |
| Views total | 125,120 |
| Reactions total | 119 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 00:16 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
677 reactions across 74 posts, in 5 distinct kinds. The most used accounts for 89.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 605 | 89.4% | |
| 🥰 | 40 | 5.91% | |
| 👍 | 18 | 2.66% | |
| 💯 | 13 | 1.92% | |
| 🔥 | 1 | 0.148% |
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 83 of the 113 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 677 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 113 most recent posts we hold, published 4 August 2026 to 2 September 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.
请前往Patreon获取游戏本体。
❤5
Surviving Purge demo 0.6.2.376 游戏:生存净化号 作者:Grizzly Gamer Studio X,Bsky 链接:itch,Patreon 历史版本:0.5.3 游戏更新0.6现已在Patreon上线! 嘿,性感的灰熊们! 0.6版本现已在此发布: 更新内容 第三幕的开场和四章 4个附加关卡 技能树,现已在秘密基地开放 14个新单位待解锁 战斗中的新单位进化系统 格拉迪奥和格鲁克的亲和对话,以及他们的技能 7个全新热门场景待解锁 现在队伍中有角色会在战斗中获得被动加成(光环) 像Robin Morningwood那样的云保存系统 游戏经过了大幅度的平衡调整 ☺️ 很快见!☺️ The Grizzly Team #SurvivingPurge #GrizzlyGamerStudio
❤7
1、切换语言 正确安装补丁后自动切换。 2、游戏篇幅(字数) 英文单词4.2w+,中文6.8w+。 3、逼逼叨叨 生存净化号 0.6.2.376版本。本次的更新内容还是很丰富的。游戏方面,新关卡,新技能术,新单位,紫卡也来了。剧情方面,新的牛头人区域解锁。牛头人区的东方奇幻风格还是很对胃口的。另外,怎么金角银角大王也来了。 翻译方面。由于单位数量的增多,原PVZ式译名已经很难准确的描述新单位了,所以现在各单位名称改回了原本的名字。虽然使用0.6.2版本测试,但我猜测补丁依然适用于新版本。这点需要验证一下。
❤3
补丁使用方法: 1、解压,得到 chinese.json 文件 2、游戏开始后 选择OPTIONS(设置)、点击 LANGAGE右侧的+号、 在文件选择窗口中选择 chinese.json 文件 按下 SELECT 按钮
❤3
File, posted without a caption
❤5
如果喜欢,请去itch上下载游戏,以支持作者。
File, posted without a caption
❤7
Crave Flesh 5.0 <全性向,有BG内容(可快进)> 游戏:血肉之欲 作者:KausAustralis 链接:itch,Patreon 历史版本:1.0 第五章来了!大家好! 第五章现已发布!首先,非常感谢大家极大的耐心,同时我也为延期深表歉意。这一章需要很多精心打磨才能把氛围调到恰到好处,我真的希望你们觉得等待是值得的。 第五章讲的是什么? 在与玛维斯的激烈对峙之后,泽克、维戈和利奥醒来,发现自己被困在洞穴深处的黑暗中。他们必须一起奋力冲出地面,但有些不对劲——洞穴本身似乎执意要留住他们。准备好迎接一段以心理、幽闭恐怖为主的叙事吧,在那里生存不仅意味着对抗物理环境,还要直面他们内心的深处。 新功能:可拖拽和最小化的理智条。为了提升你在心理机制方面的体验,我更新了界面!现在你可以通过点击并拖拽,将理智条移动到屏幕上的任意位置。如果你觉得它碍眼,或者想要更干净的场景视野,可以用理智条正上方那个切换按钮把它最小化! …
❤7🔥1
1、切换语言 更新了选择语言方式,现在找到并点击DDB图标即可切换到中文。 2、游戏篇幅(字数) 英文单词9.2w+,中文16.7w+。 3、逼逼叨叨 血肉之欲 5.0版本。一下没注意,居然更了这么多版本。5.0版本更新到了第5章内容。感觉每个章节更偏单元剧,有不同的剧情配小游戏,体验非常丰富。还真挺像那么回事。有BG内容,跳过即可。喜欢胖胖的一定不要错过。
DDB汉化 202608合集 itch收藏夹,收录了本频道本月发布的所有作品。 方便大家回顾。每部游戏下配有汉化补丁链接。 非itch游戏仅收录补丁链接。 汉化补丁标注有游戏版本号,请注意游戏当前版本是否适配。 链接:DDB汉化 2026-08 #collections
🥰15❤1
File, posted without a caption
请前往itch获取游戏本体。
Showing the 12 most recent of 113 posts we hold for @ddbhanhua. 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.
@ddbhanhua edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“DDB汉化屋” (@ddbhanhua), 20,919 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/ddbhanhua.
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.