Use the Journal’s rematch reference
Patch 1.07.00 lists rematch locations and points readers to Journal > Knowledge > Memory Fragments > Bosses. The notice also explains that some former Abyss rematches moved to land. Read the entry on your current build before following an old map marker.
| Boss | Rematch location in the notice | Scope |
|---|---|---|
| Muskan | Bonepit | Rematch; not the initial encounter. |
| Draven, the Crowcaller | Church of West Demeniss | Rematch; not a quest or unlock walkthrough. |
| Goyen | Spire of the Sun | Confirm the displayed Journal entry on your build. |
This is a selected reference, not a complete list. If the entry is unavailable in your save, the patch notice alone cannot tell you which quest or prerequisite is missing. Record the current Journal state instead of inventing an unlock sequence.
Give the attempt one learning objective
Choose the smallest problem you can recognize: avoiding a specific opening attack, managing distance after a phase transition, or finding a safe moment to recover. A rematch can be useful even if it does not end in victory, provided the observation answers that question.
Write down the installed build, character and the skills or equipment being compared. Version 2.00.00 revised parts of combat and progression, so an earlier video may demonstrate a different set of conditions. Compare the relevant dated note, not simply the video’s popularity.
Keep changes visible between attempts
| Before | During | After |
|---|---|---|
| One objective and one planned change. | The cue you recognized and the action you chose. | Whether that action solved the original problem. |
| Character, equipment and relevant skill choices. | The first point where the attempt became unstable. | Keep, revert or test the change again. |
| Build and Journal rematch entry. | A new phase or unfamiliar timing. | A specific question for the next attempt. |
If you change equipment, several skills and your response timing together, a better result will not tell you which change helped. Keep a stable reference setup and label a different build as a new experiment.
A patch note and a win prove different things
An official patch can establish that the developer changed a mechanic or reported fixing an issue. One successful attempt shows what happened under your conditions. Neither automatically proves a universal strategy, guaranteed drop or fixed farming yield.
When a problem appears repeatedly, capture the input sequence, phase, build and outcome for a correction or official support report. Avoid posting account identifiers or private save codes. For general preparation, continue with the boss preparation guide; for a dated change, use the patch tracker.
Your next-session note
Write one observation, one change and the result you want to compare. The fields stay in this open tab only; download a text copy before leaving. Nothing here reads your game save.
Enable JavaScript to download; you can also copy your notes manually.
Sources: review and scope
Sources checked 10 October 2026. Independent, AI-assisted writing checked against the specific references below. Location references below come from official version 1.07.00 and are specifically rematch locations. They do not establish first-encounter routes, rewards or the newest installed build. No new playtest is claimed.
- Pearl Abyss: patch 1.07.00, rematch locations and Journal reference
- Pearl Abyss: patch 2.00.00, combat and skill changes
Send a correction with the page, source and relevant version or travel date.