The problem is that the public side of this one is still thin. Blizzard’s latest Diablo IV PC bug index shows “Of pests and Pestilence” as a fresh topic active on April 20, 2026, but the listing itself does not expose much more detail from the category page. That means nobody should pretend we have a fully documented breakdown of the issue yet. What we do have is a live current report attached to what sounds very much like a quest, event, or progression step that has gone rotten in some interesting way.
The title alone points toward a quest or objective problem
Even with limited public details, there is a grounded way to read this. “Of Pests and Pestilence” sounds like the name of a questline, objective, or event step rather than a random system bug. If that reading is right, then the likely category here is progression friction: an objective not updating, an enemy not counting, an interact point failing, or the game simply refusing to acknowledge that the player did the thing it asked for.
That matters because these are some of the most quietly infuriating Diablo 4 bugs. A flashy crash is obvious. A quest or objective that half-breaks is worse in a slower, nastier way. It leaves players stuck in the middle of content, wondering if they missed something, misunderstood something, or just got unlucky enough to hit one more rotten little seam in the game.
Diablo 4 already has a habit of making normal progression feel weirdly fragile
This fresh report also lands in a game that has already been collecting too many “basic loop broke again” stories. We recently covered how players said Ashava’s world boss cache gave no loot, how some monsters were allegedly becoming unkillable, and how wardrobe and transmog issues were still lingering. Different systems, same mood: Diablo 4 keeps producing little moments where players stop trusting whether a normal activity will actually behave normally.
That broader pattern is what gives even a vague report like this some editorial value. In a calmer week, a mysterious quest-sounding bug title might just sit there unnoticed. In Diablo 4’s current climate, it immediately reads like one more possible case of a supposedly simple piece of content turning into avoidable friction.
Thin details do not make it worthless, just early
To be fair, this is still an early watchlist story, not a slam-dunk confirmed outbreak. The public bug index shows the topic is live, but without a visible full write-up from the category page, the responsible read is that something tied to “Of Pests and Pestilence” appears to have gone wrong for at least one player, and the fuller nature of the issue may become clearer once the thread develops.
Sometimes that means the problem turns out to be tiny. Sometimes it becomes one of those quest bugs that keeps resurfacing for weeks because it blocks exactly the wrong piece of content. Right now, this one is interesting precisely because it sits in that uncomfortable middle ground.
For now, it is one to watch
Diablo 4 does not need every bug report to explode into a giant story for it to matter. Sometimes a weird title in the bug index is enough to flag where the next annoying little fire might start. And with a name like Of Pests and Pestilence, this one already sounds like it came preloaded with a bad attitude.
