Lore

Malefacts in Beast of Reincarnation

Build a sourced Beast of Reincarnation malefact taxonomy from in-game names, regions, attacks, Blight context, drops, and versioned bestiary evidence.

Malefacts are part of the hostile entity vocabulary surrounding Beast of Reincarnation’s Blight-transformed world. Pre-release evidence supports the term and the presence of corrupted dangers, but it does not publish a complete canonical bestiary, origin tree, or rule proving that every enemy belongs to that class. A useful lore guide must begin with names the game itself assigns.

This page defines a release-ready taxonomy without turning every trailer creature into an unsupported species entry.

Confirm the malefact label in context

Use the bestiary, objective text, tutorial, subtitles, archive, or official publisher caption. Record whether “malefact” is a broad category, a particular entity type, an individual title, or a translation term. Keep capitalization and singular/plural form as the public English build shows them.

Do not apply the label based only on plant growth or aggression. Nushi, Golems, ordinary wildlife, and named characters may use distinct categories. One being can also be described differently by separate speakers, so preserve the source.

Create an entity record from the game

For each confirmed entry, capture canonical name, region, first appearance, visual traits, attack families, health/Down presentation, drop or reward, and lore text. Put version and difficulty on numerical combat observations. Keep story interpretation separate from the bestiary’s exact statement.

A screenshot should identify the entity and source, not replace text transcription. If an enemy lacks a formal name, use a clearly marked descriptive placeholder only in private notes until the game supplies one.

Place malefacts within the Blight carefully

The Blight has transformed the land and is connected visually and narratively with dangerous growth. That establishes context but not a universal origin equation. The public story must explain whether malefacts are created, corrupted, attracted, controlled, or merely classified in relation to it.

Record each claim with speaker and story point. A Colony resident’s belief may differ from an archive or later reveal. Do not flatten disagreement into one pre-launch encyclopedia sentence.

Separate Nushi from ordinary encounters

Powerful Nushi are connected to Koo gaining abilities after defeat. Whether Nushi are a subset of malefacts, a separate class, or a role is a question for the game’s taxonomy. Do not answer it through boss size.

World pages should contain Nushi routes and the combat section should contain solutions. The malefact page should discuss classification, ecology, and documented relationships. This prevents three pages from copying the same fight overview.

Record combat traits without inventing biology

An enemy’s lunge, ranged effect, armor, or Down behavior is observable. Its anatomy, intelligence, reproduction, or motive requires lore evidence. Use neutral language for visual traits and attach attack details to a tested version.

If an update changes damage or Down values, that is a combat revision, not necessarily a lore retcon. Preserve the version scope. If a localization patch changes the entity name, record the former English label as an alias rather than creating a second species.

Build a region-by-region index

Sort confirmed malefacts by canonical area and first encounter. Include landmark and story state, but move detailed routes to the world map. Note whether an entity appears only under a condition or later returns in another region.

Do not claim a complete count until inclusion rules and bestiary completion can be checked. Variants, summoned forms, bosses, and phase transformations can make totals differ. State whether the list follows game entries or encounter models.

Control spoilers in taxonomy

Opening summaries should use only public premise facts. Hide late-game names, true forms, allegiances, and origin explanations behind clear warnings. A player searching for an early enemy’s Down behavior should not be forced to learn its final-story identity.

Use reveal order for conflicting descriptions. If the game later reclassifies an entity, show the initial label in the early section and the resolved explanation after the spoiler boundary.

Evidence boundary for malefacts

The term and hostile-world context are derived from official Beast of Reincarnation publisher materials alongside the Steam Store premise and Developer_Direct explanation. No comprehensive first-party malefact catalog was public on 2026-08-01. Canonical species names, hierarchy, region counts, and origin claims therefore remain gated on in-game text rather than trailer appearance.

Continue with another focused Beast of Reincarnation guide.

Lore

Beast of Reincarnation Characters

Track confirmed Beast of Reincarnation characters from first-party names, roles, dialogue, voice credits, story appearances, and spoiler-controlled evidence.

Lore

Beast of Reincarnation Endings Guide

Check the current Beast of Reincarnation ending evidence boundary and use a spoiler-safe method to verify ending count, conditions, choices, saves, and post-game.

Lore

Beast of Reincarnation Story Guide

Read a spoiler-free Beast of Reincarnation story primer about Japan in 4026, Emma and Koo's westward journey, the Blight, Colonies, and Nushi.