Tags
Creators
Details
2.1.0
Compatibility
Changes
Adds management commands for managed villagers: /vte select, /vte deselect, /vte tp, /vte tphere, /vte moveto, and /vte list. Each managed villager gets a persistent ID, assigned lazily on chunk load. Managed villagers no longer fall on spawn — gravity is disabled, and re-applied to existing ones on chunk reload.
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:ki2hRsud:Msh5kZhg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ki2hRsud:Msh5kZhg"
}

