How do you want to share the same memory space without injecting a dll into the game?
DetectedPureosouza's Glow ESP 1.0
when i click on the download it say This attachment has not been approved yet. Please go back and read or respond to the thread. it has done that to a lot of hack latly anything i can do?
External cheats don't run in the process you want to target (for example hl2.exe), but instead inject in another program or have their very own process. They don't have direct memory access and are therefore slower at reading and writing memory, and calling functions from the target process also isn't as easy and takes much more time.
Internal cheats directly inject into the target process, and VAC scans for injected dlls inside of game processes. Because of the way VAC currently is, injected cheats are easier to detect than external ones (That can change in the future; of course). The positive in injected cheats is that they have direct memory access to the game process, so reading and writing memory is a lot faster and it's easier to call functions of the process/hook functions/whatever you would like to do basicly.
Internal cheats directly inject into the target process, and VAC scans for injected dlls inside of game processes. Because of the way VAC currently is, injected cheats are easier to detect than external ones (That can change in the future; of course). The positive in injected cheats is that they have direct memory access to the game process, so reading and writing memory is a lot faster and it's easier to call functions of the process/hook functions/whatever you would like to do basicly.
What do you think readprocessmemory and writeprocessmemory is doing? Injecting a dll?
Originally Posted by pureosouza
What do you think readprocessmemory and writeprocessmemory is doing? Injecting a dll?
I asked what you think they are doing, the inner workings
ReadProcessMemory:
Reads data from an area of memory in a specified process. The entire area to be read must be accessible or the operation fails.
WriteProcessMemory:
Writes data to an area of memory in a specified process. The entire area to be written to must be accessible or the operation fails.
Reads data from an area of memory in a specified process. The entire area to be read must be accessible or the operation fails.
WriteProcessMemory:
Writes data to an area of memory in a specified process. The entire area to be written to must be accessible or the operation fails.
I asked if you knew the inner workings, not the msdn definition
Originally Posted by WasserEsser
LOL ReadProcessMemory and WriteProcessMemory is external, holy fuck, learn some programming before you post any more shit LOL
I guess you don't know the inner workings then Wasser, so let me clear this up once again...
No it's not external
No it's not injecting a dll, but yes, it is internal
I'll let you figure out the rest, and when you have, you can come back and look at your posts in embarrassment
How are you reading the client module? If you use K32EnumProcessModules, K32GetModuleBaseNameA or any other revision of the former you are probably external. On the other hand, if you use GetModuleHandleA you are more than likely internal.
GetModuleHandleA, obviously
Soooo is this legit or naw? Waiting for approval
Works fine without any problems 
HEHE GOOD
GOODLooks amazing! Im gonna use it
This thread is closed for replies.
