Jump to content

Kaphotics

Helpful Member
 View Profile  See their activity

  • Posts

    7919

  • Joined

  • Last visited

  • Days Won

    467

 Content Type 

Everything posted by Kaphotics

  1. Kaphotics
    It's an uninitialized save file (game not started). Nothing to recover.
  2. Kaphotics
    Not a valid dump; console-encrypted files are impossible to read unless you decrypt them first. You cannot simply copy the file off the SD card and have external programs read that.
  3. Kaphotics
    Look at what game you have open for editing.
  4. Kaphotics
    If the Pokemon match your trainer name/version/IDs, they will always obey. https://bulbapedia.bulbagarden.net/wiki/Obedience
  5. Kaphotics
    Gen8+ save files have a hash at the bottom of the file. Ignoring the file size. I ran PKHeX under a debugger and manually called the hash verification function to observe the result. The program rejects on invalid size or invalid hash, your save file failed both.
  6. Kaphotics
    Editing flags is no substitute for game progress. There is so much more that would need to be changed to properly progress your save. Just play the game again or find another save file to change the OT of.
  7. Kaphotics
    Hash isn't valid, assuming you transferred via FTP, fix your setting to force Binary transfer -- not ASCII/text.
  8. Kaphotics
    Pokemon - Fire Red (BR).sav
  9. Kaphotics
    Only blocks 2,3,4 are present in your save file; missing blocks 0 (trainer info), block 1 (party), and boxes (6+), there really isn't anything recoverable. Recovers just fine by the recovery tool. Initial Release · projectpokemon/RecoverSaveGen3
  10. Kaphotics
    1. Language "should" be matching the save file, unless it was moved directly from HOME after previously residing with the exactly same OT but with a different language. It is marked as Fishy because it is a less-than-likely situation, for manual inspection. 2. Bulk checks are to raise things to your attention, and are not definitive. As you've noted, some events have fixed PID/EC values, but these are not granted as exclusions by the program as it is not implemented as such.
  11. Kaphotics
    Known; crossovers are not handled for Z-A (probably won't be for quite a while) due to how many overlapping locations there are and the resolution of which is an innermost location ID for a given coordinate.
  12. Kaphotics
    I've made a bunch of revisions on the latest commit to address the behavior you've mentioned: Small tweaks to HGSS ball check · kwsch/PKHeX@6f9daae We weren't able to figure out how exactly Mood can get deposited into the Box without being reset to 0; we did notice that swapping party slots after interacting with them in the overworld can give Mood to eggs in the party. Seems the game has an issue with keeping track of pointers. If you're able to figure out a clean repro step, that would be helpful. Here are some of the notes regarding Mood's mechanics: https://github.com/kwsch/PKHeX/blob/6f9daaed0492c4d3910a0aa0e15ed8ffaee3527f/PKHeX.Core/Legality/Verifiers/Misc/MiscVerifierG4.cs#L117-L125
  13. Kaphotics
    Gen1 save files are 0x8000 bytes (32KB) not 80KB. If your emulator is not exporting save data, then you should consult with the emulator developer('s documentation). You really shouldn't use web emulators, as you can play your ROM dump on your PC with an actual emulator that saves correctly.
  14. Kaphotics
    Not a valid save file size. Whatever conversion you tried was not right.
  15. Kaphotics
    Majority of the savedata is missing, including the first half which contains game progress/party. Only a few boxes towards the end are present, but you had nothing in those slots. Nothing to recover.
  16. Kaphotics
    Different emulators store the RTC data at the end of the save file differently. PKHeX does not do any conversion between emulator save files. Try finding a converter online, or refer to the emulator documentation online.
  17. Kaphotics
    Update your program. The program tells you it is out of date.
  18. Kaphotics
    BDSP does not have trash bytes on Eggs; you can clear the trash bytes via the trash byte editor (hold control and click on the nickname text box).
  19. Kaphotics
    Open the save file in a hex editor, and set the width to 0x1000. You can then look for the end part of each block to see where each block resides in the file. Generally, they're stored in order, but they start saving from a random block ID and loop until all are saved.
  20. Kaphotics
    Referring to the wiki on save file structure and the recovery tool's output, your save file is missing critical parts of it (namely, blocks 0, 1, 2, which store your party, game progress, and trainer information). So there's not much to be able to recover besides box data. I copied the 3 missing blocks from a donor save file (mine) and ran it through the recovery program to even out the blocks. I don't advise trying to play the save file; only use it to recover your box data by dumping it into another save file. Pokemon - Emerald Version (USA, Europe) (1).sav
  21. Kaphotics
    PKHeX tells you the playtime at the top of the program window. The pokedex editor opens just fine.
  22. Kaphotics
    Probably is because of a vblank that occurred between the RNG calls, which is statistically infeasible (but not mathematically impossible, I guess). The game generates your SID & TID via two successive RNG calls (SID first, then TID) via 2 rand calls back to back. The assumption is that there should always be a RNG state that can yield the SID & TID. If we assume there is a vblank, then only 1 seed can generate the SID & TID: 0xc69e5f27 I think the community consensus was to prefer to flag these vblank splits for SID & TID save files, because more often than not, it's because the 'mon was manually created, rather than a save file lucked upon. Relevant source code in pokeruby, dug up via Copilot Chat: pokeruby/src/new_game.c at afcbea1f17d8c68b1aad22ab5ab1768cb5cf36d5 · pret/pokeruby
  23. Kaphotics
    Edit their flag in the pokedex
  24. Kaphotics
    The previous release had fixed the program to not decrease values that were above 999. Shortly after release, a fix was added to allow more than 3 digits to be entered. https://github.com/kwsch/PKHeX/commit/91ac18dd34cfa6871c5cafa0024629ed1102a72c The next release will be made available in the next few days along with the new Box Search feature, but if you cannot wait you can always try the Development build:
  25. Kaphotics
    PKHeX does not support ROM hacks.
×
×
  • Create New...