Yes, i suspected that. I believe bps does not behave that way, so i expected it to replace ips in more games by now.
I'm sure anybody doing hacks and translations has access to the right tools. Even if they didn't know about a program like hashmyfiles, you can easily see the CRC value of the rom in winrar. If somebody is actually grabbing these values from some place online it's probably because it's a site with a good repuatation and they just didn't double check that the info was right. Hell... Even after all the work I did documenting issues with NES and FDS roms that I've posted here I would never say my info is 100%. It would require me to re-patch every single game and re-verify, which is something I would NEVER do.
Besides that, a accurate database of these things would be useful, for knowing when to upgrade the translation automatically instead of constantly checking the site. That would be helpful for *anyone*. I'd admittedly prefer if the 'softpatching' usecase was catered for too, but i'm aware as you can tell from the bitching about the 'preprocessing steps' on my posts that is not so simple to do consistently if you insist on a consistent collection of base roms (like i do, all no-intro), because many translations need to be modified with the 'hardpatch and create a new softpatch from new base to hardpatch' trick, or the tricks below.
On a subject change, more of that consistency bitching, another annoying thing is snes rom headers being needed or not for translations. When something like ipsbehead exists
Yet another annoying thing that is rather specialized is n64 patches. n64 have 3 (!) different byte order organizations on their 'base' roms, and it's not unusual for a ips or bps file to have to be recreated on the 'target base rom' for a softpatch to decrease from the size of the rom to 150kb.
The process is like this:
1. find out patch base rom is not the no-intro byte order.
3. copy n64 no-intro rom, use tool64 to change no-intro rom to byte order the patch needs, verify crc.
4. hardpatch byte order changed rom
5. use tool64 to change byte order changed rom to no-intro rom byte order
6. create a bps or ips patch from original no-intro to hardpatched rom, delete extras.
August 21, 2017, 06:50:04 pm - (Auto Merged - Double Posts are not allowed before 7 days.)
BTW, i think the lagrange point page is saying that the 'base rom' doesn't matter in this case (or doesn't matter as long as it is a header variant of that one 'base rom'.
This is very strange thing to say because ips doesn't make a distinction between the header and the rest of the rom and will happily overwrite the header if i understand it correctly.
Maybe the original was supposed to be bps and you supposed to ignore the crc error if it happened?
Regardless, i just 'tried' (not exhaustedly) the lagrange point translation on the no-intro rom crcs:
9ac10a68 Lagrange Point (Japan).ips
ead4dedc Lagrange Point (Japan).nes
and didn't see a problem in the intro, though that doesn't mean anything of course (especially with the mentions of 'SRAM disabled', maybe saves don't work?)
Another possibility to 'it was supposed to be bps' is that something similar to ipsbehead (similar because this is a nes rom not snes) was applied to the ips and that text simply doesn't matter because the ips no longer affects the header and it is ready to run on a no-header rom.
August 21, 2017, 11:47:00 pm - (Auto Merged - Double Posts are not allowed before 7 days.)
BTW, i've been applying nes translations and found that sometimes, when the game has both .bps patch and ips patch translations, since bps is 'stricter' and will not apply if the base rom doesn't have the right checksum, you sometimes want to use ips even if it's 'wrong'
is one such case. The no-intro rom changed (probably the header). BPS fails, but the IPS will happily overwrite (or maybe just ignore) the header and apply the translation.
August 22, 2017, 02:01:33 am - (Auto Merged - Double Posts are not allowed before 7 days.)
There is also another strange case i've found:
Juvei Quest (Japan) translation here:http://www.romhacking.net/translations/1826/
applies not to the first no-intro version but not to the last (Rev 1). A bit off-putting. Another bps + ips patch, haven't tried the ips on the Rev 1, because the page says to use the first.
August 22, 2017, 03:37:04 am - (Auto Merged - Double Posts are not allowed before 7 days.)
Another. This patch:http://www.romhacking.net/translations/773/
Says on the main page it uses the no-intro rom (with crc32: d994d5ff ) but this corrupts the game on movement and the readme says it uses the rom with crc32: b661b602 (whatever that is).
August 22, 2017, 05:06:37 am - (Auto Merged - Double Posts are not allowed before 7 days.)
The crc checksums on that page look familiar...
August 22, 2017, 10:35:12 am - (Auto Merged - Double Posts are not allowed before 7 days.)
The quest of Ki patch doesn't apply to no intro. It's claimed this is because no-intro has wrong headers, but the user needs to modify the patch anyway.
August 22, 2017, 11:34:53 am - (Auto Merged - Double Posts are not allowed before 7 days.)
Another case of the same thing (no-intro rom having wrong header). Check the translation description on the page, i verified the 6th byte has 40 instead of 41 on the no-intro rom:http://www.romhacking.net/translations/234/
But since this is a ips patch not bps it 'applies'. Just wrongly. It's quite easy to regenerate the patches to apply to the normal no intro with the 'create a new patch' trick if you're aware of this problem.