Sources and Evidence Register

Moonlight Peaks Tools uses public sources to research game facts, then writes an original task-focused explanation or tool around the supported claims. A link in this register identifies evidence; it does not imply that the linked organization endorses this fan site.

Evidence labels

• Official identifies a statement made by the developer, publisher, or the platform responsible for the listing. It supports only what that source actually says and may still need a region, platform, edition, date, or patch boundary.
• Fixed community revision identifies a community-maintained page whose exact revision can be reopened. It is not relabelled as a developer guarantee.
• Corroborated editorial identifies a current secondary source used to check a gameplay observation or discrepancy. Its prose, images, maps, and article structure are not copied.
• Single report is a research lead, not a production default.
• Conflicting, partial, stale, unknown, and not reconfirmed expose limits rather than filling gaps with a guessed answer.

The site owner did not purchase or play the game for this launch, so none of these labels means “personally tested by us.” See Methodology for the full publication and conflict rules.

Official game and release sources

The following first-party and platform pages support the core identity and platform information:

• Official Moonlight Peaks website for the developer’s game overview and official destinations.
• Official press sheet for developer and press-kit context.
• Steam store listing for the Steam edition, supported operating systems, listed features, current regional store information, and Steam release metadata.
• Nintendo Switch listing for the US Switch edition and platform features.
• Nintendo Switch 2 Edition and Upgrade Pack for the separate Switch 2 purchase and upgrade path.
• Google Play listing for the Google Play release and the devices named on that store page.
• Marvelous USA launch information for the dated demo, edition, and launch-price announcement used as a snapshot.

Store prices, discounts, availability, file sizes, compatibility labels, and release metadata can change. The platforms page attaches a check date to those fields and directs visitors back to the live storefront before a purchase.

Patch and known-issue sources

The official July 9 known-issues notice supplies the selected issue list and the status stated on that date. Patch 1.1.38, published July 10, supplies its three direct fixes. The Marvelous USA July 15–16 patch page and Marvelous Europe counterpart supply the 1.1.41 and 1.1.44 changes and the stated Steam-first rollout. At the July 18 check, the USA version table listed Steam 1.1.44 while the Europe table still listed Steam 1.1.41; both listed Switch, Switch 2, and Google Play Games at 1.1.3. The site preserves that regional-source difference and does not infer a non-Steam rollout.

The site’s known-issues tracker does not treat a similar-sounding patch item as an exact match when its platform or location scope differs. It also separates an announced Switch or Google Play fix from a confirmed live rollout. The tracker was last checked against the official Steam feed and both regional publisher pages on July 18, 2026 UTC.

The official support instructions are linked from the known-issues page. That support channel belongs to the game publisher, not this fan site.

Fixed community revisions used in public tools

The Copper material formulas use the community-maintained Farm Helpers revision 7995. Its complete Furnace section was rechecked against revision 9018 on July 17, 2026 and was unchanged. The calculator keeps the fixed revision visible, does not claim an official developer recipe, and excludes the processing-time fields that remain unknown.

The eight visible Death gift rows use Death revision 4660, checked July 13, 2026. The subset is deliberately non-exhaustive. Rows with additional independent support are labelled separately from rows supported only by the fixed community revision.

The character directory uses NPCs revision 9581, checked July 18, 2026, for its dated roster and category snapshot. The Death profile uses Death revision 8498 for dateability, pronouns, and the stated Net and Soul Blob milestones. These are fixed community revisions, not developer guarantees, and the pages keep that distinction visible.

Other character and gift research that depends on a moving or unpinned page remains outside the production default dataset. A missing row therefore means “not published from reproducible evidence,” not a negative gift reaction or a complete character classification.

Secondary and discovery sources

Selected editorial reporting and community discussion may be used to discover a question, corroborate a current-release observation, or identify a conflict. These sources never gain official status by repetition. When two guides repeat one unsourced value, they are not counted as independent evidence.

The project does not copy another guide’s paragraphs, full data table, route order, screenshots, or map. Claims are reduced to the facts needed for the page, checked against the strongest available evidence, and then presented through the site’s own structure, calculations, caveats, and interaction.

Text, data, and image reuse

Source access is not a blanket reuse license. Official and storefront text is used to verify facts and is rewritten rather than reproduced as marketing copy. Community-wiki text may carry an open-content license, but any adaptation still requires the applicable attribution, source link, modification notice, and share-alike analysis.

An article’s text license does not automatically cover a game screenshot or file-page image. Game imagery on this non-commercial, no-advertising fan guide remains the property of the relevant rights holders and is used only for identification and commentary within that limited context. The site does not represent that an official source has granted a general commercial asset license.

For an incorrect fact, follow the Corrections Policy. For copyright, trademark, privacy, or asset-removal concerns, use Takedown Requests.