For Future Hack Address Modders

could you explain in english this time

When you run cheat-engine...and combat arms with a bypass...once you change the address.....sometimes combat arms automatically closes , because my idea is it detected that it changed then checked your process list and saw what changed it , if it was not on your process list, then maybe? just maybe? combat arms won't detect it?

ok now in clear english

lmao, I don't understand either sorry

r u saying that if engine.exe isnt on ure process list the game wont crash, if thats wat ure saying then ure a complete idiot

hes saying that when you execute a hackin tool, hackshield wont detect it if it doesnt appear in the tasks list...

and my english sucks as well... so?

Mostly every hack , changes a ADDRESS'S VALUE with in combat arms, how ever a ADDRESS'S VALUE In combat arms, can change without a hack......Now obliviously if it changes without a hack you wouldn't get kicked......but how would they detect if your using a hack...or if your not?......

.....What I believe is....once a value is changed it searches, you computers processes that are currently running (Basically checks for components with in a program that allows it to run), and if it picks up a process that has memory searching components, and access to the address that recently changed...then it would kick you....otherwise you would stay online...Now if the hack's Process gets closed before it detects it...then maybe it wouldn't kick you..


EDIT :

Yea your right...So once the hack changes the process..it should be closed immediately, and automatically

this thread is a total fail

I get 95% of what Code Never trying to say. Quite hard to understand

i only get 5% so we can maybe help each other, u give me 95% i give u 5%

Here is what he means. He meant that when a hack is activated, it will change CA address. After CA detects the change of addresses it will take a look at the process list to see what changed it. Then he said that the future hacks should be when you click the hotkey, it activates the hack and close the process. So that when the hack activates, it might change the address of CA and CA check the process list, there will nothing on the process list so CA can't detect anything that changes it, therefore it can't d/c you. Am I English enough?

i understand what he means. Yeah that does make since. SO basically, we should code hacks that close when hackshield scans for the processes then reopen themselves automatically when its done.

HSheild doesn't work that way. HSheild does a few protection systems:

-Process String name Scan. Ex. if Your running Cheat Engine.exe it will shut down.
-It protects all the memory so you can't write using WriteProcessMemory API.

Theres a whole lot shitting more but thats all you need to know for now.

Now when CE writes to memory, it has to use an alternate meathod to write to it. So it probably uses its own memory writing driver, when HSheild detects that its protected memory area has been tampered, thread has been suspended, driver has been executed, or any signs that a memory editor is running, it will end CA.

I haven't checked CA personally, but in MS HackShield scans a specific memory region. I'm able to use hacks outside of the region, but the hacks inside of the region would give me HAD(Hacking Attempt Detected). That's probably another reason why you're getting detected. Could be an undiscovered CRC :P