Jump to content

Kaphotics

Helpful Member
  • Posts

    7273
  • Joined

  • Last visited

  • Days Won

    362

Everything posted by Kaphotics

  1. You're not using the latest version of Wine.
  2. PKHeX does not support ROM Hacks. Ensure your emulator is exporting a proper save file. The program does not know what modifications an emulator / rom hack make to a binary save file.
  3. Empty/blank lines should not be included in the text box. Ensure you have only entered two lines, and that all lines you have entered are "complete" instructions.
  4. Check the randomization settings. Low-powered moves are intended to be given instead of higher-powered moves, for a more balanced early level experience.
  5. If the checksums are invalid, then all you have to do is export the file from PKHeX and it will apply the correct values. It is important to ponder why the checksums were originally invalid -- did you manually modify the save file? Is the dump actually "complete" and not a glitched dump from dirty cartridge contacts resulting in bad reads? Is it from a ROM Hack which has modified the save structure, resulting in different checksum locations or calculation methods?
  6. Each SaveFile object exposes an `Inventory`.
  7. You didn't export your save correctly. Save states are not save files.
  8. Master Ball cannot be inherited via breeding.
  9. 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.
  10. 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
  11. Your save file is not valid. Try exporting it with homebrew again.
  12. 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.
  13. 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.
  14. 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.
  15. Kaphotics

    Change TID

    The game disallows an all 0 trainer id
  16. 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.
  17. PKHeX is working as intended. It's a bug with Pokefinder. https://github.com/Admiral-Fish/PokeFinder/issues/359
  18. .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.
  19. PkHeXEggLockeGenerator.EggLockeOptions Plugin issues should be directed at the plugin author, not to the general PKHeX help forum.
  20. 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.
  21. 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.
  22. 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.
  23. 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.
×
×
  • Create New...