Endacopia characters

Official store material identifies the red-capped protagonist as Mellow. Artwork depicts a small figure with a pale face, very large dark eyes, a red cap, blue clothing, and a deliberately simple silhouette. The design suggests vulnerability and youth, but appearance alone does not establish age, history, motives, or reliability. Those details require official text or direct dialogue capture.

Mellow's scale relative to the bedroom furniture emphasizes the player's position inside a world built from familiar childhood objects. The large eyes also make tiny changes in pose or direction unusually expressive. For wiki purposes, screenshots should describe what Mellow is doing rather than assign an emotion that the frame cannot prove.

The title image places Mellow beside a rectangular sign or board with a simple face. It is visually prominent enough to deserve an archive entry, but the retained material does not establish a canonical name, role, or whether the figure is an independent character. This page therefore uses the descriptive label 'sign figure' and marks all narrative claims as open.

This is a model for handling uncertain characters across the wiki. A descriptive label allows search and cross-reference without laundering a community nickname into official canon. Once dialogue or an official caption provides a name, the entity record can add that name while preserving the older alias for redirects.

For each new character, capture the first location, visible design, exact self-identification, dialogue topics, inventory reactions, state changes, and last confirmed appearance. Keep direct quotations short and necessary; summarize most dialogue to respect the game's text and avoid turning the wiki into a transcript archive.

Separate behavior from interpretation. 'Turns away after the player selects an item' is observable. 'Feels guilty' is interpretation unless dialogue confirms it. This distinction is especially important in surreal stories where apparent friendliness, danger, or identity may be intentionally ambiguous.

• Canonical name and spelling
• First verified appearance and build version
• Visual description without inferred personality
• Dialogue subjects and state changes
• Relationships explicitly stated in-game
• Theory notes stored separately

The character data uses four levels. Confirmed means a primary source or direct in-game text names the character. Strongly indicated means multiple pieces of direct evidence converge but no explicit name is retained. Descriptive means the figure is visible but unnamed. Theory means the entry is interpretive and should not appear in metadata or factual summaries.

Confidence can rise or fall as the game changes. An early demo label may be replaced before release, or a community nickname may later become official. Editors should update the confidence field, not silently rewrite history, so readers can understand why older guides use different terms.

Character pages can reveal more than puzzle pages because names, transformations, alliances, and absences may themselves be twists. The landing archive stays spoiler-light by showing only first-appearance material. Build-specific event summaries should live below a warning and should never appear in search descriptions, card excerpts, or image alt text.

Until a full versioned playthrough is recorded, this guide avoids biographies that would be mostly conjecture. Event timelines should be added only when every event has a source pointer and version marker.

The retained snapshot does not answer how Mellow arrived in the shown environment, what the sign figure represents, which encountered figures are recurring, or how character states persist across scenes. These are research questions, not invitations to manufacture lore. The lore page may discuss interpretations, but character facts remain conservative.

A future verification pass should collect official character captions, developer descriptions, demo dialogue, and consistent screenshots. Each addition should update both the human-readable page and the machine-readable entity record.