Diablo IV 3.2.3 Targets a Questline Blocker, but Existing Characters Need a Workaround
Blizzard schedules Diablo IV build 3.2.3 for October 14. It aims to prevent a Splinter of a Prime Evil from blocking the seasonal questline; already affected characters are not reset automatically, but Blizzard gives a same-partition workaround.

Diablo IV patch 3.2.3, build 73883, is scheduled for all platforms on October 14. As of October 12, Blizzard's notes describe a planned change to a seasonal questline blocker, not a patch that has already shipped. The key caveat is for existing characters: the update is intended to prevent new cases, but Blizzard says it will not reset progress on a character already affected. The official patch notes give the workaround.
What causes the questline block
Blizzard says a character could use a Splinter of a Prime Evil before completing the seasonal questline. That could prevent completion of the questline and access to Prime Evil Powers. The planned 3.2.3 change is intended to prevent new cases; it does not repair existing quest progress.
Blizzard's Season of Hell's Legacy guide explains that players collect Splinters from Diablo, Baal and Mephisto, then choose a Prime Evil power. Prime Evil Powers are the seasonal reward linked to that quest progression; the patch note says using a Splinter before the questline is complete can block access to them.
The notes tie the blocker to that specific sequence; they do not say every seasonal quest issue has the same cause. Players with a different progression problem should not assume this patch or workaround addresses it.
The stated workaround uses a new character
Blizzard's workaround has three steps: create a new character in the same partition as the affected character, complete the seasonal questline with that character, and unlock Prime Evil Powers for all characters in that partition. The developer note gives the labels as “Normal/Hardcore and Normal/SSF.” It does not describe carrying the blocked character's quest progress over, so follow the same-partition instruction exactly.

Other fixes listed under 3.2.3
The October 14 entry also fixes other bugs. Tyrael's spawn location after Baal could make Baal's loot difficult to pick up. A Sandstone Golem could fail to respawn if the player died during its fight, and the Countess could pass through a fog wall and block encounter progress.
Blizzard also fixes a bug that prevented some affixes from being rerolled with the Horadric Cube: Impairment Reduction, Barrier Generation, +Healing and Critical Strike Damage. Another fix addresses monsters that failed to drop Unbroken Bones during the Necromancer's Call of the Underworld quest. These are corrections to listed bugs, not new reroll categories or a general increase to drops.
These items sit beside stability, performance, visual and interface changes in the same build. They are listed as planned fixes; the notes do not confirm that build 73883 is available before the scheduled date.
Keep the September build separate
The patch page also lists 3.2.2, build 73764, for September 30. That is the earlier release. Issues such as Druid Pulverize holding a staggered boss, the Tal Rune interaction, Sol Rune damage reduction and the Artificer's Obelisk display are listed under 3.2.2, not the upcoming 3.2.3 entry. Check the build header before treating one of those older repairs as new on October 14.
A recent r/diablo4 discussion links to the notes and raises questions about console timing, runeword enchanting and seasonal portals. Those are player questions, not fixes promised by 3.2.3. After October 14, check that build 73883 is available on the relevant platform before relying on the planned prevention change.
Sources & further reading
- Diablo IV Patch NotesBlizzard Entertainment · accessed Oct 11, 2026
- Diablo IV Patch Notes - Patch notes for October 14th updateReddit, r/diablo4 community post · accessed Oct 11, 2026
- Celebrate 30 Years of Diablo in Season of Hell’s LegacyBlizzard Entertainment · accessed Oct 12, 2026