Tags
Creators
Details
Licensed MIT
Published 3 years ago
Updated last year
All versions
2.3.0-fabric-1.20.1
Release
2.3.0last year 83
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Fabric
Quilt
Supported environments
Client and server
Changes
- Fix messed up Fence Template and Post Template items from last update.
- Add a tooltip to the Slope and Tiny Slope templates reminding you that they can be placed sideways on walls by holding Shift.
- Retexturable models (for "json" and "auto" types), as well as item model overrides, can now be loaded out of a resource pack.
- See the json files lurking in
assets/templates/. - This isn't too useful, since the models only make sense when applied to a block from Templates.
- The existing code-registration API still works. These are dubbed "permanent" mappings (since they aren't cleared on resource reload).
- Permanent mappings can be overridden with resource-pack ones.
- See the json files lurking in
- More datagen.
- Potential ABI break: Use
fabric-block-view-api-v2instead of the deprecatedfabric-rendering-data-attachment-v1.- This means I use
RenderDataBlockEntityinstead of the deprecatedRenderAttachmentBlockEntityto read information about templates from the world. - If you implement
ThemeableBlockEntity, please implementThemeableBlockEntity2instead. However, the old interface has been changed to extend the new interface and forward calls fromfabric-rendering-data-attachment-v1, so addons should still work.
- This means I use
- Potential ABI break: Use
fabric-model-loading-api-v1instead of the deprecatedfabric-models-v0.- Due to shortcomings of this API (no ability to directly set an
UnbakedModelfor items), Template items now need an arbitrary json item model to suppress "missing model" logspam. - In the future I intend to make fuller use of the features afforded by this library.
- Due to shortcomings of this API (no ability to directly set an
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:xnfgHkgk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cL15qXuP:xnfgHkgk"
}

