Perhaps the biggest breaking change comes from a single word change...
Fabric API 0.79.1 was released, with breaking changes to Object Builder (FabricBlockSettings). This was followed by another patch update, 0.79.2, which fixes a mixin error.
Also, Loom 1.2 is out, with some changes to library handling, Kotlin support, and minimum Gradle version bumped to 8.1.
23w16a is here with tons of breaking changes. Yikes.
Fabric API received many breaking changes, specifically: Content Registries, Data Generation, Item Groups API, Object Builder, Rendering API, and Screen API. (Can you believe Screen API's patch version was 1.0.44 before the bump?)
VillagerPlantableRegistry was replaced with ItemTags.VILLAGER_PLANTABLE_SEEDS (data pack). For other changes, see below.
I'm sick rn.
Fabric API 0.77.1 contains yet another Object Builder breaking changes, to FabricMaterialBuilder and BlockSetTypeRegistry. A crash in Loot API was fixed in 0.77.2.
Unrelated to snapshots, but: last week, Fabric Networking API received a big update. Check https://gist.github.com/apple502j/9c6b9e5e8dec37cbf6f3916472a79d57 for more info.
23w12a is here with some changes to rendering (again!), sign, etc.
Fabric Loader 0.14.18 is released to handle the new 1.20 series. Fabric API 0.76.1 is released with, surprisingly, 0 breaking changes.
Since experimental features are no longer experimental, "OneTwenty" data generators were merged with vanilla ones. Legacy smithing table screen handler is also removed.
Five snapshots and we enter into the pre-release phase! Remember, this is when you should start porting mods (More precisely, pre-release 2 is a bit better IMO) - unless you have the special power of porting your mod every week, of course.
This past week was Fabric Toolchain Week. Fabric Loader, Fabric API, and libraries like Mixin have received many updates.
Note: this version is unstable and has several Mixin-related bugs, along with log display errors on MultiMC. Update is not recommended yet.
We thought 1.19.4 will soon come to pre phase, but guess what, we were wrong! From the country of cherry blossom trees, here's the 23w07a weekly snapshot update document.
Fabric API 0.74.1 was released. Object Builder API received some breaking changes, related to block settings, sign types, and entity types.
In addition, other parts of the platform code (such as Mixin and Loader) have received some changes, pending release. These will be released when they are ready.
Obviously, there's some sniffing mob, the second suspicious thing in the game, and a 1m cube of pink stuff, but hey we're talking about modding stuff!
It's been a year since the first post of the Snapshot Document Series! This will continue for the foreseeable future. Anyway, it's another frogging week and a snapshot update!
Fabric Loader 0.14.14 was released last week, fixing a bug where mod initializers were run a little bit later.
Fabric API for 23w06a, version 0.73.5, contains breaking changes to Item Group API, Indigo, Rendering API (v1), and Transitive Access Wideners.
It's been almost a year since the first "Snapshot Note" series! Anyway here's the 23w03a stuff info.
Fabric Loader 0.14.13 should be used for this version.
Fabric API 0.72.1 is released for this version. Biome API received 1 breaking change; setPrecipitation method in BiomeModificationContext.WeatherContext now takes a boolean.
Multiple S2C packets can now be bundled into a single packet, so that they are processed in the same client tick. The bundled packets are still sent separately, but is re-bundled in the client.
Fabric API 0.77.0 for 1.19.4 and 1.20 introduced a new way of writing networking stack. This applies to ServerPlayNetworking and ClientPlayNetworking. This is a guide on migrating existing code using Networking API v1 to new, packet-based code.
If you are still using the deprecated Networking API v0, it is recommended to switch to v1 first.
The new API makes some assumptions on the usage. While this covers most of the common and expected uses, there are cases where the old API still works better. Therefore, the old API is not deprecated in anyway. Also, the two APIs are network-compatible so long as the packet serialization is the same.
For example, you might want to continue using the old API if:
