Tags
Creators
Details
1.2.0
Compatibility
Required content
Changes
Vintner 1.2.0
Vintner 1.2.0 significantly expands wine identity, cellar storage, ageing vessels, and estate-level collection management.
Added
- Persistent wine provenance from pressing through fermentation, barrel ageing, and bottling, including grape variety, batch day, winery origin, and producer.
- Almanac reports for provenance, bottling day, and concise recommendations for whether a bottle should be held, enjoyed now, is past its peak, or spoiled.
- Vintage Archives that catalogue up to sixteen unique wine batches without consuming their bottles.
- Vintage Archive variants for all twelve supported wood families.
- Chestnut and neutral ageing barrels with distinct ageing characteristics.
- Eight-bottle large casks with their own capacity, ageing speed, quality, style affinity, and tasting character.
- Barrel stands.
- Labelled Cellar Shelves for storing a single batch.
- Tasting Cabinets for mixed-vintage collections.
- Persistent wine style and estate identity.
- Fuller body-aware tasting notes.
- Estimated wine trade value.
- Cellar prestige.
- Expanded cellar evaluation including temperature stability and nearby machinery disturbance.
Changed
- Wine quality now influences:
- Food pairing strength
- Low-quality fault risk
- Estimated trade value
- Future settlement-prestige contribution
- Labelled Cellar Shelves and Tasting Cabinets now age stored bottles.
- Storage furniture exposes accurate visual fill states.
- Wine metadata is retained through retrieval and save/reload.
- New cellar storage blocks support comparator output.
Compatibility
- Minecraft 26.2
- Fabric Loader
- Fabric API
Vintner remains under active development. Mechanics, balance, models, and compatibility may continue to evolve in future releases.
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:KHJlVyMX:11UW8ERY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KHJlVyMX:11UW8ERY"
}

