Jump to content

Kaphotics

Helpful Member
  • Posts

    7272
  • Joined

  • Last visited

  • Days Won

    362

Everything posted by Kaphotics

  1. An appropriate thread is on the first page of this subforum.
  2. Try rebuilding the romfs with another tool to determine if pk3DS is the problem or not.
  3. Already reported, already fixed :-)
  4. Error usually implies there was a problem reading a file from the location, namely the SD card. When PKHeX launches or opens the open file dialog, it looks for save files to detect the most recent file you may be wanting to load. I can enhance the error message to spit out the filename that is screwing up, but you can always scan for bad filenames or copy the save file to your desktop and remove the SD card when booting PKHeX until the next release.
  5. Pretty sure you are not using a recent version of pk3DS; re-download from the pk3DS thread or compile it yourself to make sure the build options are compatible with your system.
  6. Save file format is not recognizable
  7. Hyper training is only available once the pkm reaches level 100.
  8. You'd need to have before&after save files, and use the event flag diff tool in PKHeX to tell you which event flags were toggled. From there, you can fiddle with them until you find the flag number that causes it to respawn. Then it can be added to the event flag list
  9. Editing mystery gifts is a no; you can edit the resultant PKM's met date after receiving it ingame. If you're injecting the gift with PKHeX, just inject it directly to the tabs and edit the result there. There are other tools that can edit mystery gifts if you really must have editing of the template files.
  10. Already been fixed https://github.com/kwsch/PKHeX/issues/964
  11. reread the error message the current handler (green highlight) cannot be the OT. Set the current handler (green highlight) to the Handling Trainer, not the OT.
  12. upload the pkm it's a trade encounter but the error message indicates it can't match it.
  13. change the transfer mode or remove the SD card manually and transfer. again, the transfer program is dropping bytes resulting in an incorrect size.
  14. Read the source code or look at this site's wiki.
  15. read the shortcuts alt click the Box tab. just checked, the latest versions are not affected by this. It gives wishiwashi seen flags for both forms.
  16. hopefully I don't regret this, feels hacky https://github.com/kwsch/PKHeX/commit/eb8b9602b2d00b4cbab57528727bb1cce5ebddb3
  17. response inline; in general, I don't bother with low usage/high time requirement features and leave it up to the community to research (and even implement) what they want the program to handle. if you make any changes to the save file (ie set anything) without exporting the save, you'll get an alert. I don't see it necessary for checking even further back if the pkm that was loaded was modified (if nothing else has been set yet). I mean, I can always set the "Edited" flag when something has been viewed, but that could end up nagging people who quickly opened to view something.
  18. PKHeX decrypts the data and doesn't modify it. Dumping box data is safe.
  19. Can always do database -> advanced filter search for a box -> dump results alternatively, advanced filter for identifiercontains (box name)
  20. Keyboard shortcuts are interfering. Control click is to view, Shift click is to set, and Alt click is to delete.
  21. The one set of faces/up/down/zz is not enterable, but is present in the character table The face order was screwed up in sun/moon; PKHeX uses the same font file as the PGL.
  22. Yeah it's a known issue. If it ever happens again just initiate the transfer again; the file is fine on the SD card -- it just needs to be transferred completely. I recall seeing a setting for filezilla regarding binary transfer mode instead of ascii; may be worth looking into.
  23. Invalid save file (length) is usually caused by an FTP app not transferring the data to the PC completely. Were you using an ftp app to transfer?
×
×
  • Create New...