Links
Tags
Creators
Details
Licensed Apache-2.0
Published 5 months ago
Updated last month
All versions
4.0.0
Release
Realistic Villagers 4.0.0 Settlements & traitslast month 58
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.3–1.20.6
1.20–1.20.1
1.19.x
1.18.x
Platforms
Folia
Paper
Purpur
Spigot
Changes
Realistic Villagers 4.0.0 Settlements & traits update
Added:
- Settlements: a bell now makes a real village with a name, borders and residents, drawn on a per-player radar map
- Mayors and elections: villagers stand for office with electoral programmes that change what building costs and how fast it goes up; players and villagers both vote
- Village economy: all 13 vanilla professions produce goods, each with a secondary trade, and raw materials are refined into building materials for the settlement's shared stores
- Village storage players can deposit into and withdraw from, from the chest GUI or the hologram menu
- Commission buildings from the mayor: a ghost preview before you commit, gradual construction block by block, and clearance/collision checks so settlements don't overlap themselves. Buildings go up exactly as they were found — floor, roof and all — whether that's on the ground or cut into it
- Blueprints read straight from vanilla .nbt structures and WorldEdit .schem files, both without adding a single dependency
- Regionality for blueprints: blueprints/<region>/ per village type plus allbiomes/, so a desert village is offered desert architecture and a taiga is not
- Discovery: walk into a village and its buildings become blueprints you can raise elsewhere. Works on villages this plugin never designed, so datapack architecture can finally be reused. Recorded per player, and each building is recognised on a later visit so it's never learned twice
- Graves for villagers who die without a cross, built from block and text displays, with the parents and the manner of death written on them
- Villager names shown only to the player looking at them (nametags.only-when-looking, nametags.look-range), off by default
- Settlement crafting recipes
- Appearance traits: Every villager is born with their own height, and female villagers can also have a body-shape trait derived from their skin palette., and every woman with a figure drawn from the colours of her own skin. Players can get one too. Follows the pose — swimming, gliding, crawling, sleeping — and never lingers behind after she dies or the player leaves. Needs 1.21.4+; below that the whole feature stays off rather than half on
- Weight is a separate body-shape trait with its own toggle (appearance.build), and is available for male villagers as well.
- The resource pack that carries the shapes is written by the plugin and served over HTTP to players as they join (appearance.serve-pack, pack-port, pack-host), so nobody installs anything by hand. If it can't reach a client, that client just gets the plain model instead of a broken placeholder
- Holograms and the radar map are private to the player who opened them, including players who join while one is already drawn
- %player-name% and %villager-name% placeholders work in any hologram text
- village.build.discovery-limit: how many buildings one village may contribute
- gender-selection.allow-change: whether /gender may change an answer already given, for servers that want to reopen the question. Off by default, matching how it already worked
- ValhallaMMO integration: with its premium trading module installed, the villager menu's "Trade" button opens Valhalla's own custom-merchant interface instead of vanilla trading, converting the villager into one of Valhalla's merchants the first time it's used. Falls back to ordinary trading for any villager Valhalla has nothing configured for
Fixed
- Villagers could vanish mid-tick while farming on some server forks
- An item a villager wasn't meant to keep could be duplicated: it was handled and then also placed in her inventory
- Anvil GUI works again on 26.2
Patch
- Village data — villages.yml, graves.yml, recorded villages and discovered blueprints — now lives in the world it describes, so deleting a world takes it with it. An old villages.yml left in the plugin folder is migrated automatically
- Starter blueprints ship with the plugin, so a fresh install already has something to build
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:DsLlIJOY:TkOR0Nag"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DsLlIJOY:TkOR0Nag"
}

