Kaphotics

Use the latest posted release, and make sure you have .NET 4.6 installed.

It gives you the user config path at the start of the exception details. C:\Users\Jack\AppData\Local\ProjectPokémon\PKHeX.exe_Url_wxkwfewhdyfh5vv5bpmw1mqfcxiqswe5\1.0.0.0\user.config

The behavior has already been changed on the latest commits, wait for the next release.

Not going to add a feature, but it's easy to leverage PKHeX.Core to do things for you. string result; foreach (var file in SaveUtil.getSavesFromFolder(path)) SaveUtil.getVariantSAV(File.ReadAllBytes(file)).dumpBoxes(path, out result); Feed a path to it and it'll get all the save file paths, then dump every single one's boxes to the same path.

The property is not modifiable directly, but it's "IsShiny".

>using the Database Search advanced filters

Tools->Search Settings->Advanced Search Filter syntax/arguments are the same as the Batch Editor.

False positive for your antivirus, just restore & exclude. I'm sure many other people could chime in saying there's nothing malicious about the application; the source code is freely available for anyone to compile too.

Select the cells you want to export and press ctrl-c. It'll let you export with markdown formatting. You can always hide columns (right click) as well as prune the list by using the Database Search advanced filters to filter for a single box.

Incorrect, PKHeX allows you to dump all of your boxes via Tools->Data. Can do the same for loading a folder too; dex entries are updated unless you disable Modify Pokedex in Options-> Set to SAV.

Resolved via private message; file was empty (0 bytes). New check added for too-small sizes. https://github.com/kwsch/PKHeX/commit/f860bd31c7b564be3445ef3f7fcbbe8b7f64ae28

PM the save file

yes, fixed https://github.com/kwsch/PKHeX/commit/925a720b4c9e84a33e8dd1dea30d08c4e30edb3d

PKHeX does not check legality of Gen1->Gen7 pkm beyond the transfer changes that are made by Pokémon Bank. In other words, Moves are not checked for 1->7 pkm at this time.

PKHeX does not check item legality.

Oops, nevermind. Was fixed 4 days ago: https://github.com/kwsch/PKHeX/commit/eecb9094a806c61084dc1f29ffd27b1b1b44e941 Just wait for the next release; am currently working on RBY legality checks.

Be sure you are using the latest version posted on the forums. This was fixed 7 days ago, and is in the latest release as of 6 days ago.

"New Update Available!"

Recompile after inserting the following line after "Loading = false;" in the SAV_Trainer7.cs file: Clipboard.SetText(string.Join(Environment.NewLine, Enumerable.Range(0, 199).Select(x => SAV.getRecord(x)))); Upon opening the Trainer Info form, the program will fetch all 200 records and set them to your clipboard, ready to paste anywhere.

tl;dr - is it possible without shortcuts? no: illegal. There's a difference between abusing quirks (RNG) and causing normally unavailable quirks (glitch) and then abusing the glitch. Glitches are not part of the intended game design, thus never legal (in the eyes of the official legality checker). Corrupting memory to trigger an unavailable/custom encounter is not legal. Encounter must be available without glitches. Corrupting memory to replace data on an existing pkm is not legal. Data replacement must be available without glitches. Examples: Semi-legit: Tweaking (glitch) to encounter the ingame Darkrai; no shortcuts were used during the current play session (soft reset after arriving), and the encounter is normally obtainable without shortcuts (event distribution). Semi-legit: Hacking in the event item of a released event; again, no shortcuts were used during the current play session and the encounter is normally obtainable without shortcuts (event distribution). Illegal: For the flute Arceus, encounter is only available via setup shortcuts. Illegal: Encounter / setup is not available without glitches/cheats. Rage glitch, ACE, etc. In the diagram posted by theSlayer, naturally and shortcuts are key words when determining legal/legit/illegal. Causing the game to behave unnaturally is not legal

Why ask before trying the latest release?

The green highlight indicates who the current handler is. The past gen OT can't be the current handler because the pokemon was transferred to another generation (thus no longer handled by the OT, as he's stuck in the past).

For X/Y, the games use your PSS icon instead. Hence why it is only enabled for OR/AS saves. It'll be hidden in future releases to avoid confusion.

PKHeX does not support save states; export backup memory to obtain either the .dsv or .sav file.