Encounter Troubleshooting (Retail)

This section covers how to troubleshoot encounters and delays. If you keep missing targets, spawning in the wrong Pokémon, or can't find your result on the RNG tool, this is the place to be.

Probable Causes:

There are three main reasons that you are missing your target frame, these are:

  1. Encountered the Pokémon too early or too late due to mistiming, or incorrect information was entered on the GUI.
  2. NPC count was incorrect, causing an unexpected Jump from menu close prediction.
  3. Delay was not properly accounted for, causing the wrong Pokémon to be generated.
Encounter Mistiming:

If you are consistently mistiming your encounters, the only thing you can do is keep re-timing and working out the exact frame you hit.

Ensure you have good positioning in-game and that your encounter filters have been filled out properly using Encounter Lookup, and try again.

For Symbol encounters specifically

Your KO Count must be correctly configured to march the Pokémon you are searching. For example:

  • We are hunting for Swablu, but instead find that a NidoranF was spawned.
  • For Swablu we have 500 KOs according to the Pokedex, but for NidoranF we only have 60.
  • When searching for NidoranF, we will need to change the KO Count value to 60 to find accurate results.
Incorrect NPC Count:

NPC count must be correct when using menu close prediction or you will not hit the expected result. It is important to learn how to calibrate your NPC count.

Detailed instructions for calculating NPC count properly can be found on the main page of this guide.

Incorrect Delay:

Having an incorrect delay will always spawn the incorrect Pokémon. In some cases, delay will be 0 and will not need to be calibrated.

If you are hitting incorrect results after testing, this may mean your delay is not 0 and will require calibration.

For example - If our delay is consistently 2, we will then aim to spawn the Pokemon 2 frames before the expected target frame to hit our result.

Information about troubleshooting delays can be found on the relevant page, (e.g troubleshooting static delays can be found on the Static Encounter RNG page).


Figure 1 - Delay Troubleshooting Example



We encountered an Aerodactyl, but it wasn't shiny! So what happened here? Well... We miscalculated. Let's try to find the frame we actually hit.

Figure 2 - Calculating IVs

Using the IV calculator we can find the rough IVs of the Aerodactyl we hit and use this information to locate the exact frame we landed on according to the generator.

Figure 3 - Finding Frame Hit

By doing a filterless search we can see the shiny cluster, and frame we hit was 1 frame behind where we wanted to be, oh well! We will adjust accordingly for next time by spawning it in the overworld 1 frame later.

That's all there is to it!

Send me back to the main page!