God Eater 2

[LunaMoo]

Correct in what way? The code I posted was originally like that, no changes on my side. Maybe the codes you tried earlier were simply for different game versions. Each update changing the eboot.bin will require different codes that's almost sure.

----------------------

If you're interested more generally in trying to fix codes that are ok and works in same game version on psp, but doesn't in ppsspp. Then it's probably caused by one of the 2 ppsspp cwcheat limitations:
- unsupported code type(0xD type),
- JIT not recompiling the code changed by cheats unless it's done through cheat menu.

Sometimes it's as easy as removing the problematic code(0xD and sometimes also 0xE which while supported, might have limited use because JIT), unfortunately at other cases you'll have to have a bit of knowledge or at least some google skills to learn how the code actually works and how to change it to not be a problem under ppsspp.


So let's try to understand the one line cheat which I posted earlier:
_C0 Item Not Dec
_L 0x20096F58 0x00401023
the bold 2 is the code type(32 bit value write) followed by 7 letters of address, the numbners after space is the value to write. You can easily google for cwcheat code types for more details, for example this site should have most/all cw cheat code types.

If you check that code in ppsspp debug>disassembly the address would be 8896F58(0 in cw cheat is basically 8800000 in ppsspp disassembly, through games load their code from 8804000 and up), if you check this address in GE2 with cheat activated it'll have a value of 0x00401023 which is actually a game code looking like that:
subu v0,v0,zero
without the cheat, if you check earlier or by using restore cheat, it'll have a value of 0x00451023, just one number different, but it's a pretty big change in it's meaning:
subu v0,v0,a1

It might not be clear at all at this point either, so let's google for: subu mips - and get some info about what it does:

Code:

SUBU -- Subtract unsigned
Subtracts two registers and stores the result in a register
Operation:
$d = $s - $t;
Syntax:
subu $d, $s, $t

Now this should be very clear, the person who created this cheat firstly found some item value then found out how game works, what it does with this value and found the code above which sets one variable to same variable minus other variable and changed the last one to 0 to make a cheat.

If you find a code which doesn't work you can either try randomly deleting stuff beliving in luck, or go through similar way of understanding how it works for each code line of cheat and then building in your mind the image of how it works as a whole, keeping in mind those two limitations of ppsspp which I listed on the start. It might be more bothersome than it's worth^__^.

--------------------------------

Putting that aside, not all codes must use assembly and modify game code to get similar results. Inventory in such games for example is usually just a table or matrix storing values sorted by some index or even in how it looks at inventory screen. Instead of changing game code it's even easier to just find the address where inventory is stored and make a multi-line-write aka condensed cheat from it.

Here's a cw cheat I made using such method, if you would like to just set the item value to anything you wish in case you would need it for anything:

Code:

//GE2 v1.30
_C0 items in hand
_L 0x82F0363A 0xuuuu004C
_L 0x000000qq 0x00000000
_C0 items in storage
_L 0x82F21234 0xuuuu004C
_L 0x000000qq 0x00000000

In each code change "uuuu" to amount of unique items you have in your inventory and "qq" to quantity of each item you want. Ofc in hex, you can use windows calc in programmer mode as a converter between dec/hex values.

and example of the code:

Code:

_C0 items in hand
_L 0x82F0363A 0x0004004C
_L 0x00000063 0x00000000

would set quantity of first 4 items in your inventory to 99.

So now you have another one that should work, althrough it's more an example showing that sometimes simpler cw cheats looks to be more complicated when you don't know how they work, mass modifying values is easier in the end from modifying game code through even if results in slightly longer code.

I hate grinding myself, althrough kind of understand it for handheld games, they are usually not for long gameplays, but rather thanks to their portability played in short bursts between doing other stuff so it's just not soo boring. Unfortunately it all get's upside down when we take a portable game and run it on pc as many of us do for improved graphics and full size pad controls.;p