Originally Posted by JustinFatalx
I just tryed a .dll file I injected it and everything and still it didnt work. Do you have any good .dll hacks I can use?
Originally Posted by JustinFatalx
MPGH CA Auto-Inject
Originally Posted by JustinFatalx
Now if we have something to inject... i also have an injector i cant test cuz i got nothing to inject
wow nice you did this in AutoIt. But why did you make the close after injection option to wait for Engine.exe to close? Close after injection means for the injector to close right after injection is complete, not wait until the target process exits.
Originally Posted by spare2
wow nice you did this in AutoIt. But why did you make the close after injection option to wait for Engine.exe to close? Close after injection means for the injector to close right after injection is complete, not wait until the target process exits.
Originally Posted by Grim
read the README file
Originally Posted by spare2
That didn't answer my question, unless the answer is "Small anti-hack detection so that no signatures are left behind for later bug reports." which doesn't make any sense.
Originally Posted by Grim
sorry man but thats the best answer there is.. if it doesn't make sense to you then trying to explain it would be pointless
And, "if it doesn't make sense to you then trying to explain it would be pointless", are you trying to imply something?
I am not implying that this injector isn't working and functioning.
Originally Posted by spare2
0.o I don't think you understood my question. I asked and quote,"Why does your Close after Injection option make your injector wait for Engine.exe to exit?". Your answer is completely irrelevant to my question. The phase "Close after injection" obviously mean to call for your application to exit immediately after the injection is done. But what the actual function is completely different.
And, "if it doesn't make sense to you then trying to explain it would be pointless", are you trying to imply something?
I am not implying that this injector isn't working and functioning.
And, "if it doesn't make sense to you then trying to explain it would be pointless", are you trying to imply something?
I am not implying that this injector isn't working and functioning.
here's an attempt at it since you're so formal and not giving up on it.
When you inject a .dll file into combat arms you are injection written code into the game to change the actual view and concept of the graphics. Believe it or not when your combat arms crashes it creates a Bug Report and sends it to Nexon.
When it creates that Bug Report it gathers all of the current software information about the game so that it could find what the problem was. That's is the main way hacks get patched. If too many people use it then it is a lot easier for nexon to find out how to patch it.
The reason the hacks leave behind signatures is because of the injected dll is never freed from injection. The close after injection waits until you are finished playing combat arms before freeing the injected dll so that it doesnt leave behind any signatures for bug reports to pick up.
If you still dont understand or still confused.. please just deal with it cuz there is literally no better way to explain it.
Originally Posted by Grim
Ok.. First off i'm completely annoyed with such a question.. Second off what i was trying to imply was that if you can ask a question that you already know the answer to, yet you still dont understand it, then there's a slim chance you'll understand it at all.
here's an attempt at it since you're so formal and not giving up on it.
When you inject a .dll file into combat arms you are injection written code into the game to change the actual view and concept of the graphics. Believe it or not when your combat arms crashes it creates a Bug Report and sends it to Nexon.
When it creates that Bug Report it gathers all of the current software information about the game so that it could find what the problem was. That's is the main way hacks get patched. If too many people use it then it is a lot easier for nexon to find out how to patch it.
The reason the hacks leave behind signatures is because of the injected dll is never freed from injection. The close after injection waits until you are finished playing combat arms before freeing the injected dll so that it doesnt leave behind any signatures for bug reports to pick up.
If you still dont understand or still confused.. please just deal with it cuz there is literally no better way to explain it.
here's an attempt at it since you're so formal and not giving up on it.
When you inject a .dll file into combat arms you are injection written code into the game to change the actual view and concept of the graphics. Believe it or not when your combat arms crashes it creates a Bug Report and sends it to Nexon.
When it creates that Bug Report it gathers all of the current software information about the game so that it could find what the problem was. That's is the main way hacks get patched. If too many people use it then it is a lot easier for nexon to find out how to patch it.
The reason the hacks leave behind signatures is because of the injected dll is never freed from injection. The close after injection waits until you are finished playing combat arms before freeing the injected dll so that it doesnt leave behind any signatures for bug reports to pick up.
If you still dont understand or still confused.. please just deal with it cuz there is literally no better way to explain it.
You think I am complete dumb and dunno what what you are doing.
But in fact you are wrong in a couple of places,
first, if you wanted to make a option to close injector after process exits, why did you name it "Close after Injection?", that makes completely no sense unless you don't know what those three word means.
second of all, in your program, you use the function ProcessWait Close(Engine.exe) which pauses script execution until process does not exists. After Engine.exe exits, you try to get the handle of Engine.exe again and clear its library, but it ALREADY exited. You CANNOT get the handle of a exited process. What you tried to do will always fail to execute.
Originally Posted by spare2
You know what the funny thing is?
You think I am complete dumb and dunno what what you are doing.
But in fact you are wrong in a couple of places,
first, if you wanted to make a option to close injector after process exits, why did you name it "Close after Injection?", that makes completely no sense unless you don't know what those three word means.
second of all, in your program, you use the function ProcessWait Close(Engine.exe) which pauses script execution until process does not exists. After Engine.exe exits, you try to get the handle of Engine.exe again and clear its library, but it ALREADY exited. You CANNOT get the handle of a exited process. What you tried to do will always fail to execute.
You think I am complete dumb and dunno what what you are doing.
But in fact you are wrong in a couple of places,
first, if you wanted to make a option to close injector after process exits, why did you name it "Close after Injection?", that makes completely no sense unless you don't know what those three word means.
second of all, in your program, you use the function ProcessWait Close(Engine.exe) which pauses script execution until process does not exists. After Engine.exe exits, you try to get the handle of Engine.exe again and clear its library, but it ALREADY exited. You CANNOT get the handle of a exited process. What you tried to do will always fail to execute.
Originally Posted by 808Local
HEY DICKWAD, If you fucking think you know it all, why don't you fucking code a hack and stop fucking bitching about something you don't make. Stop being a little bitch and crying, when you yourself just come to this site just to download hacks...Be more appreciative kid, maybe they'll respect you more. He's smarter than you in many ways, I wouldn't even go with the "You're wrong in couple places"
http://www.mpgh.net/forum/3-general/...2-trainer.html
Are you mad? o.0
Just because I don't make hacks for CA, or post my hacks in MPGH, doesn't mean I am dumb. I am simply pointing out errors he has in his program. Are you done trying to be a cool guy? Want some ice cream now? Idiot.
will this inject an asi file???
Good job! 
Awesome injector as usual.
Awesome injector as usual.
Niceee Injector.
Hey man, Just a question, This injector wouldn't work for any of the old hacks unless it has a working bypass right?
This thread is closed for replies.
