Tags
Creators
Details
26.1-3.1+mod-neoforge
Compatibility
Changes
#12 Migraded to Version 26.1.1
Made minor changes to the dimension type to add compatability with the new version. Changed version numbers to include the newer version.
#13 Reworked Mod packages (only fabric)
In the last update, I added proper mod packages for Minecraft version 1.21.11. For the new version, however, I had to redo the whole thing for several reasons. The consequence of this is that it no longer relies on the architecture API, but is now fully independent. However, this also forced me to choose an ecosystem, as I had to code everything separately for Fabric and Neoforge.
As there is more demand for the Fabric version, I will discontinue the NeoForge packaging and only create standard packaging similar to past versions. I apologise for this. However, if demand persists, please contact me on GitHub and I will consider it.
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:ycIKn71C:OJkm3yDA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ycIKn71C:OJkm3yDA"
}

