Cheat Engine

[sylvanus]

Hello, sorry for my english, is poor.

i am trying a trainer for maple. and i have this ¿?

1) injected dll to maplestory.exe (odinms) with CreateRemoteThread [OK]
2) dll injected, changue memomry and hacks function [OK]

BUT, i need make a GUI, how can comunicate with my dll injected.

example this is my itemvac function in my dll functional

__declspec(naked) void itemvac()
{
__asm
{
pop [Retornar]
pushad
mov ecx,[ebp+0x8]
mov ebx,[ebp-0x24]
mov [ecx],ebx
mov [ecx+0x4],eax
mov ecx,eax
mov eax,ebx
lea edx,[eax-0x19]
mov [ebp-0x34],edx
lea edx,[ecx-0x32]
add eax,0x19
add ecx,0xA
mov [ebp-0x30],edx
mov [ebp-0x2C],eax
mov [ebp-0x28],ecx
popad
push eax
push [ebp-0x24]
lea eax,[ebp-0x34]
push [Retornar]
ret
}
}

IN MY GUI : f1 = itemvac

any idea please??

i think, make a SetWindowsHookEx in dll injected??
but, if is this, the dll injected catch keyborard msg, but my GUI no!

o MY dll catch keyboard msg and, resend with SENDMESSAGE keys to GUI?

Please, i wait your help.

[oib111]

Piping.

[&Vage]

I use window messages lol

[Jani]

And for example sockets. Google for inter-process communication (IPC).

http://en.wikipedia.org/wiki/Inter-process_communication

[HalfPrime]

Just make a GUI in the DLL?

[dnsi0]

You have 2 choices:
Make the GUI into the dll. (By Creating a new thread)

OR

Edit: Just make it into the DLL its eaiser...

Ill give u an example in delphi if u want.

[BanMe]

instead of passing the Handle to The Current Process pass in the Handle to The Dll to DialogMain

also dont handle Window Cleanup in the MessagePump do the cleanun in DLL_DETACH_PROCESS cause if Parent process is closed before window then it will cause a locked thread and prevent process from truely closing..

[ElectroFusion]

I would say just make everything work through the DLL, unless you don't know how. Harder way would be learn to use piping.

[dnsi0]

There ya go sent u the example I whiped up in like 10 seconds...

[sphere90]

[Noz3001]

[Jani]

[nog_lorp]

Create a mutex for every hack enable/disable with the GUI application.

Make a thread for every hack, that looks like this (psuedocode):

[&Vage]

[nog_lorp]

YOU're an inefficient way.

Actually if the synchronicity is planned properly it shouldn't be inefficient. The threads will block while they are waiting. Unlike a window proc which loops continuously.