Jump to content

Kaphotics

Helpful Member
  • Posts

    7957
  • Joined

  • Last visited

  • Days Won

    476

Everything posted by Kaphotics

  1. Can't know what is happening without knowing the trainer ID of the currently loaded save file, and the ID of the Pokemon. If the Pokemon details matches the save file, then it should be handled by the OT, otherwise, should be the HT. Hence the message. Sharing trainer IDs across different versions results in incorrect handler flags because the game does not check the trainer Version, and it's a sign that the Pokemon or save file is not legitimate.
  2. Date modified on your save file is an hour before your original post, yet you have save states with more recent timestamps (today). Be sure you are exporting your edited save file from PKHeX (date modified changes), and that the emulator is told to look at the edited save file (depends on the emulator).
  3. Verify that you're setting your changes to the spots you're intending, and that you're exporting your save file to the correct file location. PKHeX doesn't eat your changes and ignore them on export; data does not magically revert.
  4. You haven't mentioned how you are playing your game, via emulator or on console. If emulator, find where the emulator stores its save files. If console, dump it the same way you dumped the ROM. Not all emulators behave the same and store consistently, and it's outside the scope of PKHeX. Once you find your save file and have it exported correctly, you can load it into the program.
  5. PKHeX is a save file editor. You uploaded an nds file, which is a ROM. Open the sav instead.
  6. Was reported and fixed earlier, use the dev build or wait for the next release (maybe end of this weekend)
  7. "HaX" only unclamps some editors and allows disabling the recalculation of stats. If the emulator does not recognize changes, and your changes persist when reopening the save with the editor, then you didn't import your save back to the emulator correctly. Be sure to not be using save states when resuming your emulation session, as the emulator needs to read your saved data rather than continue from a previous snapshot.
  8. In generation 4, shininess is determined based on who hatches the pokemon. You're using two separate objects to fetch the trainer ID. The code you pasted does not compile on the latest PKHeX.Core dll, because `ShinyUtil.GetShinyPID` requires different typed arguments. public static uint GetShinyPID(in ushort tid, in ushort sid, in uint pid, in uint type) { var low = pid & 0xFFFF; return ((type ^ tid ^ sid ^ low) << 16) | low; } TrainerTID7 is a uint, not a ushort. When in doubt, look for how PKHeX itself uses the methods: As you can see, you need to provide the 16-bit trainer values. You're passing in a 0 for the old PID, so the shiny PID that comes out will be less "random" with the lowest 16 bits being 0.
  9. Previous versions didn't visibly flag pokemon for missing HOME trackers; it only showed the message if a verbose legality report was requested. Recent versions changed the behavior, because it is not legal to lack a HOME tracker for foreign game transfers. The program has a plethora of settings that you can turn on and off if you feel it is irrelevant to how you want to use the program.
  10. Kaphotics

    Problem

    The mobile application has not been updated in years, and was never updated to support BDSP and future games. This forum is for the PKHeX Windows Desktop application.
  11. Kaphotics

    Problem

    No, it opens it just fine, hence the picture I posted of it working.
  12. Kaphotics

    Problem

    PKHeX opens it just fine. You've only played 2 minutes.
  13. No it's not.
  14. Look around in PKHeX. Look around the Internet. Forks exist.
  15. You'll need to be much more descriptive because hidden ability has been around for 5 generations now. Be sure the hidden ability is possible to obtain in the game, and ensure that the encounter is capable of obtaining it in the situation where the game does not have Ability Patch available.
  16. Now compare the difference
  17. Behavior adjusted on latest commits; try dev build. https://github.com/kwsch/PKHeX/commit/6b51250f880e0075a2b1eefa78e7d6b8e0facb1c#diff-38e0fe4dc7d210c5436b833b03c8581aff804ee6526e7c2ffe4c31a1d9af260dL51 Can also just use the batch editor to clear the HiddenAbility flag.
  18. Use the encounter database. Plugins are unrelated to this forum.
  19. If it were traded to someone else, would it remember who it was last traded to?
  20. PKHeX is a save file editor. If you want to edit your save file to unlock things, open your save file to edit it. If you cannot obtain your save file (no cfw to extract it), then you cannot edit your save file.
  21. Trade evolutions require trading. If it has never been traded, it never could have been trade evolved.
  22. Those properties can only be used as filters; you cannot set to them because there is no setter in the source code. They're constant values based on the PKM class type. If you are looking to clear all trash, you can do it like so (filter for a specific pattern, clear and reapply): =OriginalTrainerName=Kurt .OriginalTrainerTrash=$[]00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00 .OriginalTrainerName=Kurt =IsNicknamed=false .NicknameTrash=$[]00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00 .IsNicknamed=false
  23. Opened in a hex editor; the file looks to be random junk. Probably the battery died and the storage stopped retaining data.
  24. Not able to replicate. You shouldn't be using hax anyway.
  25. Try a tool other than pk3DS. Probably just a bad ROM dump.
×
×
  • Create New...