The two central confirmed characters in Beast of Reincarnation are Emma and Koo. Emma is the human protagonist who fights and commands plant-like growth; Koo is her canine companion and the command-based partner who uses Bloom Arts. Pre-release trailers and announcements show other figures, but a dependable cast guide should not assign names, factions, relationships, or motives without first-party identification.
This page defines how to expand the cast from the public game while keeping trailer faces and voice speculation out of the canonical list.
Emma is the real-time protagonist
Emma moves through Japan in 4026, fights with katanas and other approaches, blocks and parries, and can control Blight-related vines for traversal. Her successful parries generate FP for Koo. Official material supports aggressive, ranged, and stealthy development paths.
Those mechanical facts do not explain her complete origin or final relationship to the Blight. The dedicated Emma lore page preserves the publisher’s pre-release biography boundary. Later revelations should be placed in chronological spoiler sections rather than retroactively inserted into a spoiler-free introduction.
Koo is partner, command role, and explorer
Koo equips Charms, uses FP-consuming Bloom Arts through a slowed menu, and gains powers connected with defeated Nushi. A hands-on preview also observed him alerting Emma to nearby threats. Together these facts establish active partnership in combat and travel.
Edition skins change Koo’s appearance but should not create duplicate cast entries. Brown and Black Shiba are entitlement names, not alternate story characters. His complete origin and ending state remain release spoilers.
Add a character only from a canonical name
Use an in-game nameplate, subtitle speaker label, menu archive, credits, official article, or publisher announcement. Record the spelling and locale. A trailer description such as “mysterious woman” is a descriptor, not permission to attach a fan nickname as canon.
If one character uses multiple names, keep a spoiler-free primary entry and place aliases behind the point where the game reveals them. If two similar models appear, do not merge them without dialogue or credits evidence.
Separate role from allegiance
For each character, record observable role, first appearance, location, and relationship statements. A person helping Emma in one scene is not automatically a permanent ally. A hostile encounter does not settle a character’s faction or motivation. Preserve the speaker and context for claims.
Use terms such as Colony resident, Nushi, malefact, or another class only when the game applies them. Visual corruption alone may not define taxonomy. This protects the cast guide from turning enemy designs into unsupported lore.
Record voice credits carefully
Beast of Reincarnation lists full audio in English and Japanese on Steam. A voice-cast table should come from official announcements or the final credits and specify language. Do not match voices by ear, reuse another database without checking, or assign one actor across all locales.
If credits update, attach the game version and preserve spelling as shown. Character aliases can make cast credits spoiler-sensitive, so place late-role mappings behind a warning even when the actor was publicly announced.
Build a reveal-order biography
Start with the public premise, then add mandatory scenes, optional dialogue, archives, and ending outcomes in the order a player can learn them. Distinguish the character’s statement from an externally confirmed event. A lie, belief, memory, or legend should not be summarized as objective history before the game resolves it.
Paraphrase extended scenes and quote only brief text needed to settle a term. Link route and boss information elsewhere. A cast page should explain who participates and why the encounter matters, not repeat a full walkthrough.
Keep enemy and boss indexes distinct
Nushi can be important story entities, but their location and combat solution belong in world and combat pages. Malefacts and Golems may represent broader enemy classes; give them taxonomy pages rather than inflating the named character count. Promote an entity into the cast only when the story individualizes it.
This distinction also makes a total meaningful. “Characters” should not silently mix every enemy model, anonymous Colony resident, and named story figure.
Evidence behind the initial cast
Emma and Koo’s roles are established by the Steam product description, the official Developer_Direct article, and current publisher articles. Steam supplies English and Japanese full-audio scope. No complete first-party character roster was public by 2026-08-01, so additional entries remain gated on canonical naming rather than visual inference.