can someone Give me a Source Code OF Hack Loader...

[catchthis]

I Hope There is A GooD People Can Give Me a Source Code of Hack......

[johnpp]

try this https://www.mpgh.net/forum/33-visual-...ader-base.html

[catchthis]

kk thnx...

[Jason]

I wouldn't use that, it's pretty bad. I was a full-blown noob when I wrote that :/

[megamandos]

I noticed in that loader you chose to find processes by image name, this seems to be common. Is this kind of the defacto standard for injecting? Do you think that I should add this functionality to Injex? Injex currently locates processes by PID or starts them up and injects based on the image path you provide, but it does not locate them by process name...

Do people locate by image name for automation reasons?

[Jason]

I noticed in that loader you chose to find processes by image name, this seems to be common. Is this kind of the defacto standard for injecting? Do you think that I should add this functionality to Injex? Injex currently locates processes by PID or starts them up and injects based on the image path you provide, but it does not locate them by process name...

Do people locate by image name for automation reasons?

I usually use the image name as the interface between the user and the injector, but break that down to a process ID internally. It's a lot easier for people to use a usually static image name rather than a dynamically allocated process ID number. It also makes auto-injection a viable option (some games need to be injected as soon as they start up because they make all their memory critical shortly after) as you just have a loop looking up the expected image name in the running processes list.

As injex is a library you probably don't HAVE to implement the ProcessName to ID functionality, but it would be a good overload to add in as it's a very commonly used for interfacing with an inexperienced user.

[megamandos]

I usually use the image name as the interface between the user and the injector, but break that down to a process ID internally. It's a lot easier for people to use a usually static image name rather than a dynamically allocated process ID number. It also makes auto-injection a viable option (some games need to be injected as soon as they start up because they make all their memory critical shortly after) as you just have a loop looking up the expected image name in the running processes list.

As injex is a library you probably don't HAVE to implement the ProcessName to ID functionality, but it would be a good overload to add in as it's a very commonly used for interfacing with an inexperienced user.

I added the injection by process name.

injex -b pwnage.dll -n game.exe

is now something you can do