• 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] (FIRE RED) Changing the Hustle's accuracy decrease and ATK increase

Manekimoney

Banned
  • 169
    Posts
    7
    Years
    • Seen Jan 18, 2024
    (This is for a binary hack, not one that is 100% done using decomp)

    While I do enjoy the concept of Hustle, being a more "fair" version of Huge Power, as the Pokemon RNG goes, you actually miss about 50% percent of the time, instead of supposed 20%. This make it very frustrating to use.

    I tried to find the offset of Hustle, by using the decomp (changing just the ATK increase formula and accuracy decrease formula and comparing that to a clean Fire Red ROM), but changing the data messes up the entire structure of the hex, making it completely different and impossible to recognize, where the change actually is.

    Just for some info, this is the code for hustle ATK boost, located in the "pokemon.c" file:
    Code:
    if (attacker->ability == ABILITY_HUSTLE)
            attack = (150 * attack) / 100;

    And this is the one for hustle accuracy, located in the "battle_script_commands.c" file:
    Code:
    if (gBattleMons[gBattlerAttacker].ability == ABILITY_HUSTLE && IS_TYPE_PHYSICAL(type))
                calc = (calc * 80) / 100;

    So, does anybody have any idea, how I could get these 2 offsets? Is perhaps there a way to change these numbers in decomp in a way, that doesn't mess up the entire hex?

    This thread is more of a last resort more than anything. I don't fully expect for someone to just come up with the straight answer, but I would appreaciate any help.
     
    Look in the .map file that gets generated when you compile a clean rom. It contains the addresses of all non-static functions/variables.

    I guess that can help. Would you know a good way to recognize the data I would be looking for in that hex range?
     
    Back
    Top