Active Quest indicator broken #920
No Assignees
OrdisPrime
OrdisPrime
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: OpenWF/SpaceNinjaServer#920
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The active quest indicator on the top right of the screen resets to not having a quest whenever you click on it. This can be an issue for certain quests that require you to click it to load into a special mission (Saya's Vigil being one). It seems to be tied to the "ActiveQuest" field in MongoDB, as setting it manually to "/Lotus/Types/Keys/GlassQuest/GlassQuestKeyChain" makes the game behave as if Saya's Vigil is active.
please re-open if it is not fixed now.
I got this error upon completing a quest. I don't think you properly unset the active quest.
2025-02-08T23:09:48:491 [0.1.0] error: Error: Quest /Lotus/Types/Keys/InfestedIntroQuest/InfestedIntroQuestKeyChain not found in questCompletionItems while processing /api/updateQuest.php request at getQuestCompletionItems (C:\Projects\OpenWF\Space-Ninja-Server\build\src\services\itemDataService.js:148:15) at updateQuestController (C:\Projects\OpenWF\Space-Ninja-Server\build\src\controllers\api\updateQuestController.js:26:84) at process.processTicksAndRejections (node:internal/process/task_queues:95:5)different issue, but sure lets fix that.
My bad, I falsely assumed it had to do with ActiveQuest.
Nono, you're good. Happy that you reported it. Just for documentation purposes.. but doesn't matter.
Can you try with the latest update?
Your account has to own the quest keys though, just an entry in QuestKeys with ItemType: "QuestKey" aside of that, quest progression should work smoothly now.
Please report if that is not the case.
Funnily enough, I was just about to submit the exact same PR you just pushed. It works, although we should probably try to fill out questCompletionRewards.json at some point.