Tags
Creators
Details
2.6.1
Compatibility
Required content
Changes
Village Quest 2.6.1 β Living Kingdoms
Living Kingdoms comes to Minecraft 26.2 with the same current content as 26.3, plus the complete 2.6.1 fixes.
Living Kingdoms arrives on Minecraft 26.2
- Build your community. Name a settlement, establish a Council Seat, inn, market and storehouse, and earn five stages of recognition.
- Meet the people. Named village staff and rare inn guests bring daily life and personal adventures. Travel with Simon, chart Lutte's coastal signals and stand watch with Marius.
- Open your market. Assign up to five trader places, discover regional goods and connect villages through trade, supply and friendship agreements.
- Earn lasting tools. Claim the Village Seal, recover personally earned guild tools and follow all five chapters of The Unwritten Promise.
- Choose your rhythm. Journal settings offer real-time or Minecraft-day resets and personal presentation options, alongside refreshed maps, objectives and medieval interfaces.
Fixes and improvements
- Reliable compact Notice Post fallback and retrofit, with protection for existing builds and removed boards.
- General recipe-book search, separate output entries and native plank ingredients.
- Quest Board timer positioning, title/scroll fixes and corrected terrain-map sampling.
- Adult-only village introductions, clearer building checks and all five village chapters explained in game.
- Revised English, German and Spanish quest instructions and material names.
Minecraft 26.2 Β· Fabric + Fabric API Β· Java 25. Back up existing worlds and match client/server versions.
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:eJsPPGy9:NvOFDlpm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eJsPPGy9:NvOFDlpm"
}

