MatrixConfig

The optimized config for Matrix Anticheat, a powerful anticheat for Minecraft.

This config works for both the free and premium versions of Matrix.
Make sure to use the config meant for the version of Matrix you use!
_{Sometimes Matrix premium updates faster than free, there will be another config file if so.}

• Less false positives.
• Better warning messages.
• More strict checks. (Better detection)
• Multiple config types to suit your needs.
• Up to date!

1. Download checks.yml, error.checks.yml, or cloud.checks.yml depending on what you want.
   _{For specific Matrix versions, head to the releases page.}
2. Rename the original checks.yml to something else. checks.old.yml will work.
3. Upload/move the checks file to your Matrix plugin folder. (<server>/plugins/matrix/)
4. If you downloaded a checks file becides checks.yml, rename the new *.checks.yml to checks.yml.
5. Restart your server!

1. Open config.yml in your Matrix plugin folder. (<server>/plugins/matrix)
2. Change the line "- 'your configuration file link'" (cloud_config.links) to "https://raw.githubusercontent.com/Encode42/MatrixConfig/master/cloud.checks.yml" or any other checks file depending on what you want.
   _{For specific Matrix versions, replace master with the config version number.}

This config may not work perfectly with your server.
Plugins, software, performance can all effect how well this config and the anticheat in general will work.
This is not a drag-and-drop solution! Some values may need to be changed to work best with your setup.

Matrix Anticheat isn't a perfect anticheat. It itself has bugs that we cannot fix.
This config aims to mitigate those issues and improve what works well, but there's only so much we can do.

The main config file. Includes the standard checks and everything advertised.

Same as checks.yml but minified. It is a lot smaller in file size, but is nearly impossible to read. Because of its small file size though, it can be automatically updated fast on server startup.
This is optimized for cloud usage in config.yml. For instructions, read Cloud Usage.

Same as checks.yml but with different kick messages.
The messages are from classic Minecraft server disconenct messages such as "java.net.SocketException: Connection reset" and "java.net.ConnectException: Connection timed out: no further information:."

1. nofall.damage: true -> nofall.damage: false (For servers with fall-damage disabled)
2. speed.tolerance: 0.0225 -> speed.tolerance: (number from 0.0125 to 0.035) (Decrease if players are bypassing speed checks)
3. hitbox.max-reach: 3.2 -> hitbox.max_reach: 3.3 (If you have issues with the hitbox check)
   _{NOTE: Makes hitbox detection more lenient! Only change this if you have to.}
4. killaura.modules.autoclicker.max_cps: 18 -> killaura.modules.autoclicker.max_cps: (number from 8 to 24) (Lower means less CPS, higher means more CPS)
   _{NOTE: The highest possible human CPS is 24. This means the number should not be above that as that indicates a macro.}
5. inventory.cancel_vl: 8 -> inventory.cancel_vl: (number from 8 to 14) (Increase if the check causes false positives)
6. fastuse.commands.24: ... -> fastuse.commands.(number): ... (Decrease if players should be kicked quicker, increase if causes false positives)
7. block.fastplace.max_place_per_second: 16 -> block.fastplace.max_place_per_second: (number from 9 to 19) (Decrease if you think there are bypasses, increase if the check causes false positives)
8. place.modules.delay.min_delay: 7 -> place.modules.delay.min_delay: (number 5 to 9) (Decrease if legit players are getting too many violations, increase if bypassed)

This check also checks if the player isn't using Angle cheats, and the NPC checks if the player can hit people behind the player. To prevent lag and false positives from happening with this, the NPC will be spawned only if the player's ping is lower than 185ms. If I'm right, this should make the killaura detection more strict. This has been approved by RE.

FIRST:
Make sure this isn't an issue with the anticheat itself. Not all issues can be fixed with a config. Head over to Matrix's support Discord and ask about the issue, or report the issue at their issue tracker.
You can also try using the default config to see if the issue still stands. If so, it's not a problem with the config.
Matrix's Discord: Here
Issue tracker: Here

THEN:
Make an issue at the issues page with the right template. If you describe what you want changed/fixed well, chances are it'll be taken care of quickly. If you already know what the issue is or how to fix it, feel free to make a pull request containing the change and why you made it.
Issues: Here
Pull Requests: Here

Yes! I encourage you do so. You can also distribute it all you want, just please don't claim it all as your own. (Credit the original authors.)