Reference records with source status attached to every entry.
This database is organized for quick lookups, but it is intentionally smaller than a launch-week wiki. Moonlight Peaks contains seven supernatural families, a magical farm, spells, potions, gathering activities, relationships, and Nokturna. Those official themes create many possible records, yet a record is useful only when its name, category, and details can be tied to an official source or reproduced in the current game.
Choose a category below, search by the term you saw in your save, and read the status before acting on the result. The database does not turn an official character portrait into a guessed romance route, or a storefront mention of potion-making into invented recipe costs. Missing fields stay visible so you can tell the difference between “not in the game” and “not confirmed here.”
Residents, families, and relationship status.
Browse 3 recordsFarm tools, crafting stations, and activity gear.
Browse 2 recordsVerified regions, services, and preparation notes.
Browse 1 recordsSpoiler-aware objectives and prerequisites.
BrowseVerification key
The displayed claim is supported by an official source or a repeatable current-build observation. Verification applies only to the fields that are actually written. A verified location name does not automatically verify every resident schedule, service time, or quest connected to that location.
The record identity is reliable, but important fields remain unchecked. This is common for characters whose names appear in official development material while gifts, family links, romance status, or schedules still require live-game confirmation. Use the known part and treat the rest as unknown.
The topic belongs in the category but is not ready to guide a decision. Pending records should not contain a precise cost, date, route, or stat. They exist to expose a research gap and should move to partial or verified only when evidence is attached.
Start with the exact noun shown by the game: a resident name, equipment label, region, or objective phrase. Search that term before trying a broader category. Then compare the page update date with your platform version. Steam and console patches may not arrive at the same moment, and a correct report from one build can be misleading on another.
For character and gift questions, confirm that the record refers to the same resident and not only the same family. For equipment, distinguish the station or tool from the recipe or action it enables. For maps, separate an officially named region from an editorial route through it. For quests, preserve the exact objective text and avoid treating a guide checklist as an in-game quest title.
Many questions cross category boundaries. A quest may point to a region, require a piece of equipment, and involve a resident, but that does not make every related detail part of the quest record. Open the linked category when you need the next layer, then return to the original objective. Keeping those claims separate makes updates easier when one location, item, or condition changes.
A useful correction includes the affected URL, platform, version, observed text, and a first-party link or repeatable in-game step. Screenshots can support a report, but the written context still matters: menus, quest states, seasons, and progression can change what appears. Corrections are applied to the narrowest affected claim so one confirmed detail does not make an entire record look complete.
The database will grow when verified information supports a real player task. It will not create a separate page for every gift, crop, card, or quest phrase simply to increase the URL count. Until a topic has enough independent value, related facts stay together in the category page or in a focused guide.