Yeah. But… I’m a completionist. And I know the thing exists now.
Because this STILL needs visibility apparently.
I ended up getting mine some months ago, though it was after some crazy number of attempts over the course of months leading up to it. Then this last Friday I read this from the hotfixes listed on October 5th:
- Fixed a bug that could prevent Everlasting Horn of Lavaswimming from dropping as intended on completion of the Siege of Dragonbane Keep.
I just want to say, reading this kind of made me angry. Of course it’s good they’re now fixing the issue, but it irritated me for a few reasons:
- This vague description of the issue. Is the bug recent? Has it been there the whole time?
- Is the bug why it took people absolutely absurd numbers of attempts to get it, or is that a separate issue that’s going to still be the case going forward for the people who haven’t got theirs yet? (This would give false hope then to some players).
- If it has been there the whole time, and is the reason for the crazy drop rate, why did it take so long for Blizzard to address it?
The bottom line is this thing was left in a broken state for a very long time, and it was vague and unclear whether this broken state was intended or an actual bug.
Some people theorized that the drop rate was potentially “better” if making new characters (through class trials) to run them through the siege. That was how I got mine a few months ago, when I switched to that tactic, which at the time I thought maybe gave a better chance but now it turns out might have been overcoming an actual bug that made my normal characters ineligible.
I get that bugs happen, but I’d say this thing is an example of:
- Really poor reaction time from Blizzard. Do they need to just hire more people to monitor and collate feedback?
- Just as a general practice, that Blizzard should put a bit more quality control practices on rewards that drop through push-loot weekly events. That format of loot dropping makes it harder for players to track what is occurring with drop rates and why, making feedback more muddled. If Blizzard is going to use that method, which obscures more of what’s happening with flagging, loot eligibility, etc., they should make doubly sure the code is working right before making it live.
This has nothing on MoP bug issue or close to a bug issue of the Sha of Anger…and mount drop that was suppose to be on Sha of Anger when it went live in MoP…months and months went by …nobody was getting the mount…we bugged blizzard over and over about it …finally they caved in or just said heck with it the told us they forgot to put the Mount on the Loot table…
The bug has been in since very early Dragonflight. I farmed this for a long time and eventually got it via class trial spamming as outlined on WoWhead. Probably had about 800+ non-trial attempts. Other items affected by similar bugs were the toys off Fyrakk and Invoq, but I think they got quietly fixed as well.