Well, this is odd... upon an in depth checking of my backup last night, I found that it was as up to date as the broken one, minus a map I had started working on (which was fomally the generic Weapon Shop map), so I think I'll chalk it up to bad luck and breathe a heavy sigh of relief.
To be safe, I'll make a new map somwhere else, in case that had a part in it haha.
Also while testing in FF4kster, I found that if you do the following:
1:Go to an NPC in the NPC Editor with "EMPTY" set as it's speech
2:Hit Tab to highlight the messages area
3:hit Tab again to go back to the "Empty" section (now glitched into a small square box)
4:Hit Enter
The editor will crash. For good reason I imagine, but still I think it's worth mentioning lol.
I use a similar technique sometimes when debugging FF4kster. One way to speed things along is to "binary search" your way through them instead of just going linearly:
- Assign an order to the changes.
- Apply all the changes in the "first" half
- If the problem appeared, the culprit is in the first half; discard the other half
- If the problem didn't appear, the culprit is in the other half; discard the first half
- Revert your rom to its original state
- Repeat entire process until you're down to one item; that's the cause of the issue.
This way you eliminate half the list at a time instead of one at a time.
That's a good way to determine a problem quickly! I'll keep that in mind in the future.
