What happened
Blizzard shipped two July Diablo IV updates that focused on broken rewards, seasonal progression, class interactions, and dungeon behavior. Patch 3.1.1, build 72836, arrived on July 14 across all platforms. Patch 3.1.2, build 73020, followed on July 28.
The official patch page is a rolling record, so players need to match a fix to the build currently installed rather than treating every July note as one update.
What patch 3.1.1 addressed
The July 14 build targeted Season of Death Awakening problems, reward behavior, crafting costs, and class issues. Secondary reporting highlighted fixes involving Mythic rewards and several classes, while Blizzard’s full notes remain the authority for exact skill and item interactions.
The practical goal was reliability. A seasonal objective that does not complete or a reward cache that does not appear can stop progress even when combat itself is working. Reducing that friction can matter more to an active player than a small numerical balance change.
What changed on July 28
Patch 3.1.2 continued the cleanup. Blizzard documented a Warlock class-quest problem that could prevent the intended reward cache from appearing. It also fixed Nightmare Dungeons opened through War Plans on the Eternal realm incorrectly carrying seasonal affixes.
The notes included tooltip clarification for Petrify as well. Blizzard said the text change reflected existing baseline behavior rather than introducing a new functional adjustment.
Timeline and comparison
The two builds landed 14 days apart. That sequence shows a first broad correction followed by a smaller pass on remaining or newly verified issues.
Compared with a seasonal launch patch, these updates are maintenance releases. They do not need a cinematic reveal to affect daily play. Their value is measured by whether progression completes, rewards arrive, dungeons use the right rule set, and class skills behave as described.
Data players can check
Both builds were listed for all platforms, which should keep the main rule set aligned on PC, PlayStation, and Xbox. Players can verify the active build number from the game client and then test the specific activity that previously failed.
For reward fixes, the useful evidence is simple: does the cache appear after the quest or objective completes? For Nightmare Dungeons, players can check whether Eternal characters still encounter seasonal affixes through War Plans. These are observable outcomes, not vague performance claims.
What this means for players
Anyone blocked by one of the named issues has a reason to return after updating. Players whose builds depend on an affected class interaction should also reread the current tooltip before changing gear or skill points.
Large patch-note lists can create the impression that everything is fixed. In reality, they close specific reports. A stable result across different platforms and character states still matters.
Questions the record does not settle Patch notes cannot prove that every edge case is gone. Blizzard did not provide public failure-rate data, the number of affected accounts, or a complete schedule for the next balance pass.
It is also unclear whether later hotfixes will adjust the same systems without requiring another client download. Players should report reproducible problems with the build number and platform attached.
Bottom line
Diablo IV’s July work was about restoring trust in seasonal rules. Patches 3.1.1 and 3.1.2 addressed concrete blockers rather than adding a new activity. The pass succeeds if rewards, class quests, and dungeons now behave the way the game tells players they should.