• 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!
  • 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 Battles freeze (Emerald)

  • 19
    Posts
    9
    Years
    • Seen May 22, 2018
    Hi everyone and sorry for my noobness.

    As the title says, some Trainer Battles in my hacked Emerald ROM make the game freeze. So far I edited every Trainer in Routes 102-104, 116, Rustboro City and Rusturf Tunnel including rematches and tested it until the Battle against my Rival in Rustboro. This issue occurs with three Trainers, always against a certain Pokémon and just after some turns (around four). If said Pokémon are defeated early, the game will proceed normally, though, so the bugged Trainers may be more. I tried to fix the Trainers by deleting the bugged Pokémon and re-creating it, but while it seemed to work on the first one, the second kept making my game freeze at every attempt.

    Here's a list of the actions I take for editing each Trainer. It's pretty basic, but I guess the eye of someone who's more expert than me will notice what I do wrong.
    Spoiler:
    Come to think about it, I changed the species of every Pokémon those three Trainers own. It's the only common trait I understood so far, I don't know if that means anything.

    That's all I can say, I tried to be the most detailed I could (maybe even too much on the list, I felt totally dumb all the time by writing like that).
     
    I don't really know how Hopeless Trainer Editor works because I don't use it, but if you increase the number of PKMN in a trainer's team, you're supposed to repoint it because that trainer's team data is bigger now than what it was previously. If you didn't repoint, then chances are you overwrote the next trainer's teams, and is probably why you're seeing this bug.

    So yeah. What I am asking is if you repointed to an empty offset after increasing the number of PKMN a trainer has?
     
    Yes, as I want to save, the Editor asks for a new offset which size depends on how many Pokémon the edited Trainer has (48 bytes for three Pokémon, 64 for 4, 80 for 5 and 96 for 6 if I remember it well), so I look for it with Free Space Finder, always beyond 0x800000 as of default, and copy-paste it on Hopeless Trainer Editor. It's the part of the process of which I'm most unsure, because I never felt that good with Free Space Finder.
     
    Back
    Top