All versions
0.8.1
Alpha
Villager Enhanced 0.8.13 months ago 6
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Client and server
Changes
Fixes from actually playing it.
Fixed
- Villager births were never announced. The birth half of 0.8.0's notifications did not work at all — it listened for an event that Minecraft does not raise for villagers. Breeding a pair now announces the child properly. Walking into a village that already contains children stays quiet, as it should.
- Several settings could not be changed. Voice volume and conversation range were decimal values shown as text boxes that refuse a decimal point, so they could only be set to whole numbers — voice volume was effectively off or full. Every numeric setting is now a slider.
- Villagers with no profession wandered off mid-conversation while everyone else stood and listened, and two players could talk to the same one at once. Both fixed; unemployed villagers now behave like the rest.
Changed
- Asking a villager's name now gets you an introduction. They tell you their name and greet you properly, rather than the window title quietly changing while they say "Hello" as though nothing had happened.
- Dialogue is paced more slowly by default — three quarters of a second per line rather than a quarter. Adjustable as before, including off.
Notes
- Voice volume and conversation range reset to their defaults when you update, because both changed form. Re-set them if you had tuned them.
- The notification radius maximum is now 256 rather than 512. Villagers beyond simulation distance are not running, so nothing happens out there to hear about.
- No protocol change; 0.8.1 talks to 0.8.0 clients and servers.
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:ccEZGZf7:k5coCZus"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ccEZGZf7:k5coCZus"
}

