1.3.2-mod
Compatibility
Changes
#1.3.2 - Hotfix
For the sake of ease-of-use, I've determined that it's better to split Vanillabean into two files, meaning a separate file is now used for the resource pack, and the main file is only used as the data pack file.
Misc. Changes
- Data and resources are now in separate files
- Updated the welcome screen for players accordingly
Bug Fixes
- Some errors appear in the logs when loading the Vanillabean file
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:LEcw1HH7:h5gHugan"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LEcw1HH7:h5gHugan"
}

