go
If you can handle it, I'll increase the difficulty level
edit: I'll point out what specific defense techniques are involved here:
1) anti-jump (from noob editing via bytecode)
2) anti-hooks (from nubo substitution of functions) + anti-gluing (including anti "
func injector ")
3) dynamic response from the server (from noob interception and substitution of traffic or editing of include files)
4) obfuscation (protection from reading code)
5) garbage (protection against decompilation)
by "noob-" I mean that the workaround is not that difficult, but nothing will work in the usual way