Author: Marzo Sette Torres Junior
Date: 09-10-13 19:20
Looking at the TFL CVS to refresh my memory, this is how I implemented that part back then: the "src" dir has several "sh" and "bat" files for building it; a "src/graphics" dir with images and a "src/ipackscripts" with ipack scripts; and a "data" dir where the new palette file is defined.
The build scripts call ipack for all scripts in "src/ipackscripts" with the command line
ipack -c ipackscripts/<filename>
where <filename> indicates the script in question. The build scripts expect you to run them from the "src" dir.
The ipack script for the title screen is called "new_mainshp.ipk", and its contents are as follows:
The paths are all relative to the "src" dir, which is where the build scripts expect to be run from. In "src/graphics/Wizardry_Dragon", you will see that the new logo file is called "logo_00.png", and there are no more "logo_XX.png" files.
So, here is the simple version:
Create a file called "new_mainshp.ipk" and paste the following in it:
In the same directory, put the new palette (with the name "intropal.pal") and the new title screen (with the name "logo_00.png"). Then create a file called "make_mainshp.bat" in this same dir and paste the following in it:
ipack -c new_mainshp.ipk
With all that in place, double-click on the bat file and your new "mainshp.flx" file should appear, ready to be copied to the patch dir.
FYI, I found out why some palette files crash ES -- they are double palette files, and ES currently has no support for it. I won't have time to properly fix this until next week, but in the mean time, slicing the palette in half, editing each half in ES separately, then merging the halves back together before running it through ipack as described above will work.
Marzo Sette Torres Junior
aka Geometrodynamic Dragon
How To Ask Questions The Smart Way