Data Methodology

What is in the current dataset

The current snapshot contains 520 seed records across 6 map types and 9,741 populated point-of-interest placements. Of those records, 250 include a named special event and 0 carry the Old Gaol flag. The site currently labels this snapshot for game version 1.03.2.

Each record has a seed ID, map type, Nightlord, and a slot-to-POI mapping. Some records also include a special event, Old Gaol flag, marker data, or coordinates. A blank slot means the source record does not assign a POI there; it must not automatically be interpreted as a claim that no dynamic activity can occur at that position.

Sources and attribution

The project combines community-contributed structured data with observations that can be checked during normal play. The foundational map and seed work is credited to thefifthmatt, with Great Hollow and related DLC material credited to kevins78. Nightreign Seed Finder transforms those records into the interactive matching interface; it does not present Artimuz as the original discoverer of every seed.

The website running in a visitor's browser does not access or modify the game process, memory, or files. That statement is separate from the provenance of the reference dataset: community research may include analysis of structured game data as well as in-game observation. This distinction is important and replaces the broader, inaccurate claim that every value came only from what the site itself observed.

Transformation and matching

1. Source values are normalized into stable map, Nightlord, event, slot, and POI identifiers.
2. Choosing a map and optional Nightlord creates the initial set of compatible seed records.
3. Every POI mark is compared with the value stored for that slot. Records with conflicting values are removed; an unmarked slot does not remove anything.
4. When one candidate remains, the result view loads that record's full layout. If several remain, the useful next action is to mark a slot whose possible values differ between candidates.

This is deterministic filtering over the available dataset, not a confidence model that can repair an incorrect observation. If a church is marked as a fort, the correct seed may be filtered out. The finder therefore favors a few high-confidence marks over filling every visible slot quickly.

How checks and corrections work

A record can be checked by comparing the result layout with the corresponding in-game run. Reports sent through the site include enough context for Artimuz to locate the affected flow; reporters should also provide the seed ID, map type, slot, expected POI, observed POI, and game version whenever possible.

Reports are reviewed as discrepancies, not automatically accepted as corrections. Common causes include selecting an adjacent slot, confusing an elemental POI variant, using data after a game patch, or an actual source-record error. Confirmed changes should be documented in the public update history.

Probability limitations

Percentages on the event-hunting page are descriptive proportions within the records being compared. For example, an event appearing in 4 of 20 compatible records is displayed as 20%. That does not prove the game selects those 20 records with equal probability. Reliable real-world odds would require a sufficiently large, independently collected sample of actual runs and knowledge of the game's selection rules.

Base-game and all-content views also use different denominators. A higher percentage in a smaller group can be useful for choosing a hunt configuration, but small samples are volatile. The page displays matching-seed counts alongside percentages so the denominator remains visible.

Known limits

• A game update can make a previously correct record stale until the dataset is reviewed.
• Random systems outside the seed record cannot be predicted by this finder.
• Missing source fields are shown as unknown or not recorded, rather than silently inferred.
• A result is only as reliable as the user's map type, Nightlord, and POI selections.
• Counts describe this dataset; they are not a substitute for official game documentation.