Thanks, fixed in latest commit:
https://github.com/kwsch/PKHeX/commit/9da1913f1b0771278653c556899653d88c57e56b
(the Static Encounter IV checking is new as of yesterday)
Open a new Windows Explorer view (Windows Key + E), and enter "%TEMP%" (no quotes) into the search bar and press enter. You can probably delete all the files there (or maybe just run ccleaner or another cleaning utility). Basically pk3DS tries to get a temporary file location, but the random file it gets is already used (failing).
As usual, loading something to tabs and calling it to check legality will end up re saving the data, which includes updating the catch rate if it is atypical.
Check the legality from the box, don't load to tabs.
Normal cartridges always yield static encounters with Method 1. Emulators do not faithfully emulate, resulting in atypical PID methods.
Since these PIDIVs are not possible on regular cartridges, the pkm is not legal. Just because you emulate the game doesn't mean you're emulating it 100% accurately.
PKHeX is working as intended.
There is not a way to select by a pkm's typing, or to filter by {is any of the following values}.
You can always move them to a box manually, then filter for that box prior to running your modifications.
Nobody has done the research on how to edit that.
Can't just wave a magic wand to get something implemented.
Save editing research belongs in another subforum.
Already reported & fixed, will be resolved in the next release:
https://github.com/kwsch/PKHeX/commit/afe16dd1a7012011d2236c2fa5bf55587ec25b3b#diff-666c51398fd0f3c609db54ad1c6ab126
Lua parser for b2w2:
you'd have to mess around with where it's reading from. script editing in gen4/5 isn't as fully fleshed out as it is for generation 2/3 games.
it's much easier to start by following the insertion/editing tutorial videos I've posted to get familiar with the process, then start tinkering with the tools to understand how they really work.
Implementation in PKHeX comes after a potential feature is sufficiently researched.
Per the stickies:
This forum section is NOT for requesting save editing research. Please use the Save Research & Development subforum.