Tags
Creators
Details
All versions
1.10.1.0
Release
1.10.1.0 - Detection Improve3 months ago 1,785
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
Platforms
Folia
Paper
Purpur
Changes
1.10.1.0 - Detection Improve
Detection Improvement
- Add option to ignore artificial air.
Code Clear Up
- Completely removed the code related to
air monitor.
Configuration Item Changed
Before:
cave:
air-threshold: 14 # When the number of air blocks reaches several, the player is considered to be in a cave?
CaveAirMultiplier: 5 # If cave air is found, regarded as how many ordinary air?
detection-range: 3 # 3 = 7x7x7, 2 = 5x5x5
check_skip_vl: true # VL add of whether or not to skip natural behavior
# Prevents players from manually creating air to bypass detection.
air-monitor:
enable: true # Enable or disable
min-path-length: 10 # Minimum digging path required to perform this detection.
air-ratio-threshold: 0.3 # Air percentage threshold (e.g., 0.3 for 30%).
violation-increase: 1 # The value of the increase in rating after each triggered violation.
violation-threshold: 5 # The number of ratings reached should be flagged as suspicion of deliberate creation of artificial air.
remove-time: 20 # How long to remove this record once (in minutes)
Now:
cave:
air-threshold: 14 # When the number of air blocks reaches several, the player is considered to be in a cave?
CaveAirMultiplier: 5 # If cave air is found, regarded as how many ordinary air?
detection-range: 3 # 3 = 7x7x7, 2 = 5x5x5
check_skip_vl: true # VL add of whether or not to skip natural behavior
ignore-artificial-air: true # When true, ignore recently player-created air when checking for caves
artificial-air-remove-time: 20 # Minutes to consider broken blocks as artificial air
Recommend update to this version.
Recommend to rebuild the config.yml
Happy using~
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:O3VQnhG2:h8P6KBel"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:O3VQnhG2:h8P6KBel"
}

