Cheat Engine

[Freiza]

I want to print all the value of [ebx+08] and ebx to lua console and to a text file.

1015C194 - 89 53 08 - mov [ebx+08],edx



And how to implement writefile in AA?

SetFilePointer(datafile, 0, 0, FILE_END);
WriteFile(datafile,text, strlen(text), &dwBytesWritten, 0);

[Dark Byte]

You'll also need CreateFile and CloseHandle

anyhow, these api's use the stdcall calling convention, so you push the values in the reverse order (or you decrease esp and write the values into the stack in the correct order)

so:

[Freiza]

And what about this:

I want to print all the value of [ebx+08] and ebx to lua console and to a text file.

1015C194 - 89 53 08 - mov [ebx+08],edx

I want to implement this is lua. I mean this code is executed 100 times per second. I want to log all the value to file and to lua console using Lua scripting

[Dark Byte]

Just write the values using writefile (write ebx and the value of ebx+8 to memory and then call writebyte with a size of 8 on that block)

then when you feel like it you can use lua to open that file and read the contents and display it on the screen

Alternatively, check out this topic: http://forum.cheatengine.org/viewtopic.php?t=550108 and don't use writefile at all, and use readInteger instead of readString

[Freiza]

[Dark Byte]

First: stop assuming you're going to write a textfile
Read the binary file back later on and ONLY THEN parse it as text

1: no, 0d,0a is a newline, but for a binary this is useless and will cause interpretation problems later on (alignment issues)

2: just one \

3: For text you first do a counting function first to count how many bytes there are in the array till you hit a 0 terminator. In your case for the header, it's 14 (0e)
In case of binary, just 4(address) or 8 (address+value)

4: neither, just alloc

5: use CreateFileA

6: as I mentioned, don't assume you're going to write clearly readable text. Just write data, interpretation can be done later on
You could of course make use of calls to "itoa", but that will complicate things a lot more

[Freiza]

[Dark Byte]

Filename is the address of the string [filename] is the 4 byte value that the first 4 characters represent

With binary file i just mean a file that does not contain any readable text and only values stored binary instead of ascii

You can use c routines if the c library is loaded in memory(even ce's tutorial, written in pascal, has it loaded). itoa for example is just a simple function

[atom0s]

Going off your original post, and using Lua instead of AA.

Using Minesweeper as an example, here is where flags are used:

[Freiza]

@DB

1)

[Dark Byte]

2 use filename instead of [filename] else createfile will try to access an address that does not exist

[Freiza]

File is not being created when the code is executed ([filename]-> filename done)
and
When I tried to see what is happening behind the scene using break and trace the program crashed.

Please copy paste the code in CE and attach tutorial i386 and run yourself. It will give you a good idea why the code is not working.

[Dark Byte]

You haven't allocated memory for filename.

What you're doing now is write the filename after "variable", which is only 4 bytes

bytewritten comes after variable, so the initialization of that will overwrite the first part of the string

allocate memory for filename first if you don't want this to happen, or place the definition of filename somewhere else (or make variable bigger)
I recommend instead of label do

[Freiza]

File created but empty, Nothing is logged onto the file.

[Dark Byte]