Tags
Creators
Details
Licensed ARR
Published 3 months ago
Updated 2 months ago
All versions
1.0.0-beta.12-hotfix.2
Beta
Villager Retaliation! 1.0.0-beta.12-hotfix.22 months ago 2,748
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
Added
- Added non-binary villager gender support across social data, breeding compatibility checks, profile/family UI labels, deterministic preset-name selection, and English localization.
- Added new config options related to villager breeding rules.
- Added five new built-in Village Supply quests:
beetroot_bundle,bottle_stock,egg_baskets,feather_fletching, andtorch_bundle, each with authored quest definitions, dialogue trees, loot tables, and player-wiki coverage. - Added
/villagerretaliation profile set_genderso operators can set a villager's stored gender directly in-game. - Added more preset villager names to the built-in male and female name pools (non-binary villagers will pool from both of these).
Changed
- Villager gender chosen through the new command is now persisted on the villager so profile data and future loads keep the override.
- Added skill-based trade-level XP scaling driven by the villager's primary profession skill, including persisted fractional progress so slowed or boosted trade XP carries cleanly across trades.
- Merchant trade UI now displays the adjusted trade-level XP gain using synced villager profile data instead of showing stale vanilla-only values.
- Skill-based trade leveling now guarantees at least 1 visible trade-level XP from XP-bearing trades, matching the updated config tooltip and avoiding zero-looking progress on valid trades.
Fixed
- Fixed skill-based trade-level XP progress desync between server-side villager leveling and the client merchant display.
- Fixed adjusted trade XP being lost between trades by syncing and caching the remaining fractional progress in villager profile payloads.
- Fixed merchant result and container flows bypassing adjusted trade-level XP presentation after a trade completed or when trade offers refreshed.
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:SGWvoBnC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2ArcBjmC:SGWvoBnC"
}



