Kaphotics

pkNX edits a folder that contains a ROM dump. Any files that are changed from the ROM dump are stored in the ROM dump's folder, inside a 16-digit folder (ROM's Title ID). This Title ID folder is what you copy to your console, and the console's layeredfs feature will load the files from that folder instead of the cart/SD when requested by the game. When loading files to edit, pkNX checks the Title ID folder to see if the file has been edited. If it exists, it loads it, otherwise, it reads it from the unmodified romfs. When you wish to revert modifications completely, you go into the Title ID folder and delete the modded files, so that pkNX loads from the unmodified romfs. When the files are deleted, the modded files will be gone, and you should be seeing unmodified data in-game and in the editor. If you are seeing randomized data in a fresh ROM dump, then you either didn't open the correct ROM dump folder, or you pirated a pre-modded ROM. Neither of which are issues with pkNX. pkNX does not load data that does not exist. It is up to you to ensure you are copying files and managing mods correctly; pkNX is just a program that loads data from where it is told to load from, same as the console.

PKHeX does not support ROM Hacks that modify the save file structure, or change things significantly from the base game.

Delete the layered FS folders on both your console and pkNX's local folder.

Yes.

It's in the tutorials and guide. Randomization of PID is a single command.

Depends. Things like exclusive tutor and level up moves that require the Pokemon to level up / evolve will require a higher level prior to transfer. Same for Gen1/2. Can always brute force the lowest possible value yourself.

There are 4 markings for early formats and 6 markings in more recent games. Keep looking.

Refer to the batch editor guides on how to find property names that you can use. All 6 that you listed are not in the list of properties. There's one property that starts with Mark***** that should be obvious how to set.

G-Max moves are not storable moves, see the Bulbapedia link. Entirely separate handling by the game.

Z-Moves and Dynamax Moves are hidden from the legal move list dropdowns as they are not valid out-of-battle moves to know. Google is your friend: https://bulbapedia.bulbagarden.net/wiki/List_of_moves

The entity db setting for Use Tabs as Criteria can be turned off, or you can pick a random nature in the editor then view the template.

Pokewalker PIDs are deterministic. Gender Ratio+Nature+TID/SID => PID. They're always going to be the same if the inputs (above) are the same.

PKHeX uses the 3DS wordfilter. When trading, it would have its nickname reset and the OT changed to a version-specific bland name. Just because you understand a word as being tame does not mean it isn't foul per Nintendo's standards. https://bulbapedia.bulbagarden.net/wiki/List_of_censored_words_(Generation_V) It is my choice to use the 3DS wordfilter for all games, instead of no wordfilter or spending time reverse engineering wordfilters for every game. Better to use the most aggressive one for all so that cross-game transfer issues will be known ahead of time.

Educate yourself on how ball inheritance works. The parent of the same species lineage has to already be in that ball. If you cannot capture a fuecoco in a beast ball, then you cannot breed one to have one either.

PKHeX doesn't do anything special with your keyboard. Try restarting your computer.

It's fine, just an error in PKHeX's checking logic. Will be fixed in future updates.

You do not need to compile plugins in order to use them. They're usually posted as releases (dll files) somewhere. You don't need plugins to solve legality issues. Use the encounter database built in to PKHeX. If you don't know if a value can be legally changed, change one thing at a time and update the legality check.

Use the encounter database.

Like every other person who has asked about powersave backups, they are useless without the original cartridge because they are still encrypted with cart-specific data.

The program already indicates in the legality analysis which form it will evolve to, just like it does for Wurmple. There are batch editor commands to set a specific EC modulo, but keep in mind that the user should still understand how the entity data determines the result.

This is not something a save editor can do. Hacked raids/rewards gets your console banned, see the hacked raids from SW/SH.

Again, evolutions for that species are predetermined, thus there's nothing you can do in-game to influence it for one you already have. The value that predetermines it is the Encryption Constant. Similar situation as Toxtricity, that has nature determine how it evolves; Maushold and Dudunsparce evolve based on the EC%100==0 check.

Working as intended. Evolutions for that species are predetermined, so if it cannot naturally evolve into its current state, it must have originated as its current state, not the pre evolution.

Set the pokemon back from the editor tabs, into the box/party.

You cannot nickname anything with fateful encounter.