Lua Error when Picking Up Quest (while In Combat)
Gogo1951 opened this issue · 4 comments
Description
Went to pick up a quest in combat, and got this error.
3x ...eQuestie/Modules/Quest/QuestEventHandler.lua:235: attempt to index field '?' (a nil value)
[string "@Questie/Modules/Quest/QuestEventHandler.lua"]:235: in function HandleQuestAccepted' [string "@Questie/Modules/Quest/QuestEventHandler.lua"]:213: in function func'
[string "@Questie/Modules/Libs/QuestieCombatQueue.lua"]:25: in function <...eQuestie/Modules/Libs/QuestieCombatQueue.lua:17>
Locals:
self =
}
questId = 3523
cacheMiss = false
_ =
}
(*temporary) = nil
(*temporary) = "QUEST_ACCEPTED"
(*temporary) = nil
(*temporary) = "Objectives are correct. Calling accept logic. quest:"
(*temporary) = 3523
(*temporary) = "attempt to index field '?' (a nil value)"
QuestLogCache =
questLog_DO_NOT_MODIFY =
}
private =
}
}
_QuestLogUpdateQueue =
}
_QuestEventHandler =
}
questLog =
1302 =
}
625 =
}
717 =
}
659 =
}
2988 =
}
543 =
}
762 =
}
2877 =
}
3636 =
}
6612 =
}
1449 =
}
2880 =
}
1264 =
}
1179 =
}
}
QUEST_LOG_STATES =
QUEST_ABANDONED = "QUEST_ABANDONED"
QUEST_TURNED_IN = "QUEST_TURNED_IN"
QUEST_REMOVED = "QUEST_REMOVED"
QUEST_ACCEPTED = "QUEST_ACCEPTED"
}
QuestieQuest =
private =
}
}
QuestieJourney =
zones =
}
continents =
}
tabGroup =
}
zoneMap =
}
private =
}
questCategoryKeys =
}
}
QuestieAnnounce =
private =
}
}
IsleOfQuelDanas =
localizedPhaseNames =
}
private =
}
quests =
}
MAX_ISLE_OF_QUEL_DANAS_PHASES = 9
}
Questie version
10.6.0
Game flavor
Era/HC
Nah, it wasn't at sign-in. I think this was in Badlands and we had been questing for a bit... I think a buddy pulled some mobs and I was racing to get the quest for that mob. I think in Badlands, fighting the last stone elemental in the chain. But I forget.
I haven't been able to reproduce this. Just flagging it in case something obvious stood out. Likely an edge case.
Did this happen right after login? 🤔 Or do you remember if you dropped combat and then immediately returned to combat?
Questie does have a check to run certain things only after combat and this is one of the cases. But somehow the code ran in an invalid state causing this nilerror.
Yeah, this 100% is an edge case. It not even obviously to me to see how this can possibly happen. Needs more research
I got it again today.
Happens when you're questing and you have a mob or are running from a mob (so you're in combat) and you turn in a quest or pick up a new quest.
Basically, the situation is, "I'm not gonna kill that thing, I can sprint / or bubble / or ignore it... so I'm just gonna grab my quest and go."
Then when you snag the quest (or turn in a quest I think is when I was able to reproduce the issue), while in combat, it gives the Lua error.