Cheat Engine

BlackMajor

Hello friends.
I have a question about scripting in Auto Assembly.
I'm trying to put a pointer into Auto Assembly to teleport one object to another object.
I have pointers for the position of both objects.

The offsets for the pointer of the first object are d0, 100, 320, 20, 1a0
While the second objects offsets are 10, 50, 10.

I'm trying to put these pointers into Auto Assembly like such.

[[[game.exe]+10]+50]+10:
readmem([[[[[game.exe]+d0]+100]+320]+20]+1a0,12)

But CE tells me that the pointers are invalid specifiers, despite working fine if i manually copy the bytes from the first address into the second.

The game i'm working in is 64-bit.

Any idea what i'm doing wrong here?

Dark Byte · Posted: Fri Apr 03, 2015 3:46 am Post subject:

currently pointer notations like that don't work on 64 bit targets (it's fixed in the svn)

you may instead want to use two entries in the cheat table (aob's 12 length)
entry1 with address [[game.exe]+10]+50]+10
entry2 with address [[[[[game.exe]+d0]+100]+320]+20]+1a0

then assign a hotkey to entry1 of type "set value" and set the new value to (entry2)

setting values using round braces will take on the current value of the entry it specifies

BlackMajor · Posted: Fri Apr 03, 2015 7:47 am Post subject:

Ah, thanks frienderino.

A tad dissapointed that i can't get the pointer into an AA script, for now.

Had some other things going on in the script other than the teleport, so it's a bit inconvenient to do it with multiple hotkeys.

Thanks for the info.

Dark Byte · Posted: Fri Apr 03, 2015 8:07 am Post subject:

you could use a {$lua} section to define the address (or do the writing itself)

e.g:

mgr.inz.Player · Posted: Fri Apr 10, 2015 3:16 pm Post subject:

similar thread: http://forum.cheatengine.org/viewtopic.php?t=580783

Could someone test this fix. It fixes the [] notation on 64bit CE attached to 64bit game or other 64bit target.

Zanzer · Posted: Fri Apr 10, 2015 3:32 pm Post subject:

I don't appear to be experiencing the bug. Or I'm not understanding it correctly.

mgr.inz.Player · Posted: Sat Apr 11, 2015 2:41 am Post subject:

@Zanzer

what values are inside:
DarkSoulsII.exe+160B8D0
[DarkSoulsII.exe+160B8D0]+d0
[[DarkSoulsII.exe+160B8D0]+d0]+490
[[[DarkSoulsII.exe+160B8D0]+d0]+490]+ec

what OS you have?

Zanzer · Posted: Sat Apr 11, 2015 7:57 am Post subject:

Windows 7 SP1 64-bit

mgr.inz.Player · Posted: Sat Apr 11, 2015 1:29 pm Post subject:

Really? Are you sure you are not using newer version ?

uninstall any CheatEngine, or use some "virtual machine". (virtualbox or etc)

Be sure you have original CE6.4, download it from cheatengine main page.

Install it.

1 Now, download CT file in the attachment

2 launch 64bit cheatengine, and attach it to itself cheatengine-x86_64
(it could be any 64 target, but my CT file is prepared only for targeting itself, because it seeks for 64 bit lua dll, because this module will probably be loaded above 0xFFFFFFFF)

3 open my CT file

4 check "lua5.1-64.dll start address". Address must be something bigger than 0xFFFFFFFF.
For me, it is 0x180000000

5 now, tick "phase 1 - init"

6 at the first entry you will see "this bike is red" instead of '??'

7 tick "phase 2 - pointerstring test"

You can not.........

8 now, execute my fix written in Lua (because only with Lua we can inject code to CE itself, well, we attached CE to itself, but, normally we don't do that, we attach CE to game process)

9 now try tick "phase 1 - init" and then "phase 2 - pointerstring test" again

10 the bike isn't red

Your CT files with pointerstrings won't work for people which are using CE6.4 and the game is also 64bit

It could work if they use CE6.4+ (my builds)
or CE6.4+ prepared by DarkByte (it still says it is 6.4)
or they compiled CE themselves.

mgr.inz.Player · Posted: Sun Apr 12, 2015 8:13 am Post subject:

Zanzer · Posted: Sun Apr 12, 2015 9:54 am Post subject:

I think the reason my script works with Dark Souls II is because the initial address is not larger than 0xFFFFFFFF.
So CE's only problem may be that the initial address is being read as 32-bits. All others are correctly 64.

I did test your script mgr.inz.Player and I was not able to enable Phase 2 without running your fix first.

mgr.inz.Player · Posted: Sun Apr 12, 2015 3:36 pm Post subject:

ah, yes.