Cheat Engine

[_Iuri]

Hi everyone, i find a way to use FASM to write assembly code in memory, but at this point i want to implement my own "section" within Autoassemble motor, like as {$lua}, {$asm}, but named {$fasm}.

I would need catch the actual address being writted.

Any idea about how implement this?

Also, thanks DaSpamer, i was helped by u and i forgeted thank you.

[LeFiXER]

For that, you would have to modify the source code but I see no reason why the fasm instructions wouldn't work under the {$ASM} directive.

[_Iuri]

Thanks for your response, Indeed, Autoassemble motor can parse FASM syntax without problems, but, the difference is that with FASM i can use Macros that will make my life much happier

Also, i having a lot of problems with Autoassemble, a few times stops working, others times the syntax check of the script will be succeded, but it won't activate... making the fixing a lot more complicated.

[LeFiXER]

If you right-click on the problematic script it will give some error information as to why the script failed.

Zanzer, another member here has a quick-and-dirty solution for macros:

[_Iuri]

I know how use Autoassemble, with x64 process that (Autoassemble) might fail without error notification, specifically and, for example, when you move a value to a register.

[LeFiXER]

I wasn't implying that you are insufficiently educated with AutoAssembler. I only wished to help find a solution to your problem. If my help is not warranted then I shall save my time.

You can use something like this to store a pointer.

[ParkourPenguin]

[_Iuri]

LeFiXER sorry, i didn't mean to be rude, i just wanted show you a tipical problem that i had with Autoassemble, it was not my intention to speak badly to you

ParkourPenguin, That was an example with a fake address, the Autoassemble script was generated with a default template... but doesn't works on ENABLE section, but does under DISABLE section

[LeFiXER]

I am unsure of the viability of this given that Cheat Engine doesn't interface with winAPI (at least to my knowledge, I could be wrong and should someone know of this then please let me know).

[Dark Byte]

to answer the first question

with registerAutoAssemblerPrologue you can add a scanner for {$fasm} blocks and replace them with the bytecode that fasm returns (use db xx xx xx xx xx)

[_Iuri]

Dark Byte, thanks for your answer, i thinked that too, but at least i need pick up the actual address being writted by Autoassemble, can i get it with registerAutoAssemblerPrologue function?

[ParkourPenguin]

[Dark Byte]

use registerAutoAssemblerPrologue in combination of registerAssembler.

Scan for the fasm block, and write it in a global table

then replace the whole {$fasm} block with fasmimplementation_#### or something like that with the requested parameters. e.g fasmimplementation(id,newmem,param1)

then in your registerAssembler hook check if the instruction starts with fasmimplementation( , and if so, parse the rest. ID as lookup in the global fasmimplementation table, and newmem and param1 for the values

then with that info create your bytes and return a bytetable

Note though that during phase 1 the parameters are given high and low addresses to determine the minimum size needed to allocate for this block so keep that in mind (it's going to give bogus addresses the first few times)

to get you on the way, here's an example script of registerAssembler:

[_Iuri]

Oh, so smart, i will try that, thanks!