[Unkovic]

Quote:

Originally Posted by VeryTallMidget Most of them will manipulate memory. When i worked on my server, i created a hack to quickly teleport to desired locations, it was done by reading players position out from sa:mp memory to save positions and writing memory to teleport savfed positiond read from ini file. Samp uses dynamic memory for player pos, so it requires offsets to read/write effectivly. dll is called from program by dll's name, so changing only that will end up with error. Код: function Out32(PortAdr: word; Data: byte): byte; stdcall; external 'inpout32.dll'; Just some example from the program code I used to read and write LPT port data to control step-motor, here the inpout32.dll is called.

I wanted to say that

Quote:

Originally Posted by Spmn As a guy who worked briefly on a clientside anticheat, I'd suggest you NOT to write an AC unless you actually have experience in modding or at least know how cheats and mods work. First step is to understand how cheats manage to change the behaviour of the game. This is mostly done from within the process (internal - so.be.it) or from other processes (external - trainers). So, experience with Win32 API is required. Moreover, you'll have to analyze the cheats you're going to detect and portions of GTA:SA+SA-MP, so prior experience with disassemblers, debuggers and other analyzing software is needed. Now let's say that you've got the base of your AC up and running. How do you protect it from haxors? You must come up with methods that will make bypassing, tampering and emulating hard to achieve.

So how can someone avoid launcher, that will disable .dll files, CLEO folder and other folders, except renaming it?