Multi-Loader

Choosing the common plugin

While these plugins are completely fine to work in simple, single-loader projects, they are really design to improve multi-loader setups using multiple sub-projects without having to add the same tons of boilerplate code everywhere.

Since there are multiple plugins serving the function of a common sub-project, here is a table of when it makes sense to use which one.

Plugin	When to use
com.possible-triangle.common	Starting with 1.21.1
com.possible-triangle.architectury	Required if a common module from a dependency also used architectury loom
com.possible-triangle.vanilla	Minecraft 1.20.1 and below

Cross-Module Dependencies

Dependencies between the different sub-projects can be defined using the dependsOn method withing the loader's extension block. These will already add source sets & merge outputs in the final JAR's, no extra configuration needed.

Examples

Multiple examples can be found in the example repository. Below is a basic example of a multi-loader project on minecraft 1.21.1 and above.

build.gradle.kts

plugins {
    id("com.possible-triangle.core")
    id("com.possible-triangle.common") apply false
    id("com.possible-triangle.forge") apply false
    id("com.possible-triangle.fabric") apply false
}

subprojects {
   // only required if you want to already configure something
   // plugin related withing this "subprojects" block
    apply(plugin = "com.possible-triangle.core")

    upload {
      maven {
         githubPackages()
      }
    }
}

common/build.gradle.kts

plugins {
    id("com.possible-triangle.common")
}

neoforge/build.gradle.kts

plugins {
    id("com.possible-triangle.neoforge")
}

neoforge {
    dependOn(project(":common"))
}

fabric/build.gradle.kts

plugins {
    id("com.possible-triangle.fabric")
}

fabric {
    dependOn(project(":common"))
}