How to read and compare wiki data

Category pages are the main reference surface. They place entries in a consistent order and expose the fields that matter for that category, such as level, location, conditions, ingredients, growth time, or value. Use the table for comparison before opening an individual item.

An individual item page is a focused view of the same structured record. It is useful for sharing a direct link, but the category table provides more context when deciding which fish, bird, crop, recipe, or seasonal collectible to pursue.

Location, time, weather, level, and distance are separate constraints. A location match alone does not prove that an entry is currently available. Read all available conditions together, and remember that some labels cover several in-game time periods.

A missing value means that the site does not currently have a verified value for that field. It should not be interpreted as zero, always available, or not applicable unless the table explicitly says so.

Where the wiki shows star prices, the values are calculated from the category's known quality multiplier or stored directly when the category uses exceptional values. Compare the displayed result rather than assuming every category uses the same multiplier.

Game updates can change base prices, multipliers, ingredients, or unlock levels. The last verified table value is a reference, not a substitute for checking the current game client after a major patch.

A collection that represents an entire event, such as snow or sand sculptures, remains useful as an archive after the event ends. Event-only rows mixed into an evergreen category may instead be hidden when their active period ends so the main table remains practical.

Archived information is clearly separated from currently obtainable information wherever lifecycle data is available. The archive documents what existed; it does not promise that an item can still be collected.

The database combines structured observations, operator review, and community corrections. Names are localized independently from numeric properties so a translation fix does not rewrite the underlying values.

If you find an error, report the exact category, item, field, expected value, and game version or observation date. Specific corrections can be checked and applied much faster than a general note that a page is wrong.