Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 09/09/21 in all areas

  1. Not a bug; PKHeX just prevents you from toggling the Captured/Defeated state back to any of the not-presented states because a simple ComboBox does not handle the changes required to set the requested not-roamed or roaming state. // CurrentStat:ComboboxSource // Not roamed: Not roamed/Defeated/Captured // Roaming: Roaming/Defeated/Captured // Defeated: Defeated/Captured // Captured: Defeated/Captured // Top 2 bit acts as flags of some sorts for (int i = 0; i < cbr.Length; i++) { int c = SAV.Data[ofsRoamer + 0x2E + i]; var states = GetStates(); if (states.All(z => z.Value != c)) states.Add(new ComboItem($"Unknown (0x{c:X2})", c)); cbr[i].Items.Clear(); cbr[i].InitializeBinding(); cbr[i].DataSource = new BindingSource(states.Where(v => v.Value >= 2 || v.Value == c).ToList(), null);
    1 point
  2. @Spica unlike gen 4 RAM gen 5 RAM doesn’t store much of the enemy Pokémon data unencrypted. The complete Pokémon is encrypted so you’ll need to decrypt then first to have it in a readable format. The tool @theSLAYER linked you to will help you if you’re wanting the current Pokémon on the screen, but if you’re needing the info for scripting reasons then this post of mine might give you a little more information
    1 point
  3. It's probably stored as a full encrypted Pokemon file (an ek5). So if you already know where the PID is, just rip out the section (the size of an ek5), save it as a ek5, and see if PKHeX would read it. Also, this tool rips out all pkx in your ram (if you need it):
    1 point
×
×
  • Create New...