Note that you wont find the hack in there if you didnt add any cheats to it.
Reverse that change I suggested to those header bytes for the two CRCs (basically undo the 8 byte changes I suggested to their previous values), and add this entry to the file "Project64.rdb" using a text editor. cht file, search for SM64s CRC number, copy the cheats, search for the hacks CRC number and paste it. Maybe GoodN64 did it I personally never bother with that.Īnyway, in that case, I might never know what really happened, but it's still an easy fix nonetheless.
How to make a rom hack say compatible in project 64 2 verification#
Your hex editor didn't do it automatically, so maybe Project64 overwrote them for whatever reason when noticing it was a modified ROM or some ROM verification utility you might have run. A Hack is a homebrew game which is based on the code of another game, with some modifications to add new features, levels etc. Some will be ROMs, others will be patches that you can then apply to roms. I will be using Pokémon Pearl for the base, and. This is a showcase of Nintendo 64 games that people have made over the years using various tools. Ive tried making GBA Pokémon ROM hacks, but Id end up breaking them pretty badly, so Im hoping I can get some people together to help me out with this. The only thing left unexplained to me, is how in the hell were the header bytes changed in the first place. Honestly not sure if ROM hacking is still big these days, but Ive decided to try and make a ROM hack.
Apparently Project64 checks what the header CRC summary should be instead of assuming the header to be correct, though this isn't as accurate as the MD5 database Mupen64 uses. You do this by launching your ROM on Project64MM, going into Options/Settings/ConfigNice, well that explains why just by changing some simple text data in VIRTUALCHESS it said "permanent loop" in Project64-didn't offset any addressing or anything.