You are not logged in.
Does anybody know where is the rom address for both sleeping snorlax encounters and the ghost marowak encounter on english red/blue?
I searched the rom for hex values 1E84, 841E, 1E91 and 911E but none of the results changed the snorlax or marowak encounters.
Out of curiosity, why are you still trying to edit English Red/Blue using a hex editor? Nobody does that anymore. It is really simple to edit those (and everything else) by editing the source code and recompiling.
Hey! Thanks for the quick response :D
Well, in fact i'm new to hacking pokemon games, but i've done some work on non pokemon hacks in the past... all of them with a hex editor.
I'm afraid i look at the source code and i have no idea what to do, or how to work with it, with a hex editor i (sorta) know at least what i'm doing.
Sorry for the noobishness D:
Source code is infinitely easier.
Data is much more readable. When editing a Pokemon encounter, would you rather try to remember a Pokemon's hex ID, or just type the word "MAROWAK"? Personally, I'd rather go with the plain English. Plus, when it comes to editing actual scripts, you're going to need to use z80 assembly. You technically can edit that in a hex editor, but it is annoying as hell. You will find almost no documentation on what the opcodes translate to in hex, but you can find all the documentation you want on how the language itself works. Plus, everything uses label names, so you don't have to worry about repointing anything or knowing a RAM or ROM address. There are also macros to simplify some common and/or awkward things in the code. It's extremely easy to pick up using the source.
I found what i'm looking for in the source code:
https://github.com/pret/pokered/blob/ma … 12.asm#L32
https://github.com/pret/pokered/blob/ma … 12.asm#L34
https://github.com/pret/pokered/blob/ma … 16.asm#L32
https://github.com/pret/pokered/blob/ma … 16.asm#L34
https://github.com/pret/pokered/blob/ma … r6.asm#L35
https://github.com/pret/pokered/blob/ma … r6.asm#L37
But i still don't know how to 'translate' that info into the rom or into a patch
Sorry for the annoyance :|
> Follow the instructions in INSTALL.md to setup a copy of it on your computer
> Edit those files with a text editor (not notepad, since it will mess up line endings. Use something like Notepad++ or Sublime or another one that is free and designed for coders, to avoid any issues)
> Save your changes
> Open the terminal
> type "cd pokered"
> type "make"
You now have a rom with your changes included. Actually, you have 2 roms. A red and a blue version, both containing your changes. They will be in the project's main folder called "pokered.gbc" and "pokeblue.gbc"
This is AMAZING! I seriously thought editing things like that was gonna be a lot more complicated than that.
How did you do it? I had no idea you could edit all those things in such a simple language. You guys really did making pokemon hacks a lot easier.
Kudos to all of you
We did it by documenting every piece of the rom, a few bytes at a time, over several years.