Links
Tags
Creators
Details
26.3.1
Compatibility
Changes
Mojang has just released the latest drop, so our mod is now available on version 26.3, Wilderness Bound. With this release, we’re also introducing a new versioning system for the mod.
- The mod now supports Minecraft 26.3.
New versioning system:
We’ve changed the versioning system to make it easier for users to understand. From now on, the version number itself tells you which Minecraft version that release of the mod is compatible with.
The new version number consists of two parts:
Minecraft version . Mod release number
The first part indicates the Minecraft version the mod is made for, while the second part indicates which release of the mod this is for that Minecraft version.
For example, 26.2.1 means:
- 26.2 - the Minecraft version this mod release supports.
- 1 - the first release of the mod for Minecraft 26.2.
This makes it possible to tell the supported Minecraft version and the mod's release number at a glance.
Enjoy exploring...
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:BZiSN452:oaW8EJHg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BZiSN452:oaW8EJHg"
}

