[Help] How does the injecting things work?

How does the injecting things work?

Hey mpgh,

I wonder how this injection thing works. Some menues like the ******.menu are not an .asi or something like that you have to put into your game folder. They have a .dll wich gets injected. But how does this work (mod side)?

Do you have to create everything by yourself? Or is it possible to use scripthook for developing and inject the .dll just as every other .dll into every other game?

If you have to create anything from scratch: Just how? I mean, only because I inject a file into an application, the application doesn't know what to do with it. Is there anything special you need to do so the game "boots" your mod after injecting?

Best wishes!

If it's DLL you'll need a undetected injector.

Hey,

thanks, but thats not really what I ment. I ment: How is that done on the programming side of the .dll?
What is exactly happening when I inject something into a process?

Originally Posted by Deazl_

Hey,

thanks, but thats not really what I ment. I ment: How is that done on the programming side of the .dll?
What is exactly happening when I inject something into a process?

depends on how you do it. there are quite a few techniques to achieve that goal. the most common way is to remotely create a thread in a process and load the library (dll) inside the target process with the given msdn(microsoft) functions.

if you want to read more about injections you might want to read about it on wikipedia or stackoverflow.

Originally Posted by Kyungrae

If it's DLL you'll need a undetected injector.

Theres no Such thing as Undetected dll injector lol there are all Undetected

ScriptHook is too an injected dll, the only difference is, it's using dxinput.dll.
This is a Library which will ussually Loaded from Windows\System32.
But every Programm look first in his own Folder if there is no explicit Path used.
So ScriptHook use a prepared dxinput.dll which is Hooking the DirectX Output and wrap to real dxinput.dll, which is injecting the ScriptHookV.dll for you.
The difference is, ScriptHook invokes Native Functions + the ScriptHandle Thread, because you can only call Functions from this.
The Last Thing (Hooking the ScriptThread) is what is detected, so other Hacks just don't use it, or avoid to write something there.

ScriptHook is Hooking the Functions and the rest dll Hacks use something like this:

Code:

BOOL APIENTRY DllMain(HMODULE hModule, DWORD  ul_reason_for_call, LPVOID lpReserved)
{
	if (ul_reason_for_call == DLL_PROCESS_ATTACH)
		CreateThread(NULL, 0, HookStart, NULL, 0, NULL);
	return TRUE;
}

which creates a Worker Thread for you, where you can do your shit.

HelpHow does the injecting things work?

Post a Reply

Similar Threads

Tags for this Thread