Tools like Cheat Engine attach to the Metin2 process. The client protection layer flags suspicious read/write and module injection; depending on policy, the game closes or an HWID ban is triggered.
Memory editors and trainers
Speed hack and damage hack (client)
When movement speed, attack delay, or damage multipliers are altered in memory, the client layer catches it. No server rubberband or packet limits - detection and action are on the client.
DLL inject and hooks
Metin2 DLL inject and Python-based loaders bring code into the client. M2Guard looks at load patterns and signatures, not only window titles.
False positives
Some overlays or drivers may rarely trigger warnings. You can adjust whitelist and warn/kick/ban policy from the panel.
Frequently asked questions
Common questions about this page and short answers.
No. Memory scanning runs only in the player’s Metin2 client process.
Writes to speed/movement fields and known cheat patterns are flagged on the client; policy ends the session or applies a ban.