Tags
Creators
Details
Licensed MIT
Published 5 months ago
Updated 3 weeks ago
All versions
1.3.1+neoforge
Release
Meow Anti-Xray 1.3.1 (NeoForge)4 months ago 42
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Server-side
Singleplayer
Changes
Meow Anti-Xray 1.3.1 更新日志
这是面向 Minecraft 26.2 的 Paper parity 小版本。
Paper 对齐
- 假块选择的运行期随机种子改为非零
ThreadLocalRandom,再沿用 xorshift 与无符号 bounded scaling,更贴近 Paper anti-xray 的随机假块选择方式。 - 补充 Paper transparent override 回归测试,锁定 spawner、barrier、shulker box、slime block、mangrove roots 不作为实心遮挡参与暴露判断。
兼容性
- 继续支持 Minecraft
26.2。 - Fabric / NeoForge 依赖范围不变。
验证
node --check tools\mc-2612-load-runner.js.\gradlew.bat clean test :neoforge:test releaseAllLoaders --console=plain- Fabric
runServer真实启动通过,2 个 Minecraft 26.2 假网络玩家 RCON spectator 跑图26s:chunks=4980、batches=383、errors=0,/antixray profile显示rewriteTasks=4980。 - NeoForge
:neoforge:runServer真实启动通过,/antixray status确认loader=neoforge, version=1.3.1, minecraft=26.2;短跑图中假玩家可登录和 RCON 传送,但本地短测未触发 chunk rewrite,后续仍需继续跟进 NeoForge 压测链路。
Meow Anti-Xray 1.3.1 Changelog
This is a Paper parity patch release for Minecraft 26.2.
Paper Parity
- Fake block selection now uses a non-zero
ThreadLocalRandomruntime seed, followed by xorshift and unsigned bounded scaling, closer to Paper anti-xray's random fake block selection. - Added regression coverage for Paper transparent overrides, locking spawner, barrier, shulker boxes, slime block, and mangrove roots as non-solid blockers for exposure checks.
Compatibility
- Continues to support Minecraft
26.2. - Fabric / NeoForge dependency ranges are unchanged.
Verification
node --check tools\mc-2612-load-runner.js.\gradlew.bat clean test :neoforge:test releaseAllLoaders --console=plain- Fabric
runServerreal startup passed. A 2-client Minecraft 26.2 RCON spectator smoke ran for26swithchunks=4980,batches=383,errors=0, and/antixray profilereportedrewriteTasks=4980. - NeoForge
:neoforge:runServerreal startup passed, and/antixray statusconfirmedloader=neoforge, version=1.3.1, minecraft=26.2. The short local run allowed fake clients to log in and receive RCON teleports, but did not trigger chunk rewrite work; the NeoForge pressure path still needs follow-up.
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:93NGZNWg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8pl8obwY:93NGZNWg"
}

