Gradle Configurations

Gradle configurations are named groups of dependencies and artifacts.

These configurations add dependencies to the compile or runtime classpaths. All of them are available in all Fabric Loom and Architectury Loom projects (as of 1.1).

All of these configurations have mod* variants such as modImplementation to use when depending on a mod. The dependency will get remapped to the project mappings and added to the correct mod classpaths.

Others won't see the configurations marked with “Not published” when they depend on your project.

• include: Bundles a mod or a library within your mod.
• forgeRuntimeLibrary (added by Architectury Loom in Forge mode):
  • Adds a library to the runtime classpath for Forge.
  • Note: mods should not added to it! Use one of the configurations above instead.
• namedElements
  • Contains the raw mod jar produced by the current project.
  • This is an outgoing configuration that is primarily intended for use in project dependencies, e.g. project(path: ':common', configuration: 'namedElements').

• development(Fabric|Forge|Quilt|NeoForge)
  • Used in platform modules for the common module in Architectury mods so that Architectury Transformer can apply its changes (@ExpectPlatform etc.)
• transformProduction(Fabric|Forge|Quilt|NeoForge)
  • Contains the transformed classes of the common module for bundling in production mod jars for the individual platforms.
  • Note: this is an outgoing configuration of common Architectury subprojects. it should only be depended on in platform projects!

• shadow (added by the Shadow plugin)
  • Includes runtime dependencies that are not bundled into the all jar created by the shadowJar task.
  • This is often confusing since modders often talk about “shadowing” dependencies when they mean including them using Shadow.
  • See also: Shadow User Guide: Configuring Shadow