Skip to content
Kimonas Sotirchos edited this page Sep 5, 2018 · 5 revisions

My rom crashes in overworld editor. after using your tool

That's because OWM repoints the original table when a rom is loaded for the first time. To fix that open up the Sprites.ini of Overworld Editor. In the Sprite Bank for your rom insert the address of "Data Address" and in the SpritePaletteHeaders insert the address of "Palette Table" from OWM.

Is there any way to use NSE 1.7.5 after using this tool?

Create an ini file for nse with these addresses [BPRE] Inherits: BPRE Sprite table = &H[Insert Pointer Address here] Palette table = &H[Insert Palette Table here] [/BPRE]

How to select the offsets where data gets reloaded?

OWM will start writing the data for all its tables starting from the 'Free Space Start' in the ini and onwards (of course if there is data there it will write when it finds free space from there on). This means that you can change the value of that option and it will reload the data to the address you give.

Isn't it too wasteful, from free space perspective, to repoint all these tables?

No, the data just is just moved to another place. This means that the original data gets whipped out (replaced with 0xFF) and can be normally used.

So what is the point of repointing anyways?

  1. because the way OWs were inside the rom, it was impossible to dynamically know how many frames each OW had. To deal with this the other Editors hard coded the number of frames for each OW. What I did was write a special pointer to the end of the frame data of each OW. This way I could calculate the total frames size of each OW and consequently know its number of frames. Because of that I would have to repoint the frames data of all the OWs and add that pointer at the end of each one of them.

  2. If I didn't repoint the table it wouldn't be possible to add more OWs as there was no free space in both OW Pointers Table, OW Data Table and frames pointers Table.

  3. Some OWs didn't have walking sprites (like players mom or Gym leaders in Fire Red) but had 9 frames. Thats because frames 3-8 were the same as 0-2. But, the problem with that is that those OWs had frames data only for the first 3 frames. This means that you cant actually insert 9 frames but 3, since the walking frames were the same with the first three. To deal with this when OWM repoints the original table it adds the data of those frames in those OWs so you can normally insert as many frames as it actually has.