Anti-Cheat

[User8382983]

https://community.multitheftauto.com/index.php?p=resources&s=details&id=18996
If you want an anti-cheat system, continue from here; this will be the right one for you.

 

Edited March 12 by User8382983

[eoL Shady]

 @User8382983 

I took some time to read through the GitHub source and I honestly like the approach you took with this project.

The modular architecture is very clean and makes the anticheat easy to maintain and extend. Splitting detections into independent modules is definitely the right direction for an MTA resource like this. I also like that everything is configurable through config.lua that makes it much easier for server owners to adapt it to their environment.

The amount of detection types is also impressive (movement, combat, environment, network etc.). Especially the event spam protection, element data protection and movement analyzers are very useful in real servers.

Another great thing is that the project is open source. Transparency is extremely important when it comes to anticheat systems, and it allows other developers to contribute and improve the system over time.

If I could give a few suggestions:
- Some detections (like wallhack scanning and VPN detection) may need further refinement because they can be unreliable in some environments.
- It might be good to move as much logic as possible to the server side, since client-side protections can sometimes be bypassed by advanced loaders.
- As the project grows, adding more documentation about how each detection works internally could also help other developers contribute.

Overall it's a very promising project and I respect the effort you put into it. It's always great to see new open-source tools for the MTA community.

Good work

[NightWatch404]

I was testing this anti-cheat, but I noticed that some of the detections are reacting late. For example, with the event spam detection, I tried spamming a trigger from the client side. The server actually processed and executed the action first, and then the kick happened after that.

[RekZ]

@eoL Shady 

Without any intention of creating conflict, I believe you should review the entire code again, because absolutely everything is a mix of “vibe code” and code copied and pasted from other sources. When I first saw it almost a year ago, I found it interesting, but once I started looking at the code, I realized that around 70% or even more of it was simply garbage code. There are detections that, when you read them, make no sense at all. In fact, you can see one of my issues about it, but when I realized it had no future, I just left it. I don’t want MTA users with less experience to trust that this is something useful, waste their time, getting frustrated and quitting MTA.