• Welcome to Final Fantasy Hacktics. Please login or sign up.
 
April 19, 2024, 06:45:54 am

News:

Don't be hasty to start your own mod; all our FFT modding projects are greatly understaffed! Find out how you can help in the Recruitment section or our Discord!


Storyline Progression in Rad 3

Started by JantheX, October 09, 2014, 06:38:53 pm

JantheX

October 09, 2014, 06:38:53 pm Last Edit: October 28, 2014, 04:51:45 pm by JantheX
Hi guys,

Question time:
1. I've been making use of Pokeytax's RAD 3 spreadsheet, which I downloaded here (http://ffhacktics.com/smf/index.php?topic=7031.0).  It is awesome.  But.
2. I want to make use of the A0 column for storyline progression.  There's a discussion between Pride, Glain, and Poxeytax on page 3 of that topic (http://ffhacktics.com/smf/index.php?topic=7031.40) that indicates that this is an integer value that increments by 1.  Apparently it is 0x006E from this list (http://ffhacktics.com/instructions.php?id=B0).
3. When I try to make use of this column in the spreadsheet, I end up tripping error where all of the new jobs bug out (as in, are automatically mastered and have no text connected to them) and all of the sprites associated with them become Chapter 1 Ramza.  This last part is mentioned by Jack of All Trades on pages 6 and 7 of the topic as being related to patching more than once, but I find that I only see this bug when I attempt to make use of the column in the spreadsheet.  I suspect I'm just using the column wrong somehow.
4. This error has occurred both when I start with 6E as the value from which I increment, and when I start with 01.  I'm not sure what I'm doing wrong.

I've included the .xml files for both the "just fine" and "way too many Ramzas" RAD patches I've tried.

If anyone can help that would be amazing!



TLDR: What do I put in the AO column of Poxeytax's RAD 3 spreadsheet to get it to do what it is supposed to do?





EDIT:  Turns out that the secret to making the AO column of the spreadsheet work was in putting an apostrophe before the bit when I entered it into the spreadsheet.  I'm using Open Office, and unless you literally type '01, the spreadsheet converts 01 into just 1, and you end up with screwy code on the .xml tab because there aren't enough digits to form full bits.  Reformatting the cells to display another leading zero doesn't actually add another zero to the value in the cell, which was what I had attempted previously to make the entries look right, and so I got the messed up code I was describing initially. As long as you enter hex integers with an apostrophe out front this part of the spreadsheet works beautifully.  I'm a little embarrassed at how long this took to figure out.