Jump to content

Kaphotics

Helpful Member
  • Posts

    8033
  • Joined

  • Last visited

  • Days Won

    486

Everything posted by Kaphotics

  1. Challenge yourself to learn how hex editors work and the layout of the save file -- set the byte width to 0x1000, then you can corrupt the most recent save blocks so the game loads your backup instead. Save data structure (Generation III) - Bulbapedia, the community-driven Pokémon encyclopedia PKHeX does not allow loading of the backup portion, only the most recent part of the save. I guess you could debug the program to tell it to load the not-latest portion, but that isn't something worth explaining in detail.
  2. PKHeX was last updated March 20th, which was ~2 weeks ago. HOME's update to allow inbound transfers was 2 days ago. PKHeX does not have handling for inbound transfers, because it does not have a future-predicting crystal ball to know exactly how GameFreak/ILCA will implement it.
  3. When was PKHeX last updated? Why are you expecting HOME transfers in to be flawlessly recognized, which is "new" as of a couple days ago?
  4. Update your game by connecting online and downloading the latest software content patch.
  5. Outdated version of PKHeX aside, the ribbon is available for a species only if the species could have been used in ranked battles. If the species couldn't be obtained yet or hasn't been legitimately transferred to a game that allowed for use, then it can't have the ribbon.
  6. The ROM (the game you are playing) forcing stats back to what it thinks is sane while the game is running is not something a save file editor can override. You need to reprogram the game to change its behavior to not do that anymore; either via cheat code while the game is running, or modify the ROM. Again, not something a save file editor is for -- a save file editor edits save files.
  7. Already reported and fixed; use to the development build in the meantime.
  8. Not a valid dump. There isn't anything in that file recognizable.
  9. Cosmetic features that you can readily change in game are not of much interest to research and implement, hence why there isn't anything for that specific feature in the program. Spirit/Mood in LGPE: https://gist.github.com/Lusamine/48654c3d0efa0cdab38d6c6816655929
  10. Probably because you used a not-Japanese save file to catch it, thus having invalid trash bytes applied. Program working as intended. The Gen3=>Gen4 transfer re-encodes both Nickname and OT, so the original trash bytes are not carried forward, hence the clean report in Gen4.
  11. An egg that originated in HGSS should have the HGSS ball set. Otherwise, it should not have a HGSS ball value. Version does not update on hatch; therefore the version ID is a clear indicator on which game it originated from. When viewed/edited in the GUI, the GUI will automatically correct it for you. Both files you attached show as legal.
  12. Add WC 0527 (#580) · projectpokemon/EventsGallery@b7d61e2
  13. PKHeX does not support ROM Hacks.
  14. I'm pretty sure the Resort slots show up in the Other tab, shouldn't need another tool to access their data.
  15. A checksum is a checksum, nothing more. In this case, it's a quick indicator that the data is not the exact same as the other file.
  16. It's a checksum of the data.
  17. Use the encounter database in PKHeX and it will generate the starters for the TID/SID of the save file if it is loaded. As for searching for a a TID/SID that gives you both starters as you'd like, I'm not sure something like that exists.
  18. Use the encounter database. PID/IV for the starters is tied to the TID/SID (because they all generate in the same sequence), so you cannot have multiple PID/IVs for a given TID/SID.
  19. 1. it's somewhere on the map, but it hasn't been captured yet so it has no location value set. 2. Alola, Raichu - Side Missions - Pokémon Legends: Z-A - the game remembers what you gave her in the scripted event.
  20. Try clicking on them.
  21. Convert it back to a PK4 (DPPt/HGSS save file), then convert it back to BK4 (Battle Revolution); don't edit it afterwards. I've added a commit to not set the BallHGSS value when editing from a Battle Revolution save.
  22. The program improves each release; it is now checking for a property that wasn't checked previously. Change the ball to something else, then change it to your desired ball.
  23. The program already tells you the issue is with the Ball value. Use the GUI to change the ball value until it is fixed.
  24. You changed the PID at some point in time. Use the encounter database to regenerate it with the IVs/Nature you currently have, and see what the resulting PID is.
×
×
  • Create New...