Tags
Creators
Details
1.9-2.0.0-31
Compatibility
Changes
speedynutty68: Massive refactors + move to Forge persistent registry
speedynutty68: Fix NPE in registry
speedynutty68: Move constants to main mod class
speedynutty68: Move entries to a map
speedynutty68: If no author is set, display owner modid if advanced tooltips
speedynutty68: Fix ordering on entry display
speedynutty68: Fix wildcard usage in recipe renders
speedynutty68: Pass 1 at cleaning up the JSON system
speedynutty68: Remove raw GL calls from buttons
speedynutty68: Fix lighting issues when main hand was rendered
speedynutty68: Another case of the lighting issue
speedynutty68: Run formatter
speedynutty68: Fix syncing of current page
speedynutty68: Decrease registry size
speedynutty68: Merge GuiHomeNew into GuiHome
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:EM9fahS3:Co0svMJu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EM9fahS3:Co0svMJu"
}

