Tags
Creators
Details
Licensed MIT
Published 3 years ago
Updated last year
All versions
2.2.0-fabric-1.20.1
Release
2.2.0last year 274
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Fabric
Quilt
Supported environments
Client and server
Changes
Old changes (~2023, unreleased until now):
- Start sketching out an API, accessible through
TemplatesClientApi.getInstance()- (Note from the future: This API will break hard in 1.21 due to Mojang fuckery)
- Code cleanups that hopefully didn't break ABI compat
- Remove some unused stuff from the jar
- Vertical slab placement is a little better
- Fix a bug where templates that look like blocks with randomized models, such as stone, could reroll their blockstate on every resource load
- Forgot to specify a random seed.
- Templated blocks always use the same model -- templated stone will still not be randomly rotated/flipped -- but at least now it uses the same same model.
New changes:
- New template: "Post Cross" - a plus shape that fits squarely on fences or the Post template. Can be placed in three different orientations.
- New template: "TNTemplate". This will end well.
- Connected textures should work! I tested with Chisel Reborn. Other blocks should be OK as long as they implement
FabricBlock#getAppearance. - Mushroom blocks now work (as well as any other blocks with
"multipart"models). - Very slightly reduce memory usage of
TemplateAppearance? - Only declare dependencies on the Fabric API modules I actually use.
TODO list:
- I still depend on two deprecated modules,
fabric-rendering-data-attachment-v1(has ABI implications) andfabric-models-v0(the replacement seems to befabric-model-loading-api-v1, and this also has ABI implications)
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:cL15qXuP:WterotfO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cL15qXuP:WterotfO"
}

