Blizzard Investigating Three Bugged Quests in WoW: Forever
Blizzard confirmed it is investigating three broken quests in WoW: Forever after its BlizzardCS support account posted directly on Wowhead quest pages.
Call of Earth, Biding Our Time, and Witch Doctor Ti’ik are all flagged as not working as intended, with no fix date given.
The Tech TL;DR:
- BlizzardCS acknowledged three bugged quests in WoW: Forever — Call of Earth, Biding Our Time, and Witch Doctor Ti’ik — via comments on Wowhead’s quest database.
- BlizzardCS has also flagged escort quests (Freedom to Ruul, Free From the Hold, The Defias Brotherhood) and an Undead Paladin quest, Rediscovering the Light, as under investigation.
- Blizzard has given no timeframe for fixes; one bug, a broken quest reward in Biding Our Time, already shows signs of a partial fix in player reports.
Three quests, three different failure modes
The bugs span the classic launch-window spectrum: a class-locked reward that never fires, a group loot drop that shortchanges party members, and a quest item that renders as an unusable red question mark. Completing Call of Earth as a level 3 Skyborne Shaman does not grant the Stoneskin Totem spell, and Ti’ik’s Head drops for only one party member when the quest is completed in a group.
BlizzardCS confirmed both on the quest pages themselves. On Call of Earth, the account wrote: “We’re aware that completing the quest as a level 3 Skyborne Shaman does not grant Stoneskin Totem spell. We’re already investigating this issue.” On Witch Doctor Ti’ik, it stated: “We’re aware that Ti’ik’s Head only drops for one party member when completing the quest in a group. We’re already investigating this issue.”
For Call of Earth and Witch Doctor Ti’ik, players had left few or no comments describing the bugs — though frustration about Ti’ik’s Head was evident.
The red question mark reward
Biding Our Time carried more community context. Several players reported in Wowhead’s database comments that Filcher’s Cowl, the quest reward, was unusable — displaying as a red question mark.
Some later comments claimed the item was fixed and they had received the cloak. BlizzardCS nonetheless posted: “We’re aware that the quest may award an item with a red question mark that cannot be used. We’re already looking into this issue.”
That gap is the interesting part: player reports suggest a partial or intermittent fix, while the official account still lists the bug as open. Either the fix is rolling out unevenly, or the reward can break again under conditions players have not pinned down. Without a stated patch window, affected players are left checking their bags after each hotfix.
Escort quests fail due to NPC despawning
The investigation is broader than the three quests detailed. BlizzardCS has also commented on the quest pages for Freedom to Ruul, Free From the Hold, and The Defias Brotherhood — escort quests that can immediately fail if the quest giver dies or, in this case, despawns.
“We’re aware that Ruul/Gilthares Firebough/Defias Traitor may disappear when moving near or across zone and area boundaries, causing the quest to fail. We’re already investigating the issue.”
The pattern points to a zone-boundary or area-transition bug affecting NPC persistence — the escort target despawns during a zone crossing, hard-failing the quest. One NPC, three quests, one likely root cause.
A fourth bug: Rediscovering the Light, an early Undead Paladin quest, sometimes grants no progress when players heal the Injured Deathguards NPCs. Blizzard acknowledged that “healing Injured Deathguards may not grant progress” and is investigating. That one is a progression blocker: paladins cannot finish the quest when the objective refuses to count.
Why the Wowhead comment strategy matters
Posting directly on database pages is an unusual support channel, but a rational one. Quest databases like Wowhead’s function as de facto bug trackers with player-verified reproduction steps, and a BlizzardCS comment there reaches exactly the players hitting the bug at the moment they search for it.
It also signals internal triage: each comment follows the same template — awareness, specifics, investigation underway — which reads like output from a structured issue queue rather than ad hoc replies.
The underlying workflow looks familiar to anyone who has run a production bug backlog. Player reports arrive through forums and in-game tickets, get deduplicated against telemetry, and land in a triage queue where each confirmed defect gets a public acknowledgment before a fix lands in a scheduled build.
# Illustrative: how a player bug report typically maps to a tracker entry
curl -X POST https://api.example-tracker.com/v1/issues
-H "Authorization: Bearer $TOKEN"
-H "Content-Type: application/json"
-d '{
"title": "Call of Earth: no Stoneskin Totem at level 3 (Skyborne Shaman)",
"labels": ["quest", "class-shaman", "confirmed"],
"body": "Repro: complete Call of Earth as level 3 Skyborne Shaman. Expected: Stoneskin Totem spell granted. Actual: spell not granted."
}'
That is the shape of the pipeline BlizzardCS’s comments imply — a confirmed, reproducible defect with expected-versus-actual behavior, waiting on a patch train. Studios running live games at this scale typically batch such fixes into scheduled maintenance windows rather than shipping one-off hotfixes per quest, which explains the absence of a fix date.
Players may re-check broken rewards
The practical guidance is limited, because Blizzard has committed to nothing beyond investigation. There is no timeframe for fixes. The one actionable signal is in the Biding Our Time comments: players who received the broken red-question-mark reward should know that some players report the item now works, which suggests re-checking the reward — or contacting in-game support about a bugged item — is reasonable while the official fix remains pending.
For studios and live-service teams watching this from the outside, the episode is a case study in community-driven QA: public database comments double as free reproduction data.
Blizzard, the company behind the bugged quests, was founded in February 1991 as Silicon & Synapse by three University of California, Los Angeles graduates: Michael Morhaime, Allen Adham, and Frank Pearce.
After a brief spell as Chaos Studios, it was renamed Blizzard Entertainment in 1994, the year it released Warcraft: Orcs & Humans — the game that eventually led to World of Warcraft in 2004, the franchise now confronting the Forever-era bugs. Since 2005 the company has also hosted BlizzCon, its annual fan convention, and in 2023 it became part of Microsoft through the acquisition of parent company Activision Blizzard.
No patch date, but the queue is public
Blizzard has not said when any of these fixes ship. What is public is the acknowledgment itself — four quest bugs confirmed across three quest categories, all carrying the same closing line: “We’re already investigating this issue.”
- Scientists Conduct First Dynamic Compression Experiments on Plutonium at National Synchrotron Facility
- Microsoft Ignite 2026: Satya Nadella Unveils Copilot as the New OS for Work and the Frontier AI Ecosystem
- RBA's Fifth Hike Adds About A$94 a Month on A$600,000; Three Voted to Hold (daybreakwire.com)