Jump to content

Kaphotics

Helpful Member
  • Posts

    7270
  • Joined

  • Last visited

  • Days Won

    362

Everything posted by Kaphotics

  1. Were these obtained on the latest patch of the game, or the unpatched base game? Not sure what may be causing this error (only for French??).
  2. Should have the nickname flag set, and the nickname different from the species name based on whatever the nickname should be for your language.
  3. Please familiarize yourself with the features of the batch editor. Right below the text entry region, the program will display the property type AND the property value of the currently loaded PKM in the PKM Editor. If you want to know specific values, you can edit them onto the PKM then check the raw integer in the batch editor and build an instruction based on its value.
  4. Kaphotics

    error message

    It means exactly what it says; some other program/hardware has locked the file for reading. Copy it to your desktop or something.
  5. They're not missing. Assuming you've not opened any save file, the default save data context is Scarlet / Violet. Are Milcery and Alcremie obtainable in that game? No, so they're filtered out of the list. If you want to edit data for a specific game, then change the program settings / load an appropriate save file.
  6. Refer to the pinned thread at the top of this sub forum. https://projectpokemon.org/home/forums/topic/56296-read-home-tracker-value/
  7. That's not a save file; whatever you extracted was incorrect.
  8. The only difference is that one is encrypted, and the other one is decrypted (not encrypted). Encrypted data must be decrypted before checking specific properties of the Pokemon (like Species), but the game stores data in the encrypted form whenever it is not in use. Decrypted data is human readable, while encrypted data is the state the game expects it to be in.
  9. Not a feature within base PKHeX. Are you thinking of a plugin?
  10. Nope.
  11. Already been fixed on the development build, you need to wait for the next release.
  12. It can learn mega drain if you transfer it to Gen2, which mutates the field when it becomes held item. It does not revert when it is traded back. If you want to disregard Gen2 entirely, there's a setting for that. The move suggestion API doesn't care about catch rate/held item snafus. Please only report issues with your own unmodified data in this thread, per the first post.
  13. Did you read the change log?
  14. Hold control and see the sources of moves. Since it has Mega Drain (only accessible from Gen2), it must have been traded to Gen2. However, it has a catch rate of 45, which is the held item value when it exists in Gen2. When you trade it to Gen2, a catch rate of '45' is translated to `83` for Bitter Berry; can't retain a value of `45` going back and forth. Therefore, the error message. 45 is not a valid Gen2 item. Remove the move, or change the catch rate/held item value.
  15. Fixed on latest commit; for now, just clear a space in your Key Items pouch because it is full.
  16. 220831 - you're nearly a year out of date. Do you have the same issue on the latest release?
  17. revised: https://github.com/kwsch/PKHeX/commit/6964d48adb652b4a13826a61d9ec00fe39388f7e
  18. The date ranges for these gifts were added after the latest release; they work fine on the bleeding edge development build.
  19. Unable to replicate. If you're referring to the Hisuian form, then please read PKHeX's release notes.
  20. PKHeX stores backups of all save files, assuming you've accepted that setting. Open the PKM Database via the Tools dropdown; literally everything in your pkmdb and save file backups will be accessible from that.
  21. PKHeX does not support ROM Hacks. If it happens to work, cool, but it's never something that is intended. If someone managed to get it working, go ask them instead. This forum isn't for getting help with this kind of thing.
  22. This isn't an issue with PKHeX. If it shows as legal in PKHeX, and a bot won't allow it to be traded, then the bot is either out of date or has added extra restrictions unrelated to PKHeX.
  23. Use the encounter database. You haven't filled out everything, hence the messages.
  24. Can't see your images. Please try again on the latest release, probably has been fixed already.
×
×
  • Create New...