#1
|
||||
|
||||
Very Random Question
Does a disassembly of any Pokémon game exist? Like, a file containing all the game's code before it's assembled? Because if there isn't, I'll try to make one.
EDIT: Basic documentation can be found here Last edited by randoguy101; May 6, 2010 at 07:23:50 PM. |
#9
|
||||
|
||||
The source code for the game, and I'll try and make it easily patchable as well, but that'll be difficult.
Basically, like SMW's all.log |
#12
|
||||
|
||||
Plz read entire thread before posting kthx
Anyway, I should probably explain what a header is before posting about it. A header is the part of a ROM that is ignored by the assembler, but read by the console. It contains data such as what version the game is, the name of the game, the area released in, etc. My ROM seems to have a header, as I found this: |
#14
|
||||
|
||||
Updated the RAM and Graphics Documentation a bit.
http://randomvids.net/romhacks/pokem...umentation.txt And I really need help with the header problem before I can start the project. |
#15
|
||||
|
||||
I'M ALMOST COMPLETELY SURE-ISH MAYBE THAT THE HEADER ENDS AT 0800:0800 PLEASE TELL ME IF I'M WRONG
ALSO, I'M BEGINNING TO ACTUALLY DISASSEMBLE STUFF </CAPS> EDIT: Hahaha, wow, ARM7 is pretty confusing with it's hexadecimals, but the opcodes are quite similar to the 65816. I'm gonna list down all of them and try to find a pattern in the hex. Last edited by randoguy101; May 18, 2010 at 07:32:56 PM. |
#16
|
||||
|
||||
2 months, and I still haven't figured it out D:
I suppose it would be smarter to start with the GB/C games, as those are generally simpler in code and set basics for the rest of the series, so I'll be able to recognize things like catch rate when I begin to disassemble the GBA (and possibly DS) games. Also the GB/C's proccessor isn't as confusing. tl;dr I'll start the project with Pokemon Yellow, then move up to Crystal, then Emerald, then maybe Platinum. e: incase the above statement didn't make it clear, I'm doing the third game of each gen because those work better than the first two Last edited by randoguy101; July 19, 2010 at 12:37:46 PM. |
#17
|
||||
|
||||
Quote:
First of all, how recent is your Hex editor? Most older Hex editors [Like mine xD] aren't made to be patched; most Hex developers typically make them once, and begin another with more options, better programming dissection, ect... If you're fairly good with your Hex editor, I wouldn't recommend kicking up to a new program, keep with what you know. As for moving from one game to another, that isn't necessarily the case. I wouldn't recommend moving from GB/C, then to GBA, and forth. While yes, the layout and embedding is similar, the overall coding isn't any more difficult nor diverse. It'll kinda be like playing Grand Theft Auto III to warm up for a round of Halo. Sure, they're both recent-gen games, but that doesn't make them any more similar. If I were you, I'd simply stick to breaking Emerald open, and reconfigure what is able. The best way to find proper code for any individual value is changing it's color, in my opinion. I like adjusting the contract, hue, or transparency to find physical code, and breaking apart code to find un-accessibles. Think of it this way though: if you are in fact the first person with this specific goal in mind, you could always post it in a few ROM forums, and coin the disassembled coding of Pokemon. :3 I'd take a crack at it, but quite frankly, I love these games to much to justify going all Technomancer on them. :c |
#18
|
||||
|
||||
Quote:
As far as actually editing the game... I think I'm fine using xvi32. Quote:
Besides, I feel there isn't enough information out there about Gen I and II! Quote:
Quote:
owait D: |