Revision 3

Patch Details

Overview

Patch 1.01.03 is a minimal single-issue hotfix that wrapped up the 1.01.x patch cycle. It addressed a bug where certain bosses would stop moving during combat, creating an inconsistent encounter experience. Unlike the Steam-only 1.01.02, this update shipped across every platform running Crimson Desert, including Steam (PC and Mac), PlayStation 5, PS5 Pro, Xbox Series X|S, Xbox on PC, the Epic Games Store, and the Mac App Store.

The release was the fourth hotfix in the roughly ten days following Patch 1.01.00 on March 28, 2026, underscoring the rapid cadence of post-launch support from Pearl Abyss during the game's first two weeks on the market.

The Fix

Fixed an issue where some bosses would sometimes stop moving during combat. This could cause encounters to feel broken or artificially easy when a boss would stand motionless mid-fight, breaking immersion and combat pacing.

Community reports indicated that the bug most often appeared during multi-phase boss fights, particularly when the player interrupted a boss attack at the exact moment a phase transition was about to start. The AI state machine could become stuck between phases, leaving the boss in a default idle state that ignored player actions. While this made the fight trivially winnable in most cases, it also caused progression issues when scripted phase transitions needed to occur for a particular attack sequence to trigger the fight's conclusion.

Impact

Because this bug affected core boss AI and could cause both an easier and a broken encounter depending on circumstances, Pearl Abyss prioritized the fix for rapid deployment. The minimal scope meant the hotfix could be tested and shipped within a day of the last 1.01.x update, closing out the rapid-fire hotfix sequence before the next content-focused patch.

Follow-Up Work

Patch 1.01.03 closes the 1.01.x hotfix line. Subsequent combat and AI tuning was bundled into Patch 1.02.00, which introduced the next batch of balance changes and quality-of-life improvements. Players who encountered related AI inconsistencies after 1.01.03 were directed to report them for inclusion in the 1.02.00 notes.

Platform Availability

Patch 1.01.03 rolled out to every supported platform on the same day, which was the standard for all-platforms hotfixes in the first two weeks of the game's release. The 03:05 UTC deployment time meant Steam players in Europe woke up to the fix, North American players received it mid-evening the day before, and Asian players had it in place ahead of weekend sessions.

Technical Background

Most of Crimson Desert's bosses use a tiered behavior tree that transitions between combat phases based on health thresholds, stagger values, and scripted story beats. Each phase transition swaps in a different attack pool and sometimes changes the boss's movement mode: grounded to flying, aggressive to defensive, single-target to area-of-effect. The transition itself is a brief blocking animation during which the boss's combat script hands off from one state to the next.

The bug fixed in 1.01.03 could trigger when the transition animation was interrupted by player input at a very specific timing window, typically a stagger or counter that landed in the last few frames of the phase-transition animation. When this happened, the AI could fail to complete the hand-off: it left the old state but never entered the new one. The boss reverted to an idle default behavior instead of the next phase, and because the idle behavior includes no attack patterns and no movement, the boss appeared to simply freeze in place.

The fix added a verification step at the end of the transition animation that confirms the new state loaded correctly; if the verification fails, the transition restarts from the beginning of the target phase rather than leaving the boss in a default idle state. This approach was chosen over trying to make transitions uninterruptible because player interrupts during phase swaps were a legitimate and intended part of many boss fights, and making the animations non-interruptible would have broken several scripted counter encounters.

Player Reports

Community reports first highlighted the bug in fights with bosses that had three or more phases. Players posted video clips of boss encounters where the boss stood motionless at a phase boundary, letting the player hit freely for the remainder of the fight. While some players appreciated the easier win, the reports made clear that the behavior felt unintended and broke immersion, especially when the boss's voice lines and cinematic triggers continued to reference a phase it had never actually entered.

In a smaller subset of cases, the bug had the opposite effect: the boss would freeze mid-attack, and the fight's scripted conclusion required a specific attack sequence to trigger. With the attack sequence never executed, the fight could not be completed. These were the reports Pearl Abyss prioritized, because they were progression blockers rather than minor inconveniences.

Verification After the Fix

After 1.01.03 rolled out, players reported that boss fights resumed their expected attack rhythm, phase transitions triggered reliably at intended health thresholds, and the idle-freeze behavior no longer occurred. Pearl Abyss continued monitoring community reports through the 1.02.00 development window to catch any remaining edge cases.

Closing the 1.01.x Cycle

Patch 1.01.03 capped a rapid sequence of four hotfixes following the 1.01.00 content update. In the roughly three-day window between March 28 and March 31, 2026, Pearl Abyss shipped: 1.01.01 (cross-platform gameplay fixes), 1.01.02 (Steam graphics fixes), and 1.01.03 (cross-platform boss AI fix). This cadence illustrated the post-launch strategy of fast, narrowly scoped hotfixes rather than monolithic patches that accumulated many changes at once.

Following 1.01.03, attention shifted to 1.02.00, which included a broader set of combat balance changes, quality-of-life improvements, additional quest fixes, and the next content drop. The rapid hotfix sequence set expectations for how quickly Pearl Abyss could respond to post-content-patch bugs and built confidence among the community that reported issues would be addressed in days rather than weeks.

For players tracking the post-launch timeline, 1.01.03 represented a turning point: after its release, the frequency of hotfixes dropped noticeably as the game settled into a more conventional patch cadence of bigger updates spaced further apart. The closing of the 1.01.x line was a quiet milestone that signaled the end of the initial rapid-response period.

Related Articles

• Patch Notes

• Patch 1.01.02

• Patch 1.02.00