Differences

This shows you the differences between two versions of the page.

--- tutorial:introduction [2019/11/03 14:56] – [Overwrite] layl
+++ tutorial:introduction [2019/11/03 23:10] – [Native Minecraft APIs] layl
@@ Line 25: / Line 25: @@
 A good example of this is the "Registry" class, which lets you add blocks and items without any modifications to Minecraft's code.
-Minecraft will also load in the JSON data files from your mod.
+Minecraft also uses JSON data files for various data-driven features.
 These JSON files are injected by the Fabric API (not the loader!).
-They're used for anything data-driven, where code isn't necessary in the first place.
 For example, block models and loot tables are implemented through JSON files.
@@ Line 47: / Line 46: @@
 Because the Fabric API is intentionally kept small and focused, third party APIs exist to fill in the gaps.
-Mixins allow any third party library to affect Minecraft's code just as much as the core Fabric API can.
+Mixins allow any third party library to affect Minecraft's code in the same way as the core Fabric API can.
 You should use these instead of writing your own mixins where possible to minimize the possibility for conflicts.
-A good example of this is [[https://github.com/cottonmc|Cotton]], which provides a variety of common utilities, as well as common resource ores, items and blocks.
+You can find an incomplete lists of [[documentation:libraries|third party libraries]] on this wiki.
 ===== Mixins =====