Originally posted by Alcaro
A freespace finder for the unexpanded area is a good idea in theory, but dangerous in practice. First, I'm not sure how well RATS tags work in the unexpanded area, I think LM gets angry if you try. Second, unexpanded freespace is FF FF FF FF, and many tables are terminated by one or more FFs; there's no way to know whether this one FF is used or not.
I wasn't strictly speaking about the area used by SMW but more in general to have bank control over freespace. Admitting, it could pose a problem in those areas if you're unlucky enough to run into a freespace area following an $FF terminated table.
Originally posted by Alcaro
Please don't. While it is indeed slightly inconvenient, it is highly intentional: It makes two of four un/headered sfc/smc combinations highly inconvenient, leaving the extension as an accurate indicator of whether it's headered. I consider this worth the minor inconvenience.
Except people don't know this and Lunar Magic will force a header anyway. Most newbies will just download a ROM and open it with Lunar Magic first, see it works and not question it further.
Not to mention any faulty files already flying around the internet as is.
Also, something else I forgot, hand in hand with the bank thing maybe to be able to use identifiers to split freespace sections. I remember this from VLDC9 where it was managing multiple patches by just having a huge incsrc file, thus also wasting some bytes on repeated freespace search. What I mean is something along these lines:
Code
;applied file incsrc "file 1.asm" incsrc "file 2.asm" ;file 1 org $xxxxxx autoclean JML hi1 freespace group(1) hi1: ;code ;file 2 org $xxxxxx autoclean JML hi2 freespace group(1) hi2: ;code
Asar would try to append the code of freesoace in file 2 after file 1.
Anime statistic on MyAnimeList:
400 animes completed ✓
6000 episodes completed ✓
100 Days completed ✓
... what even am I doing with my life?