Two of the libraries the Fabric ecosystem is built on reached 26.4 Snapshot 2 within half an hour of each other on 29 September. Fabric API 0.161.2 and YetAnotherConfigLib 3.9.8 are both marked as targeting the snapshot only, and between them they are what everything else waits for.
Why libraries go first
A snapshot port has an order. Fabric API is the compatibility layer almost every Fabric mod depends on, so nothing else can move until it does. Config libraries come next, because a mod with settings cannot build without one. Content mods come last.
That order means the library timestamps are the most reliable early indicator of how disruptive a snapshot is. Fabric API reached snapshot 1 on 22 September and snapshot 2 on 29 September – one week apart, matching the snapshot cadence exactly. A library keeping pace with the snapshot schedule means the underlying changes are not breaking its assumptions.
YACL’s version table tells the story
YetAnotherConfigLib publishes a support matrix with each release, and comparing two consecutive ones is unusually informative.
3.9.7, released 28 September, supported 26.1, 26.2 and 26.3 on Fabric and NeoForge. 3.9.8, released the next day, supports only 26.4 on Fabric – every other cell is marked unsupported.
That is a deliberate split rather than a regression. The 26.4 branch gets its own version line, and the 26.3 line stays on 3.9.7. It is the correct way to handle a snapshot port, and it means you must read the matrix rather than grabbing the highest number.
The number of people who will install 3.9.8 on a 26.3 client and file a bug report is, historically, not small.
What is already on snapshot 2
Beyond the libraries, the early movers as of the first day:
- C2ME 0.4.2-alpha.0.91, with a fix for unsigned integer maths near the world origin alongside the version bump.
- Simple Voice Chat 2.6.24, an alpha build, as it did for snapshot 1 a week earlier.
Both of those are mods with narrow surface areas – one touches chunk management, one touches networking. Neither touches rendering, which is where 26.4 has been making changes.
What is not moving yet
The rendering layer, predictably. Sodium, Iris and the shader packs are all still on 26.3, and 26.4 Snapshot 2 moved the cloud pass, renamed a core shader and added two new ones for sky occlusion.
That means the practical state of a 26.4 test client right now is: it runs, you can load Fabric API and a handful of utility mods, and it looks like vanilla. If you want to see the new fog and sky rendering, that is fine, because that is a vanilla feature. If you want to see it with shaders, wait.
Should you build a snapshot profile
For most players, no. Snapshot 2 of a cycle is early, the mod set is thin, and nothing you install will carry over cleanly.
For two groups, yes. Mod authors, obviously – the libraries being ready is the signal that you can start. And server operators who need to move promptly at release, because finding out in October which of your thirty mods has no 26.4 branch is much better than finding out on release day.
Either way, a separate profile and a throwaway world. The usual rules for keeping a modded install stable apply double during a snapshot cycle.
What to watch
The next meaningful marker is Sodium. Once the renderer moves, the shader layer follows within a week or two, and after that the content mods have no reason to wait. Until then, 26.4 is a vanilla-plus-utilities proposition.
The other thing to watch is whether the pack format numbers hold. 122.1 and 99.0 are provisional, and a change there mid-cycle would reset some of this work.
Reading a support matrix
YACL publishes one with every release, and the habit of reading it generalises. The three things a matrix tells you that a version number does not: which game versions a build targets, which loaders it covers, and whether a release is a forward port or a parallel branch.
The failure mode it prevents is installing the highest version number on the wrong game version. That produces a crash on startup with a stack trace that names a missing class, which reads as a mod bug and is not one.
Setting up a snapshot profile safely
Separate game directory, not just a separate profile. Sharing a directory between a release and a snapshot means sharing the mods folder, the config folder and the saves folder, and world data written by a snapshot cannot be read by the release it came from.
Copy a world in if you want to test against real terrain, never point the snapshot at the original. That single mistake is the most common way people lose a long-running world during a snapshot cycle.
Images: Macaw’s Trapdoors project gallery.