Tags
Creators
Details
2.1.0
Compatibility
Changes
Village Quest 2.1.0 - Prosperity & Prestige Village Quest now gives successful villages a real long-term economy—and makes the entire journey clearer, smoother, and more rewarding.
New features Invest Crowns into the Apiary, Forge, Market, Pasture, and Road Watch across three permanent ranks. Unlock lasting discounts, safer trade routes, Pilgrim commissions, and five useful village services. Build a ten-piece prestige collection, including five caravan liveries whose colors match the merchants, route map, and minimap. Track your complete economy through a new ledger for earnings, spending, purchases, investments, services, and bonuses. Use the new five-tab Prosperity board, clearer locked-quest requirements, staged objectives, progress sounds, and Questmaster chat announcements. Existing worlds upgrade smoothly: completed projects and trade routes immediately unlock their matching economy content. Bug fixes and improvements Quest hand-ins now verify and consume every required item correctly instead of allowing incomplete deliveries. Wheat, Potato, Carrot, ore, and Fortune-sensitive objectives count the real item yield instead of only the broken block. The Master's Edge and other production quests now progress through clear, dependable stages. Completed objectives, missing items, Weekly and Story timers, category badges, and locked requirements are easier to read and behave consistently. Journal, Quest Board, Pilgrim Trader, Caravan Ledger, Route Office, and Prosperity now scale consistently between fullscreen and maximized windows. Currency displays, buttons, icons, scroll handles, map navigation, and Journal return behavior received a complete visual polish. English, German, and Spanish quest text and the wiki now consistently explain fresh work, stored deliveries, and final Questmaster hand-ins. Available for Minecraft 26.2, 26.1.2, and 1.21.11.
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:EjOOpuxe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eJsPPGy9:EjOOpuxe"
}

