Characters

Mo Yuan in Phantom Blade Zero

A spoiler-aware Mo Yuan profile that records confirmed Phantom Blade Zero identity and keeps unannounced affiliation and outcomes separate.

Mo Yuan is a named Phantom Blade Zero character in official material. The currently cited public pages do not provide enough stable context to publish a full affiliation chart, quest route, combat role, or story outcome. This profile keeps the confirmed identity findable while showing exactly what evidence is required before deeper claims are added.

Current profile

FieldCurrent recordStatus
NameMo YuanOfficially named
ProductPhantom Blade ZeroBase-game scope
AffiliationNot assigned hereNeeds an explicit official or retail source
Combat roleNot assigned hereNeeds encounter or developer context
Story outcomeExcludedSpoiler-sensitive and unavailable pre-release

An incomplete field is preferable to a confident error. A trailer edit or community caption can help locate research, but it does not establish a permanent relationship or campaign result.

Why the profile remains limited

Character marketing often reveals an image or name before the story explains motivation, faction, and chronology. Filling those gaps from appearance can mislead players and spoil later reveals. This site requires direct wording, retail dialogue, a readable document, a quest entry, or unambiguous encounter context.

The result is still useful: players can distinguish the official name, find the one canonical page, and see which claims have not crossed the evidence threshold.

Affiliation evidence

An affiliation should include a story point. “Member of a faction at the outset,” “temporary ally during a named quest,” and “opponent in a specific encounter” are different statements. A costume emblem or shared weapon style alone cannot determine membership.

When the game releases, record the first scene or text that states the connection. Put later changes behind a spoiler warning, and do not expose an end-state allegiance in the navigation card.

Combat-role evidence

Playable

Requires a retail control segment or explicit developer statement. Appearing in action is not enough.

Ally

Requires observed AI cooperation, a quest role, or direct story context at a named point.

Boss or opponent

Requires an encounter identity, phase context, or official labeling; dramatic confrontation imagery is insufficient.

Story-only role

Requires campaign evidence showing narrative relevance without a directly controlled or fought encounter.

If Mo Yuan later has both a character profile and a major encounter, the profile should link to the canonical boss route. Tactics should not be copied into two pages.

Name and translation handling

Mo Yuan is used as the canonical English display here. If the final English subtitles use different spacing or romanization, the verified display name should become canonical while “Mo Yuan” remains an alias. Regional names belong on localized versions and should preserve the same character identity.

Two similar names must not be merged until a source connects them. Conversely, an alternate spelling should not become a duplicate biography once the identity is clear.

Spoiler structure after launch

The first section will retain the spoiler-light official identity. Later sections can cover first appearance, quest steps, relationships, and outcomes behind clear markers. A quest guide should lead with destination and action before story consequences.

If a player choice changes the character’s route, document the decision point, save recommendation, prerequisites, and mutually exclusive results. Do not label one route “best” without stating the reward, story, and gameplay tradeoffs.

Evidence players can capture

Useful captures include the character name in subtitles or interface, quest title, scene context, map location, chapter or objective state, and game build. A short clip should include the setup, not only the dramatic result. Avoid posting save identifiers or platform account information.

Conflicting accounts remain separate until the missing condition—such as a decision, difficulty, language, or chapter—is found. One playthrough can establish that an event occurred under those conditions, not that it is universal.

Where to continue

Use Characters for the cast verification system, Soul for the confirmed protagonist premise, Phantom World for setting context, and Updates for dated official reveals. This page will expand when evidence lets it tell a player who Mo Yuan is, where the relevant route begins, and what choices matter without relying on theory.

Primary official entry points

Continue with another focused Phantom Blade Zero guide.

Characters

Soul in Phantom Blade Zero

A spoiler-light profile of Soul, Phantom Blade Zero's playable assassin, his connection to The Order, and the 66-day campaign premise.

Guides

Is Phantom Blade Zero Single-player?

Phantom Blade Zero is listed as a single-player game on Steam; understand the campaign, map structure, and unannounced multiplayer scope.

Guides

Phantom Blade Zero Beginner Guide

Prepare a spoiler-light Phantom Blade Zero first playthrough with clear setup, combat, exploration, loadout, and upgrade decisions.