The Ichor of Undeath
Djfe opened this issue ยท 14 comments
Description
The quest errors
error forwarding quest goal for the ichor of undeath
Wowhead link
https://classic.wowhead.com/quest=8256/the-ichor-of-undeath
Screenshots
Questie version
5.10.0_fd3ff918
@Djfe Perfect, thanks! I am glad this got finally fixed.
since it's easy to get the item from the ah/my bank, I'll restart the quest once this is fixed, so I can test the fix.
I just tested this fix (I downloaded the development stage of this mod right after the patch)
It works, no error, but it doesn't place a marker on the Ruins of Eldarath:
Powerful undead, such as the lingering highborne who wander the Ruins of Eldarath, are sometimes so infused with evil that it coalesces into a sickly greenish goo. To the living, this substance is known as ichor of undeath.
mobs that drop it (according to the comments):
https://classic.wowhead.com/npc=6116/highborne-apparition
https://classic.wowhead.com/npc=6117/highborne-lichling
further mobs according to wowhead drop tables:
https://classic.wowhead.com/npc=7864/lingering-highborne
https://classic.wowhead.com/npc=6118/varothens-ghost
@BreakBB please reopen this issue
This doesn't really make any sense to me, but I will investigate. Thanks for testing this ๐
This error is still happening in 5.10.3 only the lua line is 774 instead of 772/768 like in earlier screenshots
is it possible to produce a lua error with a stack trace? I have an add-on called swatter (part of auctioneer), that let's me output lua errors and copy them to my clipboard
Or is there another way how I can help with debugging?
@Djfe Sorry for not keeping you updated on this. It is really hard to find the reason for this because I can't test this quest and don't know another way to reproduce it.
I am using BugGrabber + BugSack to catch errors and investigate them. But I am not sure if this issue is caused by a logical or database problem.
The error states that some spawn data is/got corrupted and is a number instead of a table (with coords). I assume it's a logic error, but diving into that part of the code is really not easy.
We think we found the issue and the fix will be easy.
Keep an eye out for an update ๐