Kaphotics

The save file will be saved to your SD card, all you have to do is access your SD contents on your computer and load the "main" file into PKHeX. You'll be able to do all the edits that are possible (same as Cyber Saves), which includes Wondercard Injection and other save edits (map position).

It would help if you could upload the [Details] to Pastebin so that I can see what is triggering the error. Be sure you are using the most up to date PKHeX; there was a new version posted today.I am unable to reproduce your error on my end. Try saving it to another place as the SD might be write protected (switch)?

Yes.

8/8/15 - New Update: - Added: Korean Translation. Thanks cocoblue! - Added: Can now copy current moves to Relearn Moves by clicking on the Current Moves groupBox. - Fixed: Showdown Import made a little more flexible for non-exported sets (ie, user created with mistakes). Thanks Favna! - Fixed: Showdown Import now recogizes even more edge cases. Thanks Odaxis! - Fixed: Fill Dex now doesn't error out. Thanks ShaKage! - Fixed: Characteristics should now display properly for all cases. Thanks fcugqx! - Changed: The program now keeps track of the current box to mimic the ingame box system. Thanks codemonkey85! - Fixed: Saving the current box will no longer cause black screens when saving on the Party / Battle Box tab. Thanks RustInPeace!

Did you save your savefile in PKHeX while looking at the Party/Battle Box Tab? Try re-saving with the latest commit. (it might also be worth finding out what exiting the PC ingame @ the battle box as the current view will save that byte at; open your save in HxD and go to that offset)

No idea right now. I did check on my own bank of saves and I saw that 0x483F got altered when the file was loaded, but the checksum calculation worked correctly. That'd be what is causing the 0C block to show up as bad (still have to figure out what is causing that change). (edit: this won't have any bearing and was related to loading a save and showing the current box where something failed) Try transplanting data from other backups to see what area of the save is the troublemaker. Edit2: Was that 0x483F set to 0x1F? Might be the reason why (ie, last used the PC on a non1-31 box and exited, ie battle box?) I just committed a would-be fix so that the checksum error won't appear and the &0x1F is really using a signed byte instead (to indicate battle box). If that doesn't work, maybe keeping it below 0x1F might be the fix...

Which is in the Box Name / Background / Unlock flag section. Did you make any modifications in the past to that section? I'll keep looking.. Might be worth trying to re-save the file, and comparing the differences.

Please do a bunch of tests; edit on both variants of the program with the same changes to see if there's any byte difference on the output save file.

Fixed the EV chopping in latest commit. Thanks for reporting!

Depends if you can find it reliably in the RAM and if it's stored completely in RAM.

Ah, I understand now. The answer would be no; if there's no way to pass files via upload/download then there's no way to retrieve enough contents from battle videos. Something that has not been investigated is dumping RAM while watching a battle video... Gen V had the entire video sitting in RAM so maybe that will allow you to rip out the instructions/teams/seeds to transplant into another video.

You can use a similar method to the one that KeyBV uses to decrypt battle videos: Person X: Person who can decrypt Person Y: Person who can't but is passing videos Person X downloads a battle video and decrypts it. Person Y downloads same battle video and grabs the encrypted file from the SD. Person X pads the file with Zeroes at the beginning of the file so that it matches the length of Person Y's file. Xor the two files together to obtain Person Y's Xorpad for that video slot. Person Y deletes battle video, records new one. Person Y extracts the data, xors the xorpad over and trims to the original decrypted size. Person X inserts with SDF after making modifications. === Won't work for live tournament videos and all of this can be avoided if Person Y just uploads the video for Person X to download. If you're just downloading battle videos, the replay will play back from the POV of the person who recorded it... so I don't really get what you're trying to do.

http://projectpokemon.org/forums/showthread.php?46695-Filling-Dex-Not-solved-What-am-I-doing-wrong

You can edit text/description in the Game Text editor. I prefer to keep text editing separate from other gamedata edits. Since sprite editing is more computation heavy, it's not done within pk3DS; you can use the Misc Tools to unpack garcs->bclim sprites.

rom edits, obviously.

The exploit depends on the two digits after the firmware, not the firmware being 9.0-9.5. (has to be 20 thru 22) If it's not, then the exploit will not work for you.

Fixed in latest commit. Thanks for reporting!

Use rxTools and emunand and do not exceed 9.2 firmware.

When the flag is set it prevents the Deoxys NPC from appearing; just continue as usual.

pgf is a wondercard gift file that must be inserted into save files and received in a DS game. PKHeX does not support past gen gift files as they are not directly translatable to gen6 data.

Tweaked the Trainer Randomization window to instead have a comboBox for one of the three options: 0 - Don't Modify (everything stays as is) 1 - Randomize All (all moves get randomized) 2 - Use Levelup Only (no trainer will have custom moves, will instead use the species' levelup tables) preview pic

No. Event flags/constants usage is different between games, resulting in a severely messed up overworld if you inject to the wrong game.

It is known that ram2sav will not work on the latest updates. Since you are on fw 9.2.0, please use SaveDataFiler instead of ram2sav.

You'd have to PM me the save.

Bred pokemon from generation 3 show up as unknown because Legal does not know how to check them. Legal does not work for generation 5 format pkm files.