Compare the 12 Marriage Candidates
The verified marriage-candidate list contains 12 names. Adeline, Celine, Juniper, Reina, Seridia, and Valen are listed as bachelorettes; Balor, Caldarus, Eiland, Hayden, March, and Ryis are listed as bachelors. No additional name is added without an official or current structured source.
The official FAQ states that marriage candidates are not locked by gender. A player may choose any eligible villager regardless of gender, so candidate selection can focus on personality, story, events, and personal preference. Pronouns are also selectable for the player character according to the official FAQ.
Two candidates, Caldarus and Seridia, connect to later story material and should be treated as spoiler-sensitive. Their presence on the verified list does not justify revealing their full unlock routes in a general comparison. Detailed profiles should carry clear spoiler labels before explaining consequential story conditions.
Build Friendship Before Choosing Romance
Friendship grows through supported interactions such as conversation and gift giving. Marriage candidates display a heart relationship marker, while other residents use a gem. The current relationship level is visible in the Journal, making it the appropriate place to track progress.
Resident friendship points do not decay according to the structured reference. This removes the need to visit every candidate every day simply to prevent loss. Build relationships alongside farm, town, museum, and Mines goals instead of treating social play as a mandatory daily sweep.
Gift preferences must come from a current character record. Do not assume that a job, color, or dialogue line proves an item is loved. Until a complete gift list is verified, talk regularly and use only confirmed preferences from a sourced profile.
Follow Events and Route Choices
Relationship events occur as friendship deepens and can require earlier events or other progression conditions. Some events also depend on story quests, goals, or access to a particular location. When an event fails to trigger, review its documented prerequisites rather than inventing a new heart threshold.
The relationship system supports both romantic and close platonic routes where the choice is offered. Read the scene options carefully because a heart event can define which route continues. A guide should state the decision point clearly without pretending every friendly interaction is reversible.
Festivals and dates can add relationship moments, but exact invitations and requirements must be current. Keep event-specific details in the relevant festival or character profile. This overview explains the structure while avoiding copied dialogue and unsupported timing claims.
Continue into Marriage and Family
Version 1.0 completes proposals, weddings, marriage, and children. These are official full-release features rather than speculative future roadmap items. An Early Access guide that says marriage is unavailable is no longer accurate for the current version.
The official 1.0 FAQ confirms that existing saves carry over, so returning players can continue established relationships. Load the updated save, review the new relationship cap and objectives, and let eligible retroactive achievements register. Starting over is optional and should not be presented as a relationship requirement.
Family progression should be treated as a personal choice, not a universal completion mandate. Follow the in-game relationship instructions and current official systems without inventing proposal items, costs, or dates. Detailed marriage steps belong in a guide only when every required condition has reliable current support.
Choose by Story, Not a Fake Ranking
There is no evidence-based single best spouse for every player. Candidate value depends on preferred writing, personality, events, visual design, story access, and the route a player wants to experience. A tier list would be opinion, not a factual answer to the romance-options query.
Use the character hub to find supported profiles as they are published. A complete profile should include a current schedule, verified gift preferences, event prerequisites, spoiler level, and sources. Unsupported candidates remain visible in this verified list but do not receive thin individual pages.
The safe decision process is simple: meet the cast, build friendship without fear of decay, view events in order, and choose the romantic or platonic route that fits the save. Keep the game updated because later patches can correct event blockers. When an exact detail is not supported, omit it rather than filling the gap with a plausible but invented instruction.
Return to the current Journal whenever a relationship milestone changes. It shows the save’s actual progress more reliably than a guide written for an older release. Pair that visible state with sourced event requirements before deciding that a route is blocked.