Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated 6 days ago
All versions
1.20.1-1.6.4
Release
Vintage Fabric 1.20.1-1.6.46 days ago 33
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client and server
Changes
Changelog
1.20.1-1.6.4-fabric
Added
- Ported Create: Vintage 1.6.4 from Forge to Fabric for Minecraft 1.20.1.
- Added support for Create Fabric
6.0.8.1+build.1744-mc1.20.1. - Added support for KubeJS Fabric
2001.6.5-build.26. - Added KubeJS Create Fabric
2001.2.5-build.1as a required standalone dependency instead of embedding it in the Vintage mod JAR. - Added JEI and Jade to the development environment.
- Added Startup and Server script documentation with Vintage recipe examples.
- Added Forge-compatible millibucket amounts to Vintage recipe JSON files.
Fluid amounts such as
250,500, and1000are converted internally to Fabric Fluid Units.
Changed
- Converted Forge-only item and fluid tags in recipes and data assets to Fabric-compatible common tags.
- Updated KubeJS recipe schemas and syntax for the current Fabric versions.
- Removed the HeatJS integration because HeatJS is not available for Fabric.
- Reworked the compressed iron sheet recipe condition for the Fabric mod set.
- Kept KubeJS Create Fabric as an external dependency so it can be updated and used independently.
Fixed
- Fixed Curving Press recipes ignoring every curving head except the convex curving head.
- Fixed Recipe Cards being impossible to insert into the Lathe again after removal.
- Fixed secondary Pressurizing fluid outputs being displayed as internal Compressor contents.
- Fixed incorrect fluid amounts and suspicious fluid amount warnings caused by Fabric Fluid Unit differences.
- Fixed Vintage processing recipes serializing and deserializing fluid amounts inconsistently between JSON, KubeJS, JEI, and machine processing.
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:qVZh767G:qZVJT4be"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qVZh767G:qZVJT4be"
}

