When this guide is useful
Ruby is commonly shown as a 資源 Windrose topic on public pages. Treat it as a planned check after the basic loop is stable, not as something to force the moment its name appears.
Public page fields frame it as a 資源, so this page starts with route thinking, preparation rules, and run notes until real attempts support a deeper walkthrough.
- Decide whether the topic is a route, system, gear, resource, or encounter problem.
- Use the public name and category only as orientation; the advice should stand on its own.
- When real runs change the picture, update the decision rule before adding more detail.
Recommended preparation route
Ruby should be approached by reducing the cost of first contact. Make the first trip a light scout run that checks approach risk, supply drain, and the retreat point; use the second trip for required materials or combat supplies. A failed first attempt is still useful if it produces clear route information.
If you cannot explain how the run might fail, do not carry rare materials yet. Confirm the hazard profile with a short route before turning it into a committed attempt.
- Use the first run to confirm the route, not to force completion.
- Bring required materials, combat supplies, or quest items only on the second run.
- Write the retreat point before departure so greed does not make the route longer.
What to record after a run
Current related objects include ルビー, 資源. After a real attempt, record how those objects connect to route risk, material planning, enemies, or rewards instead of turning them into fixed coordinates too early.
A useful guide should answer four practical questions: when to go, what to bring, what to change after failure, and how the topic connects to resources, ships, bosses, or beginner routing.
When to revisit this guide
Recheck this guide whenever a patch changes level, reward, approach route, enemy pressure, or required materials. Small changes should update the checklist first; larger changes can justify a more detailed walkthrough.
Manual review should add player decisions, route risk, and preparation checks. Details belong in the body only when they reduce the cost of a failed run or make the next attempt clearer.