Tags
Creators
Details
1.7.0+mc26.1.x.neoforge
Compatibility
Changes
Meow Anti-Xray 1.7.0 更新日志
这是面向 Minecraft 26.1 / 26.1.1 / 26.1.2 的 1.7.0 版本。Fabric 与 NeoForge 分别提供安装文件,要求 Java 25。
- 新增
/antixray config生效配置摘要与/antixray validate只读预检。 - 重载前验证配置;失败时保留原文件及上次有效运行配置,支持 UTF-8 BOM。
- 同步性能诊断和可重复压测工具,异步队列默认保持 16。
- 同步可退出的 bStats 客户端;默认
service-id=0,尚未激活上报。 - Fabric 要求 Loader 0.19.5 或更新版本,确保实际联机时区块发送注入正常。
- 修复 NeoForge 26.1 / 26.1.1 的方块破坏事件兼容,避免因事件类改名导致启动失败。
验证
- 完成双 loader 单元测试、发布构建与实际安装服启动。
- 26.1、26.1.1、26.1.2 两端均通过 2 客户端 / 25 秒区块收发与重写检查,0 错误。
- 配置预检、正常重载、错误重载保留原保护及 UTF-8 BOM 检查通过。
- NeoForge 三个补丁版本均通过真实挖掘验证。
Meow Anti-Xray 1.7.0
This release brings the 1.7.0 version line to Minecraft 26.1, 26.1.1, and 26.1.2. Separate Fabric and NeoForge files are provided; Java 25 is required.
- Adds
/antixray configfor effective configuration and/antixray validatefor read-only preflight checks. - Validates before reload; invalid files and the last known good runtime configuration are preserved. UTF-8 BOM is supported.
- Updates pressure diagnostics and repeatable test tools; the default async queue remains 16.
- Includes the optional bStats client; submission remains inactive with the default
service-id=0. - Requires Fabric Loader 0.19.5 or newer for compatible chunk-send mixin processing during player login.
- Fixes block-break event compatibility on NeoForge 26.1 / 26.1.1 so the older event name no longer prevents startup.
Validation
- Passed dual-loader unit tests, release builds, and standalone packaged-jar startup.
- Both loaders on 26.1, 26.1.1, and 26.1.2 passed two-client / 25-second chunk delivery and rewrite checks with zero errors.
- Passed config preflight, reload, invalid reload preserving protection, and UTF-8 BOM checks.
- All three NeoForge patch versions also passed an actual block-break check.
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:8pl8obwY:QhBYGBHB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8pl8obwY:QhBYGBHB"
}

