Tags
Creators
Details
1.8.0
Compatibility
Required content
Changes
BREAKING CHANGES!
This version uses a new system to store JSON Data inside Customizable Signs. Therefore, all the signs need to be re-initialized. Flying near them will reinitialize them completely, but there is a chance (even though I didn't experience it while testing) that customizable signs are built across two or three chunks. If one of them is not loaded, reinitialization will fail. In that case, please reinitialize manually by shift+right clicking any sign block that's part of the sign and click "Make master and initialize".
The ID of the "Upside Down Triangular Sign Block" changed due to a typo. I have implemented data fixers, though they are not working properly and the sign simply does not render/display. Therefore, replacing all upside down triangular signs is necessary. I am deeply sorry about the inconvenience.
Key changes:
- Rewrote most of JSON logic on Customizable Sign
- UX improvement
- Bug fixed
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:eiibqIju:30NoX578"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eiibqIju:30NoX578"
}

