These customer routes are reported by All Things How. Happy and Secret are community labels here, not a verified count or guaranteed main-ending recipe.
Should you help the Student?
Hear the confession request, agree to help and continue the later questions. Keep the pre-choice save until the connection to another customer appears.
Do not rush the message
Read the full conversation and choose the supportive route. The important action is participating sincerely, not choosing the fastest generic response. Save before the exchange so a localization difference or accidental selection does not force a long replay.
A completed repair can unlock the next dialogue, achievement, or story beat. Save before mutually exclusive choices when the route matters.
Positive route confirmation
Continue his later conversations. The route eventually reveals that his situation connects to another customer. That later information is a better confirmation than simply remembering that you clicked a helpful-looking line.
Customer follow-ups are not a main-ending formula
The later cross-customer connection confirms this customer follow-up. A friendly first answer alone is not the whole arc, and this callback does not establish an additional main finale.
Spoiler-safe checklist
You can preserve most of the discovery by following only these actions.
- Save before the confession request
- Agree to help
- Read the complete situation
- Continue later Student conversations
- Confirm the cross-customer connection before the finale
Student route: the reliable decision sequence
Create a manual save before the Student's decisive conversation. For the supportive route, hear the request out, agree to help with the confession, and continue the later questions instead of treating the first encouraging response as the entire arc. The route is best verified by the later cross-customer connection described in the guide, not by the emotional tone of one answer. Keep the supportive save until that connection appears. If you want the refusal outcome for comparison, return to the pre-choice save and keep it in a separate slot. Never overwrite the only checkpoint while testing both branches, because an autosave can preserve the most recent decision rather than the route you intended to continue. Finish the complete conversation and advance real story objectives before concluding that a callback is missing.
- Save before the confession decision
- Choose the supportive response
- Continue the later questions
- Confirm the later connection on the same save
Branch testing and missing-follow-up diagnosis
Use three named checkpoints: before the confession, after the supportive answer, and before the finale. The first permits an alternative-choice test; the second protects the route while you wait for follow-up content; the third lets you audit all character arcs together. If the follow-up does not appear, confirm the loaded slot, current build, active To-Do, and whether the full conversation completed. Check for a cloud restore or older timestamp before trying a workaround. Avoid claiming that money, shop rating, decoration, or repeated sleeping controls the scene unless a current-build test isolates that factor. Preserve the original save and report the last Student dialogue, active objective, other character progress, and exact point where the expected connection failed.
| Save | Purpose | Do not overwrite until |
|---|---|---|
| Before confession | Compare the main choice | Both immediate outcomes are checked |
| Supportive route | Wait for the later connection | The callback is visible |
| Before finale | Audit all major arcs | The target ending is reached |
What to record for a verified Student result
Capture the choice screen or write down the localized option, record the immediate response, then record the later connection and final ending from the same save. State whether the evidence came from first-hand play, an official statement, or a community report. A video can show that a route is possible, but it does not prove that every incidental action is required. Compare only choices that differ between controlled saves. Record build and language because wording can change while route intent remains stable. This prevents harmless actions such as buying an upgrade, completing an unrelated repair, or waiting arbitrary days from becoming invented requirements. Keep a blind-run archive if you care about the story, and use a separate research save for alternative outcomes.
