Minecraft 26.2 Client Compatibility — What Changed
Minecraft 26.2 introduced rendering updates, particularly order-independent transparency (OIT), alongside continued changes to the block and entity systems. This article documents what changed and how it affected client and module support.
Summary
26.2 is the newest tracked Minecraft release. Client support is developing — Wurst has a stable 26.2 build, while other clients are still catching up. Combat and movement modules work without changes. Some visual modules may need updates to work correctly with OIT rendering.
What changed in 26.2
- Rendering: OIT transparency system for more accurate rendering of overlapping semi-transparent objects.
- Blocks: Minor changes to block entity handling. No removals.
- Entities: Continued refinement of entity data structures.
- Network: Protocol changes affecting client-server handshake.
Client support status
| Client | Status | Notes |
|---|---|---|
| Wurst | Active | Stable 26.2 build |
| Meteor | Partial | Not officially listed for 26.2 |
| LiquidBounce | Unknown | Not yet verified |
| Aristois | Unknown | Not yet verified |
| Future | Unknown | Not yet verified |
What this means for modules
- Combat modules — KillAura, AimBot, Reach, and similar work without changes. Combat logic is not affected by rendering updates.
- Movement modules — Speed, Fly, BHop, and similar work without changes. Movement validation happens server-side and is version-independent.
- Visual modules — ESP, Chams, Tracers, and NameTags may need updates because OIT changes how rendered objects are composited. Some clients may show visual glitches until they update their rendering pipeline.
- World modules — Nuker, Scaffold, and block interaction modules work without changes.
- Utility modules — FriendFinder, AntiAFK, and FPSBoost work without changes.
Expected timeline
Historically, client developers publish major-version builds within one to four weeks of a Minecraft release. Some developers release faster because they only support the current Minecraft version; others release slower because they maintain multiple versions simultaneously.
Once a client publishes a 26.2 build, this page and the compatibility matrix will reflect the change.
What to do if you need 26.2 now
- Use Wurst if you need a client on 26.2 right now — it has a stable 26.2 build.
- For other clients, wait for updates or use 1.21.1 or 1.21.5 where broader client support exists.
- Do not attempt to run a client compiled for 1.21.x on 26.2 — the file will not load.