SOD - Magmadar Douse
- The character name and realm on which you encountered the issue, if it differs from your posting character.
WoW SOD US - Crusader strike horde - Clamcrammer
Encountered a bug yesterday where Magmadar’s douse was non-interactable. This caused us to be unable to summon major domo and progress in the raid. We were on heat level 3 and changed to heat level 2 at Barron Geddon. I’m not sure if this is related but wanted to provide context.
Below is the raid ID if that is helpful.
RAID ID : 42343237
I can’t give an ETA beyond “as soon as we can”. Fixing groups in this state is pretty complex. ![]()
Update: we just sent a fix for Magmadar’s rune not updating. If your raid is in a bad state, just swap the heat difficulty back and forth and that should activate the event that now allows you to douse the Rune of Kress in Magmadar’s room.
FuenteI’m passing it along back to the designers; sorry about this. >_<
Just for the purposes of clarification:
- New raids are fixed.
- Some raids that were already started can use the above fix to get their raids back into a good state.
- Some raids managed to get into a really bad state with regards to Magmadar and his rune, and that still needs work.

Can you head into Molten Core? I want to triple-check something in your instance.
I’m reasonably sure I know what’s going on, but I want to ensure that there aren’t any scenarios that I haven’t accounted for.
FuentePerfect, thanks, I got exactly what I needed, and it’s exactly what I expected. Appreciated!
FuenteWe are going to do our best to fix everyone, but I don’t have an ETA yet. ![]()
We are absolutely working very hard on this, though, I promise you.
FuenteClearing trash is fine.
I’m currently hanging out in your instance invisibly specifically, Annalura, so let me know if you need to reset it or something so that I can leave and not mess things up. ![]()
This is a very high priority issue for us. I can’t provide an ETA or any info beyond that. ![]()
Okay, this looks like it’s tackled. Thank you all so much for your patience.
If you’re in the really bad state, here are the steps to fix it:
If you’re currently in the instance
- Have everyone leave the instance.
- Have the raid-leader right-click their portrait and reset all instances.
- Re-enter the instance and swap the difficulties to a new one and back.
- If this doesn’t fix it, have everyone leave the instance and wait 30-45 minutes for the instance to cycle down.
- Re-enter the instance and swap the difficulties to a new one and back.
If you’re not currently in the instance and everyone’s been outside it for at least 30 minutes
- Re-enter the instance and swap the difficulties to a new one and back.
Yes. We’ve sent out a few fixes today that fixed up all of the scenarios around this bug that we’re aware of. The steps that I listed are how to pick up the final fix. ![]()
For clarification, we made some changes that went live about 30 minutes ago, and my steps are how to trigger those changes. apologies for being unclear.
FuenteThat literally should not be possible unless someone re-entered the instance while y’all were waiting. Checking.
FuenteI just ported to you and then checked out Magmadar Cavern, and it looks good to me. ![]()
On that note, I’m heading out for the weekend. I’ll keep an eye on the thread though, just in case. ![]()