Differences

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

--- documentation:fabric_loom [2023/04/17 04:48] – [Useful tasks] solidblock
+++ documentation:fabric_loom [2023/12/22 14:39] (current) – Remove confusion around loom extracting nested jars. modmuss50
@@ Line 23: / Line 23: @@
 dependencies {
 	implementation project(path: ":name", configuration: "namedElements")
+}
+</code>
+If you are using splitsource sets in a multi-project build, you will also need to add a dependency for the other projects client sourceset.
+<code>
+dependencies {
+	clientImplementation project(":name").sourceSets.client.output
 }
 </code>
@@ Line 31: / Line 39: @@
 The following snippet from a build.gradle file shows how you can enable this for your mod. As your mod will now be split across two sourcesets, you will need to use the new DSL to define your mods sourcesets. This enables Fabric Loader to group your mods classpath together. This is also useful for some other complex multi-project setups.
+Minecraft 1.18 (1.19 recommended), Loader 0.14 and Loom 1.0 or later are required to split the client and common code.
 <code>
@@ Line 252: / Line 262: @@
   - Adds dependencies of Minecraft.
   - Downloads Minecraft assets.
-  - Processes and includes mod-augmented dependencies (and optionally extracts and remaps nested JARs).
+  - Processes and includes mod-augmented dependencies.
 ==== Caches ====
@@ Line 265: / Line 275: @@
   * ''minecraft'': Defines the version of Minecraft to be used in the development environment.
   * ''mappings'': Defines the mappings to be used in the development environment.
-  * ''modCompile'', ''modImplementation'', ''modApi'' and ''modRuntime'': Augmented variants of ''compile'', ''implementation'', ''api'' and ''runtime'' for mod dependencies. Will be remapped to match the mappings in the development environment and has any nested JARs removed. Nested JARs can optionally be extracted and remapped.
+  * ''modCompile'', ''modImplementation'', ''modApi'' and ''modRuntime'': Augmented variants of ''compile'', ''implementation'', ''api'' and ''runtime'' for mod dependencies. Will be remapped to match the mappings in the development environment and has any nested JARs removed.
   * ''include'': Declares a dependency that should be included as a jar-in-jar in the ''remapJar'' output. This dependency configuration is not transitive. For non-mod dependencies, Loom will generate a mod JAR with a fabric.mod.json using the name as the mod ID and the same version.