• Just a reminder that providing specifics on, sharing links to, or naming websites where ROMs can be accessed is against the rules. If your post has any of this information it will be removed.
  • Ever thought it'd be cool to have your art, writing, or challenge runs featured on PokéCommunity? Click here for info - we'd love to spotlight your work!
  • Which Pokémon Masters protagonist do you like most? Let us know by casting a vote in our Masters favorite protagonist poll here!
  • Red, Hilda, Paxton, or Kellyn - which Pokémon protagonist is your favorite? Let us know by voting in our poll!
  • 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.

[ASM & Hex] How to hex edit hardcoded base stats for Gen 3 Pokémon?

  • 3
    Posts
    4
    Years
    • Seen Sep 26, 2020
    I had an idea for a challenge where it's Pokémon Fire Red but every Pokémon had both Shedinja's signature ability, Wonder Guard. But every Pokémon also had Shedinja's single hit point caveat. I tried finding information on this forum on how to hex edit those stats as they're hardcoded for Shedinja to only have a single hit point even if it had its base HP increased and I'm certain it can be done, but I have no idea how to find the values for all the other Pokémon so I could change them to all have only 1 HP. If anyone can help me to find the values so I can make this a reality, I would be most grateful. Thanks for reading.
     
    Stats and abilities are easy. There are a bunch of programs that can even do them.

    Now, I could be wrong, but unfortunately I think Shedinja's HP isn't as simple as just having a base stat of 1.

    There's an extra routine for him, I reckon.
     
    Last edited:
    Tacobell is right, you need to locate this code and make it always set newMaxHP = 1 for all Pokémon. Finding that code is probably best done by compiling pokefirered, because then the pokefirered.map file will tell you the offset of that function in your ROM.

    EDIT: CFRU would also be an option if it patches that function, because then you could change the C code directly.
     
    Back
    Top