How to Read a Seed Result

The result is one structured record

A seed result combines a seed ID, map type, Nightlord, slot layout, and optional fields such as a special event or Old Gaol. The ID is the stable reference to include in links and bug reports. The map is a visualization of that record, not a live reading of the game currently running on your device.

The text summary below the map is intentionally derived from the same source record. It remains readable when scripts or map assets fail and makes it possible to verify that a shared URL opened the intended seed.

Read variants literally

POI variants are counted separately. A fire ruin and a poison ruin may occupy the same type of structure but are different matching values. Empty or unpopulated slots mean no POI value is assigned in the dataset; they do not prove that every non-seed-driven game element will be absent.

Event and Old Gaol fields are independent. “No special event recorded” is not the same statement as “nothing unusual can happen in this run.” It only describes the fields covered by the current seed record.

Use the map for decisions, not guarantees

A result can help you compare routes, locate recorded structures, and decide what to check next. It cannot guarantee player drops, dynamic invasions, or systems that are randomized outside the seed data. Patch changes can also make a known record stale.

For route planning, identify a small number of objectives and compare travel order yourself. The site exposes locations but does not currently prove that a route is mathematically optimal under every character, team, or circle condition.

Share enough context

A useful shared result includes the seed URL and the game version. When discussing a suspected error, name the exact slot and the observed POI variant. “The map is wrong” is hard to reproduce; “seed 123, slot 8 shows a fire ruin but the record shows poison on version X” is actionable.