Diablo 4is filled with quests that need to be completed. There are quests that are central to the story that need to be completed to move on, but there are also tons of different side quests that can earn you worthwhile rewards.

One of the many quests inDiablo 4you will probably encounter will be the Chasing Embers quest, which is part of a quest chain in Scosglen. In order to complete this one, you will need to complete some other quests first.

Diablo-4-Chasing-Embers-Remembering-The-Goose

How to Get Chasing Embers in Diablo 4

to even pick up theDiablo 4side questcalled Chasing Embers, you will need to complete the beginning of its quest chain. The first of these quests will begin at the Fat Goose Inn, which is located in Highland Winds in Scosglan. Here is the quest chain:

Like Pyre of Ash, Chasing Embers begins immediately after finishing the previous quest. You need to return to the Goose once more to talk to Torben, who agrees that Blackweald Company needs to be eliminated. Go east to the marked area called The Scar, and locate the Pyre Victim. You must save them from the pyre, then you will learn of the location of the survivor from the old Blackweald Company; this will complete Chasing Embers.

Diablo-4-Chasing-Embers-Map

Fixing the Chasing Embers Bugged in Diablo 4

ThisDiablo 4quest has been buggedsince release, and it is still bugged at time of writing. If you want to complete this quest and continue the chain, there are a couple of things you can try to complete it. The bug occurs when you walk up to the pyre; Torben is supposed to say “I hear a live one; hurry!” You get a message that he is no longer following you.

For many people, when you walk up to the quest marker, nothing happens. There are a couple of fixes you may attempt to get the line you need to keep the quest moving. Most of these suggestions from across the web work about half the time, so you may need to try more than one to fix it.

Diablo 4 Tag Page Cover Art

ADiablo 4update in July of 2025was supposed to address this issue, and it seems to have made it better for some people; however, the bug is still in the game at the time of writing.