Jump to content

Kaphotics

Helpful Member
  • Posts

    7821
  • Joined

  • Last visited

  • Days Won

    448

Everything posted by Kaphotics

  1. There is no need to have naturally perfect IVs because bottle caps exist. So the program unconstrains itself so it may more easily generate the Pokémon. You then apply bottle caps, like you would if you actually obtained it in the game. Nobody believes you when you present a natural 6IV wild capture.
  2. 45 is the unconverted (original) catch rate value. When it is transferred to Gen2, it becomes "Bitter Berry", which is item # 83. Then transferred back to Gen1, it remains as # 83. Nickname flag is derived from the name being unmodified, without trash bytes. Potentially they are because they have been transferred to Stadium, which can alter those bytes.
  3. Open it in a hex editor then delete all the bytes after 128KB.
  4. Okay, so why isn't there any trace that it was traded to someone else to trigger the evolution?
  5. And how exactly does Kadabra evolve, and what traces would that leave in the data? You can't get duplicate save files without tomfoolery, so you are making the games misbehave.
  6. Nobody can help you if you are vague. "keep getting errors"... say what they are? There are threads dedicated to discussing running PKHeX on Linux systems. Please use them. You're likely not the first with an error message, so try google searching the error message as well.
  7. Go ask whoever is running the bot you are using, or find a different bot.
  8. Undocumented. If there were a better name to display, then it could be displayed.
  9. spend the few minutes looking for info on the error message. self-troubleshooting is a valuable skill READ: HOME Tracker Value - PKHeX - Project Pokemon Forums
  10. Not a PKHeX issue. Connect online and update your game to the latest patch and save in-game.
  11. Not a valid dump. Likely not dumping the correct region of the savedata chip of the bootleg.
  12. There is no enum, as forms vary from game to game. Use FormConverter
  13. PKHeX does not support ROM hacks that modify the save data structure.
  14. `main` opens just fine if you truncate it to the proper save file size (0x76000) with a hex editor.
  15. https://github.com/kwsch/PKHeXPluginExample
  16. your save file has a ton of stuff missing, so I just dumped the box data. your party is empty. boxdump.zip
  17. The program will need to be updated. Each new game is different from the last. Estimated timelines for support: please do not ask "eta wen"; if support is going to be added / release windows, they will be announced.
  18. Try it and see. https://github.com/kwsch/PKHeX/discussions/4500
  19. The double-game savefile issue is moreso an emulator issue, as it will never happen on actual hardware. The currently implemented heuristics have been "good enough" for years... I did recently rewrite the save detection logic a couple months ago to have a spot where it can be manually overridden: PKHeX/PKHeX.Core/Saves/Util/SaveUtil.cs at master · kwsch/PKHeX With a new game releasing in a week, I can try to fit in something. Maybe something like "hold alt when opening a file; if a save is what you loaded, it will open an override UI where you can change the detected type => load".
  20. File type detection briefly inspects the data to guess what game/language it belongs to. Seems it passed the English Crystal heuristic and was therefore assumed as such. Does this still happen if you save in a different map, after changing boxes to another box in game? If that isn't a valid workaround, I can possibly add a branch of code where if it passes both, then it checks the checksums too, but that would be a compromise that impacts manually edited files to no longer being recognizable (if they also end up clashing) hence maybe needing a more detailed detection heuristic.
  21. You cannot change immutable values, which obviously includes changing the species to something else.
×
×
  • Create New...