Minecraft 26.3 Pre-Release 2: The Multiplayer Particle Bugs Nobody Noticed (But Everyone Felt)

Mojang just pushed out 26.3 Pre-Release 2, and the thing that stands out immediately isn't a flashy feature. It's the pace. Two pre-releases in a single week means Mojang has left snapshot mode behind entirely and is now in pure bug-squashing territory, the final stretch before 26.3 goes live.

Pre-releases don't get the fun stuff. No new mobs, no new blocks, nothing to build a trailer around. What they do get is a long list of fixes that quietly make the game feel less janky, and this one has a few worth actually paying attention to.

The multiplayer sync fixes are the real story here

Scroll through the bug list and you'll notice a pattern. Several fixes deal with effects that one player could see or hear but others nearby couldn't. Block breaking particles weren't visible to other players, and neither were the sounds that go with them. Particles from entities growing, walking through powder snow, and even feeding flowers to mooshrooms had the same problem.

None of these are game-breaking on their own. But stack them together and you get a multiplayer world that quietly feels less alive than it should, where half the little sensory feedback players rely on just isn't reaching anyone except the person causing it.

Two pre-releases in one week!? That's right! Now that we're in the pre-release phase, we're no longer following our regular snapshot schedule.

For server owners running busy survival worlds, this matters more than it sounds. A lot of ambient immersion on populated servers comes from seeing other players mine, farm, and move around you. If those cues have been silently dropping for other players this whole time, fixing it should make shared worlds feel noticeably more responsive once 26.3 ships.

A villager trading exploit got shut down

One fix buried in the list is actually a real economy concern. Player-caused damage during a trade could let someone complete the trade without paying for it. On vanilla survival that's annoying. On economy servers where villager trading is tied to real player-run shops or emerald economies, that's a dupe-adjacent exploit that could've been quietly abused for a while. Worth flagging to your mods if you run anything trade-heavy.

There's also a fix for ruined portals generating on top of end portal frames, which sounds niche but has caused real headaches for stronghold-finding and speedrun-adjacent communities when portal structures overwrite each other.

Rendering backend problems keep surfacing

Minecraft's ongoing rendering overhaul keeps throwing up edge cases, and this pre-release has a rough one: severe rendering errors on Windows devices with a Snapdragon 8cx Gen 2 CPU, the kind of ARM chip found in some Surface and Windows-on-ARM laptops. There's also a fix for the mouse cursor going invisible in fullscreen on the OpenGL backend, and another for resource pack reloads causing glitches and crashes on OpenGL.

If you've been following the rendering backend transition Mojang has been working through over the last several snapshot cycles, this is par for the course. New rendering paths tend to break on hardware nobody tested against until players with that exact chip start filing reports. It's good that these are getting caught now rather than after full release, but it's also a reminder that the rendering rework still has rough edges worth watching if you run a server with a mixed player base on unusual hardware.

Smaller fixes that quietly matter

• Sculk sensors finally detect ice and snow melting, closing a gap that's existed in the redstone contraption community for a long time.
• Spawners with light-level limits set weren't spawning mobs underground at night, which broke a chunk of custom mob farm designs relying on that behavior.
• Goats behave properly now after being tempted mid-jump instead of glitching out, per MC-228273.
• Camels with two riders no longer block item interactions, something that's annoyed anyone trying to feed or equip a camel while someone else is riding along.
• Chunks could end up with absurdly high InhabitedTime values when a world loads, per MC-304719, which matters for anyone using mods or data packs that scale difficulty or loot off that stat.

What data pack creators need to know

The data pack version moved to 120.0, and the structure tag on_abandoned_camp_windswept got renamed to on_abandoned_camp_windswept_forest. It's a small change, but if your server runs a custom data pack referencing that tag by name, it'll silently break until you update the reference. This kind of thing is exactly why pre-release testing exists. Catching these renames now means fewer surprises when 26.3 lands on live servers.

There's also a fix for missing loot context parameters in "generic" loot context and a related crash fix for LootContextUser referencing parameters that weren't provided. Anyone building custom loot tables should take note, those two together were causing real stability problems for complex loot setups.

Where this leaves us

Pre-releases are never exciting reading, and this one won't convince anyone to boot up Minecraft who wasn't already planning to. But the cluster of multiplayer sync fixes is a genuinely nice quality-of-life improvement that most players won't consciously notice, they'll just feel like the game is a little more solid than it was last week.

With two pre-releases out in the same week, 26.3 full release is almost certainly close. Server owners running Java should start checking their plugins and data packs against this pre-release now rather than waiting for the stable drop, especially if anything touches loot tables, structure tags, or villager trading logic. The full patch notes are worth a skim on the official Minecraft site if you want to see every fix Mojang squeezed in.