Switch Side-Game Guidelines


This page contains information and examples for how to create proof for your Pokémon in Brilliant Diamond/Shining Pearl, Let's Go Pikachu/Eevee & Legends: Arceus to an acceptable standard for general trading in PS! Wi-Fi. Proofing instructions for any Switch game not listed on this page can be found by clicking the button below.

Important Information:
Proofing Tips:

In most cases, video proof is required for Pokémon obtained in Switch games. For this reason it is important to gain a good understanding of how Switch video capture works before attempting to prove a Pokémon to avoid creating a proof album that is invalid.

Holding down the Screenshot button for 1-2 seconds will record the previous 30 seconds of gameplay footage. This will be saved to the console SD card if there is one present. This means you should hold the Screenshot button after viewing the summary pages of your Pokémon to capture the correct 30 seconds of gameplay.

Also make sure to check out the list of untradable Pokémon to ensure that your Pokémon can be traded inside the Wi-Fi room to begin with.


IV Judge:

We advise unlocking the IV judge function before attempting to prove a Pokémon, this is the strongest and most effective method of proving the IVs in-game.

  1. In Brilliant Diamond/Shining Pearl, the judge function is unlocked after speaking to an NPC at the Battle Tower.
  2. In Let's Go, the judge function is unlocked after obtaining 30 species on the Pokédex, then talking to the professors assistant near Vermillion city.
  3. In Legends: Arceus, the judge function does not exist. An IV value of 31 is represented by an effort level value of 3 after initial capture.

IV Judge Alternatives:

CFW Alternatives:
  • 3rd party reader applications.
  • Examples Include: Encounter bots, Overlay outputs.
Vanilla Alternatives:
  • Showdown! Teambuilder output.
  • Online IV calculator.
  • Pokemon HOME IV Judge (for proving 0 & 30 IVs for PLA mons only)
  • When using either of these methods the IVs must be exact values or the proof will be considered invalid. Leveling your Pokémon to 100 using candies will provide the exact IV values.

Click here for a tutorial on proofing in Switch main series titles! (SwSh | ScVi)

Overall Proof Requirement


Pokémon that meet the description of anything listed inside each of the boxes below require proof to trade inside the PS! Wi-Fi room, no exceptions.

All Side Games (BDSP | LGPE | PLA):

Obtained from Wild/Static/Chaining/Outbreaks:

Encounters with 0 guaranteed IVs
  • 3 IV+ shiny Pokémon
  • 4 IV+ non-shiny Pokémon
  • Wild shiny Legendary birds from overworld-based encounters in LGPE
  • Flawless Legendary and Mythical Pokémon obtained in Legends: Arceus.
  • RNG abused Pokémon that qualify for the Jumbo/Teensy mark in Scarlet/Violet.
Encounters with 3+ guaranteed IVs
  • 5 IV+ shiny Pokémon
  • 6 IV non-shiny Pokémon
RNG abused Pokémon that qualify for Jumbo/Teensy mark require proof regardless of the amount of guaranteed IVs.

Obtained from event distributions:

Distributions with 0 guaranteed IVs
  • 4 IV+ non-shiny/shiny Pokémon
Distributions with 3 guaranteed IVs
  • 6 IV non-shiny/shiny Pokémon
  • Flawless Shiny & Non-Shiny Pokémon
Evemt Distributions with fixed IV/Nature values, such as the VGC player events do not need proof.


BDSP Proofing


This section covers how to create proof for Pokémon obtained in Brilliant Diamond/Shining Pearl. In all cases, your PS! Username must be visible somewhere within your proof link so that we can easily verify exactly where the Pokémon has come from.

All Encounter Types:

For VIDEO proofing you must provide:

  • A consistent video of a successful capture or redemption leading into in-box IV evaluation and summary screens, enough to clearly show OT/TID and nature of the Pokémon you caught.
  • For PokéRadar chains, you must provide an additional screenshot of the chain length as displayed on the Pokétch app.
  • If the result was achieved by RNG abuse or botting, you must provide an additional screenshot of the tool output (e.g PokéFinder/SysBot). Sensitive information can be partially blurred on every screenshot (no more than half!) .
  • Your Pokémon must be clearly identifiable with no ambiguity whatsoever. It is advised to clear a space in your party or send your Pokémon to an empty box to avoid ambiguity.

All encounters - The video should start before the battle has ended (i.e the Pokémon was caught! screen or similar).

Gift redemptions - The video should clearly show a successful redemption (i.e the You recieved a Pokémon! screen or similar).
Video Examples:

For CFW IMAGE proofing you must provide:

  • For Wild encounters - Provide an in-battle screenshot with the Overlays page open, clearly displaying the IVs, EC and PID of the Pokémon.
  • For Gift redemptions - Provide a screenshot of the Pokédex popup with the Overlays page open, clearly displaying the IVs, EC and PID of the Pokémon.
  • In any case - Provide a screenshot of the OT/TID summary page with the Overlays page open showing the same information.
  • For PokéRadar chains, you must provide an additional screenshot of the chain length as displayed on the Pokétch app.
  • If the result was achieved by RNG abuse or botting, you must provide an additional screenshot of the tool output (e.g PokéFinder/SysBot). Sensitive information can be partially blurred on every screenshot (no more than half!)
Image Examples:

Mystery Gift Redemptions:

You must provide:

  • A consistent video of a successful redemption showing a valid code has been used, leading into in-box IV evaluation, enough to clearly show IVs/Nature.
  • Alternatively, you can provide a picture of the redemption screen showing a valid code has been used, along with a picture clearly displaying the IVs/Nature of the redeemed Pokémon.
  • If CFW Overlays were used to achieve a result, you must provide a screenshot of the redemption screen with the overlay output visible. Sensitive information can be partially blurred on every screenshot (no more than half!)
  • In any case, if the Pokémon takes the OT/TID of the player, you must provide a picture of your trainer card & summary screen of the Pokémon to prove that the trainer information is a match.
  • For the BDSP Manaphy egg specifically, you must provide an uncut video of the egg hatching, leading into IV judge evaluation and showing the summary pages. (It's possible to save before hatching the egg!)
  • If the result was achieved by RNG abuse or botting, you must provide an additional screenshot of the tool output (e.g PokéFinder/SysBot). Sensitive information can be partially blurred on every screenshot (no more than half!) .

Your PS! Username must be present regardless of the method used, if you are using a series of images, a paper slip must be on display with your PS! Username written on it. This means you will need to use an external camera.

If you use the video proofing or CFW overlays, you may use watermarks instead of a paper slip to display your PS! Username.
Examples:


LGPE Proofing


This section of the page covers how to create proof for Pokémon obtained in Let's Go! Pikachu/Eevee. In all cases, your PS! Username must be visible somewhere within your proof link so that we can easily verify exactly where the Pokémon has come from.

All Encounter Types:

You must provide:

  • A consistent video of a successful capture leading into in-box IV evaluation and summary screens, enough to clearly show OT/TID and nature.
  • Your Pokémon must be clearly identifiable with no ambiguity whatsoever. It is advised to clear a space in your party or send your Pokémon to an empty box to avoid ambiguity.
  • For Overworld Legendary Birds, you must provide an additional video of the initial encounter clearly showing a shiny bird in the overworld.
  • If the result was achieved by botting, you must provide an additional screenshot of the tool output (e.g SysBot). Sensitive information can be partially blurred on every screenshot (no more than half!) .

Overworld/Legendary encounters - The video should start before the battle has ended (i.e the Pokémon was caught! screen or similar).

Gift redemptions - The video should clearly show a successful redemption (i.e the You recieved a Pokémon! screen or similar).
Examples:

Mystery Gift Redemptions:

You must provide:

  • A consistent video of a successful redemption showing a valid code has been used, leading into in-box IV evaluation, enough to clearly show IVs/Nature.
  • Alternatively, you can provide a picture of the redemption screen showing a valid code has been used, along with a picture clearly displaying the IVs/Nature of the redeemed Pokémon.
  • In both cases, if the Pokémon takes the OT/TID of the player, you must provide a picture of your trainer card & summary screen of the Pokémon to prove that the trainer information is a match.
  • Your Pokémon must be clearly identifiable with no ambiguity whatsoever. It is advised to clear a space in your party or send your Pokémon to an empty box to avoid ambiguity.

Your PS! Username must be present regardless of the method used, if you are using a series of images, a paper slip must be on display with your PS! Username written on it. This means you will need to use an external camera.

If you use the video proofing method you may use watermarks instead of a paper slip to display your PS! Username.
Examples:


Legends: Arceus Proofing


This section of the page covers how to create proof for Pokémon obtained in Legends: Arceus. In all cases, your PS! Username must be visible somewhere within your proof link so that we can easily verify exactly where the Pokémon has come from.

All Encounter Types:

You must provide:

  • A consistent video of a successful capture leading into summary screens, enough to clearly show OT/TID, nature & effort level values.
  • Your Pokémon must be clearly identifiable with no ambiguity whatsoever. It is advised to clear a space in your party because of the lack of a remote box system.
  • If the result was achieved by RNG abuse or botting, you must provide an additional screenshot of the tool output (e.g PokéFinder/SysBot). Sensitive information can be partially blurred on every screenshot (no more than half!) .
  • In the case you can't definitively prove the IVs from the effort level values alone, a screenshot of the mon in Pokemon HOME with it's Judge function showing them must be included.

Overworld/Legendary encounters - The video should start before the battle has ended (i.e the Pokémon was caught! screen or capture pop-up).

Legendary encounters with cutscene - The video should start at any point during the cutscene and should capture all of the appropriate information.

Gift redemptions - The video should clearly show a successful redemption (i.e the You recieved a Pokémon! screen or similar).
Examples:

Mystery Gift Redemptions:

You must provide:

  • A consistent video of a successful redemption showing a valid code has been used, leading into sumamry screens, enough to clearly show Nature & effort level values.
  • Alternatively, you can provide a picture of the redemption screen showing a valid code has been used, along with a picture clearly displaying the effort level values of the redeemed Pokémon.
  • In both cases, if the Pokémon takes the OT/TID of the player, you must provide a picture of your trainer card & summary screen of the Pokémon to prove that the trainer information is a match.
  • Your Pokémon must be clearly identifiable with no ambiguity whatsoever. It is advised to clear a space in your party or send your Pokémon to an empty box to avoid ambiguity.
  • In the case you can't definitively prove the IVs from the effort level values alone, a screenshot of the mon in Pokemon HOME with it's Judge function showing them must be included.

Your PS! Username must be present regardless of the method used, if you are using a series of images, a paper slip must be on display with your PS! Username written on it. This means you will need to use an external camera.

If you use the video proofing method you may use watermarks instead of a paper slip to display your PS! Username.
Examples:

I'm done reading this! Send me back to the main page!