Research-state directory

Moonlight Peaks Characters

Review the Moonlight Peaks character research boundary, known family labels, relationship evidence, and the private tracker planned for verified profiles.

This directory does not publish the project’s unpinned roster research as settled game data. It shows which identity and relationship claims have a reproducible basis, how unknown fields will behave, and what must be verified before character filters become active.

Dataset: prelaunch Last verified: 2026-07-13Preview · search indexing disabled

What is public today

Moonlight Peaks characters: directory and roster limits

The internal research table references a community page that can continue changing. Names and classifications are therefore withheld until the exact revision can be reopened.

Public roster rows Withheld

No profile is promoted from a moving source into a public fact simply because the page is marked noindex.

Official family labels Seven names

Steam achievement names support the family labels, but they do not establish a complete family tree or every member.

Relationship rule Partial evidence

A PC editorial observation describes a common four-heart invitation, with story-gated exceptions. It is not a universal promise.

Personal tracker Planned locally

Future status, heart observations and notes will remain private browser data rather than public character facts.

Directory controls

Filters prepared for evidence-qualified profiles

Disabled controls are intentional: an active empty filter would suggest the missing public roster is a game answer rather than a source gate.

Enhancement pending. Unknown values will remain visible as “Not yet verified”; they will not be converted into No.

Profile evidence pending 8 fixed gift rows

Death

The profile does not publish unpinned biographical fields, but it can show a reproducible eight-item gift subset and the exact boundary around Net and Soul Blob research.

No public roster yet

Additional profiles

Names, romance classifications, family membership, species, work and schedules will appear only as their displayed fields obtain immutable or independently reproducible evidence.

Tool route available

Gift Finder beta

The current finder uses only Death’s source-pinned subset. It does not turn unpublished characters into empty profiles or suggest that missing gift rows mean a negative reaction.

Supported identity layer

Seven family names, not seven invented family trees

Official Steam achievement labels support The Logans, The Hendersons, The Webbs, The Hosus, The Khazans, The Ambrosias and The Draculas. That evidence names groups; it does not, by itself, assign every resident or explain every relationship.

Names

What can be stated

The seven labels can organize future navigation and relationship diagrams. A page may say that the game uses those family names when it links the official achievement evidence and keeps the retrieval date visible.

Links

What still needs evidence

A surname, shared home, or nearby workplace does not prove a specific relationship. Parent, sibling, cousin, aunt, partner and child connections require their own sourced record before they appear in cards or filters.

Gaps

How unknown fields behave

An empty pronoun, species, family, occupation, schedule, birthday, gift or romance field remains “Not yet verified.” It is never silently displayed as none, not dateable, no gifts, or no event.

Relationship evidence

Track observations without declaring one universal rule

A formal-release PC editorial report observed a dating invitation around four hearts and a following-night date after sleep. Special characters may have additional story gates, so this remains an observation rather than an official global mechanic.

General observation

The reported four-heart behavior can be shown later with its PC scope, source and caveat. It should not become a hidden threshold applied to every character profile or platform.

Read the cited editorial observation

Private tracker contract

Players will be able to record Not met, Met, Interested, Dating or Favorite, add their own heart observation and keep a private note. User-entered status will be labelled personal and will not alter the source-backed directory.

Character directory FAQ

Roster, romance and missing fields

The directory answers what its evidence supports and keeps research counts outside the public roster.

Why is the full character roster not shown?

The researched roster currently points to a community page without a pinned revision. That page can change after this build, making it impossible to reproduce exactly what was reviewed. The site therefore publishes the directory structure and evidence rules now, while names and classifications wait for a fixed oldid or independent current-release verification.

Are all Moonlight Peaks characters romance options?

No complete public classification is asserted here. The research model distinguishes dateable, friendship-only and other records, but its current roster source is still gated. An unpublished or blank dating field means “not yet verified for publication,” not that the character cannot be dated.

Does dating always begin at four hearts?

A PC editorial playthrough reported a general invitation at four hearts and a date after the next sleep, but the same research notes story-gated exceptions. The site will present that as platform-scoped editorial evidence, not an official rule guaranteed for every character, save state, patch or platform.

Are schedules, birthdays and heart events complete?

No. Those fields are not complete enough for a public directory. Fixed schedules, weather or season locations, birthday data, event dialogue choices and post-relationship behavior require their own source records. A character card will display “Not yet verified” rather than filling gaps from another guide or inferring details from a family name.

Where will relationship progress be saved?

The planned tracker stores personal status, heart observations and notes in the current browser. It will not sync automatically or submit private progress as public evidence. Controls stay disabled until save, reset, import, export, schema migration and malformed-data behavior have automated browser coverage.