VALORANT: - 修复游戏更新后Cypher技能不显示的问题 - 修复游戏更新后Cypher烟雾的可视检查失效问题 - 修复极少数用户遇到的自瞄扳机导致掉帧的问题 CS2: - 修复极少数用户遇到的自瞄扳机导致掉帧的问题 PS: 1. 对于有什么问题的用户,主动联系了几次都不配合排查并解决问题的话,就不要在群里天天叫,自己受着 2. 首先 没有人的瞄准会专门拐个弯去曲线瞄人,其次 你如果真想要自瞄轨迹在人手不介入时是一条曲线 是可以调参数实现的,但选项名称不叫曲线,不要问我怎么调 3. 不允许不通过pup-loader启动软件,出现什么问题后果自负

Channel
雾汌的通知群
@shicc888
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,049subscribers
+596 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1003954479967 |
|---|---|
| Type | Channel |
| Username | @shicc888 |
| Created | Between 1 April 2026 and 1 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 19 November 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 19 November 2026 |
| On Telegram | t.me/shicc888 |
Topic
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 64% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Nov 2026, 12:41 | 1,049 | +37 |
| 14 Nov 2026, 18:29 | 1,012 | +65 |
| 4 Nov 2026, 17:46 | 947 | +50 |
| 28 Oct 2026, 02:29 | 897 | +74 |
| 21 Oct 2026, 21:20 | 823 | +86 |
| 14 Oct 2026, 04:58 | 737 | +95 |
| 7 Oct 2026, 01:59 | 642 | +78 |
| 25 Sept 2026, 08:39 | 564 | +16 |
| 13 Sept 2026, 20:19 | 548 | +22 |
| 6 Sept 2026, 22:21 | 526 | +27 |
| 29 Aug 2026, 13:16 | 499 | +11 |
| 23 Aug 2026, 04:28 | 488 | +22 |
| 15 Aug 2026, 07:23 | 466 | +11 |
| 8 Aug 2026, 05:00 | 455 | no change |
| 8 Aug 2026, 04:58 | 455 | +2 |
| 7 Aug 2026, 19:25 | 453 | first reading |
Engagement
13 posts held, back to 1 June 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 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 13 posts for this entry, the most recent from 21 July 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 3m 52s
- Average length
- 1m 17s
Measured directly from 3 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
3 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 100.0% |
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 3 of the 13 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 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 1 June 2026 to 21 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
VALORANT: - 修复新实施的优化导致在某些不支持Tiny Algorithm的DMA设备上不工作问题 为所有拥有有效Valorant订阅的用户补偿了6小时时间
VALORANT: - 解决某些特殊武器,自瞄击杀敌人后视角下降的问题 - 重新实现部分逻辑,防止在某些特殊DMA设备上出现负优化 - 在DMA初始化时,无法获取内存映射时直接返回失败,避免出现一些问题 - 移除DX11初始化时优先选择独显的逻辑,以尝试解决一些问题 CS2: - 重新实现部分逻辑,防止在某些特殊DMA设备上出现负优化 - 在DMA初始化时,无法获取内存映射时直接返回失败,避免出现一些问题 - 移除DX11初始化时优先选择独显的逻辑,以尝试解决一些问题
VALORANT: - 为自瞄 / 磁性扳机增加了无扩散(只读) - 修改后坐力来源,现在为计算得出,更精准顺滑不抖动 - 无扩散为开发中版本,不代表最终品质。 - 建议参数:目标锁定启用,平滑1,移动延迟5 如果抖就往上加延迟。 - 目前伪静默效果不如自瞄,待优化。 - 目前不适配狙击枪开镜和一些边界情况,等待后续慢慢修改。
伪静默 + 无扩散
Zero用户反馈
【ZERO 新赛季适配进度公告】 新赛季会针对性项目已知问题,并在保证稳定性的前提下进行了多项优化。 目前游戏 部分闪效果及新赛季相关机制对解密模块存在一定影响。为避免出现功能、数据异常或稳定性下降等情况,项目组决定暂缓推送相关更新到新赛季提供新版本 我们将持续跟进新赛季内容,待完成深度适配及多轮测试后再开放更新,以确保版本质量与稳定性 感谢各位用户的耐心等待与长期支持。
用户反馈
1.本次新增对edid颠覆性焕新,旨在对融合器去特征,让反作弊系统无法扫描检测到用户正在使用融合器。增加对硬盘序列号无痕修改,调整分区类型GUID使其变更以后无需进行引导层修复。sad解码完全遵循硬件品牌对应的数字id变更,这是我们支持使用者高击杀的核心因素。 2.关于200血量伤害:我们已经实现了彻底无痕加载,支持安全启动并且无法扫描出证书指纹,这是一件耗时最久非常具有挑战性的事。 对于SAD200血量伤害仅存在于账号异地登录,或曾经被200伤害过的账号,没有经过冷却频繁登录击杀。 对此我们经历大规模测试后提供对应的两种方案,异地登录需要把现在登录地点变成常用登录地点(每天登录游戏1小时持续大约3-7天)。 被不同原因200血量踢(钩子解密等)需要账号冷却3-7天 3.对于使用劣质解码产品导致自身设备id变成乱码的用户,需还原初始原机。如果你使用过硬解导致设备id是乱码请务必还原。 示例:常见格式(混合)主流厂商(如华硕、…
❤2
经测试组测试 当前1.1.1版本 后台挂一个 逆战未来 用解密1 4 都 不脱不卡 WEGAME 下载 逆战未来 不要云启动 进入游戏解密后可以 自行测试 是否可以关闭逆战未来
King更新内容 king_0602A.rar 更新: 1:修复自瞄盒子连接按钮显示 2:修复菜单页面辅机鼠标 右键还会出现刷新打印状态 3:修复上自瞄设置鼠标左键无效 增加侧键等 4:修复物品筛选-价值自定义价格 5:修复heino1 链接失败问题 6:修复菜单自定义热键 7. 修复字体翻译不全等 8. 修复战斗预览增加手持武器栏目 显示他的头甲包胸挂等级 方便鉴别 9:尝试优化坐标解密个别绘制拖闪问题等 🚀仍在持续优化中,如遇问题请及时反馈。
❤1
File, posted without a caption
Showing the 12 most recent of 13 posts we hold for @shicc888. 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.
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 19 November 2026 — this entry's latest reading, not the date you are reading this.
“雾汌的通知群” (@shicc888), 1,049 subscribers as measured 19 November 2026. Telegram Register, tgregister.com/channel/shicc888.
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.