(adsbygoogle = window.adsbygoogle || []).push({}); How do Quick Codes work, in relation to representing offsets and values? I see people publishing new Quick Codes, and would like to do the same myself, but I don't understand how a series of offset and variable byte length values can be represented in the Quick Code format (XXXXXXXX YYYYYYYY).

In addition to a line of code, they must also be 8 digits per set.

X1 = Location
Y1 = Value(s) / Amount of the cheat/item.

Most of the time, at least.


Simplest way I can put it.

So an example cheat might be, and this is just random, it's not for any game.

42027138 00000063

Where 63 = 99 in hex code.

If you wanted to change 99, to 255, the new line would be.

42027138 000000FF.

The most important thing here, is to first find the concrete location of what you want to mod.

Correct me if I'm wrong but it seems you used a multi-line method (4) at the beginning of the code.

For what I remeber:
0 = single byte
1 = 2 bytes
2 = 4 bytes
4 = multi-line (begin from - end to)
8 = search value

So your random code should be (for changing only one byte):
10027138 00000063

it says, write one byte in address 27130 starting at the 9th bit (8: in coding world counting starts from 0) so 10027138 and then the byte to write. In this case is only one (formed from 2 digits 63), the rest must be 000000.

For example if you want to write 2 of them you need to convert to 20027138 00005163

I think I messed up something

Ah, gotcha. So you can enforce specific functionality by means of the first character of the first 8 byte component? Is this documented anywhere, do you know? I'm intrigued as to how quick codes can work across different saves with different offsets - I guess that's where the search ( directive would come into play?

I'm lost here, I have an offset: (00022AA0), that I want to change to 10 (0000000A). Would that be the following:

10022AA0 0000000A

?