Jump to content

Kaphotics

Helpful Member
  • Posts

    7841
  • Joined

  • Last visited

  • Days Won

    451

Everything posted by Kaphotics

  1. Working as intended. Anything transferred from the previous generation cannot be currently-handled by the previous-generation-OT, as we're in a future generation where the OT does not exist. >when in fact, wouldn't the issue exist if the save had the same details as the Zeraora OT? 1:4billion chance to get the same ID, and picked the same exact OT for the save file it's currently on. Statistically never going to happen, hence illegal. The green highlight indicates who is currently handling it. If the green highlight is set for the OT and it cannot be legally set to the OT, then it is flagged as illegal.
  2. Almost as if that green box is indicating who you've set the current handler to be.
  3. Data doesn't magically disappear. Be sure you're exporting your save file, and opening the newest save file instead of an old file.
  4. I recommend checking how the game normally handles eyecatch trainers. It's probably a standard script.
  5. Usually it's trainer index * 3 or something. All trainer messages are stored sequentially in the text file. How to stop rebattling: have the game set an event flag, and put that event flag number as the overworld NPC's event flag to deactivate it (not hide it) -- refer to other overworld trainers that do eyecatch battles.
  6. You have to search for something. It's not going to give you a list of 100,000 things to scroll through.
  7. Maybe the Yellow Triangle is a hint that it's unusable in-game...
  8. What does it say for the move description in-game?
  9. Change the origin game to the game that it originates from. Then enter in the TID/SID you want the game to show. The Trainer ID is stored as a 32 bit value. The game does a bitshift for gen6 game-origin and prior. The game does a modulo for gen7 game-origin and up. The value-portion that is discarded is the Secret ID.
  10. ty fixed in latest commits https://github.com/kwsch/PKHeX/commit/8650b5ceb2ecb6504882a262f452808a1dabadb9 https://github.com/kwsch/PKHeX/commit/4decaa73f7f659cf01411b5f299e9fa982da21d7
  11. why bother reporting issues if you're using a program that is 6 months out of date?
  12. Gee, if only there was a Nintendo Switch Pokemon ROM Editor that added drop table editing a few days ago.
  13. ty fixed in latest commit https://github.com/kwsch/PKHeX/commit/5fc15dc9c8619a4348511a222da410330a8aa945
  14. https://github.com/kwsch/PKHeX/commit/913d2773bffe0b665eb6f9e65d99d95515da7593
  15. Is it that hard to read the stickied threads?
  16. PKHeX rejecting your file should be a hint that you are either: Loading the wrong file, or Incorrectly exported your save file.
  17. How far along have you played the game? Get your starter, save and close the emulator.
  18. ty fixed in latest commit https://github.com/kwsch/PKHeX/commit/a55b4da05c35150c9bda328511f954b80e889804
  19. It's because Darumaka-1's altform (required 1) doesn't match the current PKM's altform (actual 2) PKHeX's legality check checks for matching forms (since in prior games, pokemon didn't change their altform) edit: now fixed, thanks for reporting (I had another MrMime case passed along by someone else): https://github.com/kwsch/PKHeX/commit/913d2773bffe0b665eb6f9e65d99d95515da7593
  20. Kaphotics

    PKHeX error

    Read the stickied threads. https://projectpokemon.org/home/forums/topic/40006-issues-with-pkhex-read-this-first-swsh-update/ https://projectpokemon.org/home/forums/topic/38168-frequently-asked-questions/
  21. Try googling your error messages.
  22. In the "Solution Explorer" pane on the right, the individual projects failed to load and are listed as "incompatible". Ensure you have .NET Core SDK stuff installed. Investigate why the projects failed to load, and that should solve your issues.
  23. Already known; certain existing features don't play well with the new upsized sprites. https://github.com/kwsch/PKHeX/blob/master/PKHeX.WinForms/Resources/text/changelog.txt#L19-L20 https://github.com/kwsch/PKHeX/commit/bf47317dd1616153e7be5bb85ab641f1cb3ede1a
  24. PKHeX has never auto-deleted when dragging between two windows. The processes do not communicate with eachother. It is up you you to drag & drop, and delete stuff afterwards if you so desire.
×
×
  • Create New...