Full spoiler warning: Ending B is a branch intent, not a license to fill in a guessed sequence. Endacopia is officially tagged with Multiple Endings and Choices Matter. Before naming a trigger, verify the common route, first divergence, unique action and final confirmation in the current Steam base game.
Start at the shared route
Use a save named after the last shared room and decision. Record the exact choice wording and the immediate response. A guide should not say “choose the bad option” or another interpretation when the game gives a concrete line or object response.
Isolate the unique branch
List only the steps that differ from Ending A or the common route. State the prerequisite, action and observable state change. If the branch requires a hidden room, item or conversation, link to Secrets, Puzzles or Characters instead of duplicating the full discovery.
Confirm and cite
Confirm the ending with a distinct scene, result screen or achievement notification. Mark a community A/B/C label as such until the in-game title is checked. Compare public version and product scope when sources disagree; Demo or pre-1.08 instructions need a fresh test.
The product context comes from the official Endacopia Steam page. Third-party walkthrough demand is a working source, not text to copy. Scope is Steam base game 2684630, public 1.08.
Keep the reveal focused
A final page should show the common-route boundary, the unique choice, the prerequisite state and the confirmation. Do not repeat every room that both endings share. If an optional object is needed, link to its puzzle or secret page and place the consequence below the full-spoiler heading.
If Ending B cannot yet be reproduced, retain the branch brief and list the missing test. A transparent evidence gap lets another editor verify the route; a polished but guessed sequence can send a player away from the intended result.
Review the branch after updates
Keep the source date and public version beside the confirmed choice. When a later Steam announcement appears, retest the unique action first rather than rewriting the shared route. If the result is unchanged, record the check and leave the common guidance stable.
If the route grants a badge, link to its checklist entry after the ending confirmation. If it exposes a hidden room, link to Secrets before the reveal. The branch page should be the smallest complete answer to the ending question, with all reused exploration kept elsewhere.
An ending article should also state what remains unknown. A verified final scene can coexist with an untested first choice, and a community title can coexist with an in-game title that has not been transcribed. Keep those boundaries visible while the source corpus grows.
Use the spoiler heading as a hard boundary. Put general branch context before it, then show the choice and result only after the warning. This format serves a player who searches for the ending name and a player who only wants to know whether a saved branch can still be recovered.
When the route becomes confirmed, give a concise summary, the branch-specific steps, the confirmation and the evidence grade. Leave common exploration on its own pages. That structure makes the article easy to revise when an official announcement or a new reproduction changes one condition.
The source article should preserve the difference between a complete ending confirmation and a complete route guide. A confirmed final scene can be published with the branch sequence still pending, provided that the uncertainty is visible and the reader is not sent to a guessed choice.
Keep the branch’s source and test date beside the summary. If a later build preserves the same outcome, update the recheck note rather than rewriting every common step. If the choice changes, record the old and new states so readers can tell which report belongs to which public version.
Keep this note current.
Check it again.