Jump to content

Kaphotics

Helpful Member
  • Posts

    7270
  • Joined

  • Last visited

  • Days Won

    361

Everything posted by Kaphotics

  1. Same issue as other threads that have been reported and fixed. Using the 0x1000 block layout of gen3 saves, I rearranged the order of blocks since it seems like the save writing was interrupted when overwriting the flash chip, so that each save (primary and main) has a complete set of save blocks, and re-exported from PKHeX. POKEMONE.SAV
  2. Open it in a hex editor and compare it to a valid working save file. If it is similar, you might be able to change it manually to get it to be recognized. Can't tell if you don't share the save file.
  3. If the story progression is misbehaving, then something you did to it would have "broken" progression. Whether it's impassible depends on what was messed up. If the save file restored without needing to be re saved in a save editor, then there was no external corruption.
  4. Shininess is determined from PID and trainer ID. Changing one, of course you're going to have issues especially if there is a PID/Trainer ID correlation for the encounter.
  5. Checksums are valid upon opening the save file. Modifying things like changing the box might not be tracked as "edited", but the checksum will no longer match what is expected since the save was truly modified.
  6. PKHeX is open source, read the source code or step through with a debugger if you must understand how it works. There's way too much to describe to waste time writing guides and wikis for every single file format and interaction. X/Y's format is described here, for both the raw save archive and main: https://projectpokemon.org/home/docs/gen-6/xy-save-structure-r82/
  7. PKHeX checks for more things than PKSM to give early warning of corruption, rather than just loading if the size is correct. Your save file's footer is invalid. Use a hex editor to copy the last 0x200 bytes from another working save file and replace your save file's last 0x200 bytes with it. Then, open and export with PKHeX. More specifically, offset 0x75E00 is expected to be "BEEF", while yours is 0 (uninitialized).
  8. If the checksums are valid in PKHeX, then it's likely you manually manipulated/restored an old file on the SD card directly. If you delete your save data and recreate it (on the 3DS), then restore your old save file (with homebrew) then it should work. The console has tamper protection, hence why you can't restore backups without homebrew.
  9. Raw files on the SD card are encrypted per-console and have their own file-structure. Hence why the size/filename is different. You need to use homebrew to access the "main" save file. You should never manually manipulate/use the files on the SD card.
  10. Use the command builder drop-down. You can require properties to be equal in order for them to be modified. Refer to the batch editor guide.
  11. You're using an older version, try checking the latest release.
  12. Please try to understand the limited amount of seeds and the statistical odds to get specific requests. 3 flawless IVs is 2^5^3, which is 2^15. 2^16/2^15 is approximately 2 results are expected to have 3IV. Choose a less limited encounter (like Japanese AGETO celebi, which is CXD type, or a Gen4 wobdercard) if IVs are a must.
  13. BACD-R means there are only 2^16 seeds (0000-FFFF) possible. Obtaining the IVs you requested is 2^25 odds. No surprise you can't find anything, because there aren't any seeds that give you good results. Pretty sure OT Gender is the recipient gender, hence why it's not flagging.
  14. HOME might permit it to be uploaded, but if it's inspected in HOME, I think it will lack the metadata that a legitimate GO Mon would normally have.
  15. If it originated from a game that needed to transfer through HOME to reach the game it is in (SWSH, so yes), then it won't be legal to upload into HOME. HOME expects it to have a tracker, which it does not have, so it will reject the upload. How to get around it? As stated in the linked thread, you can't for things originating from GO. The only way to get valid trackers is to start with something transferred from GO. For meltan, generate it in LGPE originating from GO Park complex, then connect that game to HOME.
  16. Handler: means what it says. Can't be handled by the OT because the OT is from GO.
  17. Try editing in another program like PokeGen before assuming a program is at fault. Usually it's you doing something wrong instead.
  18. Wow another thread with the same error message; please check for one.
  19. It's just the formal name for the left side of the main window You can open trash bytes by clicking inside the OT text box, or you can just click the "OT" label and it'll copy the OT Name (and trash bytes for Gen1/2) automatically.
  20. Simply changing your OT (manually by typing in a new OT/batch editor) isn't enough, as the game compares all 5 (jpn) / 7 (international) trainer name bytes even if they're unused. Looking at your Articuno's OT trash bytes, it's ALEX\50\50\50. Clicking on the OT label in PKHeX's entity editor GUI will copy the save file's OT trash bytes, resulting in ALEX\50\0\0, which is what the game is wanting when the OT details match. Seems like it applies to your party (besides Mewtwo) and Box 1.
  21. It means exactly what it says. If you open it in a hex editor to see what data is inside, it'll all be the same values over and over until the end of the file. It's like a word document filled with F. Is there an essay in the document? No, it's just repeating F's. What causes the save data to be empty? For Gen1/2 cartridges, the battery keeps the save file "alive", and when it dies, the data resets back to a default state. For later generations, they don't need a battery to retain data, but if you never save in-game to flush your progress to the save file (like using save states exclusively), then you'll never update your save data from the initial values it had. PKHeX is telling you "Please ensure it was properly saved". So, did you properly save your game?
  22. Probably a secondary error caused by the program not setting up correctly with error here: It might be because of a hash collision on the species name strings, but there aren't any duplicate strings/hashes. I find it odd that other linux users do not have the same issue as you... I checked on my windows machine and not a single string has the hashcode listed ^. It would be helpful to know which strings are coming up as duplicate, if you're able to debug the program for that. You might also try installing the latest version of Wine (development) which is 9.13 (you currently have a stable release of 9.3).
  23. Kaphotics

    Weird Error

    And what technology does Bottles use? Wine. If Bottles uses an old version of Wine (not supporting .NET 8 compatibility) then you need to update the version of wine it uses, or use wine directly without Bottles. This isn't an issue with PKHeX.
  24. Kaphotics

    Weird Error

    What operating system? If you are using wine to run Windows applications, be sure you are on the latest update of wine.
×
×
  • Create New...