first off, the major rejection reasons in this update also apply to the patch it was updating, which remains in the section. shouldn't the original be deleted too, until i fix these issues? (it might be a while i kind of hate it now)
Well, I'm not that moderator who missied sa-1 tag and didn't tested it for sa-1 compatibility. I don't think we're rejecting resources that are accepted already (unless it's related with remoderation), but we can remove sa-1 tag so nobody get confused.
this is kind of a weird thing. is there any other side effect of doing this that might be a problem? like, might asar try to expand the rom past 2MB if i were to use sa1rom? maybe it's fine bc freecode only uses the early banks? idk asar's five million nooks and crannies
I agree that it's weird that sfxrom
doesn't works, but sadly asar isn't my responsibility. You can put sa1rom or lorom header, and asar'll insert the patch, but those are the only way to insert it to super-fx rom. New versions of asar didn't get proper moderation, due to lack of tool mods that aren't responsible for asar update, though afaik
this issue was present in older versions of asar, meaning some moderators didn't bothered testing them with super-fx rom, which is a no-good and makes things confusing. But there's patch remoderation going on right now, so we can fix compatibility by doing weird lorom/sa1rom instead of sfxrom for now. It's not even necessary to support super-fx roms, because it's not as common as sa-1.
also, is there a timeline on fixing this? like, if it will be fixed soon, it might it be better to just wait until asar isn't busted and submit then instead of submitting now with a weird workaround
Or drop super-fx support altogether.
That's entirely on you to wether you want to suppor super-fx roms or not.