Differences

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

--- documentation:fabric_loader [2019/06/07 21:38] – [Entrypoints] jamieswhiteshirt
+++ documentation:fabric_loader [2019/06/08 06:44] – [Nested jars] Some lil misspells :) falseresync
@@ Line 13: / Line 13: @@
 Fabric Loader makes all mods equally capable of modifying the game. As an example, anything Fabric API does can be done by any other mod.
-==== Nested jars ====
+==== Nested JARs ====
-A mod may bundle a number of other mods within its jar. See the [[https://fabricmc.net/wiki/tutorial:loader04x#nested_jars|guidelines]] for how to use nested jars effectively. Nested jars must be declared by their paths relative to the containing jar's root. A nested jar must itself also be a mod, which again can have nested jars. Fabric Loader will load nested jars while attempting to satisfy dependency constraints.
+A mod may bundle a number of other mods within its JAR. See the [[https://fabricmc.net/wiki/tutorial:loader04x#nested_jars|guidelines]] for how to use nested JARs effectively. Nested JARs must be declared by their paths relative to the containing JAR's root. A nested JAR must itself also be a mod, which again can have nested JARs. Fabric Loader will load nested JARs while attempting to satisfy dependency constraints.
-Nested jars allow a mod to provide its own dependencies, so Fabric Loader can pick the best version matching the dependencies instead of requiring separate installation of dependencies. They also allow clean packaging of submodules, so each module can be used separately. Non-mod libraries can be repackaged as mods for nested jar usage.
+Nested JARs allow a mod to provide its own dependencies, so Fabric Loader can pick the best version matching the dependencies instead of requiring separate installation of dependencies. They also allow clean packaging of submodules, so each module can be used separately. Non-mod libraries can be repackaged as mods for nested JAR usage.
-When loaded, nested jars are loaded into an in-memory file system using jimfs, then added to the classpath.
+When loaded, nested JARs are loaded into an in-memory file system using jimfs, then added to the classpath.
 ==== Entrypoints ====