Tags
Creators
Details
Licensed MIT
Published 4 months ago
Updated 2 days ago
All versions
1.4.0+neoforge
Release
Meow Anti-Xray 1.4.0 (NeoForge)3 months ago 81
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Server-side
Singleplayer
Changes
Meow Anti-Xray 1.4.0 更新日志
这是面向 Minecraft 26.2 的配置安全与诊断版本,合并了原计划中的 1.3.2 与 1.4.0。
配置检查
- 新增 OP-only 只读
/antixray config,可在游戏、控制台和 RCON 查看当前实际生效的全局、异步及分维度配置摘要。 - 新增 OP-only 只读
/antixray validate,在不应用配置的情况下检查磁盘文件,并报告 YAML 格式、布尔值、数值范围、维度、未知方块 ID、空替换列表和重复方块等问题。 - 验证结果会明确显示是否可以安全执行 reload。
安全重载
/antixray reload现在先完整验证候选配置,再一次性切换运行态。- 配置读取、格式或方块校验失败时,不覆盖原配置文件,也不使用部分解析结果。
- 运行中 reload 失败会继续使用最后一次有效配置,避免意外削弱反矿透防护。
- 首次启动遇到已有但无效的配置时,保留该文件,并使用内存中的安全默认配置启动。
兼容性
- 支持 Minecraft
26.2与 Java25。 - Fabric / NeoForge 依赖范围不变。
Meow Anti-Xray 1.4.0 Changelog
This Minecraft 26.2 release combines the previously planned 1.3.2 diagnostics work with the 1.4.0 configuration-safety iteration.
Configuration Checks
- Added OP-only read-only
/antixray configfor effective global, async, and per-dimension configuration summaries in game, console, and RCON. - Added OP-only read-only
/antixray validate, which checks the file on disk without applying it and reports YAML syntax, boolean values, numeric ranges, dimensions, unknown block ids, empty replacement lists, and duplicate blocks. - Validation clearly reports whether reload is safe.
Safe Reload
/antixray reloadnow fully validates a candidate configuration before atomically switching the runtime state.- Read, syntax, or block validation failures no longer overwrite the existing file or activate partially parsed values.
- A failed runtime reload retains the last-known-good configuration so protection is not unexpectedly weakened.
- If an existing config is invalid during first startup, the file is preserved and safe in-memory defaults are used.
Compatibility
- Supports Minecraft
26.2and Java25. - Fabric and NeoForge dependency ranges are unchanged.
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:fa0kDZLe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8pl8obwY:fa0kDZLe"
}

