Scarica Magitek Madness Rom Hack

Final Fantasy 3 (US/SNES), Final Fantasy 6 (JP/SFC)
Magitek Madness fix patch

CONTENTS:
FF3-MagitekMadness-H0.ips: The fix patch for a headered SNES v1.0 ROM file. Apply to fix the Magitek Madness Bug.
FF3-MagitekMadness-HR0.ips: The reverse patch for a headered SNES v1.0 ROM file. Apply to reverse all changes made by the previous patch.
FF3-MagitekMadness-HS0.ips: The compatibility patch for a headered SNES v1.0 ROM file. Apply after the H0 patch only if "Side Saddle" has already been applied.
FF3-MagitekMadness-N0.ips: The fix patch for a non-headered SNES v1.0 ROM file. Apply to fix the Magitek Madness Bug.
FF3-MagitekMadness-NR0.ips: The reverse patch for a non-headered SNES v1.0 ROM file. Apply to reverse all changes made by the previous patch.
FF3-MagitekMadness-NS0.ips: The compatibility patch for a non-headered SNES v1.0 ROM file. Apply after the N0 patch only if "Side Saddle" has already been applied.
FF3-MagitekMadness-H1.ips: The fix patch for a headered SNES v1.1 ROM file. Apply to fix the Magitek Madness Bug.
FF3-MagitekMadness-HR1.ips: The reverse patch for a headered SNES v1.1 ROM file. Apply to reverse all changes made by the previous patch.
FF3-MagitekMadness-HS1.ips: The compatibility patch for a headered SNES v1.1 ROM file. Apply after the H1 patch only if "Side Saddle" has already been applied.
FF3-MagitekMadness-N1.ips: The fix patch for a non-headered SNES v1.1 ROM file. Apply to fix the Magitek Madness Bug.
FF3-MagitekMadness-NR1.ips: The reverse patch for a non-headered SNES v1.1 ROM file. Apply to reverse all changes made by the previous patch.
FF3-MagitekMadness-NS1.ips: The compatibility patch for a non-headered SNES v1.1 ROM file. Apply after the N1 patch only if "Side Saddle" has already been applied.
FF6-MagitekMadness-H.ips: The fix patch for a headered SFC ROM file. Apply to fix the Magitek Madness Bug.
FF6-MagitekMadness-HR.ips: The reverse patch for a headered SFC ROM file. Apply to reverse all changes made by the previous patch.
FF6-MagitekMadness-HS.ips: The compatibility patch for a headered SFC ROM file. Apply after the H patch only if "Side Saddle" has already been applied.
FF6-MagitekMadness-N.ips: The fix patch for a non-headered SFC ROM file. Apply to fix the Magitek Madness Bug.
FF6-MagitekMadness-NR.ips: The reverse patch for a non-headered SFC ROM file. Apply to reverse all changes made by the previous patch.
FF6-MagitekMadness-NS.ips: The compatibility patch for a non-headered SFC ROM file. Apply after the N patch only if "Side Saddle" has already been applied.
readme.txt: This file.
Magitek Madness.asm: An assembly format index of code changes.
Magitek Madness-Fixed.rtf: A text format index of the new code.
Magitek Madness-Original.rtf: A text index of the old code.

URGENCY:
Low to medium. The fact that it fixes Side Saddle as well makes it more important, but both glitches are still graphical.

PURPOSE:
When a character is subject to the Doom spell, the Grim Reaper appears and drags a translucent image of their sprite away off the top of the screen; obviously, this represents their soul leaving their body. However, if that character is wearing Magitek Armor, then the soul will be missing its legs. The reason for this is that the soul sprite and the actual sprite share the same location in VRAM. This patch creates a copy of the sprite with legs, and that sprite will float away.

This sprite also fixes another bug that is also fixed by my Side Saddle patch, rendering that patch obsolete. However, if Side Saddle has been applied, then this patch will not fix the aforementioned bug, and will thus be rendered useless. To circumvent this, either remove Side Saddle or apply the included compatibility patch (do NOT do both). Those two steps, along with applying the fix patch, can be done in any desired order. The compatibility patch should be applied ONLY if Side Saddle has been applied.

VERSION HISTORY:
v1.2 (March 18, 2017): Added a JSR where one was needed. Also added a function call to correct VRAM in the case where Doom misses.

v1.1 (April 29, 2016): Fixed an erroneous byte that was making things go very wrong.

v1.0 (April 8, 2016): Initial release.