Every entity Minecraft spawns, from an arrow or an XP orb to a dropped item, gets the next number from one global counter. Most players will never think about it. In April 2026, Mikarific and KatieTheQt showed what happens when you push that counter to its limit on purpose: block updates stop firing and entities end up in places the game can’t track. They called it Entity ID Suppression. It’s the newest member of the update-suppression family that technical players have used to break the game for years.
Why it’s special
- It works in survival. The demonstrated setup doesn’t need commands or creative mode.
- It’s a new way to cause suppression. Classic update suppression relies on specific block interactions. This version gets there through the entity counter instead.
- The results stack. One machine can produce several exploits that normally need separate contraptions.
What it can do
| Effect | What it means in game |
|---|---|
| Hidden XP orbs | XP orbs you can’t see but can still collect, absorbed at the maximum rate |
| Item duplication | Duplicates complex items, including full shulker boxes |
| Shadow stacks | The same item stack existing in two places at once |
| Suppressed block updates | Water placed in the Nether and other normally impossible states |
| Advancement tricks | Interrupting trigger sequences at precise moments |
How it works, in plain terms
The machine loads and unloads chunks rapidly while spawning entities, mostly XP orbs, in bulk. That drives the global entity ID counter toward overflow. At the right moment the game’s bookkeeping desyncs. Some entities become invisible but still interactive, and some block updates never fire. The setup is complex and timing-sensitive, which is why demonstrations come from dedicated technical players rather than casual survival worlds.
The technical community has since built tools around it. One is the Entity ID Monitor Fabric mod on Modrinth, which shows the counter, the spawn rate and the time remaining until overflow. Its author warns that forcing collisions can crash servers and permanently corrupt chunks.
How to see or try it
- Use a copy of your world, never your main save. Entity ID collisions can make worlds impossible to load.
- Follow Mikarific’s video for the survival build, and use the Entity ID Monitor mod to watch the counter.
- Check your version. The technique was shown on 26.1, and Mojang hasn’t publicly confirmed whether later versions block it.
What’s next
Server owners should treat this like any dupe: watch for odd entity counts and suspicious item economies. Anarchy servers, where exploits like this matter most, will keep testing it on every new version. If Mojang fixes the underlying behaviour, it will most likely appear as an entity-handling change in a future patch. For the patches Mojang shipped during 26.1, see our Tiny Takeover guide.
