Romance Routes

Where the cast page stops

The heroines page answers who the six are and what job each one holds. This page answers the other question: how a relationship moves, which patch notes touch it, and what the game does not publish. Keeping the two separate stops the cast list from turning into a route checklist.

The confirmed frame is short. Six relationship paths sit inside a city of 40-plus NPCs, and the store page carries a Dating Sim tag. The sixth heroine is still classified. No scene count, affinity threshold, gift preference, or ending name is published.

Those blanks are not a formatting problem. A route page that fills them from comments would be wrong in a way you cannot see until you have spent a loop on it. Everything below is either a store-page claim, a patch-note line, or a step the game itself asks you to take.

Friendship starts at the counter

The first friendship movement is not a gift. It is a resident request. Once the shop is open, residents walk in with their own requests, and finishing one moves friendship with that person. The orders page lists that reward next to counter sales and faction orders for the same reason: it is part of the shop loop, not a separate dating menu.

That ordering matters. If the seed queue is stuck or the counter is empty, you are not in a position to fill the request that moves the bar. Fix the queue, run one machine, stock the matching stand, and the request has something to attach to. Standing in front of a heroine with no stock behind you does not create a scene.

Two of the six already work in the building. The others are not in the workshop roster. That is a screen-time fact, not a ranking: the people in the workshop are the ones you can speak to between tasks without abandoning the counter.

No affinity number appears in the store portrait or the trailer stills. Treat any bar in a guide as that player's save, not as marketing copy.

Gifts, friendship levels, and 1.0.5

Version 1.0.5 adjusted the story script and dialogue, refined character gift content, and fixed a reward-claim problem. If you had already reached a friendship level but never received its reward, the reward can now be claimed again. If you leveled someone before that patch and saw nothing, reopen the friendship level reward before you decide the route is broken.

The same note does not list a single gift, a value, or a per-character preference. It also does not say whether a gift adds points, unlocks a scene, or only triggers dialogue. That is why this page has no gift table.

The blank is deliberate. A preference chart is the easiest thing to fake on a romance page and the hardest thing for a reader to check. Until a source prints likes and dislikes, the honest table stays empty. Use the friendship level reward as the visible checkpoint instead.

The demo affinity stays in the demo

A copied demo save can appear in the load list and then black-screen. The reply under the launch announcement says inheritance is not supported, and that sentence is not in the announcement body itself. Affinity and workshop level from the demo are gone with that file.

For route planning this is final. Choices made in the demo, and any bar filled there, do not exist in the release. Start a new file. Do not plan around a demo screenshot, and do not copy the demo folder into the release directory to recover a scene.

Advice written during the demo window has the same problem. If a post shows an affinity value from the demo, the number has no release save behind it. Treat it as a trailer, not a measurement.

What the ending actually reads

The store page says reputation and your choices decide the end. It does not publish an ending count or a name list, and nothing verified here fills either blank. Multiple endings exist; a number does not.

Reputation is the same number that brings non-human customers and a faction's special order. The ending therefore reads a bar you were already raising for shop traffic. A romance route is not described as the thing that picks the ending. Do not assume a partner locks a branch.

Faction exclusivity is also unstated. The store page calls the six factions rivals and stops there. If a second faction's work vanishes after you commit, reload the save from before the choice, not after it.

A route conversation that looks final gets the same treatment. Save first. There is no verified way to preview the result of a choice.

Save discipline for a route push

Keep one manual slot that you do not overwrite while pushing a route. Use a second slot for the current loop. Autosave is not a preview: by the time it records a commitment, the decision is already in the file.

Save before a conversation that offers a commitment, before a faction turn-in, and before the last step of a request chain if the text warns you. The save is the only preview the game gives you.

If a scene will not advance, check the build before the save. 1.0.6 fixed a stuck state after a story sequence on the second night. 1.0.10 fixed a main-story stall that could block progression. 1.0.12 fixed ending-video volume. An older build can look like a route bug.

• One manual slot held before the commitment, one for the loop.
• Do not overwrite the pre-choice slot to save a crafting attempt.
• Do not import the demo save to recover a scene.
• Recheck the version number before reporting a scene as broken.

Patch history that touches a route

None of these lines publishes a route count, a scene list, or an affinity cap. The table is a build check, not a walkthrough. If your build predates the line you need, the scene may already be fixed and you are reading an old bug report.

A route session that does not waste a loop

Treat romance as a second pass over a shop that already works, not as a parallel game. The requests are the only friendship movement the current build lets you verify, and they arrive through the counter. Everything else is either a patch fix or a save decision.

• Run the counter and the machines first. A resident request needs stock behind it.
• Take resident requests as they appear; that is the friendship movement you can see.
• Check the friendship level reward after 1.0.5 before assuming a gift failed.
• Hold one manual save before a commitment conversation and do not overwrite it.
• Skip the gift table. None is published, and this page does not invent one.
• If a scene stalls, read the version table before the route guide.