Pointer Scan

[pacifista]

I've got generated pointers



i 've got this what writes to this process



*Pointer ends with this spesific?!* what to write here? i never understood what is eax what is rax etc.



Can anyone help me? Thx in advance. I cant even find a measly pointer for a single character stamina.

[BabyGroot]

The best teachers are Google and YouTube.

Spoiler

[pacifista]

i will follow these thx. currently i'm trying to play the game, creating lots of pointer generations for each run etc.

i hope i can find certain pointers and save my first table. how many pointers for a stamina for example?

i mean i see 40000 line of memory addresses.

if i scan the game 10 times for stamina value of a certain character's is it overkill or what?

[Paul44]

^ ptrscans die sooner then later, BUT: it is one of the best ways to get started in this "arena".
=> if one does not have the ambition/ inclination to start building tables, then this is a very good/easy way to get yourself some 'cheats' for the duration of your gameplay (within the limitations of this type of info_collection)

Practically: create a scan, and regularly (~ daily) rescan to clear out them '??' and incorrect info (use 'value' option for that)...
Eventually though, you are going to need to "find a way" to collect this info without relying on these scan (as they die out evt). "This way" is basically 'create a script for it'...

=> if you have a knack for this kind of stuff, you'll evt start doing just that. But: give yourself at least 6 months to get into it !

As for your example: it means you'll create a script - injection point - at the location you've found earlier (@ location '7FF738... = memlocation in opcode); and your script will "manipulate" them particular xmm registers.
(~ and yep, it'll take some time to pick that up)

oh yeah: ptrscans start in the 'millions' (and much more); no worries. tip: give each rescan a new name 'eg: 'Die Hard_HealthPlayer_2.ptr', and increment this way... Usually - after 2nd scan - I delete the 1st scan since this one is usually very big (read: GBs !)