sumo

Thank you so much for taking care of this! I've been a huge admirer of yours for a while, and I recently started dabbling in game analysis myself. Every day I'm reminded of just how incredible you are.

Hello, When loading a BDSP save file and accessing the Encounter Database, searching for Arceus (493) with the Version filter set to [b]"Any"[/b] causes the Search button to gray out indefinitely. It doesn't even show the standard [i]"No results found!"[/i] message. However, if the Version filter is explicitly set to [b]"BD/SP"[/b] or corresponding BDSP versions (instead of "Any"), Arceus successfully appears in the search results without any issues. [b][color=#42A5F5][Technical Details & Root Cause][/color][/b] After looking into the source code ([i]master[/i] branch), I noticed the reason why the UI freezes instead of throwing an error: [list=1] [*]In [font=courier][color=#EF5350]SAV_Encounters.cs[/color][/font], the [font=courier][color=#EF5350]B_Search_Click[/color][/font] method has an empty [b]catch[/b] block that silences exceptions, but it lacks a [b]finally[/b] block to restore the UI state. [*]When the Version is set to [font=courier]Any[/font], [font=courier][color=#EF5350]settings.GetVersions(SAV)[/color][/font] likely expands in a way that causes an exception downstream in [font=courier][color=#EF5350]GetAllSpeciesFormEncounters[/color][/font] or [font=courier][color=#EF5350]GetEncounters[/color][/font] (perhaps an unhandled Gen8b template context). [*]Because the exception is swallowed by the empty [font=courier]catch { }[/font] block, the code never reaches [font=courier][color=#EF5350]B_Search.Enabled = true;[/color][/font]. As a result, the Search button remains permanently disabled. [/list] Adding a [b]finally[/b] block there would easily fix the UI freeze, but could you also look into the actual exception happening during the "Any" search for BDSP saves? Thanks!

Thank you for the quick and clear explanation on the regular PID reroll button!As a follow-up, for shiny Pokmon (especially wild encounters in Scarlet/Violet), when I use the Ctrl + Star icon button instead: 1 Does this generate a PID that fully replicates the games actual wild shiny RNG (e.g., for non-Tera Raid encounters like overworld grass or outbreaks)? Or is it a simplified method (e.g., just calculating a TSV/FSV-compatible PID)? 2 Whats the exact behavior of this button in the latest PKHeX? Does it take into account the current IVs, Nature, EC, Gender, or Form to ensure legitimacy, or is it independent/random like the regular PID reroll? 3 For best practices to keep wild shiny edits 100% legal: ・ Should I always reroll PID after setting IVs/Nature/EC? ・ Any specific order or additional steps (e.g., re-reroll EC afterward) to match game data perfectly? ・ Does the Legality Checker automatically validate these shiny PIDs under Wild Encounter template? Id love any code references or tips for batch editing multiple shinies too. Thanks again!

Hello, I've been using PKHeX for many years now — thank you so much for the continuous development and updates!When editing wild Pokémon in Pokémon Scarlet/Violet, I usually follow this order: Randomize IVs → Set Nature → Reroll EC → Reroll PID (For shiny versions, I use Ctrl + the star icon instead of the regular PID reroll button.)My understanding is that the PID Reroll button automatically calculates a new PID based on the current IVs and Nature (to try to keep them consistent where possible). Is this correct? Or does it simply generate a completely random PID string without taking the current IVs/Nature into account?I'd really appreciate it if someone could explain the exact current behavior/specification of the PID Reroll button in the latest version of PKHeX. Thank you very much in advance!

Thank you for your reply. However, I was able to exchange the newly created Rayquaza (OT: Nobunaga) in PKHeX when I changed the SCALE to 64. Is this a new law? There seems to be a misunderstanding because I only included the necessary information. I did not try to exchange with others, but exchanged between my accounts for verification. I apologize if I have caused any discomfort...

This text was translated by Deepl Sorry if there are parts that are not translated. OT:Nobunaga TID:03172's Rayquaza created in PKHeX could not be exchanged on Pokémon SV. I moved and compared several legitimate individuals and it seems that it has something to do with HEIGHT and SCALE. The height(scale) that I was able to exchange correctly on SV is 64, 74, and 128 were identified. I hope this will be helpful.