Tags
Creators
Details
1.1.0
Compatibility
Changes
Full Changelog: Here
- Fixed: The
/halo hidecommand failed to work correctly when the halo definition included a startup animation. - Fixed: Halo definitions in the server-side
datafolder were incorrectly overriding those inassets; thedatafolder has been removed, and all halo definitions are now centrally managed withinassets.
The version number has been updated to 1.1.0, signifying that no further major features will be added; instead, the focus will shift to addressing individual bugs and preparing for compatibility across multiple versions and loaders.
- 修复:当光环定义中含有startup动画,/halo hide指令无法正常生效
- 修复:服务端的data文件夹下的光环定义错误的覆盖了assets的光环定义,现已去除data文件夹,所有光环定义由assets统一管理
版本号变更为1.1.0,意味着接下来将不再添加大功能,而是进行逐项bug修复并着手准备多版本多加载器适配
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| halo-1.1.0-sources.jar | Source jar | 209.61 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:k2fEt5RO:O6CaihQS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:k2fEt5RO:O6CaihQS"
}

