Tags
Creators
Details
1.7.0
Compatibility
Changes
Legacy build for Minecraft 1.8 - 1.20.x (Java 8+). Use the Modern build for Minecraft 1.21 - 26.3.
This is the first release that loads on Minecraft 1.20.x and older. It is built from the same code base and uses the same configuration files, commands and features as the Modern build.
Added
- Legacy build without
api-version, compiled for Java 8. - Runtime compatibility layer for sounds, particles, titles, action bars, biomes, potion effects, item-in-hand checks and hex colors.
- Legacy
Effectparticles on 1.8, plusParticlenames when the server provides them. - Cross-version sound aliases in both directions, including chains such as
ENTITY_LIGHTNING_BOLT_THUNDER->ENTITY_LIGHTNING_THUNDER->AMBIENCE_THUNDER. - Cross-version particle aliases in both directions (
EXPLOSION<->EXPLOSION_LARGE,EXPLOSION_EMITTER<->EXPLOSION_HUGE,SMOKE<->SMOKE_NORMAL, and more). - Hex color fallback: on servers without
ChatColor#ofthe closest legacy color is used. - 1.8-compatible titles and action bars.
Fixed
- Epic thunder sound rejected on Minecraft 1.9 - 1.12.
- 1.16.5 particles rejected because 1.17 names were validated literally.
/cdmreloadaborted even when validation passed, due to a mis-encoded error check./cdmconfig validatecould report the wrong issue count./cdmbroadcast particleprinted a raw enum name instead of the configured name.- Default particles no longer depend on
Effect.CLOUD, which is missing from newer APIs.
Compatibility
| Build | Minecraft | Java |
|---|---|---|
| Modern | 1.21 - 26.3 | 21+ |
| Legacy | 1.8 - 1.20.x | 8+ |
Tested on Paper 1.8.8, 1.12.2, 1.16.5 and 1.20.6 with real deaths and epic effects. No configuration keys changed.
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:LrqgmmvZ:PmJDnFWl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LrqgmmvZ:PmJDnFWl"
}

