[Request] Trainer/Memory Modifying extension

[Ham]

If you don't understand it, you probably shouldn't be using it. It just takes a memory address and a value to write.. you can't get more simple than that.

>>If you don't understand it, you probably shouldn't be using it<<

Are you suggesting that the fact of not understanding it is enough not to understand it at all?

[dragonguy]

Rewriting the memory address is easy, finding out what the memory address is, isn't.

I couldn't be bothered to post here before because I thought it was a pointless discussion, turns out I'm wrong.

[James]

That's because the Memory object doesn't find memory addresses. You'd have to use TSearch or something for that.

[Ham]

That's because the Memory object doesn't find memory addresses. You'd have to use TSearch or something for that.

Hi Jamie,

Do you have plans to complete it with a memory scan function? If not, would not that be easier to provide a PE header instead of an addresse? I don’t know but probably in that way it is possible to read and write to the data memory reserved for a particular object without just write it arbitrary. Am I wrong or have I understood that wrong?



With Respect

[Fimbul]

Yes, please.

I had trouble scanning for values using fastloops (without fastloops too), because doing so crashes the APP.

A scan function would be extremely welcome!