Links
Tags
Creators
Details
All versions
0.4.0-fabric
Beta
Multi Village Selector 0.4.011 months ago 37
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Server-side
Singleplayer
Required content
Any compatible version
Any compatible version
Changes
v0.4.0 Release Notes
🎮 Placement Control
MVS now controls village spacing directly - no more datapacks needed!
placement: {
"minecraft:villages": {
spacing: 34, // Grid cell size in chunks
separation: 8, // Buffer zone on edges
spreadType: "triangular", // linear, triangular, gaussian, etc.
}
}
Use /mvs info to see current placement values and their sources.
🔍 Locate Command
Find structures with /mvs locate <structure>:
- Autocomplete for all pool structures
- Click coordinates to teleport
- Use
/mvs locate <structure> morefor multiple results
🐛 Bug Fixes
- Spawn chunk fix: Villages now correctly spawn near world origin
- Biome sampling: Fixed position mismatch causing wrong biome detection
- Large structures: Added
relaxed_biome_validation: trueoption for mods with large villages (BCA, CTOV large, etc.)
✨ Quality of Life
/mvs help- now paginated with clickable navigation/mvs config fill-placements- auto-fill placement config with registry values/mvs structure nearby- structure IDs are now click-to-copy- Config auto-migrates from v0.3.x (adds
placement{}section)
🔧 Compatibility
- Tested compatible with C2ME (concurrent chunk generation)
- Tested compatible with Explorer's Compass (structure locations match
/mvs locate)
📖 Documentation
- New Spread Types Guide with visual diagrams
- Rewritten Spacing Guide for v0.4.0
- Updated all docs for new placement config format
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:35BiK2KV:M9v2ugW7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:35BiK2KV:M9v2ugW7"
}

