Lootbound run map, objectives and risk-event guide

Confirmed run sequence

The official pages describe a run as a chain of irreversible planning decisions rather than a fixed mission list. You start alone, choose a path on the map, find companions, equip every party member, take calculated risks and build a final Guardian from boss parts.

This is the full published structure, not a complete room or biome catalogue. Official pages do not name biomes, companions, event rooms, bosses or individual parts, so a page claiming every location today would be filling gaps with demo footage or guesswork.

Lootbound final boss and event objectives

The Lootbound final boss is a confirmed run objective, not a fully documented encounter guide: after the biome choices, the assembled Guardian faces the final boss. The official pages do not publish its name, health, attacks, arena, drop table or a guaranteed route to it. Likewise, the site can explain the confirmed event-room concept and dice-risk decisions, but cannot list every event, reward or spawn location until a versioned build exposes them.

Use this page to log each run’s route, companion recruitment, risk-room choice, boss part and final encounter result. Keep observed names and numbers marked as build-specific until they are backed by an official update or repeatable release-build testing.

Route-choice framework

The map promises valuable loot but makes the route itself a choice. Before committing, evaluate the party’s current weakness rather than chasing the highest-looking reward every time:

1. No companion yet: prioritise a route that can broaden the party if the map exposes a clear recruitment opportunity.
2. Grid is full but incoherent: value rearrangement or replacement opportunities over another large item that cannot fit.
3. Aura core exists: seek equipment that can occupy its affected cells or support the same damage approach.
4. Party lacks an armour answer: use the four official approaches—penetration, exhaustion, destruction or direct damage—to identify the missing role.
5. Approaching a biome boss: avoid treating an untested high-risk room as automatically optimal; a failed reward attempt can leave the final encounter underprepared.

These are decision principles derived from confirmed mechanics, not fixed spawn instructions.

Risk rooms and dice rewards

Special rooms present several choices at different difficulty levels. The store explicitly links greater reward value with a harder dice roll. It does not publish die size, modifiers, visible odds, failure penalties or whether an item can change the roll.

A useful run log records the offered options, displayed difficulty, displayed reward, roll result and build number. Do not publish an odds table from a small sample. If the interface shows an exact probability, capture that UI; otherwise label any observed rate as a sample, not a game rule.

Boss parts and the final Guardian

At each biome’s end, the player selects one of two boss parts. Each changes both the Guardian’s look and power. After all biomes, this completed Guardian faces the final boss. That makes every biome choice a build fork, but the official material does not say whether parts can be previewed, rerolled, replaced or combined into named sets.

Evaluate a part by the build you already have: which party weakness it covers, which damage approach it supports and whether the rest of the inventory can activate its synergies. A visually impressive part is not automatically stronger for every run.

What to record after release

For each room or event, record exact UI name, biome, entry icon, choices, cost, reward, failure outcome and version. For each boss part, record the boss, two offered parts, effect text and whether the choice is reversible. This evidence-first template will support a real route database later.

Use the weapon and item mechanics database for grid and damage fields, and the build guide when deciding how a route reward fits the party.