Crimson Desert Boss Rematch: Reminisce vs Resonate
Beat a boss once and its Memory Fragment lets you fight it again, as any of the three characters, in one of two modes. Here is how Rematch works, why it pays nothing, and what 1.07.00 and 1.13.00 moved.

The fights you already won are still out there
Crimson Desert built its bosses as one-offs. Win once, ride on. Pearl Abyss's own reason for changing that is written into the 1.05.00 patch notes: as more of the continent got liberated, there was naturally less left to fight. The fix was two systems shipped together on May 2, 2026 — Re-blockade, which puts enemies back on forts you cleared (covered in our Re-blockade guide), and Rematch, which puts bosses back in front of you.
Rematch had been trailed twice. The April 9 dev update led its new-content list with boss rematches, and the 1.04.00 notes on April 23 said the feature "will be added soon." It landed nine days later with 69 bosses and two modes, and Pearl Abyss labelled it a first step, content that "will be continuously improved through future patches."
This guide is about the system, not the fights: how to start a rematch, what the two modes actually do, what a rematch pays (the answer is short and disappointing), which bosses were added or moved after launch, and the patch-note lines that have touched Rematch since. Strategy for specific encounters lives in the bosses guide and the Golden Star guide. Everything below comes from Pearl Abyss's own notices unless another source is named.
How to start a rematch
The 1.05.00 notes lay out the loop, and it has one hard prerequisite: a Memory Fragment only becomes active after its boss has been defeated. Rematch cannot be used to scout a fight you have not won.
- Beat the boss once, in the normal course of play.
- Find its fragment. Open Journal > Knowledge > Memory Fragments > Bosses, select the boss and choose Open Map to see where its rematch sits. Rematch fragments also show on the World Map and the minimap.
- Go there and light your lantern at the fragment, then read it to start the rematch.
- Choose a mode, Reminisce or Resonate (below). Per the notes, a rematch can be attempted with any of the three playable characters — Kliff, Oongka or Damiane.
Two later patch notes add useful detail. Blinding Flash is meant to reveal a memory fragment's location too: 1.16.00 on August 1 fixed a bug where it did not. And if you remapped lantern aiming on a controller, check your version — 2.03.01 on September 21 fixed lantern aiming ignoring a customised controller input, and the lantern is how a rematch starts.
Trust the Journal over your memory of the arena. As the roster section shows, some fragments no longer sit where the original fight happened.

Reminisce vs Resonate
Rematch shipped with two modes, and Pearl Abyss's descriptions are short enough to quote whole:
| Mode | Pearl Abyss's description | What it is good for |
|---|---|---|
| Reminisce | "Fight the boss exactly as they were when you first encountered them." | Seeing a moveset again, or a victory lap |
| Resonate | "The boss's stats will scale to match the player's progression. This only applies if the player's stats are higher than the original boss's stats." | Testing a developed build against a fight that can still hurt |
The second sentence of the Resonate line is the one that matters. Scaling only switches on once you have outgrown the boss. If your stats are not higher than the boss's original numbers, nothing scales and Resonate is the original fight. Read literally, Resonate can make a boss tougher than Reminisce does, but never softer.
That sets up a clean split. Reminisce against an early boss with a late-game character is a formality — fine for watching a pattern again, useless as a test. Resonate is the mode that keeps an old fight relevant, because it pulls the boss up to where you are now.
What the notes do not say is how "progression" is measured: which stats scale, by how much, or whether it reads the character you brought or the save as a whole. That goes on the open-questions list at the end.
What a rematch pays: nothing, by design
This is the line in the 1.05.00 notes most worth knowing before you plan around the system:
"In Rematch, any consumables used will be restored to their prior state once the battle ends, and no separate loot can be obtained. Please note that this may be changed through future updates."
Two consequences follow, one good and one not.
Practice is free. Whatever you burn in a rematch comes back when the fight ends. That makes it the place to test a food loadout from the camp guide against a real boss without spending the stack, or to find out whether a new build holds before you take it somewhere that costs you.
It is not a farm. No separate loot means a rematch does not re-roll a boss's drops. That settles a question our armor guide left open — whether a boss-only refinement material could be farmed through rematches. Under the 1.05.00 rules it cannot, whichever bosses are on the list.
The "may be changed" caveat is still only a caveat. I went through the notes for every patch and hotfix from 1.05.01 to 2.03.02, and none of them adds rematch rewards.
The roster: 69, then five more
Spoiler note: Pearl Abyss tucked the names below inside a spoiler dropdown in its own patch notes. The table names late-game bosses.
1.05.00 opened Rematch to 69 bosses and did not list them. The first additions came thirteen days later. Patch 1.07.00 on May 15 "added more bosses that can be challenged again in rematches" and, unusually, printed where each one's fragment sits:
| Boss | Rematch location per 1.07.00 | Location changed in 1.13.00? |
|---|---|---|
| Muskan | Bonepit | Not listed |
| Corrupted Caliburn | Fort Musket | Yes |
| Goyen | Spire of the Sun | Yes |
| Draven, the Crowcaller | Church of West Demeniss | Yes |
| Clockwork White Horn | Gate to Advancement | Yes |
That adds up to 74: the launch 69 plus these five. Pearl Abyss has not printed that total itself, and no patch note after 1.07.00 announces more rematch bosses. The Journal's Bosses tab is the list; the patch notes are not.

The same 1.07.00 notes carried a second change: rematch locations for bosses originally fought in the Abyss were adjusted to take place on land. The likely reason is in the timing. Rematch was open to all three characters from the start, but until 1.13.00 only Kliff could enter the Abyss, so an Abyss-bound fragment would have been out of reach for two thirds of the cast.
One more name is confirmed rematchable by a bug fix rather than a list: 1.06.00 fixed a rematch with Titan opening with Titan striking the player.
Four of the five have since moved
1.13.00 on July 3 opened the Abyss to Oongka and Damiane and, in the notes' own word, "accordingly" changed the Memory Fragment locations for certain rematchable bosses. It names four: Corrupted Caliburn, Goyen, Draven the Crowcaller and Clockwork White Horn. It does not say where they went.
So for four of the five rows in that table, the 1.07.00 location is the old one. Open Map before you ride to Fort Musket.

Rematches at a retaken fort
One interaction with Re-blockade is worth a paragraph. A stronghold an enemy faction retakes goes through a Reconstruct stage after the fight, and 1.12.00 on June 19 "improved rematches so that it is now available at a stronghold undergoing reconstruction" — which implies that before June 19, a reconstructing stronghold blocked them. If a boss's fragment sits inside a fort that keeps changing hands, the Reconstruct stage no longer locks it. How the stages and the frequency settings work is in the Re-blockade guide.
The rematch fixes in the patch notes
Rematch has had a steady trickle of fixes. These are the lines that name it, plus a selection of memory-fragment and lantern fixes that bear on how a rematch starts (the notes carry other lantern and memory lines that do not):
| Patch | Date | What changed |
|---|---|---|
| 1.06.00 | May 11 | Fixed a wrong leave-the-combat-area warning in some rematches, the character turning invisible in some rematches, the boss combat-area marker lingering after loading a save mid-rematch, and a Titan rematch opening with Titan hitting you |
| 1.07.00 | May 15 | Five bosses added; rematches for Abyss bosses moved to land |
| 1.08.00 | May 22 | Fixed the game or rematches loading abnormally slowly as Oongka or Damiane in some situations |
| 1.10.00 | June 5 | Fixed a won rematch failing to keep progress and reverting to a previous state; fixed Damiane's greatsword looking wrong after giving up during a rematch |
| 1.12.00 | June 19 | Rematches available at a stronghold undergoing reconstruction |
| 1.13.00 | July 3 | Four fragments moved; fixed an occasional crash during boss rematches and comrades looking wrong while a rematch loads |
| 1.16.00 | Aug 1 | Fixed Blinding Flash not showing a memory fragment's location; dying "while reading a memory fragment" now offers only Revive at Checkpoint |
| 2.01.00 | Sept 4 | Fixed being able to walk around holding the lantern during a memory fragment |
| 2.03.01 | Sept 21 | Fixed lantern aiming not working with a remapped controller input |
Two things to take from it. The 1.10.00 progress fix is the one that mattered most: until June 5, winning a rematch could fail to stick. And the greatsword line in the same patch confirms something the 1.05.00 rules do not spell out — you can give up a rematch partway through.
The 1.16.00 and 2.01.00 lines say "memory fragment," not "rematch." Memory Fragments are a wider category that also covers story memories read with the lantern and the Visione — patch 1.00.03 in launch week made the Visione play automatically after reading one — so those two fixes may reach beyond rematches. They are listed here because a rematch starts the same way. The live Known Issues notice, last updated September 21, lists no rematch problem.
Where one guide slips
Console Pulse's rematch guide (last updated September 7) credits the fix for won rematches reverting progress to patch 1.09 and the reconstruction change to patch 1.10. Pearl Abyss's notes put them in 1.10.00 and 1.12.00; the 1.09.00 notes contain no rematch line. Its core rules — fragment activation, the two modes, the no-loot line — match the 1.05.00 notes.
What Rematch is actually for
No loot changes the job description. Four uses hold up:
- Testing a respec. Since 2.00.00, skill resets are per character and refund that character's Abyss Links, as our Abyss Link guide covers. Rebuild one character, walk to a fragment, and try the new kit on Resonate before you trust it in the story.
- Learning Oongka or Damiane. Rematch has been open to both since 1.05.00. A boss whose pattern you already know is a cleaner place to learn a second character than a fight you are also learning.
- Practising with your real consumables. They come back when the fight ends, so there is no reason to go in light.
- Checking a boss after a patch. Pearl Abyss keeps retuning fights: 2.00.00 split the Golden Star battle into distinct phases with phase-specific attack patterns. Whether Reminisce serves a reworked boss as you first met it or as it plays now is one of the things the notes leave open, so treat this use as a maybe.
One use does not hold up: grinding. Nothing drops.
What Pearl Abyss has not published
- The 69 launch names. The notes name the five 1.07.00 additions and, through a bug fix, Titan. The rest you learn from your own Journal.
- Where the four 1.13.00 fragments went.
- How Resonate measures progression — which stats scale, by how much, and whether it reads the character you brought.
- Whether the Easy/Normal/Hard setting added in 1.04.00 applies inside a rematch.
- What Reminisce does with a reworked boss, such as Golden Star after 2.00.00: the version you first met, or the current one.
- Whether 2.00.00's new boss memory fragments are rematches. The notes say 2.00.00 added "knowledge, items, memory fragments, dialog lines and conversations to strengthen the narrative of bosses," and nothing more.
- Whether rematches will ever pay. 1.05.00 says the no-loot rule "may be changed." Nothing has changed it through 2.03.02.
- Whether DLC enemies join the list. Pearl Abyss's Charting the Unknown page promises "formidable foes" across land and sea, and a notice posted September 30 moved the DLC's release to October 29, 2026. Nothing about rematches has been said.
Quick Action Checklist
- Beat the boss first. Its Memory Fragment only activates after the kill.
- Find fragments under Journal > Knowledge > Memory Fragments > Bosses > Open Map, or on the World Map and minimap.
- Light your lantern at the fragment and read it to start.
- Pick Reminisce for the boss as you first met it, Resonate to scale it up to your progression — scaling only applies once your stats beat the boss's originals.
- Bring any of the three: Kliff, Oongka or Damiane.
- Spend consumables freely. They are restored when the rematch ends.
- Do not farm. A rematch drops no separate loot.
- For Corrupted Caliburn, Goyen, Draven the Crowcaller and Clockwork White Horn, trust Open Map over any location list from before July 3.
- A retaken stronghold in Reconstruct no longer blocks rematches there (1.12.00).
- On a controller with a remapped lantern-aim input, be on 2.03.01 or later.
Frequently Asked Questions
How do you rematch a boss in Crimson Desert?
What is the difference between Reminisce and Resonate in Crimson Desert?
Do boss rematches give loot in Crimson Desert?
How many bosses can you rematch in Crimson Desert?
Can Oongka and Damiane do boss rematches in Crimson Desert?
Why can't I find a boss's Memory Fragment in Crimson Desert?
Keep Reading
- Pearl Abyss — Patch Notes Version 1.05.00 (May 2, 2026): Rematch added with 69 bosses, Memory Fragment activation, Reminisce and Resonate, consumables restored and no separate loot
- Pearl Abyss — Dev Update (April 9, 2026): boss rematches announced
- Pearl Abyss — Patch Notes Version 1.04.00 (April 23, 2026): boss rematches "will be added soon", difficulty options
- Pearl Abyss — Patch Notes Version 1.06.00 (May 11, 2026): rematch combat-area, invisibility, map-marker and Titan rematch fixes
- Pearl Abyss — Patch Notes Version 1.07.00 (May 15, 2026): five rematch bosses and locations, Abyss rematches moved to land
- Pearl Abyss — Patch Notes Version 1.08.00 (May 22, 2026): slow rematch loading as Oongka or Damiane fixed
- Pearl Abyss — Patch Notes Version 1.10.00 (June 5, 2026): won rematches reverting progress fixed, giving up during a rematch
- Pearl Abyss — Patch Notes Version 1.12.00 (June 19, 2026): rematches available at strongholds undergoing reconstruction
- Pearl Abyss — Patch Notes Version 1.13.00 (July 3, 2026): Oongka and Damiane enter the Abyss, four rematch fragment locations changed, rematch crash fix
- Pearl Abyss — Patch Notes Version 1.16.00 (August 1, 2026): Blinding Flash memory fragment location fix, Revive at Checkpoint when dying while reading a memory fragment
- Pearl Abyss — Patch Notes Version 2.00.00 (August 25, 2026): boss narrative memory fragments, Golden Star phases, per-character skill resets
- Pearl Abyss — Patch Notes Version 2.01.00 (September 4, 2026): lantern movement during a memory fragment fixed
- Pearl Abyss — Patch Notes Version 2.03.01 (September 21, 2026): lantern aiming with a remapped controller input fixed
- Pearl Abyss — Patch Notes Version 1.00.03: Visione plays automatically after reading memory fragments with the Lantern
- Pearl Abyss — Known Issues (last updated September 21, 2026): no rematch issue listed
- Pearl Abyss — Charting the Unknown: Release Date Update (September 30, 2026): DLC moved to October 29, 2026
- Pearl Abyss — Charting the Unknown official DLC page ("formidable foes" across land and sea)
- Console Pulse — Crimson Desert Boss Rematch Guide, last updated September 7, 2026 (rules summary; patch attributions for two fixes differ from Pearl Abyss's notes)
- Crimson Desert Wiki (Fandom) — Crowcaller (Draven) page and image files for Reed Devil, Myurdin, Corrupted Caliburn and Crowcaller (image sources)
Related Guides

Crimson Desert Golden Star Boss Fight Guide
Golden Star is the Chapter 11 boss that hands you Blackstar, and no guide on this site has ever explained how to beat it. Here is the arena, the four attacks, the stagger loop that wins the fight, and an honest account of what update 2.00.00 changed about it — because every walkthrough of this fight, including ours, predates that patch.

Crimson Desert Known Issues and Workarounds After 2.0
Pearl Abyss keeps one known-issues notice for Crimson Desert and revises it in place rather than reposting it. Here is what the September 21 revision carries, which two bugs have a workaround written by the developer, which five entries left the list since August 31, and what the seven patches since Crimson Desert Enhanced actually fixed.

Crimson Desert Knowledge and Research Guide: Bells, Institutes and the 1.18 Rewrite
Crimson Desert logs almost everything you touch, then sells it back to you as stat caps and infinite arrows. Patch 1.18.00, live today, added a whole Knowledge category and quietly changed what research costs. Here is the discovery layer, end to end.

Crimson Desert Trading Guide: Wagons, Royal Posts and the 1.16 Rewrite
Crimson Desert shipped with a trading system that paid worse than mining diamonds by hand. On August 1 Pearl Abyss quadrupled royal trading post prices, added 133 posts and finally let you see prices before you drive. Here is the whole system, and the maths that now works.

Crimson Desert Combat Guide: Parry, Counter, Watch & Learn
Crimson Desert is not a Souls game wearing a bigger map. It is closer to a fighting game, and the players bouncing off it are all making the same three mistakes.

Crimson Desert Updates and Roadmap: Every Patch and What Comes Next
Six months of patches turned Crimson Desert into a different game. Here is what actually shipped, version by version, and the only three things Pearl Abyss has actually committed to next.