Minecraft 26.2: Server Owner's Snapshot Guide

Darius N.
4.9

608+ Satisfied Customers

Minecraft 26.2 lands June 16, 2026. The update has moved through its weekly snapshot run and into pre-release, and the player-facing coverage has been solid. But most of it answers the wrong question for you.

If you run a server, your questions are: when does stable drop, can I run a snapshot server now, and what is going to break when I upgrade? This post answers those, then gets into the features and technical changes worth knowing about.

What 26.2 is and when to expect it

26.2 is the second game drop of 2026, officially named Chaos Cubed. It centers on a new underground cave biome called the Sulfur Caves, a new mob (the sulfur cube), and related geological features. It releases June 16, 2026.

Mojang confirmed the June 16 date in May 2026. The update ran through a weekly snapshot cycle that started April 7 (following the 26.1 Tiny Takeover release on March 24) and has since moved into its pre-release phase, where the feature set is locked and the team is fixing bugs ahead of the stable build.

Dates can still slip if Mojang finds something that needs more iteration in the final pre-releases, but June 16 is the announced target.

Should you run a snapshot server right now?

Probably not, unless you have a specific reason to test features before they land in stable. 26.2 is in its pre-release builds now, and for server purposes those behave like snapshots: version-locked clients, no stability guarantees, and limited plugin or mod support.

Here is what you are actually signing up for with a snapshot or pre-release server:

Limited plugin and mod support. Vanilla snapshot and pre-release builds are the most reliable, and Fabric ships snapshot-compatible builds fast (often within days). WinterNode’s installer also offers Paper, Forge, and NeoForge snapshot editions. The catch is compatibility: during a pre-release, the specific plugins and mods your production server depends on usually have not updated yet, and what works can shift from one build to the next. A pre-release server is for testing, not for replacing your live setup.

Version-locked clients. Players connecting to a snapshot server must be on the exact matching snapshot version. Anyone on stable (currently 26.1.2) cannot connect, and a client on one snapshot or pre-release cannot connect to a server running a different build. Every new build locks the client requirement to that exact version.

No stability guarantees. Snapshots introduce and remove features between builds. Your world, config, or data packs can break when the next snapshot ships. Mojang explicitly recommends running snapshot servers on separate worlds, not your production (main) world.

Worlds are forward-compatible but rarely backward-compatible. A world touched by a snapshot may not load cleanly in stable, and it almost certainly won’t go back to 26.1.2 cleanly.

If you want to test Chaos Cubed features before the stable release, a dedicated test server makes sense. If you want to keep playing with your community, stay on 26.1.2 until Paper has a stable 26.2 build.

Warning

Never run your production world on a snapshot server. World data changes between snapshots can corrupt saves or introduce upgrade paths that cannot be reversed. Keep a separate test world if you want to explore snapshot features.

What’s new in 26.2 - the operator-relevant parts

Most of the new features are player-side, but a few things in Chaos Cubed have implications for how your server behaves.

Sulfur Caves and world generation

The Sulfur Caves biome generates deep underground, between Y -48 and Y -64. The biome contains bands of sulfur and cinnabar blocks, sulfur pools (water bodies surrounded by sulfur and cinnabar), and sulfur spikes that form stalactites and stalagmites. Granite and tuff appear in the layers between sulfur and cinnabar deposits.

For server operators: this is new world generation, which means these features only appear in chunks that have not yet been generated. Existing worlds will not retroactively gain Sulfur Caves in already-loaded chunks. Players who want to explore them will need to travel to new, unexplored terrain. If your world border is tight, consider expanding it before upgrading.

The sulfur cube and TNT absorption

The sulfur cube is a new passive mob that spawns in the Sulfur Caves. It belongs to the hostile mob cap for spawning purposes, which means it competes with hostile mobs for spawning space in those chunks. The biome also spawns cave spiders in place of regular spiders, so if you run spider farms or grinders, expect the smaller, poison-applying variant in this terrain.

Snapshot 5 introduced an explosive archetype: sulfur cubes can absorb TNT blocks. Absorbed TNT can be primed by redstone, fire sources, or nearby explosions. When primed, the fuse runs 6 seconds. A sulfur cube carrying primed TNT cannot be picked up with a bucket, damaged, or sheared.

This has a potential griefing angle. A player could prime a sulfur cube’s absorbed TNT via fire or redstone and use it as a mobile explosive. If your server has grief protections, test how your protection plugins interact with mob-carried explosives once Paper builds are available. Existing tools like CoreProtect will log the explosion, but prevention plugins may need updates to handle this edge case.

Geysers

Geysers erupt at roughly 50-second intervals (randomized based on the block’s position), applying an upward impulse to entities above for 4-5 seconds. A Potent Sulfur block with magma underneath and water above (inside a Sulfur Pool) launches entities upward without dealing fall damage from the eruption; the more water stacked above it, the higher they go.

Server-side, this is a mob behavior and entity interaction, not a config setting. No server-side flags to manage here.

Hoglins reclassified as hostile

Hoglins are now classified as hostile mobs and no longer spawn in Peaceful mode. If you run a Peaceful server and your players were farming hoglins, that farm stops working after upgrading to 26.2.

Technical changes that touch your server

These are the changes from the 26.2 snapshot cycle that require operator attention, in order of how likely they are to affect you.

Pack format versions

Both the data pack and resource pack formats stepped up through the snapshot and pre-release cycle - the data pack format is 107.0 as of the latest pre-release, and it can still change before the stable build. If you run data packs or server-side resource packs, they need to declare the format version that matches the build you upgrade to, or players will see warnings. This is standard version-bump work - check the pack.mcmeta file in each pack against the release you are targeting and update the declared format number.

Team color command argument format

The /team modify [name] color and /waypoint modify [name] color commands now only accept lowercase names with underscores. dark_purple works; darkpurple and DarkPurple do not. If you have any command blocks, scripts, or plugin configurations that set team colors using the old format, they will break on 26.2. Audit your command block chains and plugin configs before upgrading.

Predicate format restructured

The entity predicate format has been restructured to work like data component maps. The type field has been renamed to minecraft:entity_type, and unrecognized sub-predicate components are now rejected rather than silently ignored. If you use data packs with custom predicates, test them before upgrading.

minecraft:bed block entity removed

The minecraft:bed special model type and block entity were removed in Snapshot 3. Beds now use standard block models. This is relevant if you have any resource packs or data packs that reference the bed block entity or special model type directly.

Management server starts earlier

The management server now starts before the Minecraft game server, which means the heartbeat is sent while the world is loading and upgrading. The rpc.discover and notification/server/status methods are accessible before the dedicated server is fully up; other methods return an error until startup completes. If you use any tooling that integrates with Minecraft’s management API, test that it handles the earlier startup sequence without breaking.

Java SE 25 still required

Java SE 25 was introduced as a requirement in 26.1 and carries through to 26.2. On WinterNode, Java is managed automatically - nothing to do on your end. On self-hosted setups, verify your Java version before running the 26.2 jar.

Vulkan rendering: client-side only

You may have seen headlines about Vulkan support in 26.2. Vulkan is an experimental client-side renderer that players can toggle in their launcher. It runs on the player’s machine. It has no effect on your server’s performance, configuration, or compatibility. Nothing to configure or worry about here.

Plugin and proxy compatibility outlook

This is about upgrading your live server when 26.2 stable releases. Plugin and mod support during the pre-release builds is experimental and shifts between versions, so the timelines below are about the stable release.

Paper: Based on the 26.1 Tiny Takeover release and prior update patterns, Paper typically releases a compatible build within days to a few weeks of a stable Minecraft version. Watch the Paper project announcements after the 26.2 stable drop - do not upgrade your plugin server until a Paper 26.2 build is available. See our breakdown of Paper vs Spigot if you’re unsure which to run.

ViaVersion: ViaVersion bridges allow players on different versions to connect to your server. For snapshots, ViaVersion support is partial and unofficial - it may not exist at all for pre-release builds. On stable 26.2, expect a ViaVersion update to follow within days to weeks of Paper’s release.

Velocity and BungeeCord proxies: Proxy software requires version matching with your backend servers. If you upgrade your backend to 26.2, your proxy configuration needs to match. Hold the upgrade on proxy and backend servers simultaneously, and wait until all components have 26.2 support before making the switch.

Spigot and CraftBukkit: If you’re still running vanilla Spigot rather than Paper, the same timing applies. Check BuildTools for 26.2 support before upgrading.

Running a 26.2 pre-release server on WinterNode

If you want to test pre-release features now, here is how to spin up a separate test server on WinterNode’s Minecraft server hosting alongside your production setup. The full Edition Installer guide covers every available edition.

The cleanest approach is a separate server instance with a fresh world. Do not point your production world at a pre-release build.

On WinterNode:

  1. Log into your game control panel
  2. Go to Advanced in the sidebar
  3. Click Server Actions, then Install Different Edition
  4. Set Edition to Vanilla (Snapshots) (or Fabric (Snapshots) if you want to test with mods)
  5. Set Version to the 26.2 pre-release you want
  6. Tick the Format checkbox to start with a clean world
  7. Click Install

Info

Make sure the server is stopped before installing. The install will not proceed on a running server.

For self-hosted setups: download the snapshot server.jar from minecraft.net and replace your existing jar. Use a fresh world directory or run the jar with --world snapshot-world to keep worlds separate. Check the world format compatibility guide if you’re switching between server types.

Back up first - every time

Before upgrading any server - snapshot, pre-release, or stable - back up your world.

Warning

World data upgraded by a newer Minecraft version cannot be cleanly downgraded. If something breaks after an upgrade, your backup is the only way back. Take one before every version change. Our guide on how to back up your world covers the backup and restore process on WinterNode.

On WinterNode, backups run automatically, but take a manual snapshot before a version change anyway. The full server update walkthrough covers the WinterNode panel flow in detail.

What to watch for between now and release

26.2 is in its pre-release phase, with the stable build due June 16. Things to track:

  • Final pre-release builds: The feature set is locked and Mojang is on bug fixes. This is the window to seriously test your data packs and configurations against a near-final build.
  • Pack format numbers: Formats can still tick up in the final pre-releases. Confirm the number on the build you upgrade to before updating your packs.
  • Paper compatibility: Watch the PaperMC Discord and GitHub after the June 16 stable drop. Their turnaround has been fast for recent releases - usually days to a couple of weeks.
  • ViaVersion and proxy updates: These typically follow Paper’s timeline by a few days to a week.

The short version: stay on 26.1.2 for your production server, run a separate test instance if you want to explore Chaos Cubed now, and wait for Paper before doing anything with your plugin setup.


Ready to run your server on 26.1.2 stable or set up a dedicated test instance for 26.2 snapshots? Get your Minecraft server →

Starting at $1.99/GB with no CPU limits and a 48-hour free trial. Questions about the upgrade path or snapshot setup? Our support team is on it - find us on Discord.

Frequently Asked Questions

June 16, 2026. Mojang confirmed the date in May 2026. The update is in its pre-release phase now, so the feature set is locked and the team is focused on bug fixes ahead of the stable drop.

Yes. Vanilla snapshot builds are the most reliable, and Fabric tracks snapshots within days; WinterNode's installer also lists Paper, Forge, and NeoForge snapshot editions. The catch is that plugin and mod compatibility during pre-release is unstable, so use it as a test server, not production. Players must also be on the exact matching client version; no other version can connect.

Not on day one. Paper typically releases a compatible build days to weeks after a stable Minecraft version drops. Hold off on upgrading your plugin server until Paper has a build for 26.2.

No. Vulkan is an experimental client-side renderer. It runs on the player's machine and has zero effect on server performance, config, or compatibility.

The main ones: data pack and resource pack formats both stepped up through the snapshot and pre-release cycle, so any packs need their declared format numbers updated to match the build you upgrade to; team color command arguments now require lowercase underscore format (e.g. dark_purple not darkpurple); and the minecraft:bed block entity was removed during the snapshots. Java SE 25 remains required.