v2.3.0+mc26.2
Compatibility
Changes
The latest version (stable for mc26.2) is now available, bringing massive improvements to customization, balancing, and performance for your villagers! Here are the main highlights:
Passive Healing Customization: A new slider lets you set the minimum profession level (Novice to Master) required for villagers to heal passively. Additionally, the UI now automatically grays out sub-options if general regeneration is disabled, complete with clear dependency warnings (⚠️ REQUIREMENT:).
New Sequential "Checking Pipeline": The server-side logic has been completely restructured! Passive healing now runs smoothly every game tick, filtering conditions in a strict sequence: Global Healing ➡️ Damage Delay ➡️ Bed Usage ➡️ Profession Level.
Advanced Forge (BETA): You can now customize the maximum enchantment cap that Armorers, Weaponsmiths, and Toolsmiths can sell directly via the configuration file, adding even more value to the end-game economy!
Dynamic Reputation & Economy: The system now handles both positive values (triggering automatic discounts/deflation) and negative values (triggering price increases/inflation). If left at 0, standard Minecraft Vanilla behavior takes over seamlessly, fully preserving mechanics like Hero of the Village and permanent zombie curing discounts.
Bad Gossip Blocking: Features a surgical new check that intercepts negative reputation points, preventing villagers from holding an eternal grudge against the player if you accidentally hit them. The vanilla Decay system remains untouched, allowing time to naturally clear your history.
Optimization & Stability: Restructured code introduces "Fall-Fast" micro-performance optimizations to save CPU cycles when updating entire village AIs. It also features crash-proofing to ensure full compatibility with heavy AI optimization mods (like Lithium).
⚠️ Compatibility Note: We have identified a critical conflict with the Visible Traders mod. A preventative hard lock has been added to the Fabric initializer to prevent crashes until a permanent structural fix is implemented in a future update.
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:Yf8KPA8u:nDUVEdJ3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Yf8KPA8u:nDUVEdJ3"
}

