Run-history manifestation reads an explicit journal of prior decisions at encounter entry and builds a deterministic combat manifest. A defeated foe may return as an echo, a rescued ally may become support, or a claimed relic may alter the boss. The same snapshot stays fixed through retries so consequence is legible rather than arbitrary.
Three readable journal runes record that Tavi defeated a sentinel, rescued a guide, and claimed a relic. At 1.15 seconds, crossing the vault boundary captures those versioned facts once and assigns one manifest id.
Autoplay is disabled by reduced motion. Scrub across 0.30, 0.90, 1.15, 1.55, 1.85, 2.25, 2.55, 2.85, 3.18, 3.45, 3.72, 4.55, 4.95, and 5.35 seconds.
Define the eligible history keys, ownership and version, entry boundary, mapping table, conflict priority, manifest id, retry policy, save migration, co-op authority, disclosure, fallback state, duplicate-event guards, and telemetry.
Choose a small authored set of durable facts—defeated or spared characters, rescued factions, claimed relics, destroyed objectives, vows, or route counters. Give every key an owner, type, version, default, and provenance; do not expose arbitrary save variables or infer a moral score from unrelated behavior.
Map each eligible fact to a bounded enemy, ally, attack package, arena rule, phase, or resolution option. Define priority when facts conflict, validate the full composition against budget and geometry, and produce one inspectable manifest id before combat starts.
Capture at a named entry boundary and keep that snapshot through death, restart, checkpoint reload, pause, and rollback. Rebuild only after an explicit return to world state or a documented save migration. In co-op, name whose history is authoritative and what guests are allowed to contribute.
Replacing authored route facts with hidden deaths, accuracy, or damage makes the system adaptive difficulty, not historical consequence. State which decisions matter and ensure identical journals produce identical manifests.
If world scripts, random selection, party changes, or cloud synchronization are read again after death, players cannot learn the encounter they just saw. Persist the entry snapshot and make any deliberate recomposition a visible transition.
A remembered ally can block a lane, an old victim can repeat a recognizable attack, and a claimed relic can add a new response. These are more legible than an unexplained health multiplier and create encounter texture that belongs to the player’s route.
Enumerate valid manifests or constrain them with slots and priorities. Check spawn space, simultaneous threats, camera load, accessibility, dialogue, loot, achievements, skips, speedrun routes, sequence breaks, and the case where every optional fact is absent.
Record history version, eligible keys, provenance, captured values, manifest id, rejected conflicts, enemies, allies, modifiers, entry and retry counts, checkpoint source, migration path, co-op owner, completion, deaths by manifestation, abandoned attempts, and duplicate captures.
Above the sealed floor, three runes hold Tavi’s earlier route. When the threshold closes, one fallen sentinel condenses into an echo, a rescued guide answers with a ward, and a claimed relic wakes in Kern’s chest. After defeat, the same three marks relight in the same places.
Preview the relevant journal entries with distinct icons, colors, sound labels, and a text alternative; then repeat those identifiers on their manifestations. Offer a route summary, a stable retry composition, reduced simultaneous variants, a no-history fallback, and warnings before irreversible choices.
Persistent progress preserves encounter objectives across attempts. Loadout mirror copies what the player has equipped now. Run-history manifestation reads selected facts accumulated before entry and turns them into the encounter’s authored composition; its defining problem is deterministic mapping across saves and retries.
Sans becomes the route’s final boss only when the area kill requirements and mandatory defeats preserve the Genocide state. The encounter’s existence and unusually punitive rule set are a direct manifestation of the run ledger rather than a generic late-game difficulty bump.
The river fills with ghostly representations of people Snake killed earlier, so a lethal route creates a longer and denser encounter than a nonlethal one. Individual prior acts become identifiable hazards instead of an abstract penalty.
The final battle exposes support armies and named allies assembled through earlier faction choices, and those forces can be spent during the assault that ends at the Archdemon. Recruitment history therefore becomes a tactical resource inside the boss sequence.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub