Tags
Creators
Details
1.0.0-universal
Compatibility
Changes
One jar for every loader and game version this mod supports, instead of one download per combination.
It bundles 21 builds: Fabric 1.15.2 through 26.2, Forge 1.16.5 through 1.20.1, and NeoForge 1.21.1 through 26.2. At startup a small bootstrap asks the loader which game version it booted and loads the matching build.
Why a bundle rather than one shared set of classes: the same code has to reference different Minecraft names depending on where it runs. Fabric ships intermediary names, NeoForge ships the official ones, older Forge ships SRG. Those cannot live in the same class file, so each build is kept separate inside the jar and stays invisible to the loaders' annotation scanners until it is needed.
Marked beta on purpose. The version selection and the class loading are covered by tests, but no build inside this jar has been started on a live server yet. The individual per-version downloads are unchanged and still the safe choice.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:XORScBSo:kfhG1PPf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XORScBSo:kfhG1PPf"
}

