• Our software update is now concluded. You will need to reset your password to log in. In order to do this, you will have to click "Log in" in the top right corner and then "Forgot your password?".
  • Welcome to PokéCommunity! Register now and join one of the best fan communities on the 'net to talk Pokémon and more! We are not affiliated with The Pokémon Company or Nintendo.

[Other] Trainer Editing in Yellow?

102
Posts
12
Years
    • Seen May 14, 2024
    As I understand it there isn't a working program to edit the trainers pokemon in Yellow but there's a way to do it via hex, could someone please point me to a tutorial should one exist.

    Thanks in advance.
     

    miksy91

    Dark Energy is back in action! ;)
    1,480
    Posts
    15
    Years
  • I'm not sure how complete pokeyellow disassembly is, but in case you're interested in making lots of changes to yellow, you should hack the disassembly instead of a rom file. The trainer parties are for example documented in the following asm file (https://github.com/pret/pokeyellow/blob/master/data/trainer_parties.asm) and it's very simple to edit the pokemon that any in-game trainer has by re-writing stuff there.

    That file corresponds to the contents of rom file so that you can find the exact same data in pokemon yellow rom as well, but in byte code of course. Giegue's hacking guide (https://www.angelfire.com/oh4/giegue/gmg2hpgr2c.txt) explains the byte codes of each pokemon and for example Rattata is A5 and Ekans is 6C, so the pokemon party of the first Youngster in that list is "0B A5 6C 00" (where 0B is just hex byte corresponding decimal value 11). Next you can find where the data of that youngster is located in the rom by simply searching for those 4 bytes in that order (where search most likely won't give any more than 1 result).

    Others in Skeetendo Inc. can help you out with disassembly in case you're interested in using it for hacking yellow :) It's way easier as if you for example wanted to make that youngster have 3 pokemon instead of 2, you would have to repoint (= move) the data of all youngsters elsewhere to make room for new bytes for that specific trainer. This kind of an issue won't practically come up with disassembly because you can make a rom file out of contents of disassembly by compiling it (and thus all the data following data of Youngsters is automatically moved ahead and you won't have to do manual repointing like this).
     
    Back
    Top