Base-Game vs DLC Seed Data

The scopes answer different questions

A base-game view asks which combinations are available without DLC-specific records. An all-content view includes the later records and DLC Nightlords, so it has a different candidate pool. Neither scope is inherently more accurate; each is appropriate for a different player setup.

The current dataset uses lower-numbered base-game records and later DLC records, but the interface should remain the authority for which entries are included. Avoid deriving ownership or availability from a seed ID without checking the selected scope.

Map distribution is not uniform

The six map types do not all contain the same number of records. A raw event count can therefore favor a map simply because that map has more known seeds. The event-hunting table normalizes within a comparison group, but the underlying count should still be considered.

The same applies to Nightlords. If a Nightlord-map pair has a small candidate set, one event record can produce a high percentage. Compare both the numerator and denominator before choosing it.

Choose the correct view before optimizing

If you do not own or do not want to use DLC content, stay with the base-game recommendation. If every map and Nightlord is available, the all-content view can surface combinations absent from the smaller scope. Do not combine a numerator from one view with the denominator from the other.

• Confirm content ownership and selected Nightlord.
• Read the map type and matching-seed count.
• Treat percentages as dataset proportions.
• Recheck the page after a dataset or game-version update.

How updates can change the comparison

Adding records can lower a percentage even when no existing event entry was removed, because the denominator grew. Correcting a mislabeled event can move both numerator and ranking. For that reason, screenshots of old percentages should include their date and dataset version.