Links
Tags
Creators
Details
Licensed Apache-2.0
Published 5 months ago
Updated last month
All versions
3.3.6.9
Release
Realistic Villagers 3.3.6.94 months ago 44
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
Platforms
Paper
Purpur
Spigot
Changes
Holograms and Life Ride Update
Added:
- A completely new villager menu system using holograms (if you preferred the old chest GUI, you can disable the holograms)
- Villagers can now ride camels and llamas
- The configuration file has been split into parts
- Option to disable recipes
- Ability to disable gender and assign a custom gender to each player
- Improved revive system: now a lightning bolt must strike within 2 blocks of the head for the ritual to begin in a more atmospheric way
- Players can create a special chest/barrel for a villager by placing a sign with the text [Villager] on the chest. They can also assign items that the villager can take
- A website for managing settings interactively (Currently inactive; I still need to refine this to account for regional differences.)
- Regionality system: an extensive system that influences villagers based on the region where they live. For example, in the desert, you’ll encounter villagers with darker skin tones, Arabic names, and conversations typical of desert dwellers; or perhaps in the snowy biome, villagers dressed in warm robes with Nordic names, speaking with an accent and constantly complaining about the cold (These options can be disabled and fully customized to your liking)
Fixed
- Revive works on newer versions
- Anvil GUI works again
- Villagers picking up items
- Taking items out of and putting items into containers
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:u4ry6vUt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DsLlIJOY:u4ry6vUt"
}

