Steam confirms a first-Shiny capture achievement, so Shiny Stackmon are real collection targets. It does not publish encounter odds, route boosts or a complete visual-identification rule in the checked official material. This guide therefore focuses on a repeatable player test rather than a fabricated percentage.
Player answer
Quick answer
Choose one repeatable encounter source, keep the route and build constant, record every attempt, and only call a result Shiny when the current game identifies it—not because a color looks unusual in a compressed image.
Fix one route or source and record the build.
Log attempts and the game’s visible variant label.
Separate Shiny captures from Foil captures and Foil creation.
Current limit: Official Shiny odds, boosts, reroll rules, visual markers and optimal routes are not published in the checked sources.
The official field guide UI shows discovered records, silhouettes and a Neutral tab. The screenshot is not used to claim a complete roster. Official Steam store screenshot
Start with the only confirmed Shiny milestone
The public Steam achievement Shiny Tracker requires capturing a first Shiny Stackmon. That confirms the target and the relevant action—capture—but it does not reveal whether every encounter source can produce one or whether odds vary.
Keep Shiny and Foil records separate
Steam names Shiny Tracker, Foil Chaser and Foil Creator as separate achievements. Use separate columns for Shiny encounters, Foil encounters and created Foils. Combining them would hide whether a method actually affects one variant or another.
Run one controlled route
Pick one wild encounter source or other current-build source, note the route, creature pool and session start time, then avoid changing equipment, progression state or game version during the sample. A mixed route can produce a large attempt count that answers no clear question.
Log evidence, not only successes
For each attempt, record the sequential number, creature name, source, visible variant wording and result. Save a screenshot of the first confirmed Shiny and its in-game identifier. Failed attempts matter because they define the denominator of your personal sample.
Do not publish a universal odds claim from a small sample
A personal run can show that a method worked once; it cannot establish the game-wide probability without a sufficiently large, controlled sample and stable build. Report “1 result in my recorded attempts” instead of converting it into official odds.
Recheck after every patch
If the developer changes encounter pools, booster contents or variant systems, begin a new version-labeled sample. Do not append post-patch attempts to an older dataset as though the probability were unchanged.
