Diablo 4: Lord of Hatred has a new bug-watch entry, and this one has the special launch-day stink of a quest system arguing with itself.
A fresh Diablo IV console bug report claims that a player was disconnected during the Lord of Hatred campaign and then could no longer progress. The strange part? The game reportedly says not all party members are on the same quest step — while the player says they are playing solo.
The party problem with no party
That is the kind of bug that sounds almost funny until it happens to your campaign. Being blocked because a party member is out of sync makes sense in a multiplayer ARPG. Being blocked because an invisible imaginary party member disagrees with your quest progress is much less charming.
The report comes from the Xbox section of Blizzard’s console bug forum and, at the time of writing, appears to be a single-player-submitted issue rather than a confirmed widespread problem. So no, this is not yet “everyone’s campaign is broken.” It is more specific than that — and honestly, more irritating because of it.
Disconnects make campaign bugs extra ugly
Disconnects are already annoying in Diablo. They interrupt flow, reset momentum, and usually happen at the exact moment you were starting to feel like the game respected your evening.
But when a disconnect appears to leave the campaign state confused afterward, that is a different level of trouble. A quest step mismatch can potentially strand a player between “I did the thing” and “the game refuses to believe I did the thing,” which is basically the digital equivalent of being trapped in a cursed DMV.
Lord of Hatred already has progression warnings
This report lands alongside other early Lord of Hatred launch issues. Diabloz already covered Blizzard’s official Lord of Hatred known issues, including the “She Sleeps Within You” quest blocker and the missing Talisman Tab problem.
That does not mean this solo party-step report is officially confirmed in the same way. It does mean campaign progression is already one of the areas players are watching closely. When the expansion is new, anything that blocks forward movement feels ten times worse, because nobody wants to spend launch week negotiating with a broken quest flag.
A small report worth watching
For now, this is best treated as a bug-watch story: one clear report, a nasty-sounding progression block, and no visible Blizzard reply in the thread yet.
If you are playing Lord of Hatred solo and get disconnected mid-campaign, it may be worth checking your quest state carefully before pushing on. If the game suddenly insists that your non-existent party is out of sync, congratulations: you may have discovered the loneliest multiplayer bug in Sanctuary.
Launch day bugs are one thing. Being ghosted by your own solo campaign progress is another.
