• 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.
  • Our friends from the Johto Times are hosting a favorite Pokémon poll - and we'd love for you to participate! Click here for information on how to vote for your favorites!
  • Cyndy, May, Hero (Conquest), or Wes - 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.

Safari Zone Error

  • 11
    Posts
    8
    Years
    I am using the newest version of Essentials, and other than modifying what Pokémon show up in the Safari Zone, I haven't really touched that particular map.. I only seem to get the error in Single Battles, where-as Double Battles work just fine...

    Spoiler:
     
    Last edited by a moderator:
    Hi, I am receiving an almost exact version of this error with slight differences... I am using the newest version of Essentials, and other than modifying what Pokémon show up in the Safari Zone, I haven't really touched that particular map.. I only seem to get the error in Single Battles, where-as Double Battles work just fine...

    Spoiler:

    add this line
    Code:
      def displayGender; @pokemon.gender; end
    after line 10 of PokeBattle_SafariZone.

    Normally, Safari Zone crashes (as I've experienced them) are caused when you change the GUI of battles to take advantage of functions that you add to PokeBattle_Battler, but forget to add to PokeBattle_SafariZone. In this case, Maruno added the displayGender function, designed to show the gender of a Pokemon unless the Pokemon is under an Illusion (in which case the function throws up the gender of the Pokemon the Illusion is based on), but didn't add it to the FakeBattler class as well.

    That being said, I have a copy of 16.0, and he may have fixed this issue between then and 16.2, in which case his advice of "latest update" would be valid advice.
     
    Back
    Top