Jump to content

Kaphotics

Helpful Member
 View Profile  See their activity

  • Posts

    7957

  • Joined

  • Last visited

  • Days Won

    476

 Content Type 

Everything posted by Kaphotics

  1. Kaphotics
    Yes.
  2. Kaphotics
    Same exact explanation. If it's not being handled by the OT, as in the OT is not the currently loaded save file, then it must be HT.
  3. Kaphotics
    It's the case for every Pokemon, since X/Y. The trade bot will update the handler information itself to match its save data, otherwise it would be a detectable hack. You really shouldn't be resisting this fix & detection.
  4. Kaphotics
    You don't have a save file loaded, so PKHeX provides a blank save as indicated at the top of the program window. Who is the OT of that save file? PKHeX. When you edit a Pokemon, who is handling the Pokemon? The currently loaded save file. If the handler data stored in the PKM does not match what is expected (should be the save file), then you get the messages as you've shown. How do you get it to be handled by an arbitrary OT? Load the save file for that OT so the program knows where the PKM will reside. Don't have the save file for your OT? Well, who is currently handling it?
  5. Kaphotics
    You just need to trade the egg to a game where the egg will have a trainer ID that makes the PID shiny. If you've received an egg, check the PID then RNG abuse a game to get a trainer ID that will make it shiny. If you've not received the egg yet, then identify a spread you want, and then RNG abuse that spread when receiving the egg, and RNG abuse a hatching trainer as previously described.
  6. Kaphotics
    PKHeX checks the menu advancement pattern in addition to the PIDIV. If the game menu cannot reach your PIDIV seed, then it is impossible to obtain, hence illegal.
  7. Kaphotics
    If you can't code, here's how you'd still be able to help: Find the offset within the save file that determines what you're trying to change. Change the values manually in a hex editor like HxD to document what values and offsets do what. If you provide in a post the offsets/structure of the data, and a list of values that can be used, then someone can take that and convert to code.
  8. Kaphotics
    I'd recommend using a separate more-focused ROM unpacking tools rather than pk3DS. Just get your unpacked files to pk3DS.
  9. Kaphotics
    The mystery gift database is for mystery gift files; since WC3 data never existed, they can't really be shown in the file database. They are still found in the encounter database, just like the Gen1/2 event encounters.
  10. Kaphotics
    PKHeX edits save files from official games only. Feel free to make your own tool or fork if you wish to support entirely different games.
  11. Kaphotics
    This hack in particular does not make any changes to the save file structure. OP is just restoring the save file incorrectly.
  12. Kaphotics
    Not a feature within PKHeX.
  13. Kaphotics
    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.
  14. Kaphotics
    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.
  15. Kaphotics
    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.
  16. Kaphotics
    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.
  17. Kaphotics
    play it on your console and try from that save file instead.
  18. Kaphotics
    Attached file has no issues. To check legality in box, hold control when right clicking.
  19. Kaphotics
    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
  20. Kaphotics
    Use the encounter database.
  21. Kaphotics
    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
  22. Kaphotics
    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.
  23. Kaphotics
    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.
  24. Kaphotics
    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.
  25. Kaphotics
    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.
×
×
  • Create New...