Links
Tags
Creators
Details
Licensed MIT
Published 2 months ago
Updated 5 days ago
All versions
1.5.0+mc26.2.neoforge
Release
Meow Anti-Xray 1.5.0 (NeoForge)5 days ago 15
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Server-side
Singleplayer
Changes
Meow Anti-Xray 1.5.0 更新日志
这是面向 Minecraft 26.2 的双 Loader 性能基线版本。
性能基线
- 新增可重复的 Fabric / NeoForge 压力矩阵工具,统一记录版本、JDK、CPU、配置校验和、区块吞吐及反矿透运行时指标。
- 完成 Fabric 与 NeoForge 在 8 个网络假玩家、90 秒 spectator 跑图路线下的 queue
0 / 16 / 32 / 64筛选。 - 默认
async-queue-size保持为16,优先保证异步任务可以收敛并控制内存压力。 - queue
32和64可作为高内存服务器的手动调优选项,但应结合/antixray profile观察inFlight、同步 fallback 和压力状态。
兼容性
- 支持 Minecraft
26.2与 Java25。 - Fabric 与 NeoForge 行为保持对齐。
验证
- 双 Loader 压力样本均为 8/8 客户端进入 play、0 runner errors,并产生非零区块重写任务。
- 完整矩阵与重复样本记录在
reports/1.5.0-pressure-matrix.md。
Meow Anti-Xray 1.5.0 Changelog
This is the dual-loader performance baseline release for Minecraft 26.2.
Performance Baseline
- Added repeatable Fabric and NeoForge pressure-matrix tooling that records versions, JDK, CPU, config checksums, chunk throughput, and anti-xray runtime counters.
- Completed queue
0 / 16 / 32 / 64screening with eight network fake players on a 90-second spectator route for both loaders. - Kept the default
async-queue-sizeat16to favor bounded work and predictable memory pressure. - Queues
32and64remain available as manual tuning options for servers with more memory; use/antixray profileto watchinFlight, sync fallback, and pressure.
Compatibility
- Supports Minecraft
26.2and Java25. - Fabric and NeoForge behavior remains aligned.
Verification
- Every loader sample reached play with 8/8 clients, zero runner errors, and visible rewrite activity.
- The complete matrix and repeat samples are recorded in
reports/1.5.0-pressure-matrix.md.
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:Bkv4fcCA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8pl8obwY:Bkv4fcCA"
}

