21.0.2
Compatibility
Changes
Bilingual v21.0.2 — 更新日志 🔧 改进与重构 模组正式更名:从 Template Mod 更名为 Bilingual,所有内部配置文件(Mixin 配置、mod ID 等)已统一更新 许可证变更:更新为 Apache-2.0 许可证 模组图标:新增自定义图标 assets/bilingual/icon.png 🛠️ 技术优化 Mixin 配置重命名:template-mod.mixins.json → bilingual.mixins.json 客户端 Mixin 配置重命名:template-mod.client.mixins.json → bilingual.client.mixins.json fabric.mod.json 结构优化,入口点与依赖声明更规范
英文版(Modrinth 英文更新说明) Bilingual v21.0.2 — Changelog Improvements & Refactoring Mod renamed: Changed from "Template Mod" to "Bilingual"; all internal config files (Mixin configs, mod ID, etc.) updated accordingly License update: Switched to Apache-2.0 license Mod icon: Added custom icon at assets/bilingual/icon.png Technical optimizations Mixin config renamed: template-mod.mixins.json → bilingual.mixins.json Client Mixin config renamed: template-mod.client.mixins.json → bilingual.client.mixins.json fabric.mod.json structure improved with cleaner entrypoints and dependency declarations
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:q6Xktg1R:fgkxCf5n"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:q6Xktg1R:fgkxCf5n"
}

