sephiria characters | Complete Evidence-Based Wiki Guide

sephiria characters should not be presented as a large playable roster because the reliable portion of the supplied material verifies Perr while separating many other names into NPC or role categories. Claims from an unrelated trainer page are excluded because they do not establish real unlocks or abilities. Any additional playable character remains To be confirmed until the supplied evidence clearly identifies one.

Verified playable-character evidence

The usable character index in the supplied material begins with Perr and deliberately excludes unsupported biographies. It treats a character as publishable only when the evidence answers a concrete player question about a location, event, or achievement. That rule is why a large roster, invented classes, and guessed skill multipliers do not appear here.

Perr is the only named entry presented as verified in the compact index. The source connects Perr to the Soul Plan achievement and places the relevant route at the carrot farm after Chapter II progression. It then instructs the player to talk to Perr, follow the dialogue, and complete the floating-island scene beside the Tree.

Perr and the Soul Plan route

Use Chapter II progression as the starting state for the Perr check, then visit the carrot farm rather than searching every random room. Continue the available conversation instead of leaving after the first line, because the supplied route describes a dialogue sequence leading to the floating-island scene. The achievement-facing result is meeting the Tree with Perr, matching the Soul Plan wording also present in the supplied achievement records.

The material does not provide a universal troubleshooting sequence for a missing Perr event. Recheck the chapter state, the carrot-farm location, the completed dialogue, and the Steam wording before adding another condition. Any claim about a required weapon, timer, costume, or numerical threshold is To be confirmed because none is established by the verified entry.

Chapter-character records

The source proposes a Chapter characters category for future verified entries. A useful record in that category should preserve the character name, chapter state, dialogue trigger, and progression result together. Keeping those four fields linked prevents a name seen in one scene from being promoted into a playable-character claim without evidence.

Chapter state matters because the same location can change as progression advances, while dialogue trigger explains what the player actually does. Progression result records the observable outcome instead of guessing at hidden flags. Until all of those fields are supported, the proposed entry remains a research lead marked To be confirmed.

Merchants and event NPCs

Merchants and event NPCs form a separate category in the supplied index. Their records should focus on a location or event, available purchase choices, and any consequence of hostile actions. Those fields answer practical questions without pretending that every named NPC is a selectable hero.

The supplied material also points out that an NPC-consequences guide has a different purpose from a character biography. An event consequence may explain what happens after an attack, yet it does not establish the NPC's complete role, history, or playability. Keep those scopes separate and mark any missing relationship or reward To be confirmed.

Progression figures and named enemies

To be confirmed: Tree and progression figures should be recorded with their chapter context and their relationship to Roots, Miracles, or permanent progression, following the category fields in the source. Bosses and named enemies instead need a floor or encounter context, replacement conditions, attack context, and rewards. This separation keeps progression guidance from being mixed with combat indexing.

To be confirmed: A name alone is not enough for either category. The current version, a screenshot or visible wording, and the observed chapter state should support the entry before it is published as fact. A reward or relationship copied without that context remains To be confirmed, especially when translations use different names.

Costume and companion references

To be confirmed: The source reserves another category for costume and companion references. Those entries should record an unlock condition or build interaction together with a source and patch context. They should not be used to imply that a costume, summon, and playable character are the same kind of entity.

This distinction is important for site structure as well as gameplay. A companion interaction belongs with the build or event it affects, while a verified playable entry must answer a character-specific question. If only a visual resemblance or community nickname connects them, the relationship is To be confirmed.

Bat-character video lead

A supplied video transcript describes a possible bat-character unlock through a random room and an NPC called Manok the friendly wanderer. The narrator says the player can donate blood through an Iron Maiden interaction, receive an artifact, and repeat the encounter five times across playthroughs. Because the narrator is openly unsure which floors can contain the room, the whole route remains To be confirmed rather than promoted to the verified roster.

To be confirmed: If investigating that lead, record the room, NPC wording, interaction count, health change, artifact result, and current game version. Do not convert the narrator's uncertainty into a fixed floor range, and do not claim the health cost is permanent or non-permanent without checking the current build. This makes the transcript useful as a research lead while preventing an unverified character from becoming a fabricated database entry.

Evidence checklist for new entries

To be confirmed: Before adding another name, check that the source answers at least one real question: where the character appears, which event begins, or which achievement changes. Capture the game version, chapter state, visible text, and a screenshot or equally direct record. Then classify the entry as playable character, chapter character, merchant, progression figure, named enemy, or companion reference.

Do not copy a roster from the unrelated trainer-oriented section at the beginning of the source file. Its claims about numerous heroes, classes, floors, and multipliers are not supported by the later verified index and were excluded here. Names absent from the verified section remain To be confirmed, which is more useful than a confident but invented list.

What the supplied evidence confirms

Tree and progression figures should be recorded with their chapter context and their relationship to Roots, Miracles, or permanent progression, following the category fields in the source. Bosses and named enemies instead need a floor or encounter context, replacement conditions, attack context, and rewards. This separation keeps progression guidance from being mixed with combat indexing.

Source references

The supplied character research includes the SephiriaWiki character index, a focused Perr location guide, an NPC-consequences guide, and a community video reference. These sources support the named-character and NPC discussion. They are community references rather than an official roster database.

The source document also contains an XMODhub character article. Its trainer promotion and broad genre links were excluded because they do not establish Sephiria character facts. Any unlock advice derived from that article remains explicitly attributed and version-sensitive.

Evidence boundary

The source file for sephiria characters combines material from more than one page or format, so repeated claims were consolidated and navigation, advertisements, and unrelated links were removed. Details that depend on a patch, translation, or an unverified community statement remain marked To be confirmed. This boundary is part of the answer: it prevents a plausible-sounding number, character name, item effect, or unlock condition from being invented.