Looking for pointers in ArtMoney is taking a bit longer than in Cheat Engine, however the pointer I get in Cheat Engine is in Hex,
something like "64D". Now, everything I try to use in micromacro (64D, 1613, 1316 etc) will result in bad parameters. So how do I convert this

Precede that data with a 0x. 0x will typically tell the programming language to use hex notation. 0x64D should work flawlessly. You could also use the Windows Calculator to convert it to decimal, but...who actually does that?

And yes, ArtMoney's pointer lookup may be a bit slower than Cheat Engines. The difference is in the way the search works. Depending on how the game was programmed, the two different approaches may return different results (and by results, I mean in effectiveness, not necessarily different addresses).

If I remember later, I'll post a tutorial on how to do different types of pointer look-ups in Cheat Engine. One, in particular, relies on using the "What accesses this address" function to find a static pointer and offset to it.

elverion wrote:Precede that data with a 0x. 0x will typically tell the programming language to use hex notation. 0x64D should work flawlessly. You could also use the Windows Calculator to convert it to decimal, but...who actually does that?

But it won't work Hmm, maybe my script is wrong? Wouldn't be the first time.
And no, converting them via the Science Calculator didn't help also, like I said.

elverion wrote:
And yes, ArtMoney's pointer lookup may be a bit slower than Cheat Engines. The difference is in the way the search works. Depending on how the game was programmed, the two different approaches may return different results (and by results, I mean in effectiveness, not necessarily different addresses).

I weren't actually talking about Cheat Engine being faster than ArtMoney, It's just that I don't know ArtMoney well so I assume your way is the only one finding pointers. While in CheatEngine I can add the debugger (like you said) and find the right pointer in no time with almost never restarting the client.

What do you mean it's pointing to a "different" value? Do you mean you are reading the wrong thing (ie. getting the wrong value returned)?

First, what is it you are trying to read? Are you sure it fits the size of a byte (what is the possible range of the expected value? 0 to 255, 0 to 65,535, 0 to 4,294,967,295?)? Is it even an integer (or character) you are trying to read, or could it be a float/double?

elverion wrote:What do you mean it's pointing to a "different" value? Do you mean you are reading the wrong thing (ie. getting the wrong value returned)?

First, what is it you are trying to read? Are you sure it fits the size of a byte (what is the possible range of the expected value? 0 to 255, 0 to 65,535, 0 to 4,294,967,295?)? Is it even an integer (or character) you are trying to read, or could it be a float/double?

Yes, I'm checking a 1 byte adress for a value between 1 - 60. I'm using print to display the value and it displays that the current value is 12 while in Cheat Engine its 0.