RomRaider

Hello all!

As I've defined over 2100 maps for my ROM, I decided I would share some tips and tricks on ROM disassembly inside of wols. Throughout this entire process, wols has made it a breeze to define my ROM, even though I have no prior experience or knowledge related to coding of any kind. The main area wols struggles in is with single values, some tables, alongside verifying the maps. That's where Ghidra and/or IDA Pro come in handy. But wols can give you a good idea of a potential map, which you can them compare/analyze in Ghidra/IDA to verify whether it's the map you think it is or not.

As RomRaider doesn't have a friendly history with things related to intellectual property, I have made this post on the wiki found here -> https://nissanecu.miraheze.org/wiki/Fir ... isassembly

It's a bit of a crude guide, but it's better than nothing!

Impressive amount of work went in there, for sure. Thanks for publishing this, I think it's worth a sticky.

Thank you! I felt like people just don't really know what do to once they're inside of wols for the first time. Just a bunch of random numbers all over the place in weird formats. I had to learn how to set it up properly on my own as well. My friend who has used it for a few months now didn't even know about the color scaling and removing the leading zeros! He used to exclusively use 2D and 3D mode due to the fact that 1D mode just wasn't useful before using those. So I thought that if one person was struggling, then surely others either are struggling, or will struggle in the future.

Plus introducing others to a good method of locating maps will help them out a substantial amount. I mean, it worked to define maps for a 2010 Juke by cross referencing a 2006 350z So I'm guessing that most Nissan ROMs will follow a similar pattern with how their maps are laid out. Because all the Nissan ROMs I've seen (even JDM Nismo Stagea's) follow that order. I'm sure it could start to vary once you get into 1D and 2D stuff, but that's not confirmed yet.