Minecraft 26.3 Pre-Release 3: Villager Trade Exploit Finally Gets Squashed

Minecraft 26.3 is getting close to the finish line. Pre-Release 3 dropped on September 8th, and like most late-stage pre-releases, it's not about flashy new content. It's about squashing the bugs that slipped through earlier testing before the update goes live for everyone.

That said, a few of these fixes are more than just housekeeping. One in particular has been quietly letting players rip off villagers for free, and that's the kind of thing economy server owners will want to know about before it gets patched out from under them.

The Villager Trade Exploit Was Worse Than It Sounds

Let's start with the one that actually matters for anyone running a server with a working economy. Two separate bugs let players walk away from villager trades without paying a single emerald.

The first, MC-311678, happened when a player damaged a villager enough to drop their reputation to zero while a trade screen was already open. The second, MC-311679, triggered if the villager restocked mid-trade. Either way, the game would let the trade go through without taking the payment.

Players can complete trades without payment if the villager restocks while the trading screen is open.

On a vanilla singleplayer world this is barely a footnote. On a survival server where emeralds have actual value, this is the kind of exploit that spreads through a Discord in about an hour and quietly wrecks your economy. If your server runs villager-based shops or trading halls, it's worth checking whether anyone's been abusing this before the patch lands.

Fullscreen Has Been a Mess, and This Pre-Release Cleans Up a Lot of It

Anyone who's messed with the newer exclusive fullscreen options in recent snapshots knows they've been rough. This pre-release fixes a noticeable chunk of that mess.

• On macOS, toggling Exclusive Fullscreen Mode wasn't actually changing the game's resolution (MC-311631).
• Setting the fullscreen resolution to "Current" would stubbornly keep whatever resolution was previously selected instead (MC-311634).
• Windows users saw normal fullscreen fail to kick in after disabling Exclusive Fullscreen (MC-311664), and borderless fullscreen sometimes just... didn't fill the screen (MC-311683).
• Pressing Windows+Down Arrow while in fullscreen would incorrectly boot the game into borderless windowed mode (MC-311722). A weird one, but if you've hit it, you know how annoying it is.
• Wayland users on Linux had an issue where clicking links in-game wouldn't hand focus back to the browser (MC-311113).

None of these are game-breaking for server gameplay, but they're exactly the kind of friction that makes players grumble in your support channel. Good to see Mojang chipping away at the display settings rework rather than letting it linger half-broken.

Small Visual Bugs That Were More Annoying Than They Should've Been

Falling blocks have had a flicker problem for a while now. Sand, gravel, concrete powder, whatever, it would briefly vanish the instant it landed (MC-309262). A related bug made things worse: if you broke a falling block while another one was falling on top of it, the top block would flicker invisible and reveal unlit particle effects underneath (MC-311419). Not dangerous, just visually janky in a way that stood out if you build with sand or gravel a lot.

There's also a fix for seeing through blocks when your camera clips inside snow layers (MC-311579), and a rendering glitch where the rightmost column of pixels looked wrong in windowed mode (MC-311721). Tiny stuff, but it's the kind of polish that separates a stable release from one that gets immediate follow-up patches.

Number Providers Get Consistent, Which Datapack Authors Will Appreciate

This one's buried in the technical changes section, but anyone building custom loot tables or datapacks should pay attention. The minecraft:mod float provider now uses standard modulus instead of floor modulus, matching how the integer version already worked. And raising 0 to the power of 0 in the float provider now throws an error instead of silently returning a different result than the int version.

Basically, Mojang found that integer and float number providers were giving different answers for the same math (MC-311650 and MC-311651), which is exactly the kind of inconsistency that breaks custom generation logic in subtle ways nobody notices until a loot table starts acting weird. The data pack version also bumped to 121.0, so if you maintain packs, double check compatibility before pushing this update live.

A Couple of Smaller Fixes Worth Mentioning

Shovels extinguishing campfires were supposed to lose durability, and somewhere along the way that stopped happening (MC-311673). Minor, but it was effectively a free durability exploit for anyone who puts out a lot of campfires.

There's also a fix for block-breaking particles and sounds continuing to play after you pause the game in multiplayer or step through a portal (MC-311676). Not a big deal, but immersion-breaking in the way that only Minecraft's weird little edge cases can be.

What This Means If You Run a Server

Pre-releases exist for exactly this reason: catch the stuff that snapshots missed before it ships to millions of players and thousands of servers. If you're planning to update to 26.3 the moment it goes stable, it's worth testing this pre-release on a backup copy of your world first, especially if villager trading or custom datapacks are part of your setup.

The trading exploit fix alone is reason enough to watch for the full release. Economy-focused servers, SMPs with player shops, and anything leaning on villager trading halls should treat this as a priority update once it's out of testing.

Full patch notes, including the technical changes list, are available on the official Minecraft.net post. There's a decent chance we see one more pre-release before 26.3 goes fully live, but based on how focused this list is, the full release probably isn't far off.

", "tags