Links
Tags
Creators
Details
Licensed GPL-3.0-only
Published 5 months ago
Updated 3 months ago
All versions
1.0.0
Release
MCA Reborn x Easy Villagers Compat 1.0.05 months ago 1,716
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Unavailable version
Unavailable version
Changes
1.0.0
- Adds compatibility between Minecraft Comes Alive Reborn and Easy Villagers.
- Allows MCA villagers to be picked up, stored and restored without converting them into vanilla villagers.
- Preserves the main MCA villager data, including appearance, name, gender, personality, genetics, family, relationships and profession.
- Prevents duplication issues during the pickup and restoration process.
- Renders MCA villagers correctly in the inventory, hotbar, GUI and supported Easy Villagers blocks.
- Adds support for the Trader, Breeder, Farmer, Converter, Incubator and Iron Farm blocks.
- Allows MCA babies to be generated in the Breeder when both parents are MCA villagers.
- Preserves MCA babies in the Incubator and safely updates their MCA age data.
- Implements a safe path for the Converter, correctly applying the cure reputation result.
- Prevents MCA villagers from opening the vanilla trading screen when picked up.
- Stored MCA villagers now display the villager's name.
- Adds a highly configurable sound system for stored villagers.
- Allows you to freely choose the sound type used by stored villagers: MCA sounds, vanilla/Easy Villagers sounds or no sound.
- Allows sounds to be configured by action and by block, defining which actions and blocks should use MCA sounds, vanilla sounds or remain silent.
- Keeps compatibility, rendering and debug options available for troubleshooting and modpack use.
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:b4MlkT3O:CHLYlFmg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:b4MlkT3O:CHLYlFmg"
}

