Links
Tags
Creators
Details
Licensed GPL-3.0-only
Published 5 months ago
Updated 2 months ago
All versions
1.0.0
Release
MCA Reborn x Vampirism Compat 1.0.05 months ago 2,241
Uploaded by
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Unavailable version
Unavailable version
Changes
1.0.0 - Initial Release
- Initial release of MCA Reborn x Vampirism Compat.
- Adds compatibility between Minecraft Comes Alive Rebornand Vampirism.
- Allows MCA villagers to become vampires, hunters, or werewolves without being replaced by vanilla entities, aggressive villagers, or full vampire/werewolf entities.
- Preserves MCA villager identity, including appearance, family, relationships, profession, and social data.
- Adds configurable visuals, attributes, AI behavior, and faction rules for vampire, hunter, and werewolf villagers.
- Adds curing for MCA vampire and werewolf villagers using Weakness II, a Golden Apple, and Vampirism Garlic Injection.
- Adds faction-based trade and social interactions, with trade price modifiers applied safely.
- Adds faction-based MCA command permissions, respecting commands such as Follow and Stay.
- Adds Easy Villagers integration, including faction-based pickup permissions, pickup blocking during curing, and special Trader block behavior.
- Adds safer handling for Vampirism village capture events, preventing unsafe replacement of MCA villagers.
- Special villagers can ignore common hostile mobs and avoid inappropriate panic behavior.
- MCA special guards continue defending villages against common hostile mobs, even as vampires, hunters, or werewolves.
- Adds configuration options for factions, curing, combat, MCA commands, Easy Villagers, monster behavior, village capture, and debug.
- Includes final release polish, configuration improvements, and documentation cleanup.
Optional dependencies
Unavailable version
Unavailable version
Unavailable version
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:kYO3VpZg:sUWAsaUW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kYO3VpZg:sUWAsaUW"
}

