My Hacked Rom crashes...will EXPLAIN

OK, I tried with it both of what I had and this came up.
Lunar IPS (LIPS) Version 1.01
Apply IPS Patch Log

Offset Size RLE IPS_File_Range IPS_File_Size
------ ---- ID 00000000-00000004 5
126423 D No 00000005-00000016 12
126454 C No 00000017-00000027 11
126492 E No 00000028-0000003A 13
134790 30 No 0000003B-0000006F 35
1348C8 21 No 00000070-00000095 26
1348F0 4 No 00000096-0000009E 9
2CE680 4 No 0000009F-000000A7 9
2CE802 1 No 000000A8-000000AD 6
2CE80A 1 No 000000AE-000000B3 6
2EB41E 8 No 000000B4-000000C0 D
2F4C46 52D1 No 000000C1-00005396 52D6
------ ---- EOF 00005397-00005399 3

Total Patches: B (11


@Pocoloco...Lethal effects such as monsters like Dragons that appear on Floating Continent dying and casting Shell when defeated and the entire party faints. Or the game freezing up when I enter the Narshe "we got 'em trapped now!" battle. I have gotten these effects before in a rom when using the patch. I just mentioned the Narshe one because its the easiest to explain.

All patches I make start on a vanilla version of the rom. I have never once heard that YY-CHR rearranges the data at all Poco, is there any proof of this?

not any solid proof atm

but it could be possible that when importing images via yy-chr data can be re-arranged

other then that the only other possible explanation is that u put the axes in a rom that wasnt clean by accident

Anythings a possibility, although YY-CHR overwrites existing data, or adds new data. It doesn't add random bytes, at least no one has ever said that before over on the RomHacking.net forums.
If anything, I'd say it's FF3usME's fault with the map thing.

Well I'll quote myself on this one:

Code:

Offset    Size    RLE    IPS_File_Range       IPS_File_Size
------    ----    ID     00000000-00000004        5
126423       D    No     00000005-00000016       12 (palette change)
126454       C    No     00000017-00000027       11 (palette change)
126492       E    No     00000028-0000003A       13 (palette change)
134790      30    No     0000003B-0000006F       35 (unknown data change...not on the ROM map)
1348C8      21    No     00000070-00000095       26 (unknown data change...not on the ROM map)
1348F0       4    No     00000096-0000009E        9 (unknown data change...not on the ROM map)
2CE680       4    No     0000009F-000000A7        9 (previously unused space)
2CE802       1    No     000000A8-000000AD        6 (graphics change)
2CE80A       1    No     000000AE-000000B3        6 (graphics change)
2EB41E       8    No     000000B4-000000C0        D (previously unused space)
2F4C46    52D1    No     000000C1-00005396     52D6 (world maps data and tiles graphics)
------    ----    EOF    00005397-00005399        3

Like I said in details on my post on the previous page, there is 2 writing of data in a "unused space" and 3 writing in a area labeled as "unknow data". The "unknown data" changes could be due to the palette changes because there is 3 entries, but who knows, since we don't know what kind of data is there. As for the data written in the "unused space", maybe it is used by FF3usME when you save and that could be verified by saving with FF3usME without changing anything. The world map data switching is FF3usME fault like Zeemis said and it's shouldn't affect or corrupt the game. I did a long edit to my post last night and you guys maybe haven't seen it...

that could be true as well