When this guide is useful

Jokes of the Gods works best when planned as a level 12 side quest Windrose topic. Treat it as a planned check after the basic loop is stable, not as something to force the moment its name appears.

At level 12, it belongs in a planned midgame check rather than a casual opening errand. Stabilize repairs, reserves, and return timing before folding it into a serious run.

  • Decide whether the topic is a route, system, gear, resource, or encounter problem.
  • Use the name only as orientation; the advice should stand on its own.
  • When real runs change the picture, update the preparation rule, supply floor, and retreat condition.

Recommended preparation route

Jokes of the Gods 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. Use a short route to learn whether the failure point is enemy pressure, a quest gate, supply drain, or bad return timing 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; leave when food, repairs, or ammunition drops below the floor.

What to record after a run

If the route touches Jokes of the Gods, side quest, Tumbaga Ingots, Gold Ingots, Cursed Swamp, note how those objects connect to route risk, material planning, enemies, or rewards so the next run improves for a concrete reason.

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.

Future updates should add player decisions, route risk, failure fixes, and preparation checks. Details belong in the body only when they reduce the cost of a failed run or make the next attempt clearer.