help for Cwcheat Pointer Conditional codes

[Garygrump]

I need help with cwcheat pointer codes. im trying to make it detect if the pointer code is 1 or 0. but i cant since the pointer code is diffrent from the conditional code.

0xE1020001 0x0XXXXXXX
this is the conditional code. the x is the address of the cheat.

0x6072716C 0x0000000X
0x00010001 0x00009508
this is the pointer code. the x is the value

Can anyone help?

[LunaMoo]

AFAIK there are no conditional pointer code types in cwcheat format nor anything alike which could be used for that.

As a general rule if you want to do complex cheats(or any at all for more modern/troublesome games), you just have to learn assembly specific to the platform game is compiled for, for example to cheat in pc games you need x86/x86-64, to cheat in psp games you need MIPS. Cheating tools like some more complex cwcheat code types might seem easier to use at first than learning low level programming, but they're much slower, horrible to debug in case of any problems and just very limited by design.

In other words learn programming in mips and write your cheat/mod in assembly using cwcheat only to inject it into game memory or base the condition on something else which doesn't need a pointer.

[Garygrump]

Ok thanks!

[Garygrump]

(07-18-2017 04:42 PM)LunaMoo Wrote:  AFAIK there are no conditional pointer code types in cwcheat format nor anything alike which could be used for that.

As a general rule if you want to do complex cheats(or any at all for more modern/troublesome games), you just have to learn assembly specific to the platform game is compiled for, for example to cheat in pc games you need x86/x86-64, to cheat in psp games you need MIPS. Cheating tools like some more complex cwcheat code types might seem easier to use at first than learning low level programming, but they're much slower, horrible to debug in case of any problems and just very limited by design.

In other words learn programming in mips and write your cheat/mod in assembly using cwcheat only to inject it into game memory or base the condition on something else which doesn't need a pointer.

But is there a way to convert pointers into normal addresses?

[LunaMoo]

Pointers are normal addresses, it's just a name for an address that stores another address which then leads to another pointer or data, there's nothing to convert here.

The only reason people use cwcheat pointer codes is to handle games that move memory around often leaving data under different addresses, so if you ask whenever such data can be set to be stored in some constant specific place - the answer would be yes, by learning assembly you could in theory modify the game to do that, but at that point you wouldn't as you could make things much easier making the game do all the work instead of using some weird proprietary codes.