Troubleshooting a Wrong Seed Result

Separate identification errors from data errors

Two different things go wrong here, and they need different evidence. Either the seed that opened is not the one you were in, which is an identification error, or the seed is right and one of its details does not match the run, which is a data error. For the first, keep the marks you made. For the second, keep the seed ID and the exact field that differs.

An identification error does not arrive as an error message. The builder only ever offers values that exist in a seed still standing, so a misread icon takes you to a real record rather than to a dead end, and the result looks as ordinary as any other. When something feels off, check map type and Nightlord first: they filter the most records, and a wrong one makes every correct POI mark point somewhere else. Then review the last location you selected, especially where nearby icons overlap or a variant is hard to read.

When one result looks plausible but is wrong

Compare the result’s map type, Nightlord, event, and two distinctive POIs with the run. If the identity is wrong, return to the builder and mark a location that differs between the plausible candidates. If you suspect one of your own marks instead, correct that mark rather than piling more on top of it: a location can be reopened and changed at any point, and everything else you marked stays where it is. If the identity is right but one POI differs, note that as a field-level discrepancy.

After a game patch, test whether several locations changed together. A cluster of differences may indicate that the dataset snapshot needs review for the new version rather than one isolated typo.

One more case looks like a field-level discrepancy and is not. A seed record describes what a seed contains; it does not promise that every recorded element behaves the same way in every run. Reports about an event that failed to appear usually belong here. Seed 1034 is the standing example: a player marked the Day 1 circle and two buildings and asked why the Day 1 Balancers Raid never fired. The record does say that seed carries the event; whether it fires in a given run is not something a seed record can tell you.

Build a reproducible report

Include seed URL or ID, map type, Nightlord, game version, affected location, value shown, value observed, and the steps used to identify the seed. Add a screenshot only when it makes the location or variant clearer. Never include passwords, payment details, or unrelated personal data.

• Use the footer Report button for product or data issues.
• Describe one discrepancy per field when possible.
• Say whether the problem repeats in another run.
• Mention whether minimalist mode, ad blocking, or script blocking affected the interface.