FF3ed

========================================================================
       CONSOLE APPLICATION : EventDisasm
========================================================================


AppWizard has created this EventDisasm application for you.  

This file contains a summary of what you will find in each of the files that
make up your EventDisasm application.

EventDisasm.dsp
    This file (the project file) contains information at the project level and
    is used to build a single project or subproject. Other users can share the
    project (.dsp) file, but they should export the makefiles locally.

EventDisasm.cpp
    This is the main application source file.

EventDisasm.rc
    This is a listing of all of the Microsoft Windows resources that the
    program uses.  It includes the icons, bitmaps, and cursors that are stored
    in the RES subdirectory.  This file can be directly edited in Microsoft
    Visual C++.

/////////////////////////////////////////////////////////////////////////////
Other standard files:

StdAfx.h, StdAfx.cpp
    These files are used to build a precompiled header (PCH) file
    named EventDisasm.pch and a precompiled types file named StdAfx.obj.

Resource.h
    This is the standard header file, which defines new resource IDs.
    Microsoft Visual C++ reads and updates this file.

/////////////////////////////////////////////////////////////////////////////
Other notes:

AppWizard uses "TODO:" to indicate parts of the source code you
should add to or customize.

/////////////////////////////////////////////////////////////////////////////

========================================================================
       MICROSOFT FOUNDATION CLASS LIBRARY : FF3Edit
========================================================================


AppWizard has created this FF3Edit application for you.  This application
not only demonstrates the basics of using the Microsoft Foundation classes
but is also a starting point for writing your application.

This file contains a summary of what you will find in each of the files that
make up your FF3Edit application.

FF3Edit.dsp
    This file (the project file) contains information at the project level and
    is used to build a single project or subproject. Other users can share the
    project (.dsp) file, but they should export the makefiles locally.

FF3Edit.h
    This is the main header file for the application.  It includes other
    project specific headers (including Resource.h) and declares the
    CFF3EditApp application class.

FF3Edit.cpp
    This is the main application source file that contains the application
    class CFF3EditApp.

FF3Edit.rc
    This is a listing of all of the Microsoft Windows resources that the
    program uses.  It includes the icons, bitmaps, and cursors that are stored
    in the RES subdirectory.  This file can be directly edited in Microsoft
	Visual C++.

FF3Edit.clw
    This file contains information used by ClassWizard to edit existing
    classes or add new classes.  ClassWizard also uses this file to store
    information needed to create and edit message maps and dialog data
    maps and to create prototype member functions.

res\FF3Edit.ico
    This is an icon file, which is used as the application's icon.  This
    icon is included by the main resource file FF3Edit.rc.

res\FF3Edit.rc2
    This file contains resources that are not edited by Microsoft 
	Visual C++.  You should place all resources not editable by
	the resource editor in this file.



/////////////////////////////////////////////////////////////////////////////

For the main frame window:

MainFrame.h, MainFrame.cpp
    These files contain the frame class CMainFrame, which is derived from
    CFrameWnd and controls all SDI frame features.

res\Toolbar.bmp
    This bitmap file is used to create tiled images for the toolbar.
    The initial toolbar and status bar are constructed in the CMainFrame
    class. Edit this toolbar bitmap using the resource editor, and
    update the IDR_MAINFRAME TOOLBAR array in FF3Edit.rc to add
    toolbar buttons.
/////////////////////////////////////////////////////////////////////////////

AppWizard creates one document type and one view:

FF3Doc.h, FF3Doc.cpp - the document
    These files contain your CFF3Doc class.  Edit these files to
    add your special document data and to implement file saving and loading
    (via CFF3Doc::Serialize).

WorkspaceView.h, WorkspaceView.cpp - the view of the document
    These files contain your CWorkspaceView class.
    CWorkspaceView objects are used to view CFF3Doc objects.



/////////////////////////////////////////////////////////////////////////////
Other standard files:

StdAfx.h, StdAfx.cpp
    These files are used to build a precompiled header (PCH) file
    named FF3Edit.pch and a precompiled types file named StdAfx.obj.

Resource.h
    This is the standard header file, which defines new resource IDs.
    Microsoft Visual C++ reads and updates this file.

/////////////////////////////////////////////////////////////////////////////
Other notes:

AppWizard uses "TODO:" to indicate parts of the source code you
should add to or customize.

If your application uses MFC in a shared DLL, and your application is 
in a language other than the operating system's current language, you
will need to copy the corresponding localized resources MFC42XXX.DLL
from the Microsoft Visual C++ CD-ROM onto the system or system32 directory,
and rename it to be MFCLOC.DLL.  ("XXX" stands for the language abbreviation.
For example, MFC42DEU.DLL contains resources translated to German.)  If you
don't do this, some of the UI elements of your application will remain in the
language of the operating system.

/////////////////////////////////////////////////////////////////////////////

FF3ED v?.? (binary and source)
------------------------------

Welcome to supper!

The directory FF3Edit contains the (poorly organized, written) source for the FF3 Editor.

The directory EventDisasm contains a useful utility and source for creating a script dump
of the cut scenes and event scripts throughout the game.  (Not all event commands were
decoded at this point in development--I've tried to determine the number of parameters
used to get an accurate disassembly without knowing just what the commands do, but there
are bound to be a couple of errors.)

The other miscellaneous files in the root are table files and a compilation of all the
information I've collected about the game.  There's quite a wealth of well-organized
information about the memory map of the ROM, so have a ball, guys.

Both require Visual Studio 6, MFC, and DirectX 6 or 7 (don't remember) to compile.

Several people helped me collect information on FF3, among other things.  LordTech,
CzarDragon, and anyone else I've forgotten, thanks.

I hope that someone else can use this source to finish and improve what I started.  The
problem with "the scene" is that those who have the ability and expertise to work on the
project don't have the desire to do so, and those with the desire just don't have the
ability to complete it.  There also seems to be a great lack of Win32 programmers who
are into romhacking, and those who do don't seem to respect or care for the amount of
work that goes into creating a well-functioning and attractive user-interface, whether
from the aesthetic or the development standpoint.  This is unfortunate--as buggy as some
of the custom UI code is in the editor, I'd rather see someone fix it consistently rather
than to presume that it's too difficult to use and butcher the UI to pieces.
Unfortunately, it's doubtful that someone else could easily repair it well, as the code,
mostly from scratch, is highly tuned to my development process and way of thinking. Then
there are UI elements like the monster formation viewer, which is probably my favorite
control in the whole program, and I consider it a work of art, what with the battle
background and the enemy pictures and the ability to drag the enemies to different places
on the board.  It was great fun seeing that work for the first time.  If anyone continues
the editor and fucks that control up, by God I'll come to your house and fucking kill
you.

This project will not be supported by me any longer.  I won't touch it, the source will
be deleted off my hard drive, the CD that I burned it to when I backed up my hard drive
will be snapped in two, and I'll never touch the download on my site.  LordJ's monster
editor has developed into more, and although I don't agree with his user-interface
style, maybe he, or someone else, could use this code to some benefit.

I won't vouch for what features work or don't work in this executable, because I just
don't remember.  Play around with it, and see what little you can do with it.  Word
of warning--some parts of the editor DON'T SAVE CHANGES, so if you're messing around
and find that you're changes don't show up, that's probably why.  Also look for the
possibility of overwritten data, bad compression, and pointer miscalculations.  I can't
even guarantee it will work on your system at all.  Hey, it's unsupported.
Disappointing?  Yea.  But it's better than nothing, and beggars can't be choosers.

If any of you happen to continue this project, all I ask is that you mention that it's
"based on the source provided by Yousei/Flobbster".  After that, it's all yours.

Have fun!

--
Yousei/Flobbster
12/6/2000