Diablo Immortal Fierce Pursuit Task May Be Bugged

 

Diablo Immortal has rolled out Fierce Pursuit as part of its larger DOOM-flavored event push, and it did not take long for the first bug report to crawl out of the floorboards. A fresh official forum post says one of the new event tasks is not correctly counting Castle Cyrangar boss kills, which is exactly the kind of problem that makes an event tracker feel less like a reward system and more like a suspicious little gremlin with a clipboard.

What players are reporting

According to the April 22 official Diablo Immortal bug report, the player started an Endless defence in Castle Cyrangar, killed three bosses over roughly 12 minutes, and had more than 20,000 points at the end of the run. The problem is that the Fierce Pursuit task only credited them with one boss kill instead of three. That is not a tiny rounding error. That is the event basically shrugging at two-thirds of the work.

The weird part is that it may not be fully broken

The same player later updated the thread with a second test: they ran another Endless defence, killed two bosses, let the mobs overrun the door, and this time both boss kills counted correctly. That makes the story more interesting and more annoying. It does not look like the task is simply dead on arrival. It looks inconsistent, which is often worse for players because it leaves everyone guessing whether they hit a bug, missed some hidden condition, or just got mugged by event logic for no good reason.

Why this one matters more than it sounds

On paper, this is just one bug thread with low traffic so far. In practice, it lands on day one of a new event that Blizzard itself describes as a rotating, reward-driven activity running from April 22 to May 13, with weekly featured modes feeding progress through the event structure. If task tracking is already acting strange on launch day, players are going to trust the reward ladder a lot less, and live-service games really do not need more trust problems right now.

Another bug-watch, not a full-blown meltdown

At the time of writing, the thread is live in Blizzard’s Bug Report section and does not show a visible Blizzard reply yet. So this is still best read as a bug-watch story, not proof that Fierce Pursuit is broadly busted for everyone. But it is a very fair warning sign. Diablo Immortal can get away with being noisy, grindy, and a little extra. What it cannot really afford is launching a fresh event and immediately making players wonder whether their boss kills count only when Sanctuary feels generous.

Posted in: blizzard, bugs, Castle Cyrangar, Diablo Immortal, event bug, Fierce Pursuit, rewards