0.3.0
Compatibility
Changes
Villagers have names, and they talk about you behind your back.
Minecraft villagers have always gossiped. Each one forms its own opinion of you, and they pass those opinions around when they meet. You have never been able to see any of it. Now you can ask.
Added
Names
- Every villager has a name. Names are distinct within a village, so you can tell one farmer from another.
- Villages in different biomes draw on different names, so a desert settlement sounds unlike a taiga one.
- Names are remembered. They survive world reloads, and a villager who is zombified and later cured comes back as the person you knew.
- Name a villager with a name tag and that name wins, as you would expect.
- The trade screen is now titled with the villager's name rather than their job.
Rumours
- New "What do the others say about me?" option. The villager tells you what nearby villagers think of you, naming them so you know who to thank — or who to apologise to.
- Up to four opinions, strongest first. Someone who resents you surfaces just as readily as someone who admires you.
- The interesting part: villagers you have never met can still have an opinion, because they heard it from someone who has. Trade fairly with one farmer and word gets round. Hurt someone and word gets round just as fast.
Changed
- Villagers now carry saved data of their own. Existing worlds are fine — villagers are named the first time you meet them, with nothing to convert.
- Dialogue can show several lines of speech, which is what makes rumours readable.
Notes
- Network protocol version raised to
3. Clients and servers must both be on 0.3.0. - Requires Minecraft 26.2 and NeoForge 26.2.0.48-beta, as before.
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:JwFewLxA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ccEZGZf7:JwFewLxA"
}

