The most dangerous choice in The NOexistenceN of Morphean Paradox: The Forest of Silver Shallots is trying to make every choice “correct.” The EA Rebuild records a direction across conversations, timed silences, companion decisions, deaths, and later route forks. A run that protects everyone in one scene, abandons them in the next, and reloads every failed check is harder to read and harder to recover than a run built around one clear motive.
This guide gives the current route a practical spine: establish a character motive, protect recoverable saves, verify the state that each chapter is testing, and recognize the town-defense and endgame forks before they close. It does not promise one permanent “best ending.” The developer describes the new structure as a world that remembers traces rather than a simple choice-to-ending tree, and New Game+ is designed to show a different version of the same journey.
Write one sentence before the corpse cart moves
The opening asks what kind of person is waking inside the armor before it tells you which flags are important. Give the run a one-sentence rule and use it whenever two appealing answers compete. Four workable rules cover the major route pressures without requiring hidden-variable arithmetic:
| Route rule | Favor when choices collide | What can break the route |
|---|---|---|
| Protect the group, even at a personal cost | Help strangers, travel with Lilith, recruit companions, defend Golden Chalice Town | Dropping allies for a faster objective whenever danger appears |
| Find the truth, even when trust becomes uncomfortable | Inspect anomalies, question names and memories, pursue ruins and hidden context | Choosing every comforting answer merely to preserve affinity |
| Stay independent and verify the world alone | Decline partnership, preserve Lone Wanderer decisions, leave rather than defend | Rejoining only when a companion reward is convenient |
| Control the outcome at any cost | Forceful answers, sacrifice logic, mission-first decisions | Taking compassionate reversals without accepting their route consequences |
These are navigation rules, not guaranteed ending formulas. The live personality panel is the better check. If its dominant direction no longer resembles the sentence you wrote, stop selecting answers by reward value and restore the motive over the next few genuine decisions. Do not reload merely because a percentage check failed; success and failure can both leave meaningful traces.
Use three rotating manual saves instead of one disposable quick save:
- Chapter-entry save: make it before reading the first event of a new chapter. Never overwrite it inside that chapter.
- Route-fork save: create it before joining or leaving Lilith, the guild decision, the expedition decision, the Golden Chalice stay-or-flee choice, and the final battle priority.
- Recovery save: update it after a clean return to the guild or map, when no dialogue, dispatch, or battle resolution is still running.
The developer explicitly recommends against frequent save-scumming because this route is supposed to preserve imperfect choices. The rotation is insurance against an Early Access blocker, not a tool for forcing every check to pass.
The twelve-chapter route is a sequence of state checks
A current community route maps the Rebuild across twelve chapter labels, but Steam displays warning banners on that guide and official patches continue to change flow. Treat the sequence below as a checkpoint map: chapter names, exact day numbers, and available lines may shift with route and patch. What matters is the state each checkpoint asks you to carry forward.
Opening through Chapter 2: decide who owns the journey
On the corpse cart and during the first attack, the game separates action from motive. Helping because strangers should not die is not the same trace as helping to display power. Abandoning them is not a neutral shortcut. The next decisive state is whether Lilith travels with you. If this is a companion run, accept the partnership and stop testing solo answers for curiosity. If this is a Lone Wanderer run, refuse consistently and keep the save made before that refusal.
The guild decision is the second ownership test. A companion route can inherit Lilith’s frozen guild or establish another one; the exact name is flavor, while accepting a shared institution is the durable decision. A solo route should not form a party and then repeatedly reject its members. Before leaving this chapter, confirm that the guild or solo interface matches the route you intended.
Chapters 3 and 4: open the companion paths before judging the roster
The newspaper and recruitment leads introduce Fouco, Sartre, and Green. Read every relevant lead before advancing the morning scene. Recruiting them keeps later party conversations and intervention options available; refusing them is a real route choice, not a harmless way to save resources.
The guild assessment then tests how your leader responds to Black Mist and a dangerous battle: organize evacuation, approach it as a research problem, or commit to a direct fight. Choose the answer that matches the run sentence. If a party exists, use the post-assessment conversation to strengthen the companion whose role you actually intend to use instead of scattering affinity across everyone.
Chapters 5 and 6: the strange door tests evidence and trust
When the abnormal door appears, there are two separate decisions. First decide how much risk is acceptable during testing; sending a living subject through is not equivalent to using an object. Then decide what to tell Lilith. A truth-seeking companion route should inspect the door closely, note the medicinal smell if that prompt appears, and report the full observation. A distrust route can conceal it, but should preserve a pre-door save because the missing information can change later context.
The following battle forces a priority rather than a perfect rescue: reach Lilith, save a nearby person, or pursue the attacker. Do not describe one as universally correct. Record which priority you took, then check who is present after the scene. The July 23 patch repaired a blocker caused by pressing Lilith about the door crack and repaired topics that were being cut off before the newspaper. On an updated client, ask the available topics one at a time before reading the paper. If the event silently stops, reload the chapter-entry save after confirming that Steam has applied the newest update.
Chapters 7 and 8: intervention leads into the Kallen decision
The scapegoat event measures whether you intervene openly, solve the problem through a check, or stay outside it. After the dungeon, the crowd response repeats the same test at a larger scale: calm them, study them, or deliberately intensify the situation. This is a useful consistency check. A compassionate leader who abandons the scapegoat and inflames the crowd has changed direction even if a later dialogue sounds kind.
The expedition decision is the first large route gate. Joining the subjugation keeps the central companion and town storyline in view; withdrawing begins to move toward escape. When Kallen appears, separate three questions:
- What do you promise? Protecting civilians, prioritizing the objective, and refusing a promise describe different leadership models.
- Does she stay? Accepting Kallen preserves her later party state; rejecting her is not just a roster optimization.
- What comes first in the dungeon? The truth in the ruins, an immediate rescue, or tactical reconnaissance continues the same personality argument.
Create a route-fork save before the expedition and do not overwrite it until Kallen’s status and the dungeon result are visible.
Chapters 9 and 10: Golden Chalice Town is the campaign fork
Tell the townspeople the truth, reassure them with partial information, or deflect the danger; then resolve Elin’s recruitment conversation from the route you have actually built. Attribute-gated answers may appear, but a locked check is not proof that the run has failed.
The decisive prompt is whether to protect Golden Chalice Town or leave for the capital. Current route references indicate that leaving skips the town-defense chapter and a large block of companion interaction. Staying leads into the defense, where the next choice is how to deploy the party: coordinate the guild, act alone, protect Lilith first, or split responsibilities. Save before the town choice, then commit. Repeatedly crossing that fork through reloads defeats the point of comparing its consequences in New Game+.
If you stayed, the street battle asks whether to hold formation or break it for civilians. Later, the confrontation with the changed Wilson asks what the protagonist believes has changed: personal growth, the legitimacy of acting as a player, or value created through choice. Pick the statement that explains the route so far. If you chose to flee, do not expect the same defense scenes; continue the capital line instead of treating their absence as a bug.
Chapters 11 and 12: preserve the endgame state before choosing a future
Near the last battle, current route references flag an Amethyst check tied to earlier exploration. Treat the inventory as the authority. If the item is present, preserve that save before entering the fight. If it is absent, do not assume the save is broken or invent a late pickup: continue the route you created, or return to the earlier exploration save if that state matters more than finishing this run.
The final battle priority has three practical shapes: move to protect Elin, maintain formation, or allow Fouco to intervene when the required party and trust state makes that option available. Each protects something different. The first risks the wider line, the second risks Elin, and the third transfers the cost to Fouco. This is the payoff to the party decisions made earlier, not a last-minute multiple-choice quiz.
The endgame then presents options for continuing, resting the save, returning to the beginning, or listening longer. Read the live wording before selecting; Early Access localization is still being revised. If the capital route presents commissions, complete the available gathering, delivery, and investigation work before assuming the story has stalled. Keep the chapter-entry save for this section because the July 23 developer note still listed a blocker before the King’s quest.
Build a formation around failure costs, not patch-sensitive numbers
Exact percentages and talent values are poor anchors during active Early Access. Current community build references are also warning-marked on Steam. The stable way to assemble a party is to identify who pays when the plan goes wrong:
- Lilith: a front-line protector who can support retaliation and team survival. If she cannot stabilize the first positions, move damage dealers back before adding more offense.
- The protagonist: the flexible second front position. Use that flexibility to cover the weakest ally rather than duplicating the same damage type in every slot.
- Green: a back-line physical attacker whose target access and critical plan depend on position. A formation that drags him forward can remove the advantage you recruited him for.
- Fouco: control and status pressure tied to Sanity management. If her resource collapses before the decisive turn, shorten the setup instead of assuming the finishing skill is weak.
- Sartre: magic pressure that becomes more valuable when the party can keep a target exposed long enough for repeated effects to matter.
- Kallen: high-risk offense that can consume her own or an ally’s health and Sanity. Pair her with a durable front, watch the healthiest ally before committing a costly skill, and do not press the ultimate merely because it is available.
Before every story battle, inspect the live tooltip for range, resource cost, target row, and any ally payment. The July patches fixed several cases where battle behavior did not match descriptions, including stun behavior, items, targeting, and character skills. If the observed result still contradicts the tooltip, preserve the recovery save and capture the exact skill, formation, and turn instead of rebuilding the entire party around a possible bug.
Recover a stalled route without erasing its evidence
| Failure signal | First recovery | Do not do this first |
|---|---|---|
| An old save will not load after the Rebuild | Start a new Rebuild run; the developer says the old foundation is incompatible | Copy old files repeatedly or infer that a dialogue choice caused the failure |
| The door-crack morning conversation stops | Update the client, reload the chapter-entry save, and ask each topic before the newspaper | Overwrite the only pre-morning save |
| A Lone Wanderer event or sale loops | Update and reload before the event; July fixes covered the Shadow of the Other loop and missing solo events | Join companions solely to escape a route-specific bug |
| The route stops before the King’s quest | Keep the pre-quest save, check official announcements newer than July 23, and wait for the documented fix if still unresolved | Repeat unrelated choices until the save’s route state becomes unclear |
| A battle result contradicts its tooltip | Record formation, skill, turn, and save; retry once on the newest client | Publish an exact permanent formula from one broken result |
For a reproducible bug report, include the route (companion or Lone Wanderer), chapter and scene, the last choice made, the expected next event, the actual screen, current language, and a copy of the save from before the failure. The official team says reports with saves and reproduction steps receive priority.
Commit only when four states agree
Before crossing the Golden Chalice fork or entering the endgame, pause on a normal map or guild screen and verify four things: the party contains the companions your route expects, the personality panel still reflects the motive chosen in the opening, the inventory contains any exploration item you deliberately pursued, and a chapter-entry save exists outside the active event. If one disagrees, fix that state before advancing. If all four agree, accept the consequence rather than chasing a perfect-looking answer.
Sources and official media
The official Steam listing supplied AppID 3942480, 0x0Real Studio and Nino Games credits, the January 2026 Early Access release, system descriptions, and the three untouched 1920×1080 JPG screenshots used above. The July version boundary, incompatible old saves, Rebuild design, route-specific fixes, and known King’s quest blocker were checked against the game’s official Steam announcements. Chapter checkpoints and cautious formation roles were compared with current community guides, but warning-marked pages did not support a precise rule alone. The supplied January walkthroughs describe the replaced pre-Rebuild structure; five supplied Steam guides belong to the separate game The NOexistenceN of you AND me; and the supplied Game8 URL returned no readable article body.