Jump to content

Kaphotics

Helpful Member
  • Posts

    7028
  • Joined

  • Last visited

  • Days Won

    336

Everything posted by Kaphotics

  1. 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.
  2. 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.
  3. Kaphotics

    Change TID

    The game disallows an all 0 trainer id
  4. 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.
  5. PKHeX is working as intended. It's a bug with Pokefinder. https://github.com/Admiral-Fish/PokeFinder/issues/359
  6. .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.
  7. PkHeXEggLockeGenerator.EggLockeOptions Plugin issues should be directed at the plugin author, not to the general PKHeX help forum.
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. 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.
  13. Open it in a hex editor like HxD then delete the bottom half of the bytes (0x80000 onwards).
  14. 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
  15. 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.
  16. 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.
  17. Refer to the guide. The label above the text box tells you what the current value is in the PKM editor pane.
  18. Download the regular PKHeX and extract it from the zip to your computer before running it.
  19. There's no way to specify incremental values with the batch editor. The batch editor only processes one pokemon at a time, and each does not influence any other slot. The batch editor edits a batch with the same modifications; if you want custom code with varied behavior, you can always write your own code with something like LINQPad.
  20. With custom firmware you can import any save file you like. If it was a manual backup without using custom firmware, then it's not of any use. Just import your old "main" like you would restore an edited save.
  21. The default value is 0. If you clear the HT Name, you need to clear the other HT values as well.
  22. What batch editor commands have you tried? A simple one would be to filter for species only being Zorua, then change the ball ID to the ball ID you want. The guide tells you how to find these IDs based on the currently loaded Pokémon. If it's only 6, it's probably faster to just change the ball manually rather than finding the correct IDs. Clicking on the ball will bring up a selection interface, and you can use the keyboard modifiers to quickly view/set by holding ctrl & shift respectively.
×
×
  • Create New...