Moonlight Peaks Gifts

Before you spend an item

Read the verification status first

A gift table looks authoritative even when most of its cells were copied from an early post or inferred from a character theme. This finder takes the opposite approach. A resident can appear because their identity is supported by official material, while every preference remains marked “not confirmed.” That does not mean the resident has no loved or liked gifts. It means this page does not yet have enough evidence to tell you what they are.

Use the verification column as part of the answer, not as a footnote. A pending row is suitable for finding a character name and opening a research trail, but it should not decide how you spend a rare crop, crafted item, or quest material. When a preference is eventually published, it should be tied to a current game version and a repeatable reaction or another reliable source.

Romanceability is handled separately from gift preference. An official portrait, family mention, or conversation does not confirm that a character can be dated. Likewise, a known romance candidate does not reveal their favorite items. Keeping those fields independent prevents one confirmed detail from making the entire row look complete.

Player research

A low-risk way to test a possible gift

When the database does not have an answer, treat gifting as a small experiment. The goal is to learn one reaction without creating a larger inventory problem. The steps below are editorial research guidance, not a claim about a hidden scoring formula.

1. Confirm the recipient. Check the resident name and family context before selecting an item. Similar themes or nearby homes are not enough to identify a preference.
2. Choose a replaceable item. Test something you can grow, gather, or make again. Keep unique rewards, scarce quest materials, and the last copy of an unknown ingredient out of early experiments.
3. Record the game state. Note your platform, visible version, season or story stage, and the exact item name. Those details help distinguish a changed reaction from a mistaken report.
4. Read the complete response. Preserve the reaction text or clear visual result instead of reducing it immediately to “love” or “like.” A neutral response is still evidence and can prevent another player from wasting the same item.
5. Repeat before promoting the result. One observation may be affected by context or transcription. A preference should not become a verified table value until the recipient, item, and reaction can be reproduced.

Do not reload repeatedly just to manufacture a complete list in one session. A smaller set of observations collected during normal play is easier to audit because the inventory source and relationship context are clear. It also keeps the guide aligned with the way players actually use gifts: as part of a route through town, not as an isolated laboratory.

Build a gift log you can trust

A useful personal log needs fewer columns than a public database. Record the character, exact item, observed reaction, date tested, platform, and game version. Add a short note when the reaction was ambiguous or when the item might have been connected to a quest. Avoid copying a classification from memory after several nights; write the reaction while the context is still visible.

Keep negative and neutral results. Players naturally remember a spectacular positive reaction, but the ordinary responses are what make future tests efficient. If three common forage items are already known to be neutral, you can focus on a different category instead of repeating them. A complete negative note is more valuable than an attractive blank filled with a guess.

Separate your own observation from information you want to check. A “reported” column can hold a community suggestion, while a “tested” column records what happened in your save. That distinction prevents a rumor from becoming more convincing each time it is copied. When you submit a correction to this site, send the tested observation and its context, not only the item name.

Plan a gift route without sacrificing the farm

Gifts compete with recipes, upgrades, quests, and collection goals for the same inventory. Set aside a small gift shelf or chest only after basic farm work has a reliable supply. Keep one sample of an unfamiliar material before giving away duplicates, and avoid carrying the entire collection through town. A focused route with two or three intended recipients is easier to remember and leaves room for gathering.

Choose gifts that fit places you already visit. A replaceable item gathered near a resident is usually a better research candidate than a scarce object that requires a separate trip. This is not a claim that convenient gifts produce better relationship values. It is a planning method that reduces travel and makes regular conversations easier to maintain.

When relationship progress matters, pair this page with the romance guide. The romance page explains how to separate broad official promises from route-specific unknowns. For general time and resource planning, use the beginner guide. Neither guide replaces the reaction shown in your own save.

Publication standard

How gift records will be updated

The official Steam description confirms a relationship-focused town with roughly two dozen romanceable characters across seven families, but it does not publish a complete gift chart. Official development posts can confirm selected character identities without confirming their schedules, romance status, or preferences. Those boundaries are reflected directly in the current table.

A future update may move a field from pending to verified when the reaction has been checked on the current build. The update should name the affected character and item, preserve the page date, and avoid applying one result to an entire item category. If a patch changes a reaction, the older value should be corrected with a version note rather than silently presented as if it had never differed.

This page deliberately remains one searchable gift hub while the dataset is small. It will not create separate “loved gifts,” “liked gifts,” and character gift URLs containing the same rows. A character page should be published only when there is enough verified, independent information to answer a distinct player question. Until then, use the finder, the character database, and direct anchors as the stable lookup path.

To report a result, use the contact page and include the page URL, character, item, reaction, platform, version, and a repeatable in-game step. Reports are reviewed as evidence, not counted as votes. Several unsourced copies of the same list do not replace one clear observation.