Creators
Details
1.7.10-bcaa364
Compatibility
Required content
Changes
ci: 版本号改为 MC版本-git短hash,每次push自动发版Modrinth
版本号格式:{minecraftVersion}-{shortHash},如 1.7.10-8a4f47e。 jar 文件名标注 MC 版本,每个 commit 对应一个唯一版本。
- publish-modrinth.yml: 每次 push 到 1.7.10 自动构建发版;版本号 从 gradle.properties 读 MC 版本 + git 取短 hash;发布前检查 Modrinth 是否已有同版本号,重复则跳过(重复 push 不报错); 上传前重命名 jar 为带 MC 版本的标准名。
- build-and-test.yml: 监听分支从 master/main 改为 1.7.10(与 实际主分支对齐,使 CI 生效)。
单 jar 双兼容(原版 CustomNPCs + CustomNPC+),无需区分宿主发版。
Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com
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:5skiXDDB:lXJuY79V"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5skiXDDB:lXJuY79V"
}

