This page will cover how to verify a proof album. If you are unfamiliar with checking proof albums to ensure they are valid for trading inside the room, this is the place to be. We will dissect multiple different proof albums from different encounter types to give a detailed explination on how to properly verify each one.
It is important to understand the destinction between Retail, CFW & Emulator albums, as the requirements will change based on the tools at the users disposal.
Obtainment Type | Description |
---|---|
Retail | Performed on official hardware with no aids (overlays & scripts) to help with the obtainment process. |
CFW | Performed on official hardware running Custom Firmware, may come with aids such as overlays to help with the obtainment process. |
Emulator | Performed using a PC using official games, typically comes with aids such as overlays or lua scripts to help with the obtainment process. |
Firstly, you will need to identify the following information:
These questions can be answered by looking at a proof album. For example, if a player has taken a picture or video of their console, and there are no visible overlays on-screen, we can safely assume this was achieved on a retail device.
Figure 1 - Identifying the type of encounterWe are able to quickly identify that this is a wild encounter (Unown) from a DS game (Gen 4) that was RNG abused on an emulator. We can tell that this was achieved using an emulator due to the visible lua scripts/overlays on the bottom of the DS screen.
The above mentioned questions now have answers, it's time to head over to the relevant page on the proof guidelines. In this example we will be visiting the DS page of the proof guidelines as this was achieved on a DS title. We now need to ensure that the album we are looking at contains all of the required information listed on the guidelines page.
Figure 2 - Verifying the albumBased on the Gen 4 guidelines found on the DS page, a wild encounter achieved on an emulator using RNG abuse is required to have:
The guideline does not ask for anything else, which means that we have now identified that this proof album contains all the details we need to see. Finally, we need to ensure that the details from the RNG abuse screenshot match the details shown on the emulator screenshots.
Figure 3 - Matching RNG tool informationWe can see that the initial seed of the emulator and the RNG tool screenshot both begin with F300
, and that the frame count is also a match (frame 12), this is enough proof to indicate that the Pokemon was encountered on the correct frame.
In the in-battle screenshots, we can see that the PID matches what is displayed on the RNG tool screenshot as well, the PID begins with C167
on both screenshots, and the IV/Nature combination is a perfect match (Timid 31/31/31/30/31/31)!
We have sucessfully verified that all of the details of this proof album are in order! You can use the skills you have learned from following this guide to verify any proof album that comes your way.
Here you can find different flawed proof albums, if you would like to sharpen your proof checking skills try to work out what is missing in each of these albums without viewing the answer first!
Use the checking method explained above to determine which portion of each of these albums is missing (if anything):
Test 1 - GBA Static EncounterAnswer - Seed (Sensitive information) is entirely blurred.
Test 2 - 3DS Mystery GiftAnswer - A required screenshot is missing (immediately after redemption screenshot).
Test 3 - DS Mystery GiftAnswer - PS! Username is not present at all.
Test 4 - 3DS Static EncounterAnswer - RNG tool screenshots do not match game screenshots, seeds are incorrect.