Kaphotics

I've fixed this in the latest batch of commits; just need to see if there's anything else that can be fixed prior to uploading a hotfix.

Looks like invalid pkrs values. https://github.com/pret/pokeemerald/blob/5d7c438efcd341c777c866a7eb3f8401f8548dc5/src/pokemon.c#L6036-L6058 The byte at 0x44 has "01", which decomposes to "strain 0, days 1". Can't get strain 0, and when it's cured (days elapsed), it will never remember it had pkrs. I simulated the numbers to generate a list of possible PKRS values: https://github.com/pret/pokeemerald/blob/5d7c438efcd341c777c866a7eb3f8401f8548dc5/src/pokemon.c#L5940-L5978 var list = new List<int>(); for (int i = 0; i <= 255; i++) { var val = i; if ((val & 0x7) == 0) continue; if ((val & 0xF0) != 0) val &= 7; val |= (val << 4); val &= 0xF3; val++; $"{i:000}: {val:X2}".Dump(); list.Add(val); } list.OrderBy(z => z).Select(z => $"{z:X2}").Distinct().Dump(); And here is the list of initial values: 12 23 34 41 52 63 74 92 A3 B4 C1 D2 E3 F4 Note how strain 0 and strain 8 are not generatable. === Did you hack in PKRS with a cheat?

ty fixed: https://github.com/kwsch/PKHeX/commit/1acefbcf9310570a6faa55825101fd62d46bde6d

Open the decrypted data in a hex editor. It's empty data. Not a valid save file; working as intended.

The game might not use the old logic flags, or the flags are differently ordered? I dunno.

Fixed in latest commit; removed them from the legality lists. https://github.com/kwsch/PKHeX.EncounterSlotDumper/commit/6ad4416218885c935b1a7d1753f7455f9e3439a0 https://github.com/kwsch/PKHeX/commit/b36aa0ac99f2c31c5c76befbff332baf58e2fd73

It's an RNG seed. You can replace it with another RNG seed, or you can use the current seed value to predict what the result will be (using another, undeveloped tool).

Done!

PKHeX's pkm database allows you to toggle (dumped pkm) & (box data from saves). I know that OneDrive can also force keeping files locally, but you could temporarily download them and dump them. Or, you can change the behavior of LoadPKMSaves to use whatever keep-local folder(s) you want.

Not an issue with PKHeX.

Foreign Pokemon can't get the ribbon unless they're battle version is set. This is not the place to complain about your hacks being correctly flagged.

gee i wonder if you *really* can receive the ash greninja gift on US/UM?

Thanks, fixed in latest commit: https://github.com/kwsch/PKHeX/commit/332449f53d1dc7b982d71843479cf978531c0337 Use the dev build if this false flag bothers ya

Thanks for reporting; it's a regression. Egg moves for gen6+ have to be in the relearn moves list (unless it is a "shared" egg move via Gen8's mechanic, which this pk7 is not). I've been wanting to refactor the moveset validation for a while now... maybe soon It's now fixed in the development build; next release should be in the next day or so.

Read the stickied troubleshooting thread.

Do you even earn for playing the game? Personal enjoyment and sharing.

You can reuse the PKHeX.Core.dll in other projects; like uploading the save file to your website and reading the party data directly.

Why bother asking a hypothetical question if you haven't bothered checking the program?

Sure, dump the game from your legitimately purchased copy of the game via your hacked switch.

Just download one of their releases on GitHub.

Thanks for reporting, fixed in latest commit: https://github.com/kwsch/PKHeX/commit/6d0da504d5c416a5aa4104b1b586c194357bf2a6 Wasn't fun tracking it down, haha. Was probably a typo error in noting the location ID via numpad.

Modifying individual block flags is possible with the Block Data editor; there are thousands of possible flags to change, and localizing all of them for each supported language would be tedious. We have a guide on manually editing flags (which includes the Dynamax Adventures values): Clothing is again an issue with localization; having to detail what each piece of clothing is for each language is a large amount of bloat when 99% of users just want to "unlock all" clothing options. Unlocking all can be done by importing a block obtained from the forums. With each DLC / patch, the game may use more of the clothing bits, hence different possible bits. There's also the issue of legally-obtainable (gender-specific) clothes; having an editor with that metadata is a lot to manually document & maintain.

You can download the bleeding edge Development build for testing; for the latest release, you'd have to make sure there's a save in the first slot. Second slot was occupied

Thanks, I've made some alterations to the save handling for PBR to account for saves that have an empty save slot before a filled save slot (based on your provided save).

Regarding integrating plugins into the main branch, there's upsides and downsides. * Plugins can be updated independently of the main executable, and can be developed independently and with different coding styles the author is more comfortable with. * Plugins can use external dependencies or string resources, which may bloat the overall size of the executable. Most plugins are niche use, and majority of the users never use them. * More features added to PKHeX is more for me to maintain and clean. Not all implementations are reusable/extendable... If users ask about functionality of an editor that I didn't make or report a bug, it might not reach the original author for triage. * Most plugins don't document their code thoroughly, making maintenance / other-reader comprehension more difficult. * Plugins can act as a self-contained environment to play around & have others test, without needing the full executable. * Not everything has to be a plugin or integrated with the main program; they can be standalone editors as well that reuse the core-project for exposing the save file operations and game strings. * Different licensing being possible for plugins. Some people don't like GPLv3, or MIT. === * Dynamax Adventures plugin: makes flipping the dynamax adventure flags easier. Stock PKHeX can still toggle flags via the Block Editor, and you can automatically import a list of block names via the "SCBlocks.txt" feature. Most users don't need to reset event flags, when genning exists. * Clothing: allows individual clothing piece toggles; tons of names. Stock PKHeX can import and export the final block; most users don't need to customize individual flags. * Feebas: Most users don't need to calculate position, when genning exists. * Auto Legality: Relatively big project with its own dependencies; separate development that ties into Stock PKHeX. * Raid Plugin: Relatively big project with its own feature set. Separate development that ties into Stock PKHeX. PKHeX is a hobby project; there's always more PKHeX can do, but there's only a finite amount of development attention. There is no auto-updater; infrastructure for that would take time + money (bandwidth). Not really worth when PKHeX isn't monetized. There are plans for migrating away from WinForms to MAUI later this year; yielding native mobile/non-windows platform support. Less editors for me to port = less work for me to be stressed about. There are many other large(r) projects (like Notepad++) which have their own plugin system.