Boss & Rematch Checklist

This page contains boss and rematch terminology. Use the Boss Intelligence Centre for the canonical dossiers and the Completion Companion for local progress.

Identity is not completion

An official boss name, portrait or patch-note mention proves that the encounter exists. It does not prove an unlock route, phase count, weakness, reward or rematch location.

First-encounter pass

For every accepted dossier:

• confirm the boss identity;
• record the story or world state before entry;
• record the encounter location when verified;
• preserve a save before the fight;
• note the visible completion trigger;
• verify the world or journal state after victory;
• record a reward only when directly observed or officially stated.

Rematch pass

Keep first encounters and rematches separate.

1. Open the relevant dossier.
2. Check whether the rematch route is verified, official-only or unresolved.
3. Confirm the required prior encounter state.
4. Use the accepted Memory Fragment or rematch interaction only when the dossier supports it.
5. Complete the rematch and record the visible ending state.
6. Save, reload and confirm the state persists.
7. Leave the entry in Research if the route or trigger cannot be reproduced.

Encounter record

Capture:

• patch and platform;
• boss and accepted alias;
• first encounter or rematch;
• region and precise location;
• prerequisite story state;
• entry interaction;
• character and difficulty;
• visible phases or transitions;
• victory signal;
• reward;
• replay availability after reload;
• screenshot or video source.

Defeat diagnosis before grind

If progress stalls:

• verify the fight is not exposing an unlearned defence or movement rule;
• check healing and recovery access;
• test whether lock-on helps or obstructs the camera;
• confirm the boss and critical effects render correctly;
• change one loadout variable at a time;
• consult current technical issues before assuming invisible attacks are intended;
• avoid converting one successful attempt into a universal weakness claim.

Patch regression check

Patch 1.16.00 fixed crashes and progression faults across several encounters and Abyss activities. A fault that returns on the current verified patch is a possible regression. Report the exact boss, location, action, save state and platform instead of reusing an older workaround without testing it.

Completion rule

A boss record counts as complete only when its supported completion trigger is met. A rematch counts separately only when the canonical dossier supports a rematch record.

The following remain evidence gaps until proved:

• exact route;
• exact phase count;
• numeric statistics;
• universal weaknesses;
• drop rates;
• difficulty-independent rewards;
• unlimited replayability.

Final boss audit

• Every accepted first encounter is classified.
• Every accepted rematch is classified separately.
• No unresolved route is counted as complete.
• Rewards are linked to a specific test state.
• Possible regressions have current-patch evidence.
• Full-spoiler notes are not exposed in low-spoiler records.

Official sources

• Patch Notes Version 1.16.00
• Current Known Issues