Fabric Wiki

User Tools

Site Tools

Trace:
documentation:fabric_loader

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
documentation:fabric_loader [2020/02/22 00:55] – General cleanup jamieswhiteshirtdocumentation:fabric_loader [2022/03/18 05:17] – [Nested JARs] solidblock
Line 4: Line 4:
  
 Fabric Loader has services to allow mods to have some code executed during initialization, to transform classes, declare and provide mod dependencies, all in a number of different environments. Fabric Loader has services to allow mods to have some code executed during initialization, to transform classes, declare and provide mod dependencies, all in a number of different environments.
 +
 +For each Fabric Loader version, there is Javadoc available at
 +<code>https://maven.fabricmc.net/docs/fabric-loader-[loader version]</code>
 +For example, Fabric Loader 0.11.1's documentation is at https://maven.fabricmc.net/docs/fabric-loader-0.11.1/
  
 ===== Features ===== ===== Features =====
Line 19: Line 23:
 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. A mod may bundle a number of other mods within its JAR. 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. A mod may bundle a number of other mods within its JAR. 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 are not extracted, they are instead loaded in in-memory file system using jimfs. 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.+Nested JARs are not extracted, they are instead loaded in in-memory file system using jimfs. See the [[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.
  
 ==== Entrypoints ==== ==== Entrypoints ====
documentation/fabric_loader.txt · Last modified: 2023/12/27 12:57 by 194.190.81.32