Jump to content

Kaphotics

Helpful Member
  • Posts

    7028
  • Joined

  • Last visited

  • Days Won

    336

Everything posted by Kaphotics

  1. Nothing in the save file. Save in-game correctly.
  2. Chansey is not valid, probably was hosted by someone with cheats active. Crystal cavern encounters are only allowed 1 shiny reroll. The RNG correlation of tera raids does not match the shared data.
  3. Just ignore those egg templates, they're not legal because the evolution chain for them does not exist to obtain the base species.
  4. Kaphotics

    Please Help,

    There is currently no official route for transferring into S/V from external games. Incompatible transfers must be enabled via PKHeX settings.
  5. Added in latest commit. https://github.com/kwsch/PKHeX/commit/0c0651f7192cda4f344507b6ca19c3d64c03ff63
  6. It's not currently obtainable, nothing else can learn it to mirror share. Remove the move entirely.
  7. The PIDIV in question has more than just PID and IVs correlating. It also has OT Gender, SID, and Version.
  8. Definitely not PKHeX's fault. Be sure you are setting the PKM back to the savedata prior to exporting your save, and be sure you're importing your edited save file to the console correctly. Make changes to $$$/moves or something else to make sure your changed files are imported as you expect.
  9. You're trying to view event data from other games (not S/V) when there isn't a way to convert the data -- HOME has not updated, so what should PKHeX do?
  10. Where are you seeing this? I see Tackle->Growl: https://www.serebii.net/pokemon_box/egg.shtml I've updated PKHeX to swap the two move orders for both games. https://github.com/kwsch/PKHeX/commit/f10c914eace8682165915ca902f0a20640a3c478
  11. Use any calculator that can do programmatic operations like modulo. Take PKHeX PID, convert to decimal, use % 100. Rare forms need the result to be 0. If you want the rare form, then just subtract the result from the decimal PID, convert to hex, done. Pick a new EC that has the result you want.
  12. PKHeX has an encounter database. Encounters require specific values to be set in order to be valid. Use the encounter database instead of trying to make things from scratch.
  13. Not able to replicate. They're in the encounter database with fixed OT names and PID types.
  14. The program initially calculated the "correct" form based on EC%25, when the real calc is EC%100. If the result is 0, it evolves into the rare form.
  15. It's because it imports in whatever order the operating system gives it, which is usually alphabetically. 1xxx comes before 9.
  16. 1. Default annihilate is obviously illegal 2. Marks and crossover location encounters are already known and mentioned in the change log. More time is needed to correctly recognize them.
  17. Thanks, fixed on latest commits. https://github.com/kwsch/PKHeX/commit/5d8bfb6d76c06ddce80f8f44d93b7bcb207938d5
  18. Fixed on latest commits right before you posted - https://github.com/kwsch/PKHeX/commit/6002611c809c6e43f2b7465e7283218a25e60c7e
  19. Use the encounter database. The box legendaries are constrained to specific IVs, nature, and sizes.
  20. There is no official transfer mechanism for pk8->pk9, because HOME does not support Scarlet & Violet. How is PKHeX supposed to transfer the data? It's not going to fudge it giving you a false sense of it working correctly. Still, PKHeX has a setting to enable incompatible transfers (like backwards gen 7->3, or 2->3). In the program settings. Your mileage may vary.
  21. Has been fixed in commits since last release; will be fine in the next stable release.
  22. Wasn't actually implemented (I misremembered); should be in the next release in the next day or so.
  23. It is not being thoroughly checked at the moment. The game stores the level it was received in the current game, and updates each time it is traded to whatever the current level is. If it has not been traded, it should match the met level. If it is a trade evolution with a prior evolution needing level up, then it must not be the same as the met level. Future updates may check for these restrictions once the evolution verification logic is rewritten.
×
×
  • Create New...