Jump to content

Kaphotics

Helpful Member
  • Posts

    6902
  • Joined

  • Last visited

  • Days Won

    325

Everything posted by Kaphotics

  1. Added a flag in Settings you can toggle for the Entity Editor to show Gender in Gen1 contexts. https://github.com/kwsch/PKHeX/commit/b60648627a53c3dc12799f0d91d2cc7a0061aa02 Currently only in the development build, but will be available in future releases.
  2. Kaphotics

    error

    Export your save data correctly, that doesn't appear to be a save file that you've exported with homebrew.
  3. Gender doesn't exist in Gen1, so it isn't shown. It was changed approximately 2 years ago. Sure the gender value would be the same as it is if it were transferred to Gen2, but again, it isn't shown because it could confuse users as it's not a feature in Gen1, and it doesn't seem like it would be much value added to show.
  4. Do what the message box says. You need to install the runtime for the program to work.
  5. Consider multiple languages. Gen3 does not store a flag in the pkm data; if the nickname bytes do not match the game (language specific) name, then it is nicknamed. Gen4 does store a flag; and changing the nickname to match the species name will un-nickname the pokemon. https://bulbapedia.bulbagarden.net/wiki/Nickname#Changing_nicknames
  6. Try this Had to clear boxes 27+ but it doesn't seem you had anything in them anyway. main
  7. PKHeX is a Windows application, so I'm assuming the error is with whatever you're using to run Windows applications. Check next to the exe for any error log files, otherwise it's not really possible to troubleshoot based on your description.
  8. I hotfixed the exe shortly after release with a fix for some channel recognition; can you confirm if it is flagged on latest release (or current dev build)? https://github.com/kwsch/PKHeX/commit/bf476f4de55217b4713027677b4fc1277a3562c8
  9. Working as intended; if it does not follow the PIDIV restrictions for floating/entering then the PID can't be obtained. It's a recently added check.
  10. Yes, but nobody knows because it's easier to just start a new save file.
  11. It should be a Method 1 PIDIV type, not "none". Either the PID was changed, or the IVs were changed. It's not legal, and the program is working as intended.
  12. The error message tells you why it was unable to continue, you did not give it a full ROM dump to work with. It is looking for a "rom2" path for the exefs, but no file was found, and it cannot patch the exefs for your modified files. Current advice is to use layeredfs via custom firmware, instead of rebuilding ROM files.
  13. Transfer them legitimately through HOME. https://projectpokemon.org/home/docs/home_165/relevance-of-home-tracker-home-v200-v300-and-beyond-r154/
  14. This thread is for reporting issues with legitimate pokemon; hacked pokemon that did not travel to the requisite game are being correctly flagged as hacked.
  15. Entirely different. You can ignore the resort slot messages if you know they are not currently occupied; the data is merely a shadow/remnant of a slot after you recall it from the resort.
  16. The official HOME servers assign the value. You cannot assign the value yourself, as HOME servers are the authority on authenticity. If they don't have data for your tracker that matches the content of the data, then you get the usual error 10015. https://projectpokemon.org/home/docs/home_165/relevance-of-home-tracker-home-v200-v300-and-beyond-r154/
  17. Same. Hover for whatever, and use my first message as a guide on how to convert between the two display types.
  18. Box Binaries are for copying boxes between same-format save files. The program only performs transfers for individual files, not boxdata/pcdata.
  19. Starting in generation 3, the game stores a random 32-bit number (0 - FFFFFFFF) for every Trainer to differentiate them from others with the same name. In generations 3-6, the game takes this 32-bit number and displays the lowest 16 bits of the 32, which ranges from 0-65535, as the visible Trainer ID. The remaining 16 bits are the invisible "secret" ID, also 0-65535. For trainers originating in generation 7 and beyond, the game instead displays the 32-bit number as a decimal number, but only displays the lowest 6 digits. Since the 32-bit number ranges from 0-4294967295, we have 6 digits to display, and a value 0-4294 (or 4293 depending on the lowest 6 digits) as the invisible "secret" ID. If you want to enter a 5-digit ID, then make the Trainer data (Pokémon) originate from an earlier generation. When you change it back to Gen7+, the displayed values will be equivalent. If you hover over the text boxes, the program tells you the other representation.
  20. Dump your pk1 data and search the save file for the same sequence of bytes. https://bulbapedia.bulbagarden.net/wiki/Save_data_structure_(Generation_I) Structure is not entirely sequential due to how they store strings separately from data.
×
×
  • Create New...