Kaisonic

I noticed that a couple columns in the Box Data Report are incorrect: OTLang DSRegionID The problem is the resource files have a header line as well as ID,Name for each line. This is fine for the UI since it's loaded with getUnsortedCBList, but InitializeStrings loads "languages" and "regions3ds" with getSimpleStringList, which causes those columns in the Box Data Report to be off by one index (DSRegionID is off by one, but OTLang happens to be correct most of the time just because the line numbers happen to match up with their IDs) as well as showing superfluous data ("1,Americas (NA/SA)" instead of just "Americas (NA/SA)"). Also, the position column is 0-indexed, so the Pokemon in Position B26:02 is in box 27, slot 3, which seems a bit counter-intuitive. Also also, as a completely separate question, would you be opposed to me adding the data formatting functionality of my version of KeySAV2 as a separate tool in PkHex? A couple people have asked me to add support for injectiondebug.bin, pcdata.bin, etc in KeySAV2 so they can make Reddit threads using the web injection method instead of save decrypting (and so cartridge users can do entire boxes instead of battle videos), but since PkHex already opens these files, it seems more effective to just add more text exporting options to PkHex (some users might find it helpful anyway). I'm thinking of making it just a menu option (like Tools -> Create Formatted Text from Box Data or something), and a window pops up that looks basically like the options tab of KeySAV2. Is that a good idea, or would you rather me just add support for the new bin files in KeySAV2? Thanks for all you do :-)

But what's the need for dumping battle videos if you can already dump Pokemon? If you mean for checking someone else's shiny values, it's probably faster to trade, dump the Pokemon, then trade back. That way you can do as many as you want at a time, and don't have to worry about hatching, battling, and resetting.

You can just email them, I'll PM you my email address. Do you get the error with both the official build and my build? Edit: For future reference, he was mistakenly trying to open the key file instead of a save file.

It happens when you try to load a save into the "Break" section, right? Does it also happen if you use my build? It's possible Datel changed how their saves are - can you send me the saves you're getting errors with so I can look at them?

How are you getting your saves? PowerSaves, digital, etc. And it's only your AS saves? You can still break with your Y saves?

Haven't had the time yet :-( if/when I do, I'll definitely post it on my GitHub so you can follow along :-D

Datel does not allow edited save resigning, so there will never be PowerSaves support. Someone would have to figure out how to resign saves themselves without the PowerSaves software.

From the PKHex thread: You can also use KeySAV2 to dump pk6 files, then load those into PKHex for viewing (however it doesn't retain box positions).

Just use Cyber Gadget to make save backups and follow this guide to break your save: http://www.reddit.com/r/SVExchange/comments/2nun41/new_keysav2_build_with_more_features_that_does/ That guide works with the official version. Also it doesn't have to be a .sav file, I believe it takes .bin files too; whatever Cyber Gadget outputs will work.

Haha no worries :-) I see where the confusion came from now, and you're right - most of PkHex is useless with encrypted saves, since you'd only be able to see Pokemon details and nothing else. Until perhaps someone figures out how to read other info from an encrypted save, but that's way over my head But in the meantime, if we add export options to PkHex, it's only a hop and a skip to add reading Pokemon from encrypted saves.

I don't think I entirely follow you here. Are you saying you'd want to open an encrypted save AND a decrypted save? PkHex is generally for opening one save at a time - adding the KeySAV2 dump functionality would simply allow users to open encrypted saves in PkHex in a read-only state. If you want to copy Pokemon from an encrypted save to a decrypted save, there are other methods that are already used by users that want to copy Pokemon between the decrypted saves that PkHex can already open.

Yeah I gotcha. But if we're taking the export functions from KeySAV and putting them in PkHex, and then taking the box view functions from PkHex and putting them in KeySAV, it might just be easier to combine them rather than cross-manage the code. Or, to look at it another way, once the export functions are implemented into PkHex (box selection, Reddit formatting, CSV formatting, etc), the ONLY unique function of KeySAV is breaking the encryption of encrypted saves. So if you add that last part to PkHex as well, you've got an all-in-one tool. And I like all-in-one tools :-D

But the point of combining KeySAV2 and PkHex (other than giving current PkHex users export options) is so users that only have encrypted saves are able to use PkHex to view their Pokemon. I guess I'm not completely following your last post :-/

All the source code is on Kaphotics' GitHub if you want to get an idea of what everything looks like :-) https://github.com/kwsch And then my modified version: https://github.com/Kaisonic/KeySAV2

I was thinking about that the other day. It'd be a two-step process to combine KeySAV2 and PkHex: - Add the save-breaking from KeySAV2 so PkHex could open encrypted saves, allowing the user to view boxes and Pokemon like they can now with decrypted saves (equivalent workflow now is to export pk6 files with KeySAV2 and open that folder in PkHex, but that doesn't retain box position) - Add the output formatting to PkHex, like reddit and CSV formatting - this would be useful not only for KeySAV2 users, but also for anyone that uses PkHex and just wants to export their Pokemon information in different ways. This reminds me of ViolentSpatula's version - he added the box view from PkHex to KeySAV2, which I thought was cool, but the source code wasn't in his GitHub :-( I'll have to take a crack at this if I get the time :-)

Sounds like you're following the original KeySAV tutorial. Try following this guide instead: http://www.reddit.com/r/SVExchange/comments/2nun41/new_keysav2_build_with_more_features_that_does/ You don't need Cu3PO42's build, that guide works for the official version too.

It's my understanding that Gateway can fully decrypt saves, and that's how PkHex can do anything with them. It's likely they've only figured out how to re-encrypt stuff that they need to decrypt to do the things PowerSaves does. So while the save file we see is encrypted, the program decrypts the file, applies the code, then re-encrypts the file without the user knowing. Otherwise, if the program decrypted the save completely, users would think they could do whatever they want with PkHex and then have PowerSaves re-encrypt the save for actual use, which it can't (yet).

Short answer: No. KeySAV2 is for reading data from saves and battle videos. It cannot edit data because it brute-forces decryption and cannot re-encrypt anything; data goes from game to KeySAV2, and that's it. It's really just for ESV and IV checking; it doesn't (can't) write anything back to the save file. It's useful for those of us that don't have any extra hardware other than just a stock fully-updated 3DS and 6th gen Pokemon game.

Hey guys, just added some more stuff to my KeySAV2 build. Here's the link to download it, and here's the changelog: KeySAV2 1.3.6 (2014-12-14) - CSV output file name now defaults to name of the SAV or BV you've opened - Fixed: IV counter shows "1 IVs" - Fixed: hatched date for eggs is "2000-00-00" - Added: "Steps to Hatch" column for eggs - Added: "Reset to Default" button for CSV custom output KeySAV2 1.3.5 (2014-12-07) - Added columns: OT gender, met level, OT friendship, OT affection - Fixed newlines and file paths for better compatibility

On your SD card, go in to the Nintendo 3DS folder, then in the alphanumerical folder, then another one, then for OR, it is title\00040000\0011C400\data, for AS, it is \title\00040000\0011C500\data. So, for example, your Omega Ruby save would be E:\Nintendo 3DS\*\*\title\00040000\0011c400\data\00000001.sav Assuming your SD card is drive E, and those two asterisks are a bunch of letters and digits.

TL;DR version: Download KeySAV2 1.3.4 Unofficial (updated 2014-12-07), lots of features, double-saving not required, X/Y/OR/AS supported, details below! Hi everyone! I just wanted to thank Kaphotics for his awesome work! I really liked ViolentSpatula's version (with the added information in the CSV export) but it didn't support Omega Ruby and Alpha Sapphire. So, being a programmer, I decided to try and add ORAS support to this version. I got a little carried away, and ended up merging the official version by Kaphotics and the added-feature version by VioletSpatula, along with adding a few of my own features. Around the same time, I noticed Cu3PO42 on this subreddit making their own version with even MORE features. So I decided to combine them all! Here's the thread of Cu3PO42's version, along with a full guide of how to use the program: http://www.reddit.com/r/SVExchange/comments/2nun41/new_keysav2_build_with_more_features_that_does/ And finally, you can download my version 1.3.4 here. I'm calling it KeySAV2 1.3 (edit: updated to 1.3.4, details below). Also, here is my own thread on that subreddit. My version contains all changes to the official version as of now, all changes in Cu3PO42's version as of now, all additions by me (Kaisonic), and all additions by ViolentSpatula (except the awesome stuff in their preview version, like the box view. If you're still around, I'd love the source code for that :-D). Here's my full changelog: KeySAV2 1.3 * Added available columns: Level, Region, Country, Held Item, Language, Game, Number, PID, Mark, Dex Number, Form * Fixed "mark" - pentagon mark is now present for all Pokemon created in generation 6 * Fixed "Number" column to be 1-indexed * Fixed help box to be resizable and able to be kept open while working in the main window * Added ORAS game support for "Game" and "Region" values * Fixed superfluous spaces in CSV data * Added perfect IV marker columns * Added perfect IV counter column * Added IV and EV sum columns * Changed pk6 file output to be in box order rather than species order (for better PkHex support) * Code refactoring (combined dumpPKX_BV and dumpPKX_SAV) * Added option to show ESV for hatched Pokemon * Added option to enclose trainer and Pokemon nicknames in quotes for CSV exports (to prevent problems with commas in either) And you can download the source or contribute on my newly-created GitHub! Download and use away! Let me know if you find any bugs or want to suggest any changes! KeySAV2 1.3.2 -Added "Egg Received" and "Met/Hatched" columns KeySAV2 1.3.3 - Removed legacy save breaking behavior option (confusing and unnecessary) - Fixed output text box extending beyond window - Remove unstable key-breaking code - Changed CSV custom to allow custom formats - Show headers once if "Split Boxes" is not checked - Use "Box" instead of just "B" for headers - Fixed brackets for ESV appearing in CSV data - Added columns: experience - Added translations for "Game" and "Region" columns ("Country" is still English for all) KeySAV2 1.3.4 - Fixed "Backup SAV" button size - Fixed empty first line in text output if "Split Boxes" was checked - Added more descriptive headers ("All Boxes", "Boxes 1-4", etc) - Fixed shiny star appearing for eggs (it is now a checkmark, like it should be) - Fixed Unown forms (will now show as "Unown-A", "Unown-D", "Unown-!", etc) - Added a column for number in the dump (just goes from 1 to number of Pokemon dumped) - Added Pokerus status columns (Infected and Cured) - Re-ordered default CSV custom columns to make a little more sense - To reset your CSV custom format, erase the format from the text box, switch to another format, then switch back to CSV custom and the default will be filled in - This default is just a specific order of ALL available columns - This does NOT effect the "CSV default" option, so any program that parses the standard CSV output from this program will still work! - README.txt file with changelog and full guide now included - More code refactoring