assume i use that 3427B840 somewhere but i dont know where.
Repeat again until you find a green address. Pointer Search for 3427B840.
oh and L. Spiro... can you explain why i cant edit memory... but then every once in a while i can
Because sometimes the memory protection is writeable while other times it is read-only. XTrap changes this.
Alternatively, it could be a bug in XTrap that causes it to sometimes fail to see that something is trying to change the memory in its process while other times it catches it. There are infinite variables, but none of them are in MHS.
For Disassembler modifications I can add something to force the protection to writeable to ensure it always works (using kernel-mode to do this of course, to avoid hooks and make sure it actually works).
BTW is it possible for you to add a IsDebuggerPresent (on all programs) bypass to the debugger? i think IsDebuggerPresent is inside of xtrap.xt and not Wolfteam.exe... ima freeze the proccess and open in ollydbg to see now
But I think you'll need to look deep into ASM coding and API calls especially Kernal API calls from xTrap.
A kernel-mode hook is already planned for this.
Furthermore, I have already added functions to the scripts that allow you to read and write kernel-mode RAM, which allows you to remove all XTrap/nProtect Game Guard/Hack Shield/VAC/etc. kernel hooks and to add your own.
L. Spiro