Moonfrost Database

The Moonfrost Database is a lookup layer for named things: items and materials, recipes and workstations, fish and crops, and collection entries. It is deliberately a known-content index, not a claim that every record found in a supplied build is obtainable. Each useful entry needs a name, type, source or unlock, player use, AppID and branch scope, verification status, and a route to more detail when one exists.

Moonfrost entered Early Access only on October 12, 2026. Community data indexes already expose thousands of item and recipe records, but those records can include internal names, duplicates, development placeholders, old content, or entries with no public route. A file proves that data exists; a current quest, shop, drop, harvest, station, or observed inventory result proves that a player can obtain and use it.

Choose the right index

Use a guide page when the question is “How should I plan this activity?” Use the database when the question is “What is this named entity, where does it come from, and what uses it?” A fishing route belongs in Farming; the source and collection state of one fish belongs here. A Build Mode workflow belongs in Crafting; the recipe and placement role of one object belongs here.

Read verification labels before acting

“Official” means Steam, Oxalis Games, or an authored official announcement establishes the feature, scope, or entity. “Current community” means a same-game guide or observation identifies the item in the public Early Access experience. “Data-recorded” means a supplied build contains the record or relationship, but availability has not necessarily been observed. “Needs live confirmation” means the route, value, or current use cannot safely be stated.

The labels are about the claim, not the website. One page can contain an official system description, a current player-observed route, and a data-recorded recipe. Each field needs its own scope.

Use fields that answer a player question

An item entry should include the displayed name, aliases if needed, type, rarity only when shown, known source, main use, recipe relationships, quest or collection relevance, availability, AppID, branch, date, and detail link. A recipe entry should include the station, exact inputs and qualities, output and quantity, cost or time only when verified, unlock owner, and result availability.

A fish or crop entry needs the area or seed source, tool, growth or pool context, cooking and request uses, collection state, and version. A collection entry needs its album group, acquisition method, milestone or reward when confirmed, and a clear marker when the record is known but no player acquisition route has been verified.

Do not populate an unknown rarity with “Common,” an unknown location with the first area mentioned online, or an unknown unlock with a guessed level. Empty is more honest and more actionable than false precision.

A known-entity starting set

This set is intentionally small and mixed. It shows the evidence format without pretending to be the complete inventory. The Items Database expands the lookup method and gives a more detailed card index.

Avoid the most common database traps

Internal IDs are not player-facing names. Two IDs can represent variants, a placeholder can have a description, and a recipe can exist without an obtainable blueprint. A spawn record can name an area without showing whether story gates or tool tiers make it reachable. A collection record can exist even when one entry is deliberately excluded or inaccessible.

Old Alpha, Web3-era, and Demo data must not be merged silently into the October Early Access branch. The updated Demo can transfer progress to the paid game, but that does not make every older Demo value current. Related Soundtrack AppID 4791030 has no gameplay database role.

When two sources disagree, prefer a current in-game result for the public branch, then a dated official statement, then multiple current independent observations. Preserve the disagreement if it affects a player’s materials or time.

Submit a useful entity verification

For an item, capture its displayed name, description, icon context, inventory category, source action, quantity, and current use. For a recipe, capture the workstation, inputs, quality, output, unlock state, and result. For a fish or crop, capture the area, tool, conditions, and collection registration. Include AppID 2561630, the public branch, date, and enough surrounding UI to distinguish the record from a similarly named entity.

That evidence lets the index grow without copying proprietary tables or making unsupported completeness claims. For activity instructions, return to Farming, Crafting, or World. For version changes, use Updates.

Sources

• Moonfrost Steam store
• Walkthrough Forge Moonfrost guides
• Moonfrost Wiki browse index
• Moonfrost Wiki items index