ZONE DOCTOR - FF6 Editor v3.18.4 (formerly FF6LE) *EVENT EDITING SUPPORT*

Download ZONE DOCTOR v3.18.4 | Visit ZONE DOCTOR's home page

What is ZONE DOCTOR?
Zone Doctor is a third party .NET application written in the C# programming language which is capable of editing the locations and event scripts in the Final Fantasy 6/3 (US) ROM image file. It's code base, GUI, and additional features are based off of the Lazy Shell application, with a number of changes to accomodate the different format of the source ROM image. Resources and documents consulted include but are not limited to Evil Peer's FF6 Offsets Guide, Geiger's offsets compendium, Lord J's event disassembly source code, Imzogelmo's updated event disassembly, and Yousei's compression code. To see the complete history of changes made from version to version, view the changelog.txt file.

Note: Zone Doctor is capable of working with both headered and headerless ROMs, but if you wish to view/modify the source files remember that the program is designed to work with a headerless ROM buffer array. Thus all offset values in the source files reference a headerless ROM.

Notes on latest/recent release(s)...
Full event script editing is now supported. v3.18.x is an update from FF6LE v1.0, the changes of which are almost identical to the changes undergone from Lazy Shell v2.0 to v3.18.0. The most notable, of course, is event script editing support as well as a much more highly functioning level editor. I've incorporated Lord J's location map fix code from his FF6LE rogue source (credit is given in the editor's "About" window) to make it compatible with FF3usME. Despite this being a bugfix of the beta, there still may be a possibility of ROM corruption (particularly in the event scripts editor). That is why this thread exists for posting bug reports.

Screenshots...


From the changelog.txt file:

Code:

v3.18.4 (2013-08-26)
--------------------------------------
Additions:
*Can now import world map data from a fresh ROM

Changes:
*Image drawing code now safer and much faster
*Locations: world maps draw yet another 2x faster than before!

Fixes:
*Never removed header after save b/c romLength not being updated
*Some problems with new history logging format, dragging objects
*Locations: shouldn't be asking to save if already saved
*Locations: changing world map's tile properties not updating tilemap


v3.18.3 (2013-08-16)
--------------------------------------
Changes:
*History logging now more practical, loading times now faster
*Locations: locations now draw 2x faster, world maps 4x faster!
*Locations: raised maximum exits per location to 64

Fixes:
*Event Scripts: fixed and updated command $A0 (countdown timer)
*Locations: crash if try to drag bars in palette editor
*Locations: tilemaps and tilesets were not clearing if all set to 0
*Locations: shouldn't be checking if 0 tilemap for world maps
*Locations: crashes sometimes drawing if layers different sizes


v3.18.2 (2013-08-06)
--------------------------------------
Fixes:
*Graphics Editor: crash when making selection < 4 pixels wide/high
*Graphics Editor: not nulling selection when delselecting
*Locations: sizing image when updating tilemap was ignoring zoom factor
*Locations: assembler code for solidity set still had bugs, now perfect


v3.18.1 (2013-07-30)
--------------------------------------
Additions:
*Locations: gave several unknown values descriptive labels/controls
*Locations: architecture importing/exporting added

Changes:
*Now recalculates checksum when saving a modified ROM
*Locations: long exits can be click/dragged anywhere on the field
*Locations: tags containing script stubs now more offset precise

Fixes:
*Restore elements storing location map data to tilemaps, corrupting them
*Graphics Editor: wrong picture size for world map graphics
*Event Scripts: crash when update offsets if on very last script
*Locations: finally got layer 3 drawing correctly, colors and all
*Locations: adding new exits, events, NPCs, etc. not enabling groupboxes
*Locations: changing exit destination not updating tag
*Locations: crash closing tile editor b/c solidity tiles bad assembler
*Locations: world map tile editor not redrawing in world map format
*Locations: tile editor loading tile 0 if doing auto-update
*Locations: changing destination of exit casting as byte and not short
*Locations: minimaps not saving b/c never actually decompressing first
*Locations: crash when close locations if a subwindow still open
*Locations: ignores/won't load long exits if no short exits in location
*Locations: not calculating free short exit space correctly
*Locations: couldn't draw tiles to lower part of tilemaps
*Locations: crash if try to draw tile beyond boundaries of tilemap
*Locations: never was actually saving the graphics!
*Locations: undo not being set to manual count on load/reload
*Locations: BG color should always be filled with solid black
*Locations: NPCs not redrawing when sprite # changed
*Previewer: not using correct sprites for characters in save state

If you find or encounter a bug...
As is the case with releases containing several additions, there is always the possibility of new bugs surfacing. As usual, any bugs encountered please report them here. The recently added custom exception/error message box makes this easier and less trivial. If you encounter an error read the brief instructions in the message and make a new post here. You can click "ignore error" if you don't want to close and lose your work. Always remember to frequently save your work. Make back-ups using the options in the settings. Use the notes feature to keep track of changes and keep organized, etc.

CRASHES
If the editor crashes, copy/paste the contents in the crash window here, explaining what you did before the crash occurred.

CORRUPTED DATA
For corrupted data issues such as garbled/glitched graphics, text, etc. that you encounter after modifying the ROM, please answer each of the following FOUR questions:
1. What was the last thing you changed before you first encountered the problem?
2. Were you using a fresh ROM with OK checksum (see box at top of main window)?
3. If answer "no" to #2, what portions of the ROM did you modify before the problem? Is it a hack?
4. Do the problems appear in the *editor*, the *emulator*, or *both*?

OTHER BUGS
For all other bugs encountered, such as failure of the editor to perform a task like saving or changing data, incorrectly modifying or displaying data, etc. just briefly explain what the problem is and what you're doing to cause it.