#490 UpdateQuestZone() behaves erratically for Current Zone in quest journal

Open
opened 1 year ago by Dorbin · 1 comments
Dorbin commented 1 year ago

The Lua command, UpdateQuestZone(), used in quest scripts, works on the initial acceptance of a quest and reloading of quests. The issue occurs upon logging or after zoning.

Oftentimes, the quests using this Lua will lump into a completely unrelated zone area for the Current Zone in the Quest Journal.

Its use is often recorded as follows." function Init(Quest) AddQuestStepKill(Quest, 1, "... from the creatures in the Caves.", 5, 20, "...any creatures in the Caves.", 1350, ###) AddQuestStepCompleteAction(Quest, 1, "Step1Complete") UpdateQuestZone(Quest,"Caves") end

The picture included demonstrates MULTIPLE quests referencing Thundering Steppes when almost none of them go there.

The Lua command, UpdateQuestZone(), used in quest scripts, works on the initial acceptance of a quest and reloading of quests. The issue occurs upon logging or after zoning. Oftentimes, the quests using this Lua will lump into a completely unrelated zone area for the Current Zone in the Quest Journal. Its use is often recorded as follows." function Init(Quest) AddQuestStepKill(Quest, 1, "... from the creatures in the Caves.", 5, 20, "...any creatures in the Caves.", 1350, ###) AddQuestStepCompleteAction(Quest, 1, "Step1Complete") UpdateQuestZone(Quest,"Caves") end The picture included demonstrates MULTIPLE quests referencing Thundering Steppes when almost none of them go there.
Dorbin commented 1 year ago
Poster

For clarity (TL/DR)

UpdateQuestZone() in quest scripts incorrectly lists the Current Zone in the Quest Journal after zoning/relogging.

For clarity (TL/DR) UpdateQuestZone() in quest scripts incorrectly lists the Current Zone in the Quest Journal after zoning/relogging.
Sign in to join this conversation.
Loading...
Cancel
Save
There is no content yet.