Beast of Reincarnation features powerful beings called Nushi, and official material connects their defeat to Koo obtaining powers. Before launch, however, there was no complete first-party list of canonical boss names, locations, order, or optional status. A world-boss page should therefore function as a spoiler-controlled location index built from the public game, while the boss combat guide owns strategy.
This separation matters: “where and when” can help a lost player without automatically revealing every move or solution.
Confirm that an encounter is a Nushi or boss
Use the game’s title card, objective, dialogue, bestiary, or reward text. A large enemy in a trailer is not sufficient to assign a canonical name or boss class. Preview language such as “boss-like” should remain attributed until the release UI settles the taxonomy.
Record the exact English name and any distinct phase title. Do not create two index entries for phases of one encounter unless the game treats them as separate entities. If an enemy is a miniboss or elite, preserve that label instead of promoting it for search demand.
Place the encounter in the journey
Each entry needs region, stage or area name, nearest stable landmark, route from that landmark, and story condition. Note whether plant-vine traversal, a key event, or another ability is required. Include a clear spoiler label before naming a late-story destination.
The world is a westward journey through transformed Japan, with preview reporting describing a staged structure. Stage order must be captured from public play, not guessed from trailer sequence. Marketing editing rarely represents map order.
Distinguish mandatory and optional access
An objective or blocking arena can establish a required encounter. A side route or return visit may indicate an optional one, but test whether story completion can proceed without it. Record whether the player can leave, return, or revisit after victory.
Do not call a boss missable until a save-state comparison or explicit warning shows permanent loss. Similarly, do not promise unlimited rematches. Checkpoints, chapter select, boss replay, and New Game Plus were unresolved before launch.
Record the world change after victory
Nushi defeats can be mechanically important because Koo gains powers. Capture the exact reward and whether it changes traversal, combat commands, or another system. Then inspect the area for opened routes, changed hazards, NPC movement, or permanent state.
Avoid revealing narrative consequences in the index summary. A mechanical note such as “unlocks a Koo power used at the marked vine route” can be separated from a spoiler detail placed behind a warning.
Link route evidence to a map card
A boss marker should be reachable from a named checkpoint or landmark through a written route. Include elevation and one-way drops. If the path passes a story cutscene, say that without describing its outcome. Test the route after the area is unlocked and again if return behavior is important.
Do not use coordinates from a fan image unless they can be reconciled with the in-game map. A screenshot should show a landmark, not only the arena door.
Keep the index useful before the list is complete
Publish an entry only after the name, location, and access state are supported. Mark the index version and completion state. A blank row for an assumed tenth stage or a trailer nickname creates more confusion than an explicitly incomplete public-build record.
Sort in story order for a walkthrough view and by region for return navigation. Offer a hidden-name mode if the site supports it. Boss count should be reported only after inclusion criteria are stated, since Nushi, minibosses, optional elites, and phase forms can produce different totals.
Send strategy to the combat record
The combat entry should document identifiable attacks, valid defenses, FP opportunities, Down behavior, phases, and a tested solution. The world index should retain only a brief threat note needed for preparation. This prevents two pages from repeating the same generic parry and Bloom Art prose.
Likewise, lore about a Nushi belongs in a spoiler-marked entity section after the game supplies it. A location query should not force a player to read the ending significance of the encounter.
Evidence and release boundary
The Nushi term and Koo’s captured-power relationship come from official publisher material, including the Steam Store description and Kota Furushima’s Developer_Direct article. Environment and westward-journey framing are also first-party. No full canonical boss index was public by 2026-08-01, so names and routes remain gated on release play rather than trailer inference.