2.1.30-fabric-26.1.2
Compatibility
Required content
Changes
2.1.30 sign translation hotfix
Fixes signs not showing translations on the Fabric 26.x builds.
修复 Fabric 26.x 构建上告示牌不显示翻译的问题。
- From Minecraft 26.1 on,
AbstractSignRenderer.submitSignTexttakes aSignTextargument instead of the oldboolean front. Both sign injections still targeted the old descriptor and, carryingrequire = 0, were skipped silently — translated sign text was never registered. - 自 Minecraft 26.1 起,
AbstractSignRenderer.submitSignText的参数由boolean front改为SignText。两个告示牌注入点仍指向旧签名,且带require = 0,被静默跳过——译文从未写入渲染数据。
NeoForge 26.x already used the new signature and is unaffected. Other loader/version builds remain 2.1.28 / 2.1.29 until rebuilt.
NeoForge 26.x 早已使用新签名,不受影响。其余加载器/版本仍为 2.1.28 / 2.1.29,直至后续重建。
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:FA8IDhfO:atyQd6my"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:FA8IDhfO:atyQd6my"
}

