The most impactful change is that the Registry class is now split into 3 different classes: Transfer API: add several helper APIs for fluid interactions and storage.Overwriting Screen Handler Factory: open new screen handlers without re-centering the mouse pointer.FabricLanguageProvider: easily generate language JSON files with data generation.Block Appearance API: groundwork for cross-mod connected textures.Resource Loader: support Text as pack display name.Resource Conditions: support all tags.Entity Events: add AFTER_DEATH, AFTER_DAMAGE, and ALLOW_DEATH events.Client Tags: allow client-side mods to rely on tags not present on the server.Content Registries: register villager interactions, sculk sensor frequencies, and path node types (aws404, Shnupbups, devpelux).Item API: support stack-aware recipe remainders.New Fabric API featuresįabric API added many features since the last update blog post: The old ID fabric still works in, such as depends however, the new ID is recommended for better user experience when Fabric API is missing. The mod ID of Fabric API is now fabric-api. Minecraft 1.19.3 introduces numerous breaking changes to major developer-facing APIs. ![]() Fabric changesĭevelopers should use Loom 1.0 (at the time of writing) to develop for Minecraft 1.19.3. Here are the list of all major modder-facing changes in this version.Īs usual, we ask players to be patient, and give mod developers time to update to this new version. As such, the changes in this version affect almost all mods (not even comparable to the changes in 1.18.2, and significantly bigger than 1.19). Beginning with this update, Mojang have changed their versioning scheme such that ‘minor’ releases like this one may contain larger changes under the hood. Minecraft 1.19.3 is almost here, with big changes to game internals.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |