Tags
Creators
Details
3.0
Compatibility
Changes
Changelog - NeoAntiXray V3
This update fixes the BlockBreakEvent crash, introduces the new /nax command, adds command auto-completion, improves compatibility with Paper 26.1.2, and enhances the TopLuck and Anti-XRay systems.
Fixed BlockBreakEvent Crash
Fixed the following error:
NoSuchMethodError: org.bukkit.Tag.isTagged(java.lang.Object)
NeoAntiXray no longer uses:
Tag.BASE_STONE_OVERWORLD.isTagged(...)
Instead, the plugin now uses manual stone detection fully compatible with Paper 26.1.2.
Tracked stone blocks:
STONE
DEEPSLATE
GRANITE
DIORITE
ANDESITE
TUFF
CALCITE
DRIPSTONE_BLOCK
Result:
- No more crashes when breaking blocks.
- Improved compatibility with Paper 26.1.2.
Added
New Main Command
Added a shorter command:
/nax
The original alias is still available:
/neoantixray
Available Subcommands
/nax topluck
/nax reload
/nax stats <player>
/nax history
/nax reset <player|all>
/nax help
Command Auto-Completion
Typing:
/nax
will automatically suggest:
topluck
reload
stats
history
reset
help
Typing:
/nax stats
will suggest online players.
Typing:
/nax reset
will suggest:
all
and online players.
Improved
Anti-XRay Alert System
Staff alerts are only visible to players with:
neoantixray.alerts
The anti-spam system remains active:
- One alert per vein.
- No more
x10,x9,x8,x7spam. - Immediate notification when a tracked ore vein is discovered.
TopLuck GUI
The /nax topluck GUI includes:
- Diamond / Stone percentage ranking.
- Sorting from highest percentage to lowest.
- Click a player head to view detailed statistics.
- Staff teleport button.
- Ore breakdown statistics.
- Suspicion score display.
Permissions
neoantixray.alerts
neoantixray.topluck
neoantixray.topluck.tp
neoantixray.command
neoantixray.admin
neoantixray.stats
neoantixray.history
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:7QeJs94Z:JPEPK4Zl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7QeJs94Z:JPEPK4Zl"
}

