Topic: Developing FF4kster: a comprehensive editor for FF4

[Pinkpuff]

It's definitely not a known bug, and I am unable to reproduce the behaviour.

I suspect that your rom may indeed be incompatible for some reason; especially when it's the command editor in particular that's messing up since that primarily deals with code as opposed to data. Are you certain your rom is version 1.1? If so, are you certain it hasn't had any patches applied or been modified by any other editor?

[Eternal248]

What would be the best way to tell if it's 1.1? I'm fairly certain I'd used this ROM with this editor before, though it's possible I hadn't. No patches have yet been applied to the ROM.

[chillyfeez]

Eternal248 - try this:
Download Yousei's Editor.
It ONLY works with version 1.0.
If it loads your ROM, then you are using the version that is not compatible with FF4kster.
If it refuses to load the ROM, then you're using version 1.1.

[Eternal248]

Just attempted to open it in that editor, and the ROM wouldn't open. I'm stumped now, haha.

[Pinkpuff]

Open your rom in a hex editor and tell me what byte is at 1E897 and at 1E8A5.

Or if your rom is unheadered then instead I'll need the bytes at 1E697 and 1E6A5.

[Eternal248]

I can't remember if it's headered or not, so I'll just give you each of the values.

1E897: 09
1E8A5: 60

1E697: C8
1E685: 26

Hope this helps!

[chillyfeez]

If you open your ROM in the hex editor and it reads the length as 100200 bytes, or (if this is easier) the first 32 lines are mostly 00s then your ROM has a header.

[Pinkpuff]

Ok so my guess is that your rom is unheadered and that it's reading C8 as the spell for Gird; that's spell 200 in decimal, or in other words, past the end of the spell list. Thus, the editor messes up and crashes.

For whatever reason, whether due to it being an incorrect version or otherwise corrupted or messed up somehow, the code in that part is not what it should be. My only advice would be to try to find a fresh copy of the v1.1 rom.

[Pinkpuff]

Looks like the Targeting works perfectly! That is so nice to have in the editor and cuts down on the need to jump to and fro with the Hex Editor and FF4kster. There's also another easy piece (at least I would imagine its easy) to implement that Chillyfeez discovered long ago, but it seems like the info fell through the cracks and that is the Charge Time for the various commands.

there is a table in ROM at A0189 that contains one-byte-per-command references to the duration set to perform each command. Most of them are 00, which is immediate. 01 is not one second, though. These are pointers. I haven't tested all 256 options (and probably won't) but the following are used:
00: (most commands) immediate
01: (Charge) 5 seconds
02: (Dark Wave, a few others) 2 seconds
04: (Salve, Aim) 1 second
FE: (not used, but I tested it to see if it would crash the game - it doesn't) several hundred seconds

I'm unsure if its with a header or not, but it would make a nice addition.

I can't find that chart... not at A0189, and not at A0389 either...

  Nevermind, I found it the hard way at A0089; at least I think that's it... it has 0 for Charge instead of 1, but they seem to match up otherwise.

[chillyfeez]

Sorry for the headache, Pinkpuff.
As Grimoire's noticed before, sometimes my skills as a scribe leave something to be desired.

[Pinkpuff]

No sweat! Believe me, I'm very appreciative for all the work you've done finding things and compiling it all! The odd typo is nothing to fret over.

The delay (index) has been incorporated into the command editor, as has the statuses under which the commands are disabled. Currently I'm working on the equipment requirement ranges and then there should be an update later today.

[Eternal248]

Yeah, I acquired a different ROM and it works perfectly. Thanks for all of your help and investigation! :)

[Pinkpuff]

Updated again! 

Everything from the commands should be implemented now. Let me know if I missed anything, or if anything isn't working correctly.

Yeah, I acquired a different ROM and it works perfectly. Thanks for all of your help and investigation! :)

No problem, glad to hear it!

[Grimoire LD]

I will have to test this tomorrow afternoon! Thanks for the update!

[Grimoire LD]

Alright! Now This was such a substantial update! Everything worked perfectly! The ranges, the command additions, and solo battles all worked out fantastically! If I may make one suggestion though... Can Formations show up with the necessary information on that Formation as well?

So say I set "Formation 229" To the side in a separate box it would show "1 Baigan, 1 Right Arm, 1 Left Arm". That way we have a better idea on what we're choosing without constant cross referencing.

The only issue I saw that appeared was that my custom Sing command broke when I saved in this version... which is a bit major to me, for obvious reasons. I should note that I did not touch the Commands section in this test, I thought at first it might have only crashed because of me going to the Command menu and looking at the data, but just saving breaks it. Does the data save default data somewhere to cause this?