Links
Tags
Creators
Details
Licensed LGPL-3.0-only
Published 3 years ago
Updated 2 months ago
All versions
0.1.16-mc1.21.4
Alpha
0.1.16-mc1.21.42 years ago 5,910
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.4
Platform
NeoForge
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Changes
Change
- sync
sakura-ryoko/litematica1.21.4-0.21.0-sakura.5- Bump for MaFgLib 0.2.1 (MaLiLib 1.21.4-0.23.0-sakura.3)
- Includes Config Gui Registration code
- fix: Easy Place Protocol not applying all possible rotation Directional Block States.
- Temporarily Disable the Data Fixers while browsing files in order to load the file Metadata Info Pane faster than previously.
- Update Chinese lang files, thanks to DreamingLri and snowlinouo, and zly2006
- feat: renderInfoOverlay Hotkey is now defaulted to allow an Empty Keybinding to match the Config Comment; this allows you to 'empty' the key bind, and have Info Overlay to always be active.
- fix: Info Overlay not being able to see Empty Block Entities.
- fix: InfoOverlay getting confused with the ClientWorld
- feat/fix: add switchable AO Processor config,renderAOModernEnabled in order to disable / enable the 'new' AO Processor code; or continue using the older code from 2018 without the "Shadows" that it creates in between block layers.
- Port to 1.21.4
- Add Italian, & Ukrainian
- Add File Info for when you are browsing Sponge and Vanilla Structure files. Note, that as of now, it is temporarily loading the files in order to get the Metadata, and due to the Data Fixers, there is sometimes a delay in doing so the first time for each file. I plan on trying to speed that up in a future release.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| Forgematica-0.1.16-mc1.21.4-sources.jar | Unknown | 626.45 KiB |
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:dCKRaeBC:8kMwckUK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dCKRaeBC:8kMwckUK"
}

