- 82
- Posts
- 7
- Years
- California
- Seen May 20, 2020
IF THIS I FOUND OUT PEOPLE ARE USING THIS TUTORIAL TO DISMANTLE ROMS WITHOUT THE AUTHORS PERMISSION, I WILL TAKE THIS TUTORIAL DOWN.
This is just a quick tutorial. No photos or anything. You're expected to know about pointers and repointing.
It seems like a lot of people were having issues with this so I decided it would be best to make a tutorial. What we will be doing is creating a tool .ini file from scratch. Once you know how to do this, you will be able to build any ini file for any rombase(ALL GEN 3 GAMES) for any tool. Its actually really easy once you understand what a pointer is. You need a hex editor and an ini file. Ill be using Petuuuhhh's rombase for this.
Step 1.
Open up a clean rom(im using FireRed), the rombase in question, a pge ini(could be g3t or whatever but pge's ini has a lot of data which is nice) and and a copy of pge inis(or whatever youre actually editing).
Step 2.
First, I go in pge's ini and the first thing is "Item Data". We will skip this as i dont believe he has repointed the item data. If youre building an ini for sayyyy...gaia...you need to check EVERY SINGLE ONE. Lets skip to pokemon data. In the clean ini, the pokemon data is at offset 254784. Petuuuhhh's rom at this offset has no data(FF). Lets take this offset and put it into little endian format. 84 47 25 08 is what we get. Ctrl + F and search for this in the clean rom.
Step 3.
I found "84 47 25 08" at offset 0x1BC so I will go to this offset in my rombase. This offset contains "E8 40 A0 08" or A040EB. Check to see if there is data there...there is. Repeat this process.
Step 4.
Insert A040EB in your copied ini file for the pokemon data or whatever your offset contained. Make sure to follow the same format as the ini file.
Side notes:
If you have permission from the rom author and you want to build an ini, you will mostly change 80% of the offsets in the ini.
If g3t says "missing info" for a specific offset you changed, put &H in front of the offset.
PGE wont open pokemon data until youve repointed the pokemon data, moves, move data, palette data, abilites data, ability names and much much more. It easier to go down the list and check everything rather than changing what you think needs to be changed. Trust me.
This is just a quick tutorial. No photos or anything. You're expected to know about pointers and repointing.
It seems like a lot of people were having issues with this so I decided it would be best to make a tutorial. What we will be doing is creating a tool .ini file from scratch. Once you know how to do this, you will be able to build any ini file for any rombase(ALL GEN 3 GAMES) for any tool. Its actually really easy once you understand what a pointer is. You need a hex editor and an ini file. Ill be using Petuuuhhh's rombase for this.
Step 1.
Spoiler:
Open up a clean rom(im using FireRed), the rombase in question, a pge ini(could be g3t or whatever but pge's ini has a lot of data which is nice) and and a copy of pge inis(or whatever youre actually editing).
Step 2.
Spoiler:
First, I go in pge's ini and the first thing is "Item Data". We will skip this as i dont believe he has repointed the item data. If youre building an ini for sayyyy...gaia...you need to check EVERY SINGLE ONE. Lets skip to pokemon data. In the clean ini, the pokemon data is at offset 254784. Petuuuhhh's rom at this offset has no data(FF). Lets take this offset and put it into little endian format. 84 47 25 08 is what we get. Ctrl + F and search for this in the clean rom.
Step 3.
Spoiler:
I found "84 47 25 08" at offset 0x1BC so I will go to this offset in my rombase. This offset contains "E8 40 A0 08" or A040EB. Check to see if there is data there...there is. Repeat this process.
Step 4.
Spoiler:
Insert A040EB in your copied ini file for the pokemon data or whatever your offset contained. Make sure to follow the same format as the ini file.
Side notes:
Spoiler:
If you have permission from the rom author and you want to build an ini, you will mostly change 80% of the offsets in the ini.
If g3t says "missing info" for a specific offset you changed, put &H in front of the offset.
PGE wont open pokemon data until youve repointed the pokemon data, moves, move data, palette data, abilites data, ability names and much much more. It easier to go down the list and check everything rather than changing what you think needs to be changed. Trust me.