Tags
Creators
Details
Licensed LGPL-3.0-only
Published 10 months ago
Updated 5 days ago
All versions
1.26.9.6
Release
Villager API 1.26.9.65 days ago 99
Compatibility
Minecraft: Java Edition
26.4-snapshot-1
26.3
Platform
NeoForge
Supported environments
Client and server
Changes
- Added village_types directory to villager packs to register new village types for a biome with complete control of how it'll look
- Added village_structures directory to add structures to existing vanilla villages or custom villages even from other mods as long as they follow the vanilla convention
- Multiple VillagerPacks adding villager types to the same biome will be handled properly now instead of clashing and every pack will get to have its villager type in the same biome
- Trade merging, overriding, priority and ordering have been added with many other customizations
- Completely overhauled and improved the VillagerPack generator over at https://villagerapi.neoterra.online
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:9Tp2Becg:PFy0GyPd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9Tp2Becg:PFy0GyPd"
}

