Message API (experimental): server-side manipulation of messages sent to players.REPLACE runs before MODIFY, and if one mod replaces a loot table, the callback loop will exit early and no other mod can replace the loot table.
Additionally, LootTableLoadingCallback was replaced with LootTableEvents.REPLACE event (for replacing an entire loot table) and LootTableEvents.MODIFY event (for modifying part of a loot table). The new version uses interface injection and transitive access wideners to implement most of its functionalities. Loot API v2: replacement for the Loot Table API v1, with many improvements.Convention Tags: define standard tags that Fabric mods can use, and register vanilla entries to them.FluidVariant Attributes: define and access name, temperature, etc… of fluids.Transitive Access Widener module: directly use many private/protected classes and methods in vanilla.Resource Conditions: only enable select recipes, advancements, etc… when specific conditions are met.Entity API Lookup: flexible retrieval of object instances from entities.Data Generation: easily generate JSON files for blocks, recipes, advancements, etc… (modmuss50).New Fabric API featuresįabric API added many features since the last update blog post: In addition, Fabric has introduced several new ways for mod developers to safely develop server-side mods without accidentally relying on client-exclusive code. Minecraft 1.19 introduces several code changes to major developer-facing APIs. Fabric Changes For Mod Developersĭevelopers should use Loom 0.12 (at the time of writing) to develop for Minecraft 1.19. Please be patient as mod developers dedicate some of their free time to updating their mods to this new version. Plenty of mods have already updated to 1.19 already, and we expect many more to be on the way. Players should use Fabric Installer 0.11.0 and Fabric Loader 0.14.6 (at the time of writing) to play on Minecraft 1.19. Minecraft 1.19: The Wild Update is now released, and along with it, updates for Fabric itself and many mods already.
0 kommentar(er)
