1.1.0
Compatibility
Required content
Changes
🪨 EatAndesite 1.1.0
Forge 1.19.2 and 1.20.1 (and NeoForge 1.20.1 on that Forge jar) wouldn't start with the mod installed. Fixed — it boots and works again.
Dropped 1.18.2. Supported now: Fabric + Forge 1.19.2, Fabric + Forge 1.20.1 (same Forge file also runs on NeoForge 1.20.1), NeoForge 1.21.1.
Fabric and NeoForge need Architectury; Fabric also needs Fabric API. Forge needs nothing new. Create is still required on every version.
Eating andesite, the effects, the controls, and config/eatandesite.json — same as 1.0.0. Your existing config keeps working.
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:tqKHYR4U:WHa12Kbe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:tqKHYR4U:WHa12Kbe"
}

