Tags
Creators
Details
Licensed ARR
Published 4 months ago
Updated last month
All versions
1.0.0-beta.8
Beta
Villager Retaliation! 1.0.0-beta.84 months ago 58
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
Added
- Villager recruitment: hire villagers (not implemented yet), make them follow you, dismiss them, and receive betrayal/death notices
- Villager inventory UI for high-reputation villagers, including visible equipment/armour slots
- Gift system with reputation effects, profession-based preferences, gift knowledge discovery, and high-reputation reward gifts
- Villager mood/disposition dialogue behaviour
- Grouped villager chat messages with profession-colored speaker labels for better legibility
Cover Them in Debrisadvancement- Villagers can flee natural hostile mobs when unarmed
Dialogue features are now data driven
- Dialogue is now loaded from datapack JSON
- Custom dialogue options can be added by packs/modpacks
- Notifications are now data driven with custom text, colours, triggers, filters, and world-text indicators
- Gifts are now data driven with item/tag selectors, profession rules, reputation values, and reward pools
- Villager preset names are now data driven
- Dialogue and notifications support locale overlays, with
en_usfallback
Improved
- Added gift info tooltip showing known liked/disliked gifts
- Added config for natural hostile detection radius
- Improved villager combat/equipment handling
- Improved reputation and ambient world-text notification visuals
- Clicking dialogue options no longer resets the menu scroll position
- Expanded README documentation for pack creators and translators
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:2ArcBjmC:nFAJWC6M"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2ArcBjmC:nFAJWC6M"
}



