• 2/12/21 3:38 pm
- 11.2k views • 1 today
- save_alt 787 downloads
- Compatibility
- Minecraft 1.21
- Changes include
- Advancements
- Functions
- Predicates
6
Hi,
TLDR: I created an AntiCheat Datapack and need people to contribute and test.
I created a configurable AntiCheat Datapack for Minecraft Java that is called "NoCheatMinus". This datapack is inspired by the functionality of NoCheatPlus, I tried to port many checks and functions of the original plugin to this Vanilla datapack. I spent some time creating it, but I got to a point where I wondered if this plugin is useful for somebody at all. This post isn't meant as a release or something, I just want to draw your smart eyes on it to achieve some use cases, issues-reports, contributions... I set up a discord server as well as a Minecraft-Test-Server (you're allowed to cheat on). It would be nice to find somebody who will help me extending and testing the datapack, maybe somebody even wants to contribute to this Datapack. The Datapack is maintained on GitHub, so feel free to contribute to it at any time.
Demonstration: https://www.youtube.com/watch?v=q0wzirmrWhI
Test-Server: test.nocheatminus.org
Discord-server: https://discord.gg/PrW5FH25nn
GitHub: https://github.com/n33d4n4m3/NoCheatMinus
TLDR: I created an AntiCheat Datapack and need people to contribute and test.
I created a configurable AntiCheat Datapack for Minecraft Java that is called "NoCheatMinus". This datapack is inspired by the functionality of NoCheatPlus, I tried to port many checks and functions of the original plugin to this Vanilla datapack. I spent some time creating it, but I got to a point where I wondered if this plugin is useful for somebody at all. This post isn't meant as a release or something, I just want to draw your smart eyes on it to achieve some use cases, issues-reports, contributions... I set up a discord server as well as a Minecraft-Test-Server (you're allowed to cheat on). It would be nice to find somebody who will help me extending and testing the datapack, maybe somebody even wants to contribute to this Datapack. The Datapack is maintained on GitHub, so feel free to contribute to it at any time.
Demonstration: https://www.youtube.com/watch?v=q0wzirmrWhI
Test-Server: test.nocheatminus.org
Discord-server: https://discord.gg/PrW5FH25nn
GitHub: https://github.com/n33d4n4m3/NoCheatMinus
More like this
AntiCheat DatapackMinecraft 1.14 - 1.16 Server Utility Data Pack
blockmaster23
•6/1/20 5:22
15.6k 1.2k 4x 753
The Admin Tool - DatapackMinecraft 1.21 Server Utility Data Pack
Shinnyx
12/16/25 5:33
• posted 5/17/25 10:14
7.2k 992 15x 102721
Anti GamemodeMinecraft 1.15 - 1.21 Server Utility Data Packkotukedi
10/14/25 8:54
• posted 7/5/22 11:59
6.3k 588 4x 2910
Simple Anti-Cheat | Simple Cheat Detection | 1.13-1.21.5 v2.9.5Minecraft 1.13 - 1.21 Server Utility Data Pack
Elevated
•4/16/25 11:45
6k 689x 221
Datapack Utility LibraryMinecraft 1.14 - 1.20 Server Utility Data Pack
Lawliet843
•8/7/21 1:25
2.1k 81x 156
4966408
119
Have something to say?
Really cool!
What effect does this have on the TPS?
The performance impact seems to be low for now. Some checks require precise ray tracing and real-time calculation, which could mess the server up a bit, especially when there are 20-30 players online. Race-conditions and millisecond-timed checks are a big problem... These checks don't have much impact on the TPS-value though, but the TPS-value itself has a huge effect on these checks. When the server isn't running at exactly 20 ticks per second, the wrong race conditions in the datapack's code will win, important ticks get skipped and millisecond-timed checks will fail ... This leads to many false positives. I found some ways to detect server-side lag, I even found a method to determine how many ticks were skipped. With this information, checks and configs can be temporarily disabled or blunted ... An unsolvable problem is client-side / player lag. High-latency connections make packets accumulate, after a short time they'll arrive at the checks of the datapack - too late and too quick -> The check fails. I try to approach this problem with self-adapting configs for each player, using some kind of "machine learning" with Minecraft commands. It's a PoC for now ...