Jump to content

Kaphotics

Helpful Member
  • Posts

    7825
  • Joined

  • Last visited

  • Days Won

    449

Everything posted by Kaphotics

  1. Not a feature within PKHeX.
  2. I already told you to look at the OT Tab, and check the current handler state. If you are having trouble understanding error messages, change the translation of the program via Options->Language. If your save file is not the original trainer of the pokemon, then the handler state should not be pointing to the OT.
  3. 1. Handling trainer flag must be correct for it not to be flagged. Look at the Current Handler state on the OT tab, and reread the popup message. 2. Mystery Gift files are templates, and receiving them in game will just fill out the data based on the recipient save file, same as PKHeX does it. Nobody has curated a list of which mystery gift files are region locked or language locked, into a digestible format that programs can use. So, PKHeX has no enforcement of it if it truly is unable to be received by your game save.
  4. Empty moves should have 0 PP. PKHeX takes the stance of flagging anything that disobeys the rules as invalid, even if it may have been done by bad game code. Some mystery gifts in future games also set PP to empty move slots, and need to be healed in-game/viewed&set to correctly reset to 0 PP.
  5. Read the first post of this thread again: NOT FOR USER MISTAKES OR TROUBLESHOOTING HELP. The message is clear enough to help you fix your mistake you made creating the data months ago.
  6. play it on your console and try from that save file instead.
  7. Attached file has no issues. To check legality in box, hold control when right clicking.
  8. Open in HxD set view width to 0x1000 bytes reference the block structure on bulbapedia/pkhex source code to see the "block index" at the end of the 0x1000 chunk of data. cut and paste 0x1000 byte segments to reorder
  9. Same issue as other threads that have been reported and fixed. Using the 0x1000 block layout of gen3 saves, I rearranged the order of blocks since it seems like the save writing was interrupted when overwriting the flash chip, so that each save (primary and main) has a complete set of save blocks, and re-exported from PKHeX. POKEMONE.SAV
  10. Open it in a hex editor and compare it to a valid working save file. If it is similar, you might be able to change it manually to get it to be recognized. Can't tell if you don't share the save file.
  11. If the story progression is misbehaving, then something you did to it would have "broken" progression. Whether it's impassible depends on what was messed up. If the save file restored without needing to be re saved in a save editor, then there was no external corruption.
  12. Shininess is determined from PID and trainer ID. Changing one, of course you're going to have issues especially if there is a PID/Trainer ID correlation for the encounter.
  13. Checksums are valid upon opening the save file. Modifying things like changing the box might not be tracked as "edited", but the checksum will no longer match what is expected since the save was truly modified.
  14. PKHeX is open source, read the source code or step through with a debugger if you must understand how it works. There's way too much to describe to waste time writing guides and wikis for every single file format and interaction. X/Y's format is described here, for both the raw save archive and main: https://projectpokemon.org/home/docs/gen-6/xy-save-structure-r82/
  15. PKHeX checks for more things than PKSM to give early warning of corruption, rather than just loading if the size is correct. Your save file's footer is invalid. Use a hex editor to copy the last 0x200 bytes from another working save file and replace your save file's last 0x200 bytes with it. Then, open and export with PKHeX. More specifically, offset 0x75E00 is expected to be "BEEF", while yours is 0 (uninitialized).
  16. If the checksums are valid in PKHeX, then it's likely you manually manipulated/restored an old file on the SD card directly. If you delete your save data and recreate it (on the 3DS), then restore your old save file (with homebrew) then it should work. The console has tamper protection, hence why you can't restore backups without homebrew.
  17. Raw files on the SD card are encrypted per-console and have their own file-structure. Hence why the size/filename is different. You need to use homebrew to access the "main" save file. You should never manually manipulate/use the files on the SD card.
  18. Use the command builder drop-down. You can require properties to be equal in order for them to be modified. Refer to the batch editor guide.
  19. You're using an older version, try checking the latest release.
  20. Please try to understand the limited amount of seeds and the statistical odds to get specific requests. 3 flawless IVs is 2^5^3, which is 2^15. 2^16/2^15 is approximately 2 results are expected to have 3IV. Choose a less limited encounter (like Japanese AGETO celebi, which is CXD type, or a Gen4 wobdercard) if IVs are a must.
  21. BACD-R means there are only 2^16 seeds (0000-FFFF) possible. Obtaining the IVs you requested is 2^25 odds. No surprise you can't find anything, because there aren't any seeds that give you good results. Pretty sure OT Gender is the recipient gender, hence why it's not flagging.
  22. HOME might permit it to be uploaded, but if it's inspected in HOME, I think it will lack the metadata that a legitimate GO Mon would normally have.
  23. If it originated from a game that needed to transfer through HOME to reach the game it is in (SWSH, so yes), then it won't be legal to upload into HOME. HOME expects it to have a tracker, which it does not have, so it will reject the upload. How to get around it? As stated in the linked thread, you can't for things originating from GO. The only way to get valid trackers is to start with something transferred from GO. For meltan, generate it in LGPE originating from GO Park complex, then connect that game to HOME.
  24. Handler: means what it says. Can't be handled by the OT because the OT is from GO.
×
×
  • Create New...