Links
Tags
Creators
Details
Licensed MIT
Published 3 months ago
Updated 2 months ago
All versions
v0.5.6-1.21.11
Release
WeGui v0.5.6-1.21.113 months ago 162
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Changes
v0.5.6 - 2026-07-26
[Bug Fix - 选区渲染]
- 修复选区边框透视(throughView)关闭无效的问题: · 1.21.1:用 RenderSystem.enableDepthTest/disableDepthTest 替代 GL11,并在每次 malilib 调用前重置 depth test 状态,避免 malilib 内部 RenderType 覆盖 · 1.21.11:malilib 0.27.x 的 RenderSystem 无 enableDepthTest 方法,改用 GL11.glEnable/glDisable(GL_DEPTH_TEST)
- 修复关闭透视后红绿蓝三色区域轮廓线消失的问题(1.21.11):
· malilib renderAreaOutline 内部固定使用 NO_DEPTH_NO_CULL Pipeline(始终透视),无法通过外部 GL 状态关闭
· 新增 renderAreaOutlineLequalDepth:用 RenderContext + DEBUG_LINES_MASA_SIMPLE_LEQUAL_DEPTH Pipeline
- 反射调用 malilib private drawBoundingBoxLinesX/Y/Z 绘制 12 条边(每轴 4 条,红/绿/蓝三色)
- 完全模仿 malilib drawBoundingBoxEdges 流程(builder.build() → ctx.draw(rendered, false, true)) · throughView=false 时区域轮廓线被世界方块遮挡(不再透视),throughView=true 时仍用 malilib 原方法(透视)
- 补全 1.21.1 和 1.21.11 缺失的半透明白色侧面渲染(renderAreaSides,alpha=0.4)
[Bug Fix - 1.21.11 构建]
- 修复 1.21.11 build 失败:malilib 0.27.0 的 RenderSystem 没有 enableDepthTest/disableDepthTest 方法,用 GL11 替代
[Bug Fix - 汉化]
- 补充 1.21.1 malilib 缺失的汉化 key:malilib.gui.button.config.gui.tab.all = "全部"
[Note - 渲染系统说明]
- malilib 0.27.x(1.21.11)采用 RenderPipeline(非 RenderType),通过 RenderPass.setPipeline() 强制覆盖 GL 状态
- 各渲染方法 Pipeline 行为: · renderAreaSides:固定 LEQUAL_DEPTH(始终不透视) · renderAreaOutline:固定 NO_DEPTH_NO_CULL(始终透视,已通过自定义 LEQUAL_DEPTH Pipeline 绕过) · renderBlockOutline:第 5 参数 throughView 控制 Pipeline 选择
- 1.21.11 BufferBuilder.build() 返回 MeshData(对应 malilib 编译时 class_9801 接口)
[Known Limitation]
- 1.21.11 开启透视时,半透明侧面(renderAreaSides)受 malilib 限制仍不透视(LEQUAL_DEPTH 固定)
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:M28QtA4l:JIQT6S83"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:M28QtA4l:JIQT6S83"
}

