Topic: FF6 Improvement Project

[Leviathan Mist]

Unless you're coding an emulator or using an IPS patch, it doesn't really make a difference whether or not your ROM has a header. The only reason it matters with IPS patches is because the data gets shifted depending on which ROM was used. Most people just happen to use a headered ROM for FF3us when making IPS patches.

From what I understand, headers are, or were, necessary for dumping ROMs directly from the cartridges, but emulators don't need them to run the game.

One other thing to note is that ROMs labeled with [!] typically do not have a header, while those without the ! typically do.

[Tzepish]

A helpful thing that darkmage can do is add info to the readme that explains to the user how to tell which type of rom he has (right click on the file, view number of bytes)

[Odbarc]

One other thing to note is that ROMs labeled with [!] typically do not have a header, while those without the ! typically do.

So that's what that means. Cool info.

[TheNattak]

For those that didn't know, headers can easily be applied or taken off with SNESTool. 

[Lenophis]

What's the point of Header exactly? Why have one at all? What's the benefit of or of not having this on roms?

There never was any point. They mostly belong to copiers, and most programs from the previous 15 years were built to need the headers because nobody really knew/cared. They only matter today if you have such a program that still needs a header.

[angelo26]

TheNattak and I were messing around with the improvement patch v0.92, and we found this bug in battle. In the options menu, if you change the style of the commands from window to short, and you access the "row" command in battle, this happens:



To us it seems like a problem in the code that erases the windows. The same problem happens with the "defense" command.

If someone knows how to fix it and/or reveal the address at where the code is not functioning will be greatly appreciated. The code to expand windows in battle may be close..so any help will be greatly appreciated.

[darkmage]

A helpful thing that darkmage can do is add info to the readme that explains to the user how to tell which type of rom he has (right click on the file, view number of bytes)

That's a good suggestion. I personally don't care for the headers being there, as they're created by the cartridge copiers, but I never bothered to remove the header on the rom I'm using as a project base. There are a couple of ways to add them in, but I haven't messed with that at all.

TheNattak and I were messing around with the improvement patch v0.92, and we found this bug in battle. In the options menu, if you change the style of the commands from window to short, and you access the "row" command in battle, this happens:



To us it seems like a problem in the code that erases the windows. The same problem happens with the "defense" command.

If someone knows how to fix it and/or reveal the address at where the code is not functioning will be greatly appreciated. The code to expand windows in battle may be close..so any help will be greatly appreciated.

Dammit, I suck at testing... 

I don't play that way because I don't like the window format...but I didn't do anything except change the frame graphics. Does this happen in the original game as well?

[angelo26]

no, this problem isn't present in the original game.

I applied the v0.92 of the improvement patch to a clean FF6 rom and that happened. Some bytes are shifted around the C1 bank from one of the patches included, so that's probably the problem here...

[darkmage]

I'll take a look at the documentation throughout the patches and try to find which one might be causing the issue.

[assassin]

i don't necessarily suspect any of mine, but here are ones that write to battle menus:

- Alphabetical Rage patch
- Step Mine's missing digit fix  (only changes one byte, specific to MP cost display, so hard to imagine it'd have side effects.)
- Brushless Sketch patch
- Control menu responds poorly to MP change fix

[angelo26]

I remember lenophis mentioning something about the Brushless Sketch fix conflicting with another patch, I don't remember which exact thread he said that...

[assassin]

it was Summon This!

[Lenophis]

It was this thread. And no, I still haven't updated that patch yet. I'm in the middle of getting another patch ready for release. A big patch.

[darkmage]

I still haven't updated that patch yet. I'm in the middle of getting another patch ready for release. A big patch.

If it's what I think it is, then 

Also, I didn't use the Summon This! patch, as angelo26 knows. 

I haven't had a chance to dig since work's been busy this week, but out of the patches I've seen named, I don't believe any of those would cause it. Since I haven't looked, I can't be sure, so I'll confirm that before I say any more.

[darkmage]

So I found the culprit causing the Row window issue, and it wasn't the patch I expected...the Esper Battle Menu fix is causing this issue on a clean FF3us 1.0 headered ROM.