Разработчики хорошо поработали над этим меню
Signed Алексей

Channel
@minerild
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
786subscribers
-75 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001662881837 |
|---|---|
| Type | Channel |
| Username | @minerild |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/minerild |
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 20 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 3 Oct 2026, 22:01 | 786 | -30 |
| 18 Sept 2026, 13:37 | 816 | -26 |
| 11 Sept 2026, 03:58 | 842 | +4 |
| 2 Sept 2026, 16:08 | 838 | -11 |
| 27 Aug 2026, 01:33 | 849 | -18 |
| 19 Aug 2026, 21:37 | 867 | +9 |
| 13 Aug 2026, 12:58 | 858 | -3 |
| 13 Aug 2026, 01:17 | 861 | first reading |
14 posts held, back to 9 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 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 14 posts for this entry, the most recent from 12 August 2026. An engagement rate over an empty window would be a number about nothing.
4 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 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 14 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 9 August 2026 to 12 August 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.
Разработчики хорошо поработали над этим меню
Signed Алексей
Это среда, мои чуваки! Из-за того, что разработчики вчера поломали снапшот, он выходит сегодня. И вот что нам добавили: — Переименовали карты. Теперь карта древнего города называется как карта закопанного древнего города. Тоже самое и с шахтами, и как-то переименовали карту заброшенного лагеря. — В Realm-мирах можно создавать коды приглашения для других игроков. — Подушки теперь разрушаются только тогда когда они п…
Signed Алексей
Еще больший остров... Он в несколько раз больше предыдущего острова, и я просто не смогу его целиком заснять. Размеры острова: 4к на 5к блоков Сид: 1335035814538726851 (большие биомы) Координаты: 2100 100 -2300 К слову, спавн тоже на острове... А если здесь наберется 100 реакций, то я снова соберу сборку модов и попробую выжить в таком мире...
❤2
Signed Алексей
Король среди грибных островов Этот остров настолько огромный, что чтобы его полностью прогрузить, понадобятся моды на повышенную дальность прорисовки. В центре острова есть своё внутреннее море, и еще один остров. И под ним древний город. Его нашел один из пользователей на Reddit Сид: -1718697987229885906 Координаты: -27292952 150 -24111496
❤2
Signed Алексей
Есть ещё одна интересная информация PEGI поменял правила рейтингов в июне этого года. Теперь там начали учитываться так называемые "интерактивные риски" — всё, что касается внутриигровых покупок, ограниченных по времени предложений, наград за возвращение в игру и прочее подобное. Получается, что рейтинг будет изменен просто из-за изменения правил. Ну и конечно из-за того, что на Minecraft Bedrock есть маркетплейс
Signed Алексей
С сайта Minecraft убрали возрастной рейтинг, заменив его такой картинкой. Надпись на песке читается как "Never give up" — "Никогда не сдавайся" Возможно на сайте ведутся технические работы, а возможно и что-то добавили серьезное. Снапшот выходит завтра
Signed Алексей
Оверпрайс
Signed Алексей
А вот и портал над лавовым озером. Во время путешествия по аду, я прихватил оттуда блоки из искаженного и багрового леса, и буду его еще улучшать
Signed Алексей
Выбрался в деревне неподалеку
Signed Алексей
Решил я переместить портал. В итоге получилось все так, что я забыл огниво, и мне буквально придется некоторое время выживать в незере
Signed Алексей
А вот и сам пепельный сад во всей своей красе!
Signed Алексей
Без листвы он выглядит получше. Скоро будет готовый результат
Signed Алексей
Showing the 12 most recent of 14 posts we hold for @minerild. 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.
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.
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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“MineRild” (@minerild), 786 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/minerild.
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.