0.2.0
Compatibility
Changes
Reputation you can see — and change.
Villagers have always formed opinions about you. Minecraft has never shown them to you, and has never given you a way to influence them other than trading. Now it does both.
Added
Seeing where you stand
- New "How do you see me?" option showing how this villager regards you, as a named tier rather than a raw number: Reviled, Disliked, Stranger, Acquaintance, Trusted, Honoured.
- Tiers correspond to things you have actually done. Trading regularly makes you Trusted; curing a zombie villager is the only route to Honoured; hurting or killing a villager will drop you below Stranger — and villagers gossip, so their neighbours will hear about it.
- Reputation decays over time, so standing is something you maintain rather than bank.
Giving gifts
- New "Offer what you're holding" option. Villagers accept anything they would buy in their trades, plus any food — so what a villager wants varies with their profession and trade level.
- Food is welcome from anyone, so nitwits, the unemployed and babies can be befriended too, despite having nothing to trade.
- Gifts raise their opinion of you a little, and that goodwill fades more slowly than goodwill earned by trading. Gifting cannot take you all the way to Honoured, however generous you are.
- The villager visibly reacts — you can watch it happen behind the open dialogue.
Changed
- The dialogue is now multi-page, so conversations can go somewhere and come back.
- What a villager says is now composed on the server rather than assembled by the client, and wraps properly across lines. Groundwork for longer, more varied dialogue.
Notes
- Network protocol version raised to
2. Clients and servers must both be on 0.2.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:ziojWVp0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ccEZGZf7:ziojWVp0"
}

