Players have reported completing ordinary Battleground matches without receiving credit for the event task. In one particularly revealing case, a player lost two matches without progressing the objective, then won a third and immediately received credit. The same player repeated the experiment after the weekly event reset on October 28 and reported exactly the same result.
It raises an obvious question: does Diablo Immortal's Halloween event accidentally require a Battleground victory, even though the objective only asks players to participate?
Blizzard has not officially confirmed that interpretation, and the available reports do not establish that every player is affected. Nevertheless, the repeated observations suggest a possible mismatch between what the event tells players to do and what the game actually checks.
Two Lost Matches Don't Count, but a Victory Does
The issue first appeared on Blizzard's official Diablo Immortal bug-report forum on October 21, shortly after the Halloween event began. The original reporter had completed a Battleground match and could see the activity recorded in the game's Codex, yet the Hallow's Wake objective remained unfinished.
Initially, the explanation seemed relatively straightforward. Diablo Immortal has several PvP activities, and not all of them count as standard Battleground matches. Tower War and Chaos Convoy, for example, are separate from the ordinary Battleground options offered by the Battleground Captain in Westmarch.
Completing the wrong mode could therefore explain why the Halloween task failed to register.
But that theory became less convincing when other players began testing ordinary Battleground Assault matches.
On October 23, a player named Kilometer reported completing two Battleground Assault matches without receiving credit. Both ended in defeat. The player entered a third match, this time won, and immediately saw the Halloween objective marked as complete.
Another participant in the discussion confirmed that their own successful completion had also followed a victory, although that alone did not establish that losing would have prevented it.
The most interesting development came on October 28, when Kilometer returned after the weekly event refresh. Two more Battleground defeats failed to register, while a victory in the third match once again completed the objective.
That is a fairly specific pattern, and the fact that it occurred twice makes it worth investigating.
There are still important qualifications. The original reporter said the task worked during another attempt on October 22, without establishing whether that match was won or lost. Another player had also successfully completed the objective on October 21. This is not evidence of a universal failure affecting every account.
Instead, the reports point toward two possible explanations: either the event description is incorrect and a victory really is required, or participation is supposed to be sufficient and the game's completion condition is not working consistently.
Until Blizzard clarifies the requirement, neither explanation can be treated as confirmed.
Why a Small PvP Objective Can Become a Frustrating Problem
On paper, this is hardly the most dramatic bug Diablo Immortal has ever experienced. No characters have disappeared, no Legendary equipment has been lost, and the game is not suddenly summoning three extra Rift Guardians simply because somebody pressed the wrong button.
But there is an important difference between asking players to participate in PvP and requiring them to win.
Diablo Immortal's Battlegrounds are not particularly forgiving environments, especially for players who primarily enjoy PvE. Equipment, secondary attributes, team composition and matchmaking can all have a substantial influence on the result. Even a capable player can contribute meaningfully to a match and still end up on the losing side.
We have previously examined Blizzard's attempts to improve Battleground matchmaking, including adjustments designed to account more effectively for Armor and Armor Penetration. The competitive environment has also faced criticism over the enormous burst damage associated with Overpowering Blows.
For someone who enjoys Battlegrounds, another match is simply another opportunity to compete. For somebody entering PvP only because a seasonal event asks them to participate, an unexpected victory requirement can turn a brief objective into a frustrating series of attempts.
That matters during a limited-time event.
As detailed in our coverage of the October Halloween update, Hallow's Wake and Hallows Phantom offer activities that reward Hallowed Stones, which players can exchange for items including Legendary Crests, Telluric Pearls and cosmetic rewards.
The event runs until November 11, 2026, at 2:59 a.m. server time. Unused Hallowed Stones disappear when the event ends.
Diablo Immortal is also running its separate Long March reward campaign, giving players additional weekly objectives to complete. Keeping track of several event systems is already complicated enough without the written requirements disagreeing with the apparent completion conditions.
There is some encouraging news. One forum participant noted that the disputed Battleground task was not necessary to reach the weekly reward cap. That observation has not been independently confirmed for every player, but it suggests that those encountering the problem may still be able to collect their weekly rewards through other objectives.
What Players Should Do if the Battleground Task Won't Complete
For anyone encountering the issue, the first step is to make certain that the correct PvP mode is being played. Visit the Battleground Captain in Westmarch and select an ordinary Battleground activity rather than Tower War or Chaos Convoy.
After finishing the match, check whether the result appears in your Codex and whether the Hallow's Wake objective has updated. If the Codex records participation but the Halloween task remains incomplete, that distinction is worth noting when reporting the problem.
The community reports suggest that winning a subsequent standard Battleground match may resolve the issue. However, that is a player-observed workaround, not a guaranteed solution or an officially announced requirement.
Players can contribute to the investigation by reporting the match type, result, server, game version and whether the Halloween task completed. Screenshots showing the Codex and event objective are especially useful because they provide a clearer picture than simply reporting that the task did not work.
It is also worth checking the remaining weekly objectives before spending an entire evening pursuing one stubborn Battleground task. If enough event progress can be earned elsewhere, repeatedly attempting a match that refuses to register may not be necessary.
As of October 29, Blizzard has not provided a public explanation or announced a fix in the forum discussion. The available evidence supports investigating a possible victory requirement, but it does not prove that every Battleground defeat will fail to count for every player.
That distinction is important. Bugs are sometimes inconsistent, and Diablo Immortal has enough interconnected systems that apparently identical activities do not always produce identical results.
Still, the underlying complaint is reasonable. If a seasonal objective asks players to participate, finishing the correct match should be enough unless the game clearly says otherwise.
Diablo has always rewarded persistence, and sometimes defeating an especially stubborn enemy requires several attempts. But there is something faintly absurd about discovering that a Halloween participation task may be more demanding than its description suggests.
After all, losing a Battleground is already punishment enough.
