Pokemon Job
Explain whether the Pokemon is used for gathering, movement, support, durability, or habitat setup. Avoid claiming it is the best unless there is verified evidence.
Pokopia Build Planning Standards
A practical framework for team roles, habitats, recipes, route evidence, and internal links.
Build Workflow
Home design ideasStart With a Route, Not a Ranking
Home design ideas
Use text-based layout concepts for cozy bases, visitor courtyards, recipe workshops, and showcase-ready route notes.
Progression build
Use this path when the goal is safer unlocks, cleaner habitat scouting, and fewer wasted recipe attempts.
Farming build
Use this path when the route already works and the next question is how to repeat rare checks more efficiently.
Hard route build
Use this path when damage alone is not enough and the route needs survival, timing, and role coverage.
What a Build Page Should Include
Habitat Match
List the habitats, weather notes, resource goals, and unlock assumptions that make the build useful.
Recipe Window
Describe when a recipe or buff is worth using, then link to the recipe page for ingredients and duration.
Current Editorial Standards
- Do not publish fake player names, fake screenshots, fake performance numbers, or unverifiable ranked-table claims.
- Label database-based advice as editorial until it is confirmed by official sources or tested player evidence.
- Link every build note to related Pokemon, habitats, recipes, and official context pages.
- Record the review date so readers know whether the page may need rechecking after updates.
Build Review Checklist
Source or Test Basis
A build should say whether it comes from official information, site database planning, or repeated player testing.
When It Breaks
Strong build notes explain the matchups, weather, missing food, or route conditions that make the build unreliable.
Internal Links
Every build should point readers to Pokemon pages, habitat pages, recipe pages, and relevant guides for verification.