AR CHEATS TO RAW HELP

[Saiki]

http://forums.pcsx2.net/Thread-Making-ch...hes-easier

I just use extended for everything, much easier

About that...is there is some info somewhere about how "extended" works?

ditto on the above question, been looking for that myself as well

[fateric]

WHAT DOES THE CONVERTER MEAN WHEN IT SAYS INPUT FORMAT HAS TO BE 8 SPACE 8

[Saiki]

12345678 98765432

[jesalvein]

as iakoboss said, don't use caps, please.
next time you get a warning.

[fateric]

oh ok and sorry

---

12345678 98765432 <that format
<address> <value>

so the code0480B429 1EB4778E becomes 12345678 98765432 0480B429 1EB4778E

[vsub]

Patch=1,EE,10340CEC,extended,00006262
Patch=1,EE,00340CEE,extended,00000062
Patch=1,EE,00340D49,extended,00000062
Patch=1,EE,20340DCC,extended,62626262
Patch=1,EE,10340DD0,extended,00006262

or

Patch=1,EE,10340CEC,short,00006262
Patch=1,EE,00340CEE,byte,00000062
Patch=1,EE,00340D49,byte,00000062
Patch=1,EE,20340DCC,word,62626262
Patch=1,EE,10340DD0,short,00006262

[fateric]

eh alright i give up.
tnx everyone im off to go read

[nosisab Ken Keleh]

Although already mentioned in another topic, it may be useful to repeat. You could include in your guide, Saiki.

The standard for codebreak is:
codes beginning with 0, 1, 2 indicates "byte", "short" and "word" respectively. using the significant digits is a reasonable inficator but not always correct. For example, a value can be given as x00000B7 but still being a "short" field or even a "word" field (actually x is what gives the correct length). The difference in usage being if it's placed Byte in the pnach the actual field will not receive the zeros, it may not be the intended.
So, "byte" will fill only the byte field (for example FF) and none those remaining zeros are used.
Using "short" two consecutive bytes will be filled, so it will be 00FF
Using "Word" four consecutive bytes.... so 000000FF will be effectively put on memory... notice if wrong that will fill unwanted zeros and erase the adjacent content.

Extended is an attempt to support those non conventional codes with different meanings, not all codebreaker codes are yet implemented, use with caution.

Now it may be interesting to notice there is a great difference in the pnach when using "extended" and the word --> byte direct code. With extended the code MUST be as it comes, if it has a leading 0, 1, 2, F or any other leading digit it need to be preserved. Even for 0, 1, 2 codes. That's because they are what indicates the length of the operand (byte, short or word).

But... if using Byte, short or word in the pnach, the code must begin with 0, the length being supplied by the token itself. 1 will just crash the emulator and 2 may work or not, better is using 0 always when using explicit length.

Resuming, if using extended, never change the raw code obtained, if it begins with 1 it must continue so.
If using byte, short or word, notice that digit in the code, change it to 0 and use the correct token.

Whatever other code "must" use extended without alterations.

PS: Why a "short" or "word" field must be defined so even if the code uses only a byte? Maybe one gave a too great value and now want to reduce it. For example:

you gave 100000GPs (money) = 000186A0 (obviously a word field) but resolve it is too much and want to give only 1000GP starting amount... that will be 000003e8 (apparently a short)... so you introduce the code as short... it will not work because the final value will become 000103e8 = 66536GPs ... obviously not the intended. So the code MUST be entered as "word".
obs ... in the actual memory the sequence of bytes is inverted (little endian) but it's irrelevant here.

[Saiki]

I'll add a few notes later