Cheat Engine

vng21092 · Posted: Fri Oct 23, 2015 8:24 am Post subject: Quick question

When and why, should I be using

PissJar · Newbie cheater Reputation: 0 Joined: 23 Sep 2015 Posts: 13

You should be able to find the answer at cheat engine wiki's auto assembler page. I can't post URLs yet so add me on steam or something OR PM ME because the KF2 hack is totally broken and you just WONT respond

STN · Posted: Fri Oct 23, 2015 8:37 am Post subject:

PissJar · Newbie cheater Reputation: 0 Joined: 23 Sep 2015 Posts: 13

Zanzer · Posted: Fri Oct 23, 2015 9:52 am Post subject:

Lets say, for example, you have two separate injections.
One injection writes a value to an address identifying that an event has occurred.
The other injection wants to wait for this value before performing some additional action at its location.

Script one may populate a variable with the base address of a unit the player has targeted.
Script two may update the health of ALL units when they take damage.
You want script two to automatically kill a unit, but only if the player has it targeted.

Normally, you would activate script one first to setup the variable and register it.
Only then is it possible to activate script two, which reads from the variable.

Well, with GLOBALALLOC, you can define the address in both scripts.
It only gets initialized by the first script that gets activated.
Now the game won't crash if activated out of order or if one gets disabled.

vng21092 · Posted: Fri Oct 23, 2015 10:12 am Post subject:

ahhhh I see, I've definitely ran into those problems, that makes sense. So in essence, its basically a combination of alloc, and registersymbol? And STN, I've noticed that you CAN unregister the symbol, but I'm not so sure on the deallocating part. With globalloc it defines (not sure if right word?) its own memory region, whereas registersymbol defines the symbol within the memory region allocated by the cheat. Thanks for help guys.

panraven · Posted: Fri Oct 23, 2015 11:50 am Post subject:

Some note on ALLOC vs GLOBALALLOC for whom may concern:
1. GLOBALALLOC has no address hint, ie. the 3rd parameter of ALLOC. So GLOBALALLOC should always allocate memory below 2g memory space, which may be matter in 64-bit target; <oh,nice DB will added 3rd parameter to GLOBALALLOC http://forum.cheatengine.org/viewtopic.php?t=584970#5623926 >
2. consecutive ALLOC same symbol without DEALLOC cause memory leak,while GLOBALALLOC cannot be de-allocate (aa script DEALLOC(globalallocatedSymbol) will success but the memory still there and can be refer with the symbol);
3. GLOBALLOC will refer same memory address with same symbol and size, but after unregistered the symbol, the new GLOBALALLOC of same symbol MAY allocate another memory address;
4. memory allocated by ALLOC inside a lua assemble command may not be de-allocated by DEALLOC inside another lua assemble command (but sometime it can ~_~)