Monster level up patch

Has anyone ever made a fully-reassemblable file of the game's assembly? I have one working for just the upper C2 bank (you know, the battle engine part). I don't think it would be terribly hard to do the same for the other banks and put each in a file, and use the include function to make a whole project of it.

I can write a console app that strips the XX/XXXX: from each line of the text disassembly, put a ";" before each comment and put a $db before each data byte of the small tables scattered through the disassemblies. Given we agree on using xkas 0.06 as assembler that leaves only the branchings (BRA, BCC, BEQ, BNE, BCS, etc.) to label manually to have a functional xkas file.

Even the data could be labeled and included as bin files. That's not too useful if you don't have an editor that can find the data, though. Really it would be great to have editors that can take a known address for the starting point. The assembly, properly labeled, can point the loads at the correct spots.

Some more mature romhacking scenes work from split disassemblies and just include binary blobs of data and graphics, then code editors or conversion tools to just work with those data files. You can make code and data changes, then just reassemble a new Rom. It's awesome. Sonic hackers do this I think, and there's a full split disassembly of FF1 on Rhdn.

What you both describe would be the next step to be on the right track of realizing my vision of FF6 hacking (the hobby not the forum). To make this project a reality, I'd be willing to at least make my modified FF6LE/ZoneDoctor (limited to LE content) and FF3se read offsets from code and allow relocalization / offset choice of expanded data. Editing bin data files directly from the editors is a step further that could be done also though it require the source code of all useful editors.

I was never able to compile properly FF3se, the changes made were done by Hex editor. It worth another try though. One concern is FF3usME. Since now 95% of the data and formats it can edit is written in threads and wikis, I wonder why Lord J keep secretly his source code. MFC is not longer use to my knowledge and the app does nothing ground breaking (from the features point of view, displaying 4BPP graphics from a ROM, editing offset/byte arrays and performing bits shift or boolean operations is common). My point is changing usME code is almost central if you plan on editing bin files data and be able to re-assemble your ROM. I have no solution to this other than explaining this to Lord J and see. If someone was before (or still) getting in touch semi-frequently with him, it would be cool to try to get a hold of him. I can try but fear I'll never receive and answer (or one in 8 months).

There's a full disassembly labeled and formatted to be reassembled of the C3 bank by Magno. It's in Spanish but it's ready to go.

I have his C1 ASM file in my emails! I'll put it up on the wiki soon.