Remove MythicalAC: it kicked a whitelisted player for opening a door - #9
Merged
Merged
Conversation
The Phase check escalated a legitimate player from vl 13 to 25 during ordinary movement and disconnected them. Step had already been false-flagging an op just walking through terrain. Create contraptions, Waystones teleports and ~90ms latency to LON1 all produce the position desync these checks look for, so the false positives are structural here, not incidental. Nothing could be tuned. The mod ships no config file and generates none across restarts, so no threshold could be raised and no player exempted. Its jar is 60KB with 16 classes, it logs nothing server-side (alerts go only to ops chat, leaving no audit trail), every published build is tagged beta or alpha, and its package name com/serverguard does not match its own mod id. It also defended against a threat this server does not have. The whitelist is enforced, online-mode verifies every account against Mojang, and PvP is off, so there are no untrusted players and cheating harms nobody. What remains is the protection that actually works: PrismProtect block and chest logging with rollback, ProfanityGuard, disabled command blocks, spawn protection and forced gamemode. An alerting system that cries wolf is worse than none: it taught everyone to scroll past alerts, and then it removed a child from the game. Refs #8
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #8. Escalating from a review question to a fix: it kicked a whitelisted player for opening a door.
The
Phasecheck ran the player from vl 13 to 25 on ordinary movement and disconnected them.Stephad already been false-flagging an op just walking through terrain.The false positives are structural on this server, not incidental. Create contraptions, Waystones teleports and the ~90ms latency to LON1 all produce exactly the position desync these checks are built to detect.
Nothing could be tuned. The mod ships no config file and generates none across restarts, so no threshold could be raised and no player exempted. Its jar is 60KB with 16 classes, it logs nothing server-side (alerts go only to ops chat, so there is no audit trail), every published build is tagged beta or alpha, and its package name
com/serverguarddoes not match its own mod idmythicalac.It also defended against a threat this server does not have: the whitelist is enforced, online-mode verifies every account against Mojang, and PvP is off. There are no untrusted players, and cheating harms nobody.
What still protects the server: PrismProtect block and chest logging with rollback (which unlike this mod has a real config, writes to a database, and can undo damage), ProfanityGuard on chat,
enable-command-block=false,spawn-protection=16,force-gamemode=true, and PvP off.Mod count goes 26 to 25. Applying this restarts the container; the deploy gate health-checks and rolls back automatically if the server does not come up.
Wali, flagging you on this since it closes the issue assigned to you. If you want an anticheat back, the bar is: a config file, an ops exemption, and server-side logging.