Jump to content

Kaphotics

Helpful Member
  • Posts

    7216
  • Joined

  • Last visited

  • Days Won

    357

Everything posted by Kaphotics

  1. Kaphotics

    Bug report

    Already been reported & fixed: https://github.com/kwsch/PKHeX/commit/f3382bbd603652230508cc232379424080a0d9e3
  2. Trading to RBY removes the met location data; since the PKM on crystal had met location data, it implies it was never traded back to RBY (as the met data still exists).
  3. Probably something preventing it from truly being a Happiny encounter (ie something only Chansey can have).
  4. QR Injection still works for generation 6. You're generating QRs in the generation 7 format; load a generation 6 save file then generate the QR.
  5. Use the latest release; you still need an exploitable browser version (-22).
  6. a simple google search for "pkhex sun moon qr" will give you all the help you need.
  7. Delete the PKHeX.Core.dll and executable, then extract the latest posted release.
  8. Kaphotics

    Bug report

    It's a new addition; for gen6 it isn't behaving correctly like the gen7 variant. It's accidentally resetting other flags (unknown side effects), so you're probably best off reverting to the backup. The new version (posting maybe tomorrow) will have it fixed. Relevant fix: https://github.com/kwsch/PKHeX/commit/9864d84704a8e487c79c7b242cb6ef0c1f7d4755#diff-6477ac5c93a0823ea429ed4c67f8455dL434
  9. Do you have an mgdb folder? Not sure how you snuck invalid mystery gift data into the program (I'm not able to replicate what you're experiencing).
  10. fixed 1,4,5; would need to see pkms for 2 & 3 https://github.com/kwsch/PKHeX/commit/fb326500c1427774c34a346ec2b77ed49e1c7c97 thanks for the report
  11. that umbreon is definitely hacked, xd/c pkm need to have a valid pidiv
  12. Use the advanced search option with the same syntax as the batch editor? G7TID or whatever is a PK7 property.
  13. No, it's not a false illegal check result; Emerald has two pairs of Lati@s encounters. One has a fateful encounter, while the other does not. The one without is checked first, which fails because the PIDIV is invalid for that encounter. It then checks the other encounter (with fateful), which also fails the PIDIV check. Since there are no more possible static encounters, the program will continue on assuming that the final encounter was hacked, then checks the ancillary attributes. There is no correct encounter match, thus it keeps the last tested encounter to finish up with.
  14. > edited it to be shiny, must be legal No. Can't tell anything about the Raichu without seeing more information.
  15. No, and likely never will. May change if gen2 VC releases with korean versions.
  16. works fine on latest commits a new version is getting posted in the next ~2h anyway
  17. You're using a quite old version of the program. Download the latest version posted and your problem will likely go away.
  18. Needs a valid PID-IV combination. Capture encounter fails due to the lack of a pid match; the last possible valid encounter is an egg. Hold control when viewing the legality for a more complete report.
  19. Just wait for the next release. The testing builds aren't meant for general public use.
  20. Because a pkm should have a valid PID-IV correlation. The "reroll" button only affects the PID, not the PID and IVs. Feel free to code one and submit a pull request; until then, you can use RNG Reporter to find a PIDIV combo that suits your needs. Use the latest commits; I've already fixed the bad-gender / transfer etc issues.
×
×
  • Create New...