Victory Road Archive

You are viewing an archive of Victory Road.

Victory Road closed on January 8, 2018. Thank you for making us a part of your lives since 2006! Please read this thread for details if you missed it.

Other Pokémon Gaming → Very Random Question

Page 1 of 1

1. randoguy101 said on May 6, 2010, 05:46:46 PM (-07:00)

Volcarona
688 posts

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

2. Magmaster12 said on May 6, 2010, 05:54:06 PM (-07:00)

Rayquaza
4,872 posts

I don't think there is.

3. randoguy101 said on May 6, 2010, 05:58:12 PM (-07:00)

Volcarona
688 posts

If that's the case, which game is hacked the most? I kind of want this to be useful to a majority of people.

4. Arceus is Epic said on May 6, 2010, 06:08:33 PM (-07:00)

Zoroark
292 posts

the game thats hacked the most is most likely Chaos Black. Its a fan-made game and I play it on the VBA

5. randoguy101 said on May 6, 2010, 06:10:23 PM (-07:00)

Volcarona
688 posts

No, I mean, which Pokémon game do people use to hack the most?

6. blueumbreon said on May 6, 2010, 06:24:11 PM (-07:00)

Haxorus
470 posts

I think that they're Pokemon Emerald/FireRed.

7. Magmaster12 said on May 6, 2010, 06:42:46 PM (-07:00)

Rayquaza
4,872 posts

It's usually fire red.

8. FreezeWarp said on May 6, 2010, 06:45:08 PM (-07:00)

Kyurem
2,186 posts

FireRed is most stable, but Emerald has the benefits of the real time clock, among other things. Chaos Black is a piece of **** regardless.

As for your question, I'm not entire sure what you mean. Do you mean the source of the game or the binary code or...?

9. randoguy101 said on May 6, 2010, 06:49:34 PM (-07:00)

Volcarona
688 posts

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

10. randoguy101 said on May 16, 2010, 02:41:03 PM (-07:00)

Volcarona
688 posts

I've run into a problem. I can't find out where the game's header ends. Anyone happen to know?

11. TheRagingTyranitar said on May 16, 2010, 02:47:34 PM (-07:00)

Regigigas
808 posts

It's usually FireRed/LeafGreen or Emerald.

12. randoguy101 said on May 16, 2010, 03:00:45 PM (-07:00)

Volcarona
688 posts

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:
Embedded image

13. alternateshadow300 said on May 17, 2010, 04:24:10 PM (-07:00)

Haxorus
454 posts

Yeah, I don't know why, but Fire Red is the most popular victim for hacking... Mercury is being made from Ruby, cause I don't like hacking Fire Red for one.

14. randoguy101 said on May 17, 2010, 04:47:57 PM (-07:00)

Volcarona
688 posts

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. randoguy101 said on May 18, 2010, 01:22:24 PM (-07:00)

Volcarona
688 posts

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.

16. randoguy101 said on July 19, 2010, 01:36:55 PM (-07:00)

Volcarona
688 posts

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

17. .name//Technomancer said on July 20, 2010, 12:23:51 AM (-07:00)

Haxorus
486 posts

Quote:
Originally Posted by randoguy101 View Post
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
Take my advice as you will. Learn from it and stand by it, or simply discard it.

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. randoguy101 said on July 24, 2010, 07:39:33 PM (-07:00)

Volcarona
688 posts

Quote:
Originally Posted by .name//Technomancer View Post
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.
VBA has a built in disassembly tool as well as a memory viewer; one of the main reasons I started the project was because I knew of an easy way to read the game.
As far as actually editing the game... I think I'm fine using xvi32.
Quote:
Originally Posted by .name//Technomancer View Post
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.
While I can certainly agree that moving from one platform to another will drastically change the way things are done (and can be done), the basic formulas of the game are repeated throughout the series in the sense that catching a level 5 Pidgey with a Poke Ball in Gold/Silver is the same as catching it in Ruby/Sapphire.

Besides, I feel there isn't enough information out there about Gen I and II!
Quote:
Originally Posted by .name//Technomancer View Post
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.
This is a very good idea that I may utilize.

Quote:
Originally Posted by .name//Technomancer View Post
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
It'd be nice if I had a little headway in the project before I get serious about it, though a little help would be nice...

owait
Quote:
Originally Posted by .name//Technomancer View Post
I'd take a crack at it, but quite frankly, I love these games to much to justify going all Technomancer on them. :c
D:

Page 1 of 1

User List - Contact - Privacy Statement - Lycanroc.Net