The Nocom Exploit Exposed: 2b2t’s Biggest Scandal
A July archive on the Nocom exploit, the alleged three-year 2b2t tracking scandal, loaded-chunk probing, base griefs, and community fallout.
Hey, 2b2t veterans and fresh queue warriors alike: picture this. You spent weeks, maybe months, carving out a hidden base far from spawn. Obsidian walls, hidden stashes, farms that could supply an army. You log in after a break, and it is gone. Not just griefed, but systematically looted. Every dupe stash emptied, every build torched with surgical precision. No random TNT raid. No obvious coordinate leak. Just gone, like someone knew exactly where you were the whole time.
If that story sounded familiar to many players in July 2021, they were not just paranoid. The 2b2t community was reeling from what looked like one of the biggest scandals in the server’s history: the Nocom exploit, a silent server-wide tracking system that had allegedly been running for three years.
This archive explains what Nocom was alleged to be, how it worked, who was linked to it by community reporting, and why it changed how players thought about privacy on the oldest anarchy server in Minecraft.
2b2t: where anarchy was supposed to mean freedom
For those still catching up, 2b2t is Minecraft’s wild west. No rules. No bans for hacking, griefing, or duping. Spawn is a crater of obsidian and lava. Bases get built in secret, only to be hunted down eventually. It has been running since 2010, and its history is full of wars, backdoors, and coordinate leaks.
But even in pure anarchy, there had always been an unspoken rule: if you hid your coordinates well enough and did not slip up, your base might survive. Players relied on that fragile privacy. Until Nocom.
Rumors had been swirling on r/2b2t and Discord for weeks. Mysterious griefs. 24/7 accounts that never seemed to log off. Bases found in the middle of nowhere with zero trail. The pieces started to line up around a single exploit called Nocom, short for “No Comment,” which allegedly turned the entire server into an open book for a small group of players.
The birth of Nocom: a fix that opened the floodgates
The story starts back in July 2018. PaperMC, the server software 2b2t ran on, patched a chunk-loading lag and crash exploit. The fix was meant to stop players from crashing the server by abusing block-break desync.
Instead, according to later community analysis, it created something worse.
The patch changed how the server handled certain packets, specifically CPacketPlayerDigging. Suddenly, if someone sent the right packet to any set of coordinates on the map, the server would respond one of two ways:
- If the chunk was loaded, meaning a player was nearby, it would send back the block data at that spot.
- If the chunk was not loaded, it would stay silent.
No distance limit. No obvious red flags. Just silent intelligence.
What started as a way to cause lag became a player radar.
How Nocom worked without the tech overload
Imagine the server as a giant map. Players load chunks around them. That is normal Minecraft behavior. Nocom did not need exact coordinates up front. It only needed to know whether a random location in the middle of nowhere was currently loaded.
Send the packet. Get a reply? A player was within render distance. No reply? Empty wilderness.
Do this thousands of times per second across the entire map using bots, and it becomes possible to map player locations in real time. Add enough math, and movement can be tracked over hours or days.
Early versions allegedly used simple spiral scans: slow but effective. By March 2020, the system was described as much more advanced, with one developer allegedly introducing Monte Carlo particle filters to make tracking faster and more efficient even with rate limits. The result was a live radar of the server across the Overworld, Nether, and End.
The shadow group: Nerds Inc and the architects
This was not described as a solo project. Multiple community sources pointed to Nerds Inc, a tight-knit crew connected to 2b2t drama for years. Names like 0x22, Babbaj, Fr1kin, and later leijurv, known for Baritone pathfinding work, were discussed in connection with it.
The group allegedly ran dozens of accounts 24/7, fed data into databases, and remotely mapped bases by probing chunks. They did not need to walk there and risk being seen. They could map, catalogue, and strike later.
The exploit was reportedly kept quiet for years. When players got close to the truth, explanations shifted toward lag, random griefers, or other exploits.
Three years of silent carnage
Think about what three years of unrestricted tracking means on 2b2t.
Bases like Valerian, griefed in June 2019, the real Viper Base, and Hopen in August 2020 all showed signs that community analysts later connected with Nocom-style precision. Players who thought they were safe suddenly lost everything: stashes, shulker boxes, and years of work.
It was not just grief for jokes. It was targeted, efficient, industrial-scale base hunting.
Most victims never knew why. They assumed bad luck or a coordinate leak from a trusted friend. The paranoia this created across the community became one of the scandal’s lasting effects.
The 2021 wake-up call: how it finally got exposed
In late June and early July 2021, another group, reportedly Infinity Incursion, built a cruder but still functional version of the same exploit. They were not as careful. Their activity became more obvious. Griefs started piling up faster. People connected the dots.
Suddenly, old griefs that had never made sense looked suspicious. Accusations flew. Screenshots, packet logs, and theories flooded Discords and Reddit. The secret was out, or at least cracking wide open.
As of July 1, 2021, Hausemaster had not made an official statement, but the server was on high alert. Packet limits had been tightened over the previous year, and more changes seemed likely.
Why this was one of 2b2t’s biggest scandals
2b2t had already seen backdoors, dupes, priority queue drama, and spawn wars.
Nocom felt different because it attacked a basic survival assumption: that effort and secrecy could protect a base. It turned the entire server into a panopticon for a small group and allegedly did so for three years without most players noticing.
This was not just another hack. It was an information imbalance that changed how players judged every old grief, every unexplained stash loss, and every supposedly private build.
What happened next?
The community split. Some players were furious and called for drastic fixes. Others shrugged and argued that anarchy meant exactly this kind of abuse could happen.
One thing was clear: trust dropped. Players moved bases, changed habits, and watched every 24/7 account with suspicion.
Hausemaster had always played server operations slowly and quietly, but Nocom created pressure for direct technical mitigation. Whether players saw it as an exploit, scandal, or inevitable anarchy outcome, it became a turning point in how 2b2t players thought about location privacy.
The anarchy dream got a reality check
Nocom did not kill 2b2t. It exposed how fragile privacy could be in a server where anything goes.
In a world where TNT, withers, and crystals were obvious threats, the most dangerous weapon turned out to be invisible information. The scandal changed how players treated travel routes, stash behavior, base trust, and long-term secrecy.
Current 2p1j.org context
This article is preserved as a historical anarchy archive on 2p1j.org. The active 2 Paws 1 Job server launched on January 1, 2026 with no queue, no world resets, and one shared world for Java, Bedrock, MCPE, and cracked clients. For current server data, see live statistics, server commands, and the player gallery.
FAQ
What was the Nocom exploit?
Nocom was an alleged 2b2t tracking exploit that used server packet responses to test whether distant chunks were loaded. If a chunk responded, a player was probably nearby. By scanning many coordinates with bots, operators could infer player locations, track movement, and find bases without normal exploration.
Why did Nocom matter for 2b2t bases?
Nocom mattered because it weakened the core defensive habit of anarchy players: hiding far from spawn and guarding coordinates. If the exploit could identify loaded chunks across the map, remote bases and stashes were exposed by server behavior rather than by travel trails, screenshots, betrayals, or public coordinate leaks.