Minecraft 26.2 Pre-Release 3 Out for Server Hosts

Mojang released the third pre-release for version 26.2 on 2 June 2026, delivering several engine adjustments, graphics corrections, and gameplay balance revisions. For operators monitoring upcoming updates on the Minecraft Server List, this deployment also addresses several severe crashes affecting the JVM alongside lingering multiplayer race conditions.

The update notably backtracks on a recent combat change while cleaning up telemetry tracking for shared worlds.

Attribute Swapping Reversal and Telemetry

The most notable mechanical decision in this build is Mojang's choice to pull back on a recent exploit fix.

The Attribute Swapping Reversion

In this build, the developers reverted a patch that had addressed the "Attribute Swapping" exploit. Mojang stated that the fix was undone due to unrelated side effects rather than an intention to support the behaviour. The team noted that Attribute Swapping remains unsanctioned and will instead be addressed in an upcoming snapshot.

Shared Session Telemetry

Mojang also noted a World Events telemetry property originally omitted from the 26.2 Pre-Release 2 changelog. The field server_session_id functions as a distinct identifier assigned to each multiplayer session, shared uniformly across every connected client on that instance.

Sulfur Cube and Combat Adjustments

Several fixes focus on the Sulfur Cube mob, resolving visual inconsistencies and interactions during combat encounters:

• Blocks held within a Sulfur Cube align vertically to the world grid exclusively while the mob remains invisible.
• The squishing animation no longer triggers if the entity holds a block internally.
• Players can now strike Sulfur Cubes containing primed TNT using spears (MC-307794).
• Explosions from TNT-loaded sulfur cubes now properly drop all destroyed blocks (MC-307916).
• Operators will no longer see players swapping out internal blocks while contained TNT is set to detonate (MC-308541).
• Striking mid-air cubes near their top edge no longer grants excessive vertical launch height (MC-308152).

Other combat and movement adjustments include restoring boat momentum across geysers (MC-308133), resolving desynchronisation of player sneaking states (MC-268008), and correcting geyser effectiveness against riders (MC-307822).

Host Upgrades, Stability, and Engine Crashes

Deploying testing builds or preparing Minecraft 26.2 servers requires watching several underlying stability patches included in this release.

Multiplayer Crashes and Spawner Spam

A race condition that triggered crashes during multiplayer sessions has been resolved under MC-308537. Furthermore, running worlds on Peaceful difficulty no longer floods server console logs with rendering errors when monster spawners load (MC-307969).

Rendering Engine Stability

On the client side, numerous crashes tied to the Vulkan rendering pipeline were patched. Mojang resolved memory exhaustion caused by oversized animated atlas textures (MC-307899) and fixed JVM crashes triggered when dual shaders fail to compile (MC-308533). Similar low-level graphic corrections have been applied across earlier cycles like Minecraft 26.3 pre release 1.

Administrators upgrading testing instances do not need to modify configuration files, as the release documentation specifies no custom schema revisions. A standard server restart and JAR replacement is sufficient to test the build.

What Players Will Notice

Players testing this release will immediately see smoother combat and interaction handling. Sneaking should no longer unexpectedly desync between client and server, preventing sudden slips or detection issues. An exploit that permitted character movement with inventories open—caused by binding a direction key identically to the Debug Modifier—has been closed (MC-308426).

Visually, head segments on placed beds appear without single-frame latency (MC-308065), and banner outlines no longer render purely white (MC-308448). For visual setups, the video settings tooltip for Exclusive Fullscreen now explicitly clarifies that Adaptive Sync technologies, including AMD FreeSync and Nvidia G-Sync, require the setting to be enabled to function.