Hmm thanks for the answer, but I don't think it was the pal table. I just checked, and I do have all three pointers, and they even match where they are in the hacked engine patch.
Specifically 0x05F4D8, 0x05F570, and 0x05F5C8. The only difference is that they're not pointing to 0x081A2400.
I'm pretty sure that the issue is with the overworlds table, because the tool seems to be reading the new table with pointers to the other overworld tables (and there's only one pointer right now) as a pointer to an actual overworld, which obviously isn't going to load correctly.
I guess the better question is how the tool "knows" when you're using a table of pointers to 1 of 256 tables, as opposed to automatically reading a table as a table.
1) The pointer to the original overworld table is 0x8DFDF8
2) I wanted to insert their data in the same way that is used with JPAN's engine, so up to 256 tables pointing to tables of 256 overworlds.
3) I did repoint the original overworlds table to the 0xF00000 range, but I also did update the pointer to it at the offset indicated in my answer to (1)
Btw, I don't see a need for you to update the tool. All I needed was how the tool "knows" when it is using JPAN's table method, and I can easily update my routines / location of literal pools to be compatible :)