Jump to content

Kaphotics

Helpful Member
  • Posts

    7216
  • Joined

  • Last visited

  • Days Won

    357

Everything posted by Kaphotics

  1. Nobody has bothered contributing translated legality message data. PKHeX only has translations for English, Korean, and Chinese. https://github.com/kwsch/PKHeX/blob/master/PKHeX.Core/Resources/text/en/LegalityCheckStrings_en.txt https://github.com/kwsch/PKHeX/blob/master/PKHeX.Core/Resources/text/ko/LegalityCheckStrings_ko.txt https://github.com/kwsch/PKHeX/blob/master/PKHeX.Core/Resources/text/zh/LegalityCheckStrings_zh.txt
  2. Double check you have the correct origin game; works fine for me.
  3. Balls from Male parents were not inheritable until Generation 7 (Sun/Moon); the program is correctly flagging in this case.
  4. Be sure you are using the latest stable release, and that you are importing the save file correctly.
  5. Nobody knows, but it's doubtful that cosmetic unlocks are checked / cared about. The cheat is the same type as the one for Sun moon, but no bans were observed.
  6. The Pokedex never caused save corruption, was an incorrect rumor. Any issues related to exporting save files has been fixed.
  7. Milotic is hacked (trade evolution data not present), but I've fixed the non-flagging issue. https://github.com/kwsch/PKHeX/commit/897ed84933fa1741625d8ed73087d2f95bbd05ed
  8. Read the stickies. The latest release (last month) does not support the upcoming games.
  9. Using the 2nd option (pcbin) preserves the order. As for the options, it allows you to override the current set-to-sav setting. yes = modify to fake a trade to this save file no = just inject it :^) cancel = use current setting.
  10. Two options: (Menu Ribbon) Tools -> Dump Boxes. Then drag and drop the folder into the destination save. (SAV Tab) Export Boxes to a pcdata.bin, then drop the pcdata bin into the destination save. Can only be done if the pkm format is the same between games, and the box count must be the same too. You can disable auto pkm ot fixing by unticking the checkbox in Options. I don't recommend doing that, as it'd possibly result in illegal pkm data.
  11. Should be working fine on latest commit: https://github.com/kwsch/PKHeX/commit/5e6b2f43c2e4599f04f42a1f2d3d6adfca7dd077 Thanks for reporting
  12. Added the fashion payloads to PKHeX, but there might be a few gaps? https://github.com/kwsch/PKHeX/issues/1602
  13. Post pkm files. New events distributed after the last release date are not in the event database; PKHeX dis not automatically download new gift data.
  14. Because whatever source you are referring to is incorrect. The Darkrai encounter does not come with a Fateful Encounter flag.
  15. PKHeX is correct in this case.
  16. Maybe a way would be to remove revives from shops, and force the user to conserve them. Try setting BoostACC to 0. I'd think the game reuses flags for different purposes. The only items that have the same BoostACC (=1) are... Revive, Max Revive, and Revival Herb. Alternatively, try dummying out the item completely by copying over an unused item
  17. =OT=Ash the reflective searching uses properties from the mystery gift class, not the pkm class
  18. Read the error message.
  19. Kaphotics

    PKHEX USUM

    When it's ready.
  20. You have to use the mono version and I think run it with wine.
  21. Will be hex editing only for now, I do plan to come up with something before the end of the year for this tho.
  22. it's ripping off the last few bytes used for the RTC footer -- it's probably a 1-2 lines of code fix but I'm preoccupied with the new stuff right now You can compare the two files in a hex editor at the bottom, just insert the RTC data at the end of the edited file.
  23. you've used cheats on the save file, which breaks any pattern used for save detection. you'll have to hold control when importing the save.
  24. https://github.com/kwsch/PKHeX/blob/3594d1af5cf86d946bdce1697a9c5e7a1894c995/PKHeX.Core/Resources/text/en/text_Memories_en.txt#L39-L108
×
×
  • Create New...