These are just some things that popped into my mind while glancing at the code for the code types (If I'm understanding the ASM the way it is typed).
2 byte writes (1, 7) = Need the address OR'd by 0x1FFFFFE
4 byte writes (2, 4) = Need the address OR'd by 0x1FFFFFC
Pointer write (6) = Needs to check if the pointer address obtained from the address is 0x0000000. If it is, then make the code skip to the end and execute nothing. Any modification to address 0x0000000 will instantly freeze a game.
The IF's (D, E) = I might suck at explaining this. If I put this:
e004feef 0042d9ac
10444444 00000001
I would need that yellow 4 to change itself to a 1 because there is only 1 code after it to execute. I don't know how the cheat engine works, I'm fairly clueless. If this doesn't set to 1 and you had more codes on after this, would it cause the cheat engine to skip the next 3 lines of the next codes?
Timer (B) = I didn't even check it. I'm just thinking of how to even do this. This would depend on each game and everything, but this would reset itself and be usable for anyone who has a crumb of patience to add this in with the increment codes. Here's my example idea:
E002FEEF 0042D9AC (Joker for L2 + Up)
B0010000 0001234F
30200100 004E5C98
# lines to skip
skip until it's been skipped this many times, and then reset
When you press L2 + Up, it would go to the counter which would slow down how much the increment is executed.
code E002FEEF 0042D9AC (Joker for L2 + Up)
lw t0, $0000(at) (the current count of the counter)
addiu t0, t0, $0001 (increment counter by 1)
bne at, 0001234F (if it hasn't reached the amount yet, skip the rest of this code)
sw t0, $0000(at) (store the new count which is just 1 higher than before)
jump to code 30200100 004E5C98
sw 0, $0000(at) (reset the count back to 0)
The 4 bytes where the current counter amount is located.
The only things I'm not sure of how or what to do is to tell the code where to store the current count. It would be nice though. Any time you have some code to do something like cycle through inventory, this could be incredibly useful so 1000 items don't go by in the blink of an eye.
2 byte writes (1, 7) = Need the address OR'd by 0x1FFFFFE
4 byte writes (2, 4) = Need the address OR'd by 0x1FFFFFC
Pointer write (6) = Needs to check if the pointer address obtained from the address is 0x0000000. If it is, then make the code skip to the end and execute nothing. Any modification to address 0x0000000 will instantly freeze a game.
The IF's (D, E) = I might suck at explaining this. If I put this:
e004feef 0042d9ac
10444444 00000001
I would need that yellow 4 to change itself to a 1 because there is only 1 code after it to execute. I don't know how the cheat engine works, I'm fairly clueless. If this doesn't set to 1 and you had more codes on after this, would it cause the cheat engine to skip the next 3 lines of the next codes?
Timer (B) = I didn't even check it. I'm just thinking of how to even do this. This would depend on each game and everything, but this would reset itself and be usable for anyone who has a crumb of patience to add this in with the increment codes. Here's my example idea:
E002FEEF 0042D9AC (Joker for L2 + Up)
B0010000 0001234F
30200100 004E5C98
# lines to skip
skip until it's been skipped this many times, and then reset
When you press L2 + Up, it would go to the counter which would slow down how much the increment is executed.
code E002FEEF 0042D9AC (Joker for L2 + Up)
lw t0, $0000(at) (the current count of the counter)
addiu t0, t0, $0001 (increment counter by 1)
bne at, 0001234F (if it hasn't reached the amount yet, skip the rest of this code)
sw t0, $0000(at) (store the new count which is just 1 higher than before)
jump to code 30200100 004E5C98
sw 0, $0000(at) (reset the count back to 0)
The 4 bytes where the current counter amount is located.
The only things I'm not sure of how or what to do is to tell the code where to store the current count. It would be nice though. Any time you have some code to do something like cycle through inventory, this could be incredibly useful so 1000 items don't go by in the blink of an eye.

Comment