Kaphotics

I'm pretty sure the Resort slots show up in the Other tab, shouldn't need another tool to access their data.

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.

It's a checksum of the data.

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.

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.

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.

Try clicking on them.

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.

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.

The program already tells you the issue is with the Ball value. Use the GUI to change the ball value until it is fixed.

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.

Dump your save file correctly and do not rely on save states to track your progress. Save in-game and close the game to flush all changes.

Japanese games nicknaming set trash bytes differently than international games; this check has been updated on the latest commits: Revise trash check for Japanese nickname · kwsch/PKHeX@7617f6d Your examples are probably fine if checked on the latest dev build / next release.

The latest release is not a dll, it is an exe file. Not that it matters; you can acknowledge the security popup and run it anyway if you trust the source.