create sth.beta
Major update Snapshot version: Main update: GUI, removed support for 1.11 and below, added support for 1.17-.20.4. Now supports 1.12-1.20.4! Refactored version, resolved some security issues.
This update brings improvements to core detection logic, adds new checks for specific cheating behaviors, and makes the system more stable and efficient.
- Mining Behavior Analysis Improvements
FVD (Value Density): We've improved how mining area is calculated by using an octree structure—faster and more accurate. Only recent mining activity is considered, so old actions don’t skew results. We’ve also added a decay system for value weights to prevent players from "farming" low-value blocks to game the system. TAS (Abnormal Mining Frequency): In addition to tracking average mining intervals, we now pay special attention to rapid bursts—like mining 3 or more diamonds within 2 minutes. These kinds of patterns are now flagged more aggressively. H_norm (Exploration Spread): We estimate how spread out a player’s mining locations are using the octree, then divide that by the number of mining points. A higher score means the player is mining in a very tight area—often a red flag. TA (Suspicious Camera Movement): We now monitor how much a player’s view angle (especially Yaw) changes while moving. If the camera barely moves—like it’s locked in place—it may indicate automated or bot-like behavior, common in "mine-to" cheating. 2. New: Auto Tool Switch Detection
Some cheats automatically switch to the best tool (e.g., switching to a diamond pickaxe when mining diamonds). We’ve added protection against this:
The system logs when a player switches tools. If someone switches tools very quickly (e.g., under 100ms) and always ends up with the optimal tool, they gain points toward an "auto-tool" score. If this score gets too high, the player is flagged immediately—even if other metrics look normal—and will be kicked with a high violation level. 3. Response & Admin Alerts
Kick rules still follow the QSS score tiers (0.2, 0.4, 0.6, 0.8), now enforced more consistently. When a player hits QSS 0.4 (watch), 0.6 (low alert), or 0.8 (medium alert), online admins with permission will get a clear in-chat alert with the player’s name, dimension, and current risk level. At QSS 0.8, the player is kicked with a message showing their violation level and recommended action. A SEVERE log entry is also written to the server log. 4. Sensitivity & Punishment Settings
You can adjust detection sensitivity using /adsar sensitivity. This affects thresholds like what counts as a high-value ore. Violation Level (VL) is simply QSS × 100. Players are kicked when VL ≥ 80. The new auto-tool detection can push VL straight to 90+, allowing fast response to clear threats. 5. Performance & Stability
Heavy tasks like data scanning and deep analysis now run in background threads—no more lag on the main server thread. Mining positions are managed with an octree, making area and spread calculations much faster. Thread-safe collections (like ConcurrentHashMap) are used where needed, balancing safety and speed. Old data (mining logs, view history, effort records) is cleaned up regularly to prevent memory leaks. 6. Code Cleanup
Removed unused imports, variables, and dead code. Added clear comments to key logic for easier maintenance. This update strengthens protection against modern cheating tactics—especially mine-to and auto-tool hacks—without increasing server load. Feedback is welcome.
the first.