[ASM & Hex] Help with Ghoulslash's TH/HM Expansion in FR

[JayAihara]

So I wanted to expand the number of TMs in my rom hack so I followed Ghoulslash's tutorial but I still found myself with questions.

1. Step 3 - New Compatibility Table
- I don't understand what he's doing here. I assume he wants the old compatibility table to be repointed to a lot for extra space BUT I'm not aware of the address of this table nor how long it is. Would anyone happen to know?

2. Step 5 - "1. change free RAM to your own location"
- I have installed JPANs Save block recycle but I'm not sure how to use it in the way this tutorial is mentioning. Is RAM a specific pointer in JPANs save block recycle that I need to have the asm code pointed to? If so, what is that pointer's address?

Any help would be greatly appreciated, Thank you!

 

[Koople]

So I wanted to expand the number of TMs in my rom hack so I followed Ghoulslash's tutorial but I still found myself with questions.

1. Step 3 - New Compatibility Table
- I don't understand what he's doing here. I assume he wants the old compatibility table to be repointed to a lot for extra space BUT I'm not aware of the address of this table nor how long it is. Would anyone happen to know?

2. Step 5 - "1. change free RAM to your own location"
- I have installed JPANs Save block recycle but I'm not sure how to use it in the way this tutorial is mentioning. Is RAM a specific pointer in JPANs save block recycle that I need to have the asm code pointed to? If so, what is that pointer's address?

Any help would be greatly appreciated, Thank you!

Do you have a link to the tutorial?

For expanding TMs/HMs I would guess that the old compatability table is dead and you need to make a new one yourself in free space. The tutorial might have a pointer address or assembly code address you need to change to your new table address.

If this is the save block recycle you are talking about, then it causes the game's save file to include RAM from 0x0203C000 to 0x0203CEC4. All of this is unused by the game, so you just need to find a block of it that you haven't used with any other hacks. And then there is probably some pointer in their assembly routine you need to change to that RAM address.