Jump to content

Kaphotics

Helpful Member
  • Posts

    7034
  • Joined

  • Last visited

  • Days Won

    336

Everything posted by Kaphotics

  1. The program already indicates in the legality analysis which form it will evolve to, just like it does for Wurmple. There are batch editor commands to set a specific EC modulo, but keep in mind that the user should still understand how the entity data determines the result.
  2. This is not something a save editor can do. Hacked raids/rewards gets your console banned, see the hacked raids from SW/SH.
  3. Again, evolutions for that species are predetermined, thus there's nothing you can do in-game to influence it for one you already have. The value that predetermines it is the Encryption Constant. Similar situation as Toxtricity, that has nature determine how it evolves; Maushold and Dudunsparce evolve based on the EC%100==0 check.
  4. Working as intended. Evolutions for that species are predetermined, so if it cannot naturally evolve into its current state, it must have originated as its current state, not the pre evolution.
  5. You cannot nickname anything with fateful encounter.
  6. Nothing in the save file. Save in-game correctly.
  7. 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.
  8. Just ignore those egg templates, they're not legal because the evolution chain for them does not exist to obtain the base species.
  9. 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.
  10. Added in latest commit. https://github.com/kwsch/PKHeX/commit/0c0651f7192cda4f344507b6ca19c3d64c03ff63
  11. It's not currently obtainable, nothing else can learn it to mirror share. Remove the move entirely.
  12. The PIDIV in question has more than just PID and IVs correlating. It also has OT Gender, SID, and Version.
  13. 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.
  14. 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?
  15. 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
  16. 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.
  17. 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.
  18. Not able to replicate. They're in the encounter database with fixed OT names and PID types.
  19. 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.
  20. It's because it imports in whatever order the operating system gives it, which is usually alphabetically. 1xxx comes before 9.
  21. 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.
  22. Thanks, fixed on latest commits. https://github.com/kwsch/PKHeX/commit/5d8bfb6d76c06ddce80f8f44d93b7bcb207938d5
×
×
  • Create New...