Jump to content

Kaphotics

Helpful Member
 View Profile  See their activity

  • Posts

    6884

  • Joined

  • Last visited

  • Days Won

    322

 Content Type 

Everything posted by Kaphotics

  1. Kaphotics
    Then you didn't export your save data correctly. The 3DS stores its files encrypted on the SD card to prevent people from tampering, which is why you need to use homebrew to export correctly.
  2. Kaphotics
    Resolved on Discord; the OT Name that was set to the PKM via batch editor had a leading space; end result was that the OriginalTrainerName did not match that of the save file, so HT data was being reapplied (intended). Ensure the OT name matches that of the save file
  3. Kaphotics
    Your save file is not valid. Try exporting it with homebrew again.
  4. Kaphotics
    Inside the program's settings for the encounter database you can use the main editor to provide criteria for the template generator. If you have a desired nature, gender, ability, etc, it'll try to match whatever is allowed.
  5. Kaphotics
    PID/IV correlation exists.
  6. Kaphotics
    Emulators should be able to export raw save files without extra emulator-specific metadata. PKHeX should not be responsible for supporting whatever arbitrary format the emulator/ripper decided to package the savedata as.
  7. Kaphotics
    Your hack has modified the savedata structure; PKHeX scans to make sure things are "proper", and your save is not. The first savedata object is expected to have a size of 0xF628, but it seems yours is 0xFBE0 (larger). The box storage object is also too large, coming in at 0x1E4FC (not 0x12310). So, your save struct is different from what PKHeX expects for a valid HG/SS save file, and is thus not an HG/SS save file.
  8. Kaphotics

    Change TID

    Kaphotics replied to dow1979's topic in PKHeX

    The game disallows an all 0 trainer id
  9. Kaphotics
    The answers for vague questions like this is always "it depends". Changing values after something is generated is only "safe" if the encounter is not locked into a specific requirement/correlation of values. Not every correlation is checked by PKHeX, so it's up to you to research and understand.
  10. Kaphotics
    PKHeX is working as intended. It's a bug with Pokefinder. https://github.com/Admiral-Fish/PokeFinder/issues/359
  11. Kaphotics
    .dst files are "save states", not "save files". They are memory dumps that the emulator can use to store the entire state of emulation for reloading later. Editors like PokeGen may have code written to peek into these save states and extract some data, but again, these are not save files. Save properly in-game and export your save data as you would on your console.
  12. Kaphotics
    PkHeXEggLockeGenerator.EggLockeOptions Plugin issues should be directed at the plugin author, not to the general PKHeX help forum.
  13. Kaphotics
    PKHeX is likely assuming it is the XD Gligar simply because the PIDIV you have for it is not a valid PIDIV for the Shadow Gligar from Colosseum. The PIDIV checks for the Poke Spot encounters are less strict. If neither is a complete match, it is lenient in at least giving you a close match and then verifies off that template.
  14. Kaphotics
    There's no setting to disable that; not sure why you NEED it to not change. The counters should increment if you ever write something, as you can't have 100 pokemon in the box if you've not captured/hatched at least 100 pokemon.
  15. Kaphotics
    No; the Batch Editor isn't intended for much logic based on non-stored properties. You can always write your own code (C#, LINQPad etc) to fetch the evo stage from the Personal data. Alternatively, you can use BST thresholds to apply a specific current level.
  16. Kaphotics
    The structure is shared with X/Y, which has a slot reserved for the Pokémon you give the old man in Anistar City. Dunno if it's used in OR/AS.
  17. Kaphotics
    Probably Poké Pelago.
  18. Kaphotics
    Such a thing does not exist.
  19. Kaphotics
    Probably is because of HOME restoring the wrong calculated values, and you were able to reset them by changing the form in game. Not worth fixing in PKHeX as it looks like a HOME misbehavior.
  20. Kaphotics
    Open it in a hex editor like HxD then delete the bottom half of the bytes (0x80000 onwards).
  21. Kaphotics
    Gen 4 save fi les are 512KB, not 1MB. Cut the file in half and it loads. Fix your emulator settings to use the correct savefile size. aa.sav
  22. Kaphotics
    Undocumented, unimplemented. Errors in plugins not applying required values aren't really in PKHeX's scope; when you disable settings like that, you're going to have invalid Pokémon in the save file. If the save file they reside in does not match the entire set of OT details on the Pokémon, then they can only be under the possession of a Handling Trainer (not OT). If I gave you one of my Pokémon, you're the current handler, not me. Same concept.
  23. Kaphotics
    Pokémon stored in a save file need to be handled by someone. If the current save file is not the OT, then it is with the save file (as a handling trainer) and is adjusted to be correct in the save file by applying handling trainer data. Handling trainer being OT requires OT details to match the Pokémon, such as the OT Name, ID, and trainer gender. There is a setting to disable the auto-fix, but if disabled, the Pokémon won't be legal in the save file.
  24. Kaphotics
    Refer to the guide. The label above the text box tells you what the current value is in the PKM editor pane.
  25. Kaphotics
    Download the regular PKHeX and extract it from the zip to your computer before running it.
×
×
  • Create New...