All versions
1.7.0
Beta
Pueblo_vivo 1.7.0last month 183
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
Changelog
1.7.0 - Opt-In Village Management Update (2026-08-14)
This update was shaped directly by community feedback. Pueblo Vivo no longer assumes control of every village the player visits.
Opt-in village management
- New villages remain fully vanilla until the player explicitly registers them with Pueblo Vivo.
- Existing villages already stored in a world remain registered and keep all their progression data.
- Automatic registration is disabled by default through the new
auto_register_villagescommon config option. - Modpack authors can restore the previous behavior by setting
auto_register_villages=true.
Registration controls
- Normal use of the Citizenship Module opens the panel without registering a nearby village.
- Sneak-use the Citizenship Module to register a detected village and open its management panel.
- The dedicated village scan key remains an explicit registration method.
- Added clear English, Spanish (Spain) and Spanish (Mexico) instructions when viewing an unmanaged village.
Vanilla interaction compatibility
- Unregistered villagers retain their normal vanilla trading interaction.
- Pueblo Vivo custom trade listings are only generated for villagers inside registered settlements.
- Reputation-based price adjustment only intercepts villagers belonging to registered settlements.
- Personal villager stories now use sneak-right-click, leaving normal right-click available for trading.
- Village reputation penalties, chest ownership, golem interactions, zombie-villager aid and nearby combat rewards now require a registered Pueblo Vivo village.
Compatibility
- No world migration is required.
- No existing registered village is removed or reset.
- Unregistered villages are ignored by Pueblo Vivo simulation, stories, projects and economic systems.
- Dedicated-server behavior remains authoritative and configurable.
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:eHek4dwc:C34ClE9m"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eHek4dwc:C34ClE9m"
}

