Links
Tags
Creators
Details
All versions
1.4.40
Release
[Let's Do] Vinery 1.4.40last year 652.6K
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client and server
Required content
Changes
[1.4.40]
Added
- Tooltips for all wine bottles now indicate their size (
smallorbig). - Wine bottle storage blocks now display tooltips specifying compatible bottle sizes (
smallorall sizes). - Japanese translation (Thanks to PExPE3)
- Bushy Leaves resourcepack is now bundled and supplied by default for forge as well
- Grapevine Leaves are now available again! They will grow near Grapevine Stems with Red Grape or White Grapes
Changed
- Added template models for most Vinery specific Blocks (e.g. Wine Racks, Wines) - this should reduce loading times
- Increased the
Completionist Bannereffect duration from 40 to 200 - Updated the
Overgrown Latticesadvancement description for better clarity - Replace
VineryIdentifierwithVinery.identifier- this should resolve Issues with Xaeros Map Mob Icons - Completely reworked Apple & Dark Cherry Trees - new Features, Textures and better functionality
- Wine aging now uses
getGameTime()instead ofgetDayTime()to prevent aging reset when using/time set - Wine age and upgrade progress calculation now use day-based precision instead of year rounding (Thanks to AverageChaos)
- Stackable logs now provide
1000smelting value, previously300 - Jungle Grapevine Blocks now use biome foliage tint
Fixed
- Resolved an issue where
Apple Leaveswere not properly registered as flammable Completionist Wall Bannernot having a Loottable- Fixed a crash when opening the Vinery creative tab caused by
ItemStackentries with a count greater than1 - Fixed a startup crash with Easy NPC caused by parallel modification of the strippables map during setup
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:1DWmBJVA:f2WnLIoU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1DWmBJVA:f2WnLIoU"
}![[Let's Do] Vinery](https://cdn.modrinth.com/data/1DWmBJVA/029aec55be4d860ba0aede4939dd93332b6dafad_96.webp)


