ViolentSpatula

Yeah, I have no way to test the KeyBV side of the program. I thought I had traced everything back, but obviously I left something out. >.>

I'll try it. In the meantime, if you're using my preview version, {46} should show the form number.

Fixed ("Fixed" is relative) preview version of KeySAV with Box view! Download Please notify me of any bugs~ [Edit] The file has changed, this is a new (ish) version.

Each slot has to have been empty, had one pokemon, then have had a differnt pokemon in it before the encryption is broken for that slot. The "~" shows that those conditions haven't been met.

I've got a working fix for the corrupt slot issue, and I've got the box view almost complete. To fix a corrupt slot, open box view, navigate to the box with the offending slot, then right click the slot and select "Force Key Purge." After a prompt it will purge the slot and you will have to break the slot again, it's important that the slot sees an empty slot, and two different pokémon (other than the one that caused the issue in the first place). Here's a preview version for anyone interested. [Edit]: download removed, see later post.

Until either Kaphotics or I have a fix, what you probably want to do is take out the offending pokémon and re-break all your boxes. That's what I did and that's how I ended up with only one slot with this issue. I'm not sure about this, but I think that this pokémon has to be in save1 when you first hit the break button for this issue to occur. But, like I said, I don't know about that one, but I'm sure I moved that meowstic all over my boxes and no others had this issue. Maybe it only has to be the first pokémon seen.

Yes, but I've found that every time the "corrupt pokémon," that I coded simple workarounds for, will save in the key making that slot impossible to break. I've been trying to follow the code to provide a fix, but I still don't know how it happens. I wasn't aware of the issue until I added a box view, where the problem becomes quite apparent. I've been trying to code an option to flush the slot, but having only taken a Java 1 class makes it a little difficult. It would be a "fix" as long as the slot was then seen with two different pokémon and not the one with corrupt data. More on the corrupt pokémon: It seems that randomly, before the slot's encryption is broken completely, a pokémon's data will not be able to be read. This usually takes the form of otlanguage being 0, but sometimes moves are replaced with higher than usual numbers. This makes them easy to ignore and not show in dumpPKX_SAV, but I don't know where the pkx file is getting corrupted. On top of that, I don't know how it's getting through verifyCHK as I thought this issue would be a result of bit shift or null areas in the pkx. However, as soon as the slot is 100%, the pokémon's data is correctly shown, and it causes no further issues within broken slots (obviously as they don't save to the key). Example: Like your issue, I've got ONE slot that was filled with a meowstic (with seemingly fine data, but it must be corrupted in an area that is not shown) that will not break, no matter how many pokémon or empty slots are put there. If I put an empty slot there, it will show the ~meowstic, if it's the meowstic it also shows ~meowstic, any other pokémon shows nothing ("Locked Slot"). This one slot is bothersome, but easily ignored because it happened in box 22. I've been trying to flush the data out of the key, but I can't find the appropriate time to do it where it will save to the key.

With the powersaves you can delete all pokémon in box one, so if you put all the eggs in box one you can delete them.

Glad to see you got it working! ^-^

It looks like you haven't broken your encryption for the game.

The corruption isn't on your save, don't worry about that. It happens when the program isn't 100% sure what pokémon is in a slot, typically when it tries to ghost a pokémon in an empty slot. Usually it just puts what was previously in the slot, but it seems like rarely some of the data will get garbled and show odd values. I haven't followed the error all the way back, so I'm uncertain the cause, but it doesn't seem to be more than a slight bother. If you've seen the three states (empty, filled 1, filled 2) on a slot, this won't happen to that slot. I'm here to help, if you have any more bugs/feature requests, tell me!

Update 8/2/2014: -Fixes error caused by numbers greater than 618 in data.move and data.eggmove. Download Here!

I see that the error's coming from an egg in box 17, but I can't follow it any farther than that at the moment because of my computer problems. I'll look for a solution to the error as soon as I can. It doesn't seem to be an issue with formatting, as I can see all the metadata clearly. Edit: Seems to be a problem with eggmove 4. Can you tell me what moves they were bred with? Edit Edit: Found the issue! It does have to do with data randomly corrupting! The program thinks that the pokemon in box 17, position 5,3 has an egg move of 7673. I'll release a fix to my version shortly!

Yeah, that's probably what happened then. If it hasn't seen three states for each position it ouputs the ~ before the slot and can fill it with a pokemon that simply isn't there. Sometimes when this happens the data of one of the uncertain pokemon is corrupted slightly which might have caused your error. If the error happens again feel free to post the files!

If you downloaded it from the first post, and not my build (ViolentSpatula), then I have no idea why it would cause an out of bounds error. If you could upload your save1, save2, and save that you're opening I'll try and recreate the error later. (when I fix my operating system). Does the error happen in every formatting style?