Endacopia is tagged with Nonlinear and Choices Matter on Steam, so route planning is a legitimate player need. The safe method is to preserve context, not to guess every branch. Record rooms, choices, inventory state and changed dialogue, then make a supported save before a decision that sounds final when the game allows it.
Name a save by context
Use a room and event label such as “before the visitor leaves” or “screen after first inspection.” Do not name a file after Ending A, B or C until the result is confirmed. A contextual label remains useful when the route surprises you or when a community ending name differs from the in-game wording.
Verify that a save exists and loads before continuing. This page does not claim a slot count, autosave rule or cloud guarantee without current testing. The official news feed includes a post titled 1.04 and Cloud Saving, but the title alone is not a complete technical specification.
Track shared and unique route steps
Mark the last shared room, first divergence and first convergence. This makes a later ending page shorter and helps identify which achievements can share a run. If a choice produces a visible change, write the exact decision wording and immediate result rather than interpreting it as good or bad.
For a hidden route, record the entry condition and return point. For a puzzle, note the clue that makes the action plausible. For an achievement, capture the notification. Those records can be linked from Secrets, Puzzles and Achievements without duplicating the whole story.
Recover from uncertainty
If two walkthroughs disagree, compare public version, product scope and preceding state. Demo instructions do not automatically validate the full game. A pre-1.08 report may still identify a useful clue while needing a fresh route check. Keep the conflict visible until a current test resolves it.
The official Steam store page provides the nonlinear and multiple-ending context. The official news feed provides update dates. This article is scoped to Steam base game 2684630, Windows native, public label 1.08.
A route journal that survives spoilers
Keep observations, theories and confirmed results on separate lines. For example, “the visitor leaves after the screen is inspected” is an observation; “the visitor opens Ending B” is a theory until the final route is reproduced. This distinction lets a player read a safe planning page without accidentally treating a guess as a spoiler fact.
After each meaningful event, write the new room state and the next untested clue. If a choice appears final, save before it and verify the reload. If the game only gives an autosave, document that as an observed behavior rather than claiming a general rule. A future guide editor can then repeat the exact test after a patch.
Use a second run for incompatible branches only when the split is confirmed. A clean plan may combine a secret and an achievement in one route, but it should not force a player to sacrifice discovery for a guessed completion shortcut. The official 1.04 and Cloud Saving announcement is a source link, not a substitute for testing save behavior.
Use a decision ledger
For each branch, write the choice, who is present, what changes immediately, and what remains accessible. A ledger makes it possible to compare Ending A, B and C without treating one community name as the official result. It also shows which optional achievement or secret was completed before the split.
When returning to a save, reread the last two observations before acting. This prevents a later theory from being used to justify an earlier choice. If the game’s cloud behavior differs from a local reload, record the platform and version rather than generalizing from one machine.
The most useful route plan is reversible: it tells the player where they were, what they chose, and what they can still revisit. Keep that information before adding a theory about the ending. It lets both a first-time player and a completionist decide the next step without treating an uncertain branch as settled.