Tags
Creators
Details
Licensed LGPL-3.0-only
Published 4 years ago
Updated 2 years ago
All versions
4.4.12-1.7
Release
Village Names 4.4.12 for JE 1.72 years ago 513
Compatibility
Minecraft: Java Edition
1.7.10
Platform
Forge
Supported environments
Client and server
Changes
- Bugfix: You can once again obtain Codices from librarians and cartographers, sorry about that.
- Added "Villager makes book" config option which lets you turn off the feature where villagers generate village books
- Renamed "Villager drops book" config option to "Villager drops book/codex" because it applies to both. If you changed this value from the default, you may need to change it again.
- Added "Villagers offer Codex trade" config option, where Librarians and Cartographers will sell you Codexes in the ordinary trade way. The original idea for acquiring the Codex item was going to be through a villager trade, but due to my lack of experience and the lack of ways to easily modify villager trades in 1.8, I scrapped this idea in favor of the right-click-with-emerald method in use since Village Names version 1.1 back in 2017.
- "Villager makes codex" is now false by default, to allow the Codex trade to be the preferred acquistion method.
- If "Codex Chest Loot," "Villager makes codex," and "Villagers offer Codex trade" are all false, Librarian and Cartographer villagers should no longer offer treasure trades, because you have no way to obtain Codices, and therefore no way to obtain the specialized books required for those trades.
- Structure foundations should now use cobblestone instead of dirt when in ocean, river, beach, mesa, or mountain biomes
- Changed the "Concrete Well" config option to clarify that it only applies to old-school wells: i.e. if "Activate New Village Generator" is false.
- Fixed Swamp Small House 2 foundation
- Optimized some code
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:ea7aacaC:PkFP27os"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ea7aacaC:PkFP27os"
}
