Jump to content

Kaphotics

Helpful Member
  • Posts

    7270
  • Joined

  • Last visited

  • Days Won

    362

Everything posted by Kaphotics

  1. It's fixed on the latest development build. If your auto-loaded save file had a bad hack (invalid tera type) it would have the above error.
  2. Have you captured Terapagos yet?
  3. Ah, a two-part question/report Fixed the mail ID not being cleared/set for writing party data: https://github.com/kwsch/PKHeX/commit/59e409bbd7de3fc4dbe6abb87cbaf8e65c4037c6 Will be in the next release (soon-ish)
  4. That's what it looks like when you are editing a non-Japanese save file. The 0x53 glyph is displayed as "Pk" in International games (corresponding to your image), and in Japanese it's ウ. There are only 256 possible character glyphs; they mostly match between JP/INT, but there are differences depending on the cartridge language version that displays them.
  5. Again, they were only released for Japanese region (and thus, only Japanese OT languages).
  6. PKHeX cannot know about encounters that are introduced via future DLC content, such as mass outbreaks that are from the download news. The program's latest commits should be able to recognize it, but there won't be a new stable release prior to Indigo Disk DLC's release.
  7. The development build is for testing purposes only, not for general consumption. Use an earlier commit. DLC is coming in less than 4 days, we're already preparing things.
  8. Check the SAV tab, where you can export the entire chunk of PC data. Then just drop it into the other save file.
  9. Probably a bad dump. You can try another save editor to see if it's PKHeX not reading it, but keep in mind your screenshot shows an out of date version of the program.
  10. Reusing a random 1:4billion odds seed across multiple encounters? Usually a sign that they were not encountered without some bit of cheating, hence the message. Additionally, the bulk verification requires discretion; someone can trade their copy of a shared raid, but this is not the case. Please only report legitimate issues; reread the first post in this thread.
  11. Both attachments are junk. Open them in a hex editor; contents are not a save file.
  12. Try changing the DisableScalingDpi display setting in the program options and rebooting the program.
  13. Use the encounter database. Latios is not Method H-2.
  14. Have you viewed the entry in game?
  15. PKHeX's word filter is a superset of all word filters; it is not per-generation/game. Only one word filter, used by all. It is used for prior games to indicate if there will be issues if they're transferred forward. The OT may be wiped by the game/console, or blocked from upload into HOME; so it's better to let you know ahead of time.
  16. PKHeX does not intend to support modified games. I have no idea what changes every other tool or patch may cause, but the modifications to your game resulted in things that are not possible to obtain on legitimate copies of the game. PKHeX is working as intended.
  17. Double check you're not playing on a modified copy of the game (ROM hack). A Pokémon cannot be marked as having its second ability if there is no second ability to be had.
  18. CP is stored at offset 0xFE within the PB7 structure; your Grimer has 0xFE55 (65109) which is an invalid value -- it should be 880. Note that CP caps out at 10,000. Opening your PB7 in a hex editor, it appears the Party data has been corrupted / is invalid. The CP/Stat calculation thread you linked relates to floating point calculations; can result in different decimal values if not calculated with the exact same multiplication factors. Yours is a different "issue" that I don't believe is caused by PKHeX. Did you happen to do anything else within PKHeX or another save editor program (like PKSM) to corrupt the party data? Sorting boxes perhaps? If you check your stats in-game, they'll likely be garbage, or the game will auto-heal them and they'll be valid the next time you export the updated save file.
  19. Can't tell unless you: 1. show the pokemon 2. show the release of PKHeX you're using 3. indicate what operating system you're using (windows vs other)
  20. Working as intended. Alakazam is a trade evolution, and the file you uploaded has never been traded away from the OT.
  21. Do what the message box says. You need to install the runtime for the program to work.
  22. Correct; fixed on latest commit https://github.com/kwsch/PKHeX/commit/2e736a1d4cbb493dc708a736af7fc140de4b90b5
  23. PKHeX does not support ROM hacks.
  24. PKHeX was last updated over a month ago; PKHeX doesn't know about encounters that are made available after the last release. Wait until the program is updated.
  25. Options ~> About PKHeX ~> Shortcuts
×
×
  • Create New...