Links
Tags
Creators
Details
2101.2.0-build.35
Compatibility
Changes
[release] Version 2101.2.0-build.35 -- fix refactor(network): 迁移网络通信至 NeoForge Payload 系统
移除基于 LowDragLib2 的 RPC 网络实现 (CYRPCPacket) 引入标准的 NeoForge Payload 数据包系统 重构网络处理逻辑,新增 NetworkHandler 统一处理数据包 实现了一系列 Payload 类用于处理配置同步、日志请求和 Toast 通知 fix(client): 优化提及配置界面的交互逻辑
修复提及类型主开关与通知开关的联动逻辑,确保禁用时正确锁定子选项 优化全局设置与特定类型设置的生效优先级判定 调整群发提及开关的显示状态,现在会正确响应全局开关的变化 chore(ci): 优化发布工作流
在构建前添加 runData 步骤,确保生成的数据包被正确打包
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:wPqAfquN:zGDt5aJy"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wPqAfquN:zGDt5aJy"
}

