Find the reference that answers your next question: a Gym's position in the story, a dual-type matchup, an EV calculation, a code requirement, or the status of a Roblox link.
Need the third Gym or the full order? Open Gym progression.
Need to check your team's weaknesses? Open the Team Builder, then use Type Coverage to understand the result.
Need to calculate remaining training? Open the EV Calculator. For terminology and input limits, read EV and IV training.
Need a reward or a game link? Use Codes and badge requirements for published code records, and Status for the separately checked Roblox destinations.
The Codes page groups its existing records by reported Gym or Champion requirements. Its filters describe progression gates; they do not prove that a code works in your current upload.
A code claim, the number of badges you own and the availability of the game are different checks. A loading problem does not establish that a code has expired.
The eight-Gym overview brings the documented order, city, leader, type and objective into one table. Its earlier source date remains visible because a navigation update is not a replay of every battle.
For a path that remains closed, the progression reference separates badge gates, story triggers, traversal requirements and missed interactions. It is a diagnostic reference, not proof that every re-upload has identical story rules.
The Team Builder checks selected type combinations. It does not choose available Pokémon or read their actual moves.
Type Coverage explains why two types can create a weakness, resistance, neutral result or immunity. The EV Calculator performs training arithmetic only after a current EV, target and gain have been supplied.
No. This site is fan-made. Its source policy separates page observations, publisher reports, historical records and unconfirmed claims.
No. It links the references and tools currently available on this site. It does not promise a complete current Pokédex, spawn table or drop-rate database.
Each date belongs to its own evidence. A new tool explanation does not revalidate an older Gym roster or legendary route. Read the note on the destination page.
Compare the video's publication date and game identity with the source note on the guide. Do not transplant a route, code or mechanic from another Brick Bronze project. Use Status to check recorded game identities and Sources to understand unresolved differences.
Read dual-type multipliers, shared weaknesses and six worked examples before interpreting a team score.
Separate current EVs, targets, assumed yields and multipliers before planning repetitions.
Check badge, story, traversal and interaction conditions when a documented route appears blocked.
