What breaks when Minecraft 26.3 lands: mods, farms, and servers

Every Minecraft update produces the same wave of searches: does my shader pack still work, is Sodium updated, did they break my farm. Minecraft 26.3 is due this month, and this page exists to answer those questions honestly, which means separating three very different kinds of claim.

Mod compatibility, checked against Modrinth directly

Rather than guess, we queried the Modrinth version API for each project on 1 September 2026 and read the actual game_versions field on their latest releases. That field is a fact, not a prediction: it is what the mod author has published support for, today.

What that actually means, tier by tier:

• Fact: Fabric API is the loader-facing compatibility layer, and its maintainers publish a build against nearly every snapshot as a matter of routine, because mod developers need it to test against. Seeing 26.3-snapshot-7 through snapshot-10 builds already live is normal Fabric API behavior, not a signal that the wider mod ecosystem is ready.
• Fact: as of this check, Sodium, Lithium, and Iris have no published 26.3 build, snapshot or otherwise. Their newest releases target 26.2.
• Expectation, not fact: these three will almost certainly get 26.3 builds, likely close to or shortly after release. CaffeineMC (Sodium, Lithium) and IrisShaders have shipped a compatible update for every recent quarterly release, usually within days to a couple of weeks. That track record is a reasonable basis for expecting the same here. It is not a guarantee, and there is no fixed timeline to point to.
• What we don't know: how long the gap will be this time, whether 26.3's rendering changes (below) mean more porting work than a typical update, and whether any of these projects will need a genuinely new release rather than a version bump.

If you're not sure how your current mod stack fits together, the complete Fabric performance mod stack and Sodium vs Embeddium cover the current, working baseline you'd be updating from.

The rendering change: OIT replaces Improved Transparency

This is the technical change most likely to have downstream effects, and it's worth being precise about what it actually is.

Snapshot 2 of 26.3 replaced the old Improved Transparency video setting with Order-Independent Transparency (OIT), a different algorithm for compositing translucent geometry: stained glass, water, ice, and leaves layered on top of each other. The old system's flickering and incorrect sort order on translucent surfaces is exactly what OIT targets.

• Fact: this is a change to how the vanilla renderer composites transparent pixels, confirmed in the Snapshot 2 notes and still present as of Snapshot 10.
• Reasoning we're labeling as such: any mod or shader pack that hooks into the transparency pass, reorders render layers, or assumes the old Improved Transparency pipeline is doing the compositing has a plausible reason to need updating. Iris in particular sits directly in this part of the render pipeline, which is one reason shader compatibility is worth watching closely here, not just assuming will carry over.
• What we don't know: whether OIT actually breaks any specific shader pack. We have not seen a shader pack fail against a 26.3 build, because Iris itself has no 26.3 release yet to test one on. Nobody can honestly claim a specific pack is broken until Iris ships 26.3 support and someone runs it.

This sits in the same direction as 26.2's experimental Vulkan renderer: Mojang is modernizing the rendering pipeline in stages rather than one rewrite. If you track how these rendering changes interact release over release, that guide is the place to watch.

Datapacks and map-making: format bumps are the real breakage here

Unlike client mods, this is territory where the snapshots themselves hand you a concrete, verifiable answer: data pack format has moved from 108.0 (Snapshot 1) to 118.0 (Snapshot 10), and resource pack format from 89.0 to 97.0, over the course of the cycle. A datapack or resource pack built for 1.21.4 or 26.2 will not load cleanly on 26.3 without its pack.mcmeta format number updated, and depending on what it uses, more than the number.

Concrete, verified changes that hit datapacks directly:

• New block predicate minecraft:height_range, usable in loot tables and other predicate contexts.
• New feature types (end_podium, overlay, projected_random_patchy_square), alongside renamed existing ones (glowstone_blob became random_neighbor_spread, basalt_pillar became single_block_pillar in Snapshot 2). A datapack referencing the old feature type names by their pre-26.3 identifiers will not resolve.
• New data components, including minecraft:block_transformer, minecraft:brewing_fuel, minecraft:cooking_fuel, minecraft:compostable, minecraft:villager_food, and minecraft:mob_visibility. None of these retroactively break an existing item definition, but they are new territory for anyone building custom items or loot.
• Material Rule handling moved out of noise settings into its own data-driven registry, and carver configuration was inlined rather than nested under a config key. Both are structural changes to world-generation datapacks specifically, not to loot tables or recipes.
• Trim material format overhaul: asset_name was replaced with palette_id. Any custom armor trim datapack using the old field name needs updating.
• The two new commands, /compute and /posteffect, expand what a datapack can do (/compute evaluates a number provider for scoreboard-style math; /posteffect manages post-processing shader effects on a player) but don't break anything by existing. For the day-to-day mechanics of installing and troubleshooting datapacks generally, see how to install datapacks.

If you maintain a datapack, the format-number bump alone is reason enough to test against a snapshot before release, since Mojang has already told you, in the pack format numbers, that something changed.

Farms: what we can say, and the Drowned lesson

Farm guides are exactly where "wait for release" earns its caution, and 26.3 already produced the textbook example of why.

Fact: Snapshot 2 changed Drowned so that one holding a trident within 3 blocks of a target would switch to melee instead of throwing. Fact: Snapshot 10, the most recent build as of this writing (25 August 2026), reverted that change. Drowned are back to their original trident-throwing behavior. No reason was given for either the change or the revert.

That reversal, mid-cycle, is the whole argument for not rewriting a Drowned farm's mechanics based on a snapshot. A mechanic can ship, hold for eight snapshots, and still get pulled before release. Nothing else in the snapshots so far indicates a mob-behavior change to any other farm-relevant mob (iron golems, guardians, endermen, piglins, and the rest are unchanged as of Snapshot 10), but "unchanged in the snapshots we've seen" is not the same claim as "confirmed unchanged at release."

The wider farm risk in 26.3 is not mob AI, it's structural: none of the confirmed 26.3 content (dappled forest, abandoned camps, poplar wood, straw beds, cushions) touches redstone mechanics, hopper behavior, or existing farm designs. Existing iron, gold, guardian, enderman, and mob-grinder designs from the current farm library should carry over mechanically. That's a reasonable expectation based on what has and hasn't changed in ten snapshots, not a release-day guarantee, so the honest version is: nothing in 26.3 currently threatens those designs, and we'll confirm on release. See the 26.2 farm guide collection for the current designs this applies to.

Servers: what to actually do before updating

This is process advice, not a compatibility claim, and it doesn't change release to release.

1. Never update a live world's server jar on release day. Copy the world folder to a test environment first. World format changes are one-directional: Minecraft upgrades a world's data on load and does not reliably downgrade it.
2. Check plugin and mod compatibility before the players do. If you run Paper or a fork, wait for your plugins to publish 26.3-compatible builds the same way you'd wait for Sodium above; a plugin built against a prior API can throw errors or silently misbehave on a version it wasn't tested against. If you run Fabric, the same Modrinth-check method used above for Sodium and Lithium works for every server-side mod you depend on.
3. Back up before you touch anything, snapshot testing included. If you're unclear on your current backup routine, the server backup guide covers what to automate.
4. Budget for a compatibility gap. Based on past cycles, expect days to a couple of weeks between release and your specific plugin or mod stack catching up, not zero. Plan the update window around that, not around release day itself.
5. Re-test performance after updating, not just functionality. A new renderer or new block types can shift what your server profiles as slow; the complete performance guide and Aikar JVM flags are your baseline for re-tuning if TPS or memory behavior looks different after the jump.

FAQ

Does Sodium work on Minecraft 26.3?

Not yet, as of 1 September 2026. Sodium's latest published Modrinth release targets 26.2. Based on its track record across recent updates, a 26.3 build is a reasonable expectation, not a confirmed date. Check Sodium's Modrinth page directly before updating.

Is Iris updated for 26.3?

No published 26.3 build exists yet, per Modrinth as of this writing. Iris's latest release targets 26.2. Because 26.3 changes the transparency rendering pipeline (OIT), shader compatibility is worth watching closely once Iris does publish a 26.3 build, rather than assuming a straight version bump will behave identically.

What is OIT in Minecraft 26.3 and does it break shaders?

OIT (Order-Independent Transparency) is a new rendering method that replaced the old Improved Transparency setting, aimed at fixing flicker and sort-order bugs on translucent surfaces like glass and water. It's a real change to the render pipeline that mods and shaders touching transparency have a plausible reason to need updating for. Whether any specific shader pack breaks is not yet known: nobody can test that until Iris itself has a 26.3 build.

Will my datapack work on 26.3 without changes?

Only if it doesn't use the renamed feature types, the old trim material field, or now-relocated Material Rule configuration, and even then you need to bump the pack format number (118.0 for the data pack format as of Snapshot 10, up from 108.0 at Snapshot 1). Test it on a snapshot or the release build before relying on it.

Are my farms going to work in 26.3?

Nothing confirmed in the ten 26.3 snapshots changes redstone, hoppers, or the mob AI behind common farm designs, except one reverted Drowned change. That's a reasonable basis for expecting existing iron, gold, guardian, and mob-grinder farms to keep working, not a release-day guarantee. The Drowned trident behavior specifically flipped once already mid-cycle, which is exactly why farm guides should be confirmed after release, not before.

When should I update my server to 26.3?

Not on release day, unless you're running vanilla with no plugins or mods and are willing to accept early bugs. Copy your world to a test server first, wait for your specific plugins or mods to confirm 26.3 support, and keep a backup regardless.

---

Sources & further reading:

• Minecraft Wiki - Java Edition 26.3
• Minecraft Wiki - Java Edition 26.3 Development versions
• Modrinth version API, checked 1 September 2026: Sodium, Lithium, Iris, Fabric API
• Minecraft 26.3: everything we know so far - SyntaxMine
• The complete Minecraft performance guide - SyntaxMine
• Minecraft farm guides for 26.2 - SyntaxMine