A save-safe Roria Conquest legendary and mythical hunt checklist organized by encounter category, without claiming an exhaustive current roster.
Separate your hunt into static encounters, roaming encounters, Raid Dens, event or code-linked rewards, and unresolved community entries. Save before a rare encounter when possible, carry enough capture and recovery resources, and confirm each location in the live game before checking it off.
Use this checklist before committing time, rewards, or a rare encounter.
Each step narrows the next decision and leaves room for changes in a live Roblox game.
Start with static, roaming, Raid Den, event or code-linked, or unresolved. This prevents you from applying the capture routine for one category to another system with different access rules.
Use the community guide to identify the reported area or trigger, then compare it with your story progress and available field moves. The live game prompt is decisive when a prerequisite changed.
Save before the encounter when the game permits it. Bring capture items, recovery, and a team that can manage the attempt without depending on an unconfirmed exact moveset.
If the encounter does not appear, record route, badge count, story state, and date. Do not turn a missing spawn into a statement that the Pokemon was removed or the entire game is broken.
Mark the result as caught, seen, attempted, blocked, or not checked. A category checklist stays useful even when the community roster is incomplete or a limited event ends.
Recheck story flags, route, required field move, event timing, and whether the entry is roaming or den-based.
Use your recent save if the game permits, then review supplies and the capture plan before another attempt.
The community guide is broad but this launch does not certify every current legendary and mythical.
Limited encounters and rewards need a current date and live check.
Rare encounters deserve a save-safety step before travel or interaction.
Community material is useful for task details, while the live game remains decisive when a menu, location, or requirement changes.
Short answers for the most common follow-ups.
The linked community guide is the broadest checked reference, but this page does not certify it as an exhaustive current roster.
Some collection paths may involve dens; treat that as a separate category and confirm the live encounter.
Yes, when the game permits it, especially before rare or one-time-feeling interactions.
Story state, field moves, event timing, route errors, or a different encounter category may explain it.
Move from reading to a concrete code, planning, training, or collection task.
